Sezzle
Sezzle buy-now-pay-later payment gateway integration providing flexible payment options with authorization, refunds, and secure transaction processing.
Sezzle is a buy now, pay later provider. The customer is established at Sezzle checkout and every later charge is made against that customer, so card data is never sent.
Supported Functionality
| Feature | Supported |
|---|---|
| Authorization | ✅ |
| Capture | ✅ |
| Refund | ✅ |
| Void | ❌ Full refund issued |
| Card Tokenization | ✅ Customer token |
| Dynamic Merchant Descriptors | ❌ |
| 3D Secure | ❌ |
| $0 Transactions | ❌ |
Setup
To connect a Merchant using the Sezzle Gateway,
- First add Merchant
- Select Sezzle as the Gateway
- Add Gateway Details as outlined below
| Gateway Details | Description |
|---|---|
| Public Key* | provided by Sezzle |
| Private Key* | provided by Sezzle |
| Sandbox | Check this box if these are sandbox credentials. When checked, requests are sent to the Sezzle sandbox environment. |
| Merchant Payment Methods* | The types of payment methods this merchant accepts — Sezzle only. |
| Merchant Default Currency* | Default currency that will be used, if currency is not specified |
| Merchant Currencies* | All currencies accepted on this merchant |
| Bypass $0 Transaction Authorizations | Sezzle declines $0 sales. Check this box to bypass Sezzle entirely for $0 transactions and treat them as successful. This setting only applies to initial transactions — $0 renewals will always bypass the gateway. Learn more about $0.00 transaction handling. |
*Required
Supported Payment Methods
Sezzle
Void
Sezzle has no void operation.
Voiding a transaction in Vrio issues a full refund of the original charge instead.
Card Tokenization
Vrio stores the Sezzle customer established at checkout and reuses it for every later charge, so renewals do not send the customer back through checkout.
The stored value is a Sezzle customer reference rather than a card token — Vrio never sees or sends card data for a Sezzle order.
Dynamic Merchant Descriptors
Vrio does not send a descriptor to Sezzle with the charge.
3D Secure
Sezzle does not accept 3D Secure authentication data. Authentication values passed with an order are not sent to the gateway.
Checkout Redirect
Sezzle establishes the customer at its own checkout, so the first charge cannot complete in a single call. Vrio returns a response_code: 101 with the Sezzle checkout URL in the post_data field.
Send the customer to that URL. Once they have approved the payment plan and are returned to your redirect_url, complete the order with POST /orders/{order_id}/complete.
For handling the 101 response code, see Handling 101 Response Codes.
Testing
Note : Placing test orders using Sezzle test cards will not automatically set the order as a test in Vrio. Be sure to flag the order as a test using the is_test flag after the order is processed. For more details on placing test orders, click here.
For Sezzle test cards, check here.
Updated 2 days ago
