Aeon Bank customer claims he received RM1 billion in his account by mistake
- ID
- 35748
- Status
- summarized
- Published
- 15 Oct 2026, 5:44 PM
- Fetched
- 15 Oct 2026, 6:11 PM
- Provider
- SoyaCincau
- Category
- malaysia-tech
- Original URL
- https://soyacincau.com/2026/10/15/aeon-bank-customer-rm1-billion-transfer-mistake/
- Source URL
- https://soyacincau.com/feed/
Summary
- Score
- 5.0
- Created
- 15 Oct 2026, 6:11 PM
- Tags
- Audience
- developerssaas_founders
What happened
A customer of Malaysia's Aeon Bank says RM1,000,315,879 was credited to his digital bank account on 14 October, with the transaction labelled "Cash Reward – Merdeka / Malaysia Day 2026 Campaign Cycle 6". The underlying campaign was far smaller: RM12,834 in total cash rewards across 414 winners over six weekly cycles from 17 August to 27 September 2026, with 69 winners picked each week. The customer reported it, the amount was reversed the same day, and the bank reportedly told him he would receive a reward for flagging it quickly; the bank has not explained the cause.
Why it matters
If you build reward, cashback, or batch-credit flows in a Malaysian payments context, this is the concrete failure mode to design against: a campaign whose entire prize pool was RM12,834 posted a 10-digit credit to a live customer account, and nothing in the pipeline stopped it before it reached the banking app. Add hard per-transaction and per-campaign caps on reward disbursement, and reconcile posted totals against the allocated budget before the ledger entry becomes customer-visible. Note the bank has not published a root cause, so treat any explanation as unconfirmed.
Discussion angle
Walk through what guardrails would have caught this: per-transaction caps, campaign budget reconciliation, and a staging/approval step between a batch job computing a reward and the ledger write that makes it spendable. Ask who in the room has hard limits on outbound money movement in their own product.