Cross border payments

Cross border payments, routed through regional acquirers instead of one corridor.

topropay sits across regional acquirers in every supported corridor — EU, UK, US, APAC, LATAM and partner-licensed India. Per-transaction routing picks the right landing zone for each authorisation; multi-currency settlement and FX policies make the back-end behave like one cross border payments platform.

Book a corridor review Explore the platform
EU € Buyer US $ Merchant FX 1.08 LEDGER · EU↔US €189.00 · FX 1.08 · $204.12
One corridor. Two currencies. One ledger row.
40+
corridors covered
Multi
currency settlement choice
1
ledger across regions

The short version

Where single-corridor cross border payments break — and what fixes them

Cross-border traffic carries problems domestic traffic doesn't. Five pains a single-provider setup leaks on, paired with the fix the orchestration layer brings.

  1. 01
    Pain

    Cross-border interchange and scheme assessments compound

    Fix

    Per-BIN, per-country routing picks the cheapest landing zone per authorisation, not per merchant.

  2. 02
    Pain

    Single-acquirer setups leak approvals on foreign-issued cards

    Fix

    Multi-acquirer cascade absorbs soft declines inside the same request; foreign-issuer noise stops eating revenue.

  3. 03
    Pain

    FX spreads hidden inside the underlying provider's settlement

    Fix

    Settlement currency is a policy choice per market; FX line items surface separately in the reconciliation feed.

  4. 04
    Pain

    Per-region reconciliation lives in separate CSVs

    Fix

    Daily settlement, fees, refunds and chargebacks across every region normalise into one ledger.

  5. 05
    Pain

    Local methods (PIX, BLIK, iDEAL, OXXO, PayID) require per-provider integrations

    Fix

    Local methods surface through the same unified API as cards — no per-rail SDK on the merchant side.

Key benefits

How the platform handles the major corridors

Four corridor shapes that show up most often, with what changes per corridor once the orchestration layer is in front of the regional acquirer set.

  1. Run EU and UK corridors on regional acquirers

    European card BINs route to EU-licensed acquirers; UK card BINs route to FCA-licensed UK acquirers; SEPA, iDEAL, BLIK and Open Banking surface as configured methods per market. Interchange and dispute outcomes stay local.

  2. US corridor with debit-routing-aware policies

    US card traffic routes to US-licensed acquirers with debit-network policies aligned to the merchant's compliance posture. ACH (debits and credits) runs through the same authorisation engine, sharing vault tokens with card flows.

  3. LATAM corridor with PIX, OXXO, SPEI and Boleto

    Brazilian and Mexican card traffic routes to regional acquirers; local methods (PIX in BR, OXXO in MX, SPEI as account-to-account) surface inline. Installments on the relevant scheme programmes are supported where the underlying acquirer offers them.

  4. APAC corridor with PayID, OSKO, FPX and partner-licensed India

    Australian PayID and OSKO, Singapore PromptPay-equivalent and Malaysian FPX flow as configured methods. India connectivity is delivered through licensed partner gateways under the same unified API surface.

Cross border payment process flow

From initiate to one ledger row — seven stages

