Cross-border expansion looks simple on a product roadmap. The API already works, so a second country should only need a new currency and a launch date. In practice, the problems start well away from the code. Most of them sit in treasury, compliance and operations, where a home market had hidden them for years.

So we asked industry leaders one question: what breaks first when a payments company expands into a second country? We wanted specifics on licensing, FX, settlement and local rails. Three respondents answered, and their replies point to the same weak spot. In a cross-border expansion, the operating model breaks before the technology does. Below, we set their answers against the latest rules and market data.

Licensing decides whether a cross-border expansion can start

The first gate is permission. Without it, a cross-border expansion cannot legally start. Inside the EU, a payment or e-money licence can be passported to other member states. Outside it, that shortcut disappears. Since Brexit, an EEA firm needs its own UK authorisation, and the FCA has closed the transitional regimes that once filled the gap.

Fintechbits saw this play out recently. Berlin card issuer Pliant served UK clients through a regulated partner. Then it won its own FCA e-money authorisation this month. A partner can speed up a cross-border expansion, but it adds a dependency and shares the margin.

“We match merchants, including high-risk sectors, with acquirers and payment providers, so cross-border expansion is a big part of what we look at.

The licence is usually the first surprise. An EU licence can be passported across the EU, but the moment a company adds a market outside it, like the UK, it often needs a local licence or a local entity. Teams tend to find that out after the product work is done.

The second thing is that payments quietly turn cross-border. Visa ties an online merchant to the country where the business is really run. So if you sell into a new market without local acquiring, issuers there see foreign transactions. They decline more of them, and outside the EU the fees are higher too. Lower approval rates are the usual result.

Then there’s settlement and FX. Customers pay in one currency, the merchant gets paid in another, and the conversion margin adds up. Acquirers also tend to hold a reserve when there’s no processing history, which ties up cash right when the company needs it to grow.

Local payment methods matter more than people expect, too. In Brazil, Pix has overtaken credit cards in online spending, and since 1 October 2026 providers of international payment services there need authorisation from the Central Bank.”

Adrian Begic, Founding Engineer, Ecompayer

Approval rates and fees shift without local acquiring

His answer covers the most ground, and his points on routing deserve attention. Many teams plan a cross-border expansion around one acquirer at home. That keeps contracts simple, yet it often hurts results abroad. Under Visa rules, the merchant location follows the principal place of business. Without a local acquirer, every sale in the new market counts as cross-border. As a result, issuers decline more often and fees climb.

The fee gap is large. Online interchange on cards from outside the EEA is capped at 1.15% for debit and 1.5% for credit. Those caps come from commitments Visa and Mastercard extended to 2029. By contrast, the caps for card-present payments sit at just 0.2% and 0.3%. So a cross-border expansion that relies on remote acquiring pays more on every online sale. That is why some processors now chase their own licences. Checkout.com, for instance, went live with direct US acquiring under a Georgia charter in September.

Settlement is where cash runs out

Once the licence is in place, the treasury team usually feels the strain next. This is the part of a cross-border expansion that rarely shows up in a pitch deck. Settlement timing changes from one country to the next. Card funds may arrive in two or three days in one market but far later in another. In Brazil, for example, domestic card settlement often runs to 30 days because so many purchases are split into instalments. Acquirers may also hold back part of each payout as a reserve while a new merchant builds a track record.

“Settlement timing is where it breaks first. It creates a working capital gap that most payments companies never put in their first financial model. Teams treat local rail integration as a software milestone, but the real damage shows up in treasury. At home you know your float and settlement timing by instinct. In a cross-border expansion, the gap between authorisation and money landing in your account can stretch to several business days because of batch windows and local holidays.

That gap forces you to put far more capital into the local entity just to keep the service running. If you promise instant payouts but the rail settles on T+3, you are giving merchants an unsecured advance. At scale, that eats cash faster than revenue replaces it. It is a liquidity risk, and it can freeze operations in your busiest weeks.

Reconciliation is the next thing to go. A payment authorised at midnight in one time zone can settle under a different date on the bank statement, and the backlog builds fast. Settlement files rarely share standard identifiers, so you need a layer that cleans up local quirks like tax withholdings and fees. Without it, the team ends up living in spreadsheets.”

Abhishek Pareek, Founder and Director, Coders.dev

Reconciliation and FX keep eating margin

Reconciliation is the quiet cost of any cross-border expansion. Standards are improving, but only in parts of the chain. Swift completed its switch to ISO 20022 for cross-border bank payments in November 2025. Even so, card acquirer reports and local payment method files still arrive in different formats. Real-time rails are also spreading, as Citi instant payments on Swift show. However, faster rails do not fix mismatched data.

FX adds a slower leak. Spreads, rate locks and late settlement each take a small cut, and together they add up. Meanwhile, licensing work keeps going long after launch day, with new reporting and safeguarding checks to run.

“The first thing that usually breaks isn’t the payment API. It’s the operating model around it.

Licensing is often the biggest early constraint. A model that works at home may need a local licence, a regulated partner, new KYC and KYB checks, data rules, reporting, or limits on how customer funds are held.

FX causes trouble too. You need to know who carries the FX risk, when the rate is locked, how spreads are worked out, and what happens when settlement takes longer than planned. Small FX assumptions can turn into real margin loss at scale.

My advice is to treat a cross-border expansion as a new payments operation, not a map extension. Work through licensing, banking partners, FX, local rails, settlement, reconciliation, compliance and customer support before you fix a launch date. The biggest mistake is assuming the payments setup travels just because the product does.”

Ahmed Yousuf, Financial Author, CoinTime

Local payment methods change the checkout

Card-only checkout can cap growth in some markets. In Brazil, Pix took 42% of e-commerce spending in 2025, ahead of credit cards at 41%, according to PCMI and EBANX data. Therefore, a cross-border expansion into Brazil that skips Pix leaves a large share of buyers out. The same logic applies in markets where bank transfers or wallets lead.

Brazil has also tightened the rules for foreign providers. Under Central Bank Resolution 561, only authorised firms can offer international payment services from 1 October 2026. In addition, those firms can no longer settle with overseas partners in stablecoins or crypto. Unauthorised providers already operating there have until 31 May 2027 to apply.

What to watch next

Taken together, the answers suggest a simple order of work for any cross-border expansion. None of our respondents put the API first. First, secure the licence or partner. Next, model settlement timing and reserves before promising payout speeds. Finally, build reconciliation before volume arrives, not after.

Smaller teams can also stage the work. Some start with a regulated partner, prove demand, and then apply for their own licence. That route costs margin, but it buys time to learn the local market. A staged cross-border expansion also gives treasury real settlement data before the bigger bets.

Several dates matter for teams planning a cross-border expansion in 2027. Brazil’s eFX application window closes on 31 May 2027. In the UK, the Payment Systems Regulator still plans a cap on UK-EEA online card fees. Above all, founders should treat the second country as a new business with its own cash needs. The product may travel well, but the money behind it rarely does.

FintechBits covers payments, banking and fintech developments for readers in the US and UK. This article is for information only and is not financial advice. Views expressed are those of the FintechBits editorial team.