Customer verification tiers and payouts

Every business that pays money out has two goals for verification that seem to pull against each other. Growth wants sign-up and the first sale to be effortless, because a seller or customer who meets a document request on day one often leaves. Compliance and the payment providers want money leaving the platform to go only to people whose identity is known. Businesses that resolve the tension badly end up with the worst of both: friction at sign-up for small accounts, and documents demanded at the first payout for everyone else.

This applies to any business that sends money to the people it serves: marketplaces paying sellers, fintech apps and wallets that hold balances, online stores paying cashback or refunding to a different method, and platforms paying creators or affiliates. Customer verification levels are the way out. This article explains how to design them around money movement, how to connect them to payment routing so verified customers get more options, and how to make sure a payout never becomes the first time anyone checks who is being paid.

Why do payouts end up waiting for verification?

Because checks that could have run earlier were deferred to the last moment money could be stopped. It is tempting: a sale brings revenue, a payout costs it, and asking for documents at the payout looks like free risk control.

Payment providers close that door from their side. Stripe’s Connect documentation says that if a connected account’s required information is not received by the deadline, Stripe typically disables payouts on the account. Adyen says it must verify the users on a platform before payments are processed or their funds paid out. If the platform has not collected the information in time, the provider’s deadline becomes the platform’s problem, and it usually lands at payout time.

Even where no provider forces the issue, a payout held for documents is expensive. It generates support contacts, it is the moment a seller decides whether to trust the platform, and on a marketplace a seller who is not paid on time may simply stop listing.

What should each verification tier check?

The content of customer due diligence is well defined. The UK Money Laundering Regulations, regulation 28, describe it as identifying the customer, verifying that identity on the basis of information from a reliable source independent of the customer, assessing the purpose and intended nature of the relationship, and monitoring the relationship over time. Tiers decide when each part happens and how deep it goes.

A structure that works for many marketplaces, as an example rather than a regulatory standard:

Tier	Checks	What it typically allows
0	Account created; email or phone confirmed	Browse, buy, create listings; no payouts
1	Name, date of birth and address matched against databases; company registration for a business	Sales within a low cumulative limit; earnings held in the balance
2	Identity document and liveness check; payout account verified in the seller’s name; owners of a business identified	Payouts; higher limits; more providers
3	Source of funds or enhanced review	High limits; faster payout schedules; large payouts

Two design rules matter more than the exact checks.

Make tier 1 automatic and fast. Database checks that resolve in seconds at sign-up let a seller start selling without waiting, and they give your providers the basic data they need from day one.

Reach tier 2 before the first payout, not at it. Trigger the document, liveness and payout account checks on cumulative sales or on account age, so most sellers are verified by the time they have money to be paid out.

How should triggers for the next tier work?

Use money that has moved, over time, rather than single transactions. European guidance supports this. The EBA’s guidelines on money laundering risk factors allow firms, in low-risk situations, to adjust the timing of due diligence, for example by verifying identity once transactions exceed a defined threshold or once a reasonable time limit has passed. The same paragraph sets the conditions: the customer’s identity must ultimately be verified, the threshold must be reasonably low, and the firm must have systems that detect when it is reached. For low-risk e-money products, the guidelines give postponing verification until a low threshold as an example, and say the threshold should not exceed EUR 150 where the product is not reloadable or can be used in other countries or cross-border.

Providers work the same way. Stripe lets platforms provide verification information up front or incrementally, and lists some requirements as eventually due, depending on whether the corresponding thresholds are reached.

Practical triggers:

• Cumulative sales, balance or payout volume over a rolling period, for example 30 days.
• The first payout request, if the seller has not yet reached tier 2. This should be rare if the volume trigger is set well.
• Risk signals: a new payout account, a change of country, a payout account in another name, a spike in refunds or chargebacks, or a mismatch flagged by a provider.
• Periodic review for high tiers, because ownership and source of funds information goes stale. Adyen lists periodic data reviews among the events that trigger new checks.

Each trigger should start the check early enough that the seller can complete it before they hit the limit, with a notice in their dashboard rather than a block at the moment they ask to be paid.

How do verification tiers decide payment and payout routes?

This is where verification stops being only a compliance cost. Payment providers have different appetites. Some accept new, unverified accounts with lower limits; others only take verified customers. Payout providers and bank rails usually ask for more, and some deadlines show it: when Adyen triggers new checks, users get a standard 30 days for capabilities that send funds to a bank account, against 60 days for receiving payments.

Name checks are moving into the rails themselves. Since 9 October 2025, payment providers in the euro area have had to offer verification of payee, which tells the sender whether the payee name matches the account before a standard or instant transfer is sent. Checkout.com’s documentation on card payouts asks merchants to provide as much information about the sender and recipient as possible, and says detailed data can reduce the chance of manual review.

If the verification tier travels with every payment request, routing can use it:

• Unverified customers see the methods and providers that accept them, with limits to match.
• Verified customers see more providers, which usually means more chances to be approved and more ways to be paid.
• Payout methods are offered only when the customer’s tier and payment history qualify, so the checkout never offers a route that will be refused.
• Return-to-source rules sit next to verification: refunds go back to the method the customer paid with, and payouts go to accounts in the verified name.

This is the same filtering that PSP eligibility does for country, method and currency, with verification as one more condition.

Worked example: documents first versus tiered verification

Example figures, for illustration only.

A marketplace signs up 10,000 new sellers a month and compares two designs.

	Documents at sign-up	Tiered verification
Sign-ups	10,000	10,000
Sellers who publish a listing	3,000	4,000
Sellers who make a first sale	2,250 (75%)	3,000 (75%)
Sellers at tier 2 before their first payout	2,250	2,700
First payouts held for documents	0	300

The tiered design produces 750 more selling accounts because fewer sellers stop at a document request before they list. It holds 300 first payouts for documents: the sellers whose sales arrived before their volume reached the tier 2 trigger. Lowering the trigger reduces that number at the cost of asking more sellers for documents earlier. The point is not the exact numbers but that the trade-off is visible and tunable, rather than being decided by whichever team owns the sign-up form.

What should a verification and payout checklist include?

• Define tiers by what they allow: limits, providers, payout methods.
• Run the first tier automatically at sign-up, within your providers’ requirements and local rules.
• Trigger the next tier on cumulative activity, early enough to finish before the limit.
• Verify the payout account in the seller’s name before the first payout.
• Send the customer’s verification tier with every payment request so routing can use it.
• Offer payout methods only to customers who qualify for them.
• When a payout is held, tell the seller why and what to do, unless rules forbid it.
• Measure payouts held for documents. A rising number means a trigger is set too late.

How does Omno use verification levels?

In Omno, the merchant sends the customer’s verification levels (KYC levels in the API, customer.kyc.kycLevels), customer groups, a kycVerified flag and the number of previous transactions with each checkout session, pay-in or payout request. Eligibility rules on each provider use them to decide which providers a customer can use for payments and payouts, including a minimum verification level per provider for payouts, and routing chooses among the providers that remain. The risk controls page describes the settings, and the routing and PSP eligibility guide lists the fields.