Suspicious Payment Activity: Why Google Ads Suspends or Pauses an Account Over Billing

Outline of a payment card with a lilac pause badge, inside a thin halo ring on a dark navy ground
Google runs two separate enforcements under the suspicious payment activity policy: an in-account pause you clear by answering questions, and a suspension that requires a formal appeal behind a payment verification gate. Here is how to tell which one you have, what Google actually publishes about each, and what an ownership-evidence appeal has to contain.

If your Google Ads account has stopped serving and the notice mentions payments, the first thing worth establishing is whether you have actually been suspended. Google runs two separate enforcements under the same policy name, and they are resolved in completely different ways. One is cleared inside the account by answering a short form. The other puts the account into read-only mode and requires a formal appeal, with a verification step that can sit in front of the appeal before a reviewer ever reads it.

In our casework we see appeals filed for a problem that only needed the in-account form, and advertisers waiting on an appeal decision for an account that was never suspended. The distinction matters because the two enforcements are resolved in different places, by different steps, and time spent in the wrong one does not count towards the right one.

Policy text and timings quoted here were checked against Google’s published pages on 7 September 2026. Google updates these pages without notice, so verify anything you are about to rely on against the page itself.

Read the notice before you do anything

The exact wording matters, because it tells you which enforcement you have and what Google is asking for. Advertisers report the suspension notice appearing as “Your account is suspended—To complete your appeal for Suspicious payments, verify your payment info” — the string that titles a thread on the Google Ads Community forum. Others describe a pause notification with an Answer questions button rather than an appeal link.

Note the inconsistency in Google’s own naming. The in-account string says “Suspicious payments”. Google’s policy page is titled Billing and payment suspensions: Suspicious payment activity. The email Google sends when it wants your payment method verified carries the subject “Verify your payment method”, per its guidance on verifying your payment information. These are the same policy expressed in different words. If you search for the phrase on your screen and find nothing, the likeliest explanation is that you are searching one of Google’s other labels for it, not that you are looking at a rare or bespoke enforcement.

Before you click anything, do three things. Copy the notice text out word for word. Record the date it appeared. Then read what the notification actually offers you, because that is the documented signal: an Answer questions button is the in-account pause flow that Google describes on its Ads paused for suspicious payment activity page, while an appeal link, or a prompt to verify your payment info in order to complete an appeal, is the suspension path. Which of those two you are in decides everything that follows.

Paused is not suspended

Google documents the paused state separately from the suspension, on its own page. The difference is not cosmetic.

  Ads paused for suspicious payment activity Account suspended for suspicious payment activity
Account state Ads stop serving; Google describes the fix as happening inside the account rather than through an appeal Google states suspended accounts are in read-only mode “with a few exceptions” — you can still make a payment, add a payment method, download tax documents, appeal, and complete advertiser verification
What Google asks for Select Answer questions in the in-account notification and complete information about your payment history A formal appeal, often preceded by payment method verification
Possible additional steps Confirm your payment method, make a payment, or confirm the payment instrument with a code. Google states not all of these apply to every account Verification by code, payment or uploaded documents, then appeal review
Is an appeal required? No Yes
Where it is resolved Inside Google Ads Verification runs through Google Payments; the appeal runs through Google Ads

Google publishes its own figures for the paused flow. On that page it states that if you are asked to confirm your payment method you will get an email within 10 minutes of submitting your questions; that if no email arrives in that window your questions are being reviewed and you will get a decision about the pause within 5 business days; that you should get the confirmation code right away but that it can take up to 7 days in some cases; that the temporary charge appears in your transaction history within 5 minutes; that you will get that money back within 14 days; and that after you submit the code you will get a decision within 2 business days. Those are Google’s published timings for the paused flow, not a turnaround anyone else can offer you, and they do not apply to the suspension path.

What Google actually treats as suspicious

The policy page gives two concrete examples of prohibited conduct: “Using stolen credit card numbers to pay for Google Ads” and “Using someone else’s identity to apply for monthly invoicing terms on Google Ads”. Those are the hard cases, and almost nobody reading this article is in one of them.

What catches legitimate businesses is the softer signal list. Google names, in the same document, suddenly using several new credit cards, having payments declined, chargebacks, and unclear credit card ownership or billing details. None of those is fraud. All of them are normal symptoms of a company that changed banks, hit a card limit mid-quarter, replaced an expired card, or moved billing from a director to a new company account.

Google gives two stated rationales for enforcing this. The first is protecting advertisers and their customers from scams and unauthorised charges. The second is that suspicious payment signals frequently sit alongside other violations, such as creating fake accounts or running misleading ads. We cannot see how Google routes or reads any individual case, and nothing on that page describes its review workflow. But that second stated rationale is why we treat a payments appeal as an ownership-evidence exercise rather than an accounting query: the published concern is about who is behind the payment, so that is the question the submission has to answer.

