After you input credit card #, EXP, CVC, ZIP and you miss putting the card owner name, there's a message saying "Enter the owner name as it appears on the card." There's also a message saying "Sorry, for security reasons your card cannot be processed. Please refresh this page and try again. If the problem persists please check that Javascript is enabled your browser.
If you refresh the page F5 or CTRL F5, the same messages persist and you can not continue. You have to go back to the cart and come back before you can re-enter CC info. My default theme is Bootstrap Business 7.x-1.1 and thought maybe it's something with that theme, but also tried Garland 7.69 and the same issue persists. Clearing Drupal cache does nothing either.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | no-name-on-card-error-garland-7-69.jpg | 377.39 KB | RaySilver |
| no-name-on-card-error-bootstrap-biz-7x-1-1.jpg | 36.88 KB | RaySilver |
Comments
Comment #2
RaySilver commentedComment #3
RaySilver commentedComment #4
Rafal LukawieckiI have this issue when other checkout fields are missing or vause a validation error. For example, if the required street address is missing, or VAT number fails validation (using uc_vat_number) the form validation fails with its own error message, such as 'State/Province field is required.'. Unfortunately, it also triggers the uc_stripe "Sorry, for security reasons your card cannot be processed. Please refresh this page and try again. If the problem persists please check that Javascript is enabled your browser." message and there is no way to fix the error on the page as the order review button is now disabled.
Further, this causes issues even if using a different payment method because the Stripe form error affects the Review order button even if Stripe is not active, for example if the user has selected PayPal or another payment method provided by us.
Comment #5
Rafal Lukawiecki@RaySilver, please have a look at the fix for #3168978: JS - Stripe makes the checkout form unusable when there's a form error, which has been committed to the current -dev branch, as it may solve this issue. If so, perhaps this could be closed?