NDEF Personalisation Tool
Programs the NDEF payload — URL, vCard, or custom record — onto the contactless surface of an AmbiSecure card or token. Designed for issuer use during personalisation, not for end-user reprogramming.
Issuer-side NDEF programming for AmbiSecure form factors.
URL records
Program a URL record — e.g. https://card.example.com/u/abc123 — that resolves to the user’s profile or a registration link on tap.
vCard records
Program a vCard record so a tap exchanges contact information directly into the phone’s contacts app.
Custom records
Custom NFC Forum NDEF record types for application-specific payloads (loyalty, ticket, voucher).
Bulk programming
Drives a stack of cards in parallel. Per-card unique payload via CSV or REST.
Audit
Per-card programming log with chip serial, payload hash, and outcome.
Lock policy
Optional NDEF lock-bit programming to prevent post-issuance modification.
What the tool supports.
| Targets | AmbiSecure OnePass Card, Tappable, OnePass Bio Card; any NFC Forum Type 4 surface |
|---|---|
| Record types | URI (URL), Text, vCard / MIME, custom external types |
| Standards | NFC Forum NDEF 1.0; ISO/IEC 14443 Type A; NFC Forum Type 4 Tag |
| Concurrency | 1..N readers in parallel |
| Per-card payload | CSV-driven or REST-driven per-card unique URL / vCard / payload |
| Lock policy | Optional capability container lock-bit programming |
| Audit | Append-only programming log; SIEM export |
Where this fits in the bigger picture.
Programming NDEF onto issued cards at scale?
Tell us your form factor, payload model, and audit requirements. We will tune the tool for your line.