App Store

    How Long Does Apple Tax and Banking Review Take?

    App Store Connect Agreements, Tax, and Banking section showing a Pending status while tax forms and banking information are processed.

    Apple's tax and banking setup is usually processed quickly rather than sitting in a long review: accepting the Paid Apps agreement is immediate once every section is complete, and the tax and banking information is typically processed within about 24 hours, though some international accounts take longer. It is validation and processing, not a queued review with a fixed turnaround, so there is no guaranteed timeline. If your agreement stays Pending beyond a couple of days, the usual reason is an error in a tax form such as a W-8BEN rather than a slow queue, and correcting it is what moves you to Active.

    Short answer

    Tax and banking processing is usually a day or so, not a long review. Per Apple's tax information help, you complete a required US tax form, and non-US developers are routed to a W-8BEN, W-8BEN-E, or W-8ECI based on their answers, while banking processing is cited at around 24 hours. Per Apple's agreements status help, the agreement shows Active once everything is processed. There is no fixed guarantee, so treat about a day or two as typical, expect some international accounts to take longer, and if it stays Pending with correct forms, contact Apple's finance support.

    What the tax and banking review actually is

    The tax and banking step is not a review in the sense of a person evaluating your app; it is the process of completing and validating the Paid Apps agreement, your tax forms, and your bank details so you are eligible to sell. To offer paid apps or in-app purchases, you accept the Paid Apps agreement in App Store Connect and provide tax and banking information, and the system validates those inputs. The agreement moves to Active when all of it is complete and processed.

    Understanding it as validation, not a queued content review, sets the right expectation for timing. There is no reviewer working through a line of submissions here; there is a check that your forms are correct and your banking is processed. That means the main cause of a long wait is usually an incomplete or incorrect input rather than a backlog. So when people ask how long the review takes, the honest answer is that the processing is typically fast, and delays usually trace to a form that needs fixing rather than to a slow queue.

    Typical timing: how long it takes

    In typical cases, the whole setup completes within about a day, though there is no guaranteed turnaround. Accepting the Paid Apps agreement takes effect immediately once every required section, including tax and banking, is filled in. Tax form validation is usually quick, often within roughly 24 hours, and banking information is cited by Apple at around 24 hours to process. Put together, many accounts see the agreement reach Active within a day or two of completing everything correctly.

    Some accounts take longer, and international banking is the most common reason. Cross-border bank verification can extend beyond the 24-hour figure Apple shows, so a non-US account may wait several days even with correct forms. Treat about a day or two as the normal expectation, allow extra time for international banking, and remember that Apple does not promise a fixed time. The absence of a guarantee is why you judge your wait against a typical range rather than a hard deadline.

    W-8BEN and tax forms

    The tax form is the step that most often determines your timing, because an error there keeps the agreement Pending. Apple requires a US tax form for the Paid Apps agreement, and rather than choosing a form yourself, you answer a series of questions that route you to the right one: a W-9 for US persons, and a W-8BEN, W-8BEN-E, or W-8ECI for non-US individuals and entities. Completing the correct form accurately is what lets the validation pass.

    Common W-8BEN errors are what stall accounts. A name that does not match your other details, a missing or incorrect foreign tax identifying number, an incorrect treaty claim, or a mismatch between the individual form and an entity that should file the W-8BEN-E all cause the form to be rejected or held, leaving the agreement Pending. If your setup is not going Active, review the tax form first: confirm you filled the form the questions directed you to, that the name and tax identifiers are correct, and that any treaty benefit you claimed is valid for your country.

    Active versus Pending in timing terms

    For timing, the practical distinction is that Pending means something is still processing or incomplete, and Active means the setup is done and you can sell. A Pending status right after you submit is normal and usually clears as the tax and banking validation completes over the next day or so. Pending is only a concern when it persists well beyond the typical processing window, which points to an input that needs attention rather than to ongoing processing.

    So read your status against how long you have waited. Pending in the first day or two after completing everything is expected and calls for patience. Pending after several days, especially if you never see the tax or banking sections confirm, suggests a form error or an international banking delay rather than a normal queue. Active is the signal that processing finished and you are cleared to sell, and reaching it is the goal that the tax form and banking accuracy are working toward.

    Why it stays Pending longer than expected

    When Pending lasts longer than the typical day or two, the cause is usually a correctable input, not a slow reviewer. The most frequent reasons are a tax form with an error, banking details that did not validate, or an incomplete section you have not noticed. Because the process is validation rather than a queue, these do not resolve by waiting; they resolve by correcting the specific input, after which processing completes.

    International banking is the main exception where waiting is legitimate, since cross-border verification can simply take longer than 24 hours even when everything is correct. To tell the two apart, check whether each section, agreement, tax, and banking, shows as complete: if a section is flagged or incomplete, fix it, and if all sections are complete and you are on an international account, give it a few more days before concluding something is wrong. Persistent Pending with everything correct is the case for contacting support.

    Does correcting a form reset the timing?

    Correcting a tax or banking input restarts the validation of that input, but there is no queue position to lose, so fixing an error is the right move rather than something to avoid. Unlike an app review where resubmitting can send you to the back of a line, tax and banking processing revalidates the corrected information without a penalty, so an accurate resubmission is simply the path to Active. Leaving a known error in place to preserve a place in line would make no sense here, because there is no line.

    The practical rule is to correct any flagged or incorrect input promptly rather than waiting it out. If your tax form was rejected or your banking did not validate, updating it accurately is what lets the process finish. Do not repeatedly resubmit an unchanged form hoping the result differs; change what was wrong. Because a correction does not cost you time in a queue, addressing the error is always better than waiting on a status that will not clear on its own.

    Timing at a glance

    Seeing the steps and their typical timing together sets expectations. The table below lays them out.

    StepTypical timingNotes
    Accept Paid Apps agreementImmediateOnce every section is complete
    Tax form validationOften within about 24 hoursAn error keeps it Pending
    Banking processingAround 24 hours, longer for some internationalApple cites about 24 hours
    Reaching ActiveUsually within a day or twoNo guaranteed turnaround

    Read the table as typical, not promised: correct forms usually reach Active within a day or two, while an error or international banking extends it.

    When to wait versus escalate

    Matching your situation to the right move keeps you from escalating too early or waiting too long. The table below maps common cases.

    Your situationBest moveWhy
    Submitted within the last day or twoWaitProcessing is still normal
    Pending for days, a form shows an errorFix the formAn error blocks Active
    International banking, a few days inWait a bit longerCross-border verification takes longer
    Days past with all sections correctContact Apple finance supportA genuine stall

    Read your case against the guide. Only the last row calls for support; the middle rows call for fixing an input, and the first for patience.

    Use the wait to secure your build

    Because you cannot sell paid apps or in-app purchases until the agreement is Active, the setup wait is time you can spend on the app itself rather than refreshing the status. Whether processing takes a day or several, confirming your build is sound is a more productive use of the wait, especially since payment features often go hand in hand with sensitive data handling.

    A scanner like PTKD.com analyzes your build and reports issues such as insecure data storage, leaked keys, and over-broad permissions by severity, mapped to OWASP MASVS, so you can harden the app while the agreement processes. To be clear about the boundary: PTKD does not process your tax forms, verify your banking, or change your agreement status. It helps you use the wait to make sure the app you will sell is secure.

    What to take away

    • Tax and banking setup is validation, not a queued review, so it usually completes within about a day or two rather than sitting in a long line.
    • Accepting the Paid Apps agreement is immediate once all sections are complete, and tax and banking are cited by Apple at around 24 hours to process.
    • Non-US developers are routed to a W-8BEN, W-8BEN-E, or W-8ECI, and a tax form error is the most common reason the agreement stays Pending.
    • Pending in the first day or two is normal; persistent Pending usually means a form to fix or, for international accounts, longer banking verification.
    • Correcting an input carries no queue penalty, so fix errors promptly, and use the wait to secure your build with PTKD.com.
    • #tax and banking
    • #app store connect
    • #paid apps agreement
    • #w-8ben
    • #apple developer

    Frequently asked questions

    How long does Apple tax and banking review take?
    Usually about a day or two, not a long review. Accepting the Paid Apps agreement is immediate once every section is complete, tax form validation is often within roughly 24 hours, and banking is cited by Apple at around 24 hours, though some international accounts take longer. There is no guaranteed turnaround, so treat a day or two as typical, allow extra time for international banking, and judge your wait against that range rather than a hard deadline.
    Which tax form do I need, and does W-8BEN matter?
    Apple requires a US tax form for the Paid Apps agreement and routes you to the right one through a series of questions: a W-9 for US persons, and a W-8BEN, W-8BEN-E, or W-8ECI for non-US individuals and entities. The tax form most often determines your timing, since a W-8BEN error, a name mismatch, a missing foreign tax identifying number, or an incorrect treaty claim, keeps the agreement Pending until you correct it.
    What is the difference between Active and Pending?
    Pending means something is still processing or incomplete; Active means the setup is done and you can sell. Pending right after you submit is normal and usually clears within a day or so as tax and banking validation completes. Pending becomes a concern only when it persists well beyond the typical window, which points to an input that needs attention, such as a tax form error or, for international accounts, longer banking verification, rather than ongoing processing.
    Why is my agreement stuck on Pending?
    Usually a correctable input, not a slow reviewer: a tax form with an error, banking details that did not validate, or an incomplete section you have not noticed. Because the process is validation rather than a queue, these do not resolve by waiting; you fix the specific input. The main legitimate exception is international banking, where cross-border verification can take longer than 24 hours even when everything is correct. Check that every section shows complete.
    Does correcting a tax form reset my place in line?
    No, because there is no line. Correcting a tax or banking input revalidates that input without a queue penalty, unlike an app review where resubmitting can send you to the back. So fixing an error is always the right move rather than something to avoid. Do not repeatedly resubmit an unchanged form hoping for a different result; change what was wrong, and the process completes without costing you a place in any queue.
    What should I do while I wait for Active?
    Since you cannot sell paid apps or in-app purchases until the agreement is Active, use the setup wait on the app itself. A scanner like PTKD.com (https://ptkd.com) analyzes your build and reports insecure data storage, leaked keys, and over-broad permissions by severity, mapped to OWASP MASVS, which pairs well with adding payment features. It does not process your tax forms, verify banking, or change your agreement status, but it helps you make sure the app you will sell is secure.

    Keep reading

    Scan your app in minutes

    Upload an APK, AAB, or IPA. PTKD returns an OWASP-aligned report with copy-paste fixes.

    Try PTKD free