Start the verification flow in your browser.Free Download Starus File Recovery Commercial / Office / Home full version standalone offline installer for Windows is the quickest file recovery tool on the market. To try out the end-user facing verification flow, navigate to Veriff Demo - this will Generating the value may vary depending on the programming language used, see the code examples To generate the value you need to generate a keyed hash value using your shared secret key with the HMAC-SHA256 function. X-HMAC-SIGNATURE is a special header which value is a signature generated using HMAC method. It is based on the shared secret key that is known only by you and Veriff. The X-HMAC-SIGNATURE guarantees to us, that API calls are initiated by you. Signing requests with the X-HMAC-SIGNATURE Manual: the Verifications page in Station displays sessions' details including decisions made There are 3 options to fetch decisions for a verification session: It is important to note, that the callbackURLĭoes not contain any decision or verification information yet. Is not specified for the session, the end-user will be redirected to Integration's default callbackURL, which can be Once the end-user completes the verification flow, they will be redirected to the callbackURL.
IfĪbsolutely needed, you can set the length to max value: 4096 characters. Note that you should always use the variable max length type for the sessionToken and not define it. The sessionToken is a JSON web token that consists of HS256 encrypted session ID and session creation timestamp. The sessionID should be saved on your end - you can tie back the webhook responses to your end-user record that way. The URL of the verification session is where end-user should be redirected on web.
How to find your API key and the shared secret key.
0 kommentar(er)
