DOCSEARCHbyAlgolia
Submit Docs

PayNet Developer Portal

website·Indexed 38 days ago

https://docs.devportal.uat.inet.paynet.my/docs

Technical documentation for PayNet payment services, including DuitNow QR, DuitNow AutoDebit, and DuitNow online banking and wallets. It provides integration guides for JSON Web Signature (JWS), API response and transaction codes, certificate management, and the Data Format Assurance and Validation Engine (DAVE).

Tokens
420.2K
Snippets
888
Records
2K
Agent score
49%

What's inside PayNet

  2. Overview of SAN NextSwitch Migration Self-Certification

    The SAN NextSwitch Migration uses the PayNet Developer Portal to provide a structured, self-managed self-certification journey. The portal allows participants to onboard, integrate, and validate their solutions without dependency on partner banks, using a PayNet Non-Production bank instead. Key benefits include automated role-based test cases, instant results with logs, 24/7 availability, and centralized project management.

  3. Overview of DuitNow Transfer service

    DuitNow Transfer is an instant credit transfer service for retail and corporate transactions, integrated into Internet and Mobile Banking platforms. The transaction process consists of two primary steps:

    1. Account Verification: An account inquiry is sent to the Receiving Participant to verify and display the recipient's name to the payer.
    2. Credit Transfer: After verification, the Originating Participant debits the payer's account and sends the credit transfer request to the Receiving Participant.

  4. Overview of DuitNow V3 Centralised Certificates

    The Centralised Certificate feature for DuitNow V3 allows participants to set up a single certificate and use it across multiple DuitNow V3 projects. This feature is exclusively compatible with DuitNow V3 and is not supported for DuitNow V1 or V2. Access to modify centralised configuration is restricted to users registered under the same verified company account.

  5. Overview of DuitNow Pay User Journeys

    DuitNow Pay enables online checkouts, repeat, and recurring payments directly from bank accounts or eWallets. It supports two primary payment modes: one-time payments (real-time payments via DuitNow Online Banking/Wallets) and saved payments (repeat/recurring payments via DuitNow Consent & AutoDebit).

  9. Overview of DuitNow Request payment flow

    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 payments have a longer expiry period and do not require immediate attention.

  11. Overview of MyDebit Secure Card-Not-Present (CNP) Authentication

    MyDebit Secure is a Card-Not-Present (CNP) authentication program designed to secure e-commerce transactions. It is based on the EMV 3-D Secure (E3DS) protocol, which utilizes a three-domain model to authenticate transactions:

    1. Issuer Domain: Includes cardholders and issuing Financial Institutions (FIs).
    2. Interoperability Domain: Operated by PayNet as the card network.
    3. Acquirer Domain: Includes merchants, payment gateways, and acquiring Financial Institutions (FIs).

    Key features of the E3DS standard used by MyDebit Secure include support for in-application purchases on mobile devices, risk-based decisions for frictionless authentication (where additional user steps may be skipped), and non-payment customer authentication for Identification & Verification (ID&V) services.

  12. 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 send successful payment notifications to Billers.

    Key entities involved include:

    • BVM: Provides validation and notification functions.
    • 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.
    • Biller Code: A unique identifier for the Biller service.
    • Biller Bank Account: The account where funds are credited, determined by the BVM based on the Biller Code and Payer Bank.