Use case summary
Checkout detects each customer's location, switches to their language, shows the local payment methods first, and prices in their currency based on FX rules you set. You decide which methods appear per market from the checkout builder. Result: one checkout serves every market, and adding a market is a configuration change instead of a release.
- Payment Manager
Why a checkout built at home underperforms abroad
A checkout designed for the home market travels badly. English labels, a card form first, prices in the seller's currency. It works where it was built and quietly loses money everywhere else.
Customers notice immediately. 99% of cross-border shoppers say they want to pay with their preferred local payment method, and merchants that don't offer one risk losing more than half of potential buyers.
The usual fix is a front-end project per market. Translations, a method picker, and a currency display, each scheduled against a release cycle. The checkout ends up permanently behind the markets the business is already selling into.
How payment localization works as configuration
Corefy handles localization in the checkout layer. You configure what each market sees, and the same checkout adapts per customer.
- 1
Switch localization on in checkout
Checkout identifies the customer's geolocation, switches to the right language, and displays local payment methods first. It supports 25 languages and 200+ currencies, and the country can also be passed as a parameter if you already know it.
- 2
Decide which methods each market sees
Method conditions control exactly which options appear by geography, currency, or device. In the checkout builder, you activate any combination of global cards, local methods, and wallets from a library of 800+ payment methods available through connected providers, per checkout, with no new integration.
- 3
Order them the way the market expects
Method prioritization reorders the page so the most relevant option sits first for that market or buyer profile. Personalization surfaces the methods a returning customer has already used.
- 4
Price in the customer's currency
FX rules set the currency pairs you support and where each rate comes from, so the customer sees a clear currency choice and the full total before they commit, on a rate you configured.
- 5
Match the local look, not just the local language
Language packs let you upload your own translations instead of accepting defaults, down to the label on the pay button. White-label styling keeps the page on-brand, with light, dark, or system display per checkout.
- 6
Change a market without a release
Everything above is set in the no-code checkout builder. Adding a language, reordering methods, or opening a currency is a configuration change your payment team makes directly.
What you get
Your payment team changes what each market sees without waiting on a release.
A checkout that fits every market
Language, methods, and currency adapt to the customer without a separate build.
Market changes in hours
Reordering methods or adding a language does not wait for a front-end release.
Fewer drop-offs at the last step
Customers see a familiar method, in their language, priced in their currency.
One checkout to maintain
Every market runs on the same page and the same integration.
How Grand Cru Concepts added Canada without touching its checkout
Grand Cru Concepts is a software publisher operating high-volume consumer products across the US and Canada. It launched on Corefy's hosted checkout specifically to go live without building a custom payment interface first, and added its own method selection UI later once the stack was stable. Canada was onboarded after the initial US launch, bringing Interac e-Transfer alongside cards, ACH, Google Pay, and crypto. Each addition followed the same path: connect credentials, configure routing, go live. As of May 2026, the stack runs at a 79% approval rate with no declines attributable to platform instability.