KYC/KYB Verification

Onboard personal and business clients in every market with two layers of KYC: our internal KYC checks every case in a back office you configure, then an external provider verifies identity and screens every name.

  • Individual app
  • Business app
  • Back office
An operator’s case review in the back office: risk score, documents and key answers

Two layers

Internal KYC and external KYC, working together

Personal KYC and business KYB both run through two layers. Our internal KYC checks every case in the back office, then your external provider verifies it and screens every name. The final decision stays with the licensed entity.

Internal KYC · the Finamp platform

Ours, and configured by your team in the back office (the Control Panel). Every case passes it first, and it adds checks a provider doesn’t do.

Only complete, wanted cases move on, so you pay for fewer external checks.

  • Forms you change without an app release
  • Questions asked only when an answer calls for them
  • Risk score and routing rules
  • Automatic document reading
  • Document quality checks
  • Operator review
  • Requests for missing information
  • Repeat checks at any time
  • Second-operator sign-off
  • Tiers with their own limits
  • A full audit history

External KYC · your providers

A provider per market or check confirms the case is genuine. Its result comes back to the same case, and a refer, a fail or a screening hit goes back to an operator.

  • Documents are genuine
  • Identity matches the person
  • Sanctions and PEP screening
  • Adverse-media screening
  • Company records for KYB
  • A provider per market or check

How a case moves

Pick a route and follow the case

One example setup. Every route passes internal KYC first, and every case that can open an account is screened against sanctions and PEP lists at a provider before it does.

Low risk goes straight to the provider

Internal KYC finds nothing that needs a person, so the case skips manual screening. The provider still checks it and screens every name.

  1. The customer applies in the app, which shows In review
  2. Internal KYC asks only what their answers call for and reads every document
  3. It scores the case low risk and fast-tracks it to the provider
  4. The provider checks identity and documents and screens every name
  5. The account opens, and the app shows Approved

High risk, PEP or a document issue goes to an operator

A routing rule sends the case to an operator in the back office before any paid check.

  1. The customer applies in the app
  2. Internal KYC asks only what their answers call for and reads every document
  3. A rule sends the case to manual screening: high risk, PEP or a document issue
  4. An operator reviews the answers, documents and risk breakdown, then gives it a green light
  5. The provider checks identity and documents and screens every name
  6. The account opens, and the app shows Approved

When something’s missing, the operator asks

The case doesn’t restart. It keeps its history and goes back to the operator with the new answer.

  1. The customer applies in the app
  2. Internal KYC asks only what their answers call for and reads every document
  3. A rule sends the case to manual screening
  4. The operator finds an unclear document and asks for a file, text or a date
  5. The app shows Action needed, and the customer answers in the same case
  6. The new document is read again, and the operator gives the case a green light
  7. The provider checks identity and documents and screens every name
  8. The account opens, and the app shows Approved

A provider hit comes back to an operator

A sanctions, PEP or adverse-media match, a refer or a fail never opens an account on its own. The licensed entity makes the final decision.

  1. The customer applies in the app
  2. Internal KYC asks only what their answers call for and reads every document
  3. It scores the case low risk and fast-tracks it to the provider
  4. The provider finds a possible sanctions, PEP or adverse-media match, a refer or a fail
  5. The case comes back to an operator, who reviews the hit and decides

A sanctioned country is rejected automatically

The rule is about countries, and it runs before any paid check. Name screening against sanctions and PEP lists happens at the provider.

  1. The customer applies in the app
  2. Internal KYC asks only what their answers call for and reads every document
  3. A routing rule matches a sanctioned country and rejects the case
  4. The app shows Not approved, with no reason given

Your setup

Each market and tier gets its own scenario

Four examples, from the lightest check to the heaviest. Each scenario has its own forms, rules, risk weights and providers, set in the back office, and every one includes sanctions and PEP screening.

Basic wallet · any market

No ID check. The customer can upgrade to full KYC for higher limits without starting again.
  1. Phone and details
  2. Internal screening
  3. Provider: sanctions screening
  4. Approved, low limits
