Category

FX & Cross-Border Payments

FX and cross-border payment providers move money between currencies and countries with local rails, transparent pricing and hedging. Compare on currency coverage, payout speed, pricing model, and treasury/hedging capabilities.

Global marketplaces
Payroll platforms
PSPs
Cross-border e-commerce
Treasury teams
Publish an RFPRun the Fit Check

In one minute

What it is

Infrastructure to convert currencies and move money between countries — via local payment rails where available, and correspondent banking where not.

What you get

Currency conversion, local collection and payout accounts, international transfers, rate quotes and locks, and sometimes hedging.

What you still own

Your pricing to customers, your FX risk policy, beneficiary data quality and customer communication.

When you need it

When you pay or collect in currencies other than your own, or offer that to your customers.

How it works

Your product or treasury team

Your product or treasury team

FX and payments provider

pricing, conversion, routing

Local payout and collection partners

domestic rails in each country

Correspondent banks

for routes without local rails

Beneficiary

contractor, supplier, customer

The same payment can travel very differently: locally within the destination country, or through a chain of correspondent banks. Routing decides cost, speed and predictability.

Who does what

Customer pricing

You
Owns
Provider
Supplies wholesale rate
Local partner
—

Beneficiary data

You
Collects
Provider
Validates
Local partner
—

Sanctions screening

You
Shares data
Provider
Screens
Local partner
Screens

Conversion

You
Requests
Provider
Executes
Local partner
—

Routing

You
—
Provider
Chooses route
Local partner
Executes locally

Tracking and exceptions

You
Informs customers
Provider
Tracks and investigates
Local partner
Supports

FX risk

You
Owns policy
Provider
Supplies instruments
Local partner
—

Decisions to make before you shortlist

Scope

Payouts only
Collections only
Both, plus accounts
focus versus one provider.

Pricing to customers

Pass-through
Your margin
transparency versus revenue.

Routing

Local rails first
SWIFT everywhere
cost and speed versus reach.

Risk

Spot only
Forwards and hedging
simplicity versus certainty on future flows.

Provider count

One global provider
Several by corridor
simplicity versus price and coverage.

Use cases

Pay international contractors and suppliers

Send local payouts in dozens of currencies with predictable fees and reconciliation.

Read the use case

Offer multi-currency accounts to customers

Give business or consumer users named accounts and balances across major currencies.

Read the use case

Collect from customers abroad locally

Receive payments through local rails and settle to your home currency automatically.

Read the use case

Hedge FX exposure programmatically

Book forwards or spot trades via API to lock in rates for future payouts or receivables.

Read the use case
View all FX & Cross-Border Payments use cases

What to compare

Currency and corridor coverage

Gaps become manual work

Ask: Which currencies and corridors, local or via SWIFT?

Pricing transparency

FX margins are easy to hide

Ask: What is your markup over which reference rate, and what fees apply per payment?

Speed and predictability

Beneficiaries expect certainty

Ask: Typical delivery per corridor and how you track payments

Local collection accounts

Cheaper, faster inbound

Ask: Which currencies have local receiving details?

Hedging

Protects future margins

Ask: Forwards, limit orders, via API?

Compliance

Cross-border risk

Ask: Screening, purpose codes, documentation per corridor?

Beneficiary validation

Failed payments cost time

Ask: Account-format validation before sending?

Licensing and safeguarding

Protects your funds

Ask: Licences, regulators, how client funds are held?

How providers charge

FX margin

Over a stated reference rate

Per payment fee

Differs by rail and corridor

SWIFT and intermediary fees

Depends on charging option

Account fees

For multi-currency or collection accounts

Hedging costs

Priced into forward rates

Ask each provider for the all-in cost at your expected volume, for year one and year three.

Regulatory context

EU

  • Money transmission and FX for payments are payment services requiring authorisation; client funds are safeguarded
  • The Transfer of Funds Regulation requires originator and beneficiary information to travel with transfers.

Global

  • Sanctions regimes and local capital controls shape which corridors work and how.

Orientation only, not legal advice.

What providers will ask you

Have these ready before you publish.

  • Corridors and currencies
  • Volumes and payment sizes
  • Payer and beneficiary types
  • Purpose of payments
  • Your own licence status
  • Hedging needs

Red flags

  • Margins quoted without a reference rate
  • "Global coverage" that is SWIFT everywhere
  • No payment tracking
  • Hedging offered without clarity on the permission it runs under
  • Vague safeguarding

How Finlane fits

Your RFP covers

  • Corridors and currencies
  • Collections and payouts
  • Accounts
  • Routing
  • Pricing model
  • Hedging
  • Compliance
  • Volumes
  1. 1Scope your FX requirements with the AI advisor
  2. 2Matching providers receive your brief
  3. 3Compare structured responses side by side
  4. 4Shortlist and test on your top corridors

Providers on Finlane

Browse all providers in the directory

Frequently asked questions

Related reading

Buying in FX & Cross-Border Payments?

Post a structured RFP on Finlane and compare providers’ answers side by side. Free for buyers.

Publish an RFPTalk to us