2026 Apple Developer Account Registration: Complete Steps, Individual vs. Organization Accounts, D-U-N-S Application and Payment Pitfalls Guide

This week’s action: decide whether the publisher is you or a qualifying organization, then reconcile the matching identity or company records before opening the application.

This guide is for independent developers preparing to publish under their own names, and company representatives enrolling on behalf of an organization. It also helps applicants who have submitted an application but are stuck on identity, company details, D-U-N-S, or payment.

Last updated for the 2026 enrollment cycle; checked against Apple’s enrollment, account, and D-U-N-S guidance and the D-U-N-S provider’s lookup and application pages. Requirements, payment options, and displayed charges can vary by country or region.

1Before you start: choose the applicant, not the account you prefer

Your enrollment choice determines whose identity Apple checks and what name customers may see as the app provider. Pick based on the real publishing entity—not on which option looks faster or seems to require less paperwork.

An individual application is for a person enrolling in their own name. Apple’s enrollment guidance sets an age requirement of 18 or the age of majority in the applicant’s jurisdiction, whichever applies. Confirm the applicable rule in Apple’s Program Enrollment requirements before applying. If you publish as an individual, expect the account’s public provider identity to be associated with your personal name.

An organization application is for a legal entity, such as a company or other eligible organization. Apple needs to verify that the entity exists and that you have authority to bind it to the program. The organization’s legal name—not a product name, trading style, or informal team name—must match the supporting records. Apple may also ask for a D-U-N-S Number to identify the entity.

Gather your materials before starting:

• Your Apple Account and access to its verification methods.
• The applicant’s legal name and reliable contact details.
• For an organization, the exact registered legal name, address, website if requested, and the details of the person authorized to enroll.
• Any existing D-U-N-S record or the organization’s information needed to look one up.
• A payment method that the application flow accepts in your region.

Check spelling, punctuation, address formatting, and contact details across your records. A name mismatch between the application and the organization’s D-U-N-S record can lead to additional review. A personal email address is not automatically a problem, but the contact information must be accessible and accurate. Do not use an employee’s details as the legal organization name or submit an assumed company address.

2Individual or organization: how does the account choice change?

The relevant difference is not simply whether you work alone or with colleagues. It is whether you are publishing as yourself or on behalf of an eligible legal entity.

Apple’s individual and organization enrollment guidance is the authority for eligibility. Team roles, account controls, and interface labels can change, so confirm the details shown in your account rather than relying on an old screenshot or a coworker’s previous enrollment.

Choose an individual account if you are the publisher and want your personal identity associated with the account. Choose an organization account when the app belongs to a company or eligible entity and that entity should be the publisher. If you are employed by a company but the application is intended to be published by that company, applying personally can create a mismatch between the legal owner and the account holder. Resolve that question before enrolling; changing the publishing arrangement later may involve extra account administration.

3First milestone: prepare records and check D-U-N-S

Does an organization need a D-U-N-S Number?

Apple’s organization enrollment guidance says an organization may need a D-U-N-S Number for identity verification. That does not mean every applicant needs one: the requirement depends on whether you are enrolling as an organization, the entity, and the circumstances shown in Apple’s application. Individuals should not apply for an organization identifier just because they are registering for the program.

Before requesting a number, check whether the organization already has a record. Search using the legal name and address, including known variations in spelling or business-unit naming. Use the official D-U-N-S lookup, then compare the result against the organization’s authoritative registration details.

If the record is missing or incorrect, follow the D-U-N-S provider’s current application process. The application may ask for organization details that should match the legal records. Availability, processing, and required information can depend on location and case; do not treat another company’s experience or an old estimate as a guaranteed timeline.

Before you submit an Apple application, check the following:

• The legal entity name matches the organization’s official record.
• The D-U-N-S record refers to the right entity and location.
• The address and country or region match the supporting documentation.
• The representative’s name and contact information are current.
• The person applying has authority to enroll the organization.

If the company operates under a brand name different from its registered name, use the legal name wherever Apple asks for the organization’s legal identity. A website or trading name can help describe the organization, but it does not replace the legal entity record.

4Second milestone: submit the application in the right order

The exact screens can vary by region and account status. Use Apple’s developer registration entry point and follow the current application prompts; avoid treating the labels or sequence in a third-party walkthrough as fixed.

