bill_line explaines cross-border payments: why the problem is not the provider
Expanding into new markets is a straightforward business decision. No matter what your business is about — you do this to step into the next level. So, all your resources must be full and prepared for your expansion to turn into the system — not the leap of faith. The payment infrastructure is a major part of it. It’s required to support that expansion every step of the way.
Most businesses discover this the hard way. They add a new geography, route transactions through their existing PSP and eventually watch approval rates underperform. Not because the PSP is bad. Yes, it may be, but this is a small picture to look into. Main reason is because no single provider has optimal acquiring relationships, local payment method coverage, and competitive FX rates across every corridor simultaneously. The problem is not the choice of provider. It is the assumption that one provider can handle everything.
That’s why bill_line team is online. In this article we’ll explain why and how this is the structural reality of cross-border payments, where the complexity is not a feature gap in any individual PSP, but a property of the problem itself. And solving it requires a different layer of infrastructure — which bill_line is very keen to share with you.
Where the cost actually comes from
Global cross-border payment flows exceeded $179 trln in 2024, according to the McKinsey Global Payments Map. And the average global cost of a cross-border remittance in Q1 2024 remained above 6%, per the Financial Stability Board’s annual progress report — more than double the 3% benchmark the G20 set for 2030.
What makes these costs hard to manage is that they aren’t visible as line items. A merchant reviewing their PSP fee schedule sees a processing rate. Not the exchange margin, the correspondent chain fees or the cost of a failed transaction reversing through the same intermediaries.
So, the simple thesis here is a hard-to-swallow pill: cross-border cost optimisation isn’t a procurement exercise. It’s a routing and infrastructure exercise. And here’s where our solution steps into the light. bill_line specialty is complex infrastructure solutions for business that have a need to step outside their framework and build a bigger one.
The conversion problem: one checkout doesn’t fit all markets
Cost erosion is one dimension. Conversion loss is another — and it is visible immediately when a merchant enters a new market without adapting their payment stack.
Digital wallets account for over 49% of global e-commerce transactions. But dominant wallets in one market have near-zero penetration in another.
Each market has it’s own pace. For example, our LATAM partner Pix processed over 60 billion transactions in Brazil in 2024. Card preference, open banking adoption and BNPL penetration differ across 20+ European markets. A checkout optimised for one geography is suboptimal for another by definition.
The conventional response for generic merchants and their PSPs is adding local payment methods through the existing PSP. But this temporal solutions runs into a structural limit. A single PSP’s integrations reflect its own acquiring relationships and contractual priorities. Coverage gaps manifest as declines or unsupported methods, with no visibility for the merchant. McKinsey’s 2024 Global Payments Report notes that 23% of UK SMEs regularly use fintechs and nonbank providers for cross-border payments specifically because legacy infrastructure cannot cover what their customers expect at checkout.
Solving this requires routing each transaction to the provider best positioned to approve it in that corridor — and retrying automatically through an alternative when the first fails. That’s not a feature any single PSP can offer. It is what an orchestration layer exists to do. bill_line has the tools you require for that. Contact us and get a quick demo.
Compliance: five markets, five parallel environments
Every cross-border transaction carries a compliance dimension that compounds with each geography added. PSD2 and Strong Customer Authentication govern 3DS across the EU and EEA. AML and KYC requirements differ between markets. Data localisation rules in some jurisdictions require transaction data to be processed within national borders. Subscription businesses face cardholder notification requirements that aren’t uniform globally.
The progress cross-border payment report we mentioned earlier identifies mismatched compliance requirements as one of the primary sources of friction in international payment flows, causing payments to stall at beneficiary banks. For a merchant operating across five markets through a single PSP, a compliance failure in one corridor affects the entire stack. Why? Because there’s no layer managing these environments independently of one another.
bill_line enters: what the infrastructure layer changes
The case for payment orchestration in cross-border isn’t about feature comparison. It’s about what becomes possible when routing, provider selection, and reconciliation are managed above individual PSPs rather than within any one of them.
A transaction entering the orchestration layer is evaluated against real-time performance data — approval rates by corridor, provider availability, cost per route — and directed to the provider best positioned to process it. If that provider declines, retry logic routes to the next. Exchange conversion happens at the layer with visibility across multiple providers, not locked into a single provider’s rate. Reconciliation is normalised across the stack, so finance teams see one source of truth instead of aggregating reports from multiple dashboards.
This is bill_line core infrastructure: routing and cascading logic across connected providers, multi-currency settlement across 50 countries, and a reconciliation layer that sits above individual PSP relationships. If you have questions about cross-border payment infrastructure or want to understand how bill_line handles your specific markets — be sure to get in touch with our sales team!
