Food Delivery Partner Account Deactivated and Payout Withheld? Action Plan

Who this guide is for

This guide is for food and grocery delivery partners in India whose partner account has been blocked, suspended or deactivated, and whose earned weekly payout, incentives, or security deposit are now being held back. It applies whether you ride for Swiggy, Zomato, a quick-commerce app, or any similar aggregator. It is also useful for:

• Partners who got a sudden in-app message saying the account is deactivated for fraud, low ratings, or document issues, with no clear explanation.
• Riders whose weekly settlement did not arrive in their bank account and who cannot get a straight answer from support.
• Partners told their dues are "under review" for weeks while the account stays locked.
• Anyone who paid a deposit or bought a kit and wants it refunded after the account closed.

The relationship between you and the platform is set by the onboarding agreement and the payout policy you accepted when you signed up in the app. Read those terms first — they define when payouts are made, when an account can be deactivated, and what happens to pending dues. This guide does not give personalised legal advice; where the amount is large or the platform refuses to engage, consult a lawyer or a gig-worker union.

What you can do this weekend

Friday evening

Open the partner app while you still have access. Take screenshots of everything that matters: the deactivation notice on the home screen, your current earnings balance, the pending payout amount, and your weekly statement history. Apps sometimes log you out fully after deactivation, so capture this now.

Find the deactivation message and read the exact words. It usually states a broad category — suspected fraud, customer complaints, low acceptance or ratings, fake GPS, or expired documents. Note the date the account was deactivated and the date your last successful payout was credited.

Locate your onboarding agreement and payout policy. These may be in the app under a "Documents", "Agreement", or "Help" section, or in the welcome email you received when you joined. Save them as PDFs or screenshots. You will need the payout clause to show the dues are contractual.

Saturday

Build your money trail. List every week with unpaid earnings, the amount, and the trips behind it. Match the in-app trip history to the weekly statement so the figure is defensible. Add any incentive or bonus you completed but were not paid, and any deposit or kit cost you want refunded.

Check your linked bank account. Confirm the account number and IFSC saved in the app are correct, and that the account is active. A frozen, dormant, or KYC-blocked account can silently bounce a payout while the app shows it as "sent". If you suspect a bank-side problem, see our guide on a bank account KYC freeze and RBI complaint and on how to check your bank account DBT and Aadhaar seeding status.

Raise a written support ticket in the app. Do not just call. Ask three specific things: the exact reason for deactivation, the policy clause relied on, and the date and amount of any pending payout. Request a reply by email so there is a record. Save the ticket number.

Sunday

Draft your escalation email to the platform's grievance officer (use the template in this guide). Quote the ticket number, attach your statements, and state the precise amount you are owed. A clear, numbered email is far harder to ignore than a chat message.

Decide your forum. If the core problem is the withheld money, the consumer forum or a civil money claim is usually the most direct route. If the problem is unfair working conditions or welfare, note your state labour department as a parallel track. Read the platform terms for any arbitration or jurisdiction clause so you know what you agreed to.

Organise everything into one folder — screenshots, agreement, statements, ticket numbers, and your draft email — ready to send first thing on Monday.

Documents and evidence checklist

Step-by-step action plan

Step 1 — Capture the evidence before you lose app access

Deactivation can lock you out within hours. While you can still open the app, screenshot the deactivation notice, your earnings balance, the pending payout figure, the weekly statements, and your trip history. Save your onboarding agreement and payout policy. This snapshot is the foundation of your whole claim, so do it first.

Step 2 — Read the onboarding agreement and payout policy

The agreement you accepted in the app is the contract that governs the dispute. Find the clauses on when payouts are made, what counts as a breach, and what happens to pending dues on deactivation. Most agreements describe you as an independent contractor and reserve a right to hold money during a fraud check. They rarely allow keeping earned dues permanently with no reason. Mark the payout clause — you will quote it.

Step 3 — Identify and pin down the deactivation reason

Read the in-app message and any email. Then raise a written support ticket asking for the specific reason, the policy clause relied on, and the evidence behind it. A vague "policy violation" is not enough for you to respond. Ask them to reply by email. If the reason is a document expiry or a fixable issue, ask exactly what to upload to reactivate. Keep the ticket number.

Step 4 — Reconcile and state the exact amount owed

Match your trip history against your weekly statements and your bank credits. Produce one figure: total earned, total credited, and the difference that is withheld. Add unpaid incentives and any refundable deposit. A precise rupee figure with backup is far stronger than "they owe me my dues". This number goes into every escalation.

Step 5 — Escalate to the platform's grievance officer in writing

Indian platforms that operate as intermediaries are expected to publish a grievance officer's contact for complaints. Find that email in the app, the website's terms, or the privacy/grievance page. Send a numbered email quoting your ticket number, the deactivation date, the exact amount owed, and attach your statements. Ask for a written decision within a reasonable, stated time. The template below gives you a structure.

