Create payment
Signs and submits a payment on behalf of the specified wallet using either the x402 or MPP protocol.
Protocol selection (required protocol field in the request body):
x402: provide thex402_payment_requiredchallenge object received from the payee server.mpp: provide thempp_www_authenticatechallenge string and, optionally, anmpp_sessiontoken.
Idempotency: if you supply a request_id, the endpoint checks for a previously completed transaction with the same request_id for this wallet. When a match is found the original result is returned immediately (idempotent: true) together with the original response headers (retry_headers) so you can replay the HTTP payment call without re-signing.
The wallet must be active (non-archived) and your principal must hold the WALLET_TRANSFER permission for the target wallet.
Headers
Path Parameters
UUID of the wallet to sign and submit the payment from. Obtain this value from the wallet creation or list-wallets response. The wallet must be active (not archived).
Body
Unified payment request.
Protocol-specific fields are prefixed with protocol name (x402_ / mpp_).
Payment protocol: 'x402' or 'mpp'
x402, mpp Idempotency key
255Base64-encoded JSON from Payment-Required header
WWW-Authenticate header raw value
Session parameters for MPP session actions (open/voucher/close)
Response
Successful Response
Unified payment result.
CLI uses retry_headers to retry the original request.
Pagination metadata for list responses.
Supports both legacy offset-based and cursor-based pagination.
Cursor fields (has_more, after, before) are populated for
cursor-paginated endpoints. Legacy fields (offset, limit) are
populated when the caller uses the deprecated offset parameter.