KYCGlossary

Getting User Consents

This guide provides an overview of how to create and manage entities using the FrankieOne KYC v2 API.

Before proceeding with data verification checks, obtaining consent is essential and varies based on the verification type. While general consent encompasses standard verifications against government databases, it may not include credit checks and document validations. Consult with your AML team and the FrankieOne team to determine what consent flags you need to supply.

ConsentDescription
GENERALThis indicates that the entity has given consent for their name, address, or DoB to be checked against our various databases and external services.
DOCSThis indicates that the entity has given consent to have their identity documents checked against official sources.
CREDITHEADERThis indicates that the entity has given permission to have their details checked against a credit bureau service. If this check fails, you must inform the user that the check failed and put them in touch with the bureau directly so that they may update their details as necessary. This isn’t normally available by default, so please see your account manager about making this service available.
UNDER18This indicates that the entity is under the age of 18 and a parent or guardian has provided consent. This is a special case of the consent.general flag (see above). consent.docs would still be required to check their passports or drivers license.
PAYROLLThis consent is used to allow access to verifying an identity using payroll data.
INSURANCEThis consent is used to allow access to verifying an identity using workcover data.
SUPERANNUATIONThis consent is used to allow access to verifying an identity using superannuation data.