This is Payment failures return specific, field-level… as plain markdown, the version AI agents read. Same facts as the page, without the layout.
--- title: Payment failures return specific, field-level… · Rubric description: 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… url: https://rubric.design/ux/checkout.payment-error-immediate-feedback format: agent view of this page updated: 2026-11-16 --- [UX guides](https://rubric.design/ux/) / [Cart and checkout](https://rubric.design/ux/topic/checkout) / Payment failures return specific, field-level feedback # Payment failures return specific, field-level feedback Usually high · How 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. [Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents) ## Related guides - [Optional add-ons offered and removable at the cart](https://rubric.design/ux/cart.optional-add-ons) · Usually critical · Offer optional extras — fast-track entry, parking, insurance, meal or seat upgrades — on the cart. - [Shipping cost resolved at the cart](https://rubric.design/ux/cart.shipping-cost-visible) · Usually critical · Show the real shipping cost on the cart, before the user enters payment details. - [Cart total includes taxes and mandatory fees](https://rubric.design/ux/cart.total-includes-taxes-and-fees) · Usually critical · Make the total on the cart the amount that will actually be charged. - [Guest checkout available without account creation](https://rubric.design/ux/checkout.guest-option) · Usually critical · Offer guest checkout as an equally weighted option at the first step of checkout, presented alongside sign-in rather than beneath it, and let it reach payment… - [Promotion terms are stated next to the offer, not behind a link](https://rubric.design/ux/checkout.promotion-terms-visible-inline) · Usually critical · State every material condition of a promotional offer — minimum spend, product exclusions, geographic limits, expiry — inline beside the offer, in the same…