onshore
Products / Core

A token for your systems. The real value stays in Nigeria.

Send a BVN, NIN, account number 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.

Vault Made-up data
FieldToken
BVN22123456789
NIN70123445412
NUBAN0123456789
Phone+2348031234567
The problem

Once a BVN 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.

How it works
01

Send the value

Your server, a secure form or the proxy passes the value to the vault.

02

Get a token

The vault encrypts the value and returns a token such as tok_bvn_7Hq2xP9LmA4c.

03

Reveal under policy

Only callers a policy allows can turn a token back, and each attempt is recorded.

In code

Tokenize at the source

const [{ token }] = await vault.tokenize("v_live_ng01", [
  { field: "bvn", value: bvn, subject_ref: "cust_1042" },
]);

await db.customers.update({ id: 1042, bvn_token: token });
What's included

Four kinds of token

Opaque, format-preserving for systems that check length, deterministic for matching records, and short-lived transient tokens.

Nigerian formats built in

11-digit BVN and NIN, 10-digit NUBAN and +234 phone numbers are understood from the start.

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.

Who uses this

Start with one leak.

Tell us which flow worries you most. We'll show you what it would take to keep it onshore.