Agent identity
Know which agent is acting, and attribute its permissions and authority before it can spend.
Payment infrastructure for AI agents, with built‑in contextual governance.
DORE is an independent financial infrastructure layer. One integration gives your agents access to multiple payment methods and providers, with financial controls built into every transaction.
| Agent and task | Authority | Amount | Status |
|---|---|---|---|
| AssistantTrain ticket | Approved by Sam | $64 | Paid and matched |
| Research agentData credits, March | Delegated budget: $200 a month | $260$60 over budget | Sent back for approval |
| Payroll agentPayroll run, March | Policy: monthly payroll | $48,200 | Paid and matched |
| Supplier agentInvoice INV-2207 | Policy: approved suppliers | $10,000 | Awaiting outcome data |
Agentagt_payroll_01
Policypol_payroll_monthly
EnforcementRigid
Payment methodBank transfer (ACH)
BankExample Bank
ReconciliationCompleted
How it works
One integration. Every provider.
Today, builders wire up cards, banks and tokenisation one provider at a time, each with its own API, credentials and controls. With DORE, your agent connects once and every payment gets the same financial controls.
AI agentRequests a payment method for a specific task
DORE
Payment orchestrationProvider routing and execution
GovernanceIntent, policies and approvals
One agent integration. Consistent financial controls.
Card issuingIssuer partners
TokenisationTokenisation partners
BankingACH and bank APIs
StablecoinsWallets and networks
Open standards
- x402
- AP2
- ACP
- UCP
Conceptual architecture. Capabilities are planned, and integrations are added with early customers and partners.
Payment toolkit
Everything an agent needs to pay.
From the rules before a payment to the proof after it, built as one infrastructure and governed the same way.
Before the payment
Know the rules
Policy lookup
Before it starts, the agent asks what it may buy: limits, approved merchants and who must approve. Pulled from your own systems where they are integrated.
Intent and approval
Record what was approved, and by whom, before anything is bought.
The payment
Pay through your partners
Virtual cards
Single-use cards for one task, issued by your issuer partner.
Card tokenisation
Real card details stay with the partner. The agent holds a token it can reuse safely.
Bank transfers
ACH through your banking partner, with the beneficiary and amount checked first.
Stablecoins
Pay in stablecoins where a supported wallet or network connection exists.
Open agent-payment standards
Designed to work with the standards agents and merchants are adopting. Whichever standard or rail carries the payment, the same controls apply.
- x402
- AP2
- ACP
- UCP
After the payment
Prove what happened
Transaction status
A breadcrumb of every step links the agent’s request to what was paid.
Reconciliation
Match each payment to its task and evidence, then learn for the next cycle.
Early access: these capabilities are planned and arrive integration by integration. Partners issue cards and move funds. DORE connects, orchestrates and controls.
Governance
Built into every transaction.
DORE takes part in execution, so it can do more than advise. Task intent, policies and approvals travel with every payment.
Detection
Compare what was intended, what policy allows and what is actually being bought. Spot drift at each step, not only at the end.
IntentTeam plan · $100
PolicySoftware up to $500
MerchantMatches the approval
TransactionEnterprise · $480
- At intent
- At checkout
- At authorisation
txn_7f21Drift: +$380
Enforcement
Through orchestration and detection, your policies and decisions come before agent reasoning. DORE aims to block, prevent or reduce the blast radius of a mismatched purchase.
Your decisionTeam plan · $100Locked
Agent reasoning“Enterprise looks better value”
- Block
- Prevent
- Reduce exposure
dec_9a3eBlocked · $480
Reconciliation
Match every payment back to its task and evidence, then learn from each cycle to tighten the next one.
Intent$100
Authorised$100
Cleared$100
Next cycle
Suggest lowering the software limit from $500 to $300.
recon_0312Paid and matched
Use cases
Built for developers. Designed for enterprises.
The same infrastructure serves one developer with one agent and a company with many.
Payment infrastructure
Give your AI agent a way to pay.
An AI assistant needs to book a $64 train ticket. It requests a payment method from DORE, which connects to your configured card issuer and returns a purchase-specific virtual card. The agent completes the purchase without integrating with the issuer directly.
Generic example. It does not describe an integration with any named service.
- AgentAsks to pay for the ticket
- DORERequests a scoped virtual card
- Card issuerIssues the card
Card returned to the agent
Card for this ticket only$64 · one use•••• 4821
What has to be in place
- The agent connects to DORE. A virtual card alone does not let every service connect automatically. It needs a DORE connection, such as an agent tool or API.
- Your card issuer is supported. DORE works through issuers that can create purchase-specific cards. Coverage is stated per connection and grows with demand.
Let agents pay with your existing card.
You want an AI assistant to make purchases using a card you already own. DORE connects to a supported tokenisation provider so the agent can use an authorised payment credential without accessing your underlying card details.
- Your existing card
- Tokenisation provider
- DORE
- Agent
Not a new card: your existing one, securely enabled.
Let agents pay suppliers directly.
A procurement agent receives an approved $10,000 supplier invoice. DORE verifies the beneficiary, amount and authorisation before instructing the company’s connected banking provider to initiate the transfer.
- Approved invoice
- DORE
- Connected bank
- Supplier
Stop purchases that don’t match the task.
An employee asks an agent to book a flight for under $300. The agent selects a $480 ticket. Although the card allows $500, DORE detects that the purchase exceeds the employee’s authorisation and blocks it where payment enforcement is supported.
Original taskFlight ≤ $300
Attempted payment$480
DORE decision Declined
One set of financial rules. Every agent.
Your company uses different AI agents for travel, procurement and software subscriptions. DORE applies your financial policies consistently across them, including spending limits, approved suppliers and required approvals.
Connections to policy, approval and finance systems are added with the early customers who ask for them.
Company policyApplies to every agent
SoftwareUp to $500 a month
TravelManager approves
SuppliersApproved list only
- Travel agent
- Procurement agent
- Software agent
Platform independence
Change payment providers, not your agent.
Your agent starts with one card issuer. As your business grows, you add a second issuer and a banking provider. DORE exposes those capabilities through the same integration, without requiring you to rebuild your agent’s payment logic.
Your agentUnchanged
Card issuer AConnected
Card issuer BAdded later
Banking providerAdded later
Scenarios are illustrative. Capabilities are planned and arrive integration by integration, and what works in practice depends on the agent connection and payment provider involved.
FAQ
Questions people ask.
Is DORE live?
Not yet. DORE is in early access: we are shaping it with the people who sign up. There are no live customer deployments or certifications to point to yet, and we will say so here when that changes.
Do my payment details stay private?
Yes. Your underlying card and bank details stay with your payment provider. DORE is designed not to hold your money: financial partners issue cards and move funds.
Does my agent ever see my card or bank details?
Not your underlying ones. Depending on the payment method, the agent may be given a purchase-specific virtual card, limited to that purchase, or may ask DORE to send the payment through your bank connection where supported.
Does DORE hold my money or issue cards?
No. DORE is designed to be non-custodial. Financial partners issue cards and move money; DORE checks, instructs and records.
Who owns my data?
You do. Your limits and purchase records are your confidential data. We do not sell transaction-level data.
Do my rules move with me if I change agent or provider?
Yes. Change your agent or payment provider without redefining your limits. You own them.
Do I need formal policies or a finance team to start?
No. You can start with one agent, your payment method and your own limits. Company policies, approvals and finance systems can be added later.
Will it work with every agent, payment method and provider?
Not at first. An agent has to connect to DORE, and a payment method has to be reachable through a supported provider. Coverage is stated per connection. Cards are the likely starting point, bank payments next, and wires, stablecoins and international methods are assessed one by one. Early integrations follow demand.
How firmly are limits enforced?
It depends on the connection. A DORE-connected agent tool checks before the agent submits. A provider that can ask DORE before approving adds an independent decline. Other connections are advisory, or reconcile afterwards. Each record shows which one applied, as in the example above.
Can DORE guarantee a bad payment is recovered?
No. Refunds, disputes and recalls depend on the provider. DORE aims to stop mismatches before payment where the path supports it, and to flag them afterwards where it does not.
Can I try it without anything being blocked?
Early partners can start in an observe-only mode, where DORE records and checks but blocks nothing. Switching on blocking is a separate decision.
For individuals, teams and companies
Get early access.
Tell us what you would like an agent to buy. We will get in touch to see if DORE fits, and your answers help shape what we build first.
What happens next
- You send the form. Only your name and email are required.
- We reply by email. We will say whether DORE fits what you want an agent to buy.
- Your feedback helps. It helps us prioritise what we build.
Thanks, your request is in.
We have received your early access request and will reply by email.
For ecosystem partners
Help shape how agents pay.
We want to work with agent builders, banks, card issuers, payment gateways and other payment providers. If you would like your agents or payments to work with DORE, tell us what you have in mind.
What happens next
- You tell us what you have in mind. A few lines is enough.
- We reply by email to talk through the next step.
Thanks, we have your message.
We have received your partnership enquiry and will reply by email to talk through the next step.