Pay and get paid inside AI.
One platform, both sides.
Your customers and their agents buy from you.
Your agents buy from the businesses you depend on.
SolvaPay carries both, on the same rails, with one ledger per account.
A merchant account to sell.
A buyer account to pay.
Sell
- Products and plans
- Customers and their agents
- Calls, gated and billed
- Payouts to your Stripe
Pay
- A card, kept in the account
- Spend policies: limits, allowed merchants and a purpose
- Agents with their own identity
- Approvals, to a person
Guardrails for the buyer.
A ledger for the seller.
Identity for both.
Money never stops at SolvaPay.
Sales settle to your own Stripe account. Purchases charge the card in the buyer account. We hold neither.
Nothing moves without you seeing it.
Customers, products, plans, refunds and revenue in the dashboard, or inside your own AI workflow.
Your money is safe with us.
SolvaPay never holds your funds and never hands an agent your card.
Read how we keep you safe →One product. Every entrance.
One ledger.
Usable wherever the work happens.
The same wrapper at a REST route, a web app or an MCP tool. One product, every entrance, one customer identity.
Pricing is configuration.
One-time, subscription, usage, credits or hybrid, side by side on one product. Change the mix without redeploying.
Every call, settled to you.
Each call is identified, gated, billed and settled to your own Stripe account. Nothing is held by SolvaPay.
Every protocol, today and tomorrow.
Nothing to rebuild.
The protocols that exist now and the new ones as they land, on the same integration. You never rebuild anything; you turn them on.
How you’re found and called
- MCPBe a tool inside Claude, ChatGPT, Cursor and any MCP hostLive
- REST / OpenAPIThe same payable() wrapper on an API routeLive
- Web appCheckout inside your own app or chatLive
- CLISell to developers and their agents at the terminalLive
- WebMCPYour website as a toolWatching
- A2AAgent-to-agent discovery and callsWatching
- UCP / ACPAgentic commerce protocolsWatching
Every call, charge and decision.
On one statement.
Your merchant account keeps one record: the call, the plan that billed it, the charge, and the payout to your Stripe. Nothing moves without a line on the ledger.
Your agents pay on your authority.
Never with your card.
Each agent gets its own ID.
Named and described with its harness, under the account that owns it. It acts on your authority. It never holds your card.
You set what each agent can spend.
Spending limits per agent, per merchant, per call and per month. Within your limits, your agent pays. Before it goes past one, it asks you to raise it or allow the call.
Before an agent goes past a limit, it asks its owner.
With the amount and the reason. Raise the limit, allow the call, or decline. Every yes and every no lands on the statement.
Every protocol, today and tomorrow.
Nothing to rebuild.
The protocols that exist now and the new ones as they land, on the same integration. You never rebuild anything; you turn them on.
How an agent connects and pays
- Account MCPConnect, add an agent and list purchases, from inside the agentLive
- Buy with SolvaPayAn account your agents buy with, within your limits. Request early access on the Pay pageEarly access
- OAuth 2.1 + dynamic client registrationConnecting is the sign-upLive
- AP2Agent payments protocolWatching
- x402HTTP-native paymentsWatching
Every call, charge and decision.
On one statement.
Your buyer account keeps one record: the call, the policy that allowed it, the approval if one was asked, and the charge to your card. Nothing moves without a line on the ledger.
Pay and get paid inside AI.
Start with one side and scale to the other.
Book a call.
Talk to the team about selling, paying, or both. We’ll walk you through the platform and what it would look like for you.
Frequently /asked questions
Yes. Selling runs in a merchant account and buying in a buyer account, both on the same platform. They are separate logins today; each has its own ledger.
We ship support underneath you. Your integration does not change; the new protocol becomes another way to be found or paid.
No. Stripe is the rail for payouts today. If you already have a Stripe account, connect it in the go-live flow. New rails arrive as additions, not replacements.
Yes. A plan with usage on top, credits on a plan, a one-off next to a subscription. Set them side by side on one product and change the mix without redeploying.
No. The card is stored in the buyer account. Agents pay through the account, within the limits you set, and never see the card itself.
Stripe. Purchases charge the card in the buyer account and settle over Stripe’s rails, the same as the sell side.