App Store or Play Store Developer Payout Held? Action Guide

Who this guide is for

This guide is for India-based developers, studios, and small companies that publish on the Apple App Store or Google Play and have found their developer payout held, delayed, or blocked. It applies whether you are an individual developer, a registered firm, or a company, and whether the earnings come from paid apps, in-app purchases, subscriptions, or ad revenue routed through the platform.

It is especially useful if you are in one of these situations:

• Your earnings report shows a balance, but the payout status reads "on hold", "pending", or "action required".
• The platform is asking for a tax form, tax identification, or W-8 style declaration you do not fully understand.
• Your bank rejected or returned the inward foreign remittance, or the credit is parked pending documents.
• You received a policy-violation or account-verification notice and your balance was frozen at the same time.
• Your account was suspended or terminated and you want to know whether the earned balance will still be paid.

This is a private-platform dispute. Apple and Google operate under their own developer agreements, not under an Indian payout statute. So the centre of gravity here is fixing the platform-side flag and escalating cleanly — with tax and foreign-exchange compliance handled correctly so the money can actually land in your Indian bank account.

What you can do this weekend

Friday evening

Log in to your developer console — App Store Connect for Apple or the Google Play Console for Android. Go to the payments, payouts, or financial reports area. Find the exact status line on your payout and read it word for word. The console almost always names the trigger: tax form incomplete, bank account unverified, identity verification pending, balance below threshold, or a policy or compliance hold.

Take dated screenshots of the on-hold status, the held amount, the payout cycle, and any reason text. Download your latest earnings or payout report. This is your evidence baseline. Also open the email inbox linked to the developer account and search for any verification, tax, or policy messages from the platform — the most specific instructions are often there, not in the console.

Write down which single trigger applies. If more than one is flagged, list them in order. You will fix them one at a time over the weekend.

Saturday

Work through the trigger you identified. If it is a tax form, open the tax section of your payment profile and check every field: legal name, tax residency, PAN or tax identification, and any treaty declaration. The name must match your PAN and bank records exactly. Do not certify a tax form you do not understand — note the questions and confirm the GST and income tax treatment with a chartered accountant before you submit.

If it is a bank verification issue, compare your payment profile against your actual bank passbook or statement header. Check the account holder name, account number, IFSC, SWIFT or routing details, and account currency. A single mismatched character can cause a rejection. Correct anything that differs, and keep a cancelled cheque or statement header ready as proof.

If your bank returned or parked the inward remittance, contact your bank's trade or forex desk in writing. Ask for the precise reason, the purpose code they expect for software or app revenue, and whether they need a Foreign Inward Remittance Certificate or an invoice from you. This is a foreign-exchange matter under FEMA, so getting the bank's exact requirement in writing saves repeated failed credits.

Sunday

If the hold is a policy or compliance flag, read the violation notice carefully and map each cited clause to evidence you can produce. Draft your appeal addressing every point, not a general protest. Keep earned revenue and account status as separate questions — ask explicitly whether undisputed earned balances will be released even if other action continues.

Assemble your full evidence bundle in order: developer account ID, payout ledger, on-hold screenshots, tax forms as submitted, bank proof, PAN, and any notices. Then submit the platform's support request or appeal through the official console channel and save the case or ticket number. If you are mid-fix on tax or FEMA points, get a short paid consultation with a CA before you certify anything. A clean, professional first submission usually resolves faster than several rushed ones.

Documents and evidence checklist

Step-by-step action plan

Step 1 — Read the exact reason in your developer console

Do not contact support before you know the trigger. Log in to App Store Connect or the Google Play Console, open the payments or payouts section, and read the status line precisely. The platform almost always states the reason: tax form incomplete, bank account unverified, identity check pending, balance below the minimum payout threshold, or a policy or compliance hold. Capture a dated screenshot and download your earnings report so you have the held amount and cycle on record.

Step 2 — Fix the tax form correctly

A surprising share of held payouts are simply an incomplete or mismatched tax declaration. Open the tax section of your payment profile and verify your legal name, tax residency, PAN or tax identification, and any treaty fields. The name must match your PAN and your bank account holder name. Where the platform asks you to certify your tax status, do not guess. The GST and income tax treatment of app and software revenue can vary with your turnover and structure, so have a chartered accountant confirm the position and the correct declarations before you submit. Certifying a wrong tax form can cause withholding or a fresh hold.

Step 3 — Verify and match your bank account

Compare the bank details in your payment profile against your actual bank records, field by field: account holder name, account number, IFSC, SWIFT or routing code, and account currency. Even one wrong character can make the platform reject the account or your bank bounce the credit. Correct any mismatch, save, and keep a cancelled cheque or statement header ready. If the platform supports re-verification, trigger it and wait for the verified status before expecting a payout.

Step 4 — Sort out the inward foreign remittance with your bank

Payouts from Apple or Google arrive as an inward foreign remittance, which your bank must process under FEMA rules with the correct purpose code. If a credit was returned or is parked, write to your bank's trade or forex desk. Ask for: the exact reason for the return, the purpose code they expect for software or app revenue, and whether they need an invoice or will issue a Foreign Inward Remittance Certificate. Resolve this before re-attempting the payout, otherwise the money may bounce again. For a related foreign-credit scenario, see our guide on an inward foreign remittance held by your bank.

