Skip to main content
Pricing, subscriptions, and availability Level: Beginner 12 min read

Apple Paid Applications Agreement: Banking, Tax, and Legal Requirements

The complete guide to accepting Apple's Paid Applications Agreement, configuring banking details and tax forms (W-9 / W-8BEN), and understanding what requires Apple's web portal vs. FlightDeck MCP.

Published: 2026-11-03 • Last Updated: 2026-11-03 • Author: Kip Lawrence
Key MCP Tools: app_price_schedule_getapp_store_versions_listrelease_readiness_check

Overview: The Financial Gateway to the App Store

Developing an iOS or macOS application with in-app purchases (IAP), auto-renewable subscriptions, or an upfront price tag is only half the battle. Before Apple will distribute a paid product, process customer credit cards, or disburse monthly revenue into your business checking account, your developer organization must complete Apple's mandatory financial onboarding.

This process centers around the Paid Applications Agreement (Schedule 2 of the Apple Developer Program License Agreement).

While free applications require only the standard Free Applications Agreement, any app charging even \$0.99 or offering a single consumable digital item is strictly blocked by App Store Connect until the Paid Applications Agreement is executed, banking information is validated, and tax withholding certifications are approved.

TEXT
┌────────────────────────────────────────────────────────────────────────┐
│                   APPLE DEVELOPER AGREEMENTS TAXONOMY                  │
├───────────────────────────────┬───────────────────┬────────────────────┤
│ Agreement Tier                │ Requirements      │ Monetization Scope │
├───────────────────────────────┼───────────────────┼────────────────────┤
│ Free Applications Agreement   │ Standard DPLA     │ 100% Free Apps     │
│ (Active by Default)           │ Zero Banking      │ Zero In-App Items  │
│                               │ Zero Tax Forms    │ Zero Subscriptions │
├───────────────────────────────┼───────────────────┼────────────────────┤
│ Paid Applications Agreement   │ Schedule 2 Signed │ Upfront Paid Apps  │
│ (Action Required)             │ Legal Bank Account│ In-App Purchases   │
│                               │ W-9 or W-8BEN Tax │ Auto-Renewable Subs│
└───────────────────────────────┴───────────────────┴────────────────────┘

Crucially, developers and AI coding assistants must understand the hard boundaries of automation: Apple provides zero public REST API endpoints for entering bank account numbers, accepting legal schedules, or submitting tax forms. All financial contracts must be executed manually by the Account Holder inside Apple's authenticated web portal.


The Primary Monetization Readiness Prompt

Use this prompt with your AI coding assistant (Cursor, Claude Code, Windsurf, or Roo Code) to audit your application's pricing schedule and confirm whether your submission is gated by missing financial prerequisites:

TEXT
Inspect my app [Your App Name] in App Store Connect. Check the current price schedule, list any configured in-app purchases or subscriptions, and run a release readiness audit to identify whether my release is blocked by missing legal agreements or unconfigured price points. Do not request or display any bank account numbers or tax identification numbers.

The Three Pillars of Financial Onboarding

Monetizing on the App Store requires completing three distinct administrative pillars in App Store Connect under the Business module (formerly Agreements, Tax, and Banking):

  • Account Holder Exclusivity: Only the user holding the Account Holder role can view, review, and accept the Paid Applications Agreement. Users holding Admin, Finance, or App Manager roles cannot legally bind the organization and will see the agreement greyed out with "View Only" or "Action Required by Account Holder".
  • Agreement Re-Acceptance: Apple updates Schedule 2 periodically (often following WWDC or international regulatory adjustments such as EU Digital Markets Act requirements). When a new version is posted, the agreement transitions to an expired or pending state. Failure to accept within the grace period will freeze app updates and halt payouts.

2. Banking Configuration

To receive electronic fund transfers (EFT) or wire disbursements, you must configure banking information in App Store Connect:

  • Role Permissions: In Organization accounts, users holding the Account Holder, Admin, or Finance role can view, enter, and update banking information. In Individual developer accounts, only the Account Holder can configure banking.
  • Bank Account Holder Name: Must match the exact legal entity name (for organizations) or legal name (for individual accounts) registered with Apple Developer Program. Discrepancies between your Apple entity and your commercial bank account cause wire rejections.
  • Routing & Clearing Identifiers: 9-digit ABA Routing Transit Number for US banks; Sort Code for the UK; Bank Code / Branch Code for Japan; Transit / Institution numbers for Canada.
  • IBAN and SWIFT/BIC: Mandatory for European and international cross-border disbursements.
  • Account Verification: Apple verifies bank accounts through automated format validation (checking routing number algorithms, BIC directories, and IBAN structures) and legal entity name matching. Apple does not utilize micro-deposit verification cycles.
  • Account Currency: Disbursements are typically remitted in your local currency or US Dollars depending on your banking territory.

