Finance platform
One integration.
Every acquirer you add later.
Atmora Pay sits between your checkout and your acquirers, routing each transaction on issuer, amount, method and rolling success rate. Adding a new acquirer becomes a configuration change and a week of shadow traffic, not another quarter of engineering.
- Cloud
- Private cloud
- Hybrid
Overview
Payment orchestration: one integration, several acquirers, settlement that ties to your ledger.
Atmora Pay accepts a payment intent through one API and decides the rest: which acquirer, which method, which retry schedule, based on BIN, amount band, currency and success rates measured over a rolling window. The card vault holds credentials centrally, so routing can change without a re-integration and without asking customers to enter their card again. Refunds, disputes, payouts, settlement files and reconciliation share the same object model rather than arriving as four exports that finance stitches together by hand.
This is an orchestration layer, not an acquirer. Atmora Tech does not hold merchant funds or issue a merchant identification number, and your commercial relationships stay with the acquirers you already use. If you process on a single gateway in a single country and have no plan to add another, orchestration adds a hop for no gain. The platform earns its place from the second acquirer onwards, or at the point where recurring collection and settlement reconciliation start eating a finance team's week.
- +2.9 pp
- Card authorisation rate after routing and retry tuning at Tinsmith Retail
- 41%
- Recurring collections recovered from soft declines
- 6 days
- Elapsed time to put a new acquirer on live traffic
- -73%
- Finance hours per month spent on settlement reconciliation
Modules
What ships in the box
- Routing and failover engine
- Card vault and network tokens
- Subscriptions, mandates and dunning
- Refunds, disputes and evidence
- Settlement, payouts and reconciliation
- Sub-merchant onboarding and underwriting
Integrates with
- Stripe
- Adyen
- Razorpay
- PayU
- Cashfree
- NPCI UPI
- SAP S/4HANA
- NetSuite
Capabilities
What it does
Routing rules a finance lead can read
Route on BIN, issuer, amount band, currency, method and rolling success rate. Rules are versioned and testable against replayed production traffic before they touch a single live payment.
Retries tuned per decline code
Soft declines retry on a schedule derived from the issuer response; hard declines never retry at all. Attempt counts and intervals stay inside card network rules on retry behaviour.
Network tokens and a single card vault
Card numbers are stored once and referenced by token everywhere else. Network tokens are provisioned and refreshed automatically, so a reissued card stops breaking a recurring charge.
UPI Autopay, e-NACH and card mandates
One subscription object drives all three mandate types, tracks pre-debit notification windows and stops collection the moment a mandate is revoked at the customer's own bank.
Settlement files mapped to your chart of accounts
Payouts break into gross, fee, tax and refund lines against your general ledger codes, exported nightly in a layout your finance team posts rather than re-keys by hand.
In-flight failover between acquirers
When an acquirer's success rate drops below threshold over a rolling five-minute window, traffic shifts to the next in the priority list and returns automatically once health recovers.
Sub-merchant onboarding with underwriting
Sub-merchant records carry KYB documents, risk category and reserve rules. What a merchant may charge for is driven by onboarding status, not by a spreadsheet somebody maintains.
An event stream you can replay
Every state change is emitted as a versioned webhook and retained for 30 days. After an outage a consumer replays from its cursor instead of asking support for a reconciliation file.
Built for
Where this is deployed
Industry
Retail & E-commerce
Storefronts, stock ledgers and fulfilment logic that hold together on your busiest trading day.
Industry
Banking & Financial Services
Payment rails, risk engines and core-adjacent systems built by people who have run them at 03:00 on a settlement night.
Industry
Travel & Hospitality
Booking, offer and disruption systems for operators whose worst day is a fare sale during an outage.
Industry
Telecom & Media
OSS, BSS and delivery platforms that keep working after launch night.
Industry
Education
Student and learning systems that survive enrolment week and the statutory return that follows it.
FAQ
Questions we get asked
- Do we have to move our card data to Atmora Pay?
Only if you want routing choices to be free later. Migration runs as a bulk token import from your current vault or processor, followed by network token provisioning, so cardholders are not asked to re-enter details. A pass-through mode where the acquirer keeps the credentials is also supported.
- What happens if Atmora Pay itself is unavailable?
The client SDK holds a signed direct-to-acquirer fallback configuration refreshed every few minutes. If the orchestration API stops responding, checkout continues against the last known primary acquirer and those transactions are backfilled into the platform once it returns.
- Is this useful with one acquirer?
Rarely. With a single acquirer and no recurring billing you are paying for a hop that adds latency and another dependency. The vault, mandate handling and settlement reconciliation still help some single-acquirer merchants, but we will say so plainly rather than sell you the routing engine.