Bill in your customer’s currency: the setting that decides which payment methods they see

Most stores set one currency, usually USD, and move on. It looks harmless: the card network converts anyway. But on a hosted checkout the invoice currency decides more than the number on the screen. It decides which payment methods are offered at all.

Local methods follow the local currency

• A Swedish customer billed in SEK can be offered Klarna. Billed in EUR or USD, they are not.
• India’s UPI accepts nothing but INR. An invoice in USD simply has no UPI option.
• The same pattern holds for bank-transfer methods across Europe: they are tied to the money the bank account holds.

So a USD-only store is not just showing a converted price. It is removing the way many of its customers would rather pay, and they rarely say why they left.

Which currencies Norpo accepts

The checkout accepts USD, EUR, GBP, CAD, AUD, CHF, SEK, INR and JPY. Whatever the customer pays in, you settle in USDC, so billing in nine currencies adds no accounting on your side.

How to set it

1. Detect the visitor’s country, or let them pick a currency, and show prices in it.
2. Send that currency in the currency field when you create the order, together with the local amount.
3. Keep your reference and your own record of the price. Settlement arrives in USDC either way.

{
  "amount":   499,
  "currency": "SEK",
  "wallet":   "0x…",
  "reference": "order-1042"
}

A quick check before you ship

Open your own checkout from a VPN in two or three of your main markets, with the invoice in the local currency, and look at what is offered. It takes ten minutes and usually explains a conversion gap better than any analytics dashboard. More integration details are in the docs.