Now try paying your contractors.

That's where the operational reality sets in. Not just that cross-border payments are slow, though they are. The deeper problem is access. Many banks remain reluctant to serve crypto-native companies at all, and those that do often add friction: higher fees, heavier compliance demands, and the risk of a sudden account closure. And in between, your finance team is bridging the gap with whatever they can: manual reconciliation across currencies, spreadsheets tracking what moved where, cobbled-together workflows that weren't designed for a treasury that lives on-chain.

It's a mismatch of two worlds. Your treasury can move at the speed of crypto, yet your expense operations still run on banking infrastructure built for a different era.

That mismatch is not a minor inconvenience. It is a cost, and it compounds with every transaction.

The Number That Should Make Every Web3 CFO Uncomfortable

The cost of cross-border payments is a known problem, but headline figures often understate what crypto-native companies actually pay. Businesses lose more than $120 billion annually in cross-border transaction fees, according to Oliver Wyman and J.P. Morgan. The FSB’s 2025 KPI report puts the average B2B cross-border payment cost at 1.6% of transaction value, and that is for companies with clean access to standard banking rails. Crypto-native businesses often face higher effective costs because many banks still decline to serve them. Additional processes like off-ramp routing, limited corridor access, and FX markups all add friction.

Run the numbers for your own operation. For a Web3 company processing $2 million in annual cross-border expenses (contractor payments, vendor invoices across borders etc) means $32,000 a year in fees with the FSB’s 1.6% benchmark. In practice, the figure is often higher, and should be treated as the floor, not the ceiling.

The harder costs to measure add up too: hours of manual reconciliation, three-to-five day settlement gaps that create cash flow mismatches, and the overhead of maintaining banking relationships.

Most crypto-native companies hold treasury in stablecoins but still route expenses through traditional banking rails. Every transaction carries the cost of that mismatch.

The off-ramp tax is invisible on any single transaction. Across an annual expense ledger, it becomes one of your largest controllable costs.

The Blockers

If the cost is this clear, why have so many crypto-native CFOs held back on migrating their expense stack? Two reasons, and both deserve a direct answer.

The first was regulatory uncertainty. That's improving, even if it isn't fully resolved. The GENIUS Act (July 2025) introduced the first US federal framework for USD-denominated stablecoin issuance, with 1:1 reserve backing, monthly disclosures, and regular audits. MiCA became fully applicable in the EU in December 2024. The frameworks are still maturing, but the fog that kept finance teams cautious is starting to lift. Regulatory risk is far from zero, but it is no longer undefined.

The second, and the more decisive one, was tooling. The CFOs who wanted to move their expense operations off traditional rails often had nowhere to go. The infrastructure to cleanly bridge stablecoin treasury with fiat expense management, at scale, across multiple jurisdictions, with the approval workflows and audit controls a finance team actually needs, simply did not exist. That is changing. Purpose-built tools now make it possible to connect stablecoin treasury with everyday card spend, payments, approval workflows, and reporting. Shifting this barrier from feasibility, to execution.

What the Operational Model Actually Looks Like

The mechanics are simpler than most finance teams expect. Employees never need to hold, manage, or interact with crypto directly.

Cards, for everyday team spend. A company provides stablecoins as collateral to fund a secured corporate card programme. The card issuer, operating as a Visa principal member, issues virtual and physical cards to team members. Those cards work at any Visa-accepted merchant globally and can be added to Apple Pay and Google Pay. Transactions are captured in real time on the finance dashboard. The finance team reviews, categorises, and approves spend against pre-set limits and approval workflows. At month-end, the transaction record reconciles against the on-chain audit trail.

Payments, for contractor and vendor invoices. Finance teams can send local and international payments across multiple rails and currencies directly from the same dashboard. Settlement can be as fast as T+0 on select corridors and T+1 globally, compared to three-to-five business days through traditional banking wires. The FX conversion that previously happened opaquely inside a bank wire now happens transparently at the point of transfer.

What stays the same across both: employees spend with a physical or virtual card exactly as they do today. Approval workflows, spending limits, and expense policies carry over intact. Admins manage cards and payments from a single dashboard, with real-time balance and transaction visibility on mobile.

The infrastructure changes. The user experience largely does not.

The Controls Question Every CFO Asks First

Another common hesitation from CFOs evaluating this model is not just the technology. It is the governance question: how do I maintain the same audit readiness and policy enforcement that my board and auditors expect?

Deloitte's Q2 2025 CFO Signals survey found that accounting and control complexities were cited as a concern by 42% of CFOs regarding crypto adoption. It is a fair concern. Thankfully, the answer is better than most CFOs anticipate.

The controls architecture in purpose-built stablecoin expense platforms is often rigorous. Consider three dimensions:

1. The audit trail. On-chain transactions are immutable and timestamped. Every transaction hash is a verifiable record that an auditor can inspect independently, without calling anyone, requesting a PDF, or reconciling against a folder of scanned receipts.

2. Approval workflows. Multi-user permission structures let finance teams define precisely who can fund a card, approve transactions, view reporting, and close the books. Full segregation of duties is built into the platform architecture, not enforced through procedural policy alone.

3. Spending controls. Card-level limits, merchant category restrictions, and per-transaction caps can be set and adjusted in real time from the dashboard. No need for calls to follow up with a bank. No two-day turnaround.

The governance concern is valid. The good news: it is an engineering problem, not a structural one.

What's Next?

The regulatory picture is defined. The tooling now exists. And the operational model is already running in production at a growing number of crypto-native companies.

So what's next? Choosing the right platform and implementing it.

Where Reap Fits

Reap enables crypto-native businesses to run everyday expenses without forcing stablecoin treasury through slow, fragmented legacy workflows.

Teams can issue secured cards for everyday spend and send cross-border payments across multiple currencies, all from the same stablecoin treasury.

Approval flows, permissions, reporting, balance visibility, and transaction tracking sit in one dashboard, so finance teams can manage spend without stitching together cards, payments, banking partners, and spreadsheets.

Beyond spend and payments, idle treasury balances don't have to sit still. Reap's treasury layer lets businesses put capital to work while keeping it available to fund operations.

Visit reap.global to learn more or begin onboarding.

In Sum

The cross-border friction your team absorbs today is not unavoidable. It is a legacy of using 2015 infrastructure to manage a 2025 treasury.

The next step is straightforward: map your annual cross-border expense volume and apply a realistic effective rate. The FSB benchmark for businesses with clean banking access is 1.6%; for crypto-native operations, once off-ramp routing and FX markups are included, a figure closer to 3% is probably more realistic. Put a dollar figure on what your current setup is costing, then decide whether that number justifies a conversation.

If this changed how you think about your expense stack, follow along or reach out.

Disclaimer

The information provided is for general informational purposes only and does not constitute legal, financial, tax, or business advice. It is not a recommendation or offer to engage with Reap’s products or services. Use of Reap’s services is at the user’s own discretion and risk, and subject to applicable terms, availability, and regulatory requirements. All trademarks are the property of Reap and/or their respective owners. References to third parties do not imply endorsement or affiliation.