Merchant onboarding: what payment providers ask for and why applications stall

Choosing a payment provider is the easy half. The harder half is being accepted by it. A provider takes on risk when it lets you into the card networks, so it wants to know who you are, who owns you, what you sell and how much trouble your sales are likely to cause. Merchants who treat this as a form to fill in can lose time to a mismatched name or an unfinished website.

This article covers what providers ask for, what they check on your website, why they want your processing history, why applications stall or get rejected, and how long each type of provider takes. It also explains a point that surprises many teams: each provider onboards you separately, and an orchestration layer does not change that.

Does each payment provider onboard you separately?

Yes. Visa’s rules say an acquirer must have a merchant agreement with each of its merchants, and that an acquirer or payment facilitator must make sure a prospective merchant is financially responsible, operating in an allowed jurisdiction and not misrepresenting its location. Before contracting, it must carry out an adequate due diligence review, including a site visit to the business premises where applicable, or a suitable alternative.

Those duties sit with whoever signs you. So an approval from one provider tells the next provider very little, and each one repeats the work. Global Payments for Platforms goes further and asks for its document list for each tax ID tied to the business, so a group with several legal entities should expect several packs. Our guide to multi-brand payment setups covers that structure.

A method can also need its own review inside a provider you already use. Stripe’s support page for Konbini says an external partner review takes around 30 days for Japan-based accounts, and the account cannot accept Konbini during it.

An orchestration layer sits above all of this. It gives you one integration to the providers that have approved you. It does not hold their licences, take their risk or make their decisions. Our article on adding a second PSP treats underwriting as its own step for this reason.

What documents does a payment provider ask for?

Lists differ by provider, country and business type, and Localpayment’s documentation says so directly. The groups below recur across the provider pages we read.

Group	What is usually requested	Example source
Legal existence	Incorporation certificate, business registration, articles of association, business licence	Localpayment
Ownership and control	Government IDs for directors and significant owners, proof of address, a declaration of ultimate beneficial owners	Localpayment
Bank account	A bank letter, voided cheque or recent statement in the business’s name	Worldpay for Platforms
Financials	Tax registration, income statements and balance sheets from the last two years	Localpayment, Global Payments
Processing history	Merchant processing statements from the last three months	Global Payments
Operations	Business description, website, estimated volumes, delivery times, refund and chargeback policies, supplier details	Localpayment, Worldpay for Platforms

Beneficial owners are where group structures slow down. Adyen says a beneficial owner is typically a person who owns 25% or more of the company, and that this can also mean someone with significant power, such as control of 25% or more of the voting rights. Worldpay for Platforms says it screens owners against government sanctions lists and payment-industry watchlists, so every person in the chain has to be identified.

This area is changing in Europe. Baker McKenzie notes that the EU Anti-Money Laundering Regulation sets a harmonised framework from 10 July 2027, under which a stake of 25% or more triggers beneficial owner status, and that the threshold may drop to 15% in high-risk sectors. Check with each provider what it asks for now.

Providers do not all run the same kind of checks. Worldpay for Platforms’ Australian guide describes both automated tools and manual review, and lists possible outcomes: approved, approved with conditions, or declined. Conditions are worth reading carefully. A rolling reserve or a volume limit can arrive with the approval, and our guide to reading a PSP contract covers what to look for.

What do providers check on your website?

Your website is evidence. Worldpay for Platforms says it uses the site to understand your business model, services and customer offerings, and that this supports its risk assessment and anti-money-laundering work. It is also how a provider decides your merchant category code.

Visa’s rules set a minimum for e-commerce merchants. The site or app must show a customer service contact, an address for cardholder correspondence, a policy for delivery of multiple shipments, and the country of the merchant outlet, displayed within the checkout flow itself. A link to a separate page does not meet that last requirement.

Providers add their own expectations. Stripe’s activation guidance asks for:

• A business name and descriptions of goods or services that match what you told Stripe.
• Customer service contact details, and a refund and dispute policy.
• A return policy if you sell physical goods.
• Cancellation terms, legal or export restrictions and promotion terms, where they apply.

Stripe also says the site must be reachable without a password, that any regional blocking should be removed until verification is complete, and that an account may not be activated until the site carries the necessary information. Mollie’s documentation asks that the site is online and clearly shows prices and descriptions of what you sell.

The practical rule is simple. If your site is behind a holding page on the day you apply, you are not ready to apply.

Why do providers ask for processing history?

Because your record shows a provider how much risk it would take on. Global Payments for Platforms lists merchant processing statements from the last three months alongside bank statements. Localpayment asks for processing history from existing businesses. Worldpay for Platforms’ Australian guide describes background screening for prior fraud, excessive chargebacks or unresolved legal issues.

