Introduction
This Sezzle technical documentation is designed for merchants integrating with Sezzle as a payment option.
Sezzle supports individually-authorized transactions for a single purchase of goods or services, and latest version also supports tokenization of a customer for future transactions.
In addition to a direct API integration, Sezzle also offers a lightweight Javascript SDK as well as integrations with some of the most popular eCommerce platforms.
If you have any questions regarding our API, please reach out to our team here: Submit Merchant Help Request
You need an approved Sezzle account to start the integration process. Please visit our signup page if you don't have a Sezzle account already.
Assume that all API methods require an Authorization bearer token
Direct Integration Quick Start
- Use API keys to obtain an authentication token
- Create a session with an order object
- Redirect user to Sezzle checkout URL
- User completes Sezzle checkout
- Sezzle redirects user back to merchant complete URL
- Manage the order with the Orders API
Open API
The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection.
View the Sezzle v2 OpenAPI Specification.
The OpenAPI Specification can be imported into the Swagger Editor to easily generate a Sezzle client in a variety of programming languages. If your language is not supported by Swagger, an alternate tool is OpenAPI Generator.