Demo — invented data, read-only. Nothing here is anyone’s real spending.
RewardsMaxx

A read-only demoi

What this is

The same application as the private build — same rules, same engine, same pages. Only the wallet is different.

Every merchant outside the DBS yuu cards has been replaced by a different Singapore business carrying the same MCC, and every amount has been changed. The yuu cards keep their merchant brands because their bonus is gated on named participating merchants and needs four distinct ones in a month — a random name there would delete the 18% tier rather than disguise it. Their branches are still replaced.

Because the amounts moved, the reward each statement printed was re-derived from the new figures. The canary on the card pages therefore shows the engine agreeing with itself. On the real wallet it is agreeing with the bank, which is the harder test and the reason the page exists.

Why nothing can be changed

The passcode gate is off so that anyone with the link can look around. A page anyone can open is a page anyone can edit, so writing is refused instead: resolving a duplicate, teaching a merchant its category, merging two cards, uploading a statement. One visitor merging another visitor’s transactions would spoil the demo for everyone after them, with no way back.

Reading is untouched. Every page, every card, every figure and the advisor all work.

Do not upload a real statement

Import is switched off here, and that is deliberate. The private build reads statements on the machine they live on and deletes them afterwards; nothing about a public demo offers that. If you want to try it against your own cards, run it locally.

Back to today
RewardsMaxx