limitedDistribution · Industry Research
Merchant Onboarding and KYB Decisioning Breaks at the Evidence Handoffs
A merchant submits corporate records, ownership details, projected payment volumes, and operating locations. Some fields match external sources; others conflict or remain incomplete. The chief
Merchant Onboarding and KYB Decisioning Breaks at the Evidence Handoffs
A merchant submits corporate records, ownership details, projected payment volumes, and operating locations. Some fields match external sources; others conflict or remain incomplete. The chief risk officer or payments head must decide whether to approve, reject, or escalate—without letting the case disappear into email and spreadsheets. This is where merchant onboarding and KYB decisioning slows down, creates inconsistent outcomes, and increases regulatory exposure. Fixing it requires more than another data check: it requires a governed workflow for reconciling evidence, applying policy, and documenting every decision.
Why merchant onboarding and KYB decisioning fails
Know your business (KYB) is inherently a multi-source process. FATF’s beneficial-ownership guidance calls for adequate, accurate, and current ownership information through a multi-pronged approach combining company-supplied data, registries, public authorities, and other effective mechanisms. FATF reports that countries using multiple approaches performed better in its mutual evaluations than those relying on one source. The guidance concerns national implementation; it does not prescribe merchant-onboarding technology or performance targets.
For payment processors, the control scope extends beyond confirming that a company exists. FFIEC guidance for third-party payment processors identifies merchant identity, principal business activity, location, transaction volume, corporate documents, principal-owner information, public-record and fraud-database checks, and periodic profile updates as relevant due-diligence inputs. This is supervisory guidance for banks overseeing processor relationships, not an onboarding performance study, but it illustrates the evidence that a defensible merchant decision may need to coordinate.
The process fails when those inputs arrive in different formats and systems. Application fields sit in onboarding software; ownership evidence arrives as documents; database results return through APIs; expected volumes must be compared with processor policies. Analysts then rekey information, resolve naming differences, chase missing documents, and interpret rules case by case.
The bottleneck in KYB is rarely one missing check; it is the uncontrolled handoff between evidence, policy, exceptions, and approval.
Fragmented evidence becomes a business and control problem
The operational difficulty is documented beyond payments. In a cross-industry ACFE–Thomson Reuters survey conducted among ACFE members in February and March 2023, 52% of respondents described onboarding a new business customer as moderately or extremely challenging. Banking and financial services and manufacturing were the most represented sectors, so the result is direct KYB evidence but not a merchant-acquirer benchmark.
Friction can also affect acquisition. According to a 2024 vendor-sponsored survey of more than 450 C-level executives at corporate, institutional, and commercial banks, 67% reported losing clients because of slow or inefficient onboarding and KYC. In the same survey, 86% cited poor data management and siloed processes, while only 4% said most KYC workflows were automated. These are executive responses from banks—not independently measured merchant abandonment rates—but they connect fragmented execution with cycle time, service levels, and conversion risk.
Control failures can have a more serious consequence. In 2025, the FCA found that Monzo’s business-customer procedures did not provide for verification of all beneficial owners and people with significant control. The regulator imposed a £21,091,300 penalty covering this and a broader set of financial-crime-control failures. The fine cannot be attributed solely to KYB, but the FCA’s Monzo Final Notice shows why complete ownership evidence, consistent risk assessment, and traceable decisions matter.
A controlled target workflow for merchant onboarding
A stronger operating model uses four connected steps:
-
Capture and structure the evidence. Extract merchant identity, registration, ownership, activity, geography, and expected-volume fields from application forms and corporate documents. Normalize names, addresses, identifiers, and ownership relationships into a defined schema.
-
Validate and reconcile. Match submitted information against approved registries, fraud databases, identity graphs, and internal records. Assign confidence at field level and identify conflicts, stale evidence, missing owners, or unsupported claims.
-
Apply policy and route exceptions. Evaluate the complete evidence set against jurisdiction, product, risk, and approval rules. Send only unresolved or policy-defined exceptions into case management, with the reason, evidence, and required action visible to the reviewer.
-
Deliver and preserve the decision. Write approved data and risk outcomes into the relevant processor, ledger, or onboarding system. Retain source references, rule versions, reviewer actions, timestamps, and approval rationale for monitoring and audit.
StarDox Intelligence provides the enterprise automation and decision-intelligence layer across that flow. It can use governed deep learning to classify and extract relevant document data, then validate and map the results into system-ready records. Rules remain explicit, low-confidence results enter human review, and every exception retains traceability rather than becoming an undocumented side process.
Start with the exception path
The practical first step is not a platform-wide replacement. Select one merchant segment and map its current evidence sources, policy checks, handoffs, exception reasons, approval rights, and systems of record.
Then establish a testable baseline for cycle time, straight-through processing, first-time-right rate, exception rate, and service-level performance. Assess where StarDox Intelligence could remove rekeying, reconcile conflicting evidence earlier, and give reviewers a complete decision package. The objective is a measurable control improvement: fewer avoidable touches, faster resolution of genuine exceptions, and an approval record that explains what was decided and why.
Sources
See ROI in 12 weeks
Stargo users see measurable return and operational profitability gains in just 12 weeks, with non-disruptive implementation in 4 weeks or less.