Token Checkout
Token-based checkout flow endpoints
Initiates a checkout session using a pre-generated token.
Token Generation
Tokens are generated during the standard checkout flow on the PaymentOptionSelectionPage. The token URLs (checkout_url and status_url) are included in that page's response.
Token generation requirements:
The request must be from an in-store (kiosk) device (
client_type: instore)User must be authenticated, OR the
CHECKOUT_WITH_TOKEN_ALLOW_ANONYMOUSsetting must be enabledA valid session must exist
If these conditions are not met, no token URLs are generated.
How It Works
Validates the token and retrieves the associated basket/user.
If user is anonymous, validates the
one_time_tokenquery parameter.Logs in the user (if authenticated) and redirects to the checkout page.
Sets the client type to
instorefor analytics tracking.
Configuration:
CHECKOUT_WITH_TOKEN_ALLOW_ANONYMOUS
boolean
false
Allows anonymous users to use token-based checkout. Can be changed via Admin Panel (Dynamic Setting).
Use Cases:
In-store kiosk checkout (customer scans QR code to complete purchase on their phone)
QR code-based checkout
Email/SMS checkout links
The checkout token (UUID format).
a1b2c3d4-e5f6-7890-abcd-ef1234567890Redirects to the checkout page
User mismatch
Invalid token or user not found
No content
Checks whether an order has been created for the basket associated with the token.
Business Logic:
Retrieves the basket associated with the token.
Checks if the basket status is
submitted(order created).Returns the order number if the order exists.
Use Cases:
Polling from external systems to check order completion.
In-store kiosk status display.
Real-time order tracking from POS systems.
The checkout token (UUID format).
a1b2c3d4-e5f6-7890-abcd-ef1234567890Order status
Token not found
Last updated
Was this helpful?

