KYCImplementation Guide

Country-Specific Documents

How to handle country-specific documents in the FrankieOne KYC v2 API.

Documents Overview

Country-specific documents are crucial for KYC compliance, especially when onboarding international entities. This guide explains how to manage country-specific documents using the FrankieOne KYC v2 API.

Supported Document Types (v2)

The FrankieOne KYC v2 API supports a variety of document types across different countries. Below is a list of the supported document types, their codes, and the countries in which they are accepted.

Document TypeDocument CodeSupported Countries
Birth CertificateBIRTH_CERTAUS, NZL
Centrelink CardCENTRELINKAUS
Citizenship CertificateCITIZENSHIPAUS
Immigration CardIMMIGRATION_CARDAUS
Drivers LicenseDRIVERS_LICENSEAUS, IND, NGA, NZL
Marriage CertificateMARRIAGE_CERTAUS
Name Change CertificateNAME_CHANGEAUS
National Health IDNATIONAL_HEALTH_IDAUS
National ID CardNATIONAL_IDAUS, BRA, CAN, CHL, CHN, COL, CZE, DNK, FIN, GHA, HKG, IND, JOR, KEN, LUX, MYS, MEX, NGA, PHL, POL, ROU, ZAF, ESP, SWE, THA, USA
PassportPASSPORTAUS, CHN, IND, KEN, NZL, PHL, RUS, International
Tax ID*TAX_IDCHL, ITA, JPN, MEX, NGA, PRT, RUS, ESP, TUR, International

This section provides a list of common abbreviations used for various identification documents across different countries. These abbreviations are often used in KYC processes and can help streamline document handling.

  • Aadhar: Unique Identification Number (India)
  • ASIC/MSIC: Aviation/Maritime Security Identification Card (Australia)
  • BVN: Bank Verification Number (Nigeria)
  • CAC: Corporate Affairs Commission (Nigeria)
  • CNPJ: Cadastro Nacional de Pessoas Jurídicas (Brazil)
  • CPF: Cadastro de Pessoas Físicas (Brazil)
  • CPIN: Colombian Personal Identification Number (Colombia)
  • CNP: Cod Numeric Personal (Romania)
  • CURP: Clave Única de Registro de Población (Mexico)
  • DNI: Documento Nacional de Identidad (Spain)
  • EPIC: Electors Photo Identity Card (India)
  • HKID: Hong Kong Identification Number (Hong Kong)
  • ImmiCard: Immigration Card (Australia)
  • NID: National Identification Number (Czech Republic)
  • NIE: Número de Identificación de Extranjero (Spain)
  • NIF: Número de Identificación Fiscal (Spain)
  • NIK: Nomor Induk Kependudukan (Indonesia)
  • NRIC: National Registration Identity Card (Malaysia)
  • PAN: Permanent Account Number (India)
  • PCN: PhilSys Card Number (Philippines)
  • PESEL: Powszechny Elektroniczny System Ewidencji Ludności (Poland)
  • PIN: Personal Identification Number (Sweden)
  • RFC: Registro Federal de Contribuyentes (Mexico)
  • RUT: Rol Único Tributario (Chile)
  • RUN: Rol Único Nacional (Chile)
  • SIN: Social Insurance Number (Canada)
  • SSN: Social Security Number (USA)
  • SSNIT: Social Security and National Insurance Trust (Ghana)
  • TIN: Tax Identification Number (Nigeria, Turkey)

For KYC checks, all tax identification documents must be submitted as document type NATIONAL_ID in the FrankieOne KYC v2 API to verify entity details.

Important Notes

The document codes above are used in the FrankieOne KYC v2 API. Ensure you use the correct code for each document type when making API requests.

  • Not all document types are available in every country. Refer to the specific country documentation for details.
  • Not all document types are supported in the FrankieOne Portal. If you need to use a document type not listed here, please contact FrankieOne support.

Requirements & Additional Fields for ID Documents

While FrankieOne supports a wide range of document types, some require more than the standard fields described in the API reference. In these cases, provide extra information using the supplementaryData object when submitting documents.

  • Standard Fields: Most documents can be submitted using the core fields described in the API reference.
  • Supplementary Data: For documents that require additional details (such as card numbers, issue dates, or authority names), include these in the supplementaryData object of your API request.

Refer to the following pages for country-specific guidance on required fields and valid values for different document types. These resources outline exactly what information is needed for each supported document, ensuring your submissions are complete and compliant.

Best Practices for Handling Documents

When integrating country-specific documents with the FrankieOne KYC v2 API, follow these guidelines to ensure a smooth and compliant process:

  • Understand Local Requirements: Each country may require different document types for KYC. Review the documentation for the countries you support.
  • Document Upload: Use the API to upload documents in the correct format and size. Validate files before submission to reduce errors.
  • Validation & Error Handling: Use API endpoints to validate documents. Handle errors gracefully by interpreting API error messages and providing clear feedback to users.
  • Compliance & Security: Store documents securely and restrict access to authorized personnel. Stay up to date with local data protection and KYC regulations.
  • Testing & Monitoring: Test your integration thoroughly before going live. Monitor document handling workflows to quickly identify and resolve issues.
  • User Experience: Make the upload process user-friendly. Offer clear instructions and support to help users provide the correct documents.
  • Audit & Documentation: Maintain an audit trail of uploads and validations for compliance. Keep your internal documentation current with any process changes.
  • Continuous Improvement: Gather feedback from users and your team to refine your document handling process. Stay informed about regulatory updates and adjust your workflow as needed.
  • Support & Training: Train your team on KYC requirements and API usage. Contact FrankieOne support if you encounter issues or need clarification.

By following these practices, you can streamline KYC verification and maintain compliance across different jurisdictions.