Skip to content

UX guides / Cart and checkout / Payment failures return specific, field-level feedback

Payment failures return specific, field-level feedback

Usually highHow serious this usually is when it goes wrong. Not a score.

The guideline

When a card submission is rejected, show the reason within a couple of seconds, positioned next to the specific field it concerns — expired date, invalid CVV, card number not recognised — rather than a single generic message like "Payment failed". Preserve every correctly entered field; the user should only need to re-enter the one that was flagged. Associate the message with its field via aria-describedby so assistive technology announces it.

Common failures

  • The checkout does not provide immediate, field-specific feedback when a credit card submission fails, leaving users uncertain whether the issue stems from an expired date, incorrect CVV, invalid number, or payment gateway timeout.

Where it applies

Pages

  • Checkout

Industries

  • Ecommerce
  • Hospitality

Disciplines

  • Conversion
  • Trust

Devices

  • Desktop web
  • Mobile app
  • Mobile web

Why it matters, how to fix it, and the research behind it

Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.