Help Center

Frequently Asked Questions

Everything you need to know about CoverPay, BNPL routing, integrations, security, and billing.

GeneralFor MerchantsStripe AppData & PrivacySecurityBilling

General

CoverPay is an AI-powered BNPL (Buy Now, Pay Later) aggregation and routing platform. We connect merchants with multiple BNPL providers through a single integration, automatically routing each transaction to the provider most likely to approve it. Think of us as "Mesh for BNPL" — one SDK, one API, every provider.
When a customer reaches checkout and selects a BNPL option, CoverPay's smart routing engine scores each available provider in real time based on six factors: availability (is the amount within provider limits?), APR, historical approval rate, merchant cost, business-configured preferences, and past performance. The engine then presents the provider(s) most likely to approve the transaction and offer the best terms.
CoverPay currently supports seven BNPL providers: Klarna, Affirm, Afterpay, PayPal Pay Later, Sezzle, Zip, and Synchrony. All providers are accessible through a single integration. We are continually adding new providers — no code changes are required on your end when a new provider is added.
Smart routing is CoverPay's AI-powered decision engine that automatically selects the optimal BNPL provider for each transaction. Instead of relying on a single provider (and losing customers who get declined), smart routing evaluates all available providers in real time and presents the one most likely to approve the customer at the lowest cost to the merchant. This results in higher approval rates, lower cart abandonment, and reduced BNPL fees.

For Merchants

CoverPay provides drop-in SDKs for Web (vanilla JavaScript), React, and iOS (Swift). Integration takes as little as 5 lines of code. You can also use our REST API for server-to-server integration. Start by signing up at app.coverpayme.com, getting your API keys, and following our Quickstart guide at coverpayme.com/docs/quickstart.

CoverPay offers four pricing tiers:

  • Starter ($99/mo) \u2014 All BNPL providers, 60 req/min, 2 team members, email support. Up to $100K GMV. $0.25/tx.
  • Growth ($199/mo) \u2014 All BNPL providers, 300 req/min, 5 team members, priority support, provider analytics. Up to $500K GMV. $0.20/tx.
  • Scale ($499/mo) \u2014 All BNPL providers + CoverPay native, 1,000 req/min, 15 team members, Slack support, custom routing, dedicated AM. Up to $2M GMV. $0.15/tx.
  • Enterprise (from $999/mo) \u2014 Everything in Scale, unlimited req/min, unlimited team members, white-label option, 99.9% uptime SLA, dedicated engineering support. $2M+ GMV. $0.10/tx.

All tiers include a free sandbox environment. No per-provider contracts required.

Most merchants complete their initial integration within a single day. The basic SDK integration takes under 5 minutes. Configuring BNPL provider credentials, setting up webhooks, and testing in sandbox typically takes a few hours. Our Quickstart wizard in the dashboard walks you through the entire process step by step.
No. CoverPay handles the provider relationships for you. You do not need to apply for, negotiate, or manage individual contracts with Klarna, Affirm, Afterpay, or any other provider. You provide a single set of credentials to CoverPay, and we route transactions on your behalf. However, if you already have existing provider accounts, you can bring your own credentials and we will route through them.
Yes. CoverPay has a Stripe App available on the Stripe Marketplace that integrates directly into your Stripe Dashboard. You can view BNPL routing data, provider analytics, and customer insights without leaving Stripe. CoverPay can also route through Stripe's built-in BNPL methods (Klarna, Affirm, Afterpay, and Zip via PaymentIntents) alongside direct provider APIs.

Stripe App

