Overview
KYC verifies a person. KYB verifies a company, including the people who own and control it. We wire those checks into your product so a user or a business can be approved, asked for more information, or stopped before money moves or a card is issued.
What we do
- KYC with Persona and Sumsub - documents, liveness, sanctions and PEP screening, and case review
- KYB for companies - legal entity, registration, ownership documents, ultimate beneficial owners, and control persons
- Bridge.xyz customer registration, including business KYB through the API or a hosted link
- Rain.xyz consumer KYC and corporate KYB, document upload, and card issuance after approval
- Webhooks and status mapping so your app knows when a check is approved, incomplete, or rejected
- Handoff between a verification you already hold and a platform that can reuse it
Platforms
Persona
Configurable KYC and KYB workflows inside your product: document and liveness checks, business verification, watchlists, and case management when a reviewer has to decide.
Sumsub
KYC and KYB in one stack, with transaction monitoring and Travel Rule support. A common fit for exchanges and wallets that want onboarding and ongoing checks from the same vendor.
Bridge.xyz
Bridge runs KYC on people and KYB on businesses you register, so those customers can move stablecoins and fiat. We integrate the Customers API, where you submit the data, and KYC Links, where the customer finishes a hosted flow. A standard business file includes the legal name, addresses, tax identifier, entity type, formation and ownership documents, and a person check on each ultimate beneficial owner at 25% or more and on each control person.
Rain.xyz
Rain verifies a person with KYC before a consumer card, and a company with KYB before a corporate card. The company application covers the legal entity, representatives, and ultimate beneficial owners, and each of those people still completes their own KYC. We submit the application, upload the documents Rain accepts, and follow the status until it is approved, then a card can be issued. When your program allows it, Rain can reuse a Sumsub or Persona verification you already have.
How we do it
- User map - We list who must be checked: the person, the company, each owner, and each control person.
- Vendor path - We choose whether your product owns the check with Persona or Sumsub, or the platform runs it, as Bridge and Rain do.
- Integration - We build the API calls, hosted links, document uploads, and webhooks.
- Product states - We map approved, needs-information, and rejected into the screens your users actually see.
- Production - We add idempotency, logging, and a path to resubmit when a document is rejected.
Use cases
- Wallet or exchange onboarding users with Persona or Sumsub
- Fintech registering business customers on Bridge before stablecoin payouts
- Card program submitting consumer KYC and corporate KYB to Rain
- Product that already verifies users and needs to pass that result into Bridge or Rain
Frequently asked questions
- Do you provide legal or licensing advice?
- No. We implement the verification flow. You work with legal and compliance advisors for jurisdiction-specific requirements.
- Which KYC and KYB platforms do you integrate?
- Persona and Sumsub when your product owns the identity or business check, and Bridge.xyz and Rain.xyz when that platform must approve the customer before they can move money or receive a card.
- Can Bridge or Rain use a check we already completed?
- Bridge accepts customer data through its API or a hosted KYC and KYB link. Rain accepts the documents its program requires, and when your contract allows it, a shared Sumsub or Persona verification.
- What is the difference between KYC and KYB?
- KYC verifies a person: a document, a liveness check, and a sanctions screen. KYB verifies a company: legal name, registration, ownership documents, and a person check on each ultimate beneficial owner and control person.