Opening a new market: the payments playbook. 6 chapters and a final quiz.

Chapter 1. A country's payments profile.

A country's payments profile is a one-page document, written, sourced, and dated, that answers five questions. You draft it at the start of the project, before choosing a provider and before the first technical meeting. Launches that fail start from somewhere else: the list of methods offered by the incumbent provider, which describes a commercial offering, not a market. Each of the five answers opens or closes contractual options. A wrong answer costs weeks.

The five questions, in this order

• Who regulates, and who operates? They are not always the same body. The regulator writes the rules; the operator runs the rail and publishes the technical documentation your teams will work from.
• Which rails actually exist? Cards, bulk credit transfers, instant payments, interoperable QR, mobile money, and cash vouchers. A rail that has been announced is not necessarily in use, and a rail in use is not necessarily open to a foreign company.
• Is there a domestic card scheme, and is its use mandatory? A domestic scheme changes interchange, routing, and sometimes whether your international cards are accepted at all.
• Which currency, and which foreign exchange regime? This determines how long it takes and how much it costs to bring the money home, and sometimes whether you can do it at all without a local entity.
• Who needs a license? The question is never “Am I a fintech?” but “Who takes possession of the funds?” The answer determines whether your launch takes 3 months or 18.

Chapter 2. Choosing local methods: usage, not the catalog.

Selecting a market's payment methods means choosing a subset of the available catalog, with measured usage in the country as the filter. Large international providers list catalogs of several dozen methods, and each one you enable is a separate decision. Every method you enable costs an integration, a round of testing, a reconciliation line, a refund flow, and support training. A launch therefore keeps the two or three methods that carry most of the usage, plus the one that unlocks a segment you would otherwise lose.

Three sources, three truths, and only one that applies to you

• The provider's catalog tells you what it can technically route. It says nothing about usage, and it inherently overstates the methods the provider integrated most recently.
• National statistics (central bank, rail operator) show actual usage in the country across all channels. They are the best source available, but they describe the population, not your customers.
• Your own data, once you are live, tells the truth: the actual mix, the first-attempt authorization rate by method, and the checkout abandonment rate. It is the only source that settles the question, and it only exists after launch. Hence the rule: launch small, measure, then expand the catalog.
• The taxonomy trap: market studies often classify as “wallets” apps that are merely an interface to a public rail. In India, apps that run on UPI are counted as wallets, so the country's “wallets” line is mostly UPI. Always read the definition before the number.

Chapter 3. Acquirer, MID, and authorization rate.

Collecting from a consumer in a given country relies on one of three setups. Your choice determines which methods you can offer, your authorization rate, your costs, your tax treatment, and how long repatriation takes. Cross-border acquiring means collecting from abroad under an international acquiring agreement. It is the simplest and fastest setup to put in place, and also the weakest performer of the three. The local entity with domestic acquiring setup requires you to register a company locally and sign a local acquiring agreement. Using a merchant of record hands the sale to a third party, which sells in its own name in the market and remits the sales proceeds to the merchant.

What you actually negotiate in an acquiring agreement

• Settlement currency: being settled in local currency or in your reporting currency does not change the cost. It changes who bears the currency conversion, and at what rate.
• Settlement frequency and timing, and above all how they behave on local public holidays. An unfamiliar market calendar always reveals itself at the worst possible moment.
• Rolling reserve: its rate, its duration, and above all the event that triggers it and the event that releases it.
• Cardholder statement descriptor: the leading cause of avoidable disputes. It must make sense to someone who lives in the country, not to you.
• Merchant category code: it determines interchange, eligibility for certain methods, and sometimes the authorization decision itself.
• Routing: which networks, in what order, and which local requirements apply. As the next section shows, those are not negotiable.
• Exit terms: card token portability, export of mandates and subscribers, notice period. The cost of leaving is negotiated on the way in, never on the way out.

The authorization rate measures the share of transactions the issuer approves out of those submitted to it. The useful measure is taken on the first attempt, by issuer BIN, and by method, against a baseline recorded before switching from one acquiring setup to another. A measure taken at the end of the flow includes retries, and a country-wide aggregate hides the gap specific to each issuer. In a market where cross-border transactions were being declined at scale, a one-point gain in authorization rate is often worth more than the entire fee renegotiation, which will have tied up the team for two months.

Chapter 4. Entity, license, safeguarding, and repatriation.

Taking possession of funds means holding, even briefly, money that belongs to someone else. This criterion alone determines the regulatory status you need at launch, whatever name the country gives that status. A company that sells its own products, with money going straight from the buyer to an account in its own name, remains a merchant. As soon as it collects on behalf of a third party, such as a marketplace seller, a publisher, a service provider, or a subsidiary of another group, it falls within the scope of licensing. The project timeline then shifts to a different scale.

Three thresholds, in the order they kick in

• Purely technical provider: you move data, never funds. No payment license is needed, but security requirements apply, and often data localization rules too.
• Taking possession of funds: you hold, even briefly, money that isn't yours. This is the universal trigger for licensing, whatever the country calls it.
• Ownership or nationality requirements: some markets don't stop at a license; they require the capital or voting rights to be majority-local. You don't meet that threshold with an application. You meet it with an ownership structure, so it has to be addressed very early.

