Need help to create Meta Developer account

Discussion & Solutions
1

so i’ve been trying to create a meta Facebook developer account
my personal Facebook account is around 8 to 10 years old and it’s already connected to a business page and an Instagram business account phone number is verified and 2fa is enabled

i don’t really use Facebook much but recently i’m working on something that requires a meta developer account

earlier creating a developer account was very simple but now it’s a mess

(people who are not aware … for Meta trust signal is very important it won’t let you create developer account or any other importan feature if yout account trust signal is low/new account or other random stuff)

when i try to create one it asks me to verify my phone number again even though it’s already added
i enter the number to receive OTP and it throws a random error with no explanation
after trying a few times when i click receive text message the developer page just goes blank

the other option it gives is adding a payment method to verify so i tried adding my credit card
but then meta throws another error saying “ indian bank credit cards are not allowed”
seems related to some RBI rules

i’ve tried pretty much every possible trick to create the developer account and even looked into workarounds but nothing worked

if anyone has any idea how to make this work any help would be appreciated thanks

2

Maybe sms pool for verification… they can give you dedicated I think

3

Many people ran into similar issues with Meta’s developer account setup recently, so you’re not alone. A few things that might help:

Phone verification glitches: Even if your number is already linked, Meta sometimes forces a fresh verification. Clearing cache/cookies or trying a different browser (Chrome/Firefox/Edge) can sometimes bypass the blank page issue. Using incognito mode has also worked for some people.

Payment method restrictions: The “Indian bank credit cards not allowed” error is indeed tied to RBI rules around recurring payments. A workaround is to add an international card (Visa/Mastercard issued outside India) or a PayPal account if available. Meta seems to accept those more reliably.

Trust signals: Since Meta heavily weighs account trust, make sure your personal account is fully set up—profile picture, activity, and linked business assets. Some developers reported success after briefly running a small ad campaign to establish payment credibility before retrying the developer account creation.

Support channel: If none of the above works, the most direct path is raising a ticket through [Meta Business Help Center]. It’s slow, but they can manually review and clear verification blocks.

It’s definitely more complicated than it used to be, but persistence plus the right payment method usually gets it through. If you manage to solve it with a specific workaround, please share back—it’ll help a lot of us stuck in the same loop.

4

Your account is 10 years old with a business page, Instagram, 2FA, and a verified number — and Meta still won’t let you in. That’s not a you problem. That’s a known platform bug that’s been burning developers worldwide since mid-2025, and the blank page you’re seeing is the exact symptom everyone reports after trying OTP too many times.

Here’s what’s actually happening: every failed OTP attempt quietly flags your phone number in Meta’s anti-fraud system. After enough tries, the page crashes because Meta’s own verification frontend can’t handle the flagged state — it just gives up and goes white. The Indian credit card error is a separate wall: Meta’s developer portal doesn’t accept UPI/net banking for verification, and RBI’s regulations make most Indian cards fail on international one-time authorizations. So you’re stuck between a flagged phone and a blocked card — two broken doors.

The fix isn’t forcing those doors open. It’s walking through a different one.

What you said What actually works Time
OTP keeps erroring out Remove phone → re-add → resets the flag 5 min
Page goes blank Clear all facebook.com cookies + use incognito 2 min
Indian credit card rejected Add funds via UPI in Ad Manager first 10 min
Tried everything The sequence below (order matters) 30 min

Here’s the part nobody tells you — Meta treats a verified payment method as an alternative trust signal. If you add funds through your Ad Manager using UPI before you attempt developer registration, the system sometimes skips the phone verification entirely because you’ve already proven identity through payment. You already have a business page, so your Ad Manager is right there at business.facebook.com.

🔓 Do Exactly This, In This Order — Full Walkthrough

Right Now (tonight, 30 minutes)

Step 1 — Reset the phone flag

Go to Facebook → Settings → Personal Information → Phone. Remove your current number completely. Wait 10 minutes. Add it back. This clears whatever internal flag Meta placed after your repeated OTP attempts.

