For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
KYC Reliance using API lets you submit KYC your platform has already completed (via Sumsub, Onfido, or any provider), so end-users don’t repeat KYC for Transak. Transak validates the submission and relies on your KYC instead of re-running it, cutting friction and drop-off while meeting Transak’s compliance requirements.
EEA users: send the sourceOfIncome and additionalDetails objects in the Identity Details API, and do not send driving licences. Send the consent object only when Get Additional Requirements returns type: CONSENT for the user. See MiCA Changes for EEA Users.
Our Solution
Provider agnostic
Partners are not limited to a single KYC vendor. They can collect KYC data using providers like Sumsub, Onfido, and map that data via Transak’s KYC Reliance using API.
Aggregated payloads
All required data such as personal details, address, purpose of usage, and country-specific ID documents can be submitted together in a single API call, instead of multiple calls.
"Buying/selling crypto for investments", "Buying NFTs", "Buying crypto to use a web3 protocol"
TIN Details (optional)
key
description
documentType*
[US_SSN]
documentNumber*
Identification number
Use the same allowed purposeList values as existing API contract.
Country-specific tax ID details are required only when applicable, for example US_SSN for the United States.
Either both or any other can be submitted for selfie and liveness to complete the KYC submission.
Supported Formats
Media type
Accepted formats
Selfie Image (document ID front/back, selfie)
JPEGPNGWEBP
liveness Video
MP4
Supported Document IDs
idType
Accepted documents
PASSPORT
passport
DRIVING_LICENSE
Driving Licence
ID_CARD
National Identity Card
PROOF_OF_RESIDENCE
Bank Statement, Resident Permit, Utility Bill, Payslip
VISA
visa
UNKNOWN
Any other value not listed above
Field Validation
Personal & Address Fields
Field
Constraint
firstName / lastName
1–50 characters, counted after conversion (ß counts as ss). Latin letters, including accented letters (for example é, ø, ł, ß), which are converted to plain letters. Cannot contain ^ ! # $ % * = < > ; { } " or a backslash; typographic double quotes “ ” count as ”. Letters from other scripts (Cyrillic, Greek, Arabic, Chinese and so on), symbols, ° and № are not accepted.
addressLine1
3–200 characters, with at least one letter. Latin letters, including accented letters, which are converted to plain letters, № becomes No, and º and ° become o. Letters from other scripts and symbols are not accepted.
addressLine2
Optional Up to 200 characters. If sent, it must contain at least one letter (Apt 12 is accepted, 12 alone is not). Same character rules as addressLine1.
city
2 to 50 characters, with at least one letter.
state
2 to 100 characters, with at least one letter.
postCode
Must be a valid postal code for the given countryCode
dob
ISO 8601 date (YYYY-MM-DD). User must be ≥ 18 and < 150 years old
mobileNumber
Must be a valid international phone number (E.164 format, e.g. +33791112345)
Transak keeps the name and address exactly as sent and uses the converted form for verification (for example Søren Ólafsdóttir is verified as Soren Olafsdottir). Invisible characters and extra spacing are removed, and typographic quotes and dashes are converted to their plain form before the value is checked.
The KYC Reliance API must be called only from the partner’s backend and subjected to the whitelisting of partner IP addresses. Direct API calls from the frontend apps are not supported.
FCA Flow (For UK Users) not supported
Partners can integrate the APIs to submit the FCA requirements. See the How to Submit FCA Requirements guide for step-by-step instructions.