x402
x402 Payment Modes
x402 supports two main payment modes. The choice changes the settlement flow, the recipient model, and whether callback-enabled logic is available.
Why There Are Two Modes
- DIRECT keeps the flow simple for payment-gated delivery
- DELEGATE supports more advanced settlement and callback-triggered execution
DIRECT
DIRECT is the simpler model.
Best fit
- paid APIs
- content gating
- routes where the user should pay the merchant directly
Characteristics
- settlement target is the merchant address
- no callback contract flow
- simpler operator model
- lower integration complexity
DELEGATE
DELEGATE is the advanced model.
Best fit
- callback-enabled contract execution
- apps that need settlement orchestration
- payment-triggered minting, staking, or similar actions
Characteristics
- settlement target is delegated infrastructure
- callback-capable flow
- more moving pieces, but more flexibility
Comparison
| Area | DIRECT | DELEGATE |
|---|---|---|
| User transfer target | Merchant address | Delegated / TSS settlement address |
| Callback support | No | Yes |
| Integration complexity | Lower | Higher |
| Good fit | Gated delivery | Payment-triggered execution |
| Typical flow types | ERC20_DIRECT, SOL_DIRECT | ERC20_3009, ERC20_APPROVE_XFER, SOL_APPROVE_XFER |
How to Choose
Choose DIRECT if you need:
- the shortest path to production
- straightforward payment-gated access
- fewer backend and contract dependencies
Choose DELEGATE if you need:
- callback-enabled on-chain logic
- settlement orchestration through delegated infrastructure
- a flow where payment does more than unlock a response