×

Dear Valued Customers,

SCHEDULED DOWNTIME FOR FPX & JOMPAY - PayNet

Warmest Greetings from Dagang Net Technologies Sdn Bhd

Please be informed that as requested by Payments Network Malaysia Sdn Bhd (PayNet), FPX services are schedule to be temporarily unavailable as follows:

The above mentioned downtime is to facilitate System Maintenance activity for FPX services during the said hours.

Services        : FPX & JomPAY
Date               : Wed, 11 July 2018
Time              : 02:00am to 04:00am
Duration       : 2 Hours

To minimize disruption to your business operations, you are advised to avoid submitting any Customs duty payments and Permit payments two (2) hours prior to the scheduled disruption.

For further details, please contact our Careline at 1 300 133 133 or email to careline@dagangnet.com

Thank You

Latest News

Get updates and announcements from Dagang Net

View All

Read more +27 February 2026

DNeX reshapes portfolio for growth, underlying losses narrow sharply in FY2025

Cyberjaya, 27 February 2026 - Dagang NeXchange Berhad (“DNeX” or “the Group”) today announced its financial results for the full year ended 31 December 2025 (“FY2025”), marking a pivotal year of strategic consolidation. While the Group reported a headline Loss Before Tax (“LBT”) of RM479.4 million, the result was largely driven by a one-off, non-cash impairment of RM429.5 million. This strategic reset strengthens and streamlines the balance sheet, positioning the Group on a more resilient foundation for future growth.
Read more +27 February 2026

SYSTEM DOWNTIME NOTIFICATION: NEW EPERMIT SYSTEM – IMPORTANT UPDATE FOR SIRIM USERS

With reference to our previous announcement dated 20th February 2026, kindly refer to the attached official circular from SIRIM for the relevant instructions and actions regarding this downtime.
Read more +27 February 2026

RESUMPTION OF SERVICE: INACCESSIBILITY OF SHIPPING SCHEDULE MENU IN MMSW

Please be informed that the accessibility issue affecting the Shipping Schedule menu in the MMSW system has been resolved. The feature is now functioning normally.
TOP