Onboard Users

After creating the configuration and finalizing all relevant settings such as Workflow and Text, you are now prepared to copy and distribute the URL to your end-users — whether via email or by integrating it into your website.

Onboarding Identifier

To streamline the identification of an onboarding process linked to No-code KYC, you can supply a randomly generated string known as a transaction nonce. This transaction nonce uniquely identifies an onboarding process and is included in the SDK result. The transaction nonce plays a crucial role in establishing the correlation between the onboarding request and the SDK result response. Subsequently, you can associate the transaction nonce within your system with a specific session or user profile.

You have the flexibility to define the transaction nonce by incorporating an additional query parameter labeled as "tn" in the onboarding URL. This query parameter has the capacity to accommodate any random string of up to 64 characters in length.

It is essential to emphasize that the transaction nonce will be securely stored on our server to prevent its reuse.

Important notes

• If you're using the onboarding URL in offline mode such as sending it via email, where the process isn't triggered in real-time, we highly recommend utilizing a URL that initially directs to your API. This URL can carry your unique identification, and subsequently, redirect the end user to the onboarding URL with a generated transaction nonce. This approach enables you to validate the session before directing the end user to the onboarding process and generating the corresponding transaction nonce.

• The "Transaction Nonce" denoted as "tn" should be unique for each transaction, and it is the responsibility of the customer to ensure adherence to this requirement. Failure to do so may result in an error being returned from our side when the end-user accesses the onboarding URL.