We build the layer that makes payment providers interchangeable.
NATIO is a payment orchestration company. We build the infrastructure that lets a business integrate once and then change providers, add markets and add payment methods as configuration — without rewriting its checkout, its ledger or its reporting each time.
Payment infrastructure is fragmented, and the cost lands on the merchant.
Every provider has its own API, its own status vocabulary, its own failure codes, its own report format and its own settlement rhythm. A business operating in more than one market ends up maintaining all of them.
Orchestration is the answer to a structural problem, not a feature. When provider connectivity is a layer rather than a set of point integrations, adding a country is configuration, a provider outage is a fallback instead of an incident, and the question of which provider performs best is answered from your own data.
We are building that layer deliberately narrowly. NATIO does not hold funds, does not touch card data and does not compete with the providers it connects to. It does one thing: decide, execute and record — for every payment, every payout and every provider, the same way.
- Engineering
- A new market or method means another integration, another set of edge cases, another retry policy to reason about.
- Approval rates
- Without failover a single provider incident becomes lost revenue, and without comparable data there is no basis for moving traffic.
- Operations
- Support reconstructs what happened from provider dashboards; finance reconciles incompatible reports by hand.
- Leverage
- The harder a provider is to replace, the weaker the merchant's position in every conversation about pricing and terms.
The constraints we chose.
These are design decisions, and they are the reason the product looks the way it does.
Orchestration, not intermediation
NATIO is a technology infrastructure layer. It decides where a payment goes and records what happened; the regulated act of processing stays with the licensed providers connected to the platform.
Provider neutrality
The platform is not a front end for one provider. Adapters normalise every connection to the same interface, and routing rules belong to the merchant — including the rule that moves volume away from a provider.
No custody
NATIO does not hold or take customer funds. Money moves between the merchant and licensed providers, which settle directly. That constraint shapes the product: balances and settlements are reported, not held.
Minimal PCI scope
Card data never touches NATIO. Entry and tokenisation happen at PCI-compliant providers through hosted pages, which keeps a merchant integration in the smallest assessment scope.
Auditability
Every routing decision, risk decision, provider attempt, retry and configuration change is written down and readable afterwards. A payment platform that cannot explain itself is not finished.
Determinism before intelligence
Rules first, transparent scoring second, learned ranking only when there is enough of a merchant's own data to justify it — and always with the inputs on the record.
A phased build, described honestly.
We say what exists today, what is being built next, and what would depend on conditions outside an engineering roadmap.
The orchestration technology layer
One REST API for payments, refunds and payouts; the orchestration engine with risk evaluation, rule-based routing, retry and failover with double-charge protection; the provider adapter architecture; webhooks; reconciliation, settlement visibility and analytics; the merchant dashboard; and a sandbox with demo providers that reproduce real failure paths.
Breadth of connectivity
More provider integrations across acquirers, PSPs, banks and local payment methods, and direct provider report imports for reconciliation in place of file uploads. The architecture is prepared to connect global and local providers; each connection is a commercial and technical integration, and we describe one only once it exists.
Deeper routing and operations
Richer routing inputs and a learned ranker on top of the existing scoring function, more operational tooling for finance and support teams, and deeper settlement reporting. The extension points are already in the engine: the ranking function takes candidates, statistics and context, and returns an ordered list.
Regulated entities — a possibility, not a promise
In the longer term NATIO may seek its own licences and operate regulated entities in selected markets. This would happen only if and when the relevant authorisations are obtained. Until then — and today — NATIO is not a bank, an acquirer, a payment institution or an e-money institution, and every regulated service is performed by the licensed providers connected to the platform.
What NATIO is, in plain terms.
Payments attract loose language. We would rather be precise, including about what we are not.
NATIO is
- A technology company
- We build software: an API, an orchestration engine, provider adapters and the operational tooling around them.
- A payment orchestration platform
- One integration for the merchant, connectivity to multiple providers, and the routing policy that decides between them.
- An infrastructure layer
- Positioned between merchant systems and licensed payment providers, with no role in the commercial relationship between them beyond connecting it.
NATIO is not
- A bank or an acquirer
- We do not acquire transactions, issue instruments or provide accounts.
- A payment institution or EMI
- We do not perform regulated payment services and do not hold client money. Providers connected to the platform do, under their own authorisations.
- A custodian
- Funds move between the merchant and licensed providers, which settle directly. NATIO reports settlement data; it does not hold it.
Who we build for.
Teams that have outgrown a single provider, or expect to.
Engineering teams
Finance and operations
Decision makers
Tell us about your payment stack.
Markets, methods, providers and the parts that currently hurt. We will tell you plainly whether orchestration helps, and what it would take.