Sezzle

Sezzle For Merchants: Buy Now, Pay Later Acceptance For Online And In-Store Checkout

Sezzle is a buy now, pay later (BNPL) payment option that merchants can add to checkout to let shoppers pay over time. For merchants, Sezzle positions its offering around flexible installment plans (including Pay in 4, Pay in 5, Pay in 2, and Pay Monthly) and “plug-and-play” integrations with popular ecommerce platforms. Sezzle also supports direct API integration for custom builds, plus add-ons designed to reduce checkout friction, such as Express Checkout and on-site promotional messaging widgets.

What Sezzle Offers Merchants

At a high level, Sezzle provides:

• A BNPL payment method that can be offered in checkout, enabling shoppers to select a payment plan.

• Platform integrations for common commerce stacks and a direct integration path for custom implementations.

• Conversion-focused components such as:

  • Express Checkout, which can place a one-click Sezzle button on product, cart, or checkout pages.

  • Widgets that display installment messaging on product and cart pages.

The provider also highlights its scale to prospective users, stating that it is used by “over 13 million shoppers” and “over 40 thousand merchants.”

Where Merchants Can Accept Sezzle

Online Checkout And In-App Commerce

Sezzle’s developer documentation describes accepting web and in-app payments through its API integration. For merchants building their own checkout, Sezzle’s direct integration flow generally centers on creating a payment session and redirecting the shopper to Sezzle’s UI to complete checkout, then capturing funds when appropriate.

In-Store Acceptance Via Sezzle Virtual Card

For qualifying U.S. merchants, Sezzle offers an in-store solution through the Sezzle Virtual Card. Shoppers access the card through the app and then add it to a mobile wallet (Apple Pay or Google Pay only) to pay in-store.

This model is relevant if you operate physical retail locations and want BNPL acceptance without deploying a dedicated POS terminal integration.

Invoicing For In-Store Or Phone Purchases

Sezzle also provides an invoicing workflow managed in the Merchant Dashboard, positioned as best suited for small- to medium-sized merchants. The invoice flow is designed for in-store or phone purchases and works as follows:

1. Merchant creates an invoice in the dashboard.

2. Merchant sends the invoice via text, email, or QR code.

3. Shopper opens a checkout link, logs in (or signs up), and confirms the purchase.

4. Merchant sees the invoice status change from “unpaid” to “paid” in the dashboard once completed.

Eligibility requires being an approved merchant with a linked bank account set up in CAD or USD. Sezzle also states a maximum invoice value of $2,500 (USD or CAD, depending on merchant currency), and notes that invoicing does not add extra fees beyond the merchant’s normal fees.

Integration Options And Developer Tooling

Platform Integrations

Sezzle’s merchant-facing materials and documentation emphasize “plug-and-play” integrations and list common platforms. If you run on a supported platform, your Sezzle implementation may be largely configuration-based versus a full custom build.

Direct API Integration And Sandbox

API documentation (v1 overview) describes the API as designed for merchants that want to accept Sezzle as a payment option and recommends testing in a sandbox before going live. It also provides:

• A sandbox API endpoint: https://sandbox.gateway.sezzle.com/v1

• A sandbox merchant dashboard: https://sandbox.dashboard.sezzle.com/merchant

This can support a typical dev workflow: build, test in sandbox, validate webhooks and payment states, then deploy to live.

Authorization And Capture Controls

Merchants can choose between:

• Authorize Only (authorization occurs, merchant must capture manually before authorization expires)

• Authorize And Capture (capture happens automatically after successful checkout)

This matters for merchants with fulfillment delays, partial shipments, or workflows where “paid” should only be recognized after capture.

Webhooks For Status And Dispute Events

Sezzle documents webhook security and event handling. Webhooks are secured with an HMAC-SHA256 signature, and the Sezzle-Signature header contains a hash of the webhook body generated using the merchant private key. Webhook event list includes order lifecycle events (authorized, captured, refunded) and dispute-related events (including merchant input requested and dispute outcomes). This makes webhooks a central tool for keeping your OMS, ERP, or ecommerce backend synchronized with payment status.

Express Checkout And Widgets

Sezzle positions two key add-ons as “conversion boosters”:

• Express Checkout, designed to place a Sezzle button into the cart (and optionally product and checkout pages), enabling shoppers to select Sezzle with a single click using their Sezzle account, and notes implementation “should take no longer than 3–5 days.”

• Price Breakdown Widget / promotional messaging widget, which displays available financing options on product and cart pages.

Pricing And Merchant Fees

There are several fee components:

• Order Processing Fee: a set percentage of each order plus a small processing fee.

• Minimum Account Management Fee (if applicable): incurred if the merchant completes less than $300 USD in order volume during the 30-day period before the billing date (billing date aligns with approval date and repeats every 30 days).

• Refund Fees: may apply when refunds are issued through a card on file (versus using a refund reserve account).

• Monthly Inactive Account Fee: applies to merchants with inactive accounts (referenced as a separate FAQ item).

For smaller merchants, Sezzle also describes Sezzle Pro as being for merchants who process less than $1 million annually, with pricing of $149 annually.

Settlement, Payouts, And Cash Flow

Merchant support documentation provides specific operational details:

• Order funds are transferred to the merchant’s Sezzle account when orders are placed.

• The date funds are sent to the merchant’s bank account depends on the application, and Sezzle states the most common settlement period is 3 business days.

• Merchants can track settlement dates and amounts in the dashboard on the “Settlements” tab.

• Orders with the same settlement date are grouped into a single settlement; weekend orders may be combined.

The payout system works in two parts:

• Settlements: reflect orders (not refunds) and when funds become available based on settlement timing.

• Withdrawals: reflect what is actually sent to the bank account and incorporate refunds and other adjustments. Refunds are deducted from the next deposit rather than pulled directly from the merchant’s bank account; this can result in a negative withdrawal balance until new orders offset the refunds.

Security And Compliance

Sezzle states it is PCI DSS Level 1 certified as a compliant service provider organization. It also notes that its PCI DSS responsibilities are outlined in a Level 1 Report on Compliance (ROC) and Attestation of Compliance (AOC) audited by a Qualified Security Assessor, and that its AOC is submitted to its acquiring bank(s). Sezzle indicates the AOC is available upon request through its Trust Center.

Conclusion

Sezzle is positioned as a BNPL payment acceptance option for merchants that want to offer installment plans online and, for qualifying U.S. merchants, in-store via a virtual card added to Apple Pay or Google Pay. Merchants can implement Sezzle through platform integrations or direct API integration, supported by sandbox testing, configurable authorization and capture behavior, and webhook-driven status updates. Operationally, Sezzle provides dashboard-based settlement visibility, a common three-business-day settlement period, and an invoicing workflow for in-store or phone orders. From a compliance standpoint, Sezzle publicly states PCI DSS Level 1 certification and provides a Trust Center pathway for compliance artifacts.