What payment localisation covers
- Currency: prices and charges in the buyer's own currency
- Payment methods: the local schemes, wallets and bank transfers buyers expect
- Acquiring: processing through an acquirer in the buyer's country
- Language and format: address fields, tax identifiers and date formats
- Authentication: the flow that the buyer's bank and local rules expect
- Receipts and refunds in the form the market expects
How payment localisation works
A checkout works out the buyer's country from the delivery address, the card's BIN or the device, and builds the page for it. The Netherlands, Poland and Brazil are common examples: iDEAL, BLIK and Pix are everyday ways to pay online there, and a card-only checkout loses buyers who expect them.
Behind the page, the payment is routed to a local acquirer or to the method's own provider, and the funds are settled in a currency the merchant chooses.
Why payment localisation matters to a payments business
For a PSP or a gateway, each market is an integration, a contract and often a settlement flow of its own. Serving merchants that sell across borders therefore depends on how many methods and local acquirers the platform already connects, and on a ledger that keeps each currency apart.
Where Payment localisation shows up in a platform
Modules that do the work
- CheckoutA hosted checkout for cards, wallets, bank payments and crypto, routed to the best provider.
- Card acquiringCard acceptance on the phone, in store and online, through the acquirer you choose.
- FXCurrency conversion with live rates, your margins and the liquidity provider you choose.