Timeline for How do we stop users overpaying in financial web forms?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2, 2012 at 0:07 | vote | accept | Jimmy Breck-McKye | ||
| Jun 14, 2012 at 8:25 | comment | added | Jørn E. Angeltveit | @DavidConrad, I was actually pretty skeptic to this solution myself, but I works very well. There are pros and cons to this solution, of course, but that's what the UX job is all about: Finding the optimal solution for the case you are working on. This is one of the alternatives to solve this question, and you have to test it properly and you must prioritize this aspect to other aspects regarding the payment process. It's a huge difference between an once-in-a-lifetime payment action (ie donation to FOSS project) and a ten-times-a-day payment routine (ie paying bills for your company). | |
| Jun 14, 2012 at 3:55 | comment | added | David Conrad | I am absolutely against using multiple fields for input of a single value. It's like the bad old days of three separate fields for the area code, exchange, and station of phone numbers. I'd prefer one of the other solutions. Or flip it around and let them enter in a single field, but show them separate pounds and pence when asking them to confirm. | |
| Jun 10, 2012 at 16:09 | comment | added | Jimmy Breck-McKye | I'm very keen on the concept of using a smaller textarea for numbers of lower magnitude. | |
| Jun 9, 2012 at 22:46 | history | answered | Jørn E. Angeltveit | CC BY-SA 3.0 |