Google Ads Financial Services Verification Before an Agency Handover

Before a fintech advertising handover, put four things in writing: the business being advertised, the product and target market, the verification status of the relevant account, and who will control access and billing afterward.

An agency proposal is easier to evaluate when those facts are visible. A missing verification record needs a different response from a billing problem or an unclear account owner. Treating every issue as a need for another ad account can leave the original problem unresolved.

This checklist is for marketing and operations teams preparing a Google Ads handover. It includes a UK example and a US product-policy example; neither should be applied automatically to another market. It is operational guidance, not legal or financial advice. Your compliance team should confirm the requirements for the actual product and locations.

Start with the exact business and product

Write a short description that a reviewer outside your company can understand. Include:

Avoid using “fintech” as the product description. A payments tool, consumer loan, commercial-finance broker and debt-service advertiser may face different requirements.

Google has both general financial-services rules and product-specific restrictions. For example, its US policy prohibits advertising personal loans with an APR of 36% or above, including through lead generators. That is a defined personal-loan restriction, not a rule to copy indiscriminately onto every business-finance product. Google financial products and services policy

For an MCA or other commercial-finance offer, ask the compliance owner to document the product classification and applicable disclosure requirements. Do not let a template decide whether a factor rate, APR or another disclosure is required for that offer.

Check verification for each target market

Google requires financial-services verification in specified locations, with separate verification for each location where it is required. Its policy can cover services that are not regulated by the relevant financial regulator, as well as certain non-financial advertisers. Google financial-services verification

Make one record per product and market. Include the policy link, advertiser category, account ID, submitted domains, current status, evidence date and next action. Use “not yet checked” where evidence is missing. An empty field is safer than an assumed approval.

For a UK campaign, identify the relevant FCA authorization or Google exemption route. Google's UK process has an approved-third-party route involving an FCA-authorized firm; an agency relationship alone does not establish that status. Google UK verification requirements

Separately, UK financial promotions must meet applicable FCA requirements, including being fair, clear and not misleading. Platform verification does not replace that review. FCA financial promotions and adverts

Ask what happens to verification during the handover

Do not accept “our manager account is verified” as the whole explanation. Ask which certification applies, which account and domains it covers, and what must happen when the proposed structure changes.

Google provides a Manager Account Certification application for some additional managed accounts; eligibility varies. It also says payment-profile changes can trigger re-verification. Confirm the applicable route and account status before assuming coverage carries over. Google financial-services verification

The handover record should answer:

Keep identity documents, borrower information and credentials out of an initial sales inquiry. The first conversation should establish scope and the appropriate process for any later document exchange.

Separate manager access from account ownership

Record the client account ID, manager account, direct administrators, billing contact and responsible business. Include the permissions needed for the proposed work and the permissions that are unnecessary.

Google distinguishes linking an existing account from granting its manager administrative ownership. An owner manager has additional privileges; the client account retains ownership of its data. The agreed access design should reflect those distinctions. Google manager-account ownership

Before authorizing changes, request an exit plan. It should describe how your team retrieves reports, removes access, handles outstanding billing and keeps control of its own website and business assets. “Managed access” should come with an explanation of day-to-day control and the end of the relationship.

Review the landing page and measurement together

A verification packet should point to the page customers actually see. Google’s general financial-services policy requires visible business-address and fee disclosures, plus evidence links for asserted third-party accreditation or endorsement. Product-specific requirements may add more. Google financial products and services policy

Review the current page on mobile as well as desktop. Check the advertised entity, actual offer, qualification language and destination of the inquiry. Record any claim that needs evidence or approval before it is used.

Also document which conversion events and fields would reach advertising platforms. Google’s customer-data policy prohibits enhanced-conversion measurement using conversions related to sensitive categories, including negative financial status. Hashing an identifier does not remove that restriction. Google customer-data policy

Ask the implementation owner to test the proposed data flow using synthetic inputs. Review event payloads, page URLs and downstream destinations before enabling collection. A server-side connection needs the same policy review as a browser-based connection.

If Meta or another platform is also in scope, give it a separate eligibility, targeting and data review. A Google verification record cannot answer those questions.

Use this handover sign off checklist

Assign one owner and an evidence link to each item. Mark it ready, blocked or not applicable, with a reason.

  1. Business and product identified for every target market
  2. Regulatory reviewer and applicable requirements recorded
  3. Current account verification status evidenced
  4. Proposed account or payment changes assessed
  5. Access, billing and exit responsibilities agreed
  6. Landing-page claims and disclosures reviewed
  7. Measurement events and data recipients reviewed
  8. Open dependencies and the next decision recorded

This is a coordination checklist, not a compliance score or a prediction of approval. A completed list can still contain a blocked launch if the platform has not approved the necessary step.

If there is an active suspension, resolve that issue through the platform’s process. Google's circumvention policy prohibits using new accounts to re-enter the system after suspension. A provider should not propose a handover as a way around enforcement. Google circumventing-systems policy

Request a focused infrastructure review

Fintech AdInfra’s published review scope covers account structure, billing setup, landing-page disclosures and relevant platform requirements. Start with your platform mix, product, target countries and the operational question you need answered.

Request a fintech infrastructure review. Please do not include borrower financial details, credentials or documents in the inquiry. Eligibility, scope and platform decisions need to be confirmed for your business.

Policy sources checked 3 October 2026. Requirements can change; check the linked official guidance and current account notices before acting.