INPUT
You
Natural language command

Initializing MCP server
AI-native finance on Stellar
Pay3 is the MCP server that lets AI assistants manage wallets, run DeFi, and settle payments on Stellar — inside programmable policies, without ever touching your private key.
Try saying
"What’s my Pay3 balance?"

claude-desktop
> pay 5 USDC to John
pay3.wallet.transfer()
policy ✓ · TX confirmed · 3.2s
Stellar settlement, Soroban smart contracts, MCP for AI agents, and Blend · Phoenix · Aquarius for DeFi.
The pipeline
INPUT
You
Natural language command
MCP
AI Assistant
Calls Pay3 MCP tool
POLICY
Policy Engine
Validates every rule
AUTH
Session Key
Scoped authorization
SETTLE
Stellar
Transaction settles
Platform capabilities
01 — The Bridge
Pay3 exposes wallet, DeFi, and payment tools through an MCP server — so Claude, ChatGPT, Cursor, and Gemini can act on your behalf without ever touching your private key.
Explore MCP Toolspay3-mcp-server
01 — The Bridge
Pay3 exposes wallet, DeFi, and payment tools through an MCP server — so Claude, ChatGPT, Cursor, and Gemini can act on your behalf without ever touching your private key.
Explore MCP Toolspay3-mcp-server
01 / 06
02 — Delegated Trust
Soroban session keys grant AI assistants temporary, scoped authority. Set duration, spend caps, daily budgets, and allowed protocols — then revoke anytime.
See Session Keyssession-key.yaml
02 / 06
03 — Guardrails
Daily budgets, per-tx limits, allowed smart contracts, blocked actions — nothing executes until every rule passes. The AI proposes; your policy decides.
Review Policiespolicy-engine
03 / 06
04 — DeFi Native
Blend for lending, Phoenix for swaps, Aquarius for liquidity — your AI can supply, borrow, rebalance, and claim rewards across integrated protocols.
Explore Productsportfolio.rebalance()
Total managed
$11,250.56
+ $150.56 today
Blend · Supply USDC
APY 8.2%
Phoenix · XLM → USDC
Rebalance trigger
04 / 06
05 — Real Commerce
From restaurant supply orders to API subscriptions — AI validates policy, executes USDC transfers on Stellar, and settles in seconds with near-zero fees.
Explore Paymentspayments.payMerchant()
Merchant
Fresh Farms Co-op
Amount
85.52 USDC
05 / 06
06 — Agent Network
Run Claude for payments, Cursor for development, custom agents for procurement — all connected to the same policy engine and Stellar wallet infrastructure.
Start Buildingagent-activity.log
06 / 06
Security first
Every transaction is validated before execution. Session keys expire. Limits are enforced on-chain through Soroban custom authentication.
From MCP config to live Stellar transactions — under a minute.
Sign in with Freighter on mainnet. Pay3 links a separate allocation account — only that pot is available to AI sessions.
claude_desktop_config.json
{
"mcpServers": {
"pay3": {
"command": "npx",
"args": ["-y", "@pay3/mcp"]
}
}
}Set duration, daily budget, per-tx max, and approval threshold. Review permissions, then sign with Freighter and copy the one-time MCP token.
policy-engine — create session
→ session key issued
Add Pay3 to Cursor MCP. Ask for balance or “pay Hurain 0.5 XLM.” Policy checks every transfer; revoke anytime from the dashboard.
Agent connected
pay3-mcp-server · listening on stdio
> awaiting commands_
Common questions about Pay3's AI-native financial infrastructure.
Pay3 lets an AI assistant send Stellar payments from a separate allocation pot you fund — under session limits you authorize in Freighter. Your primary wallet key never leaves Freighter.
Connect Freighter, fund the allocation account, save contacts, create an AI session, then connect Cursor with your MCP token. Natural-language commands call Pay3 tools; every transfer passes the policy engine before it settles on Stellar mainnet.
Freighter for sign-in and session authorization on Stellar mainnet. Pay3 never stores your Freighter private key. AI spends use encrypted session material and the allocation pot only.
Stellar network fees are typically fractions of a cent. Pay3 itself does not charge a product fee in this beta. Only fund the allocation pot with amounts you accept spending.
Cursor is the recommended client (local or hosted MCP). Claude Desktop can use the same stdio config. Browser claude.ai custom connectors need a hosted HTTPS MCP URL.
Native XLM transfers are supported on mainnet. Swap quote/execute via Soroswap is available when pools exist and the session allows execute_swap. Broader DeFi UX is still expanding.