# KYC Onboarding: From Signup to Accepting Payments

> What KYC onboarding involves when you sign up to sell online: the stages, the documents, why applications stall, and how it differs for freelancers and companies.
- **Author**: Deepak Jangir
- **Published**: 2026-09-17
- **Category**: Payments, SaaS
- **URL**: https://dodopayments.com/blogs/en/kyc-onboarding

---

You built the product, wired up the checkout, and pushed the landing page live. Then the dashboard tells you the account is "pending verification" and you cannot take a single payment until someone at the provider decides you are real. A day passes. An email arrives asking for a selfie, a bank statement, and an explanation of what you actually sell.

That is KYC onboarding, and it sits between every new seller and their first successful transaction.

KYC onboarding is the identity and eligibility process a payment provider runs before it lets you accept money and before it agrees to send money to you. It combines a regulatory obligation to know who its customers are with a commercial need to understand what it is about to process. For a founder or indie developer, it is the single most common reason a launch date slips.

## What KYC Onboarding Actually Covers

KYC stands for know your customer. In a banking context it means verifying an individual account holder. In a payments context, when you sign up to sell online, it expands into a bundle of checks that run in parallel.

Five things get resolved before an account goes live. Every document request you receive maps to one of them.

| What is checked | What it proves | What you typically supply |
| --- | --- | --- |
| Personal identity | You are a real, named person | Government photo ID plus a liveness selfie |
| Business registration | The selling entity legally exists | Registry extract, incorporation certificate |
| Beneficial ownership | Who ultimately controls the money | Cap table, register of members, IDs for owners |
| Bank account | Funds go to an account you control | Bank statement, void cheque, account letter |
| Website and product | What you sell matches what you said | A live, complete, publicly reachable site |

Two of these are regulatory and cannot be waived. Identity and ownership checks exist because anti-money-laundering rules oblige regulated financial institutions to identify the people behind the businesses they serve. Requirements vary by country and by provider, so treat the shape below as typical rather than universal.

The other three are a mix of regulation and commercial judgement. A bank account check is partly fraud prevention and partly a practical need to know where to send your money. A website review is almost entirely commercial: the provider is deciding whether your product is something it is willing to process.

