AiPrise Token SharingShare Verified Customer Information.

When two companies work on the same transaction, one can securely pass a customer’s verified KYB or KYC record to the other through AiPrise. The receiving partner can still run its own checks where something is missing and request further information when needed. The customer never submits the same documents twice.

Launch partners

Less Repetition. Faster Onboarding.You Stay in Control.

Less duplicate work

Less duplicate work

Compliance teams stop collecting the same documents and re-running checks another institution has already done.

Your partner starts the second onboarding with verified data

Your partner starts the second onboarding with verified data

The customer's record arrives already collected and checked. Use the checks that meet your policy, run any others you require, then request only what's missing.

Shared customers go live sooner

Shared customers go live sooner

Customers start using services with your partner sooner, with fewer document requests going back and forth.

One Customer, Many Partners in the Payment Chain

A business signs up with a payments platform. Behind it, on-ramps, stablecoin providers, off-ramps and payout partners each have to verify that same business under their own rules.

Without Token Sharing

The business uploads the same documents to every partner.

Each partner collects and checks the data from scratch.

When the partner needs more information, the request travels back through the first partner by email, adding days of manual work.

With Token Sharing

The business is verified by the first partner, the Donor.

After approval, its record is shared with the next partner, the Recipient, as a token, under rules both companies agreed to.

The partner uses the checks that meet its own policy, runs any others it requires, and asks only for what's missing.

Two Roles. Clear Rules.

The Donor is the company that already verified the customer. The Recipient is the partner that needs to onboard them. A company can be a Donor in one partnership and a Recipient in another. The Recipient uses the checks that meet its own policy and runs any others it requires.

Connect

01

The Recipient sends an invite code. Once the Donor accepts, the companies are connected. Connecting alone shares nothing.

Agree on the rules

02

The Recipient sets out what it needs: which customers qualify, how recent the verification must be, and which follow-up questions it may ask. The Donor reviews and accepts before anything is shared.

Share

03

When a customer is approved and meets the agreed rules, the Donor sends their record as a token, automatically or with one click.

Decide

04

Tokens are imported automatically, or the Recipient previews each one and imports it manually. Each becomes a new customer record, ready for review.

Fill the data gaps

05

The Recipient requests only what's missing, from the agreed list. If the Donor already holds it, it's returned without contacting the customer. If not, the Donor asks the customer on the Recipient's behalf.

Tokens carry approved KYB and KYC records. Decide what and how much you want to share or reuse.

Three Ways Partners Use It

01 · Payments and settlement

A payments platform shares merchant KYB with its settlement partner

Approved merchants arrive as tokens and run through the partner's own KYB checks. When the partner asks for a bank statement, the platform sends the copy it already has. The merchant isn't asked again.

KYB
Approved merchants
Imported automatically
02 · Marketplace lending

A marketplace shares seller KYB with a working-capital lender

The lender reviews each token before importing. Its source-of-funds question reaches the seller through the marketplace, the company the seller already knows.

KYB
Sellers who opted in
Reviewed before import
03 · Wallet and card issuing

A wallet app shares user KYC with its card-issuing partner

Users who request a card do not repeat identity steps. The issuer runs its own KYC checks on the shared data.

KYC
Approved users
Imported automatically

Illustrative setups based on common partner models. Company types are examples.

Your PoliciesStay Yours

Rules agreed up front

Rules agreed up front

Both companies agree what's shared, with whom, and under what conditions before any data moves.

Your own checks, your own decision

Your own checks, your own decision

Use the checks that meet your policy and run any others you require. The decision is always yours.

Separate records, full audit trail

Separate records, full audit trail

Each company keeps its own policies, results and decisions. Every token sent or imported, and every follow-up request, is logged.

Choose what gets shared

Choose what gets shared

Data moves only under an active agreement, and only for customers who meet its rules.

Built on theAiPrise Network

AiPrise verifies businesses and individuals across 200+ countries and 500+ government and business registries. Token Sharing lets companies on that network share verified customer information on the transactions they work on together, so customers onboard and transact sooner.