KYC verification for public companies (AUS)
This page contains only params relevant for the specific example. For a complete list of params for this API call visit this page.
API response vs Webhook response
Processing of the entity verifications is asynchronous. This means that when you submit an entity through the API, in most cases you will receive a default "pending" response to the call itself. When the verification status changes (e.g. to "verified"), you will receive a verification status update webhook. The final verification response time can range from a few seconds up to 48 hours depending on 3rd party register access and availability.
Note: Aside from the API response, you will also receive a "pending" webhook at the moment you submit the entity. Because of this behaviour, in most cases you can use the API response as an "error/validation indicator", ignore the non-error API responses and rely on the webhooks for status updates.
In the test environment, you can trigger (fake) a successful verification if the name of the entity you are trying to verify starts with "Pass". You can find all test values here.