TGX Account
The TGXAccount technical team has successfully removed payment cards from actually tested advertising accounts by executing a script in the browser Console. This article shares the specific process and operational precautions.
In the original script, OK is used to specify card deletion, while Cancel will attempt to batch-delete all bank cards. The meanings of these two options differ from standard confirmation pop-ups, so be sure to confirm before operating.
1. What are restricted cards and outstanding debt cards in Facebook ad accounts?
Friends who frequently use Facebook Ads for advertising should all be familiar with managing payment methods for ad accounts.
Generally speaking, ad accounts can be linked to credit cards, debit cards, or other supported payment methods to pay for the costs generated by ad campaigns.
However, in actual operations, you may encounter situations such as being unable to delete a bank card, payment failures, or restricted accounts.
In the Chinese advertising community, payment cards involved in such issues are often referred to as restricted cards, debt cards, or abnormal cards. These are common colloquial terms and not official uniform bank card categories designated by Meta.
Usually refers to a bank card associated with a restricted ad account, or one experiencing issues such as payment verification or transaction anomalies.
Usually refers to a payment card associated with an account that has an outstanding ad balance.
The account is normal, but the bank card has expired, been deactivated, or is no longer needed.
Regardless of the situation, if the payment method cannot be removed normally in the backend, you must first check the ad account status and bank card information.
An abnormal bank card payment does not necessarily mean the ad account is banned. An ad account restriction does not necessarily mean the bank card itself is invalid. Both should be investigated separately.
2. Why can't bank cards be deleted from Facebook ad accounts?
There isn't just one common reason why a Facebook ad account fails to delete a card.
1. The current bank card is still the primary payment method
If the bank card is still the primary payment method for the ad account, the account may require setting up another payment method first before the original card can be removed.
2. The ad account has an outstanding balance
If the ad account has unpaid advertising bills, payment method management may be restricted.
Please note that removing a bank card and settling advertising fees are two different things. Even if the bank card is successfully removed, it does not mean that the original debt has disappeared.
3. Insufficient permissions for the current Facebook account
Some team members can view campaigns, but do not have the permission to modify payment methods.
In this case, you need to first confirm whether the currently logged-in account has the corresponding payment management permissions.
4. The ad account itself is in a restricted status
If the account has payment verification, security checks, or other restrictions, some management functions may be affected.
Such situations need to be judged based on the actual status of the account, and the cause cannot be determined solely by whether the delete button is available.
3. Under normal circumstances, how to delete a bank card from a Facebook ad account?
If the ad account is in a normal state and you just need to delete an old card, it is recommended to try Meta's built-in payment settings first.
Log in to the Facebook account with corresponding management permissions.
If managing multiple ad accounts, first confirm the ad account ID you need to operate on.
Open the billing and payments management page, and find the payment method settings.
Confirm the target card based on the card brand and the last four digits.
If the account allows normal deletion, follow the on-screen prompts to complete the removal.
If normal operations cannot complete it, you can continue to learn about the methods tested by the TGXAccount technical team below.
IV. TGXAccount Practical Test: F12 Console to Remove Bank Card
The core content of this article is shared below.
In actual tests, the TGXAccount technical team successfully completed the removal of the credit card from the Facebook ad account by executing the specified script via the browser developer tools Console.
This method is different from regular payment settings. It sends a credit card removal request through internal web interfaces, so you need to confirm the account, code content, and target bank card before proceeding.
This method has been tested by the TGXAccount technical team. However, test success does not mean all ad accounts will get the same result. Different account statuses, permissions, and Facebook interface versions may affect the final execution result.
What needs to be prepared before operation?
Ensure the currently logged-in account has permission to manage the target ad account.
Confirm the brand and last four digits of the target bank card in advance.
Use a desktop browser that supports developer tools, and go to the payment settings of the target ad account.
Specific Operational Workflow
Log in to Facebook, navigate to the ad account you want to operate on, and open the corresponding payment method management page.
Before proceeding, verify the ad account ID corresponding to the current page to avoid operating on the wrong ad account by mistake.
On Windows browsers, you can usually press F12, then switch to the Console.
If you are using Chrome on Mac, you can also access developer tools via the browser menu.
Open the technical test code page provided below in this article, and confirm that the version used has been reviewed by the team.
This type of code can read current web session information and send operational requests; do not run it directly without verifying the code content.
Once the code is verified to be correct, execute the corresponding script in the Console.
If the browser displays a code pasting warning, you should first confirm the code source and operational risks. Do not treat disabling browser protection as a necessary routine operation.
The original script will make selections based on pop-ups, branching into specified bank cards or batch processing.
Special attention must be paid here: The functions of OK and Cancel are not the same.
After execution, check the results returned by the Console and review the list of payment methods.
Only by confirming that the target bank card has been removed from the corresponding payment account can you determine whether this operation was successful.
> Target: Facebook Ads Payment Settings
> Tool: Browser Console
> Action: Remove Payment Method
> Result: Verify in Billing Settings
Technical test code reference address:
External code pages may be updated, and Facebook's internal interfaces may also change. Therefore, a version that was successfully tested by the team does not mean it will necessarily work at any time in the future. Re-confirm the code content and applicable accounts before proceeding.
V. Must Read: What Do OK and Cancel Actually Mean?
This step requires the most attention in the entire tutorial.
The original script will display a browser confirmation popup. Although the interface uses the common OK and Cancel buttons, their actual functions in this code are different.
After selecting OK, the code will prompt for the target bank card information, then attempt to find the matching payment card and send a removal request.
After selecting Cancel, the original code will iterate through the retrieved bank card list, and attempt to send removal requests for each bank card separately. This is not a regular cancel operation.
The original script sets Cancel as the batch deletion branch. If you only want to delete a specific bank card, do not mistakenly think that clicking Cancel will safely exit. Batch operations also do not guarantee that all cards can be successfully removed.
How is the specified card identified?
The original script searches for the target based on the bank card brand and the last four digits of the card number entered by the user.
For example:
> MasterCard 4352
Where MasterCard represents the bank card brand, and 4352 represents the last four digits of the card number.
However, please note that if there are multiple cards with the same brand and last four digits in the account, relying solely on these two conditions may not uniquely identify the target.
Therefore, you should review the payment method list before proceeding, and avoid making random selections based on memory.
6. After the operation is complete, how to determine whether the bank card has been successfully deleted?
Prompts appearing in the Console do not necessarily mean the payment method has been successfully removed.
The original script will output results based on the information returned by the interface, but you ultimately still need to return to the ads account backend to confirm.
Check whether the script returns success messages, error prompts, or request failure logs.
Reopen the target ads account payment settings to confirm whether the corresponding card still exists.
Check for other payment restrictions, unsettled balances, or account alerts that need attention.
What if the Console indicates success, but the bank card is still there?
You can first reopen the payment settings page to check if the same card is still displayed.
If the payment method has not changed, you cannot judge success solely by the text output in the Console.
In addition, the script may fail to execute due to insufficient permissions, API updates, or account restrictions.
What if only some bank cards were deleted?
Batch operations do not necessarily mean all bank cards were successfully removed.
The original script sends payment card removal requests separately, and different cards may return different results.
Therefore, you still need to check the final list one by one.
7. What precautions should be taken in advance when using this method?
Although the TGXAccount technical team has successfully tested this, for operations involving account payment methods, it is still recommended to perform the following checks in advance.
1. Confirm that you are operating on your own ad account
Only perform operations on ad accounts for which you have administrative permissions or explicit authorization.
If you manage multiple BMs and ad accounts, it is especially important to verify the current ad account ID.
2. Do not run code directly without understanding it
This method executes code within the logged-in Facebook web environment.
The script needs to read information related to the current session and send requests through internal interfaces.
If the script is modified, the execution content may also change.
Chrome Developer Tools displays security warnings for some users' code-pasting actions to reduce the risk of users being tricked into running malicious code. When you see this prompt, you should inspect the code first rather than simply bypassing the security protection.
3. Verify bank cards before specifying card deletion
Confirm the bank card brand, the last four digits of the card number, and the current payment account.
For ad accounts with multiple payment cards, it is even more important to avoid mistakenly deleting other cards due to misidentification.
4. Confirm business impact before bulk card deletion
If the ad account is still in use, batch removing payment methods may affect subsequent ad billing.
Do not treat all bank cards as useless cards that can be deleted at will.
5. Deleting a bank card does not mean clearing outstanding balances
Payment methods and ad bills for Facebook ad accounts belong to different management objects.
Even if the bank card has been removed from the account, the actual advertising costs incurred will not automatically disappear.
This article describes the payment method removal operation, not a tutorial on clearing ad bills. If the account has an actual outstanding balance, it should be handled through the corresponding billing and payment process.
6. Deleting a card does not lift ad account restrictions.
If the account has payment verification, security reviews, or ad policy restrictions, deleting the bank card may not necessarily resolve these issues.
You should address the account status and payment issues separately, based on the specific reasons displayed in the backend.
8. What else can you check if restricted or indebted cards fail to be deleted?
If the payment method still fails to be successfully removed after performing the operations, you can continue troubleshooting according to the sequence below.
Does the currently logged-in account have payment management permissions for the corresponding ad account?
Are the card brand and the last four digits correct? Can the target card still be found in the payment method list?
Check whether the ad account has unpaid bills, as well as any payment failure prompts.
Confirm whether there are identity verification, payment verification, or other account restrictions.
If technicians are executing scripts, they should check the real API response rather than just looking at the success prompt output by the script.
If the issue persists, you can keep your ad account ID, error messages, and relevant billing information ready, and use the support channels provided by Meta for further investigation.