What the platform actually does between the merchant's authorisation request and the reconciliation row that lands in the next morning's finance export.

  1. 01

    Initiate

    Merchant's checkout or invoice flow sends an authorisation request through the unified API, tagging the buyer's geography, currency and the merchant's settlement preference.

  2. 02

    Score

    The routing engine scores every connected acquirer for that BIN, scheme, currency and country pair in under 200ms — composite policy weighing approval, cost and dispute risk.

  3. 03

    Route

    The top-ranked route receives the authorisation. The merchant doesn't pick the provider per transaction; the engine picks it from the panel.

  4. 04

    Cascade

    If the chosen route returns a soft decline, the authorisation cascades to the next ranked acquirer inside the same request — the buyer never sees a per-provider retry.

  5. 05

    Convert

    Where the merchant's settlement currency differs from the authorisation currency, FX runs at the rail's quote (or at the merchant's chosen policy) with a transparent line item.

  6. 06

    Settle

    The acquirer settles in its native currency; topropay normalises the settlement into the merchant's chosen currency and ledger row.

  7. 07

    Reconcile

    Daily exports across every corridor share one ledger format keyed off vault tokens; per-corridor analytics surface where the next policy tweak earns its keep.

Corridor snapshot

Supported corridors at a glance

A compact view of the major corridors the platform handles, with the rail-specific notes that matter most. The full matrix per acquirer is live in the merchant dashboard.

Corridor Shape
EU ↔ UK EUR / GBP settlement; SEPA, Bacs and Open Banking inline; selective 3DS2 on the auth path.
EU ↔ US USD settlement option for US-billed merchants; debit-routing-aware on US side; PSD2-compliant on EU side.
EU ↔ LATAM Brazilian / Mexican acquirers connected; PIX, OXXO, Boleto, SPEI surfaced inline; installments where supported.
EU ↔ APAC Australian, Singapore, Malaysian acquirers connected; PayID, OSKO, FPX, PromptPay-equivalent inline.
US ↔ LATAM US-domiciled merchants reach BR / MX / AR via regional acquirers; FX line items separated in reconciliation.
Any ↔ India* Indian connectivity delivered through licensed partner gateways; UPI, RuPay and NetBanking surfaced inline.
B2B ↔ Global B2B invoice flows on cards or bank rails; stablecoin lane available via partner crypto gateways for treasury that wants it.

* India connectivity is delivered through licensed partner gateways rather than a direct RBI Payment Aggregator licence held by topropay.

Main use cases

Where b2b cross border payment solutions and B2C corridors earn their keep

Six merchant shapes that share the same orchestration layer but stress the corridor mix differently. Same product, different rail mix per use case.

  • B2C

    Direct-to-consumer brands selling cross-border

    European DTC brands selling into the US, UK and APAC route each market through the relevant regional acquirer set. Local methods surface per market; reconciliation lands in one feed regardless of buyer geography.

  • B2B

    B2B cross border payments and invoicing

    B2B cross border payment solutions cover invoice-driven flows: card on file for SaaS billing, bank rails for high-ticket invoices, and partner-licensed stablecoin lanes where treasury prefers them. The reconciliation surface treats them as one ledger.

  • Sub

    Subscriptions billed across markets

    Renewals running in the merchant's preferred settlement currency while authorising buyers in their local currency. Network tokens and account updaters apply cross-border just like domestic — the underlying mechanics don't change.

  • Plat

    Marketplaces with cross-border seller payouts

    Marketplaces split payments per seller per geography; payouts land in the seller's preferred currency, with topropay's reconciliation feed keeping every party's ledger straight.

  • PSP

    PSPs reselling cross-border capacity

    Resellers inherit the platform's regional acquirer set downstream; their merchants get cross-border coverage without the PSP integrating each rail directly. The PSP keeps the relationship and pricing.

  • Travel

    Travel, ticketing and high-ticket cross-border

    Multi-currency capture, staged captures, partial refunds and dispute analytics handle the long lifecycle of an international booking through one orchestration surface.

Cost anatomy

FX and fees, broken out — not blended

Five line items that make up the cost of a cross-border authorisation, exposed as separate rows in the reconciliation feed instead of a single blended rate.

01 Interchange
Scheme-mandated fee from the issuer to the acquirer; cross-border interchange tiers are higher than domestic. Routing picks the lowest landed-cost route per authorisation.
02 Scheme assessments
Visa / Mastercard / Amex scheme fees that apply on cross-border traffic. Surfaced as a separate line in the reconciliation export — not buried in a blended rate.
03 Acquirer markup
The acquirer's margin on top of interchange and scheme. Negotiable in the contract; the platform's panel is set up to pass-through where the acquirer supports it.
04 FX spread
Spread applied when converting the authorisation currency to the merchant's settlement currency. Configurable per market; rate visible at quote time.
05 Platform fee
topropay's per-authorisation fee, separate line item. No platform retainer, no per-environment fee, no minimum monthly.

Platform features

Capabilities behind cross border payment systems on topropay

What the platform actually ships specifically for cross-border traffic — plus the general orchestration capabilities shared with domestic flows.

  • Unified payments API

    One REST contract across every corridor; SDKs for web, mobile and server.

  • Smart routing engine

    Per-transaction scoring on BIN, scheme, currency, country pair and risk — composite policy per region.

  • Cascade & retry

    Soft declines cascade to the next ranked acquirer inside the same authorisation; cross-border noise is absorbed automatically.

  • Multi-currency settlement

    Settlement currency is a policy choice per market; merchants don't carry FX they didn't ask for.

  • FX management

    Per-market FX policy with transparent line items in the reconciliation feed; rate-lock windows for high-ticket transactions.

  • Regional method coverage

    Cards, SEPA, Bacs, Open Banking, iDEAL, BLIK, PIX, OXXO, SPEI, PayID, OSKO, FPX and partner-licensed UPI / RuPay.

  • PCI DSS Level 1 vault

    Card data captures into the vault before any underlying acquirer; refunds, retries and recurring on vault tokens.

  • 3DS2 & SCA orchestration

    PSD2-compliant in Europe with selective challenges; per-region authentication policies on the auth path.

  • Unified reconciliation

    Settlements, fees, refunds and chargebacks across every corridor normalised into one ledger.

  • Operator portal

    One dashboard for authorisations, refunds, disputes and chargebacks across every region in the connected set.

Trust & compliance

Compliance posture across every corridor

Every corridor runs through the same audited environment. Sub-merchants inherit the platform's posture rather than carrying separate certifications per country.

PCI DSS Level 1
Annual on-site assessment, quarterly ASV scans; sub-merchants inherit the posture for every corridor.
PSD2 / SCA
Selective 3DS2 challenges on the EU authorisation path keep approval high without breaking compliance bars.
FCA, MAS, partner-licensed
FCA-licensed connectivity in the UK; MAS-aligned routes in Singapore; partner-licensed routes for India and other markets where direct licensing isn't held by topropay.
Cross border payments regulation
Sanctions screening, AML monitoring scaled to corridor and vertical, Travel Rule support on stablecoin lanes where the partner gateway exposes it.
Card scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP thresholds tracked per acquirer relationship in the dashboard.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported where current operating licences exist. Grey and black-market verticals are out of scope regardless of corridor.

Ready to map your corridors

Run your cross-border traffic through regional acquirers.

A 30-minute corridor review walks through the regional acquirers relevant for your buyer base, the FX policy that fits your treasury, and a sandbox to test against before any commercial commitment.

Book a corridor review Read the API docs

Frequently asked

Buyer questions about cross border payments on topropay

Questions buyers ask before committing — covering corridors, B2B vs B2C, FX transparency, compliance and the process flow under the hood.

  1. 01

    What does topropay deliver as cross border payments solutions?

    Cross border payments solutions on topropay include the regional acquirer panel (EU, UK, US, APAC, LATAM), the routing engine that scores per-transaction across them, FX management, multi-currency settlement, regional method coverage and a unified reconciliation feed. Merchants integrate against one API and reach every supported corridor.

  2. 02

    How is this different from a single-provider cross border payments platform?

    A single-provider cross border payments platform runs every authorisation through one underwriting appetite and one rate card, then sets a blended FX spread. topropay routes per transaction across several providers and exposes FX as a configurable per-market policy with separate line items — the buyer sees one form; finance sees the line-level detail.

  3. 03

    Which cross border payments companies does topropay compete with?

    Cross border payments companies typically fall into three camps: traditional correspondent-banking-based players, fintech specialists and orchestration layers. topropay sits in the orchestration camp — it integrates with several specialists per region and routes between them, rather than selling a single proprietary corridor.

  4. 04

    Is the platform suitable for b2b cross border payments at high ticket?

    Yes — b2b cross border payments at high ticket benefit most from multi-acquirer routing and FX transparency. The platform handles invoice-driven flows on cards or bank rails, with staged captures, multi-currency support and partner-licensed stablecoin lanes when treasury wants them.

  5. 05

    How does cross border payment gateway behaviour differ from a domestic gateway?

    Cross border payment gateway behaviour adds country-pair signals to the routing decision (issuer country + acquirer country), surfaces FX line items in the reconciliation feed, and applies regional authentication policies per market. Other than that, the integration shape matches a domestic gateway exactly.

  6. 06

    What cross border payment services are bundled in the standard offer?

    Cross border payment services bundled in the standard offer include the unified API, hosted and embedded checkout, smart routing, cascade & retry, multi-currency settlement, FX management, PCI vault, 3DS2 orchestration, unified reconciliation and operator portal. No per-region or per-feature add-on pricing.

  7. 07

    How do cross border payment systems handle compliance across jurisdictions?

    Cross border payment systems on topropay inherit the platform's PCI L1 posture, PSD2 / SCA on EU traffic, sanctions screening on onboarding, AML monitoring per corridor and per vertical, and partner-licensed routes for markets where direct licensing isn't held by the platform. Compliance carries across corridors automatically.

  8. 08

    What b2b cross border payment solutions are recommended for SaaS billing across markets?

    B2B cross border payment solutions for SaaS billing across markets typically combine recurring card payment in the buyer's local currency with the merchant's preferred settlement currency, network-token-by-default for renewal stability, and SEPA Direct Debit or ACH for high-ticket invoices where bank rails win on cost.

  9. 09

    Is topropay a cross border payments fintech in the standard sense?

    topropay is a cross border payments fintech in the orchestration sense — a software-driven platform that abstracts multiple providers behind a unified API. Where many cross border payments fintech players sell a proprietary corridor, the platform sells the routing and reconciliation layer above several providers' corridors.

  10. 10

    How does the platform handle cross border payments regulation specifically?

    Cross border payments regulation handling on topropay covers AML and KYB on onboarding, sanctions screening at authorisation time, jurisdiction-permitted method filtering (the platform won't surface a method in a market where the underlying acquirer doesn't permit it for the vertical), and dispute-evidence formats tuned to each region's scheme rules.

  11. 11

    What does cross border payment processing look like inside the platform?

    Cross border payment processing inside the platform is the routing engine plus the vault plus the reconciliation feed running across the connected regional acquirer set. Per-transaction the routing happens in under 200ms; per-day the settlement and dispute data normalise into one export.

  12. 12

    How are fx cross border payments handled — explicit policy or blended rate?

    FX cross border payments are handled with an explicit per-market policy, not a blended rate. The merchant chooses the settlement currency per market; the FX spread is surfaced as a separate line in the reconciliation feed. Rate-lock windows are available for high-ticket transactions where treasury wants the predictability.

  13. 13

    Are fintech cross border payments via the platform any different from card-only flows?

    Fintech cross border payments via the platform run on the same authorisation engine as card-only flows — same vault, same webhooks, same reconciliation. The difference is the rail mix: bank rails, partner-licensed stablecoins and regional APMs sit alongside cards instead of being a separate console.

  14. 14

    Can you show a cross border payment process flow end-to-end?

    Yes — the cross border payment process flow runs: (1) merchant initiates authorisation through the unified API; (2) routing engine scores connected acquirers in the relevant corridor; (3) top route receives the authorisation; (4) on soft decline, cascade to next; (5) on success, FX runs at the configured policy; (6) acquirer settles; (7) reconciliation normalises into one ledger. The seven stages are visualised in the 'How it works' section above.

  15. 15

    How does the platform deliver cross border payments for licensed high-risk verticals?

    Cross border payments for licensed high-risk verticals (subscriptions with elevated chargeback, travel, licensed gaming, nutraceuticals) inherit the multi-acquirer routing posture plus chargeback-aware policies per segment. Per-corridor risk thresholds and acquirer subsets keep chargeback bands healthy.

Related

Related on the topropay platform