The Sezzle team has prepared a public Postman collection so merchants can quickly create customers (Sezzle users), sessions, and orders for sandbox testing.

Download and Install Postman

  1. Go to postman.com/downloads
  2. Click Download the App
  3. When the installation file has finished downloading, click the file to install the application
  4. Follow installation prompts on the screen

Add Sezzle Gateway Collection

When installation is complete, follow these steps to add the Sezzle Gateway collection to Postman.

  1. Click Run in Postman below to run the collection

  2. In the Web page that opens, select your operating system

  3. Click Open Postman if prompted

  4. In Postman, the Sezzle Gateway collection is now displayed in the Collections tab

Edit collection variables

Next, copy your API Keys from the Sezzle Sandbox Dashboard into Postman.

  1. In Postman, select Sezzle Gateway to open the collection tab
  2. In the collection tab, click Variables. This tab will store your credentials that apply across the collection
    • Alternatively, move the API Keys and Gateway URL variables to your sandbox environment variables
  3. To access your credentials, log in to the Sezzle Sandbox Dashboard
  4. Go to Settings > API Keys - your sandbox credentials are here
  5. In Postman, paste your credentials into CURRENT VALUE
    • Do this for PublicAPIKey and PrivateAPIKey

The other collection variables are predefined and all additional values will be automatically assigned for smoother testing.

Using the collection

  1. Open the applicable folder for your API version (default V2)
  2. Refer to the below diagrams for request sequencing
Gateway-Flow-Postman-v1

V1 Gateway Request Flow

Gateway-Flow-Postman-v2

V2 Gateway Request Flow

  1. Once a session is created, you must visit the checkout_url in the response and complete the checkout before testing most other Orders endpoints.
    • Log in at sandbox.dashboard.sezzle.com/customer
    • The customer account does not need to match the customer details given in the session payload
    • The phone number for the customer account must be real, but other personal information can be fake
    • OTP will be 123123