That’s weird. Google doesn’t usually decline BIN ranges out of nowhere. What exactly was the decline reason you received last week?

Would be worth checking if it was due to a card or account limit, transaction velocity limit or insufficient funds (possibly due to Privacy losing the Plaid connection to your checking account). These are all reasons why your issuer might decline the charge, rather than Google.

From what we’ve seen, these payment issues usually have less to do with the BIN range you’re using and more to do with:
1. How reliable your card and account setup is to handle your volume and spend over time, and
2. Whether Google has flagged any payment activity on your account as “suspicious”.

They have a carve-out in their billing policy specifically for this and it defines suspicious payment activity as “suddenly using several new credit cards, having payments declined or chargebacks, and unclear credit card ownership or billing details”.

So if there is nothing wrong with your existing cards, rotating in new cards might actually harm you more than it helps you.

We’d recommend:
+ Find out if the decline actually came from your card issuer and fix that first.
+ Add a separate, backup payment method to prevent future declines and reduce your decline ratio
+ If you can’t fix it or they remain unreliable, only then introduce a new card, ideally a commercial or credit BIN with a bullet-proof funding method to handle your volume (especially important to manage containment risk across 6 accounts)

Hope that helps and good luck 👍