Hot answers tagged

3

Those verification methods are common and could be viable, but the underlying app may have conceptual problems. There's a lot to unpack here, so bear with me. For starters, it sounds like users would be paying for the ability to let people they don't know send them messages they don't want. You'd basically be inheriting all of the problems of Twitter ...


3

I would be more explicit with the 11/31 calculation. I would also separate the numbers from the explanation in the calculation to make it more easily readable.


2

Short answer Grey out is probably better than hiding, but only doing the one or the other is not going to solve the customer problem. Why are customers confused? Customers usually have preferred payment and delivery methods. They don't like if a shop doesn't offer their preferred methods (but still might want to buy). What confuses them is if a method is ...


2

Don't ask for payment upfront. I can tell you from experience that this is a UX disaster. One example that comes to mind was the Ouya game console that once you powered it up it asked for payment details, first thing. Offer value first, earn your user's trust and then ask for payment. Also, consider offering multiple ways of payment and built-in methods (...


2

I like keeping the up-sell right within the context of using the product. You aren't forcing the user to click on something before they find out it isn't available and you aren't hiding the functionality either. But of which could lead to more frustration than seeing the up-sell prompts. If you are concerned about it being overwhelming for users maybe you ...


1

E-transfers are email money transfers and they're all processed by interac.ca. It's super popular and super convenient because all you need is a person's email address or cell phone number. You used to only be able to use email, but recently they added the text option. The way to send an e-transfer is through your own bank. Your bank has to partner with ...


1

if i'm not wrong there's 2 questions you are asking here. One is how to communicate the payment models clearly. The other how to communicate setting up the payment method. for 1 you should ONLY focus on communicating both models as 2 options so the user can decide on one. e.g. Choose a payment model Option 1: Pay direct after you ride (you will be charged ...


1

I would suggest that you provide the user with a more specific explanation of how you are calculating the costs. Don't just rely on a simple table of values. For example, add some information before the cost breakdown: The price at checkout is calculated on a pro-rata basis for the remaining days in this month. You will initially pay $1.41 per mobile device ...


1

If the donation method needs explanation, maybe you have to consider one that doesn't. If it's not avoidable, then the user might be given a choice between showing and hiding the payment instruction.


1

I think collecting online donations should be easy, affordable and transparent. Showing payment-related FAQ/instructions at the end of the page will make sense.


Only top voted, non community-wiki answers of a minimum length are eligible