Ready to Elevate Your Payment Experience?
Get Started
Copyright © 2026 | Novupay
NovuPay operates as an Operator of Payment System that enables payment initiation, request generation, routing, transaction monitoring, and reporting. It acts as the orchestration layer between initiating participants and regulated payment infrastructure, while authorization, clearing, settlement, and custody remain outside NovuPay.
A participant or customer starts a payment through a NovuPay-powered digital interface or API submission, providing amount, reference number, participant identity, customer information, and transaction metadata.
NovuPay creates the transaction record, applies platform validation, assigns internal and participant-facing references, and prepares the request for secure transmission.
NovuPay routes the payment instruction to an accredited payment processing partner through protected APIs. The partner provides the regulated connectivity needed for QRPh or other supported payment rails.
The processing partner generates the official payment payload or hosted payment session. For QRPh transactions, this is the stage where the scannable request is produced for customer use.
The customer authorizes payment through a bank or wallet application. The regulated financial institution performs balance verification, account checks, authentication, and fraud or risk evaluation.
Authorization results move back through the payment rail and processing partner to NovuPay. NovuPay records the resulting status, updates operational records, and preserves the event trail for auditability.
NovuPay returns payment outcomes through redirects, callbacks, APIs, dashboards, or webhooks, while maintaining transaction metadata, timestamps, and references for reporting, dispute handling, and reconciliation.
| Stage | Primary actor | Standard action | Primary output |
|---|---|---|---|
| 01 | Participant / Customer | Initiates payment from a NovuPay interface or integrated participant system. | Payment request with amount, reference, and metadata. |
| 02 | NovuPay | Creates the transaction, validates data, assigns references, and prepares the orchestration payload. | Registered transaction record ready for routing. |
| 03 | NovuPay | Routes the request to a regulated payment processing partner through secure API communication. | Partner-bound payment instruction. |
| 04 | Processing partner | Generates the QRPh or hosted payment payload and returns the payment experience to the orchestration layer. | QR code, redirect URL, or hosted checkout session. |
| 05 | Customer + Financial institution | Customer authorizes payment using a participating bank or wallet, while the institution performs regulated authentication and authorization controls. | Approved, declined, or further-authentication result. |
| 06 | Payment rail / Partner | Financial result traverses regulated infrastructure and returns operational status to NovuPay through the connected partner. | Transaction confirmation message. |
| 07 | NovuPay | Updates transaction state, records references and timestamps, and triggers participant-facing response channels. | Updated status, webhook event, callback, redirect, and reporting entry. |
Settlement boundary
Authorization, clearing, and settlement occur within regulated financial institutions, payment rails, and processing partners. NovuPay remains the transaction orchestration and visibility layer, not the custodian of funds.
Payment capture begins from checkout pages, participant applications, QR-oriented interfaces, or API-based initiation. Standard inputs include amount, reference number, participant identity, and related metadata.
NovuPay persists the request, structures the data, and prepares routing instructions so downstream partners receive a complete and traceable payment message.
The regulated partner generates the QRPh payload or equivalent payment session and enables connectivity to the appropriate national or partner-operated payment rail.
The payer authorizes the transaction using a banking app or electronic wallet, and the regulated institution executes the authentication and account-level checks required for approval.
Approved, declined, or other operational responses travel back through the partner integration path and are recorded by NovuPay as the authoritative orchestration status.
Participants receive transaction visibility through dashboards, redirects, callbacks, status checks, or webhook notifications, enabling upstream systems to synchronize their records.
Merchants, utilities, government entities, and integrated services use NovuPay to initiate transactions, monitor payment outcomes, and support their operational reporting.
Payment processing partners provide rail connectivity, while financial institutions execute authentication, authorization, debiting, crediting, and regulated settlement activities.
Web-based checkout pages, participant dashboards, and supporting documentation provide the entry point for payment initiation and transaction visibility.
Modular backend services create payment requests, route transactions, receive responses, process webhooks, and maintain synchronized transaction state.
Transaction records, participant payloads, references, timestamps, audit logs, and compliance-relevant operational data are stored to support traceability and reporting.
The platform is positioned for encrypted communications, scalable routing, redundancy, continuous monitoring, and secure integration with external payment infrastructure.