4 ms·
I have to disagree with the general feeling and the details of this. 1. The web sites for credit card processors & merchant account services are completely use
by swombat 18y ago
I have to disagree with the general feeling and the details of this.
1. The web sites for credit card processors & merchant account services are completely useless
That depends on the site. Protx has awesome documentation at http://techsupport.protx.com/ http://techsupport.protx.com/ (see the "Advice" bit on the left). I'd even use it when building for other providers, because much of it is very generic.
3. Address verification (AVS) is voodoo
All the verification systems are voodoo (except the security number). Hell, even the credit card number is voodoo. Why? Because the customer could have made a mistake while typing them in. The bank lets you decide how to handle it. That is a little unclear to most cc processing beginners, but it can be resolved easily: use 3D-secure. This shifts the liability back onto the bank and you don't have to worry about that crap anymore.
4. Test charges are pretty much unavoidable
Both of the times I've had to build a cc processing system, I haven't needed "test charges". If you really need to verify a card ahead of time, don't use test charges, charge a proper setup fee. Why do you think so many sites charge setup fees?
6. Errors are incomprehensible and your credit card processor is useless at helping you solve validation issues.
Dunno what kind of merchant they're using... I get descriptive errors from my accounts.
7. When you ask why stuff doesn’t work, even due to Stuff Nobody Told You, they think you’re kinda dumb.
Again, it goes back to the first point... get a better provider that has decent documentation.
Credit card processing is a pain, but it's not that terribly hard.
- ahoyhere 18y agoThe stuff listed in the article is true for one of the most popular / well-supported processing gateways, Auth.net. If there are better alternatives, we sure weren't able to find them. Their biggest competitor is TrustCommerce and they seem to have the same web site, information, support problems.
- josefresco 18y agoWe use Auth.net with one of our clients who processes an order about every 5 minutes around the clock. They started with LinkPoint which was horrible (bad support/high failure rates), and Auth.net is like a vacation in comparison.
- alex_c 18y agoCan I ask approximately what your client's failure rate is with Auth.net? This is a problem we're struggling with - out of 10 different payment attempts, we get maybe 1 successful payment (yes, some of the attempts are bogus, but that still seems pretty bad). It might be worth switching to Auth.net or something else, but the only reason would be the failure rates, and that information isn't very easy to find.
- swombat 18y agoFailure of what? legit transactions? Are you saying that there are times when someone enters data that you know is correct and it still fails you? That should never happen. If you have full AVS checking, you might hit against the incapability of most users (quite understandably) to type in their address exactly the same way as on their credit card bill. For this reason, we (at my previous start-up) disregarded the address part of the verification (but still required post code and CCV2). Address failures aren't a good indication of fraud, since most legit users will mistype their address.
- alex_c 18y agoWell, the payments seem to fail for every possible reason imaginable (and many of the error messages aren't very descriptive), so it feels like death by a thousand cuts. The problem is that we're new to this game, and reliable information seems surprisingly difficult to find. Maybe it's perfectly normal to see 9 out of 10 people entering bad information or carders trying out numbers, but that seems high to me, and tech support has been useless. We'll look into what AVS options we have available, and I'm also reading through the Protx link you posted.
- swombat 18y agoThis is a bit lengthy to debug via HN comments, but feel free to chat me on IRC (freenode), where I hang out as (predictably) swombat for a chat about this, I might be able to help in figuring out what's going on since I've implemented 2 such systems already...
- swombat 18y agoWell, you can't generalise from a single gateway. I'm not trying to generalise to say that what I'm saying is true for the whole industry, but I've used 2 different providers so far and not had the experience that you've had. So your article might have been better titled "6 things they don't tell you about authorize.net"...
- there 18y agoi'll disagree with #2 as well. i setup a merchant account with braintree and they handled the establishment of amex, discover, visa, and mastercard accounts all for me. the only thing i would add is that once you have your american express merchant account, login to their website and immediately switch to electronic statements. otherwise they charge you a $5 fee every month for paper statements.