Verify your users. Without building your own end-to-end KYC setup.

Start from scratch and let Reap run KYC end to end. Or bring users you've already verified, so your users don’t have to go through duplicate onboarding flows. Whichever route you pick, you get compliant onboarding without building or running the entire stack yourself.

Talk to our team See how it works

LESS TO BUILD

Launch sooner, without building the entire KYC setup.

To launch a card program properly you need a KYC provider, a way to collect and store documents, and rules for each country you operate in. That's a lot of work before your first card goes out.

Skip most of the build

Reap checks your users' IDs and handles their documents through the same integration you use for everything else. If you don't have compliance tools, you don't need to build them.

No KYC provider relationship to find or manage

If you haven't built one yet, you don't need to. Reap runs on Sumsub today, and that's Reap's relationship to manage, not yours.

VERIFICATION METHODS

Flexible KYC methods.
You pick the one that fits.

Every platform starts from a different place, so there are three options. They all use the same API, the same webhooks and the same statuses. Pick the one that matches where you are today.

Managed KYC — starting from scratch

No KYC provider yet? Let Reap handle it end to end. You embed the verification SDK in your app, the user completes their identity checks, and the result comes back by webhook. You never touch identity documents — Reap handles capture, storage and provider communication.

Sumsub Token Sharing — already on Sumsub

Already using Sumsub with a verified user base? Share a token per user and Reap imports the verification directly to validate. After a one-time setup, onboarding a verified user onto Reap is a single API call.

Universal KYC — any other provider

Using a provider that isn't Sumsub? Submit the verified data and supporting documents, and Reap reviews the submission. Bring data from whoever you work with.

Whether you're starting from zero or bringing an existing verified user base, there's a route that doesn't require rearchitecting your onboarding.

NO DOUBLE-KYC

Protect user experience.
No double-KYC for cards.

Your users already proved who they are when they joined your platform. Asking them to do it again just to get a card is annoying, and some of them will give up halfway.

Bring the checks you've already run

Sumsub Token Sharing and Universal KYC let you carry them over. Reap reviews them, approves the user, and they're card-ready.

No second upload. No second selfie.

Drop-off happens where you ask for the same thing twice. This removes that step.

KYC AND KYB

Issuing to businesses too? Reap supports KYB.

Reap API's Compliance module supports both KYC and KYB — so you can launch retail card programs for individual users and corporate card programs for businesses, all from the same integration.

One compliance layer. Both program types. No separate vendors to manage.

SEE KYB

One module, both program types

Two KYB methods

One module, both program types

With Reap you don't stitch together separate vendors for individual identity verification and business verification. Both are built into the same module, under the same API.

MORE THAN KYC

Verification is one piece. Reap runs the rest too.

The same integration, the same team, the same webhooks — whatever you add next. Your approved users stay approved. Adding a module doesn't mean putting anyone through duplicate onboarding.

Card Issuing

Issue branded cards on Reap's Visa principal issuing licence.

CHECK IT OUT

Payments

Stablecoin-funded fiat payouts across 45+ corridors.

CHECK IT OUT

Agentic Payments

Let AI agents spend, bounded by policy.

CHECK IT OUT

Sentry

Managed fraud monitoring, disputes and Visa compliance.

CHECK IT OUT

USE CASES

Verification flows built on Reap

Whether you're verifying your first user or migrating a verified base, the compliance work underneath is the same — and it's the part nobody wants to build twice.

Consumer card programs Platforms that already verify their users Card programs in more than one country

01 For

Consumer card programs

You run a fintech or crypto app and want to give cards to your users. Each user has to be verified before they can have an account or a card. Let Reap run the whole check with Managed KYC, or bring your own results through Token Sharing or Universal KYC.

01 For

Platforms that already verify their users

You've already checked your users with Sumsub or another provider. There's no reason to put them through it again. Use Token Sharing to bring Sumsub verifications straight across, or Universal KYC to send results from any other provider for Reap to approve.

01 For

Card programs in more than one country

Each country has its own rules. Mexico, for example, needs extra details like CURP, country of birth and economic activity. Reap handles those differences behind the scenes, so your integration stays the same wherever your users are.

01 For

Web3-native teams

Your ops budget lives on-chain. Fiat conversion is the tax you pay to buy SaaS and AWS. With VIC, top up in USDC and transact against merchants globally — no fiat on-ramp in the middle.

01 For

Web3-native teams

Your ops budget lives on-chain. Fiat conversion is the tax you pay to buy SaaS and AWS. With VIC, top up in USDC and transact against merchants globally — no fiat on-ramp in the middle.

HOW IT WORKS

Get started in 4 steps

TALK TO OUR TEAM

