5 ms·
As the article points out, if someone can inject Javascript into your checkout page, you're most likely also having other security issues. Still, and I'm prett
by mrweasel 10y ago
As the article points out, if someone can inject Javascript into your checkout page, you're most likely also having other security issues.
Still, and I'm pretty much being called an idiot every time I point this out: You should NEVER have the user enter credit card information on your site. That is something that is best left to your PSP. If you're Amazon or similar size, fine, I can accept that you most likely have the need resources. Anyone smaller should never interact with credit card information, leave it to Stripe, BrainTree, Paypal, someone trusted, with the resources to handle it.
Also I'm not really surprised to see that it seem to be affecting Magento shops. Similarly to not accepting credit card directly: If you don't have the technical resource, don't run Magento. It's big and complicated, and you need to react fast when there's a problem. Contracting is an option, but expensive and the turn around time is a lot higher, especially if there's a critical error in Magento and everyone need the issue fixed right then and there.
- notmything 10y agoI work in ecommerce consulting - most of my clients take CC info on their site, the forms on the checkout POST (over SSL) to the PSP who then return a token to the site, all future transactions use the token. Most people don't want to bounce customers to a third party site for payment, it really hurts conversions.
- 4ad 10y agoI certainly hate it when merchants bounce me to a different site. It's most likely I will never complete the transaction and just buy from Amazon instead. If your site sacrifices user experience, I will hate your site. Simple as that. Amazon understands the convenience factor really well. I hope Apple Pay (on the web) takes off. While I don't like yet another middle man, and I don't care about its security benefits in the slightest, I appreciate the consistent and convenient interface it provides, so I will use it, if offered the choice.
- enraged_camel 10y ago>>If your site sacrifices user experience, I will hate your site. Simple as that. Even if said sacrifice keeps your credit card safe? I mean, if you are staying on the same site, you have no guarantees that the site isn't storing your credit card info in an unsecure manner.
- 4ad 10y agoI don't care about keeping my credit card safer that it already is. I am not liable for credit card fraud. In this insecure world we live in, I have not lost a single dime, nor any time, nor was I inconvenienced in any way by card theft. It's not my problem to worry about. My debit card was skimmed once, a few weeks ago. The bank detected fraud, notified me that they sent me a new card, and I didn't lost any money. I only lost two minutes of my life while I was talking to the bank on the phone.
- Cyph0n 10y agoI'm assuming you ended up with no debit card for a few days at least. That's a huge inconvenience in my opinion.
- 4ad 10y agoNo, because I have many debit cards from different banks in order to have redundancy and increase availability when the bank's system is down, or a particular card simply won't work at some merchant, but other will (usually happens in the US with my European cards).
- kalleboo 10y ago> it really hurts conversions This. We saw about 50% would prefer on-site transactions, 50% would prefer off-site transactions (PayPal or Amazon payments). Remove one of the options and half your customers just disappear.
- bemmu 10y agoWas about preference, or maybe most people just shrug and choose one at random?
- Silhouette 10y agoMost people don't want to bounce customers to a third party site for payment, it really hurts conversions. That is certainly true in my experience. Also, some of the payment services have a habit of changing the appearance and/or behaviour of their hosted systems, sometimes not for the better, and typically without warning. That is a risk you might not be willing to take for something as important as your payment flow. I know of at least one local business that switched from Stripe Checkout to using Stripe.js from their own site as a direct result of Checkout being significantly changed and resulting in customer support enquiries about the new behaviour that the business had no idea how to answer.
- phereford 10y agoI've worked with similar organizations that want the transaction on their site due to all the reasons mentioned in the comments. There are providers that use JavaScript to allow you to take payment information on your platform but never let the sensitive details hit your server. I believe this removes your platform as an attack vector for leaking credentials. The only locations that have traces of that information are the browser and the payment provider.
- Silhouette 10y agoUnfortunately, even if your payment service is hosting the system that processes the sensitive details, there's always an element of vulnerability on the merchant's side if they are hosting the rest of the site, simply because a compromise could redirect customers to a hostile alternative site to collect those sensitive details. At that point, they're really no better off than a completely fake site that never had any real relationship with a payment service at all. Merchants should always be serving their own pages securely for this among other reasons, even if they are never intending to receive sensitive payment credentials.
- phereford 10y agoYou are absolutely right.
- 10y ago
- cillian64 10y agoI don't understand this at all. I really, really don't want to give my credit card details to some random webshop who are exceedingly unlikely to have solid security. If I can use PayPal or another well known payment provider, great, I don't even have to type in my details. But even a less well known PSP is more likely to get it right than a small business webshop. A slightly jarring user interface seems a small price to pay for a much lower chance of my payment details being compromised. Is this a minority view?
- 4ad 10y agoI am not liable for credit card fraud. The last thing in the world I want is inconvenience for me, when it's other people's money at risk (bank, merchant, CC company, whoever), not mine. On the other hand, Paypal itself is a liability. Blocking your account (and your money!) for months without recourse, randomly reducing expense limits to nothing (50 EUR) are not just some Internet stories, but things that have happened to me personally multiple times. When my card was stolen (debit card even!), I didn't lose a dime, nor time. Bank just sent me a new card the same day. I didn't even have to report the fraud, they detected it themselves, as they are really good at that. They just called me to tell me about it, and that they sent me a new card.
- jjnoakes 10y agoYou aren't liable for credit card fraud, but that money comes from somewhere. Today it is a small percentage charged to the vendor; do they pass it on? And tomorrow, when the problem gets worse and the fees start to climb, will you still not care? Why be content with a system that may indirectly charge you for other people's lack of security? Why not look for ways to focus the cost on the vendors who lack security?
- ek750 10y agoYes, you're right, they pass it on. But as costs start to get noticible to the involved parties (direct and indirect), hopefully that would prod the ones that don't care now, to start.
- mrweasel 10y ago>it really hurts conversions That has to be a local issue, because that is flat out wrong. The majority of all e-commerce sites does exactly that. I have yet to meet a PSP that believe send the entire credit card number, expiry and CVV was the right solution. I've talked to exactly one PSP that supported accepting credit cards in an iframe, and that was only available to existing customers, because they where discontinuing that service. In most of northern Europe at least, customer have been use to credit card payments redirecting them to third party sites since at least 1999. It has zero effect on conversion.
- manigandham 10y ago> That has to be a local issue, because that is flat out wrong. You can't declare it a possible local issue and then say it's wrong. And it's definitely been measured (in my own testing at various companies and by many many others) that it hurts conversions to break the flow into separate redirect.
- technion 10y agoYou know it. I know it. Most of HN knows it. We are, in general, not the customer. On sites I've been involved with, in 2016, I still have to fight tooth and nail to get SSL on the payment page at all, let alone redirect users somewhere else.
- Silhouette 10y agoOn sites I've been involved with, in 2016, I still have to fight tooth and nail to get SSL on the payment page at all I'm reasonably sure that every payment service I've ever used requires payment pages to be served over HTTPS, not just HTTP, even those that have minimal other requirements and take on most of the security burden themselves with some sort of hosted arrangement. Are there really significant numbers of merchants who aren't doing that?
- technion 10y agoAs a low tech experiment, I just grabbed the list that started this thread and tried a few random sites. I only made it to the third one before I found an http:// http:// checkout page. I tried to change the address to https:// https:// and found it complaining about a cert mismatch. I also viewed source and confirmed the form submits to an http:// http:// address. So.... yes.
- Silhouette 10y agoThat is genuinely disturbing! Do some payment services not do at least a basic check of integrations before allowing them to go live? I haven't worked on a site starting out with online payments very recently, but the last time I did, there was a short series of entries in the server logs that did look like someone from the payment service had taken at least a very quick look at the relevant pages.
- enobrev 10y agoWe shouldn't be asking this of clients any more. Build the site with SSL on all pages and either require the client buys a cert or implement Let's Encrypt. But at this stage, it makes no sense to make it optional, even for non-commerce sites.
- gingerlime 10y ago> leave it to Stripe, BrainTree, Paypal, someone trusted, with the resources to handle it. Wouldn't stripe and braintree still effectively let you handle CC on your own site? i.e. If someone can inject JS code there, they can in high likelihood grab CC details even if you're using stripe or braintree. Am I missing something?
- microcolonel 10y agoIt depends on how you integrate it, but yes, you're largely right. If they have your JavaScript they may have your cards.
- 3pt14159 10y agoThe difference is if you make the user click a link to Stripe's site then unless the evil JS replaces the URL with a different domain they can no longer interact with the user. And swapping out links is something that will get noticed far more easily than passively harvesting CC details.
- the_mitsuhiko 10y agoStripe does not use an iframe/redirect for protection.
- zrail 10y agoStripe Checkout is loaded in an iframe and stripe.js uses an iframe for data transmission.
- the_mitsuhiko 10y agoI know, but the credit card information for stripe.js lives in an unprotected DOM.
- collinmanderson 10y agoRight. It's sort of a loop hole where they technically use an iframe for PCI compliance, but they don't actually get any security benefit from it.
- MarkMc 10y ago> You should NEVER have the user enter credit card information on your site My app client sends the card info to Stripe, then forwards the Stripe token to my server to charge the card each month. So far this is a standard security model. The problem is that if PayPal come along to offer me a cheaper commission on processing subscription payments, I cannot simply switch my sever to use PayPal for all my existing customers. So I'm tempted to encrypt the credit card info and store it in my database in case I want to switch in future.
- mrweasel 10y agoI don't know about PayPal, but even if you just have the token for recurring payments/subscriptions you can still switch PSPs. Most PSPs are able to exchange tokens and information, enabling you to switch between them (at a price of cause).
- teh_klev 10y ago> "So I'm tempted to encrypt the credit card info and store it in my database in case I want to switch in future." Seriously....just don't. The world of pain you'll be in if you mishandle this data and the symmetric encryption key will probably see you or your clients made bankrupt. Please read up on PCI-DSS before even considering this: https://www.pcisecuritystandards.org/document_library https://www.pcisecuritystandards.org/document_library