The payment railfor AI agents.
Your agents send, receive, and reconcile — on Solana now, on cards and ACH soon. Thirty cents per transaction, fifty cents per other service.
That's the whole bill.
Mission: Access all your payment services in one AI-powered global payment infrastructure platform.
Illustrative preview · crypto is live on devnet · cards/ACH in development
Crypto or not. Same agents either way.
Self-custody. Solana and USDC.
- Connect Phantom, Solflare, or Backpack. We never see your private key.
- USDC moves in under a second. Fees are a fraction of a cent.
- Send by @handle or wallet address. Devnet today; mainnet when licensing clears.
- Sends over the threshold run through a fraud check (Agent #51) before signing.
Pay like Venmo. Built to be backed like a bank.
- In development — no bank or card transaction can complete today. Attempted charges return 501/503, never a fake success.
- When it opens: link a bank or debit card the way you would on Apple Pay. You see dollars; we never hold the raw account number.
- Designed protections: PCI vault partner, chargeback rights, fraud check on transfers over $50. None of that is live yet.
- No seed phrases, no network picker. Until then, use the Crypto rail on Solana devnet to send test funds.
Crypto settles in seconds. Cards settle in days.
So they do not share a dashboard. Crypto clients get finality and asset mix; non-crypto clients get an authorisation rate, a settlement timeline and a dispute clock. Agent-initiated payments land in whichever ledger they belong to, tagged by the agent that made them and gated by the caps you set.
Self-custody. Keys stay in the customer’s own wallet — Phantom, Solflare or Backpack. Xaish never holds the asset, and every transfer above is a real signature you can open in a block explorer.
Two business days, against 0.8 seconds on the crypto rail. That gap is the reason both dashboards exist.
Not live yet. Seven adapters are scaffolded — Stripe, PayPal, Apple Pay, Google Pay, Plaid, Teller and Method — but no live charge path is wired, so /api/paynnt/gateway/charge returns 501 rather than a fabricated success a merchant could build against. The design above is what ships the day credentials and the capture path land.
Illustrative sample data · status chips reflect the real rail
The controls your agents need, and the brakes you need.
Phantom, Solflare, or Backpack. You sign a challenge so we know it’s really you — and we never see the key.
Set per-transaction, per-day, and per-month caps. The rail enforces them — separately for agents and for you in a browser.
Planned: the real card number stays inside a PCI-DSS Level 1 vault. Not live — no vault partner is onboarded, so no card can be tokenized today.
No agents in the loop. You sign every send yourself. Same wallet, just no autopilot.
Designed: one Paynnt call fans out to Stripe, PayPal, Google Pay, or Apple Pay. Charge path returns 501/503 today — never a fake success.
Designed: Plaid, Teller, and Method for checking, savings, and loans. Transfers return 501/503 today — no ACH can complete.
Built so your agent can find it.
Every Paynnt action is a typed POST. The schema lives in OpenAPI and the MCP descriptor. Hand your agent a key and it reads the catalog, picks the agent, calls it, and chains the next one — without you scripting the loop.