Error 131045 tells you a message could not be sent because the phone number is not properly registered. Meta documents it as "Incorrect certificate," describing it as a message that failed to send due to a phone number registration error, with an HTTP status of 500 Internal Server Error and a recommended action of registering the phone number before trying again (Meta for Developers, WhatsApp error codes reference, retrieved 2026-08-20).
The 500 is misleading in the same way it is for error 3. A server-error status usually means "wait and retry," and teams duly retry for an hour. But the recommended action says to register the number, which is a deliberate action on your side — not something that resolves itself.
This guide covers what "certificate" means here, how 131045 differs from the other registration codes, and the re-registration sequence. For the wider failure surface, our WhatsApp Business API error codes reference indexes the rest.
What "Certificate" Means Here
The terminology is a holdover. Registering a business phone number on the WhatsApp Business Platform establishes a credential binding that number to your account, and Meta's error text calls that binding a certificate. When it is missing, stale, or does not match the account making the request, sends fail with 131045.
The states that produce it:
State | How you got here |
|---|---|
Never registered | Onboarding incomplete — the number exists in the dashboard but registration was not finished |
Registration incomplete | The flow was started and abandoned, often at the verification code step |
Migrated without re-registering | Number moved between providers or WABAs and the new binding was never established |
Registration invalidated | An account change, provider switch, or security action broke the existing binding |
Wrong account | The number is registered, but to a different WABA than the credentials you are using |
That last row overlaps with error 131009, where a valid phone number ID belonging to a different account gets rejected as an invalid value. If you have several WABAs or several environments, check which account owns the number before assuming the registration itself is broken.
Registration Codes, Side by Side
Four codes cover this territory and they are routinely confused. The remedies differ enough that guessing costs a day.
Code | Meta's description | HTTP | What to do |
|---|---|---|---|
131045 | "Incorrect certificate" | 500 | Register the phone number |
"Phone number Not Registered" | 400 | Register the phone number | |
"Two step verification PIN Mismatch" | 400 | Verify or reset the PIN | |
"Too Many two step verification PIN Guesses" | 400 | Wait out the stated period |
131045 and 133010 arrive at the same remedy from different angles: one says the credential is wrong, the other says the number is not registered at all. In practice you work the same sequence for both.
The PIN codes are what you hit during that sequence, which is why the next section leads with the PIN rather than with the registration call.
The Re-Registration Sequence
Step 0 — Find the two-step verification PIN before you start. This is the step that determines whether this takes twenty minutes or three days.
Re-registration requires the PIN. It was set once during original onboarding, frequently by an agency or a colleague who has since left, and frequently never written down. Check your secret manager, your onboarding runbook, and any handover documentation now not after you have begun and hit error 133005.
If it is genuinely unavailable, you do not need the old one: disable two-step verification with a token carrying whatsapp_business_management permission, then set a new PIN. What you must not do is guess, because guessing trips the lockout in error 133008 and adds a mandatory cooldown to your outage.
Step 1 — Confirm the number belongs to the WABA you are authenticating against. A number registered to a different account produces this error while looking entirely correct in a dashboard you have open.
Step 2 — Confirm your credentials can perform the operation. Registration needs whatsapp_business_management. If this call fails on permissions, you have a separate problem in error 3 or error 10 to clear first.
Step 3 — Register the number, supplying the PIN, and complete verification via SMS or voice call to that number. Someone needs access to the physical number or its diversion to receive the code.
Step 4 — Store the PIN properly before you finish. Write it to your secret manager with a named owner and a note of which phone numbers it covers. The reason this error is expensive is almost never technical.
Step 5 — Send a test message to confirm the binding holds, rather than assuming.
If the account rather than the number appears to be the problem — a whole-WABA block rather than one number failing — you are more likely looking at error 131031, which has its own two-cause diagnostic.
Why It Shows Up at Migration
The most common real-world trigger is moving a number: between BSPs, from the WhatsApp Business App to the API, or between WhatsApp Business Accounts during a reorganisation.
A migration is a re-registration, and it needs the same PIN and the same verification step as the original. The pattern that produces an outage is a team scheduling a provider switch, completing the commercial and technical work, and discovering on cutover day that nobody has the PIN for a number registered three years ago.
The fix is a pre-migration checklist rather than a technical one. Before scheduling any cutover, confirm you can produce: the two-step verification PIN for every number, access to receive an SMS or voice call on each number, credentials with management permission on the destination account, and a named owner for the phone number assets. Our guide to switching WhatsApp API provider covers the wider handover, and multiple numbers on one WhatsApp Business Account covers the mapping you need when several numbers are in play.
Registration is also one of three independent go-live gates, alongside display name approval and billing configuration. Clearing one does not clear the others, and hitting them in sequence during launch week is a common and entirely avoidable experience.
Frequently Asked Questions
What does WhatsApp error 131045 mean?
The phone number is not properly registered, so the message could not be sent. Meta documents it as "Incorrect certificate," describing it as a phone number registration error, with a recommended action of registering the number before trying again. The certificate is the credential binding that number to your account.
Error 131045 returns HTTP 500. Is this a Meta outage?
No. A 500 normally signals a server-side fault, but Meta returns it here for a registration state problem on your account, and its own recommended action is to register the number — a deliberate action on your side. Retrying without registering will not resolve it, which is the same trap as error 3.
What is the difference between error 131045 and 133010?
Both end in the same remedy. Meta documents 133010 as "Phone number Not Registered" with HTTP 400, and 131045 as "Incorrect certificate" with HTTP 500. One says the number is not registered at all; the other says the credential binding it to your account is wrong or stale. Work the same re-registration sequence for either.
Do I need the two-step verification PIN to re-register?
Yes, and confirming you have it before you start is the difference between a twenty-minute task and a multi-day outage. If it is unavailable, you can disable two-step verification with a token carrying management permission and set a new PIN — you never need the old one. What you must not do is guess, since that trips the lockout in error 133008.
Why does this happen when migrating between providers?
Because a migration is a re-registration. It needs the same PIN and the same SMS or voice verification as the original registration, and both are commonly undocumented for a number registered years earlier. Confirm the PIN, verification access, and management credentials before scheduling any cutover date.
Check the PIN Before You Start
Error 131045 is short work when you have what it needs and a genuine outage when you do not, and the deciding factor is almost never technical. It is whether someone can produce a PIN set once during onboarding by a person who may no longer work there.
Treat that PIN as a production credential — secret manager, named owner, mapped to specific numbers, verified during access reviews, transferred in every handover. And treat registration as a lead-time gate alongside display name approval and billing setup, cleared during onboarding rather than discovered on launch day.
Want registration and credential custody handled properly? Helo.ai is a Meta Partner with 25 years of enterprise communication experience, managing number registration, two-step verification, and provider migration for enterprise WhatsApp programmes. Talk to an expert.
Next: error 133005 if the PIN is the blocker, or error 133010 for the unregistered-number case.
