Merchant Onboarding: Compliance Steps From Application to Go-Live

Merchant onboarding from application to go-live: KYB, underwriting, website review, MATCH, VAMP, transaction laundering, and monitoring after boarding.
Alexandre Berkovic

TL;DR: Merchant onboarding is the sequence a PSP, acquirer, or payment facilitator runs to decide whether a business may accept cards, on what terms, and under what monitoring. The decision has a long tail: since April 1, 2026, Visa identifies a merchant in the US, Canada, the EU, or Asia-Pacific as Excessive at a VAMP ratio of 1.5% with at least 1,500 fraud and dispute events a month. A good file records what the merchant said it would do, so later activity has something to be measured against.

What Merchant Onboarding Has to Decide

Merchant onboarding answers four questions: whether the business is real, who stands behind it, what it will actually sell, and how much loss the acquirer takes on by processing for it. KYB answers the first two. Merchant underwriting answers the last two, because an acquirer carries chargeback exposure on sales that may not have been delivered yet.

The OCC's Merchant Processing handbook sets the supervisory baseline for banks in this business. Its minimum underwriting standards include a signed application and agreement, enough understanding of the business to classify it under the right merchant category code, an on-site inspection or verification of the business, credit reports on the principal, recent processing statements where available, and evidence that the merchant is absent from the SDN List and MATCH.

Card network rules sit on top of that. Visa's Acceptance Risk Standards, in the October 2024 edition, require acquirers to define which merchant segments are permissible, conditionally restricted, and prohibited. Readers comparing vendors will find that angle in KYB solutions for payment processors. This guide follows the case itself, from the first form to the first month of live volume.

The Steps From Application to Go-Live

Most programs run these steps in roughly this order. The OCC notes that many acquirers now underwrite on a risk basis, with limited review for lower-risk merchants and far greater analysis for higher-risk ones.

  1. Take the application: legal name, trading name, owners, URLs, goods sold, expected volume, and average ticket.
  2. Verify the entity against registries and confirm address and contact details.
  3. Identify and verify owners and control persons.
  4. Check terminated merchant files, sanctions lists, and adverse media.
  5. Underwrite credit and chargeback exposure.
  6. Review the website, goods, delivery, and refund terms, then assign the merchant category code.
  7. Register the merchant with the network if its category requires it.
  8. Decide: approve, decline, or approve with conditions.
  9. Board the merchant, set the monitoring baseline, and watch early volume closely.

KYB and UBO: The Identity Layer

The first job is confirming the applicant is a legal entity that exists, is active, and is the party signing the agreement. Visa's standards describe verification of name, address, email, phone number, business registration, and documents. A full KYB program covers the registry mechanics. The merchant-specific point is narrower: every fact collected here becomes a matching key for the terminated merchant search, and a file with a wrong legal name or a missing owner will search clean.

Under 31 CFR 1010.230, a covered financial institution identifies each individual who owns 25 percent or more of a legal entity customer's equity, plus one individual with significant responsibility to control, manage, or direct it. A processor that is not itself a covered institution usually meets this through its sponsor bank's program. The networks want principals named for a separate reason: a person terminated under one company should not return under another. UBO identification is where an incomplete answer creates the most downstream risk.

MATCH, VMSS, and the Terminated Merchant Check

Before signing, an acquirer checks whether the merchant or its principals were previously terminated for cause. Mastercard's system is MATCH, now branded MATCH Pro. Visa's standards refer to the Terminated Merchant File, including the Visa Merchant Screening Service.

Mastercard's Security Rules and Procedures cover merchant screening and MATCH in Chapters 7 and 11. Mastercard revises the manual regularly, so acquirers and payment facilitators should work from the current edition for the screening duty, record retention, listing deadlines and reason codes that bind them.

A hit starts an inquiry. Visa's standards ask the acquirer to confirm the listed merchant is the same party, speak to the acquirer that listed it, and decide after reviewing credit reports and local registries. The OCC calls MATCH the starting point and says the acceptance decision should rest on the bank's own investigation. It also warns that merchants are sometimes listed for technical contract violations, so the reason for a listing matters as much as the listing.

Underwriting and Website Review

Merchant underwriting estimates what the acquirer stands to lose if the merchant fails, disappears, or generates more disputes than it can absorb. Prior processing statements show real volume, ticket size, and chargeback history. Those statements can be altered, so reviewers should know how to spot a fake merchant statement. The outcome need not be binary: Visa names reserves, holds, limits on business activity, and guarantees as conditions on an approval.

The website review tests whether the business on the application is the business actually operating. Visa directs acquirers to review URLs, goods or services, delivery methods, and return policies, and to detect templated or counterfeit sites that lack real traffic or fulfillment. Useful questions:

  • Does the site sell what the application says, and only that?
  • Does the merchant category code match the goods, including any second line of business?
  • Can a customer complete a purchase, find refund terms, and reach the merchant?
  • Do any links send cardholders to a store or checkout on another domain?

Category assignment carries weight of its own. Visa requires the code that most accurately describes the business, and two or more where, for example, an e-commerce outlet links to a separate site qualifying for a different code. Miscoding is how a restricted category ends up looking like a low-risk one.

