Cross-Border Payment Gateway: Accept International Payments Without Friction
Cross-border payments introduce a layer of complexity that purely domestic transactions do not have. Currency conversion, varying issuer risk models by market, cross-border authentication requirements, and compliance obligations across multiple jurisdictions all affect the cost and authorisation rate of international transactions. A cross-border payment gateway that handles these dimensions well allows merchants to expand internationally without creating a worse payment experience than their domestic competitors. This guide explains the key components of cross-border payment processing and how to select and configure a gateway for international acceptance.
What Cross-Border Payment Processing Involves
Cross-border payment processing occurs when the merchant's acquiring bank is in a different country from the cardholder's issuing bank. This happens whenever an international customer makes a purchase from a merchant using a processor in a different country.
The cross-border dimension: When a German cardholder buys from an Italian merchant, the transaction travels from the Italian merchant's gateway to the Italian acquiring bank, through the Visa or Mastercard network to the German issuing bank. The issuing bank applies its own fraud scoring model, which may treat cross-border transactions as higher risk than domestic ones. If the issuer's model flags cross-border transactions from the merchant's category, the authorisation may be declined or subject to additional authentication.
Currency dimension: The transaction may be initiated in the cardholder's local currency (presented at checkout in euros for a German customer) or in the merchant's pricing currency. The gateway must handle the conversion between the two. The conversion rate, the markup applied, and the settlement currency all affect the merchant's effective revenue per transaction.
Authentication complexity: PSD2 Strong Customer Authentication applies to transactions where both the merchant's payment service provider and the cardholder's payment service provider are within the EEA. Cross-border transactions where one party is outside the EEA (one-leg out) may have different SCA requirements. Understanding how authentication interacts with cross-border transactions is important for merchants with international customer bases.
Compliance across jurisdictions: Processing transactions from customers in multiple countries means the merchant's payment operations are subject to the compliance requirements of both its home jurisdiction and the regulations applicable in the customer's market. For regulated merchant categories, this can mean licencing requirements in each market.
For merchants in restricted categories expanding internationally, a high risk payment gateway with established cross-border acquiring relationships provides better approval rates than a standard processor attempting to accommodate high-risk cross-border traffic.
Currency Conversion, FX Rates, and Multi-Currency Settlement
Currency handling is one of the most commercially significant elements of cross-border payment processing, with direct impact on both customer experience and merchant revenue.
Multi-currency pricing: Presenting prices to international customers in their local currency reduces friction and increases conversion. A customer presented with a price in USD when browsing a UK site must mentally convert, estimate the bank's exchange rate, and factor in potential foreign transaction fees from their card issuer. Presenting GBP removes this friction. Most modern payment gateways support dynamic currency detection and localised pricing display.
Dynamic Currency Conversion (DCC): A specific service offered at the point of payment that allows the cardholder to choose whether to pay in the merchant's currency or their home currency at a rate provided by the acquirer. DCC is subject to strict card scheme disclosure requirements: the cardholder must be offered a clear comparison of the two rates. DCC can generate additional revenue for merchants but must be implemented carefully to avoid scheme rule violations.
Settlement currency options: Merchants typically settle in a single currency (their operating currency) with the gateway converting from transaction currencies at the time of settlement. For merchants with significant multi-currency operations, multi-currency settlement accounts may be preferable, holding balances in multiple currencies and converting at times chosen by the merchant to manage FX exposure.
FX rate transparency: Request the specific FX methodology from your gateway before committing. Some providers convert at the interbank rate with a disclosed markup; others use proprietary rate tables with less transparency. On significant cross-border volumes, a 0.5% difference in FX markup represents meaningful revenue impact.
RoxPay processes multi-currency transactions and settles to any SEPA bank account in euros in 24-48 hours. For high-volume merchants with specific multi-currency requirements, alternative settlement arrangements are available.
Compliance: AML, Sanctions Screening, and Local Regulations
Cross-border payment processing adds compliance dimensions that purely domestic processing does not encounter.
AML for cross-border transactions: Transactions crossing jurisdictions trigger enhanced attention from financial intelligence units because cross-border transfers are a standard method for money laundering. Both the merchant and the payment gateway must have AML procedures capable of identifying suspicious patterns in cross-border transaction flows.
Sanctions screening: Every transaction, domestic or cross-border, must be screened against applicable sanctions lists. For cross-border transactions, the geographic dimension increases the likelihood of encountering sanctioned jurisdictions or individuals. Transactions involving individuals or entities on OFAC, EU, or UN sanctions lists must be blocked automatically. Your gateway's sanctions screening infrastructure should be verified before processing transactions from high-risk geographic regions.
Country-specific regulatory requirements: For regulated merchant categories, each market where you accept customers may have its own licensing requirements. A gambling operator must hold licences in each jurisdiction where it accepts players from. An online pharmacy must meet the pharmaceutical regulatory requirements of each country it delivers to. These requirements do not disappear because you are processing through a foreign gateway; they apply to the merchant's business operations in each market.
VAT and local taxes: E-commerce merchants selling digital goods to EU consumers must register for VAT in each EU member state where they exceed the distance selling threshold, or register for the OSS (One Stop Shop) scheme. While this is a tax obligation rather than a payment processing one, it interacts with cross-border payment operations because transaction data from the gateway feeds into VAT reporting.
Data sovereignty: Some jurisdictions have requirements about where payment data related to their residents can be stored or processed. The EU's GDPR is the primary framework for European merchants, but merchants processing transactions from other regions (US CCPA, China's PIPL) must be aware of local data protection requirements that their gateway infrastructure must accommodate.
How to Reduce Decline Rates on International Transactions
Cross-border transactions have higher decline rates than domestic transactions because issuing banks apply more conservative risk scoring to transactions from foreign merchants. Several strategies reduce this premium.
3DS2 authentication: Properly implemented 3DS2 authentication provides the issuing bank with the authentication signal it needs to approve the transaction confidently. For cross-border transactions where the issuer has limited history with the merchant, the 3DS2 authentication record serves as a trust signal. Merchants without 3DS2 see higher decline rates on international transactions because issuers apply precautionary declines when they cannot verify the authentication.
Local acquiring: Using an acquiring bank in the same region as the customer reduces the cross-border signal in the authorisation request. A merchant with European and North American customers can reduce decline rates in each market by having an acquiring relationship in each region. While this adds complexity, for merchants with significant volume in specific markets, the authorisation rate improvement justifies it.
Card acceptance optimisation: Ensure you accept all major card types present in your target markets. American Express penetration varies significantly by country. Local co-badged cards (Carte Bancaire in France, Bancomat in Italy) may require specific acceptance configurations. Missing a significant card type in a key market means some customers cannot pay.
Retry logic for soft declines: Some cross-border declines are soft declines, meaning the issuer declined the specific transaction but would approve a slightly modified one (different authentication method, smaller amount in a split transaction). Implementing retry logic with appropriate modifications for soft decline response codes can recover some of these transactions.
Customer communication for additional verification: When an issuer requires additional verification (a 3DS2 challenge) rather than directly declining, ensure your checkout handles the challenge flow gracefully. A poor 3DS2 challenge experience causes customers to abandon rather than authenticate, creating a decline outcome that was actually preventable.
RoxPay for Cross-Border and International Merchants
RoxPay processes cross-border transactions for merchants across standard and high-risk categories, with a network of 100 partner banks and support for 120 payment systems and over 40 payment circuits.
Multi-currency transaction support: RoxPay accepts card transactions in multiple currencies, with conversion at settlement to euros. The exchange rate methodology is transparent and specified in the merchant agreement.
International card acceptance: Visa, Mastercard, American Express, Apple Pay, Google Pay, PayPal, and 40 additional circuits cover the payment methods your international customers carry.
3DS2 and cross-border authentication: Native 3DS2 support with frictionless optimisation improves authorisation rates on international transactions by providing issuers with the authentication signal they need.
High-risk cross-border capability: For merchants in restricted categories expanding internationally, RoxPay's specialist acquiring relationships cover the high-risk categories that standard international processors decline.
REST API for international integration: The REST API at app.roxpay.eu/api/v4/docs supports multi-currency payment intents, geographic transaction routing, and international webhook delivery.
To start your RoxPay application for international payment processing, specify your target markets and merchant category in the onboarding form. RoxPay is PCI DSS Level 1 certified (QS83A47X629), ISO 27001 certified, OAM registered, and has processed over 500 million euros in volume. Settlement is available to any SEPA bank in 24-48 hours, IC++ pricing from 0.45%, 99.9% uptime SLA.
Frequently Asked Questions
Why are my international transactions being declined more than domestic ones?
Cross-border transactions have higher decline rates because issuing banks apply more conservative risk scoring when they see a transaction from a foreign acquirer for an unfamiliar merchant. The most effective solutions are: implementing 3DS2 to provide the authentication signal the issuer needs, ensuring you have the correct payment method configuration for your target markets, and confirming that your gateway is transmitting all available transaction data elements in the authorisation request.
Do I need separate merchant accounts for each country I sell into?
Not necessarily. A single well-configured merchant account can process transactions from customers in multiple countries. For very high volumes in specific markets, adding in-region acquiring can improve authorisation rates, but most merchants start with a single account and expand to local acquiring only when volume data justifies it.
What is a cross-border fee and how can I minimise it?
A cross-border fee is applied by Visa and Mastercard when the merchant's acquirer and the cardholder's issuer are in different countries. It is part of the scheme fee component of IC++ pricing. Minimising cross-border fees requires using an acquirer in the same region as the majority of your customers. For EU merchants primarily serving EU customers, a European acquirer minimises cross-border fees. For merchants with global customer bases, regional acquiring relationships are the long-term solution.
You might also like
High Risk Payment Gateway
Secure payment processing for high-risk industries with multi-acquirer routing and chargeback protection.
Small Business Payment Solutions
Transparent IC++ pricing, free Smart POS terminal, and 24-hour activation for small businesses.
E-commerce Payment Integrations
One-click plugins for Shopify, WooCommerce, Magento, and PrestaShop with full API access.
Optimize your payments today
RoxPay processes cross-border payments in 40 plus circuits with 3DS2, multi-currency support, and IC++ pricing from 0.45%. PCI DSS Level 1 certified, settlement to any SEPA bank in 24-48 hours.
✓ No monthly fixed costs · ✓ Activation in 24 hours · ✓ Dedicated technical support
