Payment failed screen examples

When a payment fails, people need to know nothing was charged and how to finish the order. These checkout examples show a declined card: an alert in the payment section with the reason, the card field marked with an icon and message, other ways to pay still visible and the Pay button ready to retry, on web and mobile in eight styles. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

See it in a flow

Buy a product

Card declined at checkout design tips

Say that nothing was charged; it is the first thing people worry about.
Give the reason when you can (insufficient funds, expired card) and the next step (another card, another method).
Keep the rest of the form filled in so only the payment needs to change.
Place the error next to the payment fields, not only in a toast that disappears.

Questions

What should a card declined message say?

That the payment didn’t go through, that nothing was charged, the reason if the bank gave one, and what to do next, such as using another card.

Should the checkout form be cleared after a decline?

No. Keep contact, shipping and delivery choices so people only change the payment method.

Where should payment errors appear?

Inline in the payment section, close to the card fields, and announced to screen readers with role=alert.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.