- Posts: 130
- Thank you received: 19
Stripe.js with Memberhip Pro
- John Willems
- Topic Author
- Offline
- Premium Member
-
Less
More
8 years 8 months ago - 8 years 8 months ago #85715
by John Willems
Stripe.js with Memberhip Pro was created by John Willems
Can anyone explain how to integrate Stripe.js with MP?
I have the Stripe plugin and SSL which is required by Stripe. I am just wondering how difficult it would be to go to the next level and Stripe.js
If someone has done this I would love to hear how its done.
Thanks
I have the Stripe plugin and SSL which is required by Stripe. I am just wondering how difficult it would be to go to the next level and Stripe.js
If someone has done this I would love to hear how its done.
Thanks
Last edit: 8 years 8 months ago by John Willems.
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
-
8 years 8 months ago #85733
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Stripe.js with Memberhip Pro
Hi John
It is implemented in Membership Pro Stripe payment plugin by default, you don't have to do anything to implement it
Tuan
It is implemented in Membership Pro Stripe payment plugin by default, you don't have to do anything to implement it
Tuan
The following user(s) said Thank You: John Willems
Please Log in or Create an account to join the conversation.
- John Willems
- Topic Author
- Offline
- Premium Member
-
Less
More
- Posts: 130
- Thank you received: 19
8 years 8 months ago #85747
by John Willems
Replied by John Willems on topic Stripe.js with Memberhip Pro
I did know that, given what i have read about Stripe js that a really nice feature of the plugin.
Please Log in or Create an account to join the conversation.
- Tuan Pham Ngoc
- Offline
- Administrator
-
8 years 8 months ago #85761
by Tuan Pham Ngoc
Replied by Tuan Pham Ngoc on topic Stripe.js with Memberhip Pro
Yes. Basically, it pass credit card information directly from your browser to Stripe for encryption, then Stripe return back the encrypted data
So instead of submitting credit card information directly from your browser to the server where your website is hosted, we just pass the encrypted credit card data. It bring more secure to your subscribers, in this case, the only party we had to trust (which can get our credit card information) is Stripe
It's a nice feature. I think (with this implement, I think even your site doesn't have SSL certificate, the payment process still quite secure)
Tuan
So instead of submitting credit card information directly from your browser to the server where your website is hosted, we just pass the encrypted credit card data. It bring more secure to your subscribers, in this case, the only party we had to trust (which can get our credit card information) is Stripe
It's a nice feature. I think (with this implement, I think even your site doesn't have SSL certificate, the payment process still quite secure)
Tuan
Please Log in or Create an account to join the conversation.
- John Willems
- Topic Author
- Offline
- Premium Member
-
Less
More
- Posts: 130
- Thank you received: 19
8 years 8 months ago #85783
by John Willems
Replied by John Willems on topic Stripe.js with Memberhip Pro
There seems to be some advantage to having SSL with Stripe.js. Maybe its not a big issue, but from Stripe's documentation.
______________________________________________
" All Stripe users must be compliant with the PCI Data Security Standards (PCI DSS). Checkout and Stripe.js meets the requirements and security constraints of the Self Assessment Questionnaire (SAQ), SAQ A, by performing all transmission of sensitive cardholder data within an IFRAME served off of a stripe.com domain that is controlled by Stripe.
As long as you serve your payment pages over TLS, and use either Checkout or Stripe.js as the only way of handling card information, Stripe automatically creates a prefilled SAQ A questionnaire for you, and you won’t need to undergo a PCI audit. If card data is stored or transferred through your servers, you are responsible for following PCI DSS guidelines for handling card data, and periodic audits by a PCI-certified auditor. "
______________________________________________
" All Stripe users must be compliant with the PCI Data Security Standards (PCI DSS). Checkout and Stripe.js meets the requirements and security constraints of the Self Assessment Questionnaire (SAQ), SAQ A, by performing all transmission of sensitive cardholder data within an IFRAME served off of a stripe.com domain that is controlled by Stripe.
As long as you serve your payment pages over TLS, and use either Checkout or Stripe.js as the only way of handling card information, Stripe automatically creates a prefilled SAQ A questionnaire for you, and you won’t need to undergo a PCI audit. If card data is stored or transferred through your servers, you are responsible for following PCI DSS guidelines for handling card data, and periodic audits by a PCI-certified auditor. "
Please Log in or Create an account to join the conversation.
- spitjack
-
- Offline
- Elite Member
-
Less
More
- Posts: 234
- Thank you received: 4
8 years 8 months ago #86007
by spitjack
__
a 'spit' is a rod upon which savory food was roasted, turned in ancient times by a worker called a 'jack', a middle English word for an ordinary laborer (eg jack of all trades, steeplejack, lumberjack). Today, this job is usually referred to as a 'pitmaster'.
Replied by spitjack on topic Stripe.js with Memberhip Pro
Indeed, SSL really makes things go very smoothly. (It helps with PayPal as well, though for me, Stripe gives me far fewer problems no matter what configuration I'm running)
__
a 'spit' is a rod upon which savory food was roasted, turned in ancient times by a worker called a 'jack', a middle English word for an ordinary laborer (eg jack of all trades, steeplejack, lumberjack). Today, this job is usually referred to as a 'pitmaster'.
Please Log in or Create an account to join the conversation.
Support
Documentation
Information
Copyright © 2025 Joomla Extensions by Joomdonation. All Rights Reserved.
joomdonation.com is not affiliated with or endorsed by the Joomla! Project or Open Source Matters.
The Joomla! name and logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.
The Joomla! name and logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.