• eKYC Platform
    About TrustVision
TrustVision API Documentation

eKYC Platform Integration Guidelines

Prerequisites

Our client will be provided following credentials to initialize a unique token for an user flow:

I. Generate token to send to eKYC Platform

Reference Authencation mechanism

II. Integrate with your platform

Two integration modes are available. Choose based on your use case, then follow the guide for your platform.

Pre-built full eKYC journeysFlexible ID & Selfie Capturing

Full journey managed by TrustVision. Low-code.

Example flow_id values:

id_selfie

selfie_id

id_nfc_selfie

qr_nfc_selfie

id_form_selfie

vision_score_sanity_liveness

vision_score_only

… and more

Built-in. No provisioning needed.

💡 Flexible flows — Contact TrustVision to receive your custom flow_id before integrating. Once you have it, use it exactly the same way as the built-in flow_id values shown below.

II.1 Web or WebView

Use EncodedBase64Token generated from step I and concatenate to provided URL

Final URL:

Optional query parameters

You can append the following optional query parameters to the URL to control which eKYC journey runs, the allowed ID card types, and the UI language. Every parameter is optional — omit one to fall back to the default configured for your token.

ParameterTypeRequiredDescription
flow_idstringNoSelects which eKYC journey to run. Built-in flows include id_selfie (ID → Selfie → Matching) and selfie_id (Selfie → ID → Matching). Flexible/custom flows — such as ID-only, Selfie-only, or ID → Form → Selfie — are also supported. The exact flow_id for each flow is provisioned per client by TrustVision. If omitted, the default flow configured for your token is used.
card_typesstringNoComma-separated list of allowed ID card types, e.g. vn.national_id,vn.passport. Restricts which ID documents the user can submit. If omitted, all card types configured for your account are allowed.
languagestringNoUI language for the eKYC journey. One of vi, en, or es-mx. If omitted, the lender's default language is used.

Note: The language query parameter corresponds to the lang parameter of the Platform Initialization API.

Examples

Built-in flow (ID → Selfie) with Vietnamese UI:

https://ekyc-platform-vn-staging.trustingsocial.com/lu/[EncodedBase64Token]?flow_id=id_selfie&language=vi

Flexible flow (ID only), restricted to the national ID card, with English UI:

https://ekyc-platform-vn-staging.trustingsocial.com/lu/[EncodedBase64Token]?flow_id=[YOUR_ID_ONLY_FLOW_ID]&card_types=vn.national_id&language=en

Replace [YOUR_ID_ONLY_FLOW_ID] with the flow ID provisioned for you by TrustVision.

II.2 Android

II.2.1 eKYC Platform

Refer to this for more details.

II.2.2 eKYC Platform Webview

Refer to this for more details.

II.3 iOS

II.3.1 eKYC Platform

Refer to this for more details.

II.3.2 eKYC Platform Webview

Refer to this for more details.

II.4 Flutter

II.5 React Native

III. How client will get the result

III.1 Use callback URL

  • Use-case: TrustingSocial's Backend call to Client's Backend.
  • The result will be sent to the client's callback URL in JSON format.
  • The client should verify the signature that was signed using the TS RSA key.

III.2 Call HTTP Request

  • Use-case: Client's Backend call to TrustingSocial's Backend.
  • The client use the API Application Detail to get the user flow result.

III.3 Redirect URL

  • Use-case: TrustingSocial's Website redirect to Client's Website.
  • After the user finishes, they can be redirected to a URL you provide. Your backend can then call our API to retrieve the results. See details III.2