Step 6 — Send a formal demand if the dues stay frozen

If the grievance email does not release your money, send a final written demand by email and, for a larger amount, by registered post or courier with proof of delivery. State the amount, the contractual basis (the payout clause), the deadline you are giving, and that you will approach the consumer forum or a civil court if it is not paid. This demand record matters if you later litigate.

Step 7 — Choose your forum: consumer, civil, or labour

For recovering withheld money, the consumer forum can be an option if you can show the platform provided a service to you for a fee or commission, though whether a delivery partner is a "consumer" depends on the facts. A civil money recovery suit is the fallback for the contractual dues. For deactivation that looks unfair or for welfare and conditions, raise it with your state labour department or a registered gig-worker union, since gig-worker protections are expanding but vary by state. Take advice on which fits your facts before filing.

Step 8 — Pursue welfare and labour rights as a parallel track

India's labour codes and several states are building registration and welfare frameworks for gig and platform workers. Coverage, registration portals, and benefits differ by state and are still rolling out, so check your state labour department's current scheme. Registering as a gig worker, where available, can help with welfare benefits even though it does not directly force a payout. Keep this separate from your money claim.

Escalation ladder

Copy-paste escalation template

Replace the text in square brackets with your own details before sending. Send to the platform's grievance officer email.

When RTI can help

The Right to Information Act, 2005 applies only to public authorities — government departments, boards, and bodies substantially funded or controlled by the government. Swiggy, Zomato, and similar aggregators are private companies, so RTI cannot be used against them directly. RTI still has a narrow but real role in a delivery-partner dispute, but only where a public body holds relevant records:

• State gig-worker or labour welfare board records: If your state has a gig-worker registration or welfare scheme, you can file an RTI with the relevant board or labour department asking about your registration status, the benefits you are entitled to, or the status of any grievance you submitted to them.
• Status of a complaint to a government body: If you have lodged a complaint with a government consumer authority, the police (for example, where the platform alleged fraud), or a state labour office, RTI can help you get the action-taken status and copies of the file on your own complaint.
• Policy and scheme details: RTI can be used to obtain the text of a state gig-worker welfare scheme, eligibility rules, or the official grievance procedure that a public authority is supposed to follow.

To file an RTI, see our step-by-step guide to filing an RTI online in India. If a public authority does not reply within the time limit, use our first appeal under RTI Section 19 guide. For combining a government grievance with RTI, see CPGRAMS and RTI together, and for deeper strategy, The RTI Playbook.

When RTI will not help

RTI is the wrong tool for the core of this dispute. Be clear about its limits:

• RTI cannot reach the platform: A private aggregator is not a public authority, so you cannot use RTI to get your account file, the deactivation evidence, or your internal payout records. Use the in-app support and the grievance officer route for that.
• RTI cannot release your payout: Even where a public body holds some record, RTI only gives information. It cannot order the platform to pay you. The money has to be recovered through the platform's grievance process, the consumer forum, or a civil claim.
• RTI is slower than your live options: Your support ticket and grievance email move faster than the 30-day RTI cycle. Use RTI as a parallel record-gathering tool, not as your main recovery route.

Common mistakes to avoid

• Not screenshotting before you lose access: Once an account is deactivated, you may be logged out and unable to see your statements. Capture everything the moment you learn of the deactivation.
• Relying on phone calls and chat only: Verbal assurances vanish. Always raise a written ticket and push the platform to reply by email so you have a dated record.
• Asking vaguely for "my dues": A precise figure — total earned minus total credited, plus incentives and deposit — backed by statements is far harder to ignore than a general complaint.
• Assuming the money is gone: Earned payout for completed work is a contractual due, not a favour. A temporary hold during a fraud check is allowed; keeping earned money with no reason is not. Pursue it.
• Ignoring a bank-side failure: Sometimes the platform did send the payout but it bounced because the linked account is frozen, dormant, or has a KYC issue. Verify the account before blaming only the platform.
• Skipping the agreement: The onboarding agreement and payout policy decide the dispute. Quoting the actual payout clause makes your demand and any later case much stronger.
• Using RTI against the platform: RTI does not apply to private companies. Pointing it at Swiggy or Zomato wastes time. Use it only where a government body holds records.
• Going silent after one rejection: One unhelpful reply is not the end. Escalate up the ladder — grievance officer, formal demand, then the consumer or civil forum.

If your dispute is really about a customer-side refund rather than your own earnings, see our guide on food delivery refunds via ONDC, Swiggy and Zomato and on food delivery refund rights in India. If you are setting up your own food business and need licensing, see how to apply for an FSSAI food licence.