If you’re trying to pay in a Google checkout flow on Windows and you’re seeing card verification failures, repeated prompts to “verify,” or a charge that stays “pending,” it’s usually one of a few fixable causes: saved payment data, browser/session issues, bank verification, or a temporary hold.
Let’s get you to a clean yes/no answer fast.
1. Confirm what you’re seeing: “pending hold” vs “failed payment”
Before changing anything, check the wording. A pending charge is often an authorization hold (common for online purchases) and may drop off automatically. A failed payment usually means verification didn’t pass.
- Pending/authorization: you might see it in your bank app, but the order may still be incomplete.
- Failed/declined: Google shows an error immediately, or the checkout returns to the payment step.
If the merchant didn’t confirm the order, treat it as incomplete even if you see a pending hold.
2. Try a clean checkout session (new window + sign in once)
Payment flows are sensitive to old tabs, cached redirects, and half-signed-in states.
- Close all checkout tabs.
- Open a new browser window (not just a new tab).
- Sign in to your Google account first, then start checkout again.
If you use multiple Google accounts, double-check you’re signed into the one that actually has the card/profile you expect.
3. Clear cookies for the payment domains (targeted, not “wipe everything”)
When card verification loops or the payment step resets, corrupted cookies are a common cause—especially after password changes or switching accounts.
- In Chrome/Edge, open Settings and search for cookies.
- Use “See all site data and permissions” and remove data for these common domains:
- pay.google.com, payments.google.com, and the merchant’s checkout domain.
Then restart the browser and try again.
4. Temporarily disable extensions that can alter checkout (ad blockers, privacy tools, script blockers)
Anything that blocks scripts, iframes, popups, or third-party cookies can break verification steps (including 3‑D Secure challenges from your bank).
- Disable ad blockers/privacy extensions for the checkout attempt.
- Also pause VPN/proxy tools just for the transaction.
- If you can’t disable them, try an “InPrivate/Incognito” window with extensions off.
If the payment works with extensions off, re-enable them one by one to find the culprit.
5. Update your payment method details (and remove duplicates)
Verification failures often happen when a saved card has an old billing address, expired ZIP/postcode format, or duplicates of the same card.
- Go to Google Payments and review the card details and billing address.
- Remove duplicate entries for the same card.
- Re-add the card if edits don’t “stick.”
Also check if your bank recently issued a replacement card (new expiry/CVV) even if the number looks similar.
6. Treat repeated “verification failed” as bank-side (3‑D Secure, fraud flags, or limits)
If your bank is supposed to show a verification prompt (SMS/app approval) and it never arrives, or it arrives but still fails, it’s often the bank declining the verification attempt.
- Call or chat with the bank and ask if they see 3‑D Secure (or “online card verification”) failures.
- Ask if the merchant category is blocked, or if there’s a temporary fraud hold.
- Check daily/online limits and whether international/online purchases are enabled.
If there are multiple pending holds, avoid retrying rapidly—wait 30–60 minutes so you don’t stack authorizations.
Final thoughts
Most Windows payment failures come down to session/cookie corruption, extensions interfering with verification, or a bank-side 3‑D Secure decision.
If you want the fastest path, try a clean session with extensions off first—then update the saved payment details and involve your bank only if verification still fails.