Merchant onboarding process: steps, checks & best practices

No relationship with a merchant starts at the first transaction. It starts with onboarding, and whatever happens there sets the terms for everything that follows.

A merchant who feels vetted with care tends to stick around. A merchant who feels stalled, second-guessed, or handled like a line item tends to leave the moment a competitor offers less friction, even if that competitor is checking less carefully.

I've seen both outcomes play out enough times to know which one costs more. Here's the merchant onboarding process that actually works, the checks that matter, and the mistakes that cost PSPs the relationship before it even started.

What is merchant onboarding

Merchant onboarding is how a payment service provider (PSP), payment facilitator, or acquiring bank registers, verifies, and activates a new merchant so it can accept and process payments. It's a specific slice of business onboarding: narrower than general company registration, and far more scrutinized, because the outcome is a business moving real money through your platform.

Account creation is the easy part. The due diligence behind it decides whether a business is legitimate, compliant, and safe to transact with before a single card gets charged. Card networks such as Visa and Mastercard don't onboard merchants directly, but their rules shape every check you run, from Know Your Business (KYB) documentation you request to the monitoring you keep in place after go-live. Issuing banks sit outside this process entirely; they only step in once transactions start flowing.

Who takes part in merchant onboarding

Onboarding never rests on one team. Four parties carry it:

• The merchant. They submit the application, including business registration, ownership details, and financial documentation, and carry the burden of proving they're legitimate and financially sound.
• The PSP. It owns the workflow: collecting and verifying merchant information, setting up accounts, and making sure the merchant meets card scheme rules, security standards, and local regulations before going live.
• Compliance and risk teams. Whether in-house or outsourced, they run Know Your Customer (KYC), KYB, and anti-money laundering (AML) checks to flag risk before it becomes a liability.
• Acquiring banks and card networks. The acquirer underwrites the merchant account and assumes financial risk on the merchant's behalf. Visa and Mastercard never interact with merchants directly, but their rulebooks dictate what gets checked.

What information PSPs collect during merchant onboarding

You need enough information to answer one question with confidence: is this business what it claims to be, and can it survive scrutiny later? That means collecting:

• Business details: legal name, registered address, registration number, country of incorporation, industry category, website.
• Ownership and management: names, roles, and backgrounds of owners and directors, including ultimate beneficial owners (UBOs).
• Personal identification: government-issued IDs for principals, often with address verification, to run merchant KYC checks on the people behind the business, not just the entity itself.
• Compliance and licensing: tax IDs, regulatory licenses, or permits for restricted industries.
• Financial information: settlement bank details, financial statements, and transaction or chargeback history where it exists.
• Business model detail: what the merchant sells, how, and where, which is what actually surfaces money laundering or fraud risk.

Merchant onboarding process step by step

Most PSPs run a version of this sequence. Here's how each step plays out in practice.

• Filter out red flags. Before deep checks start, run a light-touch pass: does the business exist, does the website match what they claim to sell, is the model legal in the markets they're targeting? This is also when you set expectations on documentation, so merchants aren't blindsided later.
• Verify identity and documents. This is where the real work happens: gathering business details, owner identities, compliance documents, and financial statements, then running KYC/KYB checks against them. Automated tools scan IDs, cross-check business registrations, and flag inconsistencies faster than manual review ever could. The question being answered here is simple: do you really know who this merchant is, and are they who they claim to be?
• Assess risk. Your risk team evaluates financial stability, industry profile, and business model, then assigns a risk tier, reserve requirement, or volume limit. An online clothing store gets fast-tracked. An iGaming platform goes through deeper due diligence, because the exposure is structurally different.
• Activate and test. Once approved, create the merchant account⁠, sign the service agreement, and start integration: a copy-pasted checkout snippet for a small store, a full system integration for a larger one. Before anything goes live, run test transactions to confirm the flow works end to end.
• Train and go live. Merchants need guidance before real transactions start: navigating the dashboard, managing refunds, reading reports, handling disputes. Staying hands-on through the first few transactions is the fastest way to build confidence and catch friction before it becomes a support ticket.
• Monitor continuously. Onboarding doesn't end at the first cleared payment. Watch for unusual transaction patterns, rising chargebacks, and regulatory changes, and re-verify documents on a schedule rather than waiting for something to break. This is what protects both sides once the relationship is live.

Merchant onboarding checklist

