DocsDuitNow Bill PaymentOverview

We've Launched a New Documentation Website (Beta Launch)

The documentation for DuitNow is now available on our newly launched documentation platform. This is an initial beta rollout of our new documentation site, designed to become the long-term home for all documentation moving forward.

You'll find the familiar content you're used to—now hosted on a new platform that will progressively receive updates and enhancements.

We encourage you to start accessing DuitNow materials there to explore the new experience and ensure you're viewing the latest documentation updates. If you have any feedback, please reach out to us.

Visit the New Documentation Website

DuitNow Bill Payment

Introduction

PayNet is facilitating an industry wide initiative to implement ubiquitous online bill payments for Malaysia, called the National Bill Payment Scheme (NBPS). Its fundamental purpose is to facilitate Customers to make online payment of ANY Bill at ANY Bank in Malaysia

While this initiative is primarily targeted for online bill payments (deployment at Internet and Mobile Banking is mandatory), Banks can optionally extend this bill payment mechanism to other channels, including ATMs and Branches

Successful End-to-End Account Enquiry Flow

Step	Sender	Receiver	Process
1	Payer	Payer Bank/OFI	Customer logs into Online Banking or Mobile Banking app and initiates a Bill Payment transaction
2a	Payer Bank/OFI	RPP	Payer Bank performs the following: Authorize and validate the Bill Payment transaction Any internal validations If all validations are successful: Send Account Enquiry request
2b	RPP	Payer Bank/OFI	RPP performs the following: Message Validations Business Validations Beneficiary Account Validations If any of the Message Validations fails: Send a REJECT response If any of the Business Validations fails: Send a NEGATIVE response If any of the Beneficiary Account Validations fails: Send a NEGATIVE response If all validations are successful: Send Account Enquiry message response with the necessary beneficiary account information
3	Payer Bank/OFI	Payer	Payer Bank performs the following: Message Validations Business Validations If all validations are successful: If SUCCESSFUL response is received: Display the transaction information to the Customer for payment confirmation If UNSUCCESSFUL response is received: Display an error message to the Customer
4	Payer	Payer Bank/OFI	Customer verifies the payment details and confirms on the payment
5	Payer Bank/OFI	-	Payer Bank performs the following: Authorize and validate the Instant Transfer transaction Any internal validations Debit source account
6a	Payer Bank/OFI	RPP	Payer Bank performs the following: Authorize and validate the Instant Transfer transaction Any internal validations Debit source account If all validations are successful: Send Credit Transfer message request
6b	RPP	Payer Bank/OFI	RPP performs the following: Message Validations Business Validations If any of the Message Validations fails: Send a REJECT response If any of the Business Validations fails: Send a NEGATIVE response If all validations are successful: Update liquidity and settlement positions of both OFI and RFI Send Credit Transfer message response Send ACCEPTED response
7	Payer Bank/OFI	Payer	Payer Bank to display payment confirmation to Payer
8a	RPP	Biller Bank/RFI	RPP performs the following: Message Validations Business Validations Beneficiary Account Validations If any of the Message Validations fails: Send a REJECT response If any of the Business Validations fails: Send a NEGATIVE response If any of the Beneficiary Account Validations fails: Send a NEGATIVE response If all validations are successful: Send Credit Transfer with message request
8b	Biller Bank/RFI	RPP	Biller Bank performs the following: Message Validations Business Validations Beneficiary Account Validations If any of the Message Validations fails: Send a REJECT response If any of the Business Validations fails: Send a NEGATIVE response If any of the Beneficiary Account Validations fails: Send a NEGATIVE response If all validations are successful: Send Credit Transfer with successful message response
9a	RPP	Biller	RPP sends RTN request (web service) to Biller. Currently there are 3 communication channels / protocols supported by RPP: Web service (HTTPS) – This channel allows server-to-server communication between BNS and Billers using HTTPS via the Internet Secure FTP (sFTP) – This channel allows Biller to retrieve batch files containing multiple Biller Notifications from the BNS File Server via the sFTP protocol Email – This channel enables the Biller to receive emails from BNS’s email SMTP server Notes: This section is applicable to Biller only. Please refer to latest document guides on JomPAY Biller Notification System BNS for more information
9b	Biller	RPP	Biller sends RTN response to RPP Notes: This section is applicable to Biller only. Please refer to latest document guides on JomPAY Biller Notification System BNS for more information

Notes:

• All Bill Payment transactions (On-Us and Off-Us) to be routed to RPP
• The exception scenarios will be handled similarly to Account Enquiry & Credit Transfer flows

Exception Flows

RPP Request to Biller Bank Timeout

Condition	Actions	Alternatives
RPP sent a request to Biller Bank. However, RPP request did not reach to Biller Bank As no response is received from Biller Bank after x period of time, RPP eventually timeout	RPP shall: Timeout If retry is configured, RPP shall: Store the request to SAF If retry count has not exceeded the maximum number of retries Send a repeat request Continue processing If retry count has exceeded the maximum number of retries Display an ACCEPTED status message to Customer Stop processing	-

See also

• Recommended validations
• How does credit transfer reversal work
• How does repeat message work
• How does SAF work