FAQ Section
Payment Operations

How Does Merchant Settlement Work and What Are Reserves?

 

When merchants receive settled funds, how settlement batching and fees work, and why providers hold rolling reserves against refunds and chargebacks.

Merchant settlement is the process of paying out the funds you have collected from customers, after clearing completes and fees are accounted for. Reserves are amounts a provider or acquirer holds back from settlement to cover the risk of refunds, chargebacks and unpaids that may arrive after the money has been paid out.

Both affect your cash flow directly, so it is worth understanding how settlement is batched, what can delay it, and why reserves exist.

When do merchants receive settled funds?

Settlement timing depends on the payment method and the provider's settlement schedule:

  • Card payments are typically settled in daily batches, one or more business days after the transactions were authorised and cleared.
  • Debit order collections settle on the processing cycle for the action date, but providers may delay paying out collected funds until the main unpaid window has passed, because collections can be returned after settlement.
  • Real-time and EFT payments follow the clearing cycles described in clearing, settlement and reconciliation.

Settlement is usually batched: all transactions for a period are grouped, fees are calculated, and a single amount is paid to your bank account with a settlement report that breaks the batch down to transaction level.

What is gross vs net settlement?

  • Gross settlement pays out the full transaction value, with fees invoiced or debited separately. This makes reconciliation simpler because bank credits match transaction totals.
  • Net settlement deducts fees, refunds and adjustments before paying out. The settlement report is essential here, because the bank credit will not match the sum of transaction amounts on its own.

Confirm which model applies to your account and make sure your finance team reconciles against the settlement report, not just the bank statement.

What can delay or reduce a settlement?

  • Transactions still in an interim state, since many outcomes are asynchronous.
  • Unpaids, refunds and chargebacks deducted from the batch.
  • Public holidays and weekend cut-offs shifting value dates, as covered in cut-off times and value dates.
  • Risk reviews or verification requests on unusual volumes.
  • Bank account detail changes, which providers verify before redirecting funds.

What is a rolling reserve?

A rolling reserve is a percentage of each settlement that the provider holds for a defined period before releasing it. For example, a portion of each batch might be held and released on a rolling basis some weeks or months later. The reserve exists because liabilities can arrive after payout:

  • Card chargebacks can be raised long after the sale.
  • Debit order disputes can reverse collections that were already settled.
  • Refund obligations remain if a business stops trading before delivering goods or services.

What other reserve types exist?

  • Fixed or upfront reserve: a set amount held when the account is opened, common for higher-risk industries.
  • Capped rolling reserve: a rolling reserve that stops growing once it reaches an agreed ceiling.
  • Conditional holds: temporary holds on specific batches during a risk investigation.

How are reserve levels decided?

Providers set reserves based on the risk profile of the business, including industry, delivery timelines, chargeback and unpaid history, and processing volumes. Reserves are typically reviewed over time; a clean processing history is the strongest argument for reducing or removing a reserve.

How should you manage settlement operationally?

  • Reconcile every settlement batch to transaction level on the day it arrives.
  • Track reserve balances and release dates so cash flow forecasts are accurate.
  • Monitor unpaid and chargeback rates, since they drive both deductions and reserve levels.
  • Query discrepancies quickly, with the batch reference and affected transaction references to hand.

For related topics, see the Payment Operations hub.

Copyright © 2026 Kwik Payments