Customer tokenization allows merchants to store Sezzle as a payment method for future orders without customer interaction, ideal for subscriptions like semi-annual charges. To obtain that authorization:Documentation Index
Fetch the complete documentation index at: https://docs.sezzle.com/llms.txt
Use this file to discover all available pages before exploring further.
- Initiate and tokenize the order in a single session
- Redirect the customer to the checkout URL
Tokenization Process

- Tokenize Customer via Checkout
- The merchant calls
/v2/sessionwithtokenize: true, optionally including customer details to speed up registration for new Sezzle users. - Sezzle returns a session
tokenizetoken.
- The merchant calls
- Merchant Redirects User to Checkout URL
-
Customer sees option to allow merchant to process payments from their Sezzle account for future transactions.
- The customer may decide to allow this permission before completing their checkout.

-
If agreed, Sezzle redirects back to the merchant’s session complete URL, appending a
customer-uuidquery parameter. -
Alternatively, the merchant can call
/v2/tokenwith the session tokenize token to retrieve the UUID.
-
Customer sees option to allow merchant to process payments from their Sezzle account for future transactions.
- Charge Customer
- The merchant uses the
customer-uuidto create orders via/v2/customer/{customer_uuid}/order. - If the authorization is approved, the merchant can manage the order (release, capture, or refund) using
/v2/orderendpoints.
- The merchant uses the
Notes
- Tokenization is optional, recommended only for charging via Sezzle outside standard checkouts.
- Orders created via customer UUID are treated the same as those from a standard Sezzle checkout.
Customers
Use the customers endpoints to:- Delete a customer
- Get details on an existing customer
- Get a list of customers
- Create an order for a customer
- Preapprove an amount for the customer