x402 Payment Schemes: Exact, Upto, and Batch Settlement

x402 Payment Schemes: exact, upto, and batch-settlement

x402 is not limited to one economic pattern.

13.1 exact

Use exact when the price is known before execution.

Examples:

Weather result                  US$0.01
Company lookup                  US$0.05
Document download               US$0.25
Premium report                  US$2.00
Compliance screening            US$0.15

Conceptually:

Price known
   ↓
Buyer authorizes exact amount
   ↓
Service is delivered
   ↓
Exact amount settles

Best for:

• simple API calls;

• fixed-price digital goods;

• content;

• one-off queries;

• straightforward demonstrations.

This is the first scheme to test.

13.2 upto

Use upto when the final amount cannot be known until the service has executed.

Example:

Maximum authorized: US$1.00

AI inference runs.
Actual token consumption produces:
US$0.37 actual cost.

Seller captures:
US$0.37

Conceptually:

Buyer:
"I authorize up to $1."

       ↓

Service runs

       ↓

Actual usage = $0.37

       ↓

Seller settles $0.37

Best for:

• LLM tokens;

• compute seconds;

• storage;

• bandwidth;

• data volume;

• variable-duration jobs;

• usage-metered services.

This is materially more interesting than a fixed-price paywall because it gives machine commerce a form of bounded authorization.

13.3 batch-settlement

Batch settlement addresses a critical problem.

Suppose an agent makes:

10,000 API calls

and every call costs:

US$0.001

If every US$0.001 logical payment becomes a separate on-chain transaction, the settlement overhead can destroy the economics.

Batch settlement separates:

authorization of value

from:

immediate on-chain final settlement

A simplified model is:

Buyer commits funds
      ↓
Call #1 → signed cumulative voucher
Call #2 → signed cumulative voucher
Call #3 → signed cumulative voucher
...
Call #5,000 → signed cumulative voucher
      ↓
Seller redeems / settles accumulated value
      ↓
One or relatively few on-chain settlements

The x402 Foundation describes this as a way to make high-frequency, sub-cent interaction economically feasible while preserving cryptographically verifiable payment commitments.

This is potentially important for:

• per-token AI billing;

• high-frequency agent loops;

• per-kilobyte data;

• per-query retrieval;

• machine telemetry;

• tiny inference tasks;

• high-volume machine marketplaces.

Related x402 Explainers

• Micropayment economics

• How x402 payments work

• Beta testing and proof

If You Are Building This Commercially

If the scheme settles in stablecoins but the business ultimately needs bank settlement, FX, or conventional payouts, review how stablecoin payment structures connect digital-asset settlement to fiat operations.

Key Takeaway

Use exact for known prices, upto for bounded variable usage, and batch settlement where high-frequency logical payments need to amortize settlement overhead.

This page is part of x402 Protocol Explained, the full guide to how machine-to-machine payments work.

Sources and Further Reading

• x402 v2 specification

• x402 batch settlement