Open or settle a payment link
Single agent-facing endpoint for a payment link. Browsers receive an HTML landing that bounces to the canonical public resource. Agents receive an x402 v2 402 Payment Required challenge on first hit and retry the same URL with a PAYMENT-SIGNATURE header carrying a signed payload for the chosen chain. Successful retries return the settlement receipt; retries against an already settled link return 409; retries against a server that has paused settlement return 503 so callers know to back off and retry later.
Headers
Controls how timestamp fields are serialized in JSON response bodies.
Default (header omitted or any other value): epoch milliseconds as integers.
iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.
Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".
Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.
Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.
"iso8601"
Path Parameters
Response
Browser landing (HTML) or settlement receipt (JSON) for an agent retry. The body's media type follows the caller's Accept header.
Body returned after a successful (or declined) settlement attempt.
True if the submitted payment was accepted and settled.
CAIP-2 network identifier on which settlement was processed.
HAL-style hypermedia links for navigation and available actions.
On-chain transaction hash once settlement is finalized.
Wallet address that settled the payment, when known.
URL where a receipt for this settlement can be retrieved.