Recurly.js library released for secure, customizable checkout forms
1–10 of 41 posts
Re: Recurly.js library released for secure, customizable checkout forms
#2This is nice, but I sort of wish it stated more bluntly that it requires jQuery.
I also wish it didn't depend on jQuery, but that's just personal preference.
Re: Recurly.js library released for secure, customizable checkout forms
#3This is nice, but I sort of wish it stated more bluntly that it requires jQuery. I also wish it didn't depend on jQuery, but that's just personal preference.
I'm the author. I'll be sure to put a notice at the top of the readme that it requires jQuery. Also, I agree with you. The jQuery dependency will be removed eventually. It was a time saver in the short term as we do a lot of DOM manipulation.
Re: Recurly.js library released for secure, customizable checkout forms
#4PayPal should have been doing this years ago. Kudos to Recurly for bringing this to the public in front of Stripe which is still private.
Re: Recurly.js library released for secure, customizable checkout forms
#5This is nice, but I sort of wish it stated more bluntly that it requires jQuery. I also wish it didn't depend on jQuery, but that's just personal preference.
I'm the author. I'll be sure to put a notice at the top of the readme that it requires jQuery. Also, I agree with you. The jQuery dependency will be removed eventually. It was a time saver in the short term as we do a lot of DOM manipulation.
FYI: There are error in the display of the blogpost announcing it at: http://blog.recurly.com/
Re: Recurly.js library released for secure, customizable checkout forms
#6How is this PCI compliance?
You're exposing credit card number on the input field of the original publisher's HTML page. This means that the publisher can pick up the credit card number himself, or an included third party javascript library(like google analytics).
Re: Recurly.js library released for secure, customizable checkout forms
#7Is this accessible for audio browsers? Screen readers navigating by form elements will be pretty lost without s (and WAI-ARIA attributes for rich components, but one thing at a time).
Would hate to be the site that tried to simplify their billing but got an accessibility lawsuit[1] for their troubles.
[1]: http://en.wikipedia.org/wiki/National_Federation_of_the_Blin...
Re: Recurly.js library released for secure, customizable checkout forms
#8PayPal should have been doing this years ago. Kudos to Recurly for bringing this to the public in front of Stripe which is still private.
CheddarGetter has had this feature for awhile.
Re: Recurly.js library released for secure, customizable checkout forms
#9How is this PCI compliance? You're exposing credit card number on the input field of the original publisher's HTML page. This means that the publisher can pick up the credit card number himself, or an included third party javascript library(like google analytics).
The Recurly.js library dramatically reduces PCI compliance scope because the sensitive cardholder data does not pass thru your servers. There's a lot of additional PCI compliance issues when the credit card numbers pass thru your server, even if it only resides in memory during the request. Instead, the data is sent directly from the web browser to Recurly, who is PCI Level 1 Compliant.
Obviously, you still have to maintain a secure web server regardless of how you collect payments. That means protecting your users from cross site scripting.
Re: Recurly.js library released for secure, customizable checkout forms
#10How is this PCI compliance? You're exposing credit card number on the input field of the original publisher's HTML page. This means that the publisher can pick up the credit card number himself, or an included third party javascript library(like google analytics).
The Recurly.js library dramatically reduces PCI compliance scope because the sensitive cardholder data does not pass thru your servers. There's a lot of additional PCI compliance issues when the credit card numbers pass thru your server, even if it only resides in memory during the request. Instead, the data is sent directly from the web browser to Recurly, who is PCI Level 1 Compliant. Obviously, you still have to m…
... which thus precludes the security (and thus simplicity) aspect of Recurly.js.