We actually require that our users use SSL on their payment pages. We describe the requirements (and motivations) in more detail at https://stripe.com/help/ssl.
Re:Stripe CEO Discusses Online Payment Service
by storborg on Saturday March 03, 2012 @10:07PM
(#3661811)
I don't believe it's possible for a site accepting credit cards on a non-SSL page to be PCI compliant, period, no exceptions. It's trivial to MITM to steal your card info.
Re:Stripe CEO Discusses Online Payment Service
by eurleif on Saturday March 03, 2012 @10:11PM
(#3661818)
The merchant's page is loaded over an insecure connection, but the credit card details are sent to Stripe's servers over a secure connection using an iframe. So it's secure; the customer just can't verify that it is without looking at the source.
Re:Stripe CEO Discusses Online Payment Service
by delroth on Sunday March 04, 2012 @02:21AM
(#3662228)
If the merchant's page include any Javascript over an insecure connection (for example, jQuery from a CDN) then an attacker can intercept this connection and replace the Javascript by a malicious script that will remove Stripe's iframe and replace it by any other iframe.
So yes, passive network sniffing won't work with Stripe's iframe being loaded over HTTPS, but this does not protect against any type of "active" man in the middle attack.
Re:Stripe CEO Discusses Online Payment Service
by ZiadHilal on Saturday March 03, 2012 @11:15PM
(#3661952)
Not exactly. Iframes aren't involved (yuck how ugly!). Javascript is used to catch the form's submit, all the data on the form (credit card info) is sent straight to Stripe's server over https (via AJAX) and then their server sends back a response.
Their implementation is both elegant and smart. Even easier than Braintree.
Re:Stripe CEO Discusses Online Payment Service
by eurleif on Saturday March 03, 2012 @11:30PM
(#3661984)
There seems to be an iframe involved: http://i.imgur.com/R4efp.png
So maybe Stripe is secure, but they might want to work on appearing more trustworthy.
When I've used PayPal as a customer, it asked for my credit card on its own domain, not the merchant's. Doesn't that insulate the merchant from handling credit card details at least as well as Stripe's API does?