Idea Usher Review: Building CHIMAD — A Digital Payments App
Over the last few years, I’ve noticed that many founders on Product Hunt are working on payments, loyalty, rewards, and QR-based platforms, yet the real challenges rarely get discussed openly. Most conversations stop at feature lists, while the actual complexity lives in onboarding flows, edge cases, security tradeoffs, and operational scalability.
CHIMAD is a digital payments and rewards platform we helped engineer, and I wanted to break down how it was built, what problems mattered most, and which decisions actually made a difference. Hopefully this helps anyone building something similar avoid a few painful mistakes.
The Core Problem We Were Solving
CHIMAD wasn’t born from a “cool app idea.” It started with a very operational problem.
Businesses were using:
One system for payments
Another for coupons
Manual processes for vendor onboarding
Separate dashboards for reporting
Meanwhile, users dealt with:
Confusing redemption flows
Inconsistent QR experiences
Poor reliability in low-connectivity environments
The client wanted one platform that handled:
Digital payments
Coupon campaigns
QR-based redemption
Vendor onboarding and verification
Admin analytics and control
The key constraint was simplicity. Most existing solutions technically did these things, but only by layering complexity on top of users and vendors.
Designing for Three Stakeholders (Not One)
One early mistake many teams make is designing for “the user” as a single persona.
CHIMAD had three equally important stakeholders:
End users redeeming coupons
Vendors running campaigns
Admins managing the ecosystem
Each group had different priorities:
Users wanted speed and clarity
Vendors wanted control and transparency
Admins wanted visibility and compliance
If one group suffered, the platform would fail.
So instead of building one app with roles bolted on, we treated this as three journeys sharing the same data backbone.
User Experience: Reducing Friction Where It Actually Hurts
One lesson we’ve learned repeatedly:
Payment platforms live or die by friction tolerance.
Originally, the system used OTP for every login. On paper, this looked secure. In reality, it was annoying, especially for repeat users.
What we changed:
OTP only during registration and account recovery
Password-based login for returning users
Email/phone as identifiers
Security didn’t drop. Completion rates went up. This is a recurring pattern:
Security theater often harms real security by encouraging workarounds.
QR Code Redemption Isn’t as Simple as It Sounds
QR redemption looks trivial until you deploy it in real-world conditions.
We ran into issues like:
Poor connectivity in busy stores
Delayed server responses
Failed redemptions during peak hours
When QR redemption fails, users don’t retry politely. They abandon.
What worked? We implemented offline QR scanning on the vendor side:
Scans work without internet
Redemption data is stored locally
Sync happens automatically once connectivity returns
This single decision prevented thousands of failed transactions.
If you’re building anything QR-based, offline-first thinking is not optional.
Vendor Onboarding: The Silent Killer of Adoption
Vendor onboarding is where platforms quietly lose momentum.
CHIMAD required vendors to upload:
Business identifiers (NIF)
Personal IDs (DNI)
Representative documents
Initially, uploads failed frequently due to:
Large file sizes
Unsupported formats
Poor feedback loops
Vendors didn’t know why they were rejected.
Fixes that mattered:
Client-side file validation
Automatic image compression
Support for PDF/JPG/PNG only
Clear admin approval queues with status visibility
Transparency reduced vendor drop-off significantly.
A recurring lesson: Silence during onboarding feels like rejection.
Admin Dashboards: Where Scalability Is Won or Lost
Most founders underinvest in admin tooling.
CHIMAD’s admin dashboard had to manage:
Vendors
Users
Coupon campaigns
Redemptions
Analytics
As campaign volume increased, dashboards slowed down fast.
Performance problems we saw:
Large redemption datasets
Heavy analytics queries
Slow page loads during reporting
What fixed it:
Lazy loading instead of bulk fetches
Indexed database queries
Pre-aggregated analytics refreshed periodically
This reduced dashboard load times by 60%+ during peak usage.
Admin tools aren’t glamorous, but they determine whether your platform can operate at scale.
Security Decisions That Were Not Obvious
CHIMAD handled payments and rewards, which meant:
Abuse attempts were guaranteed
Coupon farming was inevitable
Replays and manipulation had to be expected
Instead of trying to detect abuse after it happened, we focused on preventing easy exploits:
Session-bound redemptions
Limited retry logic
Clear state transitions
The goal wasn’t to build an unbreakable system. It was to make abuse uneconomical.
Multilingual Support Isn’t Just Translation
We added multilingual support early, but the real challenge wasn’t language—it was clarity.
Error messages, permission prompts, and confirmations needed to:
Be understandable
Be explicit
Avoid legal ambiguity
Especially for:
Camera access (QR scanning)
Notifications
Location permissions
Ambiguous prompts reduce trust instantly.
Analytics: Useful Beats Impressive
We intentionally avoided “pretty dashboards” early on. Instead, we focused on analytics that answered:
Are campaigns being redeemed?
Where do users drop off?
Which vendors perform best?
When do systems slow down?
CSV export was more valuable than charts at first. This helped operators make decisions without needing analysts.
Market Reality Check (Why This Product Exists)
A few numbers that shaped our thinking:
Digital payments are growing aggressively
QR-based transactions are mainstream now
Digital coupons outperform paper by a wide margin
Admin self-service tools reduce operational costs dramatically
CHIMAD didn’t invent anything new. It connected existing behaviors into one coherent system. That’s often where real value lives.
What We’d Do the Same Again
If we had to rebuild CHIMAD from scratch, we’d still:
Design for three stakeholders from day one
Reduce login friction aggressively
Build an offline-first QR redemption
Invest early in admin tooling
Optimize dashboards before scale hits
These decisions paid off disproportionately.
What We’d Warn Other Builders About
If you’re building something similar:
Don’t overuse OTP
Don’t assume internet reliability
Don’t treat vendors as power users
Don’t postpone admin UX
Don’t underestimate data volume
Most platform failures are operational, not technical.
Final Thoughts
This Idea Usher review isn’t about celebrating a product. It’s about sharing what it actually takes to build a digital payments and rewards platform that survives real-world usage.
CHIMAD worked because:
It respected user time
It respected vendor effort
It respected operational reality
If you’re building in payments, loyalty, QR systems, or multi-stakeholder platforms, I hope this breakdown saves you some iteration cycles.
Happy to answer technical or product questions in the comments..
Replies