1. Sign in with your Apple Account. Start from Apple’s registration page and use the account you intend to keep connected to the membership. Make sure you can receive verification messages and complete any security checks requested.
2. Choose the applicant type. Select the individual path if you are enrolling yourself. Select the organization path only if the legal entity meets Apple’s criteria and you are authorized to act for it.
3. Enter identity and contact details. Use your legal personal details for an individual application. For an organization, provide the organization’s legal name and the authorized representative’s information as requested.
4. Complete the verification steps shown. Apple may ask for additional identity or organization verification. The in-app enrollment guidance explains that verification steps can form part of the process. Follow the instructions actually displayed for your account and region.
5. Review all submitted information. Compare the entered details with your identification or the organization’s records. Recheck spelling and contact channels before submitting.
6. Review the live payment screen. Confirm the displayed charge, currency, applicable tax information, and available payment methods for your region. Proceed only when those details are clear.
7. Save the confirmation and monitor the account. Keep any application reference or confirmation message. Check the account status and email for a request or next step; do not infer approval solely from a payment attempt.

An individual applicant may see identity prompts that do not appear in the same form for an organization. An organization applicant may see questions related to the entity or its representative. Do not assume that a missing field means a requirement was waived; the live application and Apple support instructions determine what is required for that case.

5Third milestone: confirm fees and payment before you submit

Membership charges are time- and region-sensitive. Apple’s enrollment pages have historically listed an annual membership price of US$99, but the amount, currency, tax treatment, and payment options shown to you can vary by territory and may change. Treat the price displayed during your own application as decisive, and verify it against Apple’s current membership guidance. Do not budget from an old invoice or assume that a displayed US-dollar amount applies in another country.

Check the payment page for the applicant’s region, currency, tax, and accepted payment methods. A payment card that works for ordinary online purchases may still be rejected if the billing details do not match, the issuer blocks the transaction, or Apple does not accept that method for the selected region. The application screen’s instructions take priority over general advice.

If payment fails, record the exact message and check these causes first:

• The billing name or address differs from the payment account’s records.
• The payment method is not available for the region shown in the application.
• The issuer declined the transaction or requires a separate authorization.
• The account is still waiting for identity or organization verification.
• A previous attempt is pending, so starting another payment could create confusion.

Do not keep retrying without checking the status. Confirm whether the application or transaction is pending, then follow Apple’s prompt or contact the relevant support channel. If the payment screen’s country or currency looks wrong, stop and correct the account or application details before paying.

6Fourth milestone: resolve delays without creating duplicate records

After submitting, judge progress from the confirmation email, account status, and any verification request—not from an assumed review duration. Apple does not provide a universal completion time that applies to every applicant and region, so avoid making plans around a fixed number of days.

For an identity hold, check that the person named in the application can complete the requested verification and that the submitted details match the identity records. For an organization hold, compare the legal name, location, and D-U-N-S information exactly. If the organization’s record is wrong, resolve it through the record provider before repeatedly resubmitting the same inconsistent details to Apple.

For a payment hold, confirm whether Apple received the payment, whether the charge is pending or declined, and whether the account still needs verification. Keep the original message and application details when contacting support. Avoid creating another Apple Account or opening a duplicate application as a workaround unless Apple specifically directs you to do so.

If you need to correct account details after enrollment, use Apple’s account information update guidance. Some changes may require additional verification, and not every legal-entity change is a simple profile edit. Check the instructions for the specific change before modifying the account.

7Your pre-submit checklist

Complete the items that match your application type. If an item is uncertain, resolve it before submitting rather than guessing and trying to repair the application later.

• [ ] I have selected the actual publisher: myself or an eligible organization.
• [ ] My Apple Account is accessible, and I can complete its verification prompts.
• [ ] My legal name and contact details match the records required for my application type.
• [ ] If I am applying for an organization, I have authority to enroll it.
• [ ] I have checked whether the organization already has a D-U-N-S record.
• [ ] The legal name and address in the organization record match the application details.
• [ ] I have reviewed the payment amount, currency, tax, and accepted method shown for my region.
• [ ] I have saved the confirmation and know where to check application status.
• [ ] I will follow the exact error or verification instruction instead of submitting a duplicate application.

Once enrollment is complete, the account is only one part of getting an iOS app ready. You still need a suitable Mac-based build environment for compiling, signing, and packaging the app. If you are mapping that next stage, browse the vpstix English development resources and compare the available vpstix options with your actual build schedule.

A Mac environment is not automatically the right choice for every team: buying a Mac can make sense for continuous, long-term local work, while a non-Mac workflow may be adequate for tasks that do not require Apple-platform builds. Those alternatives can also mean upfront hardware expense, limited access to macOS build tools, or extra setup and maintenance. If you only need a Mac temporarily for an iOS build, packaging, or release check, assess whether renting through vpstix fits that short-term workload; if you need continuous heavy use or physical peripherals, owning and operating a dedicated Mac may be the better fit.