3. Tax Certification Forms

Apple is a registered marketplace merchant and must comply with international tax laws, including United States Internal Revenue Code Chapter 3 and Chapter 61:

  • Role Permissions: In Organization accounts, users with the Account Holder, Admin, or Finance role can complete, certify, and submit electronic tax documentation.
  • US Developers (Form W-9): US citizens, residents, LLCs, and corporations must provide their legal name, federal tax classification, and Social Security Number (SSN) or Employer Identification Number (EIN).
  • Non-US Developers (Form W-8BEN / W-8BEN-E): Foreign individuals (W-8BEN) and foreign entities (W-8BEN-E) certify foreign status and claim Tax Treaty Benefits under bilateral treaties with the United States. Without an approved W-8 form, Apple is legally required by the IRS to withhold 30% of US sales proceeds at the source.
  • Territory-Specific Tax Schedules: Depending on where you sell, supplementary questionnaires may appear for Australia GST, Canada GST/HST/QST, Japan JCT, or Mexico VAT.

What FlightDeck Can and Cannot Do

Understanding what an AI assistant can manage through FlightDeck MCP protects both your security and your time:

What FlightDeck MCP Can Do

  1. Audit Current Price Schedules: Call app_price_schedule_get to inspect your active base territory pricing and verify whether the app is currently free or priced.
  2. Inspect Version & Readiness States: Call release_readiness_check and app_store_versions_list to detect submission blockers before queuing builds for review.
  3. Stage Price Updates: When the Paid Applications Agreement is active, stage new base price schedules via app_price_schedule_set with human-in-the-loop desktop confirmation.
  4. Surface Missing Requirement Warnings: Identify when an in-app purchase cannot be submitted because the version has no selected pricing tier.

What Must Be Done in Apple's Web Portal (Manual Only)

  1. Executing the Paid Applications Contract: Apple provides no API to accept Schedule 2. The Account Holder must physically log into App Store Connect > Business and click Accept.
  2. Entering Bank Credentials: Apple exposes zero REST endpoints for bank routing or account entry.
  3. Submitting Tax Identification: W-9 and W-8BEN forms are collected through Apple's secure web wizard.

[!CAUTION] Strict Financial Safety Mandate: Never paste bank routing numbers, account numbers, Social Security Numbers (SSN), Employer Identification Numbers (EIN), or foreign tax numbers into an AI assistant, prompt, or local script. FlightDeck does not accept, store, or transmit financial credentials.


Step-by-Step Workflow: Activating Paid Applications

Follow this end-to-end procedure to clear all legal blockers before submitting your paid app:

TEXT
┌────────────────────────────────────────────────────────────────────────┐
│                   PAID APPLICATIONS ONBOARDING WORKFLOW                │
│                                                                        │
│   1. ACCOUNT HOLDER SIGNS IN TO APP STORE CONNECT                      │
│   [Navigate to 'Business' module in the primary dashboard]             │
│                            │                                           │
│                            ▼                                           │
│   2. REVIEW & ACCEPT PAID APPLICATIONS AGREEMENT                       │
│   [Review Schedule 2 terms; click 'Agree']                             │
│                            │                                           │
│                            ▼                                           │
│   3. CONFIGURE BANK ACCOUNT INFORMATION                                │
│   [Enter routing/SWIFT, account number, currency, matching name]       │
│                            │                                           │
│                            ▼                                           │
│   4. SUBMIT TAX FORMS (W-9 OR W-8BEN)                                  │
│   [Complete IRS disclosure; claim tax treaty benefits if non-US]       │
│                            │                                           │
│                            ▼                                           │
│   5. AUDIT READINESS VIA FLIGHTDECK MCP                                │
│   [Run release_readiness_check to confirm submission unblocked]        │
└────────────────────────────────────────────────────────────────────────┘

Step 1: Access the Business Module

  1. Have the organization's Account Holder sign into App Store Connect.
  2. On the main dashboard, select Business (or Agreements, Tax, and Banking).
  3. Under the Agreements tab, locate Paid Applications.
  4. If the status is Action Required, click View and Agree to Terms.
  5. Scroll through the legal agreement and click Agree.

