Order lifecycle

Keep the merchant database as the business-order source of truth and use SixPay events to drive payment state.

created -> pending_payment -> checkout_opened -> payment_locked -> paid -> delivered
                                  |                              |
                                  +-> expired                    +-> refunded

Recommended states

Merchant state	Trigger
`pending_payment`	Merchant created the order and session.
`payment_locked`	Verified `order.locked` event.
`paid`	Verified `order.paid` event.
`delivered`	Verified `order.delivered` or `order.force_delivered` event.
`expired`	Verified `order.expired` event.
`refunded`	Verified `order.refunded` event.

The exact fulfillment transition is merchant-specific, but every transition should be idempotent. Store the intentId as soon as the first correlated webhook arrives and retain the merchant’s own merchantOrderId throughout. Create a new checkout session for a retry or expired session rather than reusing browser credentials outside their lifetime.

Overview

Get started

Build checkout

Operate

Reference

Recommended states

​Recommended states

Recommended states