Unable to activate Blaze plan — billing account creation fails repeatedly

Title: Unable to activate Blaze plan — billing account creation fails repeatedly

Hello,

I’ve been trying to upgrade my Firebase project to the Blaze (pay-as-you-go) plan for two days, without success, and I’m hoping someone in the community can help identify the root cause.

Project details

  • Project ID: (PII Removed by Staff)
  • Project name: (PII Removed by Staff)
  • Google account: (PII Removed by Staff)
  • Country: Senegal

What I’ve tried and the errors encountered

  1. First attempt with a prepaid card — correctly rejected (expected, prepaid cards aren’t accepted).
  2. Second attempt with a Visa debit card (issued by Djamo, a Senegalese neobank, sufficient balance available): the card was successfully added, but activation failed with:
    “Impossible de terminer la configuration de la facturation. Action impossible. [OR_BACR2_44]”
  3. Retried in a different browser (Microsoft Edge instead of Chrome): failed again with a different error code:
    “Une erreur inattendue s’est produite. Veuillez réessayer plus tard. [OR_BBFPPCPSD_23]”
  4. Removed the old declined card via Google Wallet, confirmed the Visa card shows correctly as the only payment method, retried: this time the message was
    “Impossible de trouver un compte de facturation nouvellement créé. Pouvez-vous réessayer ?” — this persisted for over 10 minutes without resolving.
  5. Tried going through Google Cloud Console directly (Billing > Modify billing) instead of the Firebase console: got “Aucun compte de facturation disponible” (no billing account available), confirming no billing account was ever actually created.
  6. Tried the official Cloud Billing support flow — it requires selecting an existing billing account administrator, which isn’t possible since no billing account was ever successfully created in the first place.

Question

Is there a known issue with billing account creation for certain card issuers or countries? Is there anything else I should try, or is this something that requires manual intervention from Google support?

Any guidance would be greatly appreciated. Thank you!

1 Like