KYB Onboarding Best Practices

Build fast, reliable KYB onboarding flows that maximize conversion and minimize fraud risk

When a business signs up to use your product, every second of friction matters. The difference between a 30-second form and a 3-minute form can cut your conversion rate in half. Yet KYB compliance requires you to collect detailed company information: legal name, registration number, address, legal representatives, beneficial owners.

The best onboarding experiences solve this tension with forms that are pre-filled using data from public company registers. Your customer selects their company from a search, and you use this info to fill in the rest. Less typing, fewer errors, more conversion.

But register data comes with challenges. Fetching it can be slow, expensive, and unreliable. This guide explains how to navigate these trade-offs to build an onboarding flow that converts.

The Fundamental Trade-off

Company registers are authoritative sources of truth, but they weren’t designed for real-time API access. When you query a register directly, you might wait seconds or sometimes minutes for a response. Some registers go down regularly. Pricing varies wildly: a company profile might cost €0.10 in one country and €5.00 in another.

These constraints are especially problematic during an onboarding. Your prospect is sitting there, waiting. Each second of delay increases the chance they’ll drop. And since many prospects won’t convert anyway, spending €5 on everyone who starts your signup process doesn’t make economic sense.

The solution is to use different data at different stages of your flow:

Early in onboarding, when you’re not sure whether the prospect will convert, use fast and affordable data. Accept that it might be slightly stale or incomplete; you’ll verify it later.

After qualification, when the customer has demonstrated real intent, invest in authoritative verification. Query the register directly, fetch official company documents, and cross-check everything.

This staged approach gives you the best of both worlds: a fast, high-conversion onboarding experience that meets your compliance requirements.

Start with Company Search

Before you can prefill anything, you need to know which company your customer represents. This means search.

Most onboarding flows already collect the customer’s country early on, to adapt the experience, determine pricing, or define the service area. Use this to scope your search. A country-scoped search is faster and returns more relevant results.

When your customer starts typing their company name, you want results to appear immediately. Use streaming search to display results as they arrive from different sources. In countries like Germany, we query both a cached index (fast, ~200ms) and live registers (comprehensive) in parallel. Your customer sees initial results almost instantly, with more appearing as additional sources respond.

Search on Topograph is free and typically returns results in less than 5 seconds. The goal is to make company selection feel effortless.

Prefill with Onboarding Data

Once your customer selects their company, you need to retrieve profile data to populate your forms. This is where the trade-off materialize.

If you query the register directly, you might have to wait 5–30 seconds for a response. In some countries, the register might be down entirely. Meanwhile your customer is staring at a loading spinner, wondering if something broke. Many will leave.

The onboarding endpoint solves this problem. It’s designed specifically for the onboarding use case, with three guarantees:

• Speed: P90 response time under 5 seconds
• Reliability: Over 99% success rate
• Predictability: Fixed price €0.50 per request, regardless of country

To achieve this, we make trade-offs. The data might come from a cache rather than a live register query. In countries where register access is expensive, we might use alternative data sources. Some data points that are particularly costly to retrieve may be omitted.

These trade-offs are acceptable during onboarding because you’re not making final compliance decisions yet. You’re just trying to reduce friction and collect initial information. The verification comes later, when the customer has proven they’re serious.

Importantly, trade-offs does not mean low-quality: we always favour official sources and when we do cache data, we still refresh it quite often.

For a complete list of supported countries, see the Onboarding Profile documentation.

Even if we offer a fast response, consider adding a lightweight UI step between launching the API request for data request and displaying your forms, e.g. phone verification or email confirmation. This gives the data a moment to load while the customer does something useful, making the experience seamless.

Check what Documents Exist

While you’re fetching onboarding data, also check which official documents are available in the register for the company of interest. This request runs in parallel and is free.

Knowing what documents are available helps you plan the rest of the flow:

• Documents that exist in the register can be retrieved automatically for verification
• Documents that don’t exist will need to be uploaded by your customer

This avoids the frustrating experience of asking customers to upload documents you could have fetched yourself.

Apply an Early Filter

With the onboarding data in hand, you can make an initial assessment: can you actually work with this company?

Check the basics:

• Is the company active, or has it been dissolved?
• Does the industry or legal form fit your product requirements?
• Are there any obvious red flags in the company structure?

Reject early if the answers require it; this saves everyone time. There’s no point putting a prospect through additional verification steps if you already know you can’t serve them.

Early rejection also protects your unit economics. Each step past this point costs money: verification data, document retrieval, manual review. Don’t spend on companies that will never become customers.

Verify against Data from the Register

This step is critical. Everything up to this point has been about speed and conversion. Now you need to verify that the information is correct.

The data your customer provided might not match reality. They could be impersonating a different company. They might have provided outdated information. Or, in rare cases, the cached data from the onboarding endpoint you used for pre-filling might have changed since last refresh.

At this stage, the customer has demonstrated real intent. They’ve filled out your forms, passed your initial filter, and progressed through your onboarding flow. Now it’s worth investing in authoritative data.

The verification data endpoint provides comprehensive, verified data:

• Live data: Fetched directly from public company registers
• Complete data: Automatically enriched with information extracted from available company documents
• Cross-checked: Data verified against register documents (beta feature, contact us to enable)

This endpoint is more expensive than the onboarding endpoint, and responses may take longer. That’s the trade-off for authoritative data. But at this stage of your flow, it’s the right trade-off to make.

Build this as an asynchronous step. Submit the verification request, then let the customer continue while it processes in the background. Use webhooks to receive the results when they’re ready.

Complete with Document Verification

The final layer of verification is cross-checking data against official documents from the register:

• Financial statements reveal the company’s financial health and disclosures
• Register extracts confirm registration details and legal representatives
• Articles of association show company structure and governance rules
• UBO extracts confirm beneficial ownership declarations

Why should you fetch these documents from the register, rather than ask your customer to upload them? To name two of the many reasons: (1) the individual filling the form does not necessarily know where the right documents are or have access to them and (2) because documents can be forged, but register responses cannot. When you retrieve a document directly from the official source, you know it’s authentic.

See our document retrieval guide for details on how document fetching works.

Putting it Together

The complete flow balances speed with thoroughness:

Stage	What happens	Why
Search	Customer finds their company	Fast, free, reduces friction
Onboarding data	Prefill forms with company info	Fast and cheap, optimized for conversion
Available documents	Check what’s in the register	Plan the verification step
First filter	Assess basic fit with your process	Save costs on unqualified leads
Verification data	Verify against live register data	Authoritative data for compliance
Document verification	Cross-check against official documents	Prevent document fraud and improve UX

The key insight is that different stages have different requirements. Early on, speed and cost matter more. Later, accuracy and authority matter most. By choosing the right data for each stage, you get better conversion and strong compliance.

The Flow

Next steps

Search

Implement company search with results streaming

Onboarding profile

Fast, affordable data for onboarding

Verification Data

Live data verification from public registers

Document Retrieval

Official company documents for verification