Technical & legal references

Sources, not superlatives.

Technical limits are documented. Benefits are hypotheses. Proposed interfaces are labelled as drafts.

Status: concept implementation. The website and interactions exist. Python and JavaScript demonstrate the native message lifecycle locally; the other languages provide paired scaffolds. Production wallet, provider service, NFC drivers and the electronic token are not supplied. No partnerships, certifications or measured savings are claimed.

Primary references

Reference check: 14 September 2026. Follow the official source for its current text; platform rules and legal applicability require review before deployment.

Android Developers — Host-based card emulation
Supported ISO-DEP/APDU protocols, reader compatibility and the warning not to rely on an HCE device’s UID. Not a BringPass implementation guide.
Open official source ↗
Apple Developer — NFC & SE Platform
Platform access and eligibility constraints. Re-check the intended use case and market before committing to implementation.
Open official source ↗
W3C — Web Authentication Level 2
A stable reference for credential creation, assertions, relying-party scope and verification. This preview does not claim certification or implement the full standard.
Open official source ↗
German federal legislation — § 5 DDG
Provider information requirements. The actual operator must determine and complete applicable disclosures.
Open official source ↗
German federal legislation — § 36 VSBG
Consumer dispute-resolution information and applicability considerations.
Open official source ↗
European Union — Regulation (EU) 2016/679
Legal anchor for transparency, rights and data protection by design. The precise notice must match actual processing; this site is not a legal assessment.
Open official source ↗
German federal legislation — § 25 TDDDG
Terminal-information storage and access. Applicability depends on deployed behaviour, including added third parties.
Open official source ↗
German federal legislation — BFSG §§ 1 and 3
Scope of covered products and services. See also § 3 for requirements and relevant service-provider exemptions.
Open official source ↗
W3C — Web Content Accessibility Guidelines 2.2
Accessibility design reference, not proof of this site’s conformance.
Open official source ↗
IETF RFC 8032 — EdDSA / Ed25519
Signature scheme used by the experimental software references. The draft message encoding is a BringPass design choice, not an IETF protocol.
Open official source ↗
NXP — MIFARE DESFire EV3
Product documentation illustrates why UID, supported application and authorised provisioning must be checked separately from “NFC compatibility”.
Open official source ↗
Node.js — cryptographic signatures
Official documentation for the Node.js cryptographic primitives used by the JavaScript reference.
Open official source ↗
Python cryptography — Ed25519
Official signing and verification documentation for the Python reference dependency.
Open official source ↗

Project assumptions

The economics calculator contains invented, editable inputs. Pairwise relationships and device-level credentials are proposed architecture choices. Compatibility depends on a tested reader, backend and enrolment policy. No claim that all NFC, barcode or QR systems can accept a user-chosen identity is made.

Design and artwork

The original concept artwork is restored from the supplied mockup. Supporting illustrations are smaller and toned down with CSS; editable SVG alternatives are retained. The restored images are raster crops, not vector reconstructions. BringPass remains a working name without trademark clearance. No remote fonts or image libraries are loaded.

Open design work

Smartcard provisioning, authenticated provider contexts, APDU messaging, secure mobile integration, offline authorisation, root recovery, metadata unlinkability and the special token’s engineering all remain to be designed and tested.