(WIP) Migration to Kraken
This page describes step-by-step how a client can migrate co to a new version.
1. Credentials
You have to request our OPS for the following credentials:
Client ID
API Key
Webhook Secret Key
Link
2. Update link
Links are similar to the previous version:
The new link did not contain a redirect URI, and it's more readable:
The link is the same for redirection or an iframe interaction.
3. Redirection back behavior
When a user is redirected back to your site, or KYC ends in an iframe. You will receive a one-time token, this one-time token needs to be exchanged for user-id: (Endpoints are secured with Bearer API key).
https://kraken.fractal.id/api-doc#/PublicKyc/PublicKycController_getSession
The user ID should be stored next to your user; later, you can use it to receive a KYC status or user data:
https://kraken.fractal.id/api-doc#/PublicKyc/PublicKycController_getData
The structure has changed, and if you want to get files, you should use:
https://kraken.fractal.id/api-doc#/PublicKyc/PublicKycController_getFile
4. Webhooks
Webhooks are (almost) the same, you would receive a message in your webhook endpoint like this:
To verify the authenticity of a webhook request, validate the signature using the X-Fractal-Signature header. Example implementation in JavaScript:
Last updated
Was this helpful?