Documents

A document in BNDRY is a structured record of a real-world identity document — a passport, a driver licence, a Medicare card, a visa, or a birth certificate. It lives in the data-collection layer of the platform and holds the fields you would read off the document itself: number, names, dates, issuing country, and any jurisdictional extras. A document is typically linked to an entity, which is the customer record it helps identify.

Why documents exist

Identity verification is a structured problem. Regulators expect you to know which document supported a verification decision, what was on it, and when it was checked. Storing that information as free text in a notes field, or burying it inside an uploaded PDF, makes it almost impossible to query, validate, or report on later.

BNDRY treats a document as a first-class record so that the operationally important fields — passport number, expiry date, issuing country — are addressable in their own right. Verification flows, reviewers, and downstream services can read those fields directly without parsing an image. The document record is the structured statement of what was on the identity document; an associated file can hold the raw scan or photo if one is captured.

Key properties and sub-types

Every document has a type, a set of type-specific fields, and a link to the entity it belongs to. The supported types are:

• Driver licence — licence number, names, date of birth, issuing country, issue and expiry dates. Australian licences also carry a card number and an issuing state.
• Passport — passport number, names, gender, date of birth, place of birth, issuing country, issue and expiry dates.
• Australian Medicare card — card number, individual reference number (1–4), card type (green, blue, or yellow), cardholder names, and expiry date.
• Visa — visa number, names, date of birth, gender, issuing country, expiry date. Australian visas also carry the associated passport number and that passport's issuing country.
• Birth certificate — registration number, names, date of birth, issuing country, and either a registration date or registration year. Australian certificates also carry an issuing state and an optional certificate number.

Documents also carry timestamps for creation, last update, and (when soft-deleted) deletion. A soft-deleted document can be restored — the platform follows the standard resource lifecycle rather than discarding records outright, so that an audit trail of past identity evidence is preserved.

How documents relate

A document usually belongs to an entity — the individual or organisation whose identity it helps establish. Documents are produced by identity-verification flows, by forms that capture customer data, and by manual entry from operators. They sit alongside files, which hold the raw uploaded image or PDF that the document's structured fields were drawn from; the two are complementary rather than interchangeable. Notes attached to the same entity capture the operator commentary around a document — why it was accepted, what looked unusual — that the structured fields themselves cannot express.