When Crypto Crosses Borders: The Operational Challenges Growing Businesses Can’t Ignore

Why Cross-Border Payments Are Where Crypto Shows Up First

There is a reason cross-border settlement is a common way for digital assets to enter the operations of businesses that did not set out to be crypto companies. Parts of the traditional cross-border payment infrastructure can be slow, costly, and opaque. A payment routed through correspondent banking may pass through multiple intermediary institutions, each potentially taking a margin, with an exchange rate that is rarely the mid-market rate and a settlement time measured in days.

Crypto, and particularly stablecoins, offers an alternative for certain payment corridors. Settlement can be much faster, costs can be lower, and the payment is traceable on-chain from the moment it is sent. It is worth being fair to the alternatives, though. Modern multi-currency accounts and fintech payment platforms have narrowed this gap considerably, offering fast and relatively low-cost fiat settlement in many corridors. The honest position is that crypto can be advantageous for specific routes and circumstances, not that it is universally cheaper or faster than every fiat option. The figures often quoted in favour of crypto are illustrative, and the right comparison is the one done for the specific corridor, currencies, and providers in question.

For crypto-native businesses, cross-border transactions are simply part of the operating model, and the challenge is doing so within a governance and compliance framework that satisfies the relevant regulators. For established businesses extending into this space, the challenge is capturing the commercial benefit without creating operational risks the finance function is not equipped to manage.

The FX Question: Where the Savings Are Real and Where New Risks Appear

The cost picture for settling cross-border payments in stablecoin is not as simple as comparing one transfer fee to another. A proper comparison accounts for the spread between the stablecoin’s peg and the actual conversion rate on and off the network, any fees charged by the exchange or platform used for conversion, and the timing risk between initiating the payment and completing the conversion.

For payments in stablecoins pegged to the US dollar, the FX exposure depends on when conversion to or from sterling happens. If the sender converts sterling to a stablecoin, sends it, and the recipient converts to their local currency, both sides bear conversion cost at different points. The total may still be lower than a traditional route for a given corridor, but it is rarely zero and not always transparent. The FD’s role is to model the true, all-in cost of each route on a like-for-like basis, rather than comparing a headline crypto fee to a worst-case bank charge.

Where the payment is made in Bitcoin or another volatile asset rather than a stablecoin, the FX risk is a different order of magnitude. The value can change materially between initiation and receipt. Specialist hedging instruments do exist for some cryptoassets, but they differ from the routine FX facilities a business might use to hedge a sterling-dollar exposure, and they can introduce additional cost, complexity, liquidity, counterparty, and governance risk. They are not a simple like-for-like substitute for a forward contract, and they should be approached with that in mind.

The commercial case for cross-border crypto settlement is often genuine. But the FD’s job is not to endorse or reject the opportunity. It is to make sure the business understands the full cost, the real risks, and the operational requirements before the second payment, not just the first.

Stablecoins Are Not Risk-Free

Because stablecoins are designed to hold a steady value, it is tempting to treat them as equivalent to holding dollars. They are not, and the differences matter for any business using them to settle cross-border obligations. The specific risks worth understanding include:

• Depegging risk: a stablecoin can lose its peg, temporarily or otherwise, meaning it no longer trades at the value you expected.
• Issuer and reserve risk: the stability depends on the issuer and the quality and accessibility of the reserves backing the token.
• Redemption limitations: converting back to fiat at scale or at speed is not always frictionless.
• Token freezing or blacklisting: some stablecoins allow the issuer to freeze or blacklist addresses, which can affect funds you hold or receive.
• Exchange or platform failure: the platform used to hold or convert the asset carries its own counterparty risk.
• Network and bridge risk: moving assets between blockchains via bridges introduces additional technical and security risk.
• Recipient off-ramp availability: the recipient needs a reliable way to convert the asset to local currency, which is not guaranteed in every jurisdiction.
• Regulatory treatment in the recipient jurisdiction: how the asset is treated at the other end can affect whether the payment works as intended.
• Sending the correct token on the wrong network: the same token can exist on multiple blockchains, and sending on the wrong network can result in loss.

None of this makes stablecoins unsuitable for cross-border settlement. It means the business should understand what it is using, choose deliberately, and build these considerations into its process rather than discovering them the hard way.

The Travel Rule and Cross-Border Compliance

The Travel Rule is frequently cited in discussions of cross-border crypto, and it is important to be precise about who it applies to. In broad terms, Travel Rule obligations generally attach to in-scope cryptoasset service providers: the exchanges, custodians, and similar businesses that transfer crypto on behalf of customers. A regulated provider may be required to collect and transmit originator and beneficiary information alongside a transfer.

An ordinary business does not automatically become a regulated cryptoasset service provider simply by paying a supplier in crypto. If it uses a regulated provider to make the payment, that provider will typically handle the Travel Rule mechanics. What the business itself should do is retain appropriate commercial, counterparty, sanctions, and payment records, sufficient to evidence what the payment was for and who it went to. The exact obligations depend on the activities, the jurisdictions, and the regulatory status of the parties involved, and specialist advice may be required where the position is unclear.

On the frequently quoted £1,000 figure: it is better understood as a level that can affect the information required to accompany a transfer, rather than a clean line between covered and uncovered transactions. The detailed application depends on the circumstances and the service providers in the chain. Presenting it as a simple on/off threshold oversimplifies a more nuanced position, and businesses should confirm the current requirements against up-to-date guidance.

Separately, the Cryptoasset Reporting Framework (CARF) is expected to increase the visibility that tax authorities have of activity conducted through in-scope reporting service providers, with data exchanged between many jurisdictions. For cross-border transactions, this means relevant data may be shared with more than one tax authority. It does not create a complete record of every direct wallet-to-wallet transaction, but it does mean the era of assuming crypto sits outside the reporting infrastructure that applies to traditional finance is ending. Businesses should build this into their processes and confirm the current position against official sources.

Regulatory Divergence: Two Sides, Two Sets of Rules

Cross-border crypto transactions introduce a regulatory complexity that traditional bank transfers often absorb on the customer’s behalf. When a business makes a conventional cross-border payment, the banking chain typically handles sanctions screening and much of the compliance on both sides. When the payment is in crypto, more of that responsibility can shift to the business and its chosen providers.

This does not mean every crypto payment requires formal legal advice in two countries. For occasional, low-value, well-understood payments to an established counterparty, proportionate internal checks may be sufficient. For recurring, material, or higher-risk arrangements, particularly those involving unfamiliar jurisdictions or counterparties, it is sensible to confirm the regulatory, sanctions, and banking position more formally before committing. The judgement about how much diligence is proportionate is exactly the kind of judgement an experienced FD is well placed to make.

The banking complication

This is a practical issue that catches many businesses off guard. Some banks remain cautious about businesses that transact in crypto. They may ask for detailed documentation about the nature and purpose of crypto transactions, and they may seek evidence of source of funds when crypto is converted to fiat and deposited. In some cases they may be reluctant to support significant crypto activity at all.

For crypto-native businesses, managing the banking relationship is a strategic priority, and finding a bank comfortable with the operating model matters. For established businesses newer to crypto, the relationship management is simpler but the underlying risk is the same: if the bank does not understand what the business is doing with crypto, the relationship can deteriorate. The FD’s role is to manage this proactively, ensuring the bank has the information it needs, the documentation is in order, and the audit trail connecting crypto transactions to their commercial purpose is clear and accessible.

A Cross-Border Crypto Payment Workflow

The practical challenge is designing a workflow that covers the full cycle, from commercial intent through to retained evidence. This is the same process design discipline that underpins any well-run payment operation, applied to a rail that behaves differently from the one the business is used to. The sequence below is a starting point that can be scaled to the volume and risk of the business:

1. Confirm the commercial purpose and the supplier agreement behind the payment.
2. Verify the counterparty and wallet details through an independent channel, not solely the email requesting payment.
3. Confirm the specific token and the blockchain network to be used.
4. Review the regulatory, sanctions, and banking implications, proportionate to the size and risk of the arrangement.
5. Model the full, all-in payment cost, including spreads, fees, and timing risk.
6. Obtain approval under the business’s payment-authorisation framework.
7. Execute a small test transaction first, where the value or novelty of the payment justifies it.
8. Record the transaction hash, valuation, fees, and conversion details.
9. Reconcile the payment against the invoice and the accounting records.
10. Retain the complete supporting evidence, ready for the bank, the auditor, or a regulator if asked.

The workflow should exist before the second payment, not the tenth. The first cross-border crypto payment is always treated as a one-off. By the third, it is a pattern. By the fifth, it is a process, whether anyone has designed it or not. The FD’s job is to make sure the design happens before the habit forms.

Different Rails, Same Discipline

Cross-border crypto payments are not a different kind of business operation. They are the same kind of operation, settlement of a commercial obligation to a trading partner, conducted on a different rail. The commercial advantages can be real. The operational requirements are specific. And the finance function’s role, designing the process, managing the risks, ensuring proportionate compliance, and keeping the bank comfortable, is unchanged.

If your business is making or receiving cross-border crypto payments, or a supplier or client has asked whether you would consider it, a short conversation can help you understand what is involved before the decision is made. The commercial case may be strong. The governance needs to match.