Step 2: Set Up Banking Information

  1. On the same page, locate the Banking section.
  2. Click Add Bank Account (or select an existing verified account).
  3. Select your bank's country or region.
  4. Search for your bank by name, SWIFT/BIC code, or routing number.
  5. Enter the exact Account Holder Name registered with your banking institution.
  6. Enter the IBAN or Account Number.
  7. Confirm that the account currency matches your local receiving requirements.
  8. Save. Apple will perform automated routing validation (typically takes 24–48 hours).

Step 3: Complete Tax Forms

  1. Under the Tax section, click Set Up Tax.
  2. Select United States Tax Forms.
  3. Answer the preliminary questions regarding US taxpayer status.
  4. For US entities, complete the electronic Form W-9.
  5. For non-US entities or developers, complete the electronic Form W-8BEN or W-8BEN-E: - Provide your official foreign registered address. - Enter your Foreign Tax Identifying Number (TIN) provided by your home country. - Select your country from the Tax Treaty dropdown to claim the reduced withholding rate (typically 0% for software royalties under most US tax treaties). - Sign electronically using your full legal name.

Step 4: Verify Readiness with FlightDeck MCP

Once Apple transitions your agreement status to Active, return to your IDE and have your AI coding assistant verify that pricing and readiness gates are clear:

TEXT
Run a release readiness check on [Your App Name]. Inspect the price schedule to confirm whether the app has an active base territory price assigned. Confirm that the version state is ready for review submission.

Payout Realities: Thresholds and Payment Cycles

Even after your agreements are active and sales begin flowing, keep these fiscal mechanics in mind:

  1. Fiscal Month vs. Calendar Month: Apple operates on a 4-5-4 fiscal calendar. Financial reports and remittances close on fiscal dates, not standard calendar month-ends.
  2. Disbursement Timing: Payments are delivered via wire or direct deposit approximately 33 days after the close of Apple's fiscal month. For example, proceeds earned during the October fiscal month are remitted in early December.
  3. Minimum Payout Threshold: Apple imposes minimum disbursement thresholds (typically \$10 USD for direct deposit in major currencies, and up to \$150 USD for international wire transfers). If your net proceeds do not meet the threshold, Apple carries the balance forward to the next fiscal cycle.
  4. Currency Conversions: Apple handles currency conversion from the customer's purchase currency into your designated bank currency using prevailing bank exchange rates at the time of settlement.

Common Errors & Troubleshooting

1. Agreement Status: Action Required / Pending User Info

  • Cause: A revised Schedule 2 has been released by Apple, or banking information failed automated validation.
  • Fix: The Account Holder must log into App Store Connect web portal, review the highlighted red banner in the Business section, and complete the missing requirement.

2. Submission Rejected: No Price Tier Selected for In-App Purchase

  • Cause: An In-App Purchase product was created in draft, but no base price point or territory availability was configured.
  • Fix: In App Store Connect, open the IAP product, select Subscription Prices or In-App Purchase Pricing, and designate a base price schedule before attaching the item to a review submission.

3. 30% US Withholding Tax Deducted from Remittance

  • Cause: Non-US developer failed to submit Form W-8BEN or omitted the Tax Treaty declaration, forcing Apple to apply standard US statutory backup withholding.
  • Fix: Log into App Store Connect > Business > Tax, update Form W-8BEN with a valid Foreign Tax ID, and claim the applicable bilateral treaty benefit. Note that tax adjustments are prospective and cannot be refunded by Apple retroactively.


Official References


Evidence Limitations & Verifications

  • L1 Official Documentation Verification: Inspection of Apple Developer documentation and App Store Connect Help confirms role requirements: only the Account Holder can accept legal agreements, while Account Holder, Admin, and Finance roles can manage banking and tax forms.
  • L2 API Specification Verification: Inspection of Apple's App Store Connect REST API schema (openapi.oas.json) confirms that Apple provides zero endpoints for bank account entry, tax certification, or legal contract execution.
  • Financial Simulation & Legal Notice: FlightDeck MCP tools (app_price_schedule_get, release_readiness_check) evaluate structural metadata; they do not process, store, or simulate live financial disbursements or bank routing numbers. This guide documents Apple platform operational prerequisites and does not constitute formal legal, accounting, or tax advice.

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store