Consumer funding sessions

Consumer funding endpoints are used only by Paybytoken-owned experiences with a consumer access token. They are not merchant API endpoints.

Creation requires an Idempotency-Key. If the consumer's persistent address is not ready, the API returns 202 with consumer_funding_setup; retry after Retry-After using the same request.

An active session includes a short-lived funding capability. Send it only to the quote_url returned in the same object. The Payments service verifies its mode, session, recipient, asset, amount and expiry before requesting an exact-output quote.

Submitting a transaction changes the session to processing; it does not credit balance. The session becomes succeeded only when the matching Base USDC ConsumerDeposit is confirmed and the ledger credit is committed in the same transaction.

Operations

The following endpoints require an administrator access token:

The inspector requires at least one bounded identifier: id, consumer_account_id, or funding_transaction_hash. Reads and repairs are written to the Paybytoken Pay support audit log. Reconciliation never changes the consumer balance.