Agent tokens under mandate
An issuer provisions a token for one agent with merchant, amount and expiry limits taken from the customer's mandate.
Payments
Card issuing and acquiring
An agent should hold its own limited credential, not the customer's card number.
Card networks have published programmes for agent-initiated payments, built on tokens issued for a specific agent that can be limited and revoked without replacing the customer's card. Issuers need to tie those tokens to a mandate; acquirers and merchants need to recognise a known agent and keep evidence for chargebacks. AgenticOpenFinance maps mandates onto agent tokens and records each use.
What agents do
What you build on AgenticOpenFinance
Per-agent controls
The customer or the issuer suspends one agent's token without touching the card or other agents.
Agent recognition at checkout
Signed agent requests are verified at the merchant's edge so a known agent is not treated as a bot.
Challenge routing
When authentication is needed, the challenge reaches the cardholder, not the agent.
Chargeback evidence
Each agent purchase keeps the mandate, the token scope and the confirmation for dispute handling.
Value chain
The actors in this chain
AgenticOpenFinance connects them with one identity check, one mandate model, one policy and one evidence trail.
CardholderIssuerCard networkAgent operatorMerchantAcquirer
Typical flow
A governed agent flow, step by step
- Cardholder grants mandate
- Issuer provisions agent token
- Agent checks out
- Merchant verifies agent
- Authorisation within token limits
- Settlement
- Evidence for disputes
Live demo
See it in the terminal
A buyer agent's €2,150.00 is held until the seller agent's conditions are met, then released (demo). Demo data
DemoAll companies, people, agents and amounts are fictional. Protocol names refer to public specifications; naming one is not a partnership or an endorsement.
Glossary