Payment Gateway Holding Your Merchant Settlement for KYC or Risk? Here Is How to Recover It

Who this guide is for

This guide is for small businesses, online sellers and individual merchants who collect payments through a payment gateway or payment aggregator, and whose settlements have been held, delayed or frozen. It applies whether you have a few orders a week or run a busy store. It is useful if you face any of these:

• The dashboard shows your settlement as "on hold", "under review" or moved into a reserve, and the bank credit has stopped.
• The gateway has asked for fresh KYC or business documents and frozen payouts until you complete them.
• A risk or fraud flag was raised after a spike in sales, high refunds or a run of customer disputes.
• Chargebacks have triggered a reserve and the gateway is holding back a slice of every settlement.

It is especially useful if the held money is squeezing your cash flow, because clear, dated, written follow-up moves these cases faster.

Who this guide is NOT for

This guide does not cover a freeze on your business bank account ordered by the police, a cyber cell or a court, which is a different problem with a different remedy. For a lien or freeze placed on your account through a cybercrime complaint, see our guide on removing a cybercrime lien on a bank account. It also does not cover a bank's own re-KYC freeze on your account, covered in our bank KYC freeze guide. This is purely about funds held by a private payment gateway or aggregator.

What you can do this weekend

Friday evening

Log in to your merchant dashboard. Open the settlement ledger and take screenshots of the held amount, the settlement status and any reason note or reference code. Look for a notifications or tickets area where the gateway may have already explained the hold. Download your transaction report and settlement statement for the affected period. Note the exact date the payouts stopped. Save everything in one dated folder. This evidence is the spine of every later step.

Saturday

Work out which type of hold you face. A KYC hold usually comes with a request for documents or an "incomplete profile" note. A risk hold tends to follow a sudden change in your sales pattern, refunds or disputes. A reserve is a percentage held back, described in your merchant agreement. Read the agreement and the dashboard's reserve or settlement settings. If the hold is KYC-related, resubmit any missing or expired documents through the dashboard right away, and keep the ticket number and a timestamp of each upload.

Sunday

Draft your written grievance to the gateway's nodal or grievance officer using the template below. Ask them to state the specific reason for the hold, the exact documents needed, and the date funds will be released. Request release of any undisputed amount that is not tied to a reserve or a live dispute. Find the grievance contact on the gateway's website, usually under a Grievance Redressal or Contact Us page. Send it through the official channel and save the acknowledgement. By Monday you will have a documented complaint and a ticket reference, which starts your escalation clock.

Documents and evidence checklist

Step-by-step action plan

Step 1 — Read the dashboard and settlement ledger

Start with the facts on your own screen. Open the merchant dashboard and the settlement ledger. Find the held amount, the settlement status and any reason code or ticket. Many gateways show a short status note such as "under review" or "documents pending". Export the settlement statement and the transaction report for the affected dates. Screenshot everything. You cannot fix a hold you do not understand, so getting the precise on-record reason is the foundation of every later step.

Step 2 — Identify the type of hold

There are three common types, and they need different responses. A KYC or documentation hold is the simplest; you cure it by submitting the right documents. A risk or fraud hold follows an unusual pattern, such as a sales spike, high refund rate or a cluster of disputes, and you clear it by proving your orders are genuine. A rolling reserve or chargeback reserve is a planned percentage held back under your merchant agreement; this is contractual rather than a flag. Read your merchant agreement and the reserve settings to see which applies, because mixing them up wastes time.

Step 3 — Cure KYC and merchant documentation

If the hold is KYC-related, resubmit the requested documents through the dashboard exactly as asked. Common items are PAN, a GST registration where you have one, business registration or incorporation papers, address proof and a bank-account proof such as a cancelled cheque. Make sure the business name, PAN and bank details match across every document and your dashboard profile, because mismatches are a frequent cause of holds. Keep the ticket number and a timestamp of each upload. Then ask the gateway to confirm in writing that the KYC is complete and to release the funds.

Step 4 — Answer a risk or fraud flag with evidence

If the hold is a risk review, the gateway is checking whether your transactions are genuine. Send the proof: invoices, order details, delivery or service evidence, and customer communication for the flagged transactions. If a sudden volume spike triggered the flag, explain the business reason, such as a sale, a campaign or a new product. Keep your tone factual and attach clean records. The faster you supply credible proof, the faster a genuine merchant clears a risk hold.

Step 5 — Write to the grievance or nodal officer