Prohibited and High-Risk Categories

Prohibited activity is what the law or the acquirer's risk appetite excludes outright. The OCC expects an underwriting policy to designate the merchant types a bank will serve. Visa's standards call for merchant agreements that prohibit knowingly submitting fraudulent or unauthorized transactions, resubmitting previously disputed charges, and transaction laundering.

High-risk categories are legal but require registration and added controls. Visa's Integrity Risk Program sorts High Integrity Risk merchants into three tiers, with card-absent adult content, dating and escort services, gambling, and pharmacies in the top tier. Acquirers need high integrity risk registration, and merchants must be registered before submitting transactions. Mastercard's Chapter 9 Specialty Merchant Registration Program has sections on non-face-to-face adult content and gambling, pharmaceutical and tobacco products, government-owned lotteries, skill games, high-risk cyberlockers, high-risk securities, cryptocurrency, and negative option billing for physical products. Both networks revise these lists by region, so teams should work from the current rules in their acquiring agreement.

VAMP: The Ratio the File Will Be Judged Against

The Visa Acquirer Monitoring Program turns merchant quality into a monthly number. Visa's VAMP fact sheet defines the ratio as the count of TC40 fraud reports plus TC15 disputes, divided by settled transactions, on card-not-present activity. Disputes resolved through pre-dispute solutions and fraud qualified for Compelling Evidence 3.0 are excluded.

LevelVAMP ratioMonthly minimum
Acquirer, Above Standard50 bps or more1,500 fraud and disputes (150 and USD 75,000 in CEMEA)
Acquirer, Excessive70 bps or moreSame as Above Standard
Merchant, Excessive, AP, Canada, EU, US150 bps or more since April 1, 20261,500 fraud and disputes
Merchant, Excessive, LAC150 bps or more1,500 fraud and disputes
Merchant, Excessive, CEMEA220 bps or more150 fraud and disputes and USD 75,000

The fact sheet applies the merchant thresholds when the acquirer is neither Above Standard nor Excessive. Because the acquirer lines sit far lower, a portfolio can reach 0.5% while no single merchant has crossed 1.5%. Onboarding decisions aggregate, and the underwriting file is where each merchant's exposure was accepted.

Transaction Laundering Starts After Approval

Visa's standards describe transaction laundering, also known as factoring, as an unknown business using an approved merchant's payment credentials to process sales for undisclosed goods or services. The approved storefront can be genuine, so an application review alone will not find it.

Visa's recommended controls point to the evidence that can. Transaction data can show amounts or volumes that do not fit the underwritten merchant. Website checks can show a site with no working checkout, or one selling something undeclared. Mismatches across merchant names, category codes, URLs, and backlinks can show a connection the application never mentioned. Mastercard's manual also sets out a Business Risk Assessment and Mitigation program in section 8.8 and a Merchant Monitoring Program in section 8.9.

Merchant Risk Monitoring After Boarding

Merchant risk monitoring compares live behavior against the file. Visa requires acquirers to detect changes in transaction velocity, new or inactive merchant activity, sudden contact-detail changes, authorization spikes, sales volume, card-present mix, and cross-border activity. The mechanism it describes is a regularly updated baseline of normal daily activity, compared against the most recent activity.

Ongoing AML due diligence continues after boarding, including sanctions, PEP, and derogatory media screening, and VMSS alerts on active merchants are compared with the original approval. The file should also reopen on events a transaction system will not catch: a new owner, a new URL, a new product line, or changed settlement instructions.

Where Sphinx Fits

Sphinx is an investigation layer inside the tools a team already uses. Its AI agents prepare the evidence for onboarding and monitoring reviews, apply the team's SOPs, and produce a traceable recommendation, and the team keeps final approval. Sphinx does not score transactions, block payments in real time, verify a person's face, or connect to bank accounts. Sphinx reports 87% fewer false positives on average and 94-98% agreement with analysts.

Frequently Asked Questions

What is the difference between KYB and merchant underwriting?

KYB establishes that the entity exists and who owns and controls it. Merchant underwriting decides whether the acquirer should take on that merchant's chargeback, fraud, and credit exposure, and on what conditions, using processing history, financial information, and a review of what the business sells.

Can an acquirer approve a merchant listed on MATCH?

A listing does not automatically bar approval. Visa's standards for its Terminated Merchant File ask the acquirer to confirm the match, contact the listing acquirer, and make an informed decision, and the OCC says the decision should rest on the bank's own investigation.

What VAMP ratio puts a merchant in the program?

In the US, Canada, the EU, and Asia-Pacific, Visa's Excessive Merchant threshold has been 150 basis points since April 1, 2026, with at least 1,500 fraud and dispute events in the month. Latin America and the Caribbean is also 150 basis points. CEMEA is 220 basis points with at least 150 events and USD 75,000.

How do you detect transaction laundering?

Compare what the merchant was approved to sell against what clears. Visa's recommended controls include reviewing transaction data for patterns that do not fit the underwritten merchant, verifying that websites sell only declared goods and can take payment, and investigating mismatches in merchant names, category codes, and linked URLs.