Settlement
settlement
Settlement is the step that makes a payment final on the ledger that protocol uses. For x402 it is the facilitator submitting the transfer and the chain confirming it. For an MPP session it is a Tempo Settled event. For ACP it is the merchant's processor capturing a charge. For L402 it is payment of a Lightning invoice.
Explanation
Authorizations happen earlier. An EIP-3009 signature, an AP2 mandate, an ACP checkout session, and an unpaid Lightning invoice are not settlements. The x402 authorization flow verifies the signature, runs the resource, and only then settles. If settlement fails, the HTTP transport returns 402 again. A resource response without a confirmed transfer is not added to the index.
Agent GDP sums settlements it can attribute from a public log: facilitator USDC transfers, and positive deltaPaid on Tempo. It does not impute a settlement from a catalog price, a mandate, or a 402 challenge. The same purchase must not be added twice when one protocol is only the authorization layer for another.
Current index
| Period | Volume | Payments | Payers | Sellers |
|---|---|---|---|---|
| 24 hours | $9,785 | 112,082 | 23,367 | 7,498 |
| 7 days | $40,722 | 180,591 | 3,687 | 2,449 |
| 30 days | $41,811 | 202,420 | 3,727 | 2,460 |
Backfill in progress on base, solana, tempo. A checkpoint is still open, so recent totals can still move.
Live data
Related terms
Sources
- x402 Protocol Specification, version 2 — Coinbase x402
- x402 HTTP transport, version 2 — Coinbase x402
- Sessions: low-cost high-throughput payments — MPP
- Agent GDP methodology — Agent GDP