Raise a formal written grievance through the gateway's grievance channel. RBI-authorised payment aggregators are required to publish a grievance or nodal officer's contact and to run a grievance redressal process. State your merchant ID, the held amount, the dates, and ask for the specific reason, the exact documents needed and the release date. Crucially, request release of any undisputed amount not tied to a reserve or live dispute. Use the template below, send it through the official channel, and save the ticket number and acknowledgement.

Step 6 — Escalate to the RBI if the gateway does not resolve it

Payment aggregators are regulated by the Reserve Bank of India. If the gateway does not resolve your grievance within its published timeline, or gives no clear documented reason, you can lodge a complaint with the RBI at cms.rbi.org.in. Attach your ledger, your grievance, the ticket number and the gateway's reply or its silence. Whether a specific dispute falls within a particular RBI ombudsman scheme can vary, so check the current scope on the RBI portal, but the RBI complaint route is the correct regulator-level escalation for a payment aggregator.

Step 7 — Use the commercial legal route for wrongful withholding

If a large sum is being withheld with no valid, documented reason after you have exhausted the grievance and RBI routes, a commercial legal remedy may be needed. A lawyer can send a legal notice demanding release of the funds, and you can pursue recovery through the appropriate civil or commercial forum. Because the amounts and the contract terms can be complex, take advice from a qualified lawyer before sending a notice or filing a case, especially where the sum at stake is significant.

Escalation ladder

Copy-paste grievance 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. A payment gateway or payment aggregator is a private company, so it is not directly covered by RTI. However, payment aggregators are regulated by the Reserve Bank of India, and the RBI is a public authority under the RTI Act. That gives you a useful, if indirect, RTI angle once you have already complained to the RBI:

• Ask the RBI whether your complaint about the gateway has been received and registered.
• Ask about the status or action taken on your complaint, in general terms.
• Ask for publicly disclosable information the RBI holds about the regulatory framework for payment aggregators.

Use the gateway grievance route and the RBI complaint route first, because those are the channels that can actually release your money. RTI to the RBI is a paper-trail and accountability tool that runs alongside, not instead of, those steps. For the mechanics of filing, read our guide on how to file an RTI online in India, and if the RBI does not reply within the prescribed period, see how to file a first appeal under RTI Section 19. Our CPGRAMS and RTI guide also explains how to push central-government grievances.

When RTI will not help

The gateway itself: You cannot file an RTI against a private payment gateway or aggregator to force it to release your settlement. RTI does not apply to private companies. The correct first routes are the gateway's grievance and nodal officer, and then a complaint to the RBI as the regulator.

RTI does not order a release: Even an RTI to the RBI only gives you information; it cannot direct a private gateway to pay you. The leverage to release funds comes from the gateway's own grievance process, the RBI complaint route, and, where funds are wrongfully withheld, a commercial legal remedy.

Commercial disputes between two businesses: A dispute over reserve terms, settlement timelines or chargebacks is a commercial matter under your merchant agreement. RTI has no role there. Use the contract, the regulator and, if needed, a civil or commercial forum, after taking legal advice for large sums.

Common mistakes to avoid

• Not reading the settlement ledger first. People often escalate before they know the on-record reason. Open the dashboard, find the held amount and the reason code, and export the statement. You cannot fix or complain about a hold you have not documented.
• Confusing a contractual reserve with a wrongful hold. A rolling or chargeback reserve described in your merchant agreement is planned, not a freeze. Check the agreement before treating a reserve as a grievance, or you will argue the wrong point.
• Submitting mismatched KYC. If your business name, PAN or bank details differ across documents and the dashboard, the hold will not lift. Make every detail match before you resubmit, and keep the ticket number for each upload.
• Only chatting with support, never raising a written grievance. Chat logs rarely create a clean escalation record. Send a written grievance to the nodal or grievance officer and keep the ticket reference, because that is what lets you escalate to the RBI.
• Not asking for the undisputed amount. Holds often affect only part of your balance. Always ask the gateway to release any amount not tied to a reserve or a live dispute, so your cash flow is not stuck unnecessarily.
• Trying to file an RTI against the gateway. Private gateways are not public authorities. An RTI to the gateway has no legal basis and wastes time. Use the grievance and RBI routes, and reserve RTI for records the RBI itself holds.
• Jumping to court before exhausting free routes. A legal notice has its place for large, wrongful holds, but the gateway grievance and RBI routes are free and often faster. Take legal advice before litigating, especially for big amounts.