vaultkit

@orvacon/vaultkit is the ergonomic layer over orvacon's card vault. The gateway tokenizes the card and orvacon returns the token; vaultkit normalizes that into a CardOnFile you persist against your own customer, hands it back as a charge PaymentSource, and deletes it when asked. It keeps no store of its own.

bun add @orvacon/vaultkit

import { vaultkit } from "@orvacon/vaultkit";

const vault = vaultkit({ orva });

const saved = await vault.save({ card, buyer, customerRef: "cus_42" });
if (saved.ok) {
  await myDb.cards.insert(saved.card); // { token, userKey?, brand, last4, label, ... }
}

// charge it again later
await orva.authorize({ ...req, source: vault.toSource(saved.card) });

// and forget it
await vault.forget(saved.card);

save returns a discriminated result ({ ok: true, card } | { ok: false, error }) — the gateway's error passes through, never thrown. label renders "Visa •••• 4242" (falling back to "Card •••• 4242", then "Saved card"). toSource and forget also accept a bare { token, userKey? }, so a row you read back from your database works without rebuilding a CardOnFile.