A customer can receive a “payment successful” message while the merchant has not yet received that money in its bank account. This is normal: payment authorization and merchant settlement are different stages of an online transaction.
Payment settlement transfers money collected for successful transactions to the merchant’s bank account after processing, adjustments, and checks. Understanding the cycle helps forecast cash flow, reconcile orders, and investigate missing funds.

Table of contents:

• How payment settlement works
• Authorisation, capture, clearing, and settlement
• What T+0, T+1, and T+2 mean
• How the settlement amount is calculated
• Why a settlement may be delayed or placed on hold
• How to reconcile payment settlements
• How PayU supports settlement operations
• FAQs

How payment settlement works

An online payment involves multiple parties. The customer pays using a card, UPI, net banking, wallet, or another supported mode. The merchant’s payment provider routes and processes the request with the relevant banking or payment-system participants. If the payment is successful, the order can move forward according to the merchant’s fulfillment policy.
Funds do not always move directly into the merchant’s bank account. A payment aggregator may receive customer payments and transfer amounts due according to its regulated structure, agreement, and settlement cycle.
RBI’s 2025 Master Direction distinguishes payment aggregators, which receive and transfer funds, from payment gateways that provide transaction-routing technology without handling funds. It also requires a non-bank payment aggregator to maintain collected merchant funds in a separate escrow account. The precise merchant timeline depends on the provider agreement, payment mode, settlement setup, cut-offs, and applicable adjustments.

Authorization, capture, clearing, and settlement

These terms are related but not interchangeable.

• Authorization

Authorization is the decision to approve or decline a payment request. The issuing bank or relevant payment participant checks factors such as credentials, account status, available balance or credit, limits, and risk controls. An approval means the payment can proceed; it does not mean the merchant’s bank account has already been credited.

• Capture

Capture confirms that an authorized card payment should complete. Some flows combine authorization and capture; others separate them. An uncaptured authorization may expire or reverse.
For other payment modes, the terminology and mechanics can differ, but the operational principle remains: the payment must reach the correct successful state before it can be included in merchant settlement.

• Clearing

Clearing exchanges and reconciles transaction information between payment participants, establishes amounts owed, and accounts for adjustments.

• Settlement

Settlement is the transfer of the net amount due to the merchant’s bank account. The payment provider generally groups eligible transactions into a settlement and supplies a reference and report. The merchant then matches that bank credit to the underlying payments and deductions.

What T+0, T+1, and T+2 mean

Settlement cycles are commonly written as T plus a number:

• T+0 means settlement on the defined transaction day.
• T+1 means settlement one eligible day after T.
• T+2 means settlement two eligible days after T.

The critical detail is the definition of T. It might be the successful transaction date under a provider’s standard cycle, but another agreement may use capture or a different stated operational event. RBI’s 2025 Master Direction requires the PA–merchant agreement to be fair and transparent about settlement timelines; it does not create one universal T+ cycle for every merchant.
“Day” may also mean a working or business day rather than a calendar day. Suppose a provider offers T+2 working-day settlement from a successful transaction on Friday. If Saturday and Sunday are not counted and Monday is a bank holiday, settlement would not be expected merely because two calendar dates passed. Cut-off times and the beneficiary bank’s processing can also affect when the credit becomes visible.
Record the event defining T, cut-off time, working-day calendar, and expected bank-credit window. Do not compare providers only by the T+ label.

How the settlement amount is calculated

The amount credited can be lower than the gross value of successful sales in the settlement period. A simplified calculation is:
Net settlement = eligible captured sales − applicable fees and taxes − refunds or reversals − chargeback or dispute adjustments ± other documented adjustments
The exact sequence and line items depend on the contract and report format. Some refunds may be funded from a settlement balance, while other arrangements may use a separate process. A reserve, rolling hold, or risk adjustment may apply in specific merchant agreements.
Finance teams need transaction- and settlement-level records showing:

