- Sezzle Virtual Card allows merchants to:
- Accept Sezzle payments as credit card transactions.
- Seamlessly integrate with existing credit card forms at checkout.
- The virtual card is issued by Sezzle and charged through your existing payment processor (e.g., Stripe, Cybersource, Braintree). Your systems will handle the card data to process the charge.
- For API-related questions, contact the Sezzle team via the Merchant Help Request form.
- An approved Sezzle account is required to begin integration; sign up if you don’t have one.
- Endpoints in this guide require an authentication token.
You can test your integration with Sezzle using Sezzle sandbox test environment.
Integration Options
| Virtual Card SDK | Manual Integration | |
|---|---|---|
| Best for | Most merchants — fastest setup | Merchants needing full control |
| How it works | Drop-in SDK handles checkout popup/iframe and card data delivery | You implement the postMessage listener and card session API calls |
| Tokenization support | Yes — use card_response_format: "token" to receive a token instead of raw card data | Not available — card data is always delivered to your frontend |
PCI DSS consideration: Because you will receive and process virtual card data through your payment gateway, ensure your integration aligns with your current PCI compliance level. The SDK’s tokenization option keeps card data out of the browser, which can reduce your PCI scope.
The shopper selects “Make a purchase request” on the Virtual Card tab.
The shopper enters the amount they plan to spend.
The shopper reads the loan terms and continues if they agree.
The shopper uses the Virtual card at your checkout or terminal.