Talk to our team

We agree on your verification method and any country-specific requirements.

Set up your method

Managed KYC, Sumsub Token Sharing or Universal KYC. Fixed once per project, configured during onboarding.

Build and test in the sandbox

The Compliance module works like the rest of Reap API, with REST endpoints and webhooks for status updates. Simulate every result — approved, rejected, retry required, restricted — without running a real check.

Go live

Start verifying real users. Reap blocks cards from going to anyone who isn't approved, so you don't need to check manually. Listen for status webhooks to keep your systems up to date.

What you do vs. what Reap does

You	Reap
Choose assets and pricing	Authorises spend against available balance
Maintain user balances (deposits/withdrawals/repayments)	Clears, reverses, and settles transactions
Fund the master collateral account	Holds the master collateral account
Keep custody and the user relationship	Polls your pricing feed for dynamic-rate assets
	Applies your balance updates atomically

FAQ

Questions platforms ask before integrating KYC

What is Reap API's Compliance module?

Reap API's Compliance module is the identity verification layer for platforms building on Reap. It covers both KYC for individual users and KYB for businesses, through the same API, webhooks and statuses as the rest of the platform. Your users complete full checks — ID, documents and a liveness selfie — run by Reap rather than your team. If you already verify your users elsewhere, you can bring those results across instead of starting again.

What KYC methods does Reap support?

Three. Managed KYC, where Reap runs the checks through a Sumsub SDK in your app. Sumsub Token Sharing, where you import verifications from your own Sumsub account. And Universal KYC, where you send results from any provider for Reap to review. You pick one per project during onboarding.

What's the difference between Token Sharing and Universal KYC?

Both let you keep your own provider, and Reap makes the final call in both. Token Sharing only works with Sumsub: you share a token, Reap checks the verification meets its standards, and nothing is collected twice. Universal KYC works with any provider: you send the data and documents, and Reap reviews them. Token Sharing is faster per user. Universal KYC works with anyone.

Do I need to manage my own KYC provider relationship?

Not if you haven't built one. Reap runs on Sumsub today and manages that relationship. If you already work with a provider, Token Sharing for Sumsub or Universal KYC for anyone else lets you keep it.

Will my existing verified users be approved automatically?

Only if their checks meet Reap's standards. If a user was verified to a lighter standard, they'll need to complete the missing steps in your KYC flow first.

Can I use a different method for different users?

No. The method is set once per project, and every user in that project uses it.

Can I verify businesses as well as individuals?

Yes. The same Compliance module handles KYB: business registration, ownership structure, and officer and UBO identification, each with its own KYC session. Once everyone is verified, the company is active and employees can start getting cards. No second vendor needed.

Who is responsible for AML and CTF?

You are, whatever setup you choose. Reap helps you meet those obligations. It doesn't take them over.

Do I need a compliance team?

You don't need a team to run the checks. Reap handles the provider, the documents and the status tracking. You do still need someone accountable for your regulatory obligations, like AML/CTF and sanctions screening.

Can I test everything in the sandbox?

Yes. You can trigger every KYC result — approved, rejected, retry required, restricted — without a real check, and test the whole flow before you go live.

What happens if I add more Reap modules later?

Your approved users stay approved. Adding Card Issuing, Payments or Agentic Payments doesn't require going through duplicate flows to onboard again.

Do you support Mexico's extra requirements?

Yes, through the same endpoints. Mexico programs collect extra details like CURP, country of birth, economic activity and who issued the ID. Mexican nationals also need a phone number, email, tax ID and a CURP document, on top of the usual ID and proof of address.

Get Started

Verify your users on Reap

TALK TO OUR TEAM

Notice

Verify your users. Without building your own end-to-end KYC setup.

Launch sooner, without building the entire KYC setup.

Skip most of the build

No KYC provider relationship to find or manage

No double onboarding for your users

Flexible KYC methods. You pick the one that fits.

Managed KYC — starting from scratch

Sumsub Token Sharing — already on Sumsub

Universal KYC — any other provider

Protect user experience. No double-KYC for cards.

Issuing to businesses too? Reap supports KYB.

One module, both program types

Verification is one piece. Reap runs the rest too.

Card Issuing

Payments

Agentic Payments

Sentry

Verification flows built on Reap

Consumer card programs

Platforms that already verify their users

Card programs in more than one country

Web3-native teams

Web3-native teams

Get started in 4 steps

Talk to our team

Set up your method

Build and test in the sandbox

Go live

What you do vs. what Reap does

Questions platforms ask before integrating KYC

Verify your users on Reap

Flexible KYC methods.
You pick the one that fits.

Protect user experience.
No double-KYC for cards.