Features
Applications & countries
The container for everything you build, and where you turn it on per market.
An Application is your account's top-level container — one Application per
product or business you run on PaymentGateway. A Country is a market you've
switched on inside that Application (e.g. TH, US) — every other feature
(customers, products, charges…) lives inside one Country.
How it works
- You create an Application once. It holds your team members and their roles.
- For each market you sell in, you add a Country. Each Country has its own currency, pricing table, and a default payment provider (Stripe, Omise, a local bank rail…) that requests in that country route through.
- Retrieve an Application, or list every Country inside it.
- Provider credentials (API keys for Stripe, Wise, etc.) are configured per
Country, not per Application — a
THcountry and aUScountry can use completely different providers. - Almost every API request is scoped to one Application + Country, usually via
the active session or an
X-Countryheader.
One Country = one default provider. If you need two providers in the same market (e.g. cards via Stripe, QR via a local rail), the routing still happens per Country config — see Providers.
Common use cases
- Launching in Thailand first, then adding a
USCountry later without touching your Thai setup. - Inviting a teammate and giving them a limited Role so they can view charges but not issue payouts.
- Running test data and live data side by side — every Country has both a test and a live space (see Core concepts).