Built on a stack that fails well
Payment infrastructure is judged on the transactions that do not go cleanly. momentPay is built on Erlang OTP runtime and Elixir — the foundation behind some of the world's most demanding telecommunications systems — paired with Phoenix, a transactional database, Redis caching and Prometheus-based metrics.
Architectural principles, and what they mean for you
| Principle | How momentPay applies it | What it means for you |
|---|---|---|
| Multi-protocol native | One platform natively parses ISO 8583 and UPI/REST messages side by side | One system to operate instead of several |
| Event-driven processing | Transactions and state changes are published as events in real time | Dashboards and alerts reflect activity immediately |
| Cloud-native footprint | Runs as containerised services across standard cloud infrastructure | Lower infrastructure overhead, easier capacity planning |
| Isolated, supervised processes | Each transaction and connection runs in its own lightweight, supervised process | A single failure is contained and recovered automatically |
| Open, standards-based design | Interfaces built on published protocols and standard APIs | Freedom to integrate and extend without vendor lock-in |
Actor-model concurrency
Each connection and transaction is an isolated, lightweight process, so millions of concurrent transactions run on modest hardware.
Let-it-crash fault tolerance
Supervisor trees detect and restart failed processes automatically, so an isolated failure does not take down the platform.
Live code updates
New releases can be deployed without a maintenance window in supported configurations.
Native real-time
Phoenix and LiveView power live operational dashboards without a separate front-end stack.
Designed around the transactions that do not go cleanly
The parts of the design that matter most are the ones that only show themselves when something breaks.
Fail closed on persistence
A transaction is written to durable storage before it is ever sent to a network. If it cannot be recorded, it is not dispatched — the alternative is a transaction the platform could never trace or reverse.
Reverse on ambiguity
A timeout or incomplete response is treated as different from a clean decline. The outcome may already have been applied on the network's side, so a reversal is triggered automatically rather than assuming nothing happened.
Configuration-driven onboarding
A network's connection details, routing rules and message format are data, not code. Extending coverage does not require touching another network's path.
Observability
Health and volume across every connected network are monitored continuously, so a degraded connection is visible before it becomes a customer-facing failure.
Layered from the network edge to the audit log
Network security
Enterprise firewalling, a web application firewall and DDoS protection at the perimeter.
Application security
Multi-factor authentication, role-based access control and API rate limiting.
Data security
AES-256 encryption at rest, TLS 1.3 in transit, and tokenization end to end.
Monitoring & audit
SIEM integration, comprehensive audit logging and security alerting.
Compliance standards
| Standard | Status | How momentPay supports it |
|---|---|---|
| ISO 27001 | Certified | Certified against the information security management standard |
| PCI DSS | In progress | Certification underway; controls for secure card data handling are built in |
| GDPR | Compliant | Data privacy built into data handling, retention and configuration |
| HIPAA | Compliant | Controls for handling protected health information in regulated billing flows |
| CSA | Compliant | Cloud security controls aligned to the Cloud Security Alliance framework |
| SOC 2 Type II | Aligned | Operational controls designed for trust and transparency reporting |
| RBI guidelines | Aligned | Designed to support India's central bank requirements for UPI processing |
| PSD2 | Aligned | API-first architecture aligned with the European payment services directive |
Certified means an audit has been completed and the certificate is held. Compliant means the platform meets the standard's requirements. Aligned means the architecture is built to the framework without a formal audit against it.
Data protection
- End-to-end encryption for sensitive data in transit and at rest
- Automatic data masking for personally identifiable information in logs and reports
- Hardware security module integration for key management
- Comprehensive audit trails for compliance reporting
- Configurable data residency controls
Transaction risk
Fraud and risk decisioning runs as its own engine, momentPay Shield, scoring every transaction against rules, machine-learning models and sanctions data in under 10 milliseconds — fail-safe, so a scoring error never blocks a payment.
Certification & onboarding
- NPCI certification completed as part of the standard UPI onboarding path
- Card network certifications coordinated alongside your relationships
- A dedicated certification checklist provided at implementation start
- Sandbox environments available for pre-certification testing
Real-time, not batch
Business metrics
Transaction volume and trends, processing revenue, authorization and settlement success rates, merchant and consumer usage patterns.
Technical metrics
Response times, throughput, error rates, network failures and recovery times, resource utilisation.
Operational metrics
Network connection health, message processing backlogs, settlement tracking and reconciliation status.
Security metrics
Failed authentication attempts and suspicious activity patterns.
Delivered through
- Executive dashboards summarising business-level metrics
- Operations dashboards for technical and infrastructure metrics
- REST API and webhook integration for external BI tools
Alerting & escalation
- Threshold and anomaly-based alerts routed automatically
- Alerts carry enough context to start triage immediately
- Escalation paths configurable by severity and time of day
Deploy where your regulator and your architecture require
| Model | Description | Best suited for |
|---|---|---|
| Cloud-native | Containerised deployment on a major cloud provider | Startups and cloud-first organisations |
| Hybrid cloud | Critical components on-premise with cloud backup | Institutions balancing compliance and agility |
| On-premise | Fully deployed within the customer's data centre | Regulated environments requiring full data control |
| Edge deployment | Distributed processing nodes closer to source traffic | Organisations with geographically distributed volume |
Connection pooling
Database connections are reused rather than opened per request.
Response caching
Frequently accessed data is served from an in-memory cache.
Asynchronous processing
Non-blocking I/O keeps throughput high under concurrent load.
Event streaming
Monitoring and reporting consume events in near real time rather than in batch.
Automatic load distribution
Traffic is balanced across nodes without manual intervention.
Horizontal scale
Additional nodes join the cluster automatically and load-balance across regions.
A phased, reversible path off your existing switch
Protocol adapters and a data bridge let momentPay run alongside a legacy platform before any production traffic moves.
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 migration with continuous monitoring.
2–4 weeksFull cutover
Complete migration and legacy decommissioning.
~1 weekRisk mitigation built in
- Parallel processing keeps both systems running simultaneously during migration
- Instant rollback to the legacy system is available if issues arise
- Continuous, real-time monitoring validates transaction processing throughout
- Traffic is shifted gradually, starting with a small percentage of volume
- A dedicated migration team is available throughout the process
Cost drivers, reframed
| Driver | momentPay approach |
|---|---|
| Licensing | Aligned to usage rather than a fixed licence tier |
| Implementation | A phased rollout designed to reach production in weeks |
| Maintenance | Self-healing, supervised processes reduce routine manual intervention |
| Capacity | Horizontal scaling adds capacity as volume grows |
Put the architecture in front of your technical team
We will walk through protocol coverage, performance specifications, the security framework and the integration model with your engineers and risk teams.