Introduction

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:

1. Initiate and tokenize the order in a single session
2. Redirect the customer to the checkout URL

For detailed instructions, view the Tokenization Process below.

​

Tokenization Process

1. Tokenize Customer via Checkout
   • The merchant calls /v2/session with tokenize: true, optionally including customer details to speed up registration for new Sezzle users.
   • Sezzle returns a session tokenize token.
2. 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.
     The only way for customers to authorize you to process future transactions on tokenized orders is by selecting that option in the initial checkout process.

   • If agreed, Sezzle redirects back to the merchant’s session complete URL, appending a customer-uuid query parameter.

   • Alternatively, the merchant can call /v2/token with the session tokenize token to retrieve the UUID.

3. Charge Customer
   • The merchant uses the customer-uuid to 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/order endpoints.

​

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