For merchants
Get paid by AI agents, and win the chargebacks. Accept agent payments on the rail you already use; every payment carries a four-signature proof that auto-defends disputes. Open standard, no processor lock-in, settlement to you.
Open standard · EU-native
The payment network for the agentic economy.
Merchants get paid by AI agents. Consumers let their agents pay within limits they set, backed by cryptographic proof.
shop.bristleandslate.com agent_payment_initiate
User prompt
Buy my everyday brushes from Bristle & Slate.
Spend cap
Ships today · arrives in 2 days
An agent buying within a set spend cap, with a signed proof trail.
Two sides, one network
Agents that pay, merchants that get paid.
For you and your agent
Let your AI agent pay, on your terms. Connect a card once with a real bank check. Set limits and rules. Your agent pays within them, every payment is provable and reversible, and you see all of it.
Why OID4Pay
Trust, not just tokens.
OID4Pay is the authorization and trust layer one level above the processors: it issues the cryptographically-bounded mandate an agent needs to pay, and the signed proof a merchant needs to defend it.
Every payment carries four signatures
- Merchant signs the offer
- You authorize the mandate
- Agent proves it holds the key
- Merchant signs the receipt
Bounded mandates
Every payment is a mandate capped by amount, merchant, and expiry. An over-cap or wrong-merchant request is rejected at verification before any charge. You set the rules, and your agent stays inside them.
Set your limitsDispute defense built in
Each payment ships the four-signature proof, and it auto-assembles into the merchant's dispute evidence. Proof of authorization, not 'we have logs.'
See how disputes resolveOpen standard, your own rail
OAuth 2.0, DPoP, SD-JWT VC, RFC 9421. MIT SDKs in four languages plus an MCP server. Settlement goes to the merchant, on the rail they already use, with no lock-in.
Browse the SDKsHow a payment works
Authorize once. Bounded every time after.
- Authorize You approve your agent once.
- Bounded mandate Capped by amount, merchant, expiry.
- Settle Money lands in the merchant account.
Authorize once
You approve your agent with a strong customer authentication (SCA) check.
Bounded mandate
The authorization server issues a mandate capped by amount, merchant, and expiry.
Agent presents it
Your agent shows the mandate to a merchant at checkout.
Merchant verifies
The merchant verifies the four signatures before it charges.
Settles on their rail
The charge settles to the merchant's own account, via Stripe today.
Signed receipt
A signed receipt and dispute pack are recorded for both sides.
Open by design
An open, EU-native, dispute-proof layer.
OID4Pay sits on top of your existing processor (Stripe today): it is not a PSP, not a bank, and not a stored-value wallet. Money settles to your own account; we charge merchants a platform fee for the authorization and dispute service.
Open protocol
OAuth and the OIDF/IETF standards track, not a single-vendor, proprietary network.
Any agent, any merchant
Works above any agent and any merchant, on any rail. No lock-in.
Cryptographic dispute trail
A four-signature proof per payment, not 'we have logs.'
EU-native
PSD2 SCA model today; EUDIW wallet identity on the roadmap.
Built on open standards OAuth 2.0 PARDPoPSD-JWT VC mandatesRFC 9421 signed offers
Build on the open standard.
Free SDKs in four languages, an MCP server, and a sandbox to try it.