Collect a BVN without it touching your code.
Drop a form into your site or app. The customer types into a frame served by the vault, and your page and servers get a token back. A breach on your side then has no identifiers to find.
Every system a BVN passes through has to be defended. If your web app never receives it, there is a lot less to defend.
Mint a client token
Your server asks for a single-use, short-lived token for one site and set of fields.
Mount the form
The frame collects and checks the value, inside the vault's own origin.
Keep the token
Your code receives a token. A typo doesn't use it up, so a customer can correct it.
On your page
<script src="https://vault.onshore.ng/embed/rv.js"></script>
<div id="bvn"></div>
<script>
const form = Onshore.collect({
vault: "v_live_ng01",
clientToken, // from your server
labels: { bvn: "Your BVN" },
theme: { accent: "#2574de", radius: "8px" },
});
form.mount("#bvn");
const tokens = await form.submit(); // { bvn: "tok_bvn_…" }
</script>Web and mobile
Web frames, plus iOS, Android and React Native views.
Reveal as well
Show a value in a frame that hides itself after a time you choose.
Allowed sites only
Frames load only on sites you list, and wildcards are refused.
Your look
Set the accent colour and corner radius to match your product.
No keys in the app
Apps never hold a credential. Your server hands them a single-use token.
Mobile protection
Autofill and copy are off, and values leave the screen when the app does.
On the web, a cross-origin frame keeps the value away from page scripts. An app has no equal boundary, so mobile views are weaker against a hostile library in your own app. Early access: mobile views need testing on real devices.
Start with one leak.
Tell us which flow worries you most. We'll show you what it would take to keep it onshore.