Validate identity data against national and global databases using 1x1 and 2x2 matching with a waterfall multi-provider approach.
The ISO 3166-1 alpha-3 country code of the issuing state. Determines which validation sources are used.
ARG, BOL, BRA, CHL, COL, CRI, DOM, ECU, ESP, GTM, HND, MEX, PAN, PER, PRY, SLV, URY, VEN The type of matching to perform: '1x1' for single-database matching or '2x2' for dual-database matching.
one_by_one, two_by_two Universal identification number field. Automatically maps to the correct country-specific field: ARG→document_number (DNI), BOL→document_number (CI), BRA→tax_number (CPF, 11 digits), CHL→personal_number (RUT), COL→personal_number (Cédula), CRI→personal_number (Cédula), DOM→personal_number (Cédula, 11 digits), ECU→personal_number (Cédula, 10 digits), ESP→personal_number (DNI/NIE), GTM→document_number (DPI), HND→document_number (DNI), MEX→personal_number (CURP, 18 chars), PAN→document_number (Cédula), PER→personal_number (DNI, 8 digits), PRY→document_number (CI), SLV→document_number (DUI), URY→personal_number (CI), VEN→document_number (Cédula).
The individual's first name. Might be required for some countries and matching types.
The individual's last name. Might be required for some countries and matching types.
The individual's date of birth in YYYY-m-d format. Might be required for some countries and matching types. Example: 1990-01-01.
The type of document being validated. P = Passport, DL = Driver License, ID = National ID, RP = Residence Permit. Optional field that may help with validation in some countries.
P, DL, ID, RP The document's expiration date in YYYY-MM-DD format. Required for ESP (Spain) database validation. Example: 2030-01-15.
The individual's nationality, expressed as an ISO 3166-1 alpha-3 country code. Might be required for some countries and matching types.
The individual's residential address. Used in specific jurisdictions where address validation is supported. Might be required for some countries and matching types.
Whether to save this API request. If true, then it will appear on the Manual Checks section in the Business Console.
A unique identifier for the vendor or user, such as a UUID or email. This field enables proper session tracking and user data aggregation across multiple verification sessions.