zhizhulailai
Newbie
- May 15, 2025
- 17
- 1
I tried changing the BIN, but I'm still running into the same problem. Bro, how did you fix it?
Did you create your ad account and start running ads immediately? Or did you wait a long time after creating it before launching your campaigns?This have been happening for a while in some latam accounts i handle, but all we need to do usually is just change the payment method (for example, if you use cc, you change for wire), and after some time, try with another bin and everything will go well
It seems I am unable to send private messages; I am currently borrowing an account that has this capability. I have already set up profiles for Thailand, Malaysia, the UK, the US, and Puerto Rico—and even changed the BIN—yet I am still consistently triggering the "PAY 20" requirement 100% of the time.“Write to me in a private message we’ll try to find the cause. It looks like there’s a vulnerability somewhere in your system, and we need to patch it
The only thing i do is the first company verification, in latam geo they are quite simple. Once the account is verificated, i begin running ads, and usually after one up to 3 weeks this payment problem happens... that's when i just select another payment method and use for 3 or 4 payments. And after that, i just go back to cc without any problem. I hope that this helps you.Did you create your ad account and start running ads immediately? Or did you wait a long time after creating it before launching your campaigns?
Did you actually pay the $20 for this verification task every single time?The only thing i do is the first company verification, in latam geo they are quite simple. Once the account is verificated, i begin running ads, and usually after one up to 3 weeks this payment problem happens... that's when i just select another payment method and use for 3 or 4 payments. And after that, i just go back to cc without any problem. I hope that this helps you.
No, never happened to me... but it might be the geo, i don't knowDid you actually pay the $20 for this verification task every single time?
Has this $20 payment task never triggered for you—based on your GEO location and BIN?No, never happened to me... but it might be the geo, i don't know
It looks like those €13/€26 charges are likely Google payment-method verification charges (or temporary authorization holds), triggered by the “Verify your account / Make a payment” process, rather than actual ad spend.
I tried the UK and got the same result.Switched to different GEO's after that s*** from Google. UK doesnt require any payments
and what if we cancel the google ad account then google still won't refund the money?
- It is recommended to change not just the card, but the bank BIN (the first 6 digits of the card), as Google no longer trusts the current BIN. Simply replacing the card without changing the issuing bank will not solve the issue.
- As an additional step, it is better to replace the second document requested by Google for address verification. Ideally, provide an alternative document from a different category.
For those accounts where Google requested a payment but did not take any action, you can add the amount it asks for. However, this money will only remain on the account balance Google will not refund it to you.
Good luck at work)
sually, when a Google Ads account is closed, the refund is automatically sent back to the original payment method the card or bank account.and what if we cancel the google ad account then google still won't refund the money?
We’ve had cases like this with new accounts, and twice with accounts that were approaching €5,000.Google has gone mad, making me pay over $7,000.View attachment 527454
Is this a Google bug or a new update trend?We’ve had cases like this with new accounts, and twice with accounts that were approaching €5,000.
Please delete this account and create a new one, my friend.
n my opinion, this is an issue on Google’s side. Most likely, some of Google’s settings have not been fully refined yet, which is causing the system to work unstably.Is this a Google bug or a new update trend?