Every marketplace reaches the same uncomfortable moment. The growth team wants sellers onboarded in minutes. Then somebody points out that money cannot be sent to an unidentified person. Both are right, and the way you resolve it shapes both
your risk and your growth rate.
The resolution is not choosing one side. It is deciding how much checking happens
at which stage.
Why the platform does this at all
When sellers receive money through your platform, you are the one who vouched for
them. Card schemes expect the platform to know who trades on it. An acquirer reviewing your account will ask what you collect and how you verify it. A platform that
cannot answer gets priced as if every seller were unknown, which is expensive.
There is a practical reason too. The cost of a fraudulent seller is not the transaction they took. It is the refunds you cover, the disputes that hit your ratio and the time spent unwinding it. Checking beforehand is the cheapest part of that
chain.
What to collect, and when
The useful principle is staged verification: ask little at signup, more before
payout, most before large volumes.
At signup. Identity of the person or company, contact details, and
a description of what they intend to sell. Light enough not to lose anyone, enough to
turn away the obviously unsuitable.
Before the first payout. Bank details in the same name as the
account, plus proof of identity or registration. This is the real checkpoint, and
sellers accept it because money is now at stake for them too.
At higher volumes. Ownership structure for companies, source of
goods where relevant, and whatever the category demands. Most sellers never reach this
stage, which is exactly why it should not sit at the start.
How this interacts with the account setup on our side is described on the
merchant accounts page.
Keeping onboarding fast anyway
Three things preserve conversion. Ask through your own interface rather than
redirecting people to a form they will not recognise. Let sellers list items while
verification is pending, holding only the payout. And tell them exactly what is missing in plain language. «Documents required» sends people to support, while «upload the registration certificate» gets a file.
How the technical side of onboarding and payouts fits together is set out under
processing.
The sequence from application to first
payout is on how it works.
What to watch after approval
Verification at signup tells you who someone was on that day. Monitoring tells you
who they are now, and the second matters more.
Watch for a seller whose catalogue drifts into categories you never approved. Watch too for volume that jumps by an order of magnitude. A dispute rate rising against a flat baseline counts as well. Each is a reason to look, not necessarily to act. Platforms that look early rarely have to act dramatically.
Keep bank details locked to the verified name as well. The most common marketplace fraud is not a fake seller at signup. It is a legitimate account whose payout destination quietly changes later.
What to do when a check fails
Verification failures are not all the same. Treating them identically is what turns a process into a complaints queue.
A mismatch between the bank account name and the registered name is usually an honest mistake. A one-line message fixes it. A document that cannot be read is a scanning
problem, not a risk signal. A seller who provides nothing after two requests is a different case entirely. The right move there is to close the account cleanly rather than leave it half-open.
Separating these three in your own process saves support time. More importantly, it keeps genuine sellers from feeling accused. Which payment methods a seller can receive money through is worth stating at the same moment. Availability differs by country, and sellers plan around it.
What good looks like
A workable setup verifies most sellers automatically. A minority goes to manual review, and that queue clears within a day. Sellers notice the speed rather than the
checking, which is the point.
Where seller funds wait between collection and payout matters too. A dedicated business IBAN keeps them separable from platform revenue. That makes audits and incident handling simpler.
Rates for middle-risk platforms start from 1.8% on the
pricing page, and connection takes from 5 days.
If you are building this for the first time, write the policy before writing the
code. The questions are commercial rather than technical. Which categories you allow, what you require at which stage, when you say no. A written answer makes the implementation obvious and survives the next owner.
If your platform operates across borders, requirements differ by country. So a single checklist rarely fits everyone. Building the process around what
changes — jurisdiction, entity type, volume — keeps it workable as you expand.
Connection from 5 days. Fees from 1.8% — transparent terms, no hidden charges.
Leave a request or book a consultation. We will put together the right setup for your niche and risk profile.