Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Information required for checkouts when customers aren't using a paymentprovider-account (like PayPal) can be entered in the actual order process. And if the customer is indeed using an account at the payment provider, chances are, the payment provider already has that info. So whether it has to be entered depends on payment method.
-
Requirement checking should be added to the required fields of your workflow...
Just saying. -
Agree with Okto and CM. I hate app and websites that ask everything since the very beginning. You can ask me payment related info after I want to proceed with buying. I want to browse around first.
-
@daniel-wu yeah, well, our product has a free trial which still requires a credit card, and the entire subscription management logic is handled by the payment processor
But we were asking for way more info than necessary even for payment, I can see it putting off potential customers -
Defirence62yCan relate, feels like the past 2+ years I've dealt with the exact same scenario. Today it's gotten so much worse that there's days like today where I want to bash my head into the desk repeatedly because none of my coworkers listen to what I say and always have some smartass comment to make despite never working on what I did or knowing even 0.1% of how it works. Good luck.
-
Defirence62y@nanobot Pretty normal thing to do for KYC, AML and so on so forth. I do agree though a true "free trial" should ask for payment details AFTER your trial is complete.
-
@nururururu The easiest way to make potential customers not even try your product is to ask for a credit card for the "free trial". People by now expect shenanigans like automatic subscriptions and shit when they have to enter their credit card details before they actually should be needed.
Also, asking for payment details triggers a premature cost-value analysis before the user used your product even once - that might lead to "nah, it won't be worth a subscription anyways" reaction without your product even getting any chance of proving itself.
Ask for credit card info after the user already committed to a buy. At that point, they want to give you that info. -
Bibbit7371ySounds like you now have a perfectly good reason during future sprint plannings to refuse picking up any work that's not properly refined :)
Requirements are like half the info you often need.. -
Honestly agree with most of above.
Free trail allows you to show of what they can do.
Then again you will have to deal with free loaders unless you ask for enough information to block someone doing repeated trails.
So there is something to be said about locking it behind something that can tie it to a person.
Honestly I personally like when they ask for info when its required. Like bitch you dont need my address unless you gotta ship something.
We had a sprint where we removed some fields from the signup page, in order not to "scare users off" with the amount of information requested. Quite a few changes in frontend and backend alike.
Only now in the final day of the sprint (where we're supposed to deploy the changes) do we realize some of that information is actually required by the payment processor, and likely for very predictable *legal* reasons which I even questioned during planning.
rant