One interview stuck with me. A café owner in Almaty. She had a notebook — handwritten, every QR transaction from the week logged manually. Not because she was old-fashioned. Because she built a system she could actually trust.
Her words: "I just need to know the money is there."
We had a perfectly functional confirmation screen. Green checkmark, amount, timestamp. She kept the notebook anyway.
That's not a UX failure. That's a trust failure.
After 60+ merchant interviews across HCB's platform, I stopped treating workarounds as problems to eliminate. They're signals. A merchant writing transactions by hand is telling you exactly what your product isn't giving them.
SMB merchants don't start from neutral. They start from a history of unexplained holds, silent failures, and support that couldn't explain where the money went for three days. That's the baseline you're designing into.
Don't remove the workaround. Raise the floor.
The instinct is to remove the workaround. Build a better flow, make the notebook unnecessary. That's the wrong read.
The right move is to give them better tools — fiscal receipts that are actually readable, push notifications with real settlement data instead of "payment received," integration with online cash registers so the transaction logs itself. Raise the floor. Make the workaround more reliable, or eventually unnecessary — but on their terms.
Trust in payment UX isn't built at the moment of success. It's built in every edge case you handled before this merchant ever opened your app.
Next: where drop-off analytics lie to you — and why the real problem is upstream.
