> ## 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.

# 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.

<Warning>
  All tokenized orders will be processed as Pay in Full.
</Warning>

<Warning>
  The approval URL was deprecated in April 2025. Now, 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.
</Warning>

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

<Frame>
  <img src="https://mintcdn.com/sezzle/hKhvshWly4M3cXTJ/images/docs/api/tokenization/Group7.png?fit=max&auto=format&n=hKhvshWly4M3cXTJ&q=85&s=65eea06cd7192e67090844474e8df4a2" alt="Group7 Pn" width="5616" height="5265" data-path="images/docs/api/tokenization/Group7.png" />
</Frame>

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.

     <Warning>
       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.
     </Warning>

     <Frame>
       <img src="https://mintcdn.com/sezzle/hKhvshWly4M3cXTJ/images/docs/api/tokenization/image.png?fit=max&auto=format&n=hKhvshWly4M3cXTJ&q=85&s=93b1f5565d1a531858f1169a7b520834" alt="Image Pn" width="568" height="837" data-path="images/docs/api/tokenization/image.png" />
     </Frame>
   * 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](/docs/api/tokenization/customers/deletev2token) a customer
* [Get](/docs/api/tokenization/customers/getv2customer) details on an existing customer
* [Get](/docs/api/tokenization/customers/getv2customerlist) a list of customers
* [Create](/docs/api/tokenization/customers/postv2customerorder) an order for a customer
* [Preapprove](/docs/api/tokenization/customers/preapprovev2token) an amount for the customer

<Warning>
  Customers are only those Sezzle users that have agreed to be tokenized by the merchant.  A customer is unique to a merchant. This API does not include all Sezzle users.
</Warning>