Ready to Elevate Your Payment Experience?
Get Started
Copyright © 2026 | Novupay
NovuPay is a digital payment gateway in the Philippine payments ecosystem. QR Ph is the national retail payment rail. The only live NovuPay payment channel is QR Ph, through a partner financial institution. GCash, Maya, and bank apps are the buyer’s QR Ph scanner. They are not NovuPay channels.
Other payment channels are a possible addition in the future, including online banking, OTC, installment platforms such as BillEase, and card payments. They are not live. If they are enabled later, the partner financial institution would still receive, hold, and settle the funds. NovuPay would not.
NovuPay creates payment requests, shows a QR Ph checkout, routes the QR Ph instruction to the partner financial institution, receives that institution’s postback, records status, notifies the merchant, and supports reconciliation. A Paid status means NovuPay received a successful postback from the partner financial institution. It is not a guarantee that the institution has settled to the merchant’s bank.
The partner financial institution receives, holds, and settles the funds to the merchant’s bank. NovuPay does not accept deposits, hold customer or merchant funds, operate a stored-value or e-money wallet, pay out balances, or perform clearing and settlement.
The buyer pays by scanning the NovuPay QR Ph in their own QR Ph-capable app, such as GCash, Maya, or a QR Ph bank app. Those apps are the buyer’s scanner. Funds never sit with NovuPay.
The merchant creates payment requests, receives status through the dashboard, status API, and merchant webhook, and is settled by the partner financial institution to a designated bank account.
The partner financial institution is the acquiring and settlement partner. It receives, holds, and settles the funds to the merchant’s bank. Settlement timing, bank credit, and acquiring decisions belong to the partner financial institution and QR Ph rules.
QR Ph participants and the buyer’s bank or wallet authorize and move funds on the QR Ph rail. NovuPay does not authorize the debit and does not perform clearing and settlement.
Each live payment follows one path. The merchant or API creates a request, NovuPay asks the partner financial institution for a QR Ph, the buyer pays in their own app, the partner financial institution posts the result, NovuPay records Paid and notifies the merchant, and the partner financial institution later settles to the merchant’s bank. NovuPay’s later reconciliation matches its Paid record to that settlement report.
The merchant or API creates a payment request. The request carries the amount, currency, reference, customer details, and callback.
NovuPay persists the request and calls the partner financial institution to generate the QR Ph. NovuPay then shows that QR Ph checkout.
The buyer pays by scanning that QR Ph in their own bank or wallet app. GCash, Maya, and QR Ph bank apps are scanners for this step. They are not NovuPay channels.
The partner financial institution posts the result to NovuPay. NovuPay accepts the postback only after source, signature, amount, and expiry checks, then marks the payment Paid. Paid means that postback succeeded. It does not mean the partner financial institution has settled to the merchant’s bank.
NovuPay notifies the merchant through the dashboard, the status API, and the merchant webhook.
The partner financial institution settles to the merchant’s bank on its own cycle. NovuPay reconciliation later matches its Paid record to that institution’s settlement report. That match is reporting. NovuPay does not move the funds.
NovuPay routes the QR Ph instruction to the partner financial institution and records what that institution reports back. It does not sit on the path of the funds. The buyer pays from their own app, the partner financial institution receives and holds the funds, and the partner financial institution settles them to the merchant’s bank.
NovuPay sits beside that path. It generates the QR Ph, validates the postback, marks the transaction Paid, notifies the merchant, and later matches the record to the partner financial institution’s report.
Buyer
→ Buyer’s QR Ph app (GCash, Maya, or a QR Ph bank app)
→ Partner financial institution QR Ph
→ Partner financial institution holds the funds
→ Partner financial institution settles to the merchant’s bank
NovuPay does not accept the deposit, hold the funds, or settle them. Settlement timing, bank credit, and acquiring decisions belong to the partner financial institution and QR Ph rules. NovuPay does not control them.
The partner financial institution holds the funds and settles them to the merchant’s bank. Clearing and settlement are not performed by NovuPay. Settlement timing, bank credit, and acquiring decisions belong to the partner financial institution and QR Ph rules. NovuPay does not control them.
A Paid status means NovuPay received a successful postback from the partner financial institution. It is not a guarantee that the partner financial institution has settled to the merchant’s bank. Reconciliation matches NovuPay’s Paid record to the partner financial institution’s settlement report. It is reporting, not NovuPay moving money.
NovuPay may collect the merchant’s settlement bank details and pass them to the partner financial institution. NovuPay does not use those details to pay the merchant. NovuPay does not accept deposits, hold customer or merchant funds, pay out balances, or keep a merchant balance.
The partner financial institution is NovuPay’s acquiring and settlement partner on QR Ph, the national retail payment rail. NovuPay sends the payment request so the partner financial institution can generate the QR Ph, then receives the postback and records the result. The partner financial institution receives, holds, and settles the funds. NovuPay does not become the custodian of those funds.
The only live NovuPay payment channel is QR Ph, through the partner financial institution. Other payment channels are a possible addition in the future: online banking, OTC, installment platforms such as BillEase, and card payments. They are not live until they are enabled. Enabling a future channel would not move custody or settlement to NovuPay.
NovuPay shows the buyer a QR Ph checkout and gives the merchant a console for payment requests, status, and reports. Operator access is a separate console. Initiation is also available through the merchant API.
Gateway services persist the payment request, call the partner financial institution to generate the QR Ph, check the postback, mark the payment Paid, and notify the merchant. They do not hold or settle funds.
NovuPay stores the payment request, status, references, and timestamps needed to notify the merchant, support audit, and match a Paid record to the partner financial institution’s settlement report.
The partner financial institution is the boundary where funds are received, held, and settled to the merchant’s bank. NovuPay exchanges the QR Ph instruction and the postback with that institution, and remains outside the funds path.
Merchant API access uses server-side credentials: an API key and a client id. The client secret is for webhook verification and must stay on the merchant server. It is not a client-side credential.
Postbacks from the partner financial institution are checked for allowed source, signature, amount, and expiry before NovuPay changes status. Transport is HTTPS. Transaction and webhook activity is logged for audit and reconciliation. Role-based access separates the merchant console from the operator console.
NovuPay’s risk posture as a digital payment gateway rests on status integrity, partner boundaries, and traceable records. Relevant categories are operational risk, cybersecurity risk, availability of the QR Ph instruction path, postback integrity, and third-party dependence on the partner financial institution and the QR Ph rail. NovuPay does not manage a merchant balance, and it does not treat a Paid status as completed settlement.
QR Ph operations depend on NovuPay’s ability to create a payment request, obtain a QR Ph from the partner financial institution, receive a postback, notify the merchant, and later match Paid records to that institution’s settlement report. NovuPay does not mark a payment Paid without a postback that passes the required checks, and it does not hold or advance funds when the partner financial institution or QR Ph is unavailable.
When an incident occurs, the response is to identify the event, classify its severity, contain it, restore the affected request, postback, or notification path, investigate the cause, and document the incident. A partner outage remains with the partner financial institution or the QR Ph rail to resolve for acquiring and settlement. NovuPay’s continuity task is to restore QR Ph checkout, status recording, merchant notification, and reconciliation reporting.
NovuPay is a digital payment gateway. It generates and routes the QR Ph, records status from the partner financial institution, and reports. The partner financial institution holds and settles. NovuPay does not. Other payment channels — online banking, OTC, installment platforms such as BillEase, and card payments — are a possible addition in the future and are not live.