upgrade

Full personal KYC · market A

ID, selfie and address, checked by the provider for this market.
  1. ID, selfie, address
  2. Internal screening
  3. Provider A: identity
  4. Approved, full limits

Agent or merchant · market B

The outlet and its owner, with limits set per tier.
  1. Outlet and owner
  2. Internal screening
  3. Provider B: owner ID
  4. Approved, limits per tier

Business KYB · market C

Company records and owners, each checked by its own provider. A completed KYB creates the business wallet.
  1. Company and owners
  2. Internal screening
  3. Provider C: registry
  4. Provider D: owners
  5. Approved, business account

Internal KYC, in the back office

Your rules, changed without an app release

Form editor with a live app preview

Forms you change in real time

Build a form in the back office and see it live in the app preview. Mark each field mandatory or optional, or ask it only when an earlier answer calls for it.

Collect text, dates, yes/no answers, lists of options, multiple choice, documents and photos, and repeating blocks. The app shows the new version without a release, and customers part-way through finish on the version they started.

Routing rules and risk weights in the back office

Routing rules decide where each case goes

Every case is scored the moment it’s submitted, and rules run top to bottom: the first match decides. A case is rejected automatically, sent to an operator, or fast-tracked to your provider. Only accepted documents go to the provider.

Rules and risk weights are set per market, product or client, and change any time.

A passport read automatically and matched against the customer’s answers

Documents are read automatically

Text is read from each document and compared with the customer’s answers, with quality checks for sharpness, glare and the machine-readable zone.

Approval stays locked while a document is unclear, and operators can correct any value that was read.

Proof of address for the next verification level

Start light, upgrade later

Each tier carries its own limits and permissions, and your team defines the tiers. A customer can start on a basic wallet and move to full KYC for higher limits without starting again.

Asking the customer to resubmit an unclear proof of address

Ask for more at any time, not only at onboarding

An operator asks for a file, text or a date and writes a note. The customer sees what’s needed in the app and answers in the same case, which keeps its history and goes back to review. It doesn’t restart.

The same works after the account is open: ask for KYC or KYB again whenever you need to, for example when a visa or ID document expires, or when a company has to renew its registration.

An operator’s case page: risk score, documents and key answers

Operators decide in one place

One page per case: risk score, documents, answers and history. From there an operator asks for more, rejects or sends the case on.

Screening hits from the provider are reviewed on the same page.

Business KYB: adding directors and owners

Personal KYC and business KYB in the same app

The same journey runs on iOS, Android and web; only the forms differ. People give personal details, ID, a selfie and proof of address.

Businesses give company details and addresses, then their directors and owners with documents, and company documents. A completed KYB creates the business wallet.

Approved: the wallet home screen after KYCNot approved, with the date the customer can apply again

The customer sees the decision in the app

When the case is approved, the app shows Approved and the wallet switches on.

When it isn’t, the customer sees Not approved, with no reason given, and can apply again later. No money is taken.

  • Sumsub
  • Onfido
  • CAComplyAdvantage

A provider per market or check

Connect providers such as Sumsub or Onfido, with AML screening such as ComplyAdvantage, or your EMI or BaaS partner’s KYC/KYB. Each market or check can point to a different provider, managed from the back office.

Reliability and security

Built to hold up when things go wrong

Bad input stops early

Missing documents block submit. Files are checked by content, with a 10 MB limit.

No case is lost

Timers live in the database and resume after a restart or a slow provider.

Operators are controlled

Sign-in codes, roles and a permission for every route. Every action is audited.

Data stays with its owner

Another customer gets “not found”. Files are owner-only, and logs hide personal data.

Tests come first

Every requirement has an ID and a test that names it, and a gate checks it.

A locked baseline

Security rules can’t be weakened without a human-approved change.

Integration

Two ways to work with us

Next step: a free technical session, where we map your markets, tiers and providers onto scenarios, live in the back office.

It runs beside your backend

Our KYC/KYB module sits between your platform and the providers. You keep your backend and ledger; we send back the decision and status.

