4 ms·
if you want to test willingness to pay you should try to recreate real conditions as much as possible to get usable test results. You would probably get a much
by fookyong 16y ago
if you want to test willingness to pay you should try to recreate real conditions as much as possible to get usable test results. You would probably get a much better response if:
1) the page had SSL
2) you show what cards you accept (i.e. logos)
3) you require the buyer's name (sounds suspicious to not require it)
4) you show a paypal button as an alternative option*
It sounds like you're just doing an MVC for payments to see if people would pay. If you're pleased with the MVC conversion rate now, I bet you'd be ecstatic if you implemented the above. I wouldn't be surprised to see a 5~10% uptick in conversion.
*anecdotally speaking, I would have totally clicked through if you had a paypal button.
- pclark 16y agodo you think #1, #2 and #3 would really make a difference? I would have thought most users (including me) when it comes to payment are simply thinking "blah blah blah take my money"
- fookyong 16y agoI don't think, I know :) Worked in ecommerce, handled millions of credit card transactions, tested extensively.
- dcurtis 16y agoRegarding 1, it actually does post the payment over HTTPS via javascript directly to the payment processor from your browser. I wasn't really trying to do a controlled experiment, otherwise I would have done the other things you describe.
- fookyong 16y agodcurtis > yeah I figured the ajax post operation would be over HTTPS, but still - a user would want to see the little padlock sign on the browser regardless :) the illusion of security is just as important as actual security!