Documents allow you to store structured document data against Entities in BNDRY. Common use cases include collecting and verifying proof of identity during customer onboarding, storing documents gathered as part of KYC or KYB checks, and maintaining an up-to-date record of customer identification for compliance purposes.
Documents are stored against an Entity and are accessible from the Entity Profile. Documents can be created and managed directly in BNDRY or via the API.
Documents store structured identity data – typed fields like document number, expiry date, and issuing authority.
Files are binary uploads (images, PDFs, etc.) attached to an Entity.
They are separate resources and are not currently linked to one another.
BNDRY supports the following identity document types:
Passport
An internationally recognised travel document issued by a national government.
Driver's Licence
A government-issued licence authorising an individual to operate a motor vehicle.
Birth Certificate
An official document recording the birth of an individual, issued by the relevant government authority.
Medicare Card (AU)
An Australian government-issued card confirming eligibility for Medicare health services.
Visa
An official endorsement allowing an individual to enter, stay in, or leave a country.
Once a Document is stored against an Entity, you can use BNDRY's Document Verification automation to check it against authoritative government sources. The Individual Document Verification guide walks through the full API flow — creating a verification job, running it against an Entity's stored Document, and polling for the result.
When you run a verification job, you specify an idType (e.g., PASSPORT) and an Entity. BNDRY uses the structured Document data stored against that Entity — document number, expiry date, issuing authority, and other typed fields — as the input to the verification check. The Document must exist and be fully populated before the job is run.