Users are surprised that there's a confirmation step the first time they bid

[dblock]

A user bids in the last seconds only to discover that there's a confirmation step. Improve UI in a way that makes it clear that there will be a confirmation step.

[katarinabatina]

@dblock I see the problem here but I don't understand how telling them that there is a confirmation step will help them understand that their bid won't be placed in time. Seems like we need a slightly more holistic approach to solving this issue. I typically find that a line of copy is lost on a user who just wants to bid (this was true in the early days of user testing a prototype where there was much copy explaining each step)

[dblock]

Totally agree @katarinabatina. An example would be changing the "Bid" button to "Bid (You will be asked to confirm)", obviously that really ugly, I don't know what the solution is, but I know it's a problem :)

[dblock]

One idea that comes to mind is if instead of "Bid" it said "Next" as you start typing a number.

[ashfurrow]

We could examine ways to make the process faster. Maybe use CC as a form of user authentication somehow? That way it's enter number - bid - swipe - done.

[alloy]

As far as I understand the problem, I agree with @ashfurrow. Isn’t having the payment go through the most important detail? You can deal with the personal details after the payment has gone through.

[katarinabatina]

@ashfurrow I like the idea of using the CC as a personal identifier but that is probably a larger change out of scope for the immediate future.

@alloy getting a CC for unregistered users is the most important however to figure out whether or not they are registered we need to ask for personal details upfront...hence the cc swipe coming later in the flow.

[alloy]

Just want to put this out there, but even with this there are still plenty of design/implementation questions (listed at the bottom).

I assume the creditcard details are being stored on Stripe for later use? If so, Stripe offers a ‘fingerprint’ for each stored creditcard that can be used to identify a creditcard later on: https://stripe.com/docs/api#card_object

i.e. if I create an account and store my creditcard then Artsy can store the fingerprint of that creditcard along with my account and next time I use my creditcard Artsy can find my account by that fingerprint.

• when a creditcard’s fingerprint is not found in the Artsy DB it could either be a new customer or an existing one using a different creditcard
• when there are multiple Artsy accounts using the same creditcard