KYC sharing and verification with Mercuryo

Mercuryo’s KYC (Know Your Customer) sharing system streamlines user identity verification by integrating with partners and third-party providers like SumSub. This process ensures compliance with regulatory requirements, while minimizing repeated verification steps for users.

When users complete KYC directly within Mercuryo’s widget or wallet, the verification typically includes:

• Identity verification via passport, ID card, or driver’s license.
• Liveness verification (selfie or video).
• Address confirmation (required for IBAN and card features; for cards, address is entered without document upload).
• Phone number verification (required for IBAN feature).

A Share token can only be used once per applicant due to SumSub’s architecture. Partners must ensure applicant documents are up to date before sharing.

Access Tokens and API Endpoints

Mercuryo provides several API endpoints for managing KYC status and access:

• Access Tokens
  • Used to authorize KYC sessions and redirect users to complete verification.
  • Examples include GET /b2b/kyc/access-token and GET /user22/kyc-access-token.
• KYC Status Checks:
  • Use GET /b2b/user/kyc-status to check if a user’s KYC is complete, under review, failed, or incomplete.
  • Statuses include:
    • complete: KYC passed successfully.
    • under_review: Documents are being reviewed.
    • failed_attempt: First verification attempt failed.
    • failed: Verification failed; contact support.
• Document Retrieval:
  • Use GET /b2b/kyc/documents to obtain details of uploaded KYC documents.

Share-Token for KYC Data Sharing

To avoid duplicate KYC verifications, Mercuryo uses a share-token mechanism to transfer verified user data from partners to Mercuryo:

• Generating share-token:
  • Partners generate a share-token via the SumSub API, specifying the applicant ID and Mercuryo as the client.
• Using share-token:
  • In the widget URL to pre-fill or skip KYC steps.
  • Via API calls like POST /b2b/user/kyc-share-token to submit verified user data.
• Important notes:
  • Share-token can only be used once per applicant due to SumSub’s architecture.
  • Partners must ensure applicant documents are up to date before sharing.

Uploading KYC documents via API

Partners can also upload or update KYC documents through API endpoints:

• POST /b2b/user/kyc-documents to submit identity and address verification documents.
• GET /b2b/kyc/documents to review submitted documents.

For IBAN features, address proof documents such as bank statements, utility bills, or rental agreements may be required in addition to identity documents.

Special considerations

• US residents:  KYC for US users requires additional processing through ZeroHash. If verification fails, Mercuryo handles the case accordingly.
• KYC renewal:  KYC status can expire, requiring users to re-verify.
• Error handling:  Common errors include invalid parameters or failed verification attempts. Support is available for resolution.

Benefits for partners

• Eliminate duplicate KYC verifications through share-token sharing.
• Provide clear API methods to check and manage KYC status.
• Ensure regulatory compliance while improving user experience.

• Support of comprehensive document management for identity and address verification.

   

For detailed technical implementation, partners should consult Mercuryo’s API documentation and coordinate with their integration manager.