The Stripe App surfaces CoverPay BNPL data directly in your Stripe Dashboard across eight views: a home overview with transaction analytics, payment list with BNPL session details, individual payment routing info, customer BNPL profiles, product eligibility checks, a configuration drawer, settings for your API key, and an onboarding flow. You can monitor approval rates, provider performance, and routing decisions without leaving Stripe.
The CoverPay Stripe App will be available on the Stripe App Marketplace. Once published, you can install it directly from your Stripe Dashboard under Apps. After installation, open the app, navigate to Settings, and enter your CoverPay API key (found in your CoverPay dashboard at app.coverpayme.com/api-keys). The app will immediately begin displaying your BNPL data.
The CoverPay Stripe App requires the following permissions: payment_method_read (to display payment context), payment_intent_read (to correlate BNPL sessions), customer_read (to show customer profiles), product_read (to check product eligibility), and secret_write (to securely store your CoverPay API key in Stripe's Secret Store). The app does not modify any of your Stripe data.
After installing the Stripe App, go to the Settings view within the app and enter your CoverPay API key. The key is securely stored in Stripe's Secret Store (account-scoped, encrypted at rest). Every API call from the app authenticates using this key. You can rotate or update the key at any time through the app's Settings view.

Data & Privacy

CoverPay collects the minimum data necessary to route BNPL transactions: transaction amounts, merchant identifiers, customer email (for provider matching), device metadata, and routing outcomes. For merchants, we collect business information, API usage metrics, and provider configuration. We do not collect Social Security numbers, bank account details, or full credit card numbers. See our full Privacy Policy at coverpayme.com/legal/privacy.
All data is encrypted in transit using TLS 1.3 and at rest using AES-256 encryption. BNPL provider credentials (API keys and secrets) are encrypted with AES-256 before storage and decrypted only at the moment of use via server-side RPC. We implement multi-factor authentication, regular security audits, and role-based access controls. Our infrastructure runs on Supabase (US-based) with row-level security policies.
All CoverPay data is stored in the United States. Our primary database is hosted on Supabase in the us-east-1 region. Our website and dashboard are hosted on Vercel with US-based edge infrastructure. We do not transfer data outside the United States unless explicitly required by a BNPL provider to process a specific transaction, and only the minimum data necessary is shared.
CoverPay is pursuing PCI DSS Level 1 compliance. Currently, we do not directly handle, process, or store credit card numbers — all card-present transactions are processed through Stripe, which is PCI DSS Level 1 certified. BNPL transactions are handled through each provider's own PCI-compliant infrastructure. CoverPay acts as a routing layer and does not process raw card data.
CoverPay is committed to compliance with both GDPR and CCPA. Under CCPA, California residents have the right to know what data is collected, request deletion, and opt out of data sales — we do not sell personal information. Under GDPR, EU data subjects have similar rights including data portability and the right to erasure. To exercise any data rights, contact privacy@coverpayme.com.

Security

CoverPay API keys are generated server-side with the format cp_{env}_{businessId}_{suffix}_{secret}. Keys are SHA-256 hashed before storage — the full key is returned only once at creation time and is never stored in plaintext. Key rotation is supported with a 24-hour grace period during which both old and new keys remain valid. All API key usage is logged for audit purposes.
All BNPL provider credentials (Klarna API keys, Affirm private keys, Afterpay merchant secrets, etc.) are encrypted at rest using AES-256 encryption before being stored in the database. Decryption occurs only at the moment of use via a server-side RPC function (decrypt_credential) using a dedicated encryption key. Credentials are never logged, cached in plaintext, or exposed through API responses.
CoverPay minimizes the customer PII it handles. We receive only the data necessary for BNPL routing — primarily email addresses and transaction amounts. This data is transmitted to BNPL providers only as required to process the specific transaction. We do not store customer financial data (SSN, bank accounts, credit card numbers). All PII in our database is protected by Supabase row-level security policies and encrypted at rest.

Billing

CoverPay offers a free sandbox environment that lets you test all BNPL providers with simulated transactions before going live. There is no time limit on sandbox access. You only begin paying when you activate a live environment and process real transactions. This allows you to fully evaluate the integration, test routing logic, and demo to stakeholders at no cost.
Yes. CoverPay subscriptions are month-to-month with no long-term contracts. You can cancel at any time from your dashboard billing page or by contacting support@coverpayme.com. Upon cancellation, your account remains active through the end of the current billing period. Any outstanding transaction fees are settled at the end of the billing cycle.
CoverPay billing is processed through Stripe. We accept all major credit and debit cards (Visa, Mastercard, American Express, Discover), as well as ACH bank transfers for Enterprise accounts. Invoices are generated monthly and accessible through the billing section of your dashboard.

Still have questions?

Our team is here to help. Reach out to support or explore our documentation.

Contact SupportExplore Docs