Skip to content
← Back to all announcements
Non-Breaking ChangeTechPublished October 6, 2025· Effective: October 14, 2025·Engineering Team

Non-breaking API update: New response field for /v2/transactions (biller_code)

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.

IIMMPACT Platform Announcements