.png)
Key Highlights
Google’s help documentation puts the decline decision with your credit card company or bank, and Meta points to the issuing bank for a large share of failures too.
- Google’s help documentation puts the decline decision with your credit card company or bank, and Meta points to the issuing bank for a large share of failures too.
- Meta stops the ads and takes the ad account offline until the outstanding balance clears, so a failed payment costs you delivery.
- Google’s suspension policy extends a suspension to accounts linked by payment method, so one card shared across several ad accounts is a single point of failure for all of them.
- Meta caps a single payment method at roughly ten ad accounts. Google and X both read repeated failed payments and chargebacks as a risk signal against the account.
- Across the seven Meta and Google billing and policy pages we reviewed, neither platform publishes a card trust score or a blocked-BIN list.
An ad account card declined mid-flight costs you more than the charge, because Meta pauses your ads and disables the ad account until you pay the amount due. The cause is usually a limit on the card, a verification step that cannot complete, or one card saved to too many ad accounts. This article covers what Meta, Google and X publish about each.
Who declines an ad account card, your bank or the ad platform?
Your bank declines the charge in most cases.
Google states it directly: “your credit card company or bank declines your payment, not Google.” Google’s support teams cannot overturn a decision the issuer made.
For Meta, it is both. Meta’s failed-payment guidance says your issuing bank “may also decline the transaction due to their internal rules”, and the same page lists refusals that belong to Meta, such as a payment method unsupported in your country or a card saved to too many ad accounts.
Check the error message first, because it names which party to go to. A bank-side refusal typically names funds, limits or verification. A platform-side refusal typically names support, eligibility, or the account itself.
Common reasons an ad account card gets declined
Google and Meta document these causes in their own billing pages. The third column names who can resolve each one.
More often than not, insufficient funds are not the reason. Advertisers see plenty of declines on cards with money sitting right there.
Why is an ad account card declined when there is money in the account?
Because your bank checks limits as well as balance. Google names both: a cap on how many charges the card accepts in a period, and a ceiling on what it allows in one transaction. So a fully funded card can break either.
Advertisers run into these limits more often than most card users. Since a media buyer charging daily across several campaigns can hit a per-period cap with plenty of credit still left on the card. Sometimes a finance team wants to reduce the administrative load and raises the billing threshold, which makes each charge larger and can push one past the card's single-transaction limit.
Platforms will usually shows the stated decline reason on the Billing Summary page whenever the issuer supplies one, so check there before changing anything on the card.
Why does a Facebook ads card declined error appear when the bank is fine?
Meta / Facebook sets its own conditions on a payment method for Facebook ads, separate from anything your bank decides. The common failures are about how the card is set up rather than whether there is money on it.
1. Saved to too many ad accounts. Meta says a payment method can typically be added to up to ten ad accounts, and frames the cap as an account-safety measure. Agencies tend to meet this one first. Saving the company card into every new client account crosses the line eventually, usually without anyone tracking how close it was.
2. 3D Secure cannot complete. Meta reports four ways that step fails where it is mandatory for a new card: a wrong CVV or one-time password, an undelivered one-time password, a connection problem at the card network, and the bank’s own internal rules. Advertisers fix more of these by keeping the phone attached to the card within reach than by swapping the card.
3. No security code on the card. Meta states that it accepts only cards carrying a CVV, CVC or CSC.
4. Not supported where your ad account sits. The payment methods for Facebook ads vary by the country and currency of the ad account, which typically catches teams working across several markets. Meta’s accepted list covers credit cards and co-branded debit cards. American Express works on automatic billing only, and not at all in India.
Does your card type or BIN affect whether an ad account gets blocked?
Google publishes one rule about card type, and it concerns prepaid: Google does not accept prepaid cards for postpay billing. That is the only card-type rule either platform spells out. Google pays more attention to how you pay than to what you pay with, and names suspicious payment activity as grounds for suspending an account or limiting its spend. The signals it lists include a sudden run of several new credit cards, repeated declines or chargebacks, and unclear card ownership.
But BIN quality does play a part, one layer below the ad platform itself. Visa documents that merchants and processors consume BIN attribute data covering the issuer, the product, and whether a card is credit, debit or prepaid. As a general industry practice, fraud tooling at the payment gateway or the acquiring bank can refuse a transaction on BIN-level risk before the authorisation ever reaches your issuer. So if an agency runs ad spend on cards sitting on a low-quality BIN, one with heavy fraud or chargeback history, or on ranges tied to prepaid and virtual cards used in suspicious patterns, those payments are more likely to be refused at that layer.
Neither Meta nor Google publishes any of this themselves. We reviewed seven of their billing and policy pages in October 2026 and found no BIN trust score and no blocked-BIN ranges, so your BIN can affect a charge without either platform holding a rule about it.
Do high-spend advertisers get moved off cards?
Some do, and on Meta and Google the change arrives as a requirement. Advertisers supported by Google’s Customer Solutions High Touch teams cannot pay by credit card, debit card or e-wallet, and advertisers under Large Customer Sales cannot pay by credit or debit card. Both groups move to monthly invoicing or direct debit instead.
Meta moved a group of advertisers the same way in 2026. A Meta spokesperson told Payments Dive in March that the company was “updating and streamlining our billing experience for a very small percentage of advertisers”, with affected accounts switching to monthly invoicing or direct bank debits from 1 April. Meta added that smaller advertisers were not affected, and disclosed no spending threshold. Agency trackers covering the change put the trigger near USD 50,000 of monthly spend. None of them cites a Meta source for that figure, so treat it as an estimate from the field.
Meta can still stop delivery under invoicing, because a credit limit caps the unpaid ad spend allowed on the line at any time, and Meta pauses ads once you spend the full amount. Meta is explicit that the limit is not a form of credit or financing.
What does it take to apply for monthly invoicing?
Advertisers can apply instead of waiting to be moved. Google and X both publish what that takes.
Google asks for a spend of USD 5,000 a month in any 3 of the last 12 months, a business registered for at least a year, and a Google Ads account in good standing for at least 6 months. Google calls those its initial requirements, so the full list may be longer.
Similar for X, X tells advertisers planning to spend USD 5,000 or more a month to apply for an insertion order, which removes the credit limit that otherwise caps an ads account.
We found no equivalent page from Meta, so an advertiser on Meta has nothing published to plan against.
Best Practices for Payments to Prevent Ad Account Blocks
Advertisers fix most repeat failures in the setup, so this is where the changes typically hold. Each practice below answers a payment failure that Meta, Google or X names in its own guidance. None of them removes policy risk or account risk, and no card choice guarantees approval.
- Add a backup payment method. Meta and Google both recommend one, and Google charges the backup only when the primary method is declined. Your campaigns keep delivering through a single bank refusal.
- Match your billing threshold to the card’s transaction limit. Meta advises lowering the threshold when a card caps single transactions, which turns one large failed charge into several smaller successful ones.
- Give each ad account its own payment method. Google’s billing and payment suspensions policy covers accounts related to a suspended one, and names a shared payment method as one of those links. Agencies isolate the exposure with one card per client.
- Keep funds available around the billing date. Meta charges at your payment threshold and again on the monthly bill date, so the balance has to clear two separate moments.
- Keep the card contactable and current. Meta’s verification depends on reaching the phone number attached to the card for a one-time password.
- Work out the cause on one card before adding another. Google names a sudden run of new credit cards as a suspicious payment signal, and X halts ads accounts for inconsistent payment information or for repeated chargebacks and failed payments. Cycling through cards after a decline looks a lot like the pattern both policies are built to catch.
FAQ
Why did my card get declined when I have money in my account?
Your issuer checks several things besides the balance. Google lists four reasons that fail on a funded account: a charge exceeding a single-transaction limit, a card that has taken too many charges in a period, an issuer blocking internet or international transactions, and an issuer that cannot complete Strong Customer Authentication.
Why is my debit card not working on Facebook?
The accepted payment methods for Facebook ads depend on the country and currency of the ad account, and Meta’s list covers credit cards and co-branded debit cards. Meta states that it accepts only cards carrying a security code, so a debit card with no CVV, CVC or CSC cannot be added.
Does a declined payment disable a Meta ad account?
Yes. Meta pauses the ads and disables the ad account until the amount due is paid, and applies no further charges in the meantime. Meta resumes active and scheduled ads once the balance clears, and attempts to make up lost time against the original campaign dates and budgets.
Can one declined card affect other ad accounts?
It can. Google’s billing and payment suspensions policy counts a shared card as a link between ad accounts, and acts on the accounts it links. An advertiser running one card across a whole portfolio typically ends up with a single shared point of failure.
How Reap Can Help
Reap is a Visa Principal Member and issues its own cards.
A team can scope each Visa credit card to a single client or campaign, with its own budget cap, category lock and expiry date. Every ad account then holds a card of its own, which answers the shared-payment-method problem directly.
Reap cards also have 3D Secure built in - this safety feature is important for ad spend as Meta makes that verification mandatory when you add a new card in some countries, and Google tells advertisers whose bank cannot complete Strong Customer Authentication to use a different payment method. The same account runs payments, expense management and treasury.
New Promotion on Ad Spends and Subscriptions: Businesses approved between 1 October and 31 December 2026 earn 10% cashback on their first USD 5,000 of qualifying advertising, SaaS and cloud card spend, capped at USD 500, subject to the published terms. See Reap’s cards for advertising.
Disclaimer
The information provided in this material is for general informational purposes only and does not constitute legal, financial, tax, or business advice. It should not be interpreted as a recommendation, offer, solicitation, or inducement to engage with Reap’s products or services. Any use of Reap’s services is at the user’s sole risk and discretion.
Reap makes no representation or warranty, express or implied, regarding the accuracy, completeness, or reliability of the information provided. Services are governed exclusively by Reap’s applicable legal agreements. Service availability, features, and eligibility may vary by jurisdiction and are subject to regulatory, card network, and operational limitations.
All trademarks, logos, and brand names are the property of Reap and/or their respective owners. References to third-party platforms or services are for descriptive purposes only and do not imply endorsement, partnership, or affiliation.
Reap’s services and information are provided on an “as is” and “as available” basis, without warranties of any kind. Reap shall not be liable for any loss or damage arising from the use of, or reliance on, this information or its services.
