Hacker News Reader

Comment by sfjustin | Hacker News Reader

CheddarGetter has had this feature for awhile.

I just looked and wasn't able to find it. For one, CheddarGetter looks to be a hosted provider whereas Recurly and Stripe support buyers remaining on the merchant's web pages. But the main feature I was referencing was a JavaScript library that handles credit card information so that the merchant never sees a credit card number and thus need not worry about PCI compliance. That historically has not been provided in a way that allows the payer to remain on the merchant's web page.

I think Braintree does it, kind of: "By using our Transparent Redirect (TR) and Vault, merchants can achieve PCI Compliance in days. TR and the Vault will eliminate the handling, processing or storing credit card data so you can qualify for the Self Assessment Questionnaire A, the shortest of the four SAQs."

http://www.braintreepayments.com/services/pci-compliance

edit: So, w/ Recurly I wonder if it's the same thing and I'd need to do the Self Assessment Questionnaire A when using recurly.js

With Recurly.js and our Transparent Post, merchants only need to fill out the Self Assessment Questionnaire A.

We launched our own Transparent Post back in March 2011. We created Recurly.js to simplify performing client-side validation, pricing calculations (w/ coupons, VAT, add-ons), and proper error handling when a transaction is declined. It's 10x easier to implement than Transparent Post, and has a much better user experience for the customer.

Thanks for spelling that out for me. As for being simple - I have begun teaching myself somewhat recently while looking for a good match w/ someone more technical. I can really only handle html & css at this point - sad I know. Anyways, this was very easy for me to setup. I've already got it going on my site w/ sandbox account.

But, going to hold off for now and just use hosted payment pages for a bit. Will likely use this in the near future though - thanks to the Recurly team.

Ok, I see, so it's a bit different from Stripe's approach which to actually Ajax the cc# to stripe's server and return a token which the merchant then uses as a proxy for thee cc in normal API calls. I think they claim to obviate the self-exam for merchants despite it being materially similar to e transparent post.

It is indeed. Recurly has really improved over time, you have been doing a great job. It is so much easier to set up subscription payments today (with a solution like Recurly) than it was 2-3 years ago. Keep up the good work!

Reply on news.ycombinator.com