Summary
Credit insurance for payment companies is a specialist insurance product that covers the chargeback liability acquirers, PSPs, ISOs and PayFacs carry when a merchant fails to deliver goods or services that cardholders have already paid for. This article explains where that liability sits across the payments value chain, how credit insurance covers it, and how the underwriting actually works in practice.
Who carries the credit risk when a merchant fails?
If you run a payment business, your card processing agreements almost certainly make you the financial counterparty to the merchant. When a merchant cannot deliver the goods or services a cardholder paid for, the cardholder raises a chargeback. The issuing bank refunds the cardholder. The card scheme bills the chargeback back to you. If the merchant is solvent, you recover the funds from the merchant’s settlement account. If the merchant is insolvent, you do not.
This is the part most people new to merchant credit risk underestimate. The liability does not stay with the merchant. It flows upstream to whoever holds the licence with the card schemes.
That is a different entity depending on how the merchant is connected to the network.
For acquirers and acquiring banks (Worldpay, JPMorgan Payments, Adyen, Stripe Acquiring), the liability sits squarely on the acquirer’s balance sheet. The acquirer is the scheme-licensed entity. There is no one further upstream to absorb the loss.
For PayFacs and master merchants (Stripe Connect, Square, Adyen for Platforms, Lazada, Airbnb), the PayFac is the merchant of record to the card schemes. Their sub-merchants sit underneath that master ID. When a sub-merchant fails, the PayFac eats the chargebacks. Their sponsoring acquirer can ultimately come back on the PayFac if the PayFac itself fails to absorb the losses.
For ISOs, the liability typically sits with the sponsoring acquirer rather than the ISO itself, but commercial terms vary, and some ISOs have skin in the game through tiered revenue-share or first-loss arrangements.
For PSPs and payment gateways without an acquiring licence, the liability sits with whichever entity holds the scheme licence the PSP routes through. The PSP may still take commercial risk on their merchants, but the chargeback liability legally rests with the licensed acquirer.
The practical implication is the same across all of these structures: whoever is closest to the card scheme licence carries the credit risk on every merchant in the book. That single fact is what credit insurance for payment companies addresses.
How credit insurance changes the equation
Payment companies have historically managed this exposure with rolling reserves and upfront collateral, typically applied to higher-risk or deferred-delivery merchants where the gap between payment and delivery creates outsized risk. A reserve withholds a portion of the merchant’s settlement; collateral takes an upfront cash deposit or bank guarantee. Both work, but they tie up the merchant’s working capital and rarely size correctly against the actual exposure on the book. We cover that structural trade-off in detail in Insurance Instead of Rolling Reserves.
Envisso replaces that mechanic with credit insurance. A Tier 1 insurer absorbs the chargeback liability instead, and the payment company stops holding capital against the merchant. The rest of this section explains how the cover works.
The payment company takes out a policy with a Tier 1 insurer. The cover responds whenever a merchant is unable to meet its obligation to deliver the goods or services cardholders have already paid for. That does not have to mean formal insolvency. The more common trigger is protracted default: the merchant runs a negative balance with the payment company for 30 consecutive days, whether or not they have entered a formal insolvency process. Either path activates the policy. When a covered event occurs, a claim is filed with the insurer and the chargeback liability is paid out. The payment company never holds capital against the exposure.
A workable policy in the payments context names the covered chargeback reason codes (broadly the goods-or-services-not-received family across the major card schemes), aligns its coverage window to the card-scheme chargeback period, and prices on transaction volume so the cover scales with the book. The acquirer typically passes the cost through to the merchant as a small transparent fee.
How insurance works
Putting credit insurance in place for a payment company has four moving parts: partnering with the right insurer, underwriting the merchant book, structuring the policy, and running the live programme of enrollment and claims.
The insurer behind the policy. A credit insurance policy is only as good as the insurer paying out under stress. Envisso writes its programmes through Tier 1, AA-rated insurance partners including Swiss Re, Chubb, and Income Insurance: institutions with the balance sheet and the regulatory standing to honour claims at scale. When a merchant in the book defaults, the insurer carries the loss, not the payment company. The insurer behind the policy matters as much as the platform in front of it.
Underwriting the merchant book. Each merchant is scored against a model that pulls from 30+ data sources, combining transaction-level processing data (volume, growth, dispute trends, refund patterns, MCC, geography), a credit signal on the merchant entity (bureau data, financial statements, beneficial ownership), unstructured web signals (website risk indicators, customer reviews, adverse media), and an estimate of delivery days that converts processing volume into value-at-risk. The model is calibrated against historical payments default outcomes, which is what allows the insurer to price merchant credit risk in payments accurately rather than off generic credit-default curves. Most merchants get a coverage decision the same day; above-threshold cases are reviewed by the insurer’s underwriting team within 48 hours.
Drafting the policy and pricing at portfolio level. Envisso sizes each programme at portfolio level: aggregate exposure across the book, stress-tested against 10,000 macroeconomic scenarios, with limits and pricing calibrated against the insurer’s appetite. The output is a single policy that covers the whole portfolio, with per-merchant limits and premium assigned dynamically based on the risk score rather than negotiated one merchant at a time. This is the difference between an insurance programme and a stack of one-off policies.
Enrollment and claims handling. Once the policy is bound, new merchants flow through the same risk model at onboarding and are enrolled into the cover automatically when they fall inside appetite. When a covered event occurs (court-declared insolvency or 30 days of protracted default), the payment company files a claim through Envisso, the insurer reviews against the policy terms, and the claim is paid. A standard timeline from claim submission to payment runs roughly four to six weeks, depending on the policy. After paying out, the insurer can pursue subrogation against the failed merchant to recover what it can. The payment company runs all of this through one platform: enrollment, monitoring, alerts, and claims, with Envisso operating the interface between the merchant book and the insurer.
About Envisso
Envisso provides embedded credit insurance and AI-powered merchant risk monitoring for acquirers, PSPs, payment facilitators, and acquiring banks. The platform monitors 45,000+ merchants across 35+ countries, protects $18B+ in annual processing volume, and is backed by Tier 1 insurance partners including Swiss Re, Chubb, and Income Insurance. Envisso operates from offices across the UK, Singapore, India, Thailand, Indonesia, the Philippines, and Australia.
Want to talk to us about credit insurance for your portfolio? Get in touch.