• Provider transaction and merchant order references
• Payment date, mode, amount, and final status
• Settlement ID, settlement date, and bank reference or UTR
• Fees, taxes, refunds, reversals, disputes, and other adjustments
• Net amount credited

This data creates an audit trail from a customer order to the bank statement.

Why a settlement may be delayed or placed on hold

• Incomplete onboarding or bank verification

A provider may be unable to release settlements until the merchant has completed required verification, supplied documents, signed the applicable agreement, and confirmed the beneficiary bank account. Businesses should complete these steps before accepting production payments where possible.

• Weekends, bank holidays, and cut-off times

A transaction processed after a cut-off may enter the next cycle. Non-working days can extend a working-day timeline. Check the provider’s current calendar and cycle definition rather than calculating only from the customer’s payment timestamp.

• Risk or compliance review

Unusual transaction patterns, a high dispute rate, prohibited activity, a mismatch in merchant information, or a request for proof of delivery can lead to review or a hold. Respond through the provider’s official support channel and supply the requested evidence.

• Refunds, reversals, and chargebacks

A payment that was initially successful may later be refunded, reversed, or disputed. These events can change the amount available for settlement or appear as adjustments in a later cycle.

• Technical or bank processing issues

Incorrect beneficiary details, a bank rejection, service disruption, or a delayed status update can affect the visible credit. Keep settlement references and bank statements ready when raising an investigation.

How to reconcile payment settlements

Reconciliation should be a repeatable daily process, not an end-of-month rescue exercise.
First, export or retrieve the provider’s transaction, refund, dispute, and settlement data. Match merchant order IDs to provider transaction IDs and confirm that only final eligible payments were fulfilled. Next, map each transaction to a settlement ID and verify every fee or adjustment against the agreed schedule.
Then match the settlement’s net amount and bank reference with the credit in the business bank statement. Move unmatched records into clear exception queues: successful but unsettled, settled but unmatched, duplicate order, pending payment, refund mismatch, fee variance, or bank credit missing.
Automate matching where volume justifies it, with review controls. Alert on ageing unsettled payments, fee changes, repeated holds, unexplained adjustments, and missed credits. Restrict changes to beneficiary bank details.
Useful metrics include average settlement age, percentage settled on expected date, unreconciled value, fee variance, refund aging, dispute rate, and time to resolve exceptions.

How PayU supports settlement operations

PayU currently documents a standard settlement cycle of T+2 working days, where T is the successful transaction date, excluding bank holidays. The actual first credit and ongoing cycle depend on completed bank verification, required documents and agreement, the settlement type selected, and any applicable review or hold.
The PayU Dashboard provides settlement information including sales amount, fees, settled amount, status, date, and UTR. Businesses can also generate reports for transactions, settlements, refunds, and service-fee invoices to support reconciliation. Eligible merchants may see priority-settlement options; availability, cycle, limits, and charges depend on current eligibility and terms.
Review the latest PayU settlement documentation before setting cash-flow expectations, and investigate exceptions using the settlement ID and bank reference rather than the order number alone.

FAQs

1. Is settlement the same as payment success?

No. Payment success indicates that a customer transaction reached an approved or successful state. Settlement is the later transfer of the eligible net amount to the merchant’s bank account.

2. What does T+2 settlement mean?

It means settlement two eligible days after the event defined as T. Check whether T is transaction, capture, shipment, delivery, or another trigger, and whether the provider counts business days or calendar days.

3. Why is my settled amount lower than my sales amount?

The settlement may be net of applicable fees, taxes, refunds, reversals, disputes, reserves, or other documented adjustments. Use the settlement report to trace each difference.

4. Do weekends and bank holidays count in settlement cycles?

Not when the cycle is stated in working or business days. Provider cut-offs and the beneficiary bank’s processing may also affect when the credit appears.

5. What should I do if a settlement is missing?

Confirm the expected date, bank account verification, settlement status, adjustments, and bank statement. Then contact the provider with the merchant ID, settlement ID, expected amount, date, and UTR or bank-reference status. Do not ask the customer to pay again when their original payment is already successful.