> This means that their credit card details never hit your server. One thing I've been seeing recently is that some implementations using Stripe DO have the CC details hitting their server. The most common case being when Javascript is disabled the form posts to the website because the developer didn't design with graceful degradation, a dangerous mistake when mixed with credit card numbers. It doesn't appear to be a…
Stripe And A/B Testing Made Me A Small Fortune
41–50 of 164 posts
Re: Stripe And A/B Testing Made Me A Small Fortune
#42Earlier quoted context omitted.
I worked on something with credit card processing a few years ago. As I remember, it doesn't really matter if the details hit your server, but the point is you absolutely can not save them. No putting them in a DB, no putting the in a log file (not even the last four or something like that), nothing. So if your form takes the numbers in, you make an API call, and then you blank them in memory you were OK. If you put…
To make sure there isn't confusion here, having card details go through your server, even if you aren't saving them, still can lead to certain PCI compliance burdens (e.g. you may need to get an audit from a PCI auditor verifying this). Having the card never go to your server is the best way to make sure you are PCI compliant, as you mention.
Re: Stripe And A/B Testing Made Me A Small Fortune
#43Or spend a few hours, get a merchant account through a bank and authorize.net with much lower fees and a pretty standard API. Tons of classes to use authorize.net with and super simple... no point of adding ANOTHER layer... charging with a merchant account is trivial.
That's what a company I worked with did, and I thought it was a bad decision. The per-transaction fees are lower, but there is a monthly (or yearly) cost. The API is big because it covers so many cases that you probably won't use. Plus there are fees. Sure, they'll let you do e-checks (every customer wants those, right?), but that's a fee. Return? That's a fee. Chargeback? Fee. Process transactions in real-time inste…
You have no clue what you're talking about. I guarantee Stripe will charge you CB fees too.
Only way Stripe is worth the time and % they jack it up is if you do LOW volume.
edit: 5 seconds in google and Stripe charges $15 for a chargeback, same as Chase. Basically paying Stripe 1% + another $0.15 or so per transaction. NO THANKS! No one doing any type of CC volume would be dumb enough to give that $ away.
Re: Stripe And A/B Testing Made Me A Small Fortune
#44Re: Stripe And A/B Testing Made Me A Small Fortune
#45Stripe is a great service, but I get the feeling their PR company or marketing department promotes extensively here (Makes sense since its the target audience).
For what it's worth, we don't have a PR company or marketing department currently =). We try not to post on HN unless we actually think people on HN will like the content (and we've argued internally before and decided not to post stuff to HN because it didn't seem useful enough).
Re: Stripe And A/B Testing Made Me A Small Fortune
#46In case anyone is curious, here's Patrick's sales graph: http://www.bingocardcreator.com/stats/sales-by-month You can see the big jump in May-July (although the jump for July is 32%, not 53%)
Oopsie. Thanks for the correction.
Re: Stripe And A/B Testing Made Me A Small Fortune
#47Just curious: are there any good options outside the US?
[I used to work for 2co. I don't any more.]
Re: Stripe And A/B Testing Made Me A Small Fortune
#48Or spend a few hours, get a merchant account through a bank and authorize.net with much lower fees and a pretty standard API. Tons of classes to use authorize.net with and super simple... no point of adding ANOTHER layer... charging with a merchant account is trivial.
Also, we have volume discounts for people processing more than a million dollars a year, so this may be something you'd be interested in.
Re: Stripe And A/B Testing Made Me A Small Fortune
#49Earlier quoted context omitted.
I worked on something with credit card processing a few years ago. As I remember, it doesn't really matter if the details hit your server, but the point is you absolutely can not save them. No putting them in a DB, no putting the in a log file (not even the last four or something like that), nothing. So if your form takes the numbers in, you make an API call, and then you blank them in memory you were OK. If you put…
To make sure there isn't confusion here, having card details go through your server, even if you aren't saving them, still can lead to certain PCI compliance burdens (e.g. you may need to get an audit from a PCI auditor verifying this). Having the card never go to your server is the best way to make sure you are PCI compliant, as you mention.
From data security standpoint is is easier to let somebody else do it, but end users tend to have a less satisfying checkout experience.
Re: Stripe And A/B Testing Made Me A Small Fortune
#50Patrick, I'm curious how you have been using Stripe as you are in Japan and it seems they only recently began expanding out of America. Is the business entity behind BCC registered in the US?