GMC Suspicious Payment Activity Suspension: How to Fix It

Updated: June 2026 • 10 min read

A "suspicious payment activity" suspension is one of the more opaque violations Google Merchant Center issues. The notification is vague, the checklist Google provides is short, and merchants often fix the obvious issues only to get denied again. This guide covers every signal Google looks for, how the triggers differ for new versus established merchants, the six most common root causes, and a proven appeal structure.

If you want to run a full automated check of your store first, use the GMCSuspension.com free audit tool. It scans 43 policy requirements, including payment-related ones, in under two minutes.

What Triggers a Suspicious Payment Activity Flag

Google's systems and manual reviewers assess your payment setup at several points: when you first submit your account, when you make significant changes to your product feed, and during periodic re-reviews. A suspicious payment activity flag is raised when the reviewer or automated system cannot confirm that your store accepts real payments in a trustworthy and consistent way.

The core question Google is asking is: "Can a real customer complete a purchase here, and will that experience match what the Shopping ad promises?" If the answer is no for any reason, the account is flagged.

Specific triggers include:

• A checkout flow that does not reach an actual payment screen
• No visible payment processor or recognized payment method logos on the checkout page
• Currency shown on the checkout page that does not match the feed currency
• Missing SSL certificate or a certificate that throws a browser warning
• Checkout that requires an account login with no guest option
• A payment page that loads a generic theme placeholder instead of a real payment form
• Test mode or sandbox mode still active on your payment processor
• Checkout that errors out or redirects to a broken page

Google does not always disclose which specific trigger caused the suspension. Your job is to audit every single one of the above points before submitting an appeal.

New Merchant vs Established Merchant: Different Triggers

How Google treats a suspicious payment activity flag depends heavily on your account's history.

New merchants are reviewed against a stricter baseline. Google assumes nothing about your intent. A checkout that is 90% complete but missing the final payment confirmation screen will trigger a suspension in days, sometimes hours. Google's automated crawlers test new merchant checkouts almost immediately after the account is verified. Common traps for new merchants:

• Shopify store still in "coming soon" or password-protected mode when the account is submitted
• Payment processor account created but not fully activated (Stripe requires identity verification; if that step is pending, live payments will not process)
• Theme installed but payment badges not yet added to the footer
• Test products with placeholder prices (like $0.01 or $999,999) still in the feed

Established merchants with a clean review history get slightly more runway. Google may send a warning before suspending, or the flag may only affect specific products rather than the entire account. However, a pattern of payment-related issues can still escalate to a full account suspension even for long-standing accounts. Triggers specific to established merchants include:

• A payment processor change that was not reflected in the checkout experience (e.g., switching from PayPal to Stripe but leaving old PayPal buttons that no longer work)
• A currency change mid-campaign that created a mismatch between the live feed and the checkout
• An app or plugin update that broke the checkout flow
• Adding a new market or language with a checkout that was not fully set up for that region

The fix process is the same either way. Identify every broken or missing payment signal, fix all of them, then appeal with documented evidence.

The 6 Most Common Payment-Related Suspension Causes

1. No Real Checkout Available

This is the most common cause, especially for new Shopify and WooCommerce merchants. "No real checkout" means Google's reviewer reached a product page, added an item to the cart, and then hit a dead end: a password protection screen, a "coming soon" page, a cart that does not advance, or a checkout page that throws a 404 or 500 error.

It also includes stores where the checkout exists but requires mandatory account creation with no guest checkout option. Google requires that a customer can complete a purchase without creating an account.

2. Payment Processor Not Visible

Google's reviewers look for recognizable payment processor branding at checkout. If your checkout page shows a generic "pay now" button with no logo, no payment method icons, and no recognizable processor name, that reads as suspicious. It does not mean the payment does not work behind the scenes. It means the trust signals that would reassure a real shopper are absent, which is a policy violation in itself.

Accepted processors include Stripe, PayPal, Square, Mollie, Adyen, Klarna, Braintree, Shopify Payments, and similar established providers. The processor's name or logo must appear visibly on the payment step.

3. Inconsistent Currency

Your Google Shopping feed specifies a currency for every price. The prices shown on your product pages and at checkout must use the same currency. A mismatch, such as a feed listing prices in EUR while the checkout displays USD, is a direct policy violation. It also happens when multi-currency plugins dynamically convert prices but the feed is not updated to match, creating a visible discrepancy when Google's reviewer checks the checkout.

This is a harder-to-catch issue because it often only appears for certain visitor geolocations or certain browser languages. Test your checkout from the same context Google's reviewers use: a US or European IP, English language, no logged-in session.

4. Missing Payment Security Information

Google expects merchants to demonstrate that the payment experience is secure. Concretely, that means:

• An active SSL certificate with no browser certificate warning (padlock in the address bar)
• Accepted payment method logos (Visa, Mastercard, PayPal, etc.) displayed on the checkout page and in the footer
• A short security statement near the payment form, such as "Payments are encrypted and processed securely by [Processor Name]"

A store with HTTPS but no visible payment logos or security statement is still vulnerable to this flag. The logos and statement are trust signals for shoppers and signals for Google's reviewers that the merchant has actively set up a secure payment environment.

5. Untested Checkout Flow

Many merchants set up their store, submit to Google, and never actually complete a test purchase. This leads to uncaught problems: a promo code field that throws an error and blocks checkout progression, a shipping calculation that fails for certain zip codes, a payment confirmation page that returns a blank screen, or a "thank you" page that 404s.

Google's reviewers test the checkout as a real customer would. Any step that fails or produces an error is a potential suspension trigger. Before appealing, complete at least three full test purchases: one standard, one with a promo or coupon code if you offer them, and one from a mobile device.

6. Accepted Payment Methods Not Matching the Feed

If your Google Shopping feed includes attributes for installment payments, buy-now-pay-later options (Klarna, Afterpay, etc.), or specific financing arrangements, those methods must actually be available and functional at checkout. If Google's reviewer sees "Pay in 4 installments" on the product page but that option does not appear at checkout, the discrepancy reads as misleading and triggers a payment activity flag.

The reverse also triggers issues: if your checkout offers Klarna but your feed does not reflect installment pricing, Google may flag the inconsistency. The feed and the live checkout must tell the same story.

How to Fix Each Cause Before Appealing

Do not appeal until you have addressed every applicable issue from the list above. A premature appeal with outstanding issues wastes your attempt and extends the timeline. Here is the fix sequence:

1. Unlock your store completely. Remove any password protection, coming-soon mode, or maintenance-mode plugin. Verify that every product page, cart, and checkout page is publicly accessible without a login.
2. Activate your payment processor fully. Log into your processor dashboard (Stripe, PayPal, etc.) and confirm your account is live, not in test/sandbox mode. Complete any pending identity verification steps. Place a real test transaction, even for a small amount, to confirm payments process end to end.
3. Add payment logos and a security statement. Add Visa, Mastercard, and your processor's logo to your footer and to the checkout page. Add a one-line security note near the payment form. Most Shopify themes have a built-in payment badges section in the theme editor under the footer settings.
4. Align currency across feed and site. Open your Google Merchant Center feed and note the currency. Open your site in an incognito window and go through checkout. Confirm the displayed currency matches at every step. If you use a multi-currency plugin, configure it so the default currency shown to Google matches the feed.
5. Enable guest checkout. In Shopify, go to Settings → Checkout and set customer accounts to "Optional" or "Disabled." In WooCommerce, go to WooCommerce → Settings → Accounts and enable the guest checkout option.
6. Test three full purchases. Complete the entire checkout from product page to order confirmation page, once on desktop incognito, once on mobile, and once as a logged-out guest. Screenshot every screen. Save these screenshots for your appeal.
7. Reconcile feed payment attributes with checkout reality. If your feed has installment or BNPL attributes, verify those options work at checkout. If they do not work yet, remove the attributes from the feed before appealing.

After completing all fixes, run the GMCSuspension.com free scan again to confirm no remaining policy issues before submitting your appeal.

The Appeal Statement for Payment Activity Suspensions

The appeal form in Google Merchant Center asks you to explain what changes you made. Be specific and factual. Do not write a general statement about your business. Write a direct account of what was broken, what you changed, and how you verified the fix.

Here is a structure that works:

We reviewed our account following the suspicious payment activity suspension and identified and resolved the following issues:

1. Payment processor visibility: We added our Stripe payment logo and accepted card logos (Visa, Mastercard, Amex) to the checkout page and footer. A security statement ("Payments processed securely by Stripe") is now displayed near the payment form.

2. Checkout flow: We completed three full test purchases on [date] from incognito desktop and mobile browsers. All purchases proceeded from product page to order confirmation without errors. Screenshots are attached.

3. Currency consistency: We confirmed that the currency in our product feed (EUR) matches the currency displayed at all checkout steps on the live site.

4. Guest checkout: We enabled guest checkout so customers can complete a purchase without creating an account.

All identified issues have been resolved. We ask that you review our account for reinstatement. Please let us know if additional information is needed.

Attach your checkout screenshots directly to the appeal if the form allows it. If it does not allow attachments, host the screenshots on a public URL (Google Drive with link sharing on, Dropbox, or your own domain) and include the link in the text.

Keep the tone factual. Do not apologize excessively or make claims about your intent. Google's reviewers want to see that the specific policy issues have been resolved, not reassurances about your character as a merchant.

FAQ