Effective date: 16 March 2026

Overview
We're adding a new field to the transaction callback payload to include the product name alongside the existing product code. This is an additive, backward-compatible change. No request parameters, status codes, or existing callback fields are affected.

Callback methods impacted:
- POST callback
- GET callback

What's changing
New field in the callback payload under data:
"data": {
"product": "CELCOM", // existing field
"productName": "Celcom Prepaid", // new String field
...
}
productName (string): The human-readable display name for the product associated with the transaction. This field already exists in the POST /v2/topup response and will now also be included in the callback payload.

Backward compatibility
- Non-breaking; existing fields and their formats are unchanged.
- productName is additive only. Callbacks that previously parsed will continue to parse.
- If you use strict JSON schema/model validation, update your models to include productName or configure them to ignore unknown properties.

Actions for integrators
- No action required to maintain existing functionality.
- Optional: You can now use productName from the callback payload directly to display product names in your callback-driven flows, eliminating the need to maintain a separate product code-to-name mapping.

Should you require any further assistance or additional information, please do not hesitate to reach out to us via email at support@iimmpact.com

Please be informed that the following products will be discontinue, effective immediately.

Rest assured, any existing vouchers purchased can still be redeemed at the respective outlets within their validity period.

For any further assistance or inquiries, please do not hesitate to contact our Customer Support at support@iimmpact.com or reach out to your respective Business Development Manager.

We apologize for any inconvenience this may cause and sincerely appreciate your understanding

Please be informed that the following products will be discontinue, effective 3/3/2026.

For any further assistance or inquiries, please do not hesitate to contact our Customer Support at support@iimmpact.com or reach out to your respective Business Development Manager.

We apologize for any inconvenience this may cause and sincerely appreciate your understanding.

Please be informed that to launch the Federal Government Account Closing process in 2025, we would like to inform that the operation of receiving water bill payments for the BEKALAN AIR LABUAN will be temporary unavailable from 15 DECEMBER 2025 to 31 DECEMBER 2025.

BEKALAN AIR LABUAN will resume normal operations on 01 JANUARY 2026.

Any inconvenience is greatly regretted.

Should you require any further assistance or additional information, please do not hesitate to reach out to us via email at support@iimmpact.com.

Please be informed that the minimum payment threshold for Maxis Postpaid will be revised from RM5 to RM20. This change will take effect on 19th November 2025.

We kindly request you to take the necessary actions to implement this new minimum payment threshold. Your cooperation in ensuring a smooth transition is greatly appreciated.

Thank you.

We hope this message finds you well.

We are writing to inform you of an important update regarding our callback infrastructure. To enhance our service reliability and ensure uninterrupted connectivity, we have deployed a backup production IP address that needs to be added to your whitelist.


Action Required:

Please whitelist the following IP address in addition to your existing production IP:

Implementation Timeline:

We recommend updating your security configurations at your earliest convenience to ensure seamless callback operations. This backup IP will be activated in the event of any service disruptions, and having it whitelisted in advance will prevent any potential connection failures.

Questions or Assistance:

If you have any questions or require additional technical details regarding this update, please don't hesitate to reach out to our technical support team at support@iimmpact.com. We're here to help!

Thank you for your attention to this matter and for your continued partnership.

Effective date: 31 October 2025

Overview We’re adding new aggregated fields to the v2 transactions response and a new summary object to the v2 balance statements response. These are additive, backward‑compatible changes. No request parameters, pagination, status codes, or rate limits are affected.

Endpoints impacted:

• GET /v2/transactions
• GET /v2/balance-statements

What’s changing

/v2/transactions

• New fields in the top‑level meta object:

_{"meta": {
"transaction_count": "0", // existing field
"total_amount": "0", // existing field
"total_price": "0", // existing field
"profit": "0", // new String field
"failed_count": "0", // new String field
"successful_count": "311", // new String field
"pending_count": "0", // new String field
"refund_count": "0", // new String field
}}

/v2/balance-statements

