You have the option to initiate a new onboarding request, either by using preset data or by starting from scratch without any data.
The application of preset data is particularly beneficial in situations where comprehensive personal information is necessary to complete a request. For instance, if you already possess a user's data, you can eliminate the need for them to fill out a form. Conversely, it is important to ensure that you can identify a specific individual, which allows you to implement necessary process checks effectively.
Starting without any data can result in potential identification for any user who receives the link. In certain workflows, you also require users to complete a form, which provides Namirial Onboarding with all the necessary information to facilitate a comprehensive onboarding process.
For and example of new request creation with preset data, please refer to this page:
Otherwise, if you want to start from scratch, please refer to this page:
The idempotency key
An idempotency key is a unique identifier included in a request to ensure that even if the request is sent multiple times, it will only be processed once. Imagine you’re ordering something online and accidentally click the “Submit Order” button twice. Without an idempotency key, the system might process your order twice, charging you twice and sending you two of the same item. With an idempotency key, the system recognizes that the second request is a duplicate and ignores it, preventing any unwanted duplicates.
In the context of Namirial Onboarding, when you create a new request, you can include an idempotency key. This ensures that if the request is accidentally sent multiple times due to network issues or user error, the system will only process it once. For example, if you send a request to start a new onboarding process with the idempotency key 123456789, the system will process this request and start the onboarding process. If the same request is sent again with the same idempotency key, the system will see that it has already processed a request with that key and will ignore the duplicate request.
In summary, an idempotency key acts as a safeguard to ensure your requests are processed correctly and only once, even if they are accidentally sent multiple times. In Namirial Onboarding, this feature is especially beneficial as it prevents the creation of duplicate requests. Duplicate requests can lead to unnecessary costs and cause confusion regarding the onboarding process that has already been completed.