Every onboarding process eventually condenses to the same list, regardless of provider or region. Business and identity documentation confirms the merchant is who they claim to be. Compliance and risk checks confirm they're safe to work with at the volume they're requesting. Technical and operational setup confirms the account will actually function once approved, and stays monitored after it does.

Where onboarding actually breaks down

These are the failure points that come up most often:

• Misaligned expectations. Merchants expect the ‘instant onboarding’ fintech competitors promise. When your process involves more thorough checks, that gap feels like friction, unless you explain upfront why the extra step exists and what it protects them from.
• Integration complexity. For merchants running custom systems, onboarding is as much an engineering project as a compliance one. When technical and compliance timelines don't move together, the whole onboarding stalls, not just one side of it.
• Cross-border blind spots. A merchant expanding into three new markets means three new tax regimes, licensing regimes, and banking standards to check simultaneously. Missing one local requirement is the most common way cross-border onboarding goes wrong.
• MID availability and stability. Onboarding often stalls because the merchant does not yet have the required merchant accounts, or an existing MID is suspended or withdrawn during the process. Checking provider availability, market coverage, and onboarding requirements early through resources like PayAtlas⁠ can help teams identify suitable alternatives before the issue delays launch.
• Hidden high-risk behavior. A merchant can look low-risk on paper, with clean registration and a clear business model, and still carry weak refund policies or thin fraud controls that only surface after volume ramps up. Paper checks alone won't catch this; it takes qualitative review.

Merchant onboarding best practices

Here are a few practices to help you make the journey smooth and stress-free for your merchants.

Make it digital and guided

Endless email back-and-forth is what makes merchants abandon onboarding. Digital merchant onboarding fixes most of that: a portal with guided forms, secure document upload, and visible progress. Some PSPs go further and give merchants a test dashboard on day one, so they stay engaged while compliance checks run in the background.

Layer the verification

No single check catches everything. Cross-check business registrations against official databases, validate identity documents with AI-driven tools, and screen owners against AML and sanctions lists, running these checks in parallel rather than in sequence so thoroughness doesn't cost speed.

Automate the repetitive parts

Manual merchant onboarding can stretch on for weeks depending on the complexity of the business being reviewed. Automated KYC/KYB screening and risk scoring compress standard-profile onboarding down to a fraction of that time, and switching from manual to automated workflows meaningfully cuts the cost of processing each application. This shift toward payment processing with automated onboarding changes how many merchants one compliance team can actually handle.

Back it with real support

Good docs make all the difference. Clear guides, short video tutorials, and a solid knowledge base help merchants know exactly what to do. Pair that with quick, friendly support – whether it's chat, email, or a dedicated manager – and you remove confusion, speed up go-live, and keep merchants confident throughout the onboarding process.

Merchant onboarding with Corefy

For PSPs using Corefy’s white-label infrastructure⁠, onboarding is smooth and structured. Purpose-built tools and personal support help you move through each stage with confidence. Although most capabilities are designed for internal teams, they make merchant onboarding easier to manage and scale.

• 24/7 knowledge base: access detailed manuals and tutorials to help your team confidently navigate the platform and support merchant onboarding. For extra clarity, we also provide a checklist of key questions – ideal for teams unsure what to ask merchants.
• Personal education sessions: our Onboarding Team delivers live configuration sessions tailored to your setup – ideal for double-checking before onboarding merchants. Recordings are shared for reference or team training.
• Postman integration support: use our preconfigured queries to verify core payment flows. Need something more specific? We’ll prepare a custom Postman collection so your developers can test only the flows you care about – cards, APMs, payouts, tokenization, and more – saving merchant integration time and reducing errors.
• Swagger API documentation and testing: use Swagger to explore available methods, review request and response structures, and test endpoints before implementation. This helps developers understand the integration logic, validate key flows, and resolve issues faster during merchant onboarding.
• Hands-on merchant launch support: we can set up a temporary chat with your first merchants during the integration period and provide a personal Postman collection. This makes launches much faster and ensures questions are resolved instantly, without requiring deep platform knowledge or sending every issue to support.
• Platform news: we proactively share updates and new features so you’re always ready to offer the latest capabilities to your merchants.

Final thoughts

Onboarding is the first real signal a merchant gets about what working with you will be like. Rush it, and you save a few days now at the cost of a merchant who never fully trusts the relationship. Slow it down without explaining why, and you lose them to a competitor promising less friction, even if that competitor checks less carefully. The PSPs that get this right treat every step, from the first document request to the first month of monitoring, as part of the same conversation with the merchant, not a gate they pass through before it begins.