Overview

KYC Sharing allows merchants to independently perform KYC verification and submit the user's KYC information to Saber for reference purposes. Saber does not verify the submitted information but stores it for compliance and record-keeping.

Steps for KYC Sharing

1. Create the User:

   • Before KYC information can be shared, the user must be created using the create user API. Read more about the API here.

2. Submit KYC Information:

   • Use the KYC Sharing API to provide the user's documents and details. Read more about the API here.
     • Step 1: Share KYC PII Data including the following mandatory fields:
       • Legal Name
       • Proof of Address (Document Number)
       • Proof of Identity (Document Number)
       • Country ISO
     • Step 2: Share KYC supporting document files
   • Ensure the documents meet the required specifications (see below).

3. Store for Reference:

   • Saber retains the KYC information for future reference but does not perform the verification process.

4. Add a Bank Account (For Indian Users):

   • Once KYC is approved, use the Update Bank API to add a bank account for Indian users. Read more about the API here.
   • This step is only required for Indian users and does not apply to non-Indian users.

Note:

• KYC is marked as approved post KYC PII data sharing.
• The KYC Data should be unique for each user.
• Please ensure that the KYC Data is correct and follows the standard regex format.
• Supporting files can be shared async as they are required for compliance reporting.

Document Requirements

To ensure smooth processing, documents submitted through the KYC Sharing API must conform to the following specifications:

1. Supported File Formats:

   • .pdf, .jpg, .png, .xml, .zip.

2. Maximum File Size:

   • Less than 2 MB.

Key APIs for KYC Sharing

Important Notes

• Merchant Responsibility:

  • KYC verification is assumed to be complete before submitting the information to Saber.
  • Only verified users can perform operations like on-ramp and off-ramp transactions. Once the documents are shared, a user is assumed to be approved.

• Bank Account for Indian Users:

  • Adding a bank account is mandatory for Indian users after KYC approval.
  • This step must be performed manually through the API unless the KYC SDK is used.

• Compliance:

  • Ensure that submitted documents adhere to the specified format and size requirements to avoid errors.

KYC Sharing provides a streamlined approach for merchants who wish to manage KYC verification independently while leveraging Saber’s platform for record-keeping and compliance.