Payment Mandate
What is a Payment Mandate?
A Payment Mandate is a signed authorization from the payer that grants one-time payment permission to the payee.
Think of it as a digital check that authorizes the payee to debit a specific amount from the payer's wallet within a specified timeframe.
How Payment Mandates Work
┌─────────────┐
│ Payer │
│ Agent │ Requests mandate from wallet
└──────┬──────┘
│
↓
┌─────────────────┐
│ Agent Debit │ Signs the payment mandate
│ Wallet │ with cryptographic signature
└──────┬──────────┘
│
↓
┌────────────────────────────┐
│ Signed Payment Mandate │
│ ───────────────────────── │
│ • mandate_id │
│ • from_wallet │
│ • to_wallet │
│ • amount │
│ • nonce │
│ • signature │
└────────────┬───────────────┘
│ Base64 encoded
↓
┌──────────────────────────────┐
│ U29ycnksIHRoaXMgaXMgYSByYW... │ ← Embedded in protocol request
└──────────────────────────────┘Embedding in Protocols
Payment mandates are designed to be embedded directly in agent communication protocols:
- Base64 encoded for transport
- Embedded in HTTP headers (for x402, MCP, A2A)
- Verified by the payee before service delivery
- Submitted to settlement processor for deferred settlement
The Flow
The complete flow of payment mandate diagram is:
- Payer requests mandate from Agent Debit Wallet
- Wallet signs the payment mandate with cryptographic signature
- Mandate is Base64 encoded for transport
- Encoded mandate is embedded in A2A protocol payload (HTTP, x402, MCP, A2A, etc.)
- Payee receives the request and extracts the mandate
- Payee verifies the payment mandate
- If verification passes, payee executes the request
- Payee enqueues the mandate for settlement
- Later, settlement processor receives the mandate and settles
Next Steps
- Debit Wallet - Learn about the wallet that enables deferred settlement
- Settlement Processor - Understand how settlement works
- Embedded Payment - See how mandates integrate with protocols