#saimonp
1 messages · Page 1 of 1 (latest)
Our recommendation is to include Stripe.js on all pages across your site, not just the checkout/payment page: https://github.com/stripe/stripe-js?tab=readme-ov-file#ensuring-stripejs-is-available-everywhere
So it does I see
Recently one of my long time customer is blocked after I moved my site. Since I removed Stripe.js from other pages maybe it's seen as the user accessing checkout instantly hence more risk score?
Would be hard to say without an example payment that was 'blocked'. It could be that the bank declined the payment, as opposed to a Stripe/Radar block
It was a 80+ in Radar score so it's Radar's blocking correct?
If you share a pi_xxx ID I can confirm
like this one
Yep, looks like Radar blocked it
Granted this was also due to a bug in my site causing billing_name not being sent to Stripe, his name and email should've been flagged as similar otherwise (For some reason not having last name field caused this) So I can't blame Radar fully on this one.
But it's just odd how many recent customers have higher base score.
So I will try Stripe.js on all page thank you