Client wanted “Swipe to Pay” button on the payment confirmation screen. They had another app as reference and liked that interaction for the CTA.
Before touching anything, I asked if this would apply to every payment or only selected ones. This question matter more. Users make 5–20 payments in a single session. A logistics manager paying drivers after a shift is not doing one payment and logging off, He is going through this flow many times in working hours.
Making user swipe every single time would just add friction to something he does on repeat.
The client’s concern is not wrong either. For a large transfer, accidental confirmation is a real risk. So instead of treating Swipe to Pay is good or bad, I looked at where it actually make sense.
Regular payments kept the normal button. Bulk and higher-volumes got the swipe confirmation.
₹8,000 driver advance? Normal button. ₹1,45,000 transfer to five people? Swipe.
I have not scraped what client told me. I just do not force every user through it every time.
It’s a small UI call, but these are usually the conversations I find more useful than debating whether a button should look one way or another.