Skip to main content
POST
Settle an x402 payment

Authorizations

Authorization
string
header
required

Bearer token authentication with a Circle API key. Use this for production settlement. Settling with an API key also binds the payTo to your Circle account, which ends the keyless trial allowance.

Body

application/json
x402Version
enum<integer>
required

x402 protocol version. Facilitator Service supports version 2.

Available options:
2
paymentPayload
object
required

x402 v2 payment payload. Includes the payment terms the buyer accepted and the signed EIP-3009 authorization that authorizes the USDC transfer.

paymentRequirements
object
required

Payment terms the seller advertises for an x402 resource. Facilitator Service validates that the buyer's authorization matches these requirements.

Response

Terminal or unresolved settlement result

success
boolean
required

Whether the transfer settled onchain within the wait window. Check the settlement-status extension to distinguish failed from pending.

Example:

true

payer
string
required

Buyer address recovered from the signed authorization.

Example:

"0x9aE2..."

transaction
string
required

Transaction hash on terminal success. Empty string when settlement is still pending or failed before submission.

Example:

"0x6f9e1d..."

network
string
required

CAIP-2 network identifier for the settled payment.

Example:

"eip155:5042002"

amount
string

Amount in atomic USDC units.

Example:

"1000000"

errorReason
enum<string>

Reason code. Present whenever success is false, either because the payment failed terminally or because the outcome was unresolved at the wait deadline (settlement_pending).

Available options:
settlement_pending,
invalid_x402_version,
unsupported_scheme,
invalid_network,
invalid_payment_requirements,
invalid_payload,
invalid_exact_evm_payload_recipient_mismatch,
invalid_exact_evm_payload_authorization_value_mismatch,
invalid_exact_evm_payload_authorization_valid_after,
invalid_exact_evm_payload_authorization_valid_before,
invalid_exact_evm_payload_signature,
invalid_transaction_state,
insufficient_funds
Example:

"invalid_exact_evm_payload_signature"

extensions
object

x402 extensions. Facilitator Service returns a settlement-status extension only after a payment has been recorded — on settlement_pending and on terminal failures that have a paymentId. Pre-recording validation failures (invalid_x402_version, unsupported_scheme, invalid_network, invalid_payment_requirements, invalid_payload, and the other request-validation errorReason values) return success: false with an errorReason and no extension, because there is no paymentId to reconcile. When present, the extension carries status, paymentId, and statusUrl. Settlement returns no poll hints.

Example: