Opinion

A shipped site can still fail to take a payment

17 August 2026, 3 minute read

Picture a checkout button three clicks deep, behind a menu labeled Services, under a tab few visitors open. A site like that is live, and most visitors will never find a way to pay on it.

Ask one question of everything you've shipped: can a stranger pay for this today? Ask it about a visitor who found the page cold, decided quickly and reached for a card. Leave out the warm lead who already emailed you.

Common small failures

Most launched sites fail that question in small ways. A payment link still carries a placeholder token from testing, so it loads and looks finished but takes no money. A pricing page lists tiers with no way to select one. A form collects an email and promises a follow-up that never got automated.

None of that shows up in a deploy log, where every check passes. Usually one path is broken, and it stays broken because the owner already knows where the checkout is and never has to look for it.

Why does nobody catch it?

The person who built the site tests that each page loads. Few owners test that a stranger can complete a purchase, because that means spending money on their own business, and that feels absurd. So nobody runs the check, and the broken path can stay broken for months.

How do I check my own site?

Open your own site in a private window. Start from wherever a stranger would land, which is often a different page from the one you're proud of. Try to buy from yourself. Note where you stall.

Write down every place you had to already know something to keep going. Those are the things to fix. Usually a clear path from the homepage to the payment fixes them without a redesign.

Related reading

Part of the guide AI automation for small businesses.