Repatriation is the transfer of funds collected in a foreign market back to the headquarters country. It is the item launch plans most consistently underestimate. Each country has its own foreign exchange regime for it, with its own reporting formalities and authorized intermediaries. In Brazil, foreign exchange is governed by Lei nº 14.286 of December 29, 2021 and Resolução BCB nº 277 of December 31, 2022. The purpose of the transaction must be declared up to a threshold of $50,000, with the reporting responsibility shifting to the authorized institution. The regime explicitly recognizes eFX providers. These firms are not authorized to conduct foreign exchange themselves; they operate under a contract with an institution that is. In India, cross-border business has its own dedicated status, PA-CB, with inbound and outbound collection accounts kept separate from the domestic escrow account. In both cases, the time between local collection and funds becoming available at headquarters is a parameter of the funding plan.

Chapter 5. Tax and invoicing: what blocks go-live.

Payment and invoicing meet two separate requirements: one transfers the funds, the other provides tax evidence of the transaction. Mandatory e-invoicing is a regime in which an invoice legally exists only once it has been validated by the tax authority or an approved third party, sometimes before the sale. A growing number of markets apply such a regime, and the seller loses control over issuing the document. A launch that is technically ready, with acquiring signed and rails connected, stays blocked if the invoicing module does not produce a valid document. Along with licensing, this is one of the two most common reasons a launch slips by a quarter.

Three architectures for invoice control

• You no longer control numbering: the tax authority or the approved third party validates it, and a rejection blocks the sale, not just the bookkeeping.
• The data you collect at checkout changes: the customer's tax ID, tax address, and the nature of the transaction. A checkout flow designed for another market doesn't ask for them.
• Invoice status becomes a state to track, exactly like payment status, with its rejections, retries, and monitoring.
• Archiving has its own retention period and format, separate from your payment logs, and it carries legal weight.
• The timeline is set by regulation: it can't be negotiated or postponed, and missing a go-live date is not a project delay but an inability to invoice.

Payment terms are the time a business buyer has to pay an invoice. They fall under local law, separate from both payments and tax, and they apply as soon as a company sells to other businesses. They drive a launch's working capital needs far more reliably than the seller's own terms and conditions. In the EU, Directive 2011/7/EU caps agreed payment terms between businesses at 60 calendar days, unless expressly agreed otherwise and not grossly unfair, and at 30 days for public authorities. It also gives an automatic right to a minimum recovery fee of €40 for late payment. In the UK, no statutory cap limits agreed terms; the law works through the cost of paying late. The Late Payment of Commercial Debts (Interest) Act 1998 grants interest at 8 percentage points above the Bank of England base rate, plus fixed compensation of £40, £70, or £100 depending on the size of the debt. In India, the MSMED Act 2006 specifically protects micro and small enterprises, with a maximum term of 45 days (Section 15). Beyond that, interest is due, compounded monthly, at three times the bank rate notified by the Reserve Bank of India (Section 16). These three markets take three different approaches: a statutory cap on terms, a late-payment penalty, and protection for one category of business.

Chapter 6. A realistic timeline and the six mistakes that cost a quarter.

A country launch plan, worked backward from go-live, sequences the dependencies between workstreams, then assigns each one a duration taken from the timelines the authorities publish. Delays almost never come from the code. They come from waiting for a license, registering an entity, an incomplete KYB file, or an invoicing module that doesn't produce a valid document. Two regulatory windows give a sense of the lead times imposed. The Reserve Bank of India set December 31, 2025 as the deadline for filing aggregator authorization applications, with non-filers required to cease operations by February 28, 2026. Poland is phasing in the KSeF requirement on February 1, 2026, then April 1, 2026. A planning template imported from another country tells you nothing about these durations, which you have to get from the relevant regulator.

• The cardholder statement descriptor has been read and approved by someone who lives in the country, not by the team that entered it.
• A real end-to-end payment has been completed: local currency, local account, valid invoice issued, refund tested, on every method enabled, including those without chargebacks.
• The first-attempt authorization rate is instrumented by BIN and by method, with a baseline taken before the switch.
• Local disclosure requirements (price, tax, surcharge, return policy, invoice details) have been approved by local counsel.
• Exit terms are in writing before signing: card token portability, export of mandates and subscribers, notice period, and data return format.
• The market calendar is loaded into your systems: local public holidays, settlement windows, year-end cutoffs. Launching the day before a holiday week is a scheduled incident.

Opening a market ends with the first decision made on the merchant's own data, not with the first successful transaction. Thirty days after launch, three metrics provide the basis for that decision. The actual mix compared with the forecast mix shows whether the methods you enabled are the ones customers use. The first-attempt authorization rate by BIN shows whether the acquiring setup is holding up. The reconciliation gap between settlements received and orders recorded shows whether the accounting chain is keeping up. Until these three metrics are instrumented, the country is connected but not open: transactions go through, but no decision can be based on numbers.