How the payment page check works
- We open your home page the way a visitor does and follow its links to your pricing or payment page.
- On each check, we open that page again and look for a payment form, a card field, a Pay button or a WhatsApp order button.
- If we find one, the check passes and stops there. We never click Pay.
- If the page doesn’t open, or the payment form is gone, the check fails and you get an alert.
What “working” and “not working” look like
A passing check shows in your dashboard as “Payment page: Opened and showed what it should. Working”.
A failing check sends you an alert (by email, or on paid plans also to Slack, Telegram or a webhook). The email has a subject such as “[Heedza] Checkout broken on your-app.lovable.app”. It says what was missing, has a picture of the page attached, and includes a fix to paste into your AI tool. The fix tells the tool not to enter a card or make a charge while it fixes the page. See what an alert looks like.
How often we check
| Plan | Price per month | Sites | Online check | Page checks |
|---|---|---|---|---|
| Free | $0 | 1 | Every 5 minutes | Once a day |
| Solo | $9 | 2 | Every minute | Every hour |
| Starter | $19 | 5 | Every minute | Every hour |
| Pro | $39 | 12 | Every 30 seconds | Every 30 minutes |
| Business | $99 | 30 | Every 30 seconds | Every 15 minutes |
See pricing for details.
What it doesn’t do
- It never pays. So it can’t tell you whether a real payment goes through, or whether Stripe tells your app about the payment afterwards (Stripe calls this a webhook).
- It only finds payment pages it can reach by following links. A Stripe Checkout page that is made only after someone clicks a button may not be reachable, so the check may stop at your pricing page instead.
- It doesn’t log in, so a payment page that is only shown to logged-in users can’t be checked.