Payments

The payment surface for autonomous coordination.

MPP, x402, AP2, Visa TAP, Mastercard Agent Pay, Tempo, on-chain settlement, and per-token micropayment channels — one open network, every rail humans and machines need to transact.

Overview

Every rail. Human-to-machine, machine-to-machine, machine-to-human.

Tenzro Network supports the full payment surface for the AI age. HTTP 402-based machine payments (MPP, x402). Cart-mandate validation (AP2). Card network agent rails (Visa TAP, Mastercard Agent Pay). Stablecoin settlement (Tempo). Per-token micropayment channels for inference. On-chain escrow for high-value coordination. Bound to TDIP identity. Enforced by ERC-7579 validator modules. Settled in TNZO.

Rails

Six protocols. One unified surface.

MPP

Machine Payments Protocol co-authored by Stripe and Tempo. HTTP 402 challenge/credential/receipt flow with session management.

x402

Coinbase's HTTP 402 payment protocol. EIP-3009 transferWithAuthorization. CDP facilitator for verify/settle. Stablecoin-native.

AP2

Cart-mandate validation against TDIP delegation and runtime spending policy. Three-axis ceiling enforced before settlement.

Visa TAP

Visa's Trusted Agent Payments — card rails for agents acting on behalf of consumers, with cryptographic mandate validation.

Mastercard Agent Pay

Mastercard's agentic payment program — agent-initiated card transactions with verifiable delegation.

Tempo + Stripe

Direct Tempo participation — EIP-155 signing, RLP encoding, stablecoin settlement. Stripe Payment Intents for fiat onramps.

Micropayment channels

Off-chain per-token billing. Ed25519-signed state updates. Strict signature verification. Dispute resolution on-chain.

On-chain escrow

CreateEscrow / ReleaseEscrow / RefundEscrow consensus-mediated typed transactions. Derived vault addresses. Payer-only authorization.

Identity binding

IdentityPaymentBinder enforces TDIP DelegationScope and runtime SpendingPolicy — two-axis ceiling on every payment.

How it composes

From challenge to receipt.

01
Resource gates with HTTP 402
A model API, TEE endpoint, or any HTTP resource returns 402 with a payment challenge — MPP session, x402 stateless, or AP2 cart.
02
Agent submits credential
The agent's wallet signs a credential against the challenge — bound to its TDIP identity, validated against its delegation scope.
03
Network verifies
PaymentGateway routes to the right protocol — MPP, x402, AP2 — and verifies the credential against the challenge.
04
Settlement executes
Settlement engine moves TNZO, opens a channel, releases escrow, or routes to a card network — depending on the rail.
05
Receipt anchors
Signed receipt returned to client. Optional on-chain commitment for high-value flows. Channel state persisted for replay.
06
Mandate replay-safe
Nonce-based replay protection across every protocol. Mandate hashes bound to TDIP DID. Cross-chain mandates anchored.

Specifications

Protocols: MPP, x402, AP2, Visa TAP, Mastercard Agent Pay, Tempo, native
Channels: Off-chain micropayment channels with Ed25519 signature verification, on-chain dispute resolution
Escrow: On-chain typed transactions — CreateEscrow (0x01000010), ReleaseEscrow (0x01000011), RefundEscrow (0x01000012)
Identity binding: TDIP DelegationScope + runtime SpendingPolicy + ERC-7579 validator modules
Card rails: Visa Trusted Agent Payments + Mastercard Agent Pay with verifiable delegation
Stablecoin settlement: Tempo (EIP-155 signed transactions) + Stripe Payment Intents + Coinbase x402 facilitator

Get started

Ship on the open network.

Accept agent payments

Payments docs