A declined ad payment is often immediately blamed on a virtual card. First establish whether the problem is the payment entry point, cardholder verification, an issuer decline or a restricted asset.
Identify the point of failure
| What appears on screen | Where the issue starts | Next action |
|---|---|---|
| Payment option is unavailable | Access, target asset or ad-account state | Verify Profile, asset and permissions |
| 3DS or a holder check is requested | Cardholder and issuer verification | The authorized holder completes or reviews it |
| Card or issuer explicitly declines | Payment method | Check status, balance, billing details and capability |
| Account or BM is restricted | Account or asset state | Preserve status and use the relevant owner path |
Do not add a second variable too early
A new card cannot repair an unavailable payment entry point or an account restriction. Repeated submissions do not complete cardholder verification.
Check payment responsibility
Before binding a payment method, confirm the target ad account, the authorized holder, billing details and any current balance or pending item. Never collect passwords, cookies, TOTP codes, verification codes, full card numbers or CVV in routine task notes.
Read back the ad-account state
A tool confirmation is not proof that the ad account is usable. Return to the ad account and record the page result separately from the payment result.
Keep payment and account outcomes separate
An accepted card-binding action does not prove that an ad account is active, and a restricted ad account does not establish that a card was declined. Preserve both results as shown on their own pages so the next action remains attributable.
When to replace a card
Consider it only after an explicit payment-layer decline with a normal ad-account state. Otherwise resolve the identity, asset or restriction result first.
For the wider workflow, see Facebook BM workflow automation and BM delivery verification. To discuss a permitted workflow integration, use product contact; do not provide passwords, Cookie values, TOTP secrets, verification codes, full card numbers or CVV.
When the page shows a personal-account, ad-account or BM restriction rather than a clear decline, see which Facebook object is restricted. For an identity prompt, see required BM 2FA.