DOCSEARCHbyAlgolia
Submit Docs

PayNet Developer Documentation

website·Indexed 38 days ago

https://docs.developer.paynet.my/

Technical documentation for PayNet payment services, including MyDebit, FPX, JomPay, DuitNow, and RPP. It provides specifications for financial reports APIs, network administration, transaction and response codes, and onboarding guides for the NFP Public API.

Tokens
468.3K
Snippets
981
Records
2.2K
Agent score
58%

What's inside PayNet

  1. Overview of DuitNow Request integration

    DuitNow Request allows a Merchant or Biller to send a payment request to a Customer. These requests typically appear in the Customer's e-banking channel (Internet Banking or Mobile Banking) for review and action. Unlike some payment flows, DuitNow Request does not require immediate attention and supports a longer expiry period.

  2. Overview of DuitNow Bill Payment (NBPS)

    DuitNow Bill Payment is part of the National Bill Payment Scheme (NBPS), an industry-wide initiative in Malaysia designed to allow customers to make online payments for any bill at any bank. While deployment for Internet and Mobile Banking is mandatory, banks may optionally extend this mechanism to other channels such as ATMs and Branches.

  3. Overview of PayNet Certificate Management

    Certificate Management is a PKI (Public Key Infrastructure) service responsible for the issuance, signing, and lifecycle management of X.509 certificates for PayNet participants. It handles signing participant public keys via Certificate Signing Requests (CSR) and managing certificate validity.

    Key Constraints:

    • The service does NOT handle SSL/TLS or mTLS connections; these must be implemented by the consuming systems.
    • Private keys must be generated and stored securely by the participants. PayNet never receives or stores private keys.

  4. Overview of DuitNow Pay payment journeys

    DuitNow Pay enables online checkouts, repeat, and recurring payments directly from bank accounts or eWallets. It supports two primary payment modes:

    1. One-time payments: Real-time payments made via DuitNow Online Banking or Wallets.
    2. Saved payments: Faster repeat and recurring payments enabled by customer consent for future transactions via DuitNow Consent & AutoDebit.

  5. Overview of DuitNow Request

    DuitNow Request allows Merchants or Billers to send payment requests to Customers. These requests appear in the Customer's e-banking inbox (Internet or Mobile Banking). Unlike immediate payment methods, DuitNow Request has a longer expiry period, allowing customers to review and take action at their convenience.

  6. Overview of the DuitNow Signature Generator Sample App

    The DuitNow Signature Generator is a sample application designed to help developers generate and verify signatures and create JSON Web Tokens (JWT). The app consists of four primary functional tabs:

    1. DuitNow Version 1: Generates signatures for Version 1 using XML format.
    2. DuitNow Version 2, X-Signature: Generates signatures for Version 2 using string format.
    3. DuitNow Version 2, JWS: Generates a JSON Web Token (JWT).
    4. Verify Signature: Verifies signed messages and signatures using a public key derived from the signing private key.

  8. Overview of SAN NextSwitch Migration Self-Certification

    The SAN NextSwitch Migration uses the PayNet Developer Portal to provide a self-service environment for participants to onboard, integrate, and validate their solutions. The portal allows organizations to manage projects, execute automated role-based test cases, and track certification progress without dependency on partner banks, as PayNet provides a Non-Production bank to act as the partner.

  9. Overview of the Biller Validation Module (BVM)

    The Biller Validation Module (BVM) is a 24/7 online service hosted by PayNet as part of the National Bill Payment Scheme (NBPS). It allows Payer Banks to perform online validation of bill payments and provide successful payment notifications to Billers.

    Key entities involved include:

    • Payer: The customer making the payment.
    • Payer Bank: The bank where the Payer holds an account and initiates the transaction.
    • Biller: The entity receiving the payment for goods or services.
    • Biller Code: A unique identifier for the Biller's service.
    • Biller Bank Account: The account where funds are credited, as advised by the BVM based on the Biller Code.

  11. Overview of the Financial Reports Generation API

    The Financial Reports Generation API provides an automated, flexible method for retrieving financial reports and querying data. It replaces manual or semi-automated processes that relied on fixed formats and rigid access methods. Key benefits include the ability to customize report fields to receive only necessary data, a scalable architecture that supports new data structures without system overhauls, and a self-service interface for API key management to replace SSH keys or manual credential provisioning.

  12. Overview of the Merchant Profile API

    The Merchant Profile API serves as a master merchant database acting as the single source of truth. It is designed to provide a standardized integration method for external services and applications requiring merchant profile access. Key capabilities include:

    • Schema Evolution Support: Manages changes to data structures over time without disrupting existing systems.
    • Data Quality Enforcement: Applies validation rules and quality controls to ensure consistent and accurate data.
    • Data Evergreen Processes: Uses automated processes to maintain up-to-date and continuously refreshed data.

    Availability Note: The Merchant Profile API is scheduled to be available effective Q3 2025.