Use casesMerchant onboarding
USE CASE · PAYMENTS

Merchant onboarding: from application to a decision.

Merchant onboarding is where the risk and growth trade-off is sharpest. Tighten the controls to stop the fraudulent applicants and the legitimate ones leave during the wait. Loosen them and you find out later, from someone else.

Use case

From application to a decision.

The problem

A good business applies, gets asked for a register extract, an ID, a bank statement and a signed form, then waits for someone to read them. The fraudulent one has every document ready, because preparing them is their job. Controls built this way filter for patience, not for legitimacy.

The application

The applicant types a company name. Company data retrieved from more than 200 trade registers replaces the extract upload, normalised, cross-checked and timestamped. Ownership resolves through holding structures until it reaches people, and the people it finds go through identity and screening in the same case. Bank ownership is confirmed over open banking, or through Verification of Payee (VOP) where that gives the smoother path. Directors selected to sign are vetted for signing authority and identified to AML standard; where identification is by eID or QES at qualified level, the same identity signs the agreement itself. Authoritative documents and register data are translated instantly and at high quality from the native register language, so the original evidence stays authoritative rather than becoming a translation task. Straight-through cases complete without manual document handling; exceptions arrive as assembled cases for review.

Why it matters beyond merchant onboarding

The same components, company data retrieval, ownership resolution, bank verification and signing-authority checks, apply wherever a business rather than a person is the applicant. What changes between industries is the risk policy applied to the decision, not the mechanism that gathers the evidence for it.