A wallet where the regulated pieces are pluggable.

01 — THE CHALLENGE

The app most tightly bound to geography.

Wallets are usually the hardest product to take across borders, because fiat rails and card issuance are licensed market by market. Build on one country’s bank partner and that country’s rules quietly become your architecture.

The brief was to invert that: make the regulated pieces — fiat rail, card issuer, custody provider — pluggable per market, while the app, ledger, and crypto layer stay identical everywhere.

02 — OUR APPROACH

Regulated at the edges, uniform at the core.

The wallet sits on multi-market embedded-finance providers that already run licensed rails across many countries behind one API, with card issuance handled by platforms that issue across multiple regions and networks. Each layer can be swapped or run in parallel per market.

Crypto custody uses MPC key infrastructure with no inherent geographic dependency — keys aren’t tied to any one jurisdiction. Card data is tokenized the moment it enters the system, so the app never holds a PAN and stays out of country-specific PCI scope wherever it operates.

03 — THE OUTCOME

One app, one ledger, any market.

A double-entry, currency-agnostic ledger treats every balance the same — fiat or crypto, any denomination. The same service layer orchestrates whichever regional rail is active for a given user.

Data residency is handled by region-segmented infrastructure, so local regulatory requirements pin data to a region without forking the application. The security baseline — KMS/HSM key management on a SOC 2 roadmap — satisfies most regulators without market-specific rework.

04 — RESULTS

• Double-entry ledger, agnostic to currency and asset class
• Virtual & physical card issuance from one platform
• Card data token-vaulted — app out of PCI scope
• MPC custody with no jurisdictional dependency
• Region-pinned data residency without forking the app
• KMS/HSM key management on a SOC 2 roadmap