Reviewed on: 2026-06-12.
A held payout is almost always one specific flag, and each flag has its own fix. Find your reason in this table first; everything else in this guide hangs off it.
| Hold reason shown in the console | Who fixes it | Remedy | Typical clearing time |
|---|---|---|---|
| Tax form incomplete or mismatched | You | Complete the tax profile so the legal name matches PAN and bank records exactly; take CA advice before certifying | Next payout cycle after correction |
| Bank account unverified or rejected | You + your bank | Re-enter account holder name, account number, IFSC and SWIFT character for character; re-trigger verification | A few days to one cycle |
| Balance below minimum payout threshold | Nobody | Wait; the balance carries forward until it crosses the threshold shown in the console | Automatic |
| Identity or payment-profile verification pending | You | Upload the exact ID documents requested; match the developer account legal name | Days to weeks |
| Policy or suspected-fraud flag | Platform | File the formal appeal answering each cited clause; ask in writing whether earned balances will be released | Weeks; depends on appeal |
| Inward remittance returned by your Indian bank | Your bank | Get the purpose code and document list in writing from the bank's forex desk; ask the platform to re-attempt | One to two cycles |
Two facts anchor everything. Apple and Google are private companies operating under their developer agreements, so no Indian regulator can simply order a payout released, and RTI does not apply to them. And money in a verification hold is parked, not confiscated; fixing the named flag releases it in the normal cycle.
Two-person studio Pixelvine LLP in Indore had a Google Play balance of USD 2,340 (about Rs 1.95 lakh) held in February 2026 with the status “payments on hold: verify your payments profile”. The trigger: the payments profile said “Pixelvine”, while the PAN and current account said “Pixelvine LLP”. They corrected the legal name, uploaded the LLP deed and PAN as requested, and the profile verified in six days. The held balance paid out in the next monthly cycle, on the regular payout date, with no support ticket needed. Repeat tickets before fixing the name mismatch would have changed nothing, because support cannot override a failed verification.
When the console shows no actionable reason, or the flag is fixed and the hold persists past a full cycle, escalate within the platform. This is the primary route, ahead of any government forum.
Keep every ticket number; one clean thread beats five fresh tickets.
Exactly two Indian authorities can ever step in, and each has a narrow gate.
MSME Samadhaan, only if you are a registered MSME. If your studio or firm holds Udyam registration, the MSMED Act treats payment due from a buyer of your goods or services as delayed after 45 days, and you can file a delayed-payment case on samadhaan.msme.gov.in against the Indian contracting entity named in your developer agreement. This route suits clear, undisputed earned balances, and it moves through the state MSE Facilitation Council, which can take months. It is not available to unregistered individual developers, and it cannot resolve a policy dispute about whether the money is owed at all.
RBI, only for payment-aggregator issues. RBI regulates banks and payment aggregators in India. If the actual failure is on the Indian payments leg, for example your bank or an RBI-authorised aggregator mishandling the inward credit, a complaint on the RBI complaint management system at cms.rbi.org.in is in scope. RBI has no jurisdiction over Apple's or Google's decision to hold a developer balance, and a complaint against the platform itself gets closed as outside scope.
And the RTI question, since this site is about RTI: the RTI Act reaches public authorities only. You cannot RTI Apple or Google. RTI is useful at the edges, for example to a public sector bank about how your inward remittance was handled, or to track a CPGRAMS or MSEFC file. See how to file RTI online if one of those edges applies; the appeal path is at first and second appeals.
Platform payouts arrive as inward foreign remittances, and Indian banks process them under FEMA with a purpose code. If a credit bounces, write to your bank's trade or forex desk and ask for three things in writing: the return reason, the purpose code they expect for software or app revenue, and whether they need an invoice before issuing the FIRA or FIRC. A KYC-frozen account will also block the credit; if that is your situation, clear it first using the bank KYC-freeze guide. Keep the FIRC, because it anchors your export-of-services position for GST and your income tax return. Exporters who also ship physical goods will recognise this purpose-code discipline from AD code registration at the port.
Verification holds usually clear within one or two payout cycles once the flag is fixed. Policy-investigation holds follow the developer agreement and can run longer; the agreement, not Indian statute, sets the timeline.
Not automatically. Both platforms' terms distinguish account action from settled earnings, less refunds, chargebacks and amounts tied to the violation. File the appeal and ask in writing for the payout date of the undisputed balance.
No. The delayed-payment remedy is for registered MSMEs. Individuals can consider Udyam registration for the future, but it does not apply retrospectively to a dispute already running.
You are a business counterparty under a developer agreement, not a consumer of the payout service, so consumer forums are generally a poor fit. For a clearly earned, refused balance, a civil route on legal advice is the realistic backstop.
It depends on turnover and supply type, and app revenue routed through the platforms has specific treatment. Confirm with a chartered accountant; do not improvise on the platform tax form.
No. Platform support works off the flag in their system. A precise ticket naming the flag, the fix you applied, and the documents attached is what shortens the queue.
Download the developer payout-hold checklist (PDF).