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

* 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](https://merchant-help.sezzle.com/hc/en-us/requests/new) form.
* An approved Sezzle account is required to begin integration; [sign up](https://dashboard.sezzle.com/merchant/signup) if you don’t have one.
* Endpoints in this guide require an [authentication](/docs/api/core/authentication/postauthentication) token.

<Note>
  You can test your integration with Sezzle using [Sezzle sandbox test environment](/docs/api/environments).
</Note>

<Warning>
  This product is currently only available in the United States. Support for Canada coming soon.
</Warning>

## Integration Options

|                          | [Virtual Card SDK](./automated)                                                        | [Manual Integration](./manual)                                      |
| ------------------------ | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **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     |

<Note>
  **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](./automated#oncomplete-with-tokenization) keeps card data out of the browser, which can reduce your PCI scope.
</Note>

<CardGroup cols={4}>
  <Card img="https://mintcdn.com/sezzle/bhJvsyK0HUx1pDUg/images/docs/guides/virtual/Screenshot2025-05-12at11.40.11AM.png?fit=max&auto=format&n=bhJvsyK0HUx1pDUg&q=85&s=cf3bb6119a6f97bc3b3ce77b302b76d6" width="562" height="1054" data-path="images/docs/guides/virtual/Screenshot2025-05-12at11.40.11AM.png">
    The shopper selects "Make a purchase request" on the Virtual Card tab.
  </Card>

  <Card img="https://mintcdn.com/sezzle/bhJvsyK0HUx1pDUg/images/docs/guides/virtual/Screenshot2025-05-12at11.40.22AM.png?fit=max&auto=format&n=bhJvsyK0HUx1pDUg&q=85&s=97c565bc4907f9e3b5dd0f04eb130056" width="530" height="1040" data-path="images/docs/guides/virtual/Screenshot2025-05-12at11.40.22AM.png">
    The shopper enters the amount they plan to spend.
  </Card>

  <Card img="https://mintcdn.com/sezzle/bhJvsyK0HUx1pDUg/images/docs/guides/virtual/Screenshot2025-05-12at11.40.28AM.png?fit=max&auto=format&n=bhJvsyK0HUx1pDUg&q=85&s=44fe34b3bab159defd86de0f3cb9a233" width="558" height="1050" data-path="images/docs/guides/virtual/Screenshot2025-05-12at11.40.28AM.png">
    The shopper reads the loan terms and continues if they agree.
  </Card>

  <Card img="https://mintcdn.com/sezzle/bhJvsyK0HUx1pDUg/images/docs/guides/virtual/Screenshot2025-05-12at11.40.35AM.png?fit=max&auto=format&n=bhJvsyK0HUx1pDUg&q=85&s=afe1a80f2e8aa5662058af0d806c51c8" width="550" height="1054" data-path="images/docs/guides/virtual/Screenshot2025-05-12at11.40.35AM.png">
    The shopper uses the Virtual card at your checkout or terminal.
  </Card>
</CardGroup>