Overview
The BGLiD Frequently Asked Questions (FAQs) provides clear answers to common queries about setup, functionality, and troubleshooting. It is designed to help users quickly find practical solutions, better understand key features, and make the most of BGLiD.
Note: For the full list of supported and unsupported ID documents, see Supported Identification – BGLiD.
- GOV ID - If the ID provided does not match the details held by the issuer of the ID.
- PEP/Sanctions - Increases when there is a Politically Exposed Person (PEP), Sanctions, or AML evidence related to the contact.
The issuer refers to which government body issued the identification, for example:
- Passports = Department of Foreign Affairs (any passport that is registered)
- Drivers Licence = State road authorities
The currently accepted ID's are:
- AU passport
- AU drivers licence
- Passports of other countries, if the contact holds an eligible visa subclass registered with the Department of Home Affairs, not all visa types qualify (see Supported Identification – BGLiD for the full list of supported and unsupported visa categories)
- Medicare Card (this is only available if two sources are selected)
The following ID's are accepted for other Jurisdictions:
- NZ drivers licence - New Zealand
- National Registration Identity Card (NRIC) - Singapore
This article will be updated as support for new identification is added. For the complete, current list – including unsupported document types – see Supported Identification – BGLiD.
Requesting identification through BGLiD does not cause this ID to flow through to CAS 360 unless specifically requested. Otherwise, the only identification details stored within CAS 360 are manually entered details.
- Once an ID verification has been completed, these manually entered details can be removed.
If the option to Request to store ID is toggled to YES, ID information can be imported given that the relevant individual provides consent.
- For information on this process, see Request to store ID Documents with BGLiD.
FrankieOne and stored ID data
Please note that FrankieOne does store data that was successfully verified for 1 month.
After this period, that data is removed.
The information relating to what causes ID checks to fail is not provided. FrankieOne only provides the verification document stating the results.
AML/PEP/Sanction information is public and will be displayed.
After 21 days, if the verification request has not been completed, the verification link will expire. A notification will appear in CAS 360 notifying the user that the verification link is now invalid.
While the request is outstanding, reminder emails are sent to the recipient automatically. The frequency is configurable in the request settings, between every 1 day and every 7 days.
Resending a request to a recipient who has not yet completed verification does not incur an additional charge. This applies whether you're resending before the recipient has acted, or reissuing a new 21-day link after the original has expired.
A charge applies only if a verification attempt has already been completed and a subsequent attempt then fails. Resending avoids a charge solely when the original request remains incomplete.
BGLiD uses email-only 2FA. SMS-based 2FA is not available for BGLiD in CAS 360. Confirm the contact has access to the email address on their record before sending a request, as they'll need it for both the link and the 2FA step.
Why is my ID check not working? This can be due to the photo of the ID not being clear or the expiry date of the licence being too close to the date of the identification.