Providers are added by configuration and called only when needed.

Or our engineers join your build

If you’d rather build KYC/KYB yourselves, our engineers join your team and bring the same forms, rules and screening approach.

Checklist

All 15 KYC/KYB Verification features

Where each one is available. The full feature list covers every module.

KYC/KYB Verification: features and where they are available
FeatureIndividual appBusiness appBack office
KYC/KYB data managementUsers provide and update the identity data needed to verify a person or a business.Individual appAvailableBusiness appAvailableNot available
Verification tiersVerification levels, each with its own limits and permissions, that users move through as they verify.Individual appAvailableBusiness appAvailableNot available
Verification statusesUsers always see the current status of their verification.Individual appAvailableBusiness appAvailableNot available
Tier-based permissionsWhat a user can do in the app depends on the verification tier they have reached.Individual appAvailableBusiness appAvailableNot available
External KYC provider integrationIdentity checks run through an external KYC provider connected to the product.Individual appAvailableBusiness appAvailableNot available
Sanctions and PEP screeningEvery case, the basic wallet included, is screened against sanctions and PEP lists at a provider before an account opens.Individual appAvailableBusiness appAvailableNot available
Verification queue with search and filtersStaff work through KYC and KYB requests in a searchable, filterable list.Not availableNot availableBack officeAvailable
KYC/KYB review cardStaff review each verification request on a single card with its submitted data.Not availableNot availableBack officeAvailable
Tier management: limits and permissionsStaff define verification tiers and the limits and permissions attached to each one.Not availableNot availableBack officeAvailable
External KYC provider settingsStaff manage the connection to the external KYC provider from the back office.Not availableNot availableBack officeAvailable
KYC/KYB form builderStaff build and change verification forms with a live preview, and the apps show them without a release.Not availableNot availableBack officeAvailable
Scenarios per market and tierEach market, tier and client type gets its own forms, rules, risk weights and providers.Not availableNot availableBack officeAvailable
Risk scoring and routing rulesEach submitted case is scored and routed: rejected, sent to an operator or fast-tracked to a provider.Not availableNot availableBack officeAvailable
Information requestsStaff ask for a file, text or a date at any time, for example when a document expires, without restarting the case.Not availableNot availableBack officeAvailable
Automatic document readingText is read from each uploaded document and compared with the customer’s answers.Not availableNot availableBack officeAvailable

Frequently asked questions

Every case, personal KYC or business KYB, passes our internal KYC first: configurable forms, risk scoring and routing rules, automatic document reading and operator review in the back office. Complete, wanted cases then go to an external provider, which confirms documents and identity, checks company records and screens every name against sanctions and PEP lists. The provider’s result comes back to the same case.

Yes. Each market, tier and client type gets its own scenario, with its own forms, rules, risk weights and providers, set in the back office. Changes reach the app without a release.

Yes. Every case is scored and routed the moment it’s submitted. A case from a sanctioned country is rejected automatically, high-risk cases go to an operator, and only complete, wanted cases reach a paid provider.

Yes. Every case, the fast track and basic wallet included, is screened against sanctions and PEP lists at a provider before an account opens. Any hit goes back to an operator.

Yes. You can ask for KYC or KYB again at any time, for example when a visa or ID document expires, or when a company has to renew its registration. The customer answers in the app, and the request is added to their history.

Yes. A customer can start on a basic wallet with low limits and upgrade to full KYC for higher limits without starting again. Each tier carries its own limits and permissions.

The licensed entity. Finamp is a technical provider: the platform screens and routes cases, the provider confirms documents and screens names, and the final decision stays with the licensed entity.

The platform has its own KYC/KYB, and connects to external providers such as Sumsub and Onfido or to your EMI or BaaS partner’s KYC/KYB. A provider you already work with can be added, and each market or check can use a different one.

With a free technical session: we map your markets, tiers and providers onto scenarios, live in the back office. The module then runs beside your backend, or our engineers join your own KYC/KYB build.

Start with a free technical session

Book a demo