Statements let a provider compare what you say with what happened. Worldpay for Platforms asks for average transaction size, highest transaction amount and total monthly transactions, and says realistic estimates help avoid delays. It also uses them to set fees and fraud monitoring, so an estimate far from reality can cause a problem after go-live as well as before it.

Two scheme-level lists matter most. Stripe’s documentation explains that acquirers must screen applicants against Mastercard’s MATCH and Visa’s VMSS, that listings stay active for 5 years, and that most processors automatically reject listed businesses or principal owners. A listing follows the owners as well as the company, which is why a new legal entity is not a way around it. Stripe also says closing a processing account does not prevent a listing.

Why do applications stall or get rejected?

Stalls tend to come from the file. Rejections tend to come from the business itself.

Problem	What providers say	How to avoid it
Legal name mismatch	Adyen says the legal name must match the registration document exactly, and a trading name in that field delays onboarding	Copy the name from the registration document, character for character
Expired or altered documents	Adyen says it cannot process expired, hole-punched or otherwise modified documents, and wants bank documents dated less than 12 months ago	Check dates before you upload
Bank account in another name	Worldpay for Platforms says the account name must match the legal business name, or it may ask for more documents	Use an account in the legal entity’s name
Unfinished or blocked website	Stripe may not activate an account until the site carries the necessary information	Publish products, policies and contacts first
Restricted business type	Stripe says businesses on its restricted list commonly see longer delays	Read the list before applying and raise it early
Terminated merchant listing	Most processors automatically reject listed businesses or principal owners, according to Stripe	Find out early, and contact the listing acquirer if it is an error

Adyen is plain about the effect: incomplete or incorrect information can delay onboarding. A vague description has the same result. Worldpay for Platforms wants to know whether your goods or services comply with legal and regulatory guidelines, and it cannot judge that from a sentence such as “online retail”.

How long does onboarding take by provider type?

Few providers publish a number, and those that do are stating what is typical, not promising it. These are the published statements we found.

Provider type	Example	Published timing
Automated, card-led provider	Stripe	Nearly instantaneous in most cases, longer for restricted businesses
Regional provider with a review stage	Mollie	Review may take up to 10 business days
Processor with manual underwriting	Global Payments for Platforms	A few days up to a few weeks for a standard review
Local provider with a compliance process	Localpayment	No timing published; six stages from commercial negotiation to go-live
Method that needs a partner’s review	Konbini on Stripe in Japan	Around 30 days

Fast approval and low scrutiny are not the same thing. Stripe says it may reach out for more information, and that it regularly checks your website afterwards. Adyen’s onboarding FAQ says that if your information is not received or verified in time, processing and payouts must stop.

Your provider type can also change as you grow. Visa’s rules say an acquirer working with a payment facilitator must enter a direct merchant agreement with a sponsored merchant above USD 1 million in annual transaction volume, with some exceptions, including where the facilitator has held the relationship for at least 2 years with the same acquirer, reports to it and stays under its oversight. Ask a facilitator what happens when you cross that line.

Commercial and technical steps add to the time. Localpayment places negotiation before compliance review, and agreement signature and integration after it. Our guides to choosing PSPs for Latin America and how many PSPs you need per market can help you decide how many of these processes to start.

How do you prepare for several provider applications?

Work through this once, then reuse the pack for each provider.

1. Fix the facts. Agree one legal name, trading name, registered address, business description and set of owners. Use them everywhere.
2. Map ownership. Draw the chain up to the people at the top, and collect IDs for anyone at or near 25%.
3. Check document dates. Replace anything expired or more than 12 months old.
4. Finish the website. Publish products, prices, delivery terms, refund policy, contact details and the checkout country information.
5. Open the right bank account. It should be in the legal entity’s name, in the settlement currency you want.
6. Gather history. Collect three months of bank and processing statements, plus your chargeback figures.
7. Write realistic volumes. Give average order value, largest order and monthly count per market.
8. Ask each provider four questions. What do you need for my country and category? Who reviews it? What is your usual time from a complete file? Which conditions might you attach?
9. Start with the slowest. Local acquirers and methods with partner reviews can set your launch date, so apply to them first.
10. Track it. Keep one owner and one status sheet per provider. Stalled applications are often waiting on a reply nobody saw.

How does Omno fit into merchant onboarding?

Omno is not a bank, an acquirer or a merchant of record, and it does not run KYC. Connecting to Omno does not onboard you with any provider: each provider reviews and approves you separately, under its own agreement. Once a provider has approved you, your team runs it from the Omno dashboard alongside your other providers, with routing rules and PSP eligibility rules deciding which payments it receives. The payment orchestration page explains how that works.