3 ms·
You can make an exception for payments (where you rely on the payment processor anyway, so the reliability argument goes away - if the processor is down, the pa
by Nextgrid 5y ago
You can make an exception for payments (where you rely on the payment processor anyway, so the reliability argument goes away - if the processor is down, the payment will fail even if you self-host the payment script). Of course, embed the payment script only on the actual payment page, even if your processor tells you otherwise and quotes some fraud-related bullshit.
- samwillis 5y ago> even if your processor tells you otherwise and quotes some fraud-related bullshit. You may be right 99.9% of the time. But if your site starts being used by someone automatically testing stolen credit card to see if they work you will be thankful for the automated script detection this gives. Every chargeback cost the vendor $20, now imagine 1k of those in a sort period of time, not pretty. So far I have fortunately not been a victim of this but have read about people who have and it gives me enough fear to stick that script on all pages.
- Nextgrid 5y agoCan't you just enforce 3D-Secure and be done with it?
- samwillis 5y agoI may well be out of date (last looked at it about 18 months ago) but I don’t think all card issuers have implemented 3D secure yet. Although I think there may have been a deadline for them to. Also friction in the checkout process is bad and can contribute to dropouts. You can decide to always enforce 3d secure or to have it only run when banks require/suggest it. Personally I set a cart total threshold above which it’s required and set it only to be applied when banks require it for lower value orders.