I'm not sure a donor can even get to this point without javascript enabled, so maybe we can safely remove that part of the message?

They can access our payment form from the sidebar and that does not require javascript. Also the message about the card is intentionally vague for a bunch of reasons. I think this should all load in an iframe on the payment form. If this is supposed to be a whole separate page we should add a link to the problems donating page.

Donatewiki requires javascript

Payments-wiki requires javascript too - there's really no way to get to the credit card entry without it. That error is probably just triggered because the random card number doesn't pass the Luhn check. If you want a test card number that doesn't trigger the check error, you can always use 4111 1111 1111 1111.

It looks like we can change this text via the language packs in the key gc.general.paymentProductFields.validationErrors.allowedInContext.label

Would we want to just delete the reference to script blockers?

I guess people who allow JS per domain could have allowed it on donatewiki and paymentswiki, but not on Ingenico's site.

Would we want to just delete the reference to script blockers?

We have in the past seen donors for whom the Ingenico domain was what was blocked by their extension. Can we preview the new error text here before we publish it?

I think this task should be higher than low priority, even if the absolute numbers of people receiving this message are relatively low. These tickets take a lot of DS bandwidth, relative to other tickets, and the clearer we can be with the message the more likely we are to rescue these donations.

If no one gets to this message w/out JS enabled, I would +1 the suggestion to remove that wording at least.

Maybe it would be best to just keep the error message simple and focused for user actions?

Something along the lines of "There was an error processing your card, please close and reopen your browser and try again"

This message is triggered client side though, it's not really an issue with processing the card, so I don't think that would be appropriate.

I noticed for GB and US (which load as an iframe) the message is different and already excludes the javascript part:

It seems the best solution would be to have 2 separate error messages: failed Luhn check, and no javascript available (probably contained in a <noscript> tag). However that is probably something that would need to be done by Ingenico.

While testing T267152 I noticed this unclear error message DOES appear for the US (although not for GB)