Fintech engineering
A payment is a journey, not a button.
A useful payment experience explains what happens before, during and after money moves.
HASRIN EDITORIAL · ENGINEERING NOTES
Start with explicit states
Pending, successful, failed and reversed are different states. Model them explicitly. A timeout does not prove that a payment failed; the provider may still be processing it.
Treat retries as a design decision
Use stable transaction references and idempotency controls. A user tapping twice or a server retrying should not create an unintended duplicate transaction.
Build reconciliation into the product
Verify provider events, record an audit trail and reconcile against an authoritative source. Give support staff enough context to investigate without exposing sensitive customer data.
Design the waiting experience
Explain what is known, what is still being checked and what the user should do next. Clear status communication is part of financial infrastructure.