Zynk
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Customers & Identity
  • Transformer - Cross Border Transfer
    • Overview
    • Customers & Identity
      • Entities/Customers
      • About KYC/KYB
      • RFI Scenarios for Customers
      • Identity Rejection Reasons
    • Accounts & Wallets
      • External Accounts(To be deprecated soon)
      • Fetch Requirements for External Accounts V2
      • External Accounts V2
      • Funding Accounts
      • About Plaid Integration
    • Transfers
      • Counterparty Risk details
      • Addition transfer requirements
      • Transfer in Action
      • Limits and Minimums
      • Fee details
    • Miscellaneous
      • Bank Codes
      • Supported chains and currencies
      • Partner payments signature generation
      • Reserves requirements
      • Partner Payments
      • Status updates - Webhooks
  • Transporter - Automated Liquidity Manager
    • Overview
    • Visibility Protocol
    • Instant liquidity process - How it works
    • Status updates - Webhooks
  • Teleport - Pay-In Accounts
    • Overview
    • About Teleport routes
  • Warp - Pay-Outs
    • Overview
  • Continuum - Wallet Infrastructure
    • Overview
    • Authentication
    • Continuum APIs
    • Transactions on Continuum
    • Details on generating signatures
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Customers & Identity

Identity Rejection Reasons

USD-1
USD-2
AED
The KYC process may also includes,
Database Verification (validates PII against voter, telco, utility or credit databases)
AML Screening, including
PEP / HIO report
Watchlist / Sanctions report
Adverse Media Report
The following failures will cause the customer to be rejected. The same will be passed to partners in the webhook updates.
Error CodeReason
id_check_failureThe document failed verification analysis. This could occur due to blurry photos, obscured data, missing data, or other compliance check failures.
duplicate_person_check_failureThe customer has already signed up for the service via your application.
id_quality_check_failureThe image of the document is too blurry to extract information or perform face recognition.
id_barcode_check_failureThe barcode on the back of the document could not be properly read.
id_expiration_check_failureThe ID is expired.
id_double_side_check_failureThe ID is double sided, but only one side of the ID was provided.
id_type_allowed_check_failureThe document is not a supported document. Supported documents include Driver's License, National ID, Passport, Passport Card, PR Card, Visa, or Work Permit.
id_country_allowed_check_failureThe document is not from a supported country. For example, U.S. customers must use a U.S. form of ID.
selfie_check_failureThe selfie images are too blurry, not the correct facial angles, too light, too dark, or cannot be matched to the photo on the provided government ID.
database_check_failureA match for the customer’s name, address, date of birth, or SSN cannot be found in any of the government databases. Databases searched include Telco, Credit, Voter, and Utility database.
pep_check_failureIf the individual is a known Politically Exposed Person (PEP), they may show up on this AML report.
media_check_failureIf the individual shows up on Adverse Media, they may appear in this AML report.
watchlist_check_failureIf the individual is on a known government or international watchlist or sanctions list, they may appear in this report.
Additional documents such as Bank Statement from last 90 days and Utility or Telephone Bill can be requested if an issue occurs with validating the Date of Birth (DoB) or address.
Modified at 2025-08-13 16:13:04
Previous
RFI Scenarios for Customers
Next
External Accounts(To be deprecated soon)
Built with