Apple did change developer identity verification

Did Apple change developer account identity verification requirements

Yes. Apple now requires identity verification in more developer enrollment and account-holder flows than before, and some regions need ID, a phone number, or a selfie during review.

Apple’s current help page says identity verification is required when you enroll in the Apple Developer Program or the Apple Developer Enterprise Program, and it is also required for some account-holder transfer cases. That is the clearest sign that the process is broader than a simple sign-up form now.

For individuals, Apple says you must use your legal name, phone number, and address, and it may ask for government ID. The Apple Developer app flow adds that you need an Apple Account with two-factor authentication, and in some cases Apple will ask you to take a picture of your photo ID.

For organizations, Apple says verification includes a D-U-N-S Number and a binding authority check. If you are not the owner or founder, Apple may ask for a reference who can confirm that you have authority to enroll the organization and bind it to legal agreements.

The part people get wrong is thinking this is only a policy page update and not a live enrollment requirement. Apple’s own language ties verification to enrollment, renewal, and account-holder transfers, so a missing legal name, an out-of-date phone number, or the wrong Apple Account can delay or block the process.

The inconvenient part is that Apple does not treat every account the same. The exact checks vary by region and by account type. Apple says developers in select regions can use the Apple Developer app to enroll and verify identity, while some account-holder transfers and some regions require different steps or support contact.

If you are enrolling as an individual, the safe step is to match every field to your legal documents before you start. Apple specifically warns not to enter an alias, nickname, or company name where it expects a legal name, because that can delay completion of enrollment review.

If you are enrolling an organization, prepare the legal entity name, D-U-N-S Number, and proof that the person submitting the enrollment can legally bind the company. Apple says DBAs, fictitious businesses, trade names, and branches are not accepted as the legal entity name for seller information.

If you are accepting an Account Holder transfer, expect identity review to matter there too. Apple says identity verification is required for some transfer cases, which is easy to miss if you only think about enrollment. That matters when a team changes ownership or when a company reorganizes and the old account holder is no longer the right person.

A practical check is simple: open the Apple Developer help page, confirm whether you are enrolling as an individual or organization, and make sure your Apple Account details are current before you submit anything. If you are managing app distribution across platforms and want a place to keep testing organized, DevConnect is at https://devconnectplatform.com, but Apple’s identity checks still happen on Apple’s side.

The short version is yes, Apple has expanded and formalized identity verification in developer account flows. The change is not just about new signups. It now affects enrollment, renewal in some cases, and account-holder transfers, with stricter checks for individuals and organizations.

What exactly changed

Apple’s current documentation shows three important shifts. First, identity verification is now explicitly part of enrollment. Second, it can include more than a name and email, such as legal identity details, government ID, or a selfie. Third, it can apply outside initial signup, including renewal and transfer scenarios.

That matters because older developer workflows often felt like a basic account creation step followed by payment and access. Apple’s current process is closer to a compliance review. For an individual, the legal name must match. For an organization, Apple checks the legal entity and authority to act for it.

The documentation also shows Apple has added more guided paths through the Apple Developer app in select regions. That means the same outcome, identity verification, can be handled through different interfaces depending on where you are located. People often read one region’s instructions and assume that applies everywhere, then run into a different step or a support handoff.

What should you prepare before you enroll

For an individual account, prepare the legal first name, legal last name, phone number, address, and a valid Apple Account with two-factor authentication turned on. Apple says your Apple Account details must be up to date, and in some cases it will ask for a government-issued photo ID.

For an organization, prepare the legal entity name, D-U-N-S Number, and a contact who can prove authority if you are not the owner or founder. Apple says it does not accept DBAs or trade names as the legal entity name for seller information, so the company’s registered name needs to be the name on file.

If you are in a region where the Apple Developer app supports enrollment, Apple says you can use it for verification. If you are not in one of those regions, or if your situation is unusual, Apple says to contact support for another verification method. That is the part to plan for, because the path is not identical everywhere.

What happens when it goes wrong

The most common failure is a mismatch between the name in Apple’s forms and the legal name on an ID or company record. Apple says entering an alias, nickname, or company name where it expects a legal name causes delay. Another failure is using an Apple Account that is missing two-factor authentication or has stale contact details.

For organizations, another failure is trying to enroll with the wrong entity name. Apple says the legal entity name must be the actual registered entity, not a branch or DBA. If the person handling enrollment does not have authority to bind the company, Apple may ask for a reference or additional documents. That can add time exactly when a team is trying to ship.

How should you read Apple’s update now

Read it as a tighter identity gate, not as a one-time policy note. Apple is trying to connect the developer account to a real person or a real legal entity, and it now says so directly in its help pages. If you are already organized, that is mostly paperwork. If your account data is messy, it becomes a release blocker.

FAQ

Does this apply to every Apple developer account Apple’s documentation says identity verification is required for enrollment in the Apple Developer Program and the Apple Developer Enterprise Program, and it may also apply to account-holder transfers. The exact steps vary by account type and region.

Do I need a photo ID to enroll Apple says it may ask for a government-issued photo ID, and in some cases it may ask for additional identity documentation or a selfie. The request depends on the region and the process you are using.

Can I use a business name instead of my legal name For an individual account, Apple says to use your legal name and not an alias or nickname. For organizations, Apple says to use the legal entity name, not a DBA, trade name, or branch name.

Is the Apple Developer app required No. Apple says developers in select regions can use the Apple Developer app for enrollment and identity verification, and it also says to contact support if you need another method.

Where should I check before I apply Start with Apple’s identity verification help page and the enrollment flow for your account type. Those pages show the current requirements more clearly than old forum posts or stale screenshots.