✅ Rapid Verification Methods

Rapid supports four flexible verification options to help you meet compliance requirements and onboard users globally:

• Built-In Verification (US & Non-US)
• KYC Reliance
• Passing External KYC Data
• Sumsub Token Sharing

🔒 Rapid's Built-In Verification

🇺🇸 Verifying US Withdrawers

Use the Register User endpoint with KycUsRequestBody:

• Inputs: Email, name, address, country, date of birth, last 4 digits of SSN

• If verification passes instantly → ✅ you're done.

• If verification fails:

  • API returns 451 with a verificationLink
  • Withdrawer's status is set to pending
  • Redirect the user to the verificationLink to complete selfie + full SSN submission
  • They’ll be sent back to your redirectLink after completing verification

🌎 Verifying Non-US Withdrawers

Use the same Register User endpoint with KycDocVRequestBody:

• Inputs: Email and country (minimum)
• Always returns a 451 requiring further verification
• User is sent to the verificationLink to upload a photo ID and take a selfie
• After success, Rapid redirects them to your redirectLink

💡

Using Rapid's prebuilt UI? You don’t need to handle these verification redirects — Rapid manages them for you.

🤝 KYC Reliance

For merchants with their own KYC provider (not Sumsub) who want to share verified user data with Rapid.

Steps to Enable:

1. Request Rapid's KYC Reliance Questionnaire

2. Submit for Compliance Review

3. Enable Sandbox Testing

   • Rapid enables the KYC attestation feature in your sandbox

4. Integrate Attested Endpoint

   • After approval, call the KYC attested endpoint in production

⚠️

If not approved, fallback to Passing External KYC Data

📤 Passing External KYC Data

Allows you to pass verified user information to Rapid from your own KYC provider (non-Sumsub).

Requirements:

• Call the Register User via Document endpoint
• Required fields: email, country, front and back of photo ID

Behavior:

• Approvely attempts to reverify submitted data

• If re-verification fails:

  • Returns 451
  • User uploads ID + selfie via verificationLink
  • On success, they’re redirected to your redirectLink

🔁

If using Rapid's prebuilt UI, call this endpoint before rendering so a verification record exists.

🔄 Sumsub Token Sharing with Rapid

For merchants with their own Sumsub account

Allows you to reuse KYC data already collected through Sumsub by setting up a tri-party agreement.

How to Get Started:

1. Contact Approvely with your Sumsub client ID

2. Get tri-party data-sharing agreement signed via Sumsub

3. After approval:

   • Call Sumsub’s Generate Share Token
   • Call Rapid's Register User Via Share Token
   • Use Rapid's prebuilt UI (e.g. CoinflowWithdraw) after registration

🧠

Rapid will provide its Sumsub client ID upon request.

📊 Verification Method Comparison