1–10 of 10 posts
I thought the customer ALWAYS had to give a billing address on top of their Credit Card to prevent fraud charges.
How does Basecamp charge with no address?
The only two NECESSARY pieces of data are the CC number and the expiration date. ZIP code drops some of the risk, and, accordingly, drops a fraction off the percent you're charged by the processor.
On the web app we're about to launch, we only have the number and the expiration date. I'm hoping to get my act together to do some A/B tests, but we're going into it assuming that we'll do better with fewer fields to fill out.
Collecting a billing address or not doesn't do much to stem fraud when you're not shipping anything physical. Unless you're going to have your customers sign and mail/fax written authorization, you're going to have a hard time disputing chargebacks regardless.
It's not necessary. In fact, at some point I hope to write up a larger piece on it. The only two NECESSARY pieces of data are the CC number and the expiration date. ZIP code drops some of the risk, and, accordingly, drops a fraction off the percent you're charged by the processor. On the web app we're about to launch, we only have the number and the expiration date. I'm hoping to get my act together to do some A/B te…
It's not necessary. In fact, at some point I hope to write up a larger piece on it. The only two NECESSARY pieces of data are the CC number and the expiration date. ZIP code drops some of the risk, and, accordingly, drops a fraction off the percent you're charged by the processor. On the web app we're about to launch, we only have the number and the expiration date. I'm hoping to get my act together to do some A/B te…
I could be wrong, but I don't think the expiration date is necessary either. You have to send one to your gateway, but I don't think it's actually used for anything. You can keep charging cards that expired and have been reissued with the same number; I suspect if you send a valid card number with any future expiration date, it's going to work too.
It is easier to see the thief's risk/reward proposition when ordering a large screen TV with a stolen card than then signing up for a $50\month service. There as soon as you are discovered you loose access to the data that was the whole point anyway.
Not sure how Brain Tree handles that thing.
37Signals, and OrangeSlyce (my company) use Braintree which provides a VERY innovate solution called "Transparent Redirect". It allows you to accept credit cards directly on your site, with your domain, but the form posts directly to Braintree, and transparently redirects back to your site so the customer never leaves your domain. It's very cool stuff and I don't know of any other merchants that offer this.
Most importantly, the CC data never even enters your environment.