Ownership is the whole policy

Google’s own best-practice guidance under this policy is to use a valid payment method that you own or have permission to use. That phrase is doing all the work. For a UK limited company it resolves into four common situations. What follows is the documentary chain we assemble for each — it is not a list Google publishes as its requirements. Google’s published UK document requirements are narrower, and are set out further down.

  • A company card in the company’s registered name. The simplest case. The bank statement header, the certificate of incorporation and the Google payments profile should all carry the same legal name. Keep a statement showing the Google charges alongside the card.
  • A director’s personal card. This can still be a payment method the business owns or has permission to use, in Google’s own formulation, but the permission has to be evidenced rather than assumed — and evidenced by something that already existed. The director’s own photo ID, a contemporaneous board minute or a written authorisation that pre-dates the enforcement and records that the director pays company advertising costs, and the expense reimbursement trail that corroborates it. Paperwork created after the fact to describe an arrangement that was never made is not evidence, and we will not prepare it.
  • A parent company card. The registered names will not match, and an unexplained name mismatch between the payer and the profile is exactly the ambiguity the policy’s “unclear credit card ownership or billing details” signal describes. So we evidence the group structure: incorporation documents for both entities and something showing the relationship between them.
  • An agency paying on a client’s behalf. Common and legitimate, but it needs a signed client agreement or written authorisation naming the agency as the payer for that specific account.

The 30-day verification gate in front of the appeal

This is the part that produces the most confusion. Google’s Billing and payment suspensions page states that before processing an appeal for billing and payment suspensions, you may be asked to verify your payment method within 30 days, and that after successful verification your appeal will be sent for review. Verification is not the appeal. It is a gate in front of it.

Those two processes also run on different rails. Verification updates arrive from Google Payments at payments-noreply@google.com, while correspondence about the suspension appeal itself comes through Google Ads. That is why your account status and your inbox can appear to contradict each other: a completed verification email says one thing while the Ads-side status still shows an unreviewed appeal. Neither is wrong. The appeal simply has not started yet.

Two practical consequences. Treat the 30 days as a real deadline and calendar it. And do not read a verification confirmation as a reinstatement — after verification succeeds, the appeal goes for review, and the decision comes separately.

The micro-charge code, end to end

The code route works like this. Google places a temporary charge on the card, which its Fix issues with payment method verification codes page describes as “a temporary hold or charge of $1.95 USD called ‘GOOGLE.’ This amount varies by currency.” A UK business card will therefore show the local-currency equivalent against a GOOGLE descriptor, not a dollar figure. Next to that hold, Google states, there is a six digit verification code. You enter the six digits in the account to prove you control the instrument.

The refund wording differs by page and by what happens to the code, so it is worth reading both. On the verification codes page, Google states that if you do not use the code, the refund will be processed within 14 days and it may take up to two more weeks for the refund to appear in your account; where the code is used, that page says it may take up to 30 days for the refund to appear. On the separate paused-account page, describing the in-account pause flow, Google states the charge appears in your transaction history within 5 minutes and that you will get that money back within 14 days. If your figures do not seem to match, check which of the two pages, and which of the two flows, you are reading.

Google publishes a specific list of reasons the code fails on the verification codes page:

  • Wrong card. You entered the code for a card other than the one being verified.
  • Expired code. Google states that if it has been more than 14 days, the code is expired and you must try verification again.
  • Card deleted after the request. If you removed the card after requesting the code, the code is no longer valid. Re-add the card and request a fresh one.
  • Fewer than six digits. Submit documents instead if the option is offered, or use another payment method.

The same page’s troubleshooting steps also cover the mundane causes: browser problems, where it suggests clearing cache and cookies, trying a private window, disabling extensions and updating the browser; and bank-side blocks, where it directs you to confirm with the bank that nothing is preventing the authorisation.

A practitioner observation for UK business accounts, not something Google publishes: some corporate banking portals truncate merchant descriptors, so the six digits appear on the full statement or in the bank’s app detail view but not in the summary transaction list. Check the expanded transaction record before concluding the code never arrived.

Document verification as the alternative route

Where the code route is unavailable or has failed, Google may accept documents. Google’s document requirements page is country-specific and account-type-specific; for the United Kingdom it names, for organisations, a certificate of incorporation, a VAT registration certificate, or a certificate of registration of charity. For an authorised representative’s government-issued photo ID it names a passport, an identification card, a driving licence, or a permanent residence card. For an individual it names a driving licence, a passport, or a permanent residence card — a shorter list, without the identification card. Check the page for your own country before assembling anything.

