For the person
A smaller physical wallet, a choice of carriers, and fewer replacement journeys. No mandatory central account in the proposed design.
The pitch: let members bring suitable credentials, keep local accounts intact, and reduce the work of issuing another piece of plastic.
A smaller physical wallet, a choice of carriers, and fewer replacement journeys. No mandatory central account in the proposed design.
Potentially fewer cards to procure, personalise and hand out. The account, eligibility checks and access rules stay with you.
Start from the actual reader and data model. Add only the interfaces needed; keep a documented exit and fallback route.
BringPass proposes a transition from organisation-issued tokens to user-supplied credentials. At a compatible front desk, the process can be as simple as enrolling a card someone already owns. Native integrations can later add provider-specific identifiers, cryptographic proof and device-level revocation.
Providers keep their local records. Members keep a choice. Issued cards remain available when they are needed.
Download the pitch textAn editable illustration, not a savings forecast. Defaults are invented assumptions.
Membership decisions, identity checks where needed, lost-credential handling, abuse prevention and account closure still belong to the provider. Some staff time shifts rather than vanishes.
Fewer issued cards can mean less material use, but no environmental impact figure is claimed. Hardware manufacturing, extra devices and replacement rates need a lifecycle assessment.
Pairwise credentials reduce direct identifier-based linking in the proposed native model. They do not prevent correlation through names, shared hardware UIDs, IP addresses or other metadata.
Define a measurable pilot