Payments and settlement

Payments overview.

Every rail an agent needs: MPP, x402, AP2, Visa TAP, Mastercard Agent Pay, Tempo, and native TNZO. Bound to identity and policy at signing time.

STATUS: Testnet
CRATE: tenzro-payments
STABILITY: Stable
TYPE: Reference

Two-axis ceiling

Every payment passes through IdentityPaymentBinder. Both the protocol DelegationScope and the runtime SpendingPolicy must approve. ERC-7579 validator modules also gate signing on-chain.

Rails

MPP            Stripe + Tempo HTTP 402 session
x402           Coinbase HTTP 402 stateless
AP2            cart mandates
Visa TAP       Visa Trusted Agent Payments
Mastercard     Agent Pay
Tempo          stablecoin chain
Native TNZO    payment channels

HTTP 402

All HTTP-bearing rails use HTTP 402. The server issues a challenge; the client presents a credential; the gateway verifies, settles, and emits a receipt.

Self-hosted x402

For external-chain USDC, an operator verifies and settles from its own EVM relayer instead of a remote service. The node runs the eight exact/EVM checks — network, recipient, and amount parity, the signed time window, EIP-712 recovery, nonce reuse via authorizationState, funding via balanceOf, and a transferWithAuthorization simulation — then broadcasts the meta-transaction on the chain where the asset lives. Set the payments.x402_facilitator config block to enable it; tenzro_listX402Schemes reports the active mode as facilitator_mode.

Middleware

axum middleware automates challenge issuance and credential verification for resources behind a payment wall.

← All docs