A token for your systems. The real value stays in its country.
Send a national ID, account number, IBAN or phone number to the vault. It stores the value encrypted and returns a token your databases, apps and vendors can use in its place.
Once a national ID sits in your main database, it spreads to replicas, exports, analytics and every vendor those feed. A token can go all of those places. A leaked token gives away no identity.
Send the value
Your server, a secure form or the proxy passes the value to the vault.
Get a token
The vault encrypts the value and returns a token such as tok_uk_nino_7Hq2xP9LmA4c.
Reveal under policy
Only callers a policy allows can turn a token back, and each attempt is recorded.
Tokenize at the source
const [{ token }] = await vault.tokenize("v_live_gb01", [
{ field: "national_id", value: nationalId, subject_ref: "cust_1042" },
]);
await db.customers.update({ id: 1042, national_id_token: token });Four kinds of token
Opaque, format-preserving for systems that check length, deterministic for matching records, and short-lived transient tokens.
Local formats built in
Country packs understand IDs, accounts and phone numbers from 18 countries, from NI numbers and Aadhaar to CPFs, Emirates IDs and BVNs.
Envelope encryption
Each value is encrypted on its own. Data keys are wrapped by a master key held in the key service.
Keys in your control
Use the bundled OpenBao key service, or connect a bank's own HSM over PKCS#11.
Find without revealing
Look up a person by a searchable field and get a token back rather than the value.
Erase one person
Export or delete everything held on a person, with a record that it happened.
Start with one leak.
Tell us which flow worries you most. We'll show you what it would take to keep it onshore.