Transaction Modes
ASP supports two payment initiation modes to accommodate different payment scenarios:
- Intent Mode: Payer-initiated
- Order Mode: Payee-initiated
Mode Comparison
| Feature | Intent Mode | Order Mode |
|---|---|---|
| Initiator | Payer | Payee |
| Interaction Rounds | One-round | Two-round |
| Price Discovery | Payer knows price upfront | Payee provides quote |
| Use Cases | Automated calls, micropayments | Task settlement, subscriptions |
| Complexity | Simple | Moderate |
Order Mode (Payee-Initiated Mode)
Definition
Order Mode is a payment model where the payee creates a payment request (order).
The payee first returns an order containing amount, terms, and other details (payment request). The payer then signs a payment mandate and submits it. The payee verifies and completes the transaction.
Key Characteristics
✓ Payee initiates order / payment request
✓ Two-round transaction
✓ Can include billing details, quotes, or task information
✓ Suitable for task settlement, subscription payments, pay-as-you-go scenarios
Flow Diagram
┌─────────┐ ┌─────────┐
│ Payer │ │ Payee │
│ Agent │ │ Agent │
└────┬────┘ └────┬────┘
│ │
│ 1. Request │
├─────────────────────────────────────────>│
│ │
│ │ Create
│ │ order
│ │
│ 2. Response embedded with │
│ payment order │
│ <─────────────────────────────────────-─┤
│ │
│ │
│ 3. Payment mandate │
├─────────────────────────────────────────>│
│ │
│ │ Verify
│ │ mandate
│ │
│ 4. Successful response │
│ <─────────────────────────────────────-─┤
│ │Process Steps
Round 1: Request → Order
- Payer sends service request to payee
- Payee calculates price and creates an order
- Payee returns order with amount, description, and details
The order includes:
order_idamountdescription- Optional: itemized breakdown
Round 2: Mandate → Service
- Payer reviews the order
- Payer signs a payment mandate (linked to the order_id)
- Payer submits mandate to payee
- Payee verifies mandate matches the order
- Payee executes the service
- Payee returns result
- Settlement happens later in the background
When to Use Order Mode?
Order Mode is ideal when:
- Service pricing is dynamic or complex
- Need to show billing breakdown
- User needs to approve before payment
- Large amounts or critical transactions
- Subscription and task settlement
Examples:
- Task completion billing
- Subscription service payments
- Usage-based metering
- Custom service quotes
Intent Mode (Payer-Initiated Mode)
Definition
Intent Mode is a payment model where the payer proactively initiates payment intent.
AI agents embed a one-time payment mandate directly in their requests (such as x402, A2A, MCP calls). The payee verifies the mandate and completes the transaction.
Key Characteristics
✓ Payer initiates payment
✓ No order or quote required
✓ One-round transaction
✓ Suitable for automated calls, micropayments, continuous delivery tasks
Flow Diagram
┌─────────┐ ┌─────────┐
│ Client │ │ Server │
│ Agent │ │ Agent │
└────┬────┘ └────┬────┘
│ │
│ Request embedded with │
│ payment mandate │
├─────────────────────────────────────────>│
│ │
│ │ Verify
│ │ mandate
│ │
│ Successful response │
│ <─────────────────────────────────────-─┤
│ │Process Steps
- Client Agent creates a payment mandate
- Embed the mandate in the request (typically as a Base64-encoded header)
- Server Agent receives the request and extracts the mandate
- Verify the mandate signature and amount
- Execute the requested service
- Return successful response
- Settle later - the mandate is queued for deferred settlement
When to Use Intent Mode?
Intent Mode is ideal when:
- Service price is fixed and known upfront
- High frequency, low latency interactions are needed
- Micropayments ($0.001 - $0.1 range)
- Automated agent-to-agent calls
- No user confirmation needed for each transaction
Examples:
- API calls billed per request
- Data streams billed per message
- Automated agent interactions
Choosing the Right Mode
Use Intent Mode When:
✓ Service price is fixed and public
✓ Need high-frequency, low-latency interaction
✓ Micropayment scenarios ($0.001 - $0.1)
✓ Automated agent-to-agent calls
✓ No need for user confirmation each time
Use Order Mode When:
✓ Service price is dynamic or complex
✓ Need to display billing details
✓ User needs to confirm before paying
✓ Large or critical transactions
✓ Subscription and task settlements
Implementation in Protocols
x402 Integration
x402 protocol can enable ASP for deferred payment functionality.
Intent Mode: Mandate embedded in request headers Order Mode: Order returned in response headers, then mandate in follow-up request
MCP/A2A Integration
MCP/A2A protocols can embed ASP to achieve pay-per-call payment models.
Both Intent and Order modes can be implemented depending on the use case.
AP2 Authorization
ASP's payment mandate can leverage the AP2 protocol.
Only mandates that obtain user authorization through AP2 are considered valid. This adds user consent as an additional security layer.
Next Steps
- Architecture - Understand the complete ASP system architecture
- Payment Mandate - Deep dive into payment mandates
- Debit Wallet - Learn about debit wallet design