Step 5 — Clear the payout threshold and cycle

Sometimes nothing is wrong at all — your balance has simply not crossed the platform's minimum payout threshold, or the next payout cycle has not arrived. Check the stated threshold and the payout schedule in the console. If you are below it, the balance carries forward and pays out once it crosses. Confirm this is the case before raising a support ticket, so you do not chase a "problem" that is just the normal schedule.

Step 6 — Handle a policy or compliance hold properly

If the hold is tied to a policy-violation or account-verification notice, treat it as two separate questions: the account action and the earned money. Read the notice and map each cited clause to evidence. Draft a factual appeal addressing every point — not a general complaint — and file it within any stated window through the official appeal channel. In the same submission, ask explicitly whether undisputed earned balances, net of refunds and chargebacks, will be released and on what timeline. Keep copies of everything.

Step 7 — Escalate inside the platform with a clean record

If support gives no substantive answer, escalate within the platform's own channels: a follow-up on the same ticket, the developer support contact form, and any senior or specialist queue the platform offers. Quote your account ID, the held amount, the cycle, and your earlier ticket numbers every time. Be specific about the outcome you want — release of the verified payout — and the date by which you expect a response. A calm, well-documented escalation is far more effective than repeated angry messages.

Step 8 — Take professional or legal advice if the money is clearly earned and withheld

If the platform keeps a clearly earned balance, gives no coherent reason, and exhausts your appeals, consider professional advice. A chartered accountant can confirm the tax and FEMA position so nothing on your side blocks the credit. A lawyer can assess whether, on your specific facts, a consumer or civil route is available, since the developer agreement governs your relationship. Where a public authority such as your bank or the tax department holds relevant records, RTI can help you gather documents — see the RTI section below.

Escalation ladder

Copy-paste support template

Replace the text in square brackets with your own details before sending.

When RTI can help

The Right to Information Act, 2005 applies only to public authorities. Apple and Google are private companies, so RTI cannot be used directly against them or their developer payment systems. However, a held payout often touches Indian public authorities at the edges, and RTI can help you gather records from those bodies to support your case:

• Public sector bank records: If your payout was returned or parked by a public sector (government-owned) bank, you can file an RTI with that bank's Central Public Information Officer asking for the policy or reason recorded for handling your inward remittance, and the purpose-code requirement applied to your credit. Private banks are generally outside RTI, so use their internal grievance route instead.
• Income tax records: If a tax question is blocking your declaration, RTI to the income tax department can help you obtain copies of your own filed records or the status of a grievance you raised, so your tax form to the platform is accurate.
• Grievance handling by a regulator: If you have filed a complaint with a payments or foreign-exchange regulator and it is not moving, RTI can be used to ask how that complaint was processed and what action was taken.

To file an RTI online with a central public authority, see our step-by-step RTI filing guide. The standard fee for central government authorities is the prescribed amount, and the CPIO must respond within 30 days. If you get no reply or an unsatisfactory one, our guide on the RTI first appeal under Section 19 explains the next step, and the full first and second appeal guide covers escalation to the Information Commission. For deeper strategy, The RTI Playbook covers using RTI in complex disputes.

When RTI will not help

RTI has clear limits in a developer-payout dispute:

• RTI cannot release your payout: No Information Commission can order Apple or Google to pay you. The release route is the platform's own appeal and support process, and ultimately the developer agreement and any consumer or civil remedy.
• No access to platform internals: RTI cannot get you Apple's or Google's internal account notes, fraud-scoring logic, or policy-decision records, because they are private bodies.
• Private bank and private platform decisions: If your bank is a private bank, RTI does not apply; use its grievance cell and, if needed, the banking ombudsman scheme. For tax and FEMA correctness, a chartered accountant is faster and more useful than an RTI.

Common mistakes to avoid

• Assuming the money is gone: A held payout is usually parked behind a fixable flag, not confiscated. Find the trigger and fix it instead of panicking or writing it off.
• Contacting support before reading the reason: Support cannot help efficiently if you do not know whether it is a tax, bank, threshold, or policy hold. Read the console first.
• Certifying a tax form you do not understand: Wrong tax declarations cause withholding and fresh holds. Confirm the GST and income tax position with a CA before you certify anything.
• Name and bank mismatches: If the account holder name, PAN name, and tax form name do not match, payouts fail. Make all three identical, character for character.
• Ignoring FEMA and purpose codes: Foreign payouts must arrive with the correct purpose code. Skipping this gets the credit returned. Confirm the requirement with your bank in writing.
• Treating an appeal as a rant: A general complaint gets a templated reply. Address each cited clause with evidence, and ask specifically for release of undisputed earned balances.
• Confusing account action with earned money: Even if an account is suspended, earned revenue is a separate question. Always ask in writing what happens to the balance.
• Expecting RTI to release the payout: RTI only gets records from public authorities. It supports your case; it does not compel Apple or Google to pay.

For related platform and online-business disputes, see our guides on a marketplace seller payment held on Amazon, Flipkart or Meesho, an e-commerce account blocked with a wallet or gift-card balance, and an online course refund denied after a misleading promise. If you are dealing with in-app purchase refunds on the consumer side, see in-app purchase refunds and parental controls.