/GetAccountsDetail or /GetAccountsDetailAsync repeatedly, Flinks sends a POST callback to your endpoint with the JSON result as soon as data extraction is complete.
Webhook types
Flinks supports the following types of webhooks:The KYC webhook is delivered as soon as the customer’s personal information is processed, without waiting for full account data. This is useful for time-sensitive identity verification. You will still receive a separate
GetAccountsDetail webhook once all data is processed.Enabling webhooks
To enable webhooks on your instance, open a ticket via the Flinks Support Portal with the following information:- Your webhook URL.
- The instance (environment) where the webhook should be configured.
- Flinks configures your instance to send callbacks to your URL.
Endpoint requirements
Your webhook endpoint must:- Accept HTTP POST requests
- Respond with an HTTP 200 status code to confirm receipt
- Have a valid SSL certificate (self-signed certificates are not accepted)
Delivery failure handling
Custom tags in webhooks
If you pass aTag parameter in the Flinks Connect iframe URL, the tag value is included in the webhook payload. This allows you to correlate webhook data with your internal records.
Reconciling user accounts
You can embed your internal UserId as a custom tag during the Flinks connection flow. When the webhook payload is delivered, it includes both this tag and the FlinksLoginId, making it straightforward to map your internal user records to their corresponding Flinks connection without any additional lookups.