Scenario: adding multi-currency exchange and cross-border FX
What changes when a community bank owns its exchange and FX rails
This is a representative scenario built around an archetypal mid-sized community bank, grounded in industry benchmarks rather than a named-client result. There is no real institution behind it and no reported figures; the outcomes below are stated as targets to plan against, not results ACM is claiming a specific bank achieved. It illustrates how adding white-label multi-currency exchange and cross-border FX could unfold and what is realistic to aim for.
An archetype: a $2-4B community bank losing cross-border business
Our archetype is a community bank with roughly $2 to $4 billion in assets, serving a regional base of retail customers and small-to-mid-sized commercial clients, a growing share of whom import goods, pay overseas suppliers, or receive funds from abroad.
Today the bank cannot serve those needs from its own platform. International payments are handed off to a correspondent network the bank does not control, FX is quoted manually by a small treasury team or outsourced entirely, and commercial clients with real cross-border volume increasingly route that business to larger banks and fintech competitors that quote instantly and settle faster. The bank keeps the deposit relationship but loses the fee income, the data, and, over time, the primary relationship itself.
FX that is slow, opaque, and owned by someone else
The drag is structural, not a matter of effort. Cross-border money movement sits outside the bank's core, so every currency transaction adds cost, delay, and a place for things to break.
- Opaque, manual pricing: rates are quoted by phone or spreadsheet with wide, inconsistent spreads, so clients cannot see what they pay before they commit and the bank cannot compete on transparency.
- Correspondent dependence: cross-border settlement runs through intermediary banks the institution does not control, adding days of float, layered fees, and limited visibility into where a payment is.
- Lost commercial business: importers, exporters, and clients with overseas payroll take their FX, and frequently their operating accounts, to providers that quote and settle in real time.
- Reconciliation gaps: FX sits in a separate workflow from the core ledger, so multi-currency activity is reconciled by hand and rarely matches cleanly.
- Long-lived data exposure: settlement and payment records that must be retained for years are a "harvest now, decrypt later" target, where data captured today could be decrypted once quantum computing matures.
Bring exchange and FX inside the bank's own stack
Rather than negotiate another correspondent arrangement, the scenario stands up a white-label exchange and FX capability the bank brands, controls, and runs as its own, posting to the same ledger as the rest of its accounts. Delivery follows ACM's Agile Speed Framework, beginning with one high-value flow rather than a multi-year build.
Real-time multi-currency pricing
Live FX across major currency pairs, with the bank applying its own spreads and tiered rate sheets, so commercial clients see a transparent quote before they convert instead of waiting on a manual callback.
Cross-border settlement on owned rails
Settlement wired into the core, with the option to route over conventional and stablecoin rails, reducing dependence on a correspondent chain the bank cannot see into.
Reconciliation built into the flow
Conversions and multi-currency balances post to one integrated ledger, so FX activity reconciles automatically rather than in a separate spreadsheet workflow.
Post-quantum protection by default
Settlement and payment records are secured with cryptography aligned to NIST's 2024 standards, ML-KEM (FIPS 203) and ML-DSA (FIPS 204), guarding long-lived data from harvest-now-decrypt-later exposure.
The engagement starts narrow, typically with commercial USD-to-EUR and USD-to-GBP flows for existing import clients, proves the model against that real volume, then expands to more currencies, retail in-app conversion, and stablecoin settlement options as they fit the bank's roadmap. ACM's ecosystem partners extend the platform where it adds value: Lux Network for tokenized settlement rails and Hanzo.ai for AI-assisted pricing and monitoring.
From handing FX away to running it as a product
The difference shows up first in what the bank can now offer under its own brand, and then in the control its risk and operations teams gain over the flow.
- Instant, branded quotes: commercial clients convert inside the bank's own digital channels at transparent rates, so cross-border business stays in-house instead of migrating to competitors.
- Shorter settlement path: owned rails and, where appropriate, stablecoin settlement compress multi-day correspondent timelines toward near-real-time finality on migrated flows.
- One reconciled ledger: multi-currency balances and conversions sit in the same system as deposits and payments, ending the manual matching that separate FX tooling forces.
- FX as fee income: the bank captures spread and fee revenue it previously surrendered to correspondents and outside FX providers.
- Controls and audit built in: per-currency dealing limits, maker-checker on rate changes, and an immutable, exportable audit trail are designed to support SOC 2, ISO 27001, and PCI-DSS requirements rather than added afterward.
Benchmark-based targets, stated honestly
The figures below are objectives to model and plan against, derived from published benchmarks and from the measurable cost and speed differences between correspondent settlement and owned, programmable rails. They are not results claimed for any institution, and actual outcomes depend on client mix, currency volume, and which flows the bank modernizes first.
- Up to 95% lower infrastructure cost versus standing up FX on legacy, on-premises systems, as a target based on cloud-native platform benchmarks, freeing budget to compete on price.
- Faster settlement: a target of moving migrated cross-border flows from multi-day correspondent timelines toward near-real-time finality, with stablecoin transfer volume reaching roughly $27.6T in 2024 (2024 on-chain data) as evidence the rails are maturing.
- Recaptured fee income: a goal of retaining FX spread and fees currently lost to correspondents and third-party providers.
- Higher commercial retention: deeper, transparent cross-border service aimed at keeping importers' and exporters' primary relationships in-house.
- Lower reconciliation effort: a target reduction in manual multi-currency matching as conversions post to one integrated ledger.
A discovery engagement turns these benchmarks into a model specific to your institution, sizing the opportunity against your own client base, currency volume, and the first flow you choose to bring in-house. This scenario reflects ACM's approach for community and mid-sized banks; the same pattern applies to corporate treasury operations managing multi-entity FX.
Regulated-first delivery, in stages your risk teams trust
A capability that touches cross-border settlement succeeds on governance and delivery discipline, not technology alone. ACM brings both, with compliance in scope from the first release.
- Compliance designed in: sanctions and watchlist screening, KYC reuse, and transaction monitoring connect to the AML stack the bank already runs, so cross-border conversions clear the same controls as everything else.
- Co-creation, not handoff: ACM builds with the bank's treasury, operations, and compliance teams, designing the flow around its clients and examiners.
- Iterate from real volume: starting with one live commercial flow means decisions rest on production behavior, not assumptions, before scope expands.
- Security that holds up: post-quantum protection on long-lived settlement records is part of the platform; see the post-quantum security approach.
- Start the conversation early: the most useful first step is mapping your cross-border flows. Contact ACM to begin.
Model this scenario against your own flows
Bring your client mix, your busiest currency corridors, and the cross-border volume you are handing to correspondents today. We will map a realistic first flow and a benchmark-based path to value for your institution. Further reading: ACM ecosystem research at papers.hanzo.ai and tokenized settlement at lux.network.
Map your FX scenarioFrequently asked questions
Is this a real client case study?
No. This is a representative scenario built around an archetypal mid-sized community bank with roughly $2 to $4 billion in assets, grounded in published industry benchmarks. It does not describe a named client, and the outcomes are stated as targets to plan against, not reported results. It exists to show how adding white-label exchange and cross-border FX with ACM could realistically unfold.
How are the target outcomes derived?
They are benchmark-based, not client-reported. Cost targets reference cloud-native banking platform benchmarks, including ACM's goal of up to 95% lower infrastructure cost versus legacy systems. Settlement-speed targets reflect the measurable difference between correspondent timelines and owned, programmable rails, with stablecoin transfer volume reaching roughly $27.6T in 2024 (2024 on-chain data) cited as evidence those rails are maturing. Actual outcomes depend on client mix, currency volume, and which flows a bank modernizes first.
Would the bank have to replace its existing systems?
No. The exchange and FX platform is modular and delivered through ACM's Agile Speed Framework. Most institutions begin with one high-value flow, such as commercial USD-to-EUR settlement for existing import clients, and connect ACM components to the core, payment rails, and AML screening already in place, then expand in phased, testable releases rather than a single high-risk cutover.