โ ๏ธ Update: This issue has now been fixed. Refer to this post for more details |
Figuring out the all-important Merchant Category Code (MCC) used to be a game of guess and check, but in recent times it’s become much more straightforward thanks to tools like the DBS digibot and HeyMax.
Unfortunately, it looks like the former may have just been nerfed. While it remains to be seen whether this is a permanent change or just a temporary error, it’s still worth taking note of.
DBS digibot no longer providing MCCs
The DBS digibot allows DBS/POSB cardholders to look up their past transactions. You can access it via the DBS digibank app or DBS ibanking.
- For the app, tap the question mark on the top right corner and scroll down to tap โask digibotโ
- For desktop, click the icon at the bottom right corner
Navigate to Check my Recent Transactions > Credit Cards > Select the card you used > View Transaction History. You can then see pending, unbilled, billed or declined transactions.
At some point on Friday, 6 October 2023, MileLion community members began reporting that the DBS digibot was no longer listing transaction MCCs. This is the case regardless of whether you’re looking up previous transactions…
…or using the “block card” method to find out MCCs before transacting.
The only information currently shown is transaction description (for pending and billed transactions) or the reason the transaction was declined (for declined transactions).
However, it is still possible to see MCCs for unbilled transactions.
At this point it’s too early to say whether it’s a temporary bug or a permanent change. I distinctly recall another instance in the past when MCCs temporarily disappeared, only to be restored later. In any case I’ve reached out to DBS, and will update this post if/when I get a response.
HeyMax alternative
Max |
In the meantime, you can continue to use HeyMax.ai to look up the MCCs of any merchant, whether in Singapore or overseas.
While HeyMax is a lot easier to use than the DBS “block card” method and will be mostly accurate, you’ll encounter problems when dealing with merchants that process transactions over a range of MCCs. Classic examples are e-commerce sites like Amazon, Lazada and Shopee, where HeyMax can provide the full list of potential MCCs, but can’t tell you exactly which one it’ll be.
This is where the DBS “block card” method would have come in useful, because you could block your card, attempt to carry out the transaction, check the MCC, then come back with the right card.
But for most use cases (like figuring out whether a restaurant within a hotel codes as a restaurant or hotel, or whether a clinic codes as a hospital), HeyMax should get the job done.
To learn more about HeyMax, refer to the post below.
Conclusion
The DBS digibot no longer shows transaction MCCs, whether it’s for a past transaction or a declined one. This is potentially a major headache, since it’s currently the most accurate way for a cardholder to look up an MCC before spending.
In the meantime, MCC queries can be checked via HeyMax, though the platform doesn’t work so well for merchants which process transactions over a range of MCCs.
Hopefully this is just a temporary glitch, but stay tuned…
Hope after reaching out to DBS, it would revert back to normalโฆ Cheers!
that sucks โฆ i guess the blocking and unblocking activities add overheads , which i do not blame them.. btw ai max is terrible for me
Hello! Thanks for the feedback with heymax.ai! I’m one of the cofounder looking to improve. Would you be so kind to share what frustrates you? We are always seeking feedback to make it truly useful for customers. I’m sorry it’s not up to your standards yet.
Following. I love Hey Max so curious to understand where the gaps are