Payments.
Orchestrated.
Connect once. Route payments across providers, countries and payment methods through one infrastructure layer — with failover, reconciliation and a decision trail for every transaction.
One infrastructure layer between your platform and the payment providers.
Your systems talk to NATIO. NATIO talks to acquirers, banks, PSPs and local payment methods, decides where each payment goes, retries safely when a provider fails, and reports what happened.
- Idempotency-Key
- natio_sk_test_ / natio_sk_live_
- Natio-Signature webhooks
- Acquirers
- Banks
- PSPs
- Local payment methods
Create a payment. NATIO does the rest.
A single request carries amount, currency and payment method. Risk evaluation, routing, provider calls and failover happen inside the request; the response tells you the outcome and the route taken.
Amounts in minor units
10000 is 100.00 USD. No floating point, no ambiguity across currencies.Payment method as a type or a token
"card", or a stored payment method reference issued by a PCI-compliant provider. NATIO never receives card numbers.Route object on every payment
next_action for asynchronous rails
next_action; completion arrives by webhook.curl https://api.natio.me/v1/payments \
-H "Authorization: Bearer natio_sk_test_..." \
-H "Idempotency-Key: order-1001" \
-H "Content-Type: application/json" \
-d '{
"amount": 10000,
"currency": "USD",
"payment_method": "card",
"country": "US",
"reference": "ORD-1001"
}'{
"id": "pay_7Kq2mN9xR4vL8wP1tY3z",
"object": "payment",
"status": "successful",
"amount": 10000,
"currency": "USD",
"route": {
"provider": { "code": "demo_acquirer_b", "name": "NATIO Demo Acquirer B" },
"attempts": 2,
"rule": "Cards → Acquirer A, fallback Acquirer B"
},
"next_action": null
}Rules decide. Failover protects. The timeline explains.
The orchestration engine turns provider connectivity into a policy you control: where a payment goes, what happens when a provider declines or fails, and a complete record of every decision.
Routing rules
Retry and failover
Transaction timeline
Built for the teams who run payments every day.
Engineering integrates once. Finance and operations get a single place to monitor transactions, reconcile provider reports, follow settlements and compare providers.
Transaction monitor
Reconciliation
Settlement visibility
Analytics
Designed like the systems it connects to.
NATIO is a technology layer between merchants and licensed payment providers. It is engineered to be predictable, verifiable and narrow in scope.
Encryption at rest and in transit
Provider credentials and webhook secrets are encrypted with AES-256-GCM; all traffic is TLS.
Key hashing
API keys are stored as SHA-256 hashes and shown once. Prefixes identify keys without exposing them.
Role-based access control
Merchant users and operators act under explicit permissions; every action is attributable.
Audit logs
Configuration changes, manual reviews, refunds and resends are written to an immutable audit trail.
Signed webhooks
Every event carries a Natio-Signature header (HMAC-SHA256 with timestamp) so you can verify origin and freshness.
PCI scope minimisation
Card data never touches NATIO. Hosted pages and tokenisation are performed by PCI-compliant providers.
Idempotency
Idempotency-Key on every mutating request: retries replay the original response instead of creating duplicates.
No custody
NATIO does not hold or take customer funds. Providers settle directly with the merchant.
For teams operating across markets.
If your business accepts or sends payments in more than one country, through more than one provider, or via more than one payment method, orchestration replaces a growing set of integrations with one.
Fintech companies
Embed payments and payouts behind your own product without maintaining a provider integration per market.
Marketplaces & platforms
Collect from buyers across rails and pay out to sellers through licensed providers, with one ledger view.
E-commerce
Cards, wallets, bank transfers and local methods under one checkout contract, with automatic failover.
Subscription businesses
Stored payment method references, manual capture and retry logic for recurring charges.
Travel
High-value, multi-currency transactions where routing by amount, currency and provider limits matters.
Digital services
Fast integration, deterministic routing and full visibility of every attempt for support teams.
International merchants
Add countries and payment methods by configuration rather than by new integrations.
Supported payment method types. The architecture is prepared for connecting global and local providers behind each of them.
Ready to connect once?
Create a sandbox account, run test scenarios against demo providers and see routing, failover and reconciliation end to end.