• New object added to the response:

<sub>"summary": {
"total_transactions": {
"amount": -3444.4284, // Calculated total transaction amount for the statement period (signed decimal).
"count": 65000 // Calculated total number of transactions for the statement period.
},
"total_deposit": {
"amount": 5000.00, // Calculated total deposit amount for the statement period.
"count": 17 // Calculated total number of deposits for the statement period.

},
"total_refund": {
"amount": 150.00, // Calculated total refund amount for the statement period.
"count": 5 // Calculated total number of refunds for the statement period.
}
}</sub>

Backward compatibility

• Non‑breaking; existing fields and formats are unchanged.
• New fields are additive only. Responses that previously parsed will continue to parse.
• If you use strict JSON schema/model validation, update your models to include the new meta fields on /v2/transactions and the summary object on /v2/balance-statements, or configure them to ignore unknown properties.

Actions for integrators

• No action required to maintain existing functionality.

Should you require any further assistance or additional information, please do not hesitate to reach out to us via email at support@iimmpact.com.

We are pleased to inform you that Digi Prepaid has updated its denominations. Please find the details below:

• RM5
• RM10
• RM30
• RM50
• RM100

Should you have any questions, please feel free to reach out to our support team at support@iimmpact.com

Thank you for your attention.

Effective date: 14 October 2025

Overview

We're adding an optional field to the v2 transactions endpoint to return the JomPAY biller code where applicable. This is an additive, backward‑compatible change. No request parameters, pagination, status codes, or rate limits are affected.

Endpoint impacted:
GET /v2/transactions

What's changing:
New field in each item under data[]:
biller_code (string|null): JomPAY biller code for JomPAY transactions; null for non‑JomPAY transactions.

Backward compatibility:
Non‑breaking; existing fields and formats are unchanged.
biller_code will be present and may be null for non‑JomPAY transactions and some historical records.

If you use strict JSON schema/model validation, update your models to include biller_code or configure them to ignore unknown properties.

Actions for integrators:
No action required to maintain existing functionality.

Optional:
Surface biller_code in your UI or reports for JomPAY transactions and handle null safely.
If indexing or filtering by biller_code, account for null values.

Effective date: 5 September 2025

Overview

We’ve added optional fields to two v2 endpoints to enrich product metadata. These are additive, backward‑compatible changes. No request parameters, pagination, status codes, or rate limits are affected.

Endpoints impacted

1. GET /v2/transactions
2. GET /v2/invoice

What’s changing

1. /v2/transactions- New fields in each item under data[]:
   a. product_image_url (string, URL): Link to the product logo
   b. category (string): Product category

2. /v2/invoice- New fields in each item under data[]:
   a. product_code (string): Product code
   b. product_image_url (string, URL): Link to the product logo/image (same convention as transactions)

Backward compatibility

- This is a non‑breaking change; existing fields and their formats are unchanged.
- New fields may be null or absent for some records. Clients should handle missing values gracefully.
- If you use strict JSON schema/model validation, ensure your models are updated to include these optional fields or are configured to ignore unknown properties.

Actions for integrators

- No action required to maintain existing functionality.

Should you require any further assistance or additional information, please do not hesitate to reach out to us via email at support@iimmpact.com.

We are excited to inform Mobile Legend is available now. This is the new product codes: MLBB, MLBBTP, and MLBBWP! These products now feature denominations based on game currency, making your in-game purchases smoother and more convenient than ever. 

Effective immediately, these new product codes are ready for use.

What’s New?

• The denomination is now based on Diamonds

1. Click on the provided link and enter the pincode.
2. Insert your account ID and zone.
3. Receive your diamonds successfully!

Available Packages:

Should you require any further assistance or additional information, please do not hesitate to reach out to us via email at support@iimmpact.com.

We are excited to announce that you can now view and download all your e-invoices directly from the dashboard.

No more logging into the LHDN MyInvois portal separately to retrieve your bills. We automatically sync the validated e-invoices, so you can access everything in one place.