Cross-border receivables · multi-currency
Cross-border card, wallet, ACH and SEPA acceptance behind one unified API — with multi-currency settlement, smart routing across acquirers, and one reconciliation feed. topropay is a receivables-side platform; buyers arriving from "amex fx international payments" queries — that's a different (Amex) product, discontinued.
Key benefits
Four properties that show up when a merchant stops running per-market acceptance stacks and starts running one platform behind every cross-border authorisation.
Cross-border card, wallet, ACH and SEPA volume converted at the point of authorisation where the buyer's issuer supports it. Merchant settlement in EUR, GBP, USD, AUD, and other supported currencies through the connected acquirer per contract.
Per-BIN, per-country and per-currency scoring picks the highest-EV acquirer for each authorisation. Local acquiring where available; cross-border lanes where it isn't. Cross-border fees stay visible, not buried.
Settlements, interchange, scheme fees, FX margins and chargebacks from every connected acquirer normalise into one ledger. Daily exports tagged by currency, country pair, acquirer and scheme.
For buyers arriving via 'amex fx international payments' or similar B2B FX searches: topropay is a different platform, focused on the acceptance side of international payments for business. It's a possible destination for merchants whose prior cross-border acceptance stack has been discontinued or is winding down.
How international payments for business work here
What happens between a buyer tapping their card in one currency and the settlement landing in the merchant's bank in another.
Hosted checkout, hosted fields or SDK renders the method list per market. The buyer picks a card, wallet, SEPA SDD, ACH or a regional rail; the total shows in their currency.
Card credentials capture into the PCI L1 vault; the platform reads the BIN's country and currency to pick the routing policy that fits.
The routing engine scores each connected acquirer by BIN, scheme, currency, country pair and risk. Local acquirers preferred where available; cross-border lanes as fallback.
Selective 3DS2 / SCA on the European card leg; scheme rules for card-present; NACHA / SEPA mandates for bank-rail debits. Cross-border processing charges are surfaced per transaction.
Settlement files ingest per acquirer, per currency; FX margins broken out; unified reconciliation feed for finance, tagged with country pair and settlement currency.
Main use cases
Five merchant shapes that pay for the platform inside their first cross-border quarter — DTC, SaaS, travel, wholesale and PSPs.
One checkout per market, one merchant record across markets. Cards, wallets, regional bank rails (iDEAL, Bancontact, PIX, PayID) surface per buyer's country; settlements roll into one ledger.
Recurring card on VTS / MDES network tokens plus SEPA Direct Debit for EU accounts. Multi-currency invoicing where the platform partners with accounting tools; single ledger for finance.
Auth-only at booking (in the buyer's currency), capture at fulfilment, refunds against the same vault token. Cross-border refund reversal aligns with the original authorisation currency.
B2B counterparties paying by card or bank rail across borders; per-invoice hosted pay links; NET-30 / NET-60 dunning that respects the buyer's local currency and rail preferences.
PSPs inherit the multi-acquirer, multi-currency stack and configure their downstream merchants per market. The PSP keeps the relationship and pricing; the platform handles the international-side message exchange.
Platform features
Twelve capabilities the platform ships once and reuses across every currency, corridor and connected acquirer.
Industry relevance
Licensed merchants operating across EU, UK, APAC and LATAM benefit most from a single receivables stack — DTC brands, SaaS billing across borders, travel and ticketing, wholesale and trade counterparties, and licensed gaming where the operating licences exist.
Trust & compliance
One audited environment underpins the orchestration layer; scheme programmes surface per acquirer; sanctions and AML monitoring adapt to the merchant's cross-border corridor mix.
Ready to consolidate cross-border
A 30-minute cross-border review covers the buyer markets relevant to your traffic, the connected acquirers that fit, per-corridor routing weights and a sandbox to test against before any commercial commitment.
Frequently asked
Definitions, the AmEx FX IP disambiguation, tracking and login questions, fees and the practicalities of running cross-border acceptance through one platform.
International payments for business on topropay means the acceptance side — accepting card, wallet, bank-rail and regional-rail volume from buyers in different markets, and settling the merchant in a supported currency. It's not a B2B FX / SWIFT payout product; the platform's focus is inbound cross-border receivables.
No. American Express FX International Payments (AmEx FX IP) was a separate American Express B2B international-payments service; it's a different product from topropay. American Express itself announced the discontinuation of the FX IP service (the closure has been publicised as 'amex fx international payments closing' in commentary). topropay is an independent payment orchestration platform focused on merchant acceptance across borders.
Yes. AmEx FX International Payments was Amex's platform for sending B2B FX / cross-border business payouts. topropay is an orchestration platform for the receivables / acceptance side — inbound card, wallet, ACH and SEPA volume across markets. The two products don't overlap in function.
The 'american express fx international payments login' and 'amex fx international payments login' pages belonged to Amex's platform. As of Amex's announced discontinuation of the FX IP service, users should refer to American Express's own communications for the current status of that login and any migration steps. topropay does not host or replace that login.
For UK merchants who previously used American Express FX International Payments UK for the FX / payouts side, topropay covers a different domain — inbound acceptance and reconciliation of cross-border card, wallet, ACH and SEPA volume, not B2B FX payouts. topropay may be a suitable destination for the acceptance-side of a merchant's stack; the B2B FX payout side needs a dedicated FX / treasury platform.
'Amex fx international payments platform' referred to Amex's own product. topropay is a separately-branded and separately-operated platform. For merchants comparing options after the AmEx FX IP wind-down, topropay may cover the receivables / acceptance part of the workflow; the FX / payout part is best handled by a treasury or FX-payout specialist.
The 'fx international payments business' framing typically describes the outbound B2B payments side — sending money across borders. topropay's core business is the inbound side — accepting cross-border payments from buyers. Some merchants need both; on the topropay side we cover the acceptance / receivables shape.
The phrase 'fx international payments closing' has referenced the AmEx FX IP wind-down. It does not describe topropay. topropay continues to operate its receivables-side platform for merchants and PSPs across EU, UK, APAC and LATAM markets.
topropay's pricing is receivables-side: acceptance costs (interchange, scheme, acquirer margin) and per-transaction platform fees. Where cross-border processing charges apply on the card side, they're broken out per transaction and per settlement row. There is no separate 'fx international payments fees' schedule in the AmEx sense — the cost model matches merchant acquiring.
The equivalent of an 'fx international payments login' on topropay is the merchant dashboard — one login covers cards, bank rails, wallets and reconciliation across every connected acquirer and market. Multi-user roles with audit-grade event logs are supported.
'Fx international payments tracking' as a phrase typically covers outbound payout / SWIFT-message tracking, which sits outside topropay's scope. topropay offers full lifecycle tracking of inbound acceptance events — authorised, captured, settled, refunded, disputed — via signed webhooks and the merchant dashboard.
For 'fx international payments for business' on the inbound side, topropay accepts the buyer's card / wallet / bank-rail payment in the buyer's currency (where the connected acquirer supports it), routes it to the highest-EV acquirer, and settles the merchant in a supported currency. Multi-currency reconciliation is built in.
The 'best business account for international payments' depends on which side of the flow matters most: inbound acceptance, outbound payouts, or treasury / FX conversion. topropay is a good fit for the inbound acceptance side; a treasury / bank / FX specialist is a better fit for outbound and settlement operations. Many merchants pair the two.
Yes. Migration support includes KYB fast-track, sandbox parallel-run against the incumbent stack, and a phased traffic cutover. Existing vault tokens from a source provider can often be ingested where a scheme-compliant token portability path exists between the source PSP and topropay's connected acquirers.
Inbound cross-border acceptance is available across EU, UK, APAC and LATAM as a baseline, with additional geographies added as partner acquirer relationships expand. India connectivity is delivered via licensed partner gateways; the merchant doesn't need a direct RBI licence to accept cards issued in India.
Related