On that UK page, the quality rules attach to the government-issued photo ID: the ID must be valid and not expired, the image in colour rather than black and white, clear and well lit, and it must not be a photocopy nor a screenshot. Google’s separate guidance on verifying your payment information sets out the image standards for documents you submit — in colour rather than black and white, no blur, glare or dim light, and showing all four corners of the full document — and adds that you should use the same full name in all documents that you submit, and that verification can take up to 5 business days after you submit your documents. In our casework, image quality is a recurring reason an otherwise sound submission comes back.

Beyond Google’s published instruction to use the same full name across documents, this is how we work, offered as a practitioner observation rather than a published rule: we treat the organisation name on the payments profile and the name on the incorporation certificate as needing to be identical, not merely close. A payments profile reading “Smith Trading” against a certificate of incorporation reading “Smith Trading Limited” is the kind of gap we would correct on the profile first and submit afterwards, rather than submit and then explain.

The country problem nobody warns you about

This is the one that cannot be solved with better paperwork, and it disproportionately affects businesses that have relocated or restructured.

Google states plainly that you cannot change the country for an existing payments profile, because each payments profile can be associated with only one country due to tax regulations, and that you must create a new profile to use a different country.

Google also publishes country mismatch as a named verification failure. Its page on a payments mismatch with submitted documents gives the failure reason as the country listed for your payment profile being different from the address listed in your submitted document, and instructs you to re-submit a document with a country that matches your payments profile country, with an exception that for European Economic Area countries any ID is accepted if it is issued by any country that is part of the EEA. Where the profile country genuinely does not match your registration documents, that same page directs you to contact Google Ads support to ask to create a new payments profile with a different country. To be explicit about the boundary, because it matters in an enforcement context: that is a payments profile created with Google Ads support against the same, existing Google Ads account. It is not, and must never become, the creation of a new Google Ads account.

So if your company was incorporated overseas and has since redomiciled to the UK, or the profile was opened years ago by a contractor sitting in another country, documents alone will not resolve it — the profile country has to be corrected first. Documents issued by a third country will not clear a country mismatch either, because the problem is the country recorded on the profile, not the quality of the paperwork.

Four billing problems that look identical and are not

All four produce a stopped account and a billing-flavoured notice. They are different policies with different remedies.

Problem What triggers it What resolves it
Suspicious payment activity Stolen card use, identity misuse for invoicing, or the signal cluster: several new cards in quick succession, declines, chargebacks, unclear ownership Verification of payment method ownership, then an appeal explaining ownership and every decline or chargeback
Unpaid balance or declined payments Google states an account may be suspended where there are unpaid balances, or concerns about the ability to make future payments due to payment method issues or declined payments Settle the balance and fix the instrument. In the UK and EEA, a decline can be a Strong Customer Authentication failure rather than a lack of funds — Google’s page on resolving a declined card payment notes that your bank may not support it and that it is required to authenticate a card or payment in the European Union, so confirm with the bank
Chargeback Google states that instructing your bank to reverse a charge paid against a legitimate Google Ads balance may result in suspension Resolve the disputed amount directly, then appeal with the reversal explained
Promotional code abuse Google states that attempting to sell promotional codes, or using more than one on an account, may result in suspension A different appeal entirely; do not treat it as a payments ownership case

Two things worth knowing about chargebacks specifically. Google’s guidance on disputing a Google Ads charge asks you to identify an unrecognised charge through its troubleshooter before going to your bank — a chargeback filed against a charge that turns out to be your own account’s legitimate spend is a self-inflicted suspension. And if the bank finds in your favour while Google maintains the charge was legitimate, Google states the account will carry an overdue balance that must be paid before ads can run again. Winning the dispute at the bank does not clear the account.

What an appeal under this policy has to contain

Google’s own appeal guidance for this policy is unusually narrow. It asks you to “give details about who owns the payment method listed on your account or explain any declined payments or chargebacks”. Read that sentence closely before you write anything: it names two subjects, ownership and payment history, and nothing else.

This is an ownership-and-explanation exercise, not a persuasion exercise. Arguments about how much you have spent historically, how long you have advertised, or how damaging the suspension is to the business do not answer either question, so we leave them out. What answers them is a chain:

  1. Name the legal entity as registered, exactly as it appears on the payments profile.
  2. Name the payment instrument and state its relationship to that entity — company card, director’s card with existing authority, parent company card, agency card under a client agreement.
  3. Evidence that relationship with the corresponding document.
  4. Take every decline and every chargeback in date order and give the cause of each in one sentence: card expiry, SCA challenge not completed, limit reached, bank fraud hold, or a dispute and how it was resolved.
  5. State what has changed so the pattern does not recur — the settled instrument now on the account, and who has billing authority.

If you want a broader view of how appeals are read across policy types, our overview of Google Ads suspension policies and what they mean in practice covers the wider landscape, and our case study on reinstating a Google Ads account shows how the documentary chain was assembled in one matter — timings depend entirely on the account, and are not something anyone can commit to in advance.

How a payment suspension spreads

Payment suspensions rarely stay in one account. Google’s account suspensions overview states that accounts related to the suspended account may be suspended, and that any new accounts the advertiser tries to create may also be suspended. It does not say what makes accounts related, and we are not in a position to tell you. For anyone running a manager account, the practical point stands regardless: a single client account’s billing flag can have consequences for the accounts sitting alongside it, so plan on that basis.

There is one automatic remedy, and it is worth knowing before you file five separate appeals. Google states that if your account was suspended because other accounts verified using the same identity documents were suspended, your account will be automatically reinstated once those other accounts are successfully appealed. In that specific situation the correct sequence is to identify the originating account, appeal that one properly, and let the linked reinstatements follow — rather than filing parallel appeals that each restate an incomplete picture.

The worst possible next move

When ads stop and revenue stops with them, the instinct is to open a fresh account and keep trading. Do not. It converts a billing problem into a far more serious one.

Google’s Circumventing systems policy names, as a violation, attempting to use the Google Ads system again by creating new accounts to re-enter it after a previous suspension decision. It states that violations of that policy are considered egregious, and that accounts will be suspended upon detection and without prior warning. The suspensions overview reinforces the point, recommending that advertisers reinstate suspended accounts before attempting to create new ones.

The same policy names providing false or fraudulent information as part of advertiser verification. That matters here because verification is the gate in front of this appeal. Submitting a document that does not genuinely evidence the entity, or naming a payer who did not in fact authorise the payment, is providing false information to Google. It is dishonest, and it is not work we will take on for any business, at any price. It is also self-defeating: it replaces a billing question with a Circumventing Systems finding, a policy Google states it treats as egregious and enforces upon detection without prior warning.

An illustrative scenario

The following is an illustrative scenario written to show the order of work. It is not a client and not a case study.

A UK trading subsidiary is suspended for suspicious payment activity. Its Google Ads billing has, since inception, been paid on a corporate card issued to the parent company, which is registered under a different name. The payments profile carries the subsidiary’s name. Two card replacements after a bank migration produced three new instruments in six weeks and two declines. Every individual fact is innocuous; together they read exactly like the signal list Google publishes.

The order in which ownership is evidenced is what makes the appeal legible. First, the payments profile is corrected so the legal name and address match the subsidiary’s certificate of incorporation character for character. Second, verification is completed on the instrument actually in use, so that the payments side and the ads side are not describing different cards. Third, the ownership chain is set out in one paragraph: the card is issued to the named parent, the parent owns the subsidiary, and here are the incorporation documents for both. Fourth, the three-cards-in-six-weeks pattern is explained as a bank migration with dates, and each decline is attributed to a specific cause. Fifth, the appeal states that billing now sits on a single instrument with a named authorised person.

Nothing in that sequence argues that the enforcement was unfair. It removes every ambiguity the policy is designed to catch.

Where AdRestore fits

Most of the work in a payments suspension is not writing — it is establishing, document by document, that the entity, the profile and the instrument are the same story, and then explaining a payment history clearly enough that a reviewer does not have to guess. That is the work behind our Suspicious Payment Activity reinstatement service, and it sits alongside the rest of our Google Ads suspension and compliance services.

Written by Gianluca Catinella, Director of Ad Restore Ltd, who has worked on over 100 Google Ads suspension appeals.

If you are holding a payments notice and are not certain whether you have a pause or a suspension — or whether the country on your payments profile is going to block verification before you start — that is exactly the question a short call can settle. You can book a free consultation and we will tell you what you are dealing with and what the realistic route is, before you commit to anything.

Picture of Gianluca Catinella

Gianluca Catinella

Gianluca Catinella is the Director of Ad Restore Ltd. He has worked with businesses across a wide range of industries, managing high-spend Google Ads accounts and handling complex account suspensions — including some of the most challenging policy and reinstatement cases. His work covers Circumventing Systems Policy, Suspicious Payment Activity and Unacceptable Business Practices, along with advertiser verification, Merchant Center and Google Business Profile suspensions. He came to this work from the receiving end. Running Google Ads for his own first business, he had an account suspended and found almost no support available to explain what had actually been flagged or how to put it right. He spent the months that followed reading the policies properly — every suspension type, what reviewers look for, and what a successful appeal has to contain — and he now tracks Google’s policy changes as they ship. Automated enforcement has to cast a wide net to keep scammers and bad actors out, and legitimate businesses get caught in it. Gianluca’s job is the bridge from confusion to clarity: working out exactly which policy was triggered, fixing the underlying issue, and putting a clear, evidenced appeal in front of Google so the business can get back to trading.
Share this post

More from the blog

Leave a Review

Schedule a Consultation

Preferred contact method