Selling to the World
Selling to the World is the payment setup where a customer can see and pay in one currency while the merchant reports, accounts for, and receives funds in another. Checkout currency, transaction currency, conversion rate, fees, reporting currency, and payout currency are separate choices in the payment flow.
International selling creates a mismatch between what feels local to the buyer and what is operationally manageable for the merchant. A customer in India may trust a checkout priced in rupees, while the business wants accounts, tax reporting, and bank deposits in dollars. Treating those as the same thing leads to confusion when the dashboard shows a dollar sale for a purchase the buyer never saw in dollars.
The mechanism is a chain of records and movements, not a single magical currency. The checkout shows a local amount, the payment is authorised in a transaction currency, and the processor records the value on its ledger. If needed, it applies an exchange rate, calculates gross and net amounts, subtracts fees, and later pays the merchant in the configured settlement currency.
The trade-off is that each separation adds places where money can move slightly differently from the product price. Exchange rates, conversion margins, card network rules, processor fees, refund timing, and chargebacks can all affect the amount eventually settled. The honest answer to “what will I receive?” is “it depends”, mainly on the processor, currency pair, settlement settings, fee model, and timing.
Engineers meet this in payment provider APIs, dashboards, reconciliation jobs, invoices, and accounting exports. Look for fields such as amount, currency, presentment currency, exchange rate, balance transaction, fee, net amount, reporting currency, and payout currency. A common bug is assuming one currency field explains the whole payment. Correct systems store and display each monetary amount with its own currency.
Common questions
- Does the checkout currency have to match the payout currency?
- No. This is the common misunderstanding. A processor can show the buyer a local price, authorise and record the payment, convert it internally or through partners, then settle the merchant in a different currency. Whether this is available depends on the processor, merchant country, supported currencies, and account configuration.
- How can a rupee purchase appear as a dollar sale in reports?
- The buyer is charged in rupees, but the processor creates an internal record in the merchant’s reporting or settlement currency. It uses an exchange rate to translate the value, then shows the gross amount, fees, and net amount in dollars. The customer experience and the merchant ledger are related but not identical views.
- What should engineers store for multi-currency payments?
- Store money as amount plus currency at every step: displayed price, charged amount, converted amount, fees, refunds, disputes, and payout. Do not overwrite the original customer-facing amount with the settlement amount. Reconciliation becomes much easier when the system preserves the exchange rate, fee breakdown, processor identifiers, and payout linkage.