Submit KYC

Our KYC API simplifies the user verification process, increasing your conversion rate. We adhere to the highest global standards for AML and KYC and gather necessary documents from our customer's users using a risk-based approach.

Using our KYC endpoints, you can verify customers during sign-up or at their convenience. Once verified, they can make or receive payments without any extra steps during checkout.

This section is a guide for API users to retrieve a list of documents that have to be uploaded for a specified individual or company. It is mandatory for the sender of funds to be KYCed with relevant documents.

1. Submit KYC using TransFi API: You can directly KYC your users using TransFi API. We use Sumsub as our KYC provider and with the /kyc/standard endpoint you will get a URL to KYC your users directly with us.
2. Share KYC through Sumsub Agreement: TransFi and its clients can enter into a tripartite agreement with Sumsub and enable direct KYC sharing based on a common token. This endpoint facilitates seamless integration for sharing KYC.
3. Share KYC from other KYC Partner: If you do not use Sumsub as your KYC provider, fret not! You can pass the required KYC information directly to us and we will take care of the rest.
4. Additional KYC Documents: For higher transactional volumes after certain volumes are already paid in or out, it is necessary to collect additional documents and information on the sender of funds. Those requests can be fulfilled by sharing directly using this endpoint.

Submit KYC using TransFi API:

Below are the user experience for the direct KYC submission on TransFi. The specific documents required depends on the transaction volume and the jurisdiction of the sender/recepient of funds.

Share KYC through Sumsub Agreement:

With Reusable KYC, the user details can be shared from our customer to TransFi to simplify and speed up verification for their users that have already passed it.

Such an approach minimizes onboarding drop-offs and enables your users to avoid repeat verification.

How it works:

Assume User A passed user verification in Customer (Service X) and is now registering at TransFi (Service Y). If Customer agrees to share information about User A with TransFi, it can be done as follows:

1. Customer generates a share token and passes it to TransFi.
2. TransFi calls the API method with the received share token and obtains information on user A with all its data and documents.

Customer generate share token using sumsub api

curl --request POST 'https://api.sumsub.com/resources/accessTokens/- /shareToken?applicantId={{sumsubApplicantId}}&forClientId=transfi.com_123'

The value for the paramsumsubApplicantId can be obtained from Sumsub platform and forClientId will be shared by TransFi on the integration phase.

Shared token on the response:

{
	"token": "_act-b8ebfb63-5f24-4b89-9c08-000000000000",
	"forClientId": " transfi.com_123" 
}

Making API request to share the KYC:

curl --request POST \
     --url https://sandbox-api.transfi.com/v2/kyc/share/same-vendor \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "token": "_act-b8ebfb63-5f24-4b89-9c08-000000000000",
  "email": "[email protected]",
  "name": "john doe"
}
'