Cross-border payment challenges belong in your market-entry budget: which customers can pay, why payments fail, and how much reaches your bank account after conversion. Before opening another market, ask your payment team for a country-level breakdown of declines, settlement costs and compliance responsibilities.
For a platform serving merchants in several countries, this is also an onboarding decision. Define the payment requirements of the next customer before promising a launch date.
The business cost of getting international payments wrong
Measure lost orders separately from processing expenses. In an illustrative model, 10,000 attempted orders at $100 each represent $1 million of potential sales. A two-percentage-point increase in completed orders adds $20,000 of gross sales if order values stay constant. That is a calculation, not a forecast of recoverable revenue or profit.
Ask for approval rates by issuing country, payment method and currency. Compare completed orders as well as individual payment attempts, so repeated retries do not inflate the apparent opportunity. Then subtract processing, fraud and refund costs from any proposed improvement.
Use that model to decide whether a new acquiring relationship, checkout change or payment infrastructure investment addresses a measurable business constraint.
Why cross-border transactions fail at higher rates
A decline needs a diagnosis before it needs another processor. Authentication requirements, unsupported currencies and unavailable issuers call for different responses. Stripe’s published decline-code guidance distinguishes these cases; the table below uses its card-payment examples, not a claim that every provider uses the same codes. (Stripe documentation, accessed September 28, 2026)
| Failure | Action to request from your payment team |
|---|---|
| Additional authentication required | Let the customer complete the cardholder verification flow. |
| Currency unsupported by the card | Ask the customer to confirm supported currencies with their issuer. |
| Issuer unavailable | Follow the provider’s retry guidance and check whether the attempt succeeded before creating another charge. |
| Card cannot support this purchase | Give the customer a route to contact their issuer or use another payment method. |
Review these categories by market before assuming local acquiring will solve every decline. A different acquiring bank does not change an expired card or complete a customer authentication challenge. Treat any proposed routing change as a test with a defined group of transactions and a completed-order metric.
Local payment methods: the market entry requirement most businesses underestimate
Stripe’s April 10, 2025 experiment found an average 7.4% conversion increase and 12% revenue increase when checkout dynamically displayed at least one additional relevant payment method beyond cards. Those are results from Stripe’s experiment, not guaranteed gains for your platform. (Stripe, April 10, 2025)
Use the study as a reason to test country-specific checkout choices. Ask which methods your target customers use, whether the provider can onboard your merchant entity, and how refunds and settlement work. A method’s popularity does not establish that your chosen integration supports it.
For Orchestra projects, check the current integration catalogue before promising a named method. Build the launch requirement around the supported method, country, currency and merchant account together.
Currency conversion, interchange, and the hidden costs of cross-border processing
Ask for a fee breakdown for the actual route you plan to use. One historical example shows why geography matters: the UK Payment Systems Regulator documented increases in Mastercard and Visa UK-EEA card-not-present consumer interchange from 0.2% to 1.15% for debit and from 0.3% to 1.5% for credit after EU withdrawal. These are corridor-specific interchange figures, not a universal cross-border surcharge or a current merchant quote. (PSR market review, final report December 13, 2024)
For each provider quote, separate interchange, scheme assessments, processor charges and currency conversion. Request the exchange-rate reference, markup and conversion timing in writing. Do the same for refunds rather than assuming the original exchange rate will apply.
Currency conversion has two sides. The currency charged to the customer can differ from the currency of their card account; the currency paid into your bank account can differ again. Stripe documents customer-side issuer conversion fees and merchant-side settlement conversion as separate possibilities. (Stripe currency documentation, accessed September 28, 2026)
| Arrangement | What to establish before launch |
|---|---|
| Dynamic currency conversion | The customer can choose a home-currency conversion offer, with its exchange rate and additional fees disclosed. |
| Processor conversion at settlement | Confirm which currency reaches your bank account and what conversion rate and fees apply. |
| Local-currency pricing and settlement | Confirm eligibility for the settlement currency; price any later conversion when you move those funds. |
Visa’s guidance on dynamic currency conversion requires a clear choice and disclosure of the conversion rate and additional fees. Showing a familiar currency does not make conversion free. (Visa, undated; accessed September 28, 2026)
Our budgeting recommendation is to compare the complete route, including account costs and repatriation of funds. Do not approve local acquiring on an assumed percentage saving that no provider has quoted.
Regulatory complexity across jurisdictions
Separate card security, payment authentication and personal-data handling in the launch review. A working payment integration is only one input to that review.
PCI DSS is the card-data security standard. Use the current standard and validation documents from the PCI Security Standards Council, then confirm the applicable scope and validation route with your acquiring bank or assessor. (PCI SSC document library, accessed September 28, 2026)
The regional questions differ:
| Region | Requirement to check | Practical launch question |
|---|---|---|
| European Economic Area | Strong Customer Authentication under PSD2, with scope and exemptions assessed for the transaction | Can checkout handle a required authentication challenge? |
| United Kingdom | UK payment-services rules and authentication standards | Has the provider confirmed the UK authentication flow and applicable exemptions? |
| India | RBI payment-aggregator rules, including cross-border activity | Is the provider authorised for the intended activity, with the required merchant checks and settlement arrangements? |
| Brazil | LGPD personal-data rules and international-transfer mechanisms | Where does customer data go, and which permitted transfer mechanism covers that movement? |
The EBA explains that having one payment provider outside the Union does not create a blanket exemption: authentication rules apply to the parts of the transaction carried out within the Union as described in its guidance. Avoid labelling every “one-leg-out” payment exempt. (EBA Q&A 2018_4233, accessed September 28, 2026)
The UK’s FCA describes its authentication requirements and exemptions separately. Confirm the relevant flow with the provider instead of treating an EEA configuration as proof of UK compliance. (FCA, updated February 15, 2023)
India’s September 15, 2025 Master Direction brings payment-aggregator categories, including cross-border aggregators, into one framework. Its requirements include authorisation and merchant due diligence. A blanket statement that every foreign merchant must use the same authentication flow misses the provider and activity distinctions. (RBI, September 15, 2025)
Brazil’s ANPD Resolution 19 establishes rules for international transfers of personal data, including contractual mechanisms. Treat payment acceptance and permission to transfer customer data as separate workstreams. (ANPD, August 23, 2024)
For each launch, name the owner of provider due diligence, authentication testing and data-transfer review. Record the applicable requirements for the actual countries and entities involved; a regional summary cannot determine every merchant’s obligations.
How payment orchestration addresses the multi-market problem
Orchestra’s integration uses a JavaScript library for payment capture and a REST API for operations after capture, such as charging stored tokens and issuing refunds. The parts work together. (Orchestra integration model, founder clarification August 29, 2026)
Your platform chooses the initial provider and fallback order; Orchestra executes that configured logic. Keep the failure diagnosis above in that design: adding a backup provider does not remove the need for authentication or merchant approval. (Orchestra routing capabilities, product clarification September 18, 2026)
Start a global payment acceptance discussion with one proposed market, its merchant entity, required methods and settlement currency. Ask which existing connections cover those requirements, what onboarding remains, and which decline categories the proposed fallback can address. That gives your team a concrete scope to price and test.
Frequently asked questions
How much more do cross-border payments cost?
Use a provider quote for the country pair, card or payment method, and currencies involved. Compare processing charges, conversion and settlement costs together. The UK-EEA example above illustrates a specific interchange change; it does not establish a worldwide fee range.
Does local-currency pricing eliminate conversion costs?
Check both sides of the payment. Matching the customer’s currency can avoid a currency mismatch at checkout, while conversion may still occur when you settle or later move funds. Confirm the supported currencies and fee schedule with the provider.
Will a backup processor recover every failed payment?
No. An authentication challenge needs customer verification, and an unsupported currency needs a compatible payment arrangement. Use the provider’s failure reason and retry guidance to decide what happens next.
What should a business leader ask for before entering a new market?
Ask for a launch sheet naming the merchant entity, supported payment methods, authentication flow, settlement currency, complete fee quote and compliance owners. Use that sheet to set the launch date and the initial success measures.
