Legacy V1 compatibility endpoint. New integrations should use V2. V1 returns x402Version=1, method-specific facilitatorAddress, and V1 signer-map semantics.
Request parameters.
Return the live x402 V2 payment kinds available to the authenticated Developer Portal project. Use the result to construct HTTP 402 payment requirements. Copy the selected extra object verbatim and refresh cached configuration periodically.
Request parameters.
Legacy V1 on-chain settlement endpoint. New integrations should use V2. This operation can move real funds and is irreversible. V1 additionally returns confirmations in the settlement result.
Request parameters.
Submit a verified x402 V2 authorization on-chain. This operation can move real funds and is irreversible. For permit2-upto, provide settleAmount in atomic units. Business failure is returned as HTTP 200 with data.success=false; reconcile any non-empty transaction hash before retrying.
Request parameters.
Legacy V1 off-chain verification endpoint. New integrations should use V2. Portal identity is resolved from the API Key project, so merchantId is omitted from the external request.
Request parameters.
Validate an x402 V2 payment authorization off-chain without spending funds or broadcasting a transaction. Portal identity is resolved from the authenticated API Key project; omit merchantId. A validation failure is returned as HTTP 200 with data.isValid=false.
Request parameters.
B402PaymentsApi - object-oriented interface B402PaymentsApi