Payment gateway settlement on hold can interrupt cash flow even when customers are still placing orders. This guide explains what the hold usually means, what evidence to send, and how a direct UPI collection channel can keep new payments separate from a gateway review.
Before you start: what you need
Collect the hold email, dashboard screenshot, settlement ID, affected dates, amount, and support ticket number. Also keep your business registration or identity documents, website URL, refund policy, order list, invoices, delivery records, and customer communication ready if the provider asks for them.
Do not assume that every “pending” label means the same thing. A payment can be authorised but not settled, a percentage can be held as a rolling reserve, or one disputed transaction can be deducted from an otherwise normal payout. Your first job is to identify which of these is happening.
Step 1: Identify exactly what is on hold
Why this matters: The remedy for an account review is different from the remedy for a scheduled reserve or an individual chargeback.
Do this: Open the provider’s settlement, balance, or risk page and record:
- Whether all settlements are paused or only a percentage is withheld.
- The first affected settlement date and the most recent affected date.
- The gross amount, fees, refunds, disputes, reserve amount, and net amount shown separately.
- The exact status: under review, pending, reserve, dispute, negative balance, or another label.
- Any stated release date, required document, or action button.
Then ask support one precise question: “Is this a full settlement hold, a rolling reserve, or a transaction-level dispute deduction?” Ask for the case reference and the next review step in writing.
Success looks like: You can explain whether the provider is reviewing the account, holding a percentage on a schedule, or removing a named amount for a dispute. Save the relevant screen or export with the date and time.
Step 2: Match the hold to its common cause
Why this matters: Payment providers manage exposure to refunds, disputes, fraud, delivery problems, and regulatory checks. A clear cause tells you which records will be useful.
Common reasons for a payment gateway settlement on hold include:
- Risk review after a change in pattern: A sharp rise in volume, a new product, a new country, unusually large orders, or a mismatch between your normal business and recent transactions can trigger a manual review.
- KYC or business-information refresh: The provider may need current identity, ownership, bank-account, website, or business-activity information. In India, the RBI framework requires payment aggregators to maintain merchant onboarding and KYC/AML-related controls, so a request for updated information is not unusual.
- Chargebacks, refunds, or customer disputes: The provider may keep funds available to cover a dispute, refund, or related liability while it reviews the transaction history.
- Delivery or fulfilment exposure: Pre-orders, long delivery windows, digital access delivered later, or incomplete delivery evidence can increase the risk that a customer will ask for a refund or raise a dispute.
- Negative balance or unpaid obligations: Refunds, disputes, fees, or reversals can reduce the available balance below zero. Payouts may be used to recover that balance.
- Website or policy review: Missing contact details, unclear terms, absent refund information, or a website that does not match the declared business can delay approval or settlement.
The RBI Guidelines on Regulation of Payment Aggregators and Payment Gateways distinguish a payment aggregator, which receives and transfers customer funds, from a payment gateway, which provides technology infrastructure without handling funds. In everyday conversation, merchants often call both a “gateway”; check your agreement to see which entity is actually holding or delaying the settlement.
Success looks like: You have one likely reason, one alternative explanation to rule out, and a list of documents that directly addresses the provider’s question.
Step 3: Separate a rolling reserve from a full hold
Why this matters: A rolling reserve is a cash-flow rule, not the same event as a frozen account or a chargeback.
| Status | What usually happens | What to check |
|---|---|---|
| Full settlement hold | Payouts are paused while the provider reviews the account or a material risk | The written reason, documents requested, and review process |
| Rolling reserve | A fixed percentage of new settlements stays unavailable for a stated window, then releases on a schedule | Reserve rate, holding period, start date, and release schedule in your agreement |
| Transaction-level dispute | A named payment or amount is deducted or set aside for a customer dispute, refund, or reversal | Transaction ID, response deadline, and evidence required |
| Negative balance recovery | Future settlements are applied against an amount you owe the provider | Balance calculation, deductions, refunds, and fees |
For example, if your agreement says 15% of each settlement is held for 30 days, the withheld amount from today’s eligible sales is not automatically the same as a full account hold. The provider should show the rate and release window in the agreement or account notice. Do not budget reserved money as available working capital until it appears in the available balance.
Success looks like: Your cash-flow sheet has separate lines for available settlement, reserve, dispute amount, and expected release. You are not treating a displayed gross sale total as money ready to spend.
Step 4: Send a complete review pack
Why this matters: An incomplete reply can create another round of questions. A short, indexed evidence pack makes it easier for the reviewer to connect your business activity to the transactions.
Do this: Reply in the original ticket or official dashboard channel. Include only documents relevant to the request, and redact unrelated customer information where possible.
Use this order:
- A one-paragraph business summary: What you sell, who buys it, how delivery works, and your normal order value.
- Business and identity documents: Send the current items requested by the provider, with names and addresses consistent across the account, website, and bank details.
- Website evidence: Share the live URL and point to contact details, terms, refund policy, privacy notice, delivery information, and product or service descriptions.
- Order and settlement reconciliation: Map order ID, payment ID, date, amount, customer reference, fulfilment status, refund status, and settlement status in a spreadsheet.
- Fulfilment proof: Attach delivery confirmation, service completion evidence, access logs, signed acknowledgements, or customer acceptance where relevant.
- A risk explanation: If volume changed, explain the real reason—campaign, seasonality, new client, launch, or a large contract—and attach supporting evidence.
Ask the provider to confirm three things: which item is still missing, whether the hold covers future sales or only existing funds, and how the next review will be triggered. Never edit an invoice, create backdated delivery proof, or describe a product differently just to satisfy a review.
Success looks like: The provider acknowledges the case, identifies any missing item, and gives you a written next action or review stage. A response is not a promise that funds will be released immediately, so keep operating cash separate while the review continues.
Step 5: Add a second collection channel for new orders
Why this matters: A single settlement route creates concentration risk. If the gateway is reviewing old transactions, you still need a clean way for customers to pay for new orders without mixing those sales into the disputed history.
A second channel is not a way to bypass a provider’s review or avoid obligations. It is a way to keep accepting an appropriate payment method while you answer the review accurately.
For Indian merchants, direct UPI can be a practical option when your customers already prefer UPI. The customer pays the merchant’s own UPI merchant account. A verification service then matches the UTR and amount to the order and notifies your store or application.
This is different from a payment gateway: PaymentSetu does not collect, pool, or hold your money. It is a payment verification service for connecting your own Paytm Business or PhonePe Business merchant account to your order flow. Money goes directly to your own merchant account, and the service matches the payment to the order.
If your checkout is on WooCommerce, see the guide to integrating UPI on a website without a gateway. If you are still choosing the right merchant account, start with how to open a UPI merchant account in India.
Success looks like: New UPI payments are visible in your own merchant account, linked to the right order, and recorded separately from the gateway settlement that is under review.
Step 6: Set up direct UPI in one working session
Why this matters: A backup route only helps when the customer, order system, and reconciliation process are ready before the next cash-flow problem.
1. Confirm the merchant account
Use a merchant account that belongs to your business. PaymentSetu currently connects Paytm Business and PhonePe Business accounts. Confirm that the displayed UPI ID, business name, and bank details are the ones you want customers to pay.
Success looks like: A small test payment reaches your own merchant account and the credited amount is visible in the provider’s transaction history.
2. Create the PaymentSetu account and choose capacity
Select the plan that matches your verified-payment volume. The Business plan is ₹1,499 per 30 days and includes 100,000 verified payments, dynamic QR, webhooks, API access, a unified dashboard, priority support, and a dedicated account manager. One credit represents one successful payment verified.
Success looks like: Your dashboard shows the active plan and available credits without changing where customer money settles.
3. Connect the payment flow
For WooCommerce, use the PaymentSetu WooCommerce plugin. For a WHMCS billing system, use the PaymentSetu WHMCS module. For a custom checkout, create an order through POST /api/create_order, retain the returned client transaction reference, and check status with GET /api/order_status/{client_txn_id}. Protect the API key on the server and validate HMAC-signed webhooks before changing an order to paid.
Success looks like: Your application creates a unique order, displays a dynamic QR or payment instruction, receives a verified result, and marks the order paid only after the verification event.
4. Test reconciliation before switching traffic
Run one low-value internal test. Compare the order ID, amount, UTR, merchant-account credit, dashboard entry, and webhook payload. Test a second order so you can confirm that each payment maps to only one order.
Success looks like: You can export or view a day’s payment list and match every verified order to a credit in your own merchant account.
Link the new route from the checkout or invoice only where it fits your business and customer experience. Keep the gateway review ticket open, answer it honestly, and maintain the original provider’s requested records.
Verify your cash position every day
Use a simple settlement register until the hold is resolved. Add one row for each affected settlement or reserve movement:
| Field | Example entry |
|---|---|
| Date | 28 October 2026 |
| Gross customer payments | ₹1,20,000 |
| Available settlement | Amount shown as available |
| Reserve or hold | Amount and reason shown by provider |
| Dispute/refund deductions | Transaction IDs and amounts |
| Evidence sent | File names and ticket date |
| Expected next action | Review reply, reserve release, or support follow-up |
Reconcile the register against your bank statement, gateway export, order system, refund log, and direct UPI merchant-account statement. Keep the held amount visible as a receivable or restricted balance according to your accountant’s process; do not record it as lost merely because it is delayed, and do not treat it as available merely because the customer paid.
For the fee side of the decision, compare the gateway’s percentage charges and settlement terms with a direct UPI plan. The UPI payment gateway charges in India guide gives a useful way to model the monthly difference before you move a meaningful share of orders.
Troubleshooting a settlement hold
The dashboard says “pending” but gives no reason
Save the status, timestamp, settlement ID, and affected amount. Contact support through the official channel and ask whether it is a normal payout cycle, a risk review, a reserve, or a dispute. Keep the question narrow and request a case reference.
The provider asks for the same document again
Check whether the document is current, readable, complete, and consistent with the account name and address. Reply in the existing ticket with the exact file name and ask which page or field failed validation. Do not open multiple tickets with conflicting explanations.
Only part of each payout is missing
Look for a reserve percentage, refund deduction, dispute amount, fee, or negative-balance recovery. Compare the withheld amount with the agreement and settlement report rather than guessing from the bank credit.
Customers need to keep paying while the review continues
Keep the gateway review active and provide the appropriate direct UPI option for new orders. With PaymentSetu, the payment lands in your own Paytm Business or PhonePe Business merchant account, while the service verifies the UTR and amount against the order.
The gateway says the review is complete but the balance is still not clear
Ask for the release or payout reference, the amount still outstanding, and whether another reserve, dispute, refund, or negative balance remains. Reconcile the response to your register and bank statement. If the figures do not match, send a dated transaction-level list rather than a general complaint.
FAQ
What does payment gateway settlement on hold mean?
It usually means the provider has paused, reduced, or reserved a payout rather than treating the customer payment as a normal available settlement. The exact reason may be an account review, rolling reserve, dispute, refund exposure, negative balance, or missing business information.
How long does a settlement hold last?
There is no single timeline for every provider or account. Ask for the written reason, the documents still required, and the next review or release event; a rolling reserve follows its stated schedule, while an account review depends on the provider’s assessment.
Is a rolling reserve the same as a settlement hold?
No. A rolling reserve normally withholds a stated percentage of settlements for a stated period and releases each amount on a schedule. A full hold pauses payouts while the provider reviews an account or a material risk issue, and a chargeback deduction relates to a named disputed transaction.
Can direct UPI prevent a gateway settlement hold?
No payment route can remove another provider’s hold or replace its review process. Direct UPI can give you a separate collection channel: customers pay your own merchant account, while PaymentSetu verifies the payment against the order and sends the result to your store or application.
What should I send when a payment gateway asks for documents?
Send the exact current documents requested, plus a concise description of your business, live website policies, order-to-settlement reconciliation, and genuine delivery or service evidence. Ask the provider to confirm what is still missing and keep all replies in the official case thread.