9 ms·
Payment iframe - the easiest way to insert Stripe into your website
- benblodgett 14y agoStripe is meant for developers, and it is quite easy to integrate using their javascript api. If you can code a form you write basic javascript you can integrate stripe.
- xyzzyb 14y agoExactly. Stripe is probably one of the easiest integrations I've ever done. In fact, their tutorials are so well written and their signup so frictionless that I'd say that any interested website creator should have little trouble setting up a form actually using stripe instead of an iframe.
- infinite8s 14y agoThe whole point of the iframe is that it prevents the code from inside the iframe (ie the payment handling code that sends data to stripe) from having access to the parent page's data. Sometimes the CC info isn't the most sensitive info a user has given that website (particularly for a service that manages your online backups).
- pilif 14y agoBy including their JS, you give them full access to all of the contents of your payment page and depending on how you have configured your session cookie or depending on the browser, full access to the users session. Now in general, you can probably trust them, but what if they are compromised? By using an iframe you make sure that they do not get access to any information on your page - much less the users session cookie.
- JSadowski 14y agoAnd you can accomplish the same thing by using an iframe that you have full control over. Instead, if you use this service, you're trusting another 3rd party site to be available and to not be compromised.
- tptacek 14y agoThat is true, but the point is that the only thing that is going to be compromised is the data that would be going to Stripe. I know it is shocking to many of you to hear this, but the data Stripe collects is not really the most sensitive information on the Internet. The point of the iframe is to contain the damage from any possible compromise. If PAYMENTIFRAME.COM is insecure (heh), you still aren't going to lose user sessions to your actual application.
- JSadowski 14y agoNo, just potentially their credit card information.
- cperciva 14y agoI've been hanging out in the Stripe Campfire chat for the past week. There's a rather scary number of people who need something like this.
- TomGullen 14y ago> one of the basic principles of security is to avoid trusting people unnecessarily And asking customers to enter their CC details on your domain doesn't break this rule? > a form will be submitted to your server with a stripe_token for you to process I'm assuming it just sends the Stripe token, and not CC info? If it does send CC info, I assume it's compliant with all the laws and regulations in every country?
- cperciva 14y agoasking customers to enter their CC details on your page doesn't break this rule? It doesn't break that rule for me. It is a reason why other Stripe users might want to think twice before using the iframe I host, of course. I'm assuming it just sends the Stripe token, and not CC info? Yes.
- TomGullen 14y ago> It is a reason why other Stripe users might want to think twice before using the iframe I host, of course. Well that's the point really. You say that a "basic principle of security" is to "avoid trusting people unnecessarily" which is exactly what this service you have created is asking people to do.
- cperciva 14y agoI'm not asking anyone to use this, just making it available to people who want it and showing off a concept which people can re-implement themselves.
- TomGullen 14y agoDo you not think the way you have presented it is encouraging people to use it? I love Stripe, I love people hacking and creating new cool things but an emerging trend I'm seeing with Stripe is that people are really not taking the security of the CC numbers their customers have entrusted to them as cautiously and as securely as they should.
- sudaily 14y agoOr use an authorize.net form and save a ton of $ on Stripe's ripoff fees!
- suweekly 14y agoOr use authorize.net's iframe module and save a ton of $ on Stripe's ripoff fees.
- Zr40 14y agohttp://www.authorize.net/files/cybersource_pricing.pdf http://www.authorize.net/files/cybersource_pricing.pdf Ignoring all those extra fees and charges unrelated to a single payment, Authorize.net charges 2.19% + $0.27 in the best case (qualified domestic Visa). In the worst case (non-qualified international MasterCard), they charge 4.49% + $0.2685. Even only considering the best case, Stripe's 2.9% + $0.30 doesn't seem 'ripoff' to me.
- suweekly 14y agoGet the merch acct through Chase, gateway through auth.net - BIG SAVINGS!
- majke 14y agoIframes can leak key presses to an evil parent frame: https://www.owasp.org/index.php/Cross_Frame_Scripting https://www.owasp.org/index.php/Cross_Frame_Scripting > Every key press the browser user makes in the example.com frame, while trying to log into example.com, can be captured by the attacker, and reported back to evil.com. But this is irrelevant - user can't verify if the domain of the iframe is trusted. If the attacker can modify the parent frame javascript he can just replace the iframe with a phishing page.
- cperciva 14y agoThe point of a payment iframe is to keep javascript inside the frame from doing anything evil to the site outside the frame, not vice versa.
- sergiotapia 14y agoI would never ever use this. Too much of a security risk.
- bentlegen 14y agoPlease don't use this. There is nothing stopping paymentiframe.com from taking your customer's credit card numbers.
- DASD 14y agoBen, Are you going to be addressing this in your book, Third Party Javascript? Would love to hear your recommendations for how to handle payment processing such as this.
- bentlegen 14y agoThe book describes techniques that Stripe could use in developing their own iframed credit card form. I'd only trust a solution from them directly.
- tptacek 14y agoThat doesn't make any sense, because the whole point of PAYMENTIFRAME.COM is that you don't trust Stripe. Colin implemented this because besides credit card numbers, he was unwilling to give Stripe control over his website. Colin's users trust him with things that are much more sensitive than credit card numbers.
- DASD 14y agoPeople trust Stripe. I think the issue here is Javascript and origin-policy and relinquishing control. When Stripe releases their version of STRIPEPAYMENTIFRAME.COM as an iframe solution then this can go away. I believe Colin mentioned a need for this now rather than waiting for Stripe. Interesting side note: Yes I know it's only meant to be a demonstration site but PAYMENTIFRAME.COM is using Google Analytics. Oh HAI GA...what's my Security Code again? Just needed a nice chuckle before I head back from lunch.
- tptacek 14y agoColin trusts Stripe to collect credit cards. He does not trust them for anything else. Embedding the form on a page on TARSNAP.COM trusts them for everything that can happen on any web application on the same domain.
- kevinsimper 14y agoThis may be even more unsecure. Who would like their user to put in their creditcard information on a unknown site? The change for that paymentiframe.com get comprimised I see is way higher, than Stripe is getting comprimised.
- cperciva 14y agoThe [chance] for that paymentiframe.com get compromised I see is way higher, than Stripe is getting compromised. We'll have to agree to disagree about that. Not that there's anything wrong with Stripe's security, but I know a little bit about the subject too. :-)
- gatordan 14y agoI have to agree with everyone here that this doesn't make sense. I'm currently working on integrating Stripe into my application to create a subscription system. By far the easiest part has been payment form. In their tutorial they have a basic form that you can plug into a .html file and create test customers within minutes. It's laid out in 3 well documented steps in that link he calls "daunting".
- estel 14y agoWould using this service affect one's PCI DSS compliance?
- cperciva 14y agoNot based on my understanding of PCI DSS.
- jellicle 14y agoMerchants are either required to be PCI DSS compliant themselves or outsource their card-handling only to third-party entities who are PCI DSS compliant themselves. So, one of two things is true: -- Paymentiframe/tarsnap is a PCI DSS compliant third party -- the merchant is intentionally violating the PCI DSS rules by sending credit card data to you So, which is it?
- cperciva 14y agoNobody is sending credit card data to me. I'm serving up a form with javascript which sends the credit card data directly to Stripe.
- mrgreenfur 14y agoThis is a lovely form. Ideally, Stripe would offer something like this as a way to quickly generate a nice cc entry form with the intention that site owners would put the generated code directly on their site, or that stripe would host the service themselves. After all, you're already trusting them to run the service, might as well trust them to run the form too. Not that it's terribly hard to build a stripe-compatible form...
- cperciva 14y agosite owners would put the generated code directly on their site That would defeat the protection which the Same Origin policy gives you (since the iframe would have the same origin as the rest of your site). or that stripe would host the service themselves Yes, that would be much better.
- mrgreenfur 14y agoI meant that they'd put it directly on their pages, no iframe needed. Agree that it'd be much better if Stripe just did it themselves.
- cperciva 14y agoI meant that they'd put it directly on their pages, no iframe needed. At the expense of loading third party javascript directly into their pages, you mean?
- mrgreenfur 14y agoYeah, I guess that misses the point of isolating the javascript, doesn't it? So, the idea is good, but has to be offered by Stripe to really minimize any exposure.
- staunch 14y agoIf I was Stripe I'd be politely asking you to take this down. It's using their trademark (presumably) without permission and encouraging their users to do something very inadvisable. Offering to host this seems like a really bad idea. I know you're well meaning and trustworthy, but this shouldn't be run by a third party. For long term reliability reasons as much as security.
- cperciva 14y agoI showed it to people at Stripe before announcing it.
- lsh123 14y agohttp://www.wepay.com/api http://www.wepay.com/api