In an era where digital money transfer services promise speed, low fees, and global reach, regulatory scrutiny is intensifying—not on transaction volume or technology, but on how transparently firms communicate true costs to consumers. The Consumer Financial Protection Bureau’s (CFPB) recent enforcement action against Wise US Inc. underscores a growing priority: ensuring that foreign exchange (FX) markups are not buried in fine print, but surfaced with clarity and consistency.
What the CFPB Found—and Why It Matters
The CFPB’s order, issued in May 2024, identified systemic failures in Wise’s disclosure practices between 2019 and 2023. During that period, Wise did not consistently display its FX markup—the difference between the mid-market rate and the rate offered to customers—as a standalone, quantifiable figure. Instead, users often encountered blended rates embedded within total fee summaries, obscuring how much of their payment went toward currency conversion versus service charges. This lack of granularity violated Regulation E and the Electronic Fund Transfer Act, which require clear, conspicuous, and accurate cost disclosures before consumers commit to a transaction.
Crucially, the $1.5 million civil penalty wasn’t tied to fraud or intentional deception—but to operational gaps in disclosure design, testing, and compliance monitoring. That distinction signals a broader shift: regulators now treat UX-level transparency as a non-negotiable compliance requirement, not merely a marketing best practice.
Three Core Disclosure Gaps Identified by the CFPB
Where Transparency Broke Down
- Dynamic FX markup concealment: Wise updated its displayed exchange rates in real time but failed to show how those updates affected the actual markup—especially during volatile market conditions.
- Inconsistent pre-transfer previews: On mobile apps and web interfaces, some users saw full breakdowns of fees and rates; others received only aggregated totals, depending on device type, browser version, or geographic location.
- Absence of standardized benchmarking: No clear reference to the mid-market rate was provided at point-of-commitment—leaving consumers unable to independently verify the fairness or competitiveness of the quoted rate.
These gaps weren’t isolated bugs—they reflected structural shortcomings in Wise’s compliance-by-design framework. Unlike legacy banks subject to decades of FX oversight, neobanks and fintechs often build disclosure logic incrementally, prioritizing feature velocity over audit-ready documentation. The CFPB’s action confirms that ‘move fast and break things’ no longer applies to consumer-facing pricing interfaces.
Toward Standardized FX Cost Reporting
The settlement mandates corrective actions beyond the penalty: Wise must implement a new disclosure protocol that surfaces the FX markup as a separate, percentage-based line item—visible before confirmation and preserved in post-transaction receipts. It must also submit quarterly compliance reports to the CFPB for two years and conduct independent third-party audits of its disclosure systems. These requirements go further than prior enforcement actions, setting a de facto benchmark for the industry.
Notably, the CFPB referenced emerging standards from the International Organization of Securities Commissions (IOSCO) and the UK’s Financial Conduct Authority (FCA), both of which advocate for ‘all-in’ cost labeling—including FX spread—in retail remittance contexts. While no U.S. federal rule yet mandates markup percentage disclosure, the Wise case effectively establishes enforcement precedent. Competitors—including Remitly, Xoom, and PayPal’s Xoom-branded services—are now reviewing their own disclosure flows with heightened urgency.
As cross-border payments increasingly converge with embedded finance—via payroll platforms, e-commerce checkouts, and gig economy wallets—the demand for auditable, machine-readable FX cost data will only grow. Regulators aren’t asking for perfection—but they are demanding intentionality: every pixel in a checkout flow must serve accountability, not just conversion.