If you want the deep version of the entity side specifically, [KYB verification](https://dodopayments.com/blogs/kyb-verification) covers the business checks in detail, including which registry documents get rejected and why beneficial ownership thresholds differ between jurisdictions. This guide stays on the journey: what happens, in what order, and where it goes wrong.

## The KYC Onboarding Process, Stage by Stage

The process is more sequential than it looks from the dashboard. Understanding the order tells you which stage you are actually stuck in.

### Stage 1: Account creation and business profile

You create login credentials and describe the business. Legal name, country of incorporation or residence, business type, what you sell, expected monthly volume, and the domain you will sell from.

This stage is fast and feels trivial. It is not. Almost every later problem traces back to something entered here that did not match a document submitted three days afterwards.

### Stage 2: Identity verification

A government-issued photo ID plus a liveness check, usually run through a specialist vendor inside the provider's flow. Dodo Payments runs this step through Persona, as described in the [account verification documentation](https://docs.dodopayments.com/miscellaneous/verification-process).

For a sole trader this is often the only identity step. For a registered company it repeats for every director and every beneficial owner above the disclosure threshold.

### Stage 3: Entity and ownership verification

Only applies if you sell through a registered company. The provider looks up the entity in the official registry, then traces ownership upward until it reaches natural persons.

This is the slowest stage when it is slow. A single operating company owned directly by two founders resolves in minutes. A holding company in one country owning an operating company in another needs registry evidence at each layer.

### Stage 4: Website and product review

A human or an automated crawler visits your site. They are looking for a working product, pricing, terms of service, a refund policy, and a contact route. They are also checking that the product category matches what you declared.

This is the stage founders underestimate most, because it is the one with no document to upload. You cannot fix it by sending a PDF. The site has to be finished.

### Stage 5: Bank account and payout setup

You supply settlement details. The account name generally has to match the verified entity or individual. A company account in a founder's personal name is a routine rejection.

### Stage 6: Approval, limits, and going live

Approval is rarely binary. Many accounts go live with initial volume caps, a reserve, or a longer settlement cycle that relaxes once there is transaction history. [Merchant underwriting explained](https://dodopayments.com/blogs/merchant-underwriting-explained) covers how that risk assessment is formed, and [MoR payouts and settlement](https://dodopayments.com/blogs/mor-payouts-settlement-explained) covers what the resulting payout schedule looks like in practice.

```mermaid
flowchart TD
    A[Create account, describe business] --> B[Identity verification: ID + liveness]
    B --> C{Registered company?}
    C -- No --> E[Website and product review]
    C -- Yes --> D[Registry lookup + ownership chain]
    D --> E
    E --> F{Site complete and category accepted?}
    F -- No --> R[Manual review or information request]
    F -- Yes --> G[Bank account verification]
    G --> H{Account name matches entity?}
    H -- No --> R
    H -- Yes --> I[Approved: live with initial limits]
    R --> J{Gap resolved?}
    J -- Yes --> I
    J -- No --> K[Declined]
```

## Documents Required for KYC Onboarding

The exact list depends on your jurisdiction and structure, but the categories are consistent. Providers typically request the following.

| Document | Who needs it | Most common reason it fails |
| --- | --- | --- |
| Government photo ID | Everyone | Glare, cropped edge, or expired |
| Liveness selfie | Everyone | Poor lighting or a photo of a photo |
| Proof of address | Everyone | Older than the accepted window |
| Certificate of incorporation | Registered entities | Superseded by a later amendment |
| Registry extract | Registered entities | Pulled years ago, no longer current |
| Register of members or cap table | Registered entities | Option pool counted as issued shares |
| Bank account proof | Everyone | Account name differs from the entity |
| Tax identification number | Most sellers | Wrong format for the jurisdiction |

Assemble these before you start rather than hunting for them while a reviewer waits. An application that answers every request within hours behaves very differently from one that takes four days per round trip, even when the underlying business is identical.

One more practical point: image quality causes more failures than content does. Automated document checks reject a perfectly valid passport because a reflection crosses the machine-readable strip. Photograph documents flat, in even light, with all four corners visible.

## KYC Onboarding for Individuals vs Registered Companies

This is the question most indie developers actually have, and the answer is that both paths exist at most providers but they are not identical.

| | Individual or freelancer | Registered company |
| --- | --- | --- |
| Identity checks | One person | Every director and qualifying owner |
| Entity verification | Not applicable | Registry lookup required |
| Ownership mapping | Not applicable | Required, often the slowest step |
| Typical document count | Three to four | Eight or more |
| Bank account | Personal account usually accepted | Must generally be in the entity name |
| Typical speed | Faster | Slower, scaling with structural complexity |
| Tax handling | Personal income | Corporate, plus any indirect tax obligations |

Selling as an individual is genuinely faster because there is no ownership chain to trace. The tradeoff is not on the payments side, it is on the liability and tax side, which [do you need a business license to sell digital products](https://dodopayments.com/blogs/business-license-sell-digital-products) and [tax compliance for solopreneurs](https://dodopayments.com/blogs/solopreneurs-tax-compliance) both cover.

A common sequencing mistake: incorporating a company mid-onboarding. If you start verification as an individual and then form an entity two weeks later, you are not updating an application. You are starting a new one, because the legal counterparty changed. Decide the structure first.

## Why KYC Onboarding Applications Get Delayed or Rejected

Most stalls are not judgements about your business. They are mismatches a reviewer cannot resolve without asking you.

- **Name inconsistency.** The legal name on the registry, the bank account, the domain, and the application must agree. A trading name is fine if it is disclosed rather than substituted.
- **An unfinished website.** No pricing page, a placeholder terms of service, or a checkout that does not reach a product. Reviewers cannot approve something they cannot see working.
- **A product description that does not match the site.** Declaring "developer tools" against a site selling coaching bundles reads as a discrepancy, not a rounding error.
- **Category restrictions.** Some verticals are excluded or need extra review regardless of how well documented you are. The [merchant acceptance documentation](https://docs.dodopayments.com/miscellaneous/merchant-acceptance) lists which categories are accepted, and [high risk merchant accounts](https://dodopayments.com/blogs/high-risk-merchant-account) covers what changes when the vertical itself is the obstacle.
- **Opaque ownership.** Layered holdings, nominee arrangements, or trusts each add a round of evidence gathering.
- **Bank account mismatch.** A settlement account in a name the provider has not verified.
- **Undisclosed history.** A previous account termination that surfaces during screening is treated far more seriously than one you declared up front.

Rejection is also not always permanent. A decline for an incomplete site is a fixable state. A decline for a prohibited category is not, and the productive response is a provider whose acceptance policy covers your product rather than a reapplication with better photographs. If you arrived here after an account closure elsewhere, [what to do when your Stripe account is banned](https://dodopayments.com/blogs/stripe-account-banned-alternative) covers the recovery path.

## How Long KYC Onboarding Takes

For a straightforward case, a day or two is normal. Dodo Payments publishes a typical verification window of one to three business days, with most reviews completing inside 72 hours.

Straightforward means: one operating entity or one individual, a jurisdiction with a searchable public registry, ownership that is one layer deep, a finished website, and a bank account in the matching name.

Complexity extends it. Each corporate layer, each additional beneficial owner, each jurisdiction with a thin registry, and each round trip for a clearer document adds time. Weeks rather than days is a structure problem, not usually a queue problem.

The controllable variable is response latency. Providers work the file when you answer. Two hours versus two days per request compounds quickly across four or five exchanges.

## What KYC Onboarding Software Does Behind the Scenes

When people search for KYC onboarding software they usually mean one of two different things, and the distinction matters for what you actually need.

The first is the compliance stack a payment provider runs internally: document capture, optical character recognition, liveness detection, registry lookups, sanctions and politically exposed person screening, adverse media checks, and a case management queue for anything the automation cannot clear. You do not buy this. You experience it as the verification flow inside your provider's dashboard.

The second is standalone identity verification you embed in your own product, because your users need verifying. A marketplace vetting sellers, a fintech onboarding account holders, or a platform paying contractors all have this problem independently of their own merchant onboarding.

The two get conflated in search results, and it leads founders to evaluate enterprise compliance vendors when what they needed was a payment provider that verifies them quickly. If you are onboarding to sell a product, the second category is not your problem yet.

Worth knowing: automation clears the ordinary cases and escalates the rest. A file that goes to manual review has not failed. It has simply hit a condition the rules could not resolve, most often an ownership chain or a website that did not load cleanly.

## How the Merchant of Record Model Changes Onboarding

Under a direct merchant account, you are onboarded as a merchant by an acquiring bank. That means acquirer-level underwriting, card network registration, and separate processes if you expand into new markets with new acquirers.

Under a [merchant of record](https://dodopayments.com/blogs/what-is-a-merchant-of-record), the MoR holds those relationships and becomes the legal seller of record. You are verified once as a business partner it settles funds to, and that single verification covers selling into the markets the MoR already supports.

It does not remove KYC. Regulated financial institutions must verify the businesses they pay, and an MoR paying you is exactly that relationship. What changes is how many times you do it and who carries the indirect tax liability afterwards. [Merchant of record vs PSP](https://dodopayments.com/blogs/merchant-of-record-vs-psp) and [merchant of record vs PayFac](https://dodopayments.com/blogs/merchant-of-record-vs-payfac) cover the structural differences, and [merchant of record for SaaS](https://dodopayments.com/blogs/merchant-of-record-for-saas) covers the subscription case specifically.

Dodo Payments operates as an MoR, supports payments across 220+ countries and territories, and handles tax compliance in 190+ countries. The [accounts documentation](https://docs.dodopayments.com/miscellaneous/accounts) covers what changes once verification clears, and the [supported countries list](https://docs.dodopayments.com/miscellaneous/accepted-countries-and-territories) covers geographic eligibility.

## What Happens After You Go Live

Verification is a record that has to stay accurate, not a gate you pass once.

Providers re-verify periodically, and certain events trigger a refresh outside that cycle: a funding round that moves someone across the ownership threshold, a director change, a redomiciliation, a new product in a different risk category, or a screening hit on an existing owner. The failure mode is a stale file. You raise a round, add investors, change a director, tell the registry and not the provider, and eighteen months later a routine refresh finds a mismatch and restricts the account at an inconvenient moment.

The habit that prevents this is simple: whenever you file a change with the company registry, file the same change with your payment provider.

Early operations also matter more than most founders expect. Chargeback rates, refund rates, and fraud signals in the first months feed directly into limits and reserves. [Chargeback prevention for SaaS](https://dodopayments.com/blogs/chargeback-prevention-saas) and [card testing fraud](https://dodopayments.com/blogs/card-testing-fraud) cover the two patterns most likely to trigger a review. On the data side, [PCI DSS compliance for digital businesses](https://dodopayments.com/blogs/pci-dss-compliance-digital-business) and [payment compliance under GDPR and PSD2](https://dodopayments.com/blogs/payment-compliance-gdpr-psd2) cover obligations that continue after onboarding.

If you are still building the integration while verification runs, the [integration guide](https://docs.dodopayments.com/developer-resources/integration-guide) covers the technical setup, which you can complete in test mode in parallel.

## FAQ

### What is KYC onboarding?

KYC onboarding is the verification process a payment provider runs before letting you accept payments and receive payouts. It confirms your identity, the legal existence of your selling entity, who ultimately owns it, the bank account funds will reach, and whether your website and product match what you declared.

### How long does KYC onboarding take?

For a single entity or individual in a jurisdiction with a searchable registry, typically one to three business days. Layered ownership, an unfinished website, or slow responses to document requests can extend it to weeks, and the response speed is usually the part you control.

### Do I need a registered company to pass KYC onboarding?

Not necessarily. Many providers onboard sole traders and individuals through personal identity verification instead of entity verification, though available products, limits, and payout options can differ. If you sell through a registered entity, that entity is what gets verified regardless of who owns it.

### Why was my KYC onboarding application rejected?

The most common causes are fixable mismatches: a legal name that differs across the registry, bank account, and application; an unfinished website without pricing or terms; or a product description that does not match the live site. A rejection based on a prohibited business category is different, since no amount of documentation changes the category.

### What documents do I need for KYC onboarding?

Typically a government photo ID and liveness selfie, proof of address, and bank account proof for everyone. Registered companies usually add a registry extract, incorporation certificate, a register of members or cap table, and identity documents for each director and qualifying beneficial owner. Exact requirements vary by country and provider, so confirm the list with yours.

## The Takeaway

KYC onboarding is a sequence, not a single approval. Identity, entity, ownership, website, and bank account each get resolved in turn, and a file stalls at whichever one a reviewer cannot close on the evidence in front of them.

Nearly every avoidable delay comes from the same three places: a name that is not identical everywhere it appears, a website that is not actually finished, and documents gathered reactively instead of in advance. Fix those before you apply and the process usually closes in days.

Decide your structure first, assemble the pack, ship the full site including pricing and terms, and answer requests the same day. The verification queue is not the bottleneck. The round trips are.
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)