By Lau Linares, Lead Product Designer at Payabli
Picture this. You are at the store with a cart full of groceries, paying from the store’s own app, steering the cart with one hand and scanning items with the other. The checkout process is going smoothly: tap, tap, tap, payment method selected, card already on file. Then you notice the CVV field sitting empty and waiting for manual input. Damn!
So now, in the middle of a flow that was supposed to take seconds, you have to pull your cart to the corner, dig through your purse, and find the physical card you only hopefully remembered to bring. An experience that felt effortless a second ago has quietly fallen apart in your hands.
That single moment is what I want to talk about. The best payment experience is the one you never notice, and most of the time the reason we do notice is that something asked us to work harder than we should have, or honestly, harder than we want to (human laziness is a real thing).
What “disappearing” actually means
When I say a payment should disappear, I am not talking about hiding it or rushing it. I am talking about a flow that is fully there and working while the person using it barely feels its weight, with no friction, no broken steps, and none of that sinking “wait, do I really have to enter all of this again?” that turns a quick task into a chore.
Paying should feel like a single tap. Once you have lived inside something like Apple Pay or Tap to Pay, the traditional payment form starts to feel like a relic from another era. That is exactly why, at Payabli, the team has been building Tap to Pay into a dedicated SDK, one that turns an NFC-enabled iPhone into a payment terminal with no extra reader, no dongle, and no hardware at all, embedded directly inside our partners’ own apps. Working alongside engineering on it has only made me more convinced of the point: the bar today is the quiet absence of that long form asking for your full name, your card number, your CVV, and your zip code one more time, as if you had never been here before.
Everything I believe about this comes down to one idea that is almost embarrassingly simple: set and forget. A platform worth trusting should remember you.
The form is only the surface
Payment flows are one of the most used patterns in the entire world, and they are also, somehow, one of the most confusing. Even when every product is asking for the same handful of things, each one asks in a completely different way, stretching across one step or five, scattering buttons wherever they happen to fit, and rarely telling the user what comes next or why a particular field is even there. The styling changes from product to product while the underlying experience gets quietly ignored.
This is where I see platforms fool themselves, convinced they have modernized payments because they added a saved card or a shinier button. But storing a card and actually delivering ‘set and forget’ are two very different things. A flow that keeps your card on file yet still demands the CVV on every single purchase, exactly like my grocery story, has done the technical work while letting the design betray the person it was supposed to serve.
A lot of what passes for modern payment UI is really just a prettier version of the same form, dressed up with new colors and rounded corners while keeping the same four fields underneath. The question worth asking was never how to style the form, but whether the form needed to be there at all.
Trust is earned across the whole relationship
Here is the part that tends to get skipped: invisibility only works once trust has already been built. The flows that feel like magic feel that way precisely because the company behind them earned that credential long before you reached the checkout. A platform that has not yet earned the same trust cannot simply borrow the button and expect the feeling to come along with it.
And trust reveals itself most clearly at the scariest moment of any flow, the second right after you hit pay. What is actually running through someone’s mind is fear in its plainest form: where did my money go, am I about to be charged twice, do I need to wait, what just happened?
When you press “Pay” and the screen answers with “Something went wrong” instead of a clear, calm confirmation, the spell breaks and the trust goes with it. That is why designing payments has so little to do with the form itself, and so much to do with whether the platform is reliable enough that the fear never has a chance to surface.
What I want our designers to carry with them
Confidence was never something you build by adding steps. It grows out of the boring and invisible work of storing the right data, remembering the user, and confirming clearly and immediately that the money moved. Get that right, and the payment disappears in the best possible way.
So my take, as the designer behind a lot of these flows, is to stop polishing the form and start questioning it. Kill every moment where we ask people to re-prove something they already handed us, and treat returning users like we actually know them, because we do.
The magic was never the button. The magic is the moment someone taps “Pay” and feels absolutely nothing, because somewhere along the way they stopped worrying and simply trusted that it would work.
Gracias por el cafecito. Now go delete a form field.