Checkout lifecycle

A checkout session is the central object for a customer payment. It represents the amount due, the selected rails/network, and the current payment status.

Typical flow

1. Create session (merchant backend).
2. Customer pays (wallet transfer / network tx).
3. Matching / verification confirms funds received and attaches a definitive reference.
4. Session updates to paid (or expires if timeout).
5. Invoice / receipt may be generated and optionally enriched with attachments.

Integration recommendations

• Call create/init endpoints from your backend and store the returned session ID.
• Use polling or webhooks (if available) to detect payment state changes.
• Treat matching/verification as asynchronous: networks can be slow, and re-orgs/finality rules may apply.

Next: see errors & retries or browse the API Reference.