A White Paper on ACM's White-Label Mobile Wallet for Regulated Institutions
Rethinking the mobile wallet for regulated institutions
The phone is now the branch. This paper examines why most banking apps fail to keep pace with how members actually move money, and sets out ACM's architecture for a white-label mobile wallet that unifies deposits, cards, transfers, and in-app FX behind your brand, engineered regulated-first with post-quantum cryptography at the foundation.
The mobile gap is a structural problem, not a UI problem
For most credit unions and community banks, the mobile app is the primary point of contact with members, yet it is often the least owned part of the stack.
Three forces have widened the gap between what members expect and what regulated institutions can ship. First, the everyday experience bar is now set by large consumer fintechs, where balances, payments, and cards live in one place and update instantly. Second, money movement has fragmented: a single member may use ACH, real-time payments, cards, cross-border transfers, and increasingly stablecoin rails in the same week. Third, the underlying systems were never designed to feed a real-time mobile surface, so institutions bolt a thin app onto a batch-oriented core and inherit its limits.
The common workaround, licensing a generic app from one vendor and stitching it to a card processor, an FX provider, and a payments gateway from others, produces a brittle result. The institution carries the integration risk and the examiner's questions, but does not own the experience, the data, or the roadmap. When members ask why a balance is stale or a transfer is slow, the answer lives in a seam between vendors.
One client-owned surface over one ecosystem
ACM treats the wallet not as a standalone app but as the customer-facing layer of a single banking ecosystem, so the surface and the rails behind it are designed together.
The design principle is consolidation without lock-in. Because deposits, payments, FX, cards, and optional tokenized assets are components of one platform rather than separate procurements, the data model is shared and the seams disappear. The institution owns the brand, the app-store presence, the customer relationship, and the data; ACM provides the technology and stays behind the curtain. White-labeling is not a skin on a generic template, it is a configurable product your members experience as entirely your own.
Branded everyday banking
Balances, deposit products, statements, and account-to-account movement update in real time against your core banking platform, under your name in the app stores.
Cards in the wallet
Issued cards provision to Apple Pay, Google Pay, and Samsung Wallet through in-app push provisioning, with instant freeze, controls, and transactions visible as they post.
Transfers across rails
Person-to-person, bill pay, and account transfers call ACH, RTP, and wire from one surface, with optional stablecoin settlement where your model and regulators allow.
In-app FX
Hold and convert across currencies with real-time rates spanning a wide set of markets, drawing on the same exchange and FX engine used elsewhere in the platform.
How the wallet is built
The wallet is a thin, secure client over a set of platform services, designed so the experience stays fast while the institution retains control of data and policy.
- Native clients, shared services: iOS and Android clients consume the same documented REST APIs and mobile SDKs that power the rest of the ecosystem, so behavior is consistent and the app surface stays lightweight.
- Composable money services: deposits, transfers, cards, and FX are discrete services behind the wallet, allowing an institution to launch a focused experience first and enable additional capabilities without re-platforming.
- Real-time data binding: connectors map balances, transactions, and member records to your core or a third-party ledger, replacing batch refresh with event-driven updates so what a member sees matches the system of record.
- Non-custodial key management: for digital-asset features, threshold cryptography supports non-custodial designs where members retain control of their keys, removing single points of compromise where your model and regulators call for it.
- Crypto-agile foundation: cryptographic primitives are abstracted from the application, so algorithms can be rotated as standards evolve without rebuilding dependent systems.
Engineered for the layer examiners scrutinize hardest
A consumer-facing app holds identities, transaction histories, and credentials that stay sensitive for years. ACM treats the wallet as a regulated system from the first line of code.
The most consequential decision is forward-looking. Adversaries can capture encrypted traffic and stored records today and decrypt them once a cryptographically relevant quantum computer exists, a risk widely described as "harvest now, decrypt later." Because banking records remain confidential for years or decades, this is a present-day governance decision rather than a future problem. In 2024 NIST finalized the first post-quantum standards, ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205). These standards are recent, so ACM frames its work as building on and aligning to them, deploying post-quantum cryptography in a hybrid configuration alongside proven classical algorithms and prioritizing the longest-lived, highest-sensitivity data first. You can read more on our post-quantum security approach.
- Post-quantum protection: hybrid, NIST-aligned cryptography protects member data in transit and at rest, with crypto-agility to rotate primitives as the standards mature.
- Device and session trust: biometric authentication, device binding, and per-member session control let you revoke a lost device and force re-authentication.
- Examiner-ready audit trails: configuration changes, card freezes, provisioning events, and transactions are logged immutably for the reviews bank and credit-union examiners expect.
- Compliance-ready posture: controls, data residency options, and documentation are designed to support SOC 2, ISO 27001, PCI-DSS, and HIPAA requirements; certification remains the institution's to pursue.
Fits the systems behind it and the phones in front of it
Because the wallet is the front door, it has to bind to the institution's existing core, ledger, and identity stack rather than forcing a rip-and-replace.
ACM exposes documented REST APIs and mobile SDKs, federates sign-in through OIDC and SAML, and hands off identity verification to your existing KYC and AML provider. Card tokenization, payments, and FX are reached through the same platform, so an institution is configuring one ecosystem instead of integrating several vendors. Delivery follows ACM's Agile Speed Framework, which is designed to put a branded wallet into members' hands in reviewable increments and then iterate, rather than staking everything on one disruptive cutover. AI and data tooling, developed with ecosystem partners Hanzo.ai and Lux Network, helps institutions understand engagement and personalize the experience over time. The same model fits credit unions and community banks that want a member-owned digital front door.
What to expect, stated honestly
We describe outcomes as targets to plan against and design goals, not as reported results from named clients.
- One owned surface: consolidating deposits, cards, transfers, and FX into a single branded app removes the vendor seams that create stale data and slow support answers.
- A wider on-ramp to modern money: optional stablecoin settlement and tokenized-asset support, surfaced beside everyday balances, let an institution meet emerging demand without a separate app. For context on the market, BCG projects tokenized real-world assets could reach $16T+ by 2030, and 2024 stablecoin transfer volume has been estimated near $27.6T.
- Efficiency by design: a modern, cloud-native stack is engineered to target up to 95% lower infrastructure cost versus legacy core systems, a goal to validate against your environment.
- Quantum-readiness as a program: the wallet advances a documented, examiner-ready path to post-quantum protection rather than leaving the institution exposed to harvest-now-decrypt-later risk.
Related research
Original research from across the ACM ecosystem on the technologies behind the wallet.
- Agentic AI and applied research: papers.hanzo.ai, on the AI and data work informing engagement and personalization.
- Tokenized finance and settlement: lux.network, on tokenized assets, stablecoins, and settlement infrastructure.
- Platform context: our trust and security posture and the broader payments and stablecoins capabilities the wallet draws on.
Put your brand in members' pockets
Let's scope a white-label mobile wallet around your core, your compliance posture, and your roadmap, and walk through the architecture in this paper against your environment.
Book a discovery callFrequently asked questions
Is this white paper based on a specific client deployment?
No. It describes ACM's architecture and design approach for the mobile wallet, and states outcomes as targets to plan against and design goals rather than reported results from named clients. Figures such as up to 95% lower infrastructure cost versus legacy core systems are objectives to validate against your environment, and any compliance posture is described as designed to support SOC 2, ISO 27001, PCI-DSS, and HIPAA requirements.
Why does a mobile wallet need post-quantum cryptography now?
Because a wallet protects identities, credentials, and transaction histories that stay sensitive for years, it is exposed to harvest-now-decrypt-later risk, where data captured today is decrypted once quantum computers mature. NIST finalized the first post-quantum standards in 2024 (ML-KEM/FIPS 203, ML-DSA/FIPS 204, SLH-DSA/FIPS 205). ACM builds on and aligns to these recent standards, deploying post-quantum algorithms in a hybrid configuration alongside classical ones and protecting the longest-lived data first.
How does the wallet connect to our existing core and vendors?
It binds to your environment rather than forcing a rip-and-replace. ACM exposes documented REST APIs and mobile SDKs, federates sign-in through OIDC and SAML, and hands identity verification to your existing KYC and AML provider. Cards, payments, and FX are reached through one platform, so you configure a single ecosystem instead of integrating separate vendors, with delivery sequenced through the Agile Speed Framework.