Help Centre

PAYMENZ is the software that sits between a bank and Malaysia’s payment networks. When someone sends money instantly through DuitNow, pays a bill through JomPAY, or receives an international transfer, the message has to travel from the national payment network into the bank’s own systems, and back again. PAYMENZ is the layer that makes that journey work. It checks each message, converts it into the format the bank’s systems understand, delivers it, and keeps a record of everything that happened. 

PAYMENZ is for banks, Islamic banks, development financial institutions and licensed payment companies operating in Malaysia. In short, it's for any institution that connects to the national payment rails and needs those connections to be fast, accurate and always available. It is not a consumer app. Members of the public will never use PAYMENZ directly, but they benefit from it whenever a payment at their bank goes through instantly and correctly.

They can, but it becomes expensive and slow to change. Most banks run core systems that were designed decades ago around overnight batch processing: the idea that the day's payments are totalled up and settled once, at night.

Malaysia's payment networks no longer work that way. Payments now settle instantly, around the clock, and use a modern international message format. Connecting each new payment service directly into an older core system means a major IT project every time. PAYMENZ absorbs that complexity in one place, so the core system can stay as it is.

PAYMENZ covers the Malaysian payment landscape from a single connection: 

• DuitNow for instant fund transfers, DuitNow QR (domestic and cross-border), Request to Pay, AutoDebit & Consent, DuitNow Online Banking/Wallets 

• Interbank GIRO (IBG), JomPAY bill payments, FPX online banking and Direct Debit 

• RENTAS for large-value and high-priority payments 

• SWIFT for international payments, including GPI payment tracking 

Adding another service later is normally a configuration change within PAYMENZ rather than a new project inside the bank’s core system. 

No. That is the point of the product. PAYMENZ is built to speak whatever language the existing core system already uses. This can include file transfers, message queues, older fixed-format records or in-house APIs. The translation work happens inside PAYMENZ. The core system keeps its existing interfaces and carries on as before.

Considerably less time than doing it inside the core system, because most of the work is configuration rather than new software development. When a payment network changes its rules, which happens regularly, the change is handled inside PAYMENZ. The bank only needs to make a change of its own where the new information genuinely has to reach the core system. Actual timelines depend on the institution and the service, and we scope them together before any commitment.

Security is built into the design rather than added afterwards. Stored information is encrypted, and information moving between systems travels over encrypted connections using current industry standards.Cryptographic keys are held in dedicated hardware security modules (HSM), with each bank given its own separate partition and its own master keys, so a bank's keys remain under its own control and custody. Every message is also checked at the gateway before it reaches the core system, which allows suspicious activity to be caught early rather than after the fact.

Yes. PAYMENZ is designed to align with Bank Negara Malaysia's Risk Management in Technology policy and with the control expectations set out in PCI DSS and ISO 27001, producing the audit trails and reporting institutions are asked to provide. It also handles international messaging standards, including the change taking effect on 14 November 2026 that requires properly structured addresses on cross-border payment messages. One important clarification: formal certification is always held by the institution and assessed against its own deployment. PAYMENZ is designed to support that process and supply evidence for it, it does not replace it.

It is designed to be. Instant payments do not pause overnight or at weekends, and since RENTAS+ went live in September 2025 settlement between banks runs 24 hours a day. PAYMENZ runs in an active–active arrangement, meaning processing nodes at more than one site handle live traffic at the same time. That serves two purposes: it provides more capacity when volumes peak, and it allows maintenance and upgrades to be carried out without taking the payment path offline. 

PAYMENZ can be installed in a private cloud (Finexus's cloud) as a SaaS model (recommended), in the institution's own cloud/data centre, or in a combination of the two, whichever fits the institution's technology risk position and its regulator's expectations. The best starting point is a scoping session. It takes about an hour and produces a concrete picture of how PAYMENZ would fit alongside the systems and payment services already in place. Reach out through our Contact Us page to get started.