Issuing
Acquiring · Issuing · Switching
One platform. Every payment.
momentPay builds the processing core that banks, processors, PSPs and fintechs run their card businesses on — merchant acquiring, card issuing, and the real-time switch that connects both to the networks.
25,500+ TPS
Throughput in a production configuration
<15 ms
Authorization response at the 99th percentile
99.99%
Target platform availability
1M+
Concurrent sessions supported
The platform
Seven products, one connected platform
From the billing counter to the general ledger — capture, switching, issuing, acquiring, risk and reconciliation are built as one system, so you deploy the parts you need without carrying the operational weight of the parts you do not.
Acquiring
Switching
Fraud & risk
In-store collection
Online collection
momentPay Orchestrate
Sends the payment request, accepts it on every digital channel and routes it through the aggregator that clears it best — payment links, e-commerce, apps and marketplaces on one platform.
Explore momentPay Orchestrate
Reconciliation
Architecture
Both sides of the transaction, on the same engine
Every card transaction has an acquirer standing behind the merchant and an issuer standing behind the cardholder. Conventional estates run those as separate platforms with separate integrations. momentPay runs them as mirror roles on one protocol engine.
- Acquiring takes a transaction from a terminal or checkout page, works out which network owns the card, and dispatches it in that network's exact wire format.
- Issuing does the mirror job: it receives a transaction the network is routing to the issuer and hands it to an authorization decision service.
- Shared core handles routing, message translation and persistence for both directions, so a new scheme is a configuration exercise rather than a rebuild.
Acquiring side
Terminal & checkout ingressAccepts card-present and card-not-present traffic
3-D Secure authenticationCardholder step-up before authorization
Authorization & persistenceRecorded before dispatch, reversed on ambiguity
Issuing side
Issuing listenerOne inbound connection per card network
Decision service interfacemomentPay Shield, or your existing host
Response encodingMapped back to each scheme's response codes
Shared core — routing engine · network message translation · direct network API adapters · HSM, monitoring & configuration
Why momentPay
Engineered for institutions that cannot go down
Multi-protocol native
ISO 8583 card processing and UPI/QR digital payments run as first-class workloads on one platform, not as a bolt-on module bridged to a second system.
Actor-model concurrency
Built on Elixir and the OTP runtime. Each connection and transaction runs as an isolated, supervised process, so a single failure is contained and recovered automatically.
Fail closed, reverse on ambiguity
A transaction is written to durable storage before it is dispatched. A timeout is treated differently from a decline, and triggers an automatic reversal rather than an assumption.
Hardware-protected keys
PIN blocks and cryptographic keys are handled through a hardware security module, never held in application memory in the clear.
Configuration, not rebuilds
A network's connection details, routing rules and message format are data rather than code. Extending coverage never touches another network's path.
Scales without re-architecture
Additional nodes join the cluster and load-balance automatically, so growth in transaction volume is an infrastructure change rather than an architectural one.
Network connectivity
Connected to the networks your business depends on
Each network is reached through whichever interface the relationship requires — a direct ISO 8583 connection over TCP, or a direct-to-scheme REST API secured with mutual TLS. Both run through the same protocol engine.
EMV chip
Contactless
3-D Secure
Multi-currency
Tokenization
NPCI UPI 2.0
| Network | Card present | Card not present |
|---|---|---|
| Visa | Live | Live |
| Mastercard | Live | In certification |
| American Express | Live | Planned |
| JCB | Live | Planned |
| Discover | Live | Planned |
| RuPay | Live | Planned |
| UPI (NPCI) | Live | Live |
Status reflects online authorization coverage. Every network added follows the same pattern: a routing rule plus a message translator.
Who we serve
Built for the institutions that move money
Banks & FIs
Stand behind the cards you issue, or launch acquiring, without replacing core systems.
Read moreProcessors
Onboard new banks and merchants faster on one standardised, certified platform.
Read morePSPs & fintechs
Launch card and account products without deep upfront payments investment.
Read moreAcquirers & ISOs
Modernise or replace a legacy switching estate with a staged, reversible migration.
Read more
Implementation
A phased path to production
Migration runs in parallel with your existing platform before any production traffic moves, with instant rollback available at every stage.
Assessment
System analysis and architecture planning.
~1 weekParallel setup
Deployed alongside the existing system.
~2 weeksTesting
Transaction validation and performance testing.
~2 weeksGradual migration
Progressive traffic shift under continuous monitoring.
2–4 weeksFull cutover
Complete migration and legacy decommissioning.
~1 weekSee momentPay against your own volumes
Bring your transaction profile, the networks you need, and your preferred deployment model. We will scope a proof of concept and walk through pricing for your deployment size.