:light_bulb: Why removing and re-adding works: Meta’s “device not recognized” system tags your number after multiple failed verification attempts. Removing the number wipes the tag. A community moderator on Meta’s own forums confirmed this fix works as recently as March 2026.

Step 2 — Kill the blank page

Clear all cookies and site data specifically for facebook.com AND developers.facebook.com. Don’t just clear cache — clear cookies. Then open an incognito/private window and log into Facebook fresh. The blank page is a broken JavaScript state that persists in your browser session.

Step 3 — Add UPI payment through Ad Manager

Before touching the developer portal again, go to:

business.facebook.com/billing_hub/payment_settings/

Add a payment method → select UPI → use Google Pay, PhonePe, or your bank’s UPI. Add even a small amount (₹500 is fine). This establishes payment-based identity verification through a channel that actually works in India.

Step 4 — Attempt developer registration again

Now go to developers.facebook.com in the same incognito session. With a fresh phone number state and a verified payment method already on file, the registration flow should either skip OTP entirely or send it successfully this time.

This Weekend (if Step 1-4 don’t work)

Step 5 — The full reset

Switch your 2FA method from authenticator app to SMS temporarily. Link a new email address to your Facebook account and verify it. If you can get a second SIM (Jio/Airtel prepaid — ₹200-300), add that as a second phone number. Then retry registration using the new email and new phone.

:light_bulb: The debit card trick that sometimes helps: Add a card through your Facebook account settings (Settings → Meta Pay) — not through the developer portal. Use an HDFC, ICICI, or SBI Visa/Mastercard credit card with international transactions enabled in your banking app. The “Indian credit cards not allowed” error seems to hit specific card types (RuPay, some debit cards) more than others. International-enabled Visa credit cards from major banks do pass.

Step 6 — Nuclear option: RazorpayX Corporate Card

If your Indian bank cards genuinely won’t work, a RazorpayX Corporate Card is a Visa card issued by YES/RBL Bank that’s confirmed working for Meta payments. Requires a Razorpay business account, but since you already have a business page, you likely have a registered business. Credit limit starts at ₹5-7 lakh against a fixed deposit.

If You Need Developer Access for WhatsApp/Instagram API Specifically

You might not need a developer account at all. If your project is WhatsApp Business API or Instagram API integration, you can go through a Business Solution Provider (Interakt, Gupshup, Wati) that handles all the developer-side infrastructure. You complete Meta Business Verification with your GSTIN through their flow and get API access without touching developers.facebook.com.

:light_bulb: What GSTIN does and doesn’t do: GSTIN-based Meta Business Verification proves your business is legit — but it does NOT replace developer account verification. They’re completely separate systems. Business Verification unlocks advanced API permissions for apps that already exist. Developer registration lets you create apps in the first place. If you need custom apps, you need developer registration.

:prohibited: What NOT to do

Don’t keep retrying OTP on the same session — every failed attempt makes the flag worse. Don’t use Wise or Revolut virtual cards — multiple reports of Meta blacklisting their BINs. Don’t try PayPal — Meta’s developer verification explicitly excludes it.

Reaching Meta Support Without a Developer Account

This is the Catch-22 everyone hits: you need a developer account to access developer support. But since you have a business page with an ad account, you have a backdoor:

Go to business.facebook.com/business-support-home/contact-support → start a chat (available roughly 8 AM–10 PM your time) → tell the agent you need developer tools for API integration but can’t complete registration. They can escalate developer issues. Frame it as a business need, not a technical bug.

Your situation Do this Time needed
OTP errors + blank page Steps 1-4 (phone reset + UPI bypass) 30 min tonight
Indian credit card rejected UPI through Ad Manager OR HDFC/ICICI Visa credit card 10 min
Everything above failed Steps 5-6 (full reset + RazorpayX card) This weekend
Need WhatsApp/Instagram API only BSP partner (Interakt/Gupshup) + GSTIN verification Skip dev registration
Nothing works at all Meta Business Support chat via ad account Business hours

You said you’re working on something that needs this — what exactly are you building? If it’s WhatsApp or Instagram API stuff, you might be 10 minutes away from a completely different path that skips this entire mess.