Cross-Border Payments Are Currency Transactions Between Whom?

Cross-border payments are currency transactions between parties in different countries. Those parties can be businesses, individuals, governments, or financial institutions. More precisely, they are international payments: they may involve currency conversion, but do not have to.

The short answer to “between whom?” is therefore payers and recipients in different countries—not necessarily parties using different currencies. The Association for Financial Professionals’ cross-border payments definition uses the location of the sender and recipient as the central distinction.

For finance teams paying hundreds of international recipients, this is more than terminology. Treating “cross-border,” “foreign currency,” and “international wire” as interchangeable can lead to unnecessary conversions, incomplete onboarding, and inaccurate cost reporting.

Who are the parties in a cross-border payment?

The underlying payment connects the party that owes money with the party entitled to receive it. Banks and payment providers help execute that obligation, but they are not necessarily the commercial counterparties.

• Business to business: A company pays an overseas supplier, agency, or incorporated contractor.
• Business to individual: A platform pays an overseas seller or creator, or a company pays an individual contractor.
• Individual to individual: A person sends a remittance to someone in another country.
• Individual to business: A customer pays a merchant abroad.
• Institutional payments: Banks, governments, and other institutions transfer funds internationally.

Do not confuse the recipient with the recipient’s bank. A supplier’s incorporation country, operating location, and bank-account country may differ. Likewise, a payment provider may receive funding in one jurisdiction and deliver the payout through a domestic account elsewhere.

For ordinary explanation, payer and recipient countries establish the concept. For regulatory reporting, card-network classification, or provider eligibility, use the applicable definition: residence, legal establishment, account location, and payment-instrument issuance can matter differently.

Cross-border payment and currency exchange are separate concepts

A cross-border payment answers where the parties are. Foreign exchange answers whether one currency is exchanged for another. The delivery rail answers how the payment reaches the receiving account.

The following hypothetical cases show why these should be separate fields in a payment record.

Same currency does not mean domestic, and a domestic delivery rail does not mean the underlying obligation is domestic. Conversely, a foreign-currency transaction does not prove that the parties are in different countries.

What actually happens to the money?

In an electronic bank payment, physical currency is not shipped across a border. Institutions debit and credit accounts, exchange payment instructions, and settle obligations through the relevant arrangements.

Correspondent banking connects institutions

Where the sending and receiving banks lack a suitable direct relationship, intermediary banks can help complete the payment through correspondent accounts. SWIFT can carry the payment messages; it is not itself the account holding the supplier’s money.

Intermediaries can introduce additional processing, deductions, or investigations. However, counting intermediaries alone does not establish the final price or arrival time. Currency, account arrangements, compliance checks, and service terms also matter.

Local delivery changes the final leg

A provider may collect funds from the payer and use liquidity already held in the destination market to make a domestic transfer to the recipient. Funding, conversion, and recipient credit can occur at different times.

That structure can simplify delivery, but it does not remove the provider’s need to manage liquidity and applicable compliance obligations. Finance should still identify the legal payer, beneficiary, funding currency, and amount due.

Currency conversion may happen before, during, or after payment

A company can buy destination currency before a payment run, request conversion when releasing a payment, or send a currency that the receiving bank later converts. These choices place control over the exchange rate in different hands.

Holding funds through multi-currency global accounts can separate conversion timing from payout timing. It does not eliminate currency exposure: holding a currency ahead of a future obligation creates its own treasury decisions.

Separate the payment obligation from the FX trade

Consider a hypothetical US business that owes a UK contractor an amount denominated in pounds. It holds dollars but can choose when to buy the pounds.

There are distinct records to preserve:

• Commercial obligation: The contractor must receive the agreed sterling amount under the contract’s fee and payment terms.
• FX transaction: The business exchanges dollars for pounds at an agreed rate, subject to the quote’s conditions.
• Payment execution: The provider delivers pounds to the contractor’s eligible account.

If the business already holds enough pounds, it can make the payment without a new conversion. If it buys pounds but the payout fails, the conversion may remain completed. A payment failure does not automatically reverse the FX trade.

This distinction also separates different risks. Exchange-rate risk concerns changing currency values. Payment-delivery risk concerns whether the beneficiary receives the funds. FX settlement risk concerns delivering the currency sold without receiving the currency bought.

The BIS Committee on Payments and Market Infrastructures discusses this last risk in its report on FX settlement risk mitigation. Payment-versus-payment arrangements address that currency-exchange settlement risk; they do not by themselves guarantee that a supplier’s account has been credited.

Build a classification record before selecting the rail

For a scaled payout operation, a single “international payment” flag is too coarse. Keep the following dimensions separate so that routing, compliance, and reconciliation use the same underlying facts.

1. Identify the obligation’s parties. Record the paying legal entity and the beneficiary’s legal name, entity type, and relevant country information.
2. Identify the accounts. Capture the sending and receiving account countries separately from the parties’ countries.
3. Record the currencies. Distinguish invoice currency, funding currency, instructed payout currency, and expected credit currency.
4. Assign conversion responsibility. Specify whether treasury, the sending provider, or the receiving institution controls any conversion.
5. Define the amount owed. Establish whether the agreement requires a fixed recipient amount and who bears permitted charges.
6. Validate corridor-specific requirements. Confirm account identifiers, bank details, beneficiary information, payment purpose, and supporting documents where required.
7. Define completion evidence. Distinguish an accepted instruction from account debit, settlement, and confirmed beneficiary credit.

Country requirements are not interchangeable. An IBAN is not a universal account identifier, and a BIC alone does not identify the beneficiary’s account. Use the country-by-country international contractor payment guide as a starting point, then confirm current requirements with the executing provider.

Keep payment classification distinct from tax classification, too. A recipient’s bank-account country alone does not establish tax residence or withholding treatment. Tax documentation and identity checks support the broader process but should not be reduced to a bank-location lookup.

What the definition cannot tell you

Calling a payment cross-border does not establish its speed, price, or regulatory treatment. An instant domestic final leg may still depend on prior funding, conversion, screening, or operating windows elsewhere in the chain.

The BIS report on extending and aligning payment-system operating hours identifies operating-hour differences as a cross-border payment friction. Ask providers which stage their delivery estimate measures and what conditions must be met before the clock starts.

Similarly, “no conversion” does not mean “no fees.” Same-currency international payments may still incur transfer, intermediary, or receiving-bank charges.

Start with the parties, then design the payment

The answer is straightforward: cross-border payments connect parties in different countries. Currency exchange is a possible component, not the defining requirement.

Before your next payment run, classify obligations, account locations, currencies, and conversion responsibilities separately. Review exceptions where those fields disagree rather than forcing them into a single domestic-or-international label.

Then evaluate payout automation against that record: can the workflow preserve the intended recipient amount, apply the appropriate controls, and reconcile conversion separately from delivery? Those are more useful acceptance criteria than an “international payments supported” checkbox.

Created with AI assistance. Sources are linked in the article; this content is general information, not legal, tax, or financial advice.