Merchant underwriting is the decision at the center of onboarding: whether to accept a business, and on what terms. A PSP that accepts a merchant takes on its chargebacks if the merchant can't pay them, so underwriting is really a judgment about future losses made with today's information.
Automated merchant underwriting doesn't replace that judgment. It gathers the evidence, scores it the same way every time and sends only the unclear cases to a person. This page covers what underwriters check, how a score turns into terms, and where the software stops.
What is merchant underwriting?
It's the risk assessment a PSP or acquirer runs before letting a business process card payments, and payment facilitators run the same assessment on every sub-merchant they sign under their sponsor's rules. The outcome isn't only yes or no. Many approvals come with conditions, such as a rolling reserve, a monthly volume cap or a delay before the first payout.
Underwriting also comes back later. A merchant's volumes and chargeback history change, so a good process reassesses existing merchants instead of treating approval as permanent.
The merchant underwriting process: what gets checked
Underwriters look at the same handful of factors, weighted by how much each one predicts loss. The table explains why each matters.
| Factor | What the underwriter looks at | Why it matters |
|---|---|---|
| Business model and category | What the merchant sells and its merchant category code | Some categories see more disputes or more scrutiny from the card schemes |
| Delivery time | How long between payment and delivery | Prepaid goods delivered months later leave refunds exposed for months |
| Volume and ticket size | Expected monthly volume and average payment | Large, sudden volumes are harder to cover if something goes wrong |
| Processing history | Previous statements, refund and chargeback rates | Past behavior is the best single predictor |
| Owners and directors | Identity, background, other businesses | Owners of a failed merchant may try again under a new name |
| Geography | Where the business and its customers are | Cross-border payments carry more fraud and more disputes |
| Website and terms | Clear prices, refund policy, contact details | Missing basics often precede customer complaints |
Delivery time is the factor newcomers miss most. A merchant selling event tickets or annual subscriptions can look healthy for months before refunds arrive all at once.
A worked score for automated merchant underwriting
Here's a simplified, hypothetical scoring model to show how automated underwriting turns those factors into a decision. Each factor adds points, and the total sets the outcome: under 30 is approved on standard terms, 30 to 60 goes to manual review, and over 60 is declined.
| Factor | Points available | Example merchant | Points scored |
|---|---|---|---|
| Category risk | 0 to 30 | Online subscription box | 12 |
| Delivery time | 0 to 20 | Ships monthly, billed quarterly | 10 |
| Processing history | 0 to 25 | Two years of statements, refunds normal | 4 |
| Geography | 0 to 15 | Sells to three EU countries | 6 |
| Ownership clarity | 0 to 10 | One owner, verified | 0 |
| Total | 100 | 32 |
At 32 points the merchant lands just inside manual review. An underwriter might approve it with a reserve covering the gap between quarterly billing and monthly shipping, which is the kind of call a fixed rule handles poorly and a person handles well.
Terms by risk tier
The score sets terms too. Here are the kinds of conditions PSPs attach at each level.
| Tier | Typical outcome | Common conditions |
|---|---|---|
| Low | Approved | Standard pricing, regular payout schedule |
| Medium | Approved with conditions | Rolling reserve, volume limit, review after three months |
| Elevated | Manual review | Extra documents, a higher reserve, delayed first payout |
| Unacceptable | Declined | None |
Conditions should come off as the merchant builds a record. A reserve that never releases tells a good merchant to look for another PSP.
Merchant onboarding vs merchant underwriting
Onboarding is the whole journey from application to go-live, including KYB and account setup. Underwriting is the risk decision inside that journey. A merchant onboarding flow can be fast and well designed and still sign bad merchants if the underwriting step is weak, so the two are worth measuring separately.
What merchant underwriting software should do
Software earns its place by doing the repetitive parts the same way every time. Our merchant management system scores every merchant during onboarding and through the rest of its life on the platform, applying your own rules to approve, review or decline.
It keeps merchants in the right category for pricing and risk, reassesses them as volumes change, and applies rolling reserves and holdbacks at settlement. The rules stay yours to set and change, and every decision stays in the audit trail for your sponsor and your auditors.
Questions
What is automated merchant underwriting?
Software that collects a merchant's data, scores it against your risk rules and either decides or routes it to a person, the same way for every application. People still decide the unclear cases.
What does a merchant underwriter check?
The business model and category, delivery time and expected volumes, then processing history, the people behind the business, geography and the website's terms.
What's the difference between merchant onboarding and merchant underwriting?
Onboarding is the full process from application to going live. Underwriting is the risk decision within it, about whether to accept the merchant and on what terms.
Can an approved merchant be underwritten again?
Yes, and it should be. Reassessing merchants as their volumes and chargeback rates change catches risk that didn't exist at approval.