From the journal

Challenging card chargebacks and settlement holds: the merchant’s legal remedies

A rise in card disputes can create three immediate problems for a digital-services business: reversed payments, a larger merchant rolling reserve and settlement that no longer arrives. A termination warning adds a fourth. Assess suspected chargeback fraud through evidence of payment consent, service performance and the specific allegation; investigate each separately before attributing dishonesty.

39 min read

The merchant needs two coordinated challenges. The first answers each card dispute under its actual reason code and deadline. The second tests the provider’s authority to debit, retain or increase security over the merchant’s money. Winning a transaction dispute may reduce the provider’s exposure. The merchant agreement and applicable law determine how that reduced exposure affects reserve release and whether the provider may retain unrelated sale receipts. The applicable network rules, merchant agreement and local law answer different parts of the question.[1][2][3]

This comparison examines the United States and Canada; the UK, France and Germany within the relevant European framework; Singapore and India; the United Arab Emirates (UAE) and Saudi Arabia; South Africa and Nigeria; Brazil and Mexico; and Australia and New Zealand. It states the law, network rules and provider terms as at 19 November 2026. The most useful differences concern who owes settlement, how contractual discretion is controlled, which complaint or court route can order a remedy, and whether the retained funds survive the provider’s insolvency.

Four routes that should not be confused

  • Merchant refund. Who acts against whom: Customer requests performance, cancellation or reimbursement from the seller or merchant of record; the merchant instructs the refund. What must be established: Applicable sale terms and consumer law, the refund ground, amount and actual credit. What the outcome does not automatically decide: Whether a chargeback also occurred, who bears fees, or whether the provider may retain a separate reserve.
  • Statutory issuer remedy. Who acts against whom: A qualifying cardholder or payment user claims against the issuer or its payment service provider (PSP). What must be established: The statutory product, territorial and customer scope; notification; and the particular error, unauthorised payment or linked-credit claim. What the outcome does not automatically decide: The merchant’s liability under its acquiring contract or the legality of a settlement hold.
  • Scheme chargeback. Who acts against whom: Issuer and acquirer use the card network’s process; the merchant supplies evidence through its provider. What must be established: The reason code, operative rule, stage, regional exceptions and admissible evidence submitted on time. What the outcome does not automatically decide: All rights under the sale contract or a separate merchant-provider claim.
  • Merchant-provider claim. Who acts against whom: The merchant claims against the entity owing settlement or another party with a proved legal responsibility. What must be established: A due debt, breach, invalid or misused term, accounting duty or proprietary entitlement, plus the conditions for the remedy sought. What the outcome does not automatically decide: A right to bypass the agreed forum, recover the same loss twice or disregard a valid customer defence.

US Regulation Z makes the separation particularly clear. Its billing-error procedure and its claims-and-defences procedure are distinct, and the latter preserves underlying claims without deciding their validity. EU payment legislation likewise defines a payment transaction independently of the underlying obligation. A scheme decision therefore needs to be read for what it decided, together with any later settlement, release, award or judgment.[4][5][6]

Identify the settlement debtor before demanding release

Start with legal names and contracts. The issuer owes duties to its cardholder. The acquirer participates in the network and contracts with a merchant or facilitator. A payment facilitator may contract with sponsored merchants. A merchant of record may be the legal seller and acquiring customer, leaving the digital-service supplier with a separate payout claim. A technical gateway may never receive funds. These roles can sit in different companies within the same branded group.[7][8]

Obtain the executed merchant agreement and acceptance record, acquiring or submerchant addenda, merchant identifiers, payout account details and transaction statements. Map each receipt and transfer. Then distinguish unsettled proceeds, a debt already due for payment, collateral securing future chargebacks and amounts already applied to actual fees or liabilities. The legal holder, contractual debtor and safeguarding institution may be different entities.

This distinction changes the demand in Nigeria. The Central Bank of Nigeria (CBN) 2021 non-bank acquiring framework, section 6, prohibits a non-bank acquirer from directly holding merchant funds for settlement, reversal or any other reason. The sponsor or settlement bank and the executed service-level agreement therefore matter. Published Paystack Nigerian terms also identify acquiring banks or payment-method acquirers as the parties settling the payout account. A complaint addressed only to the dashboard operator may miss the party that holds or owes the money.[9][10]

In South Africa, the 2026 transfer of payment oversight from the Payments Association of South Africa to the South African Reserve Bank (SARB) preserves existing third-party payment-provider registrations during transition. As at 19 November 2026, Directive 1/2007 remained effective, and sponsoring-bank arrangements remain relevant to identifying the provider and funds route.[11]

Singapore provides a litigation warning. In B High House v MCDP Phoenix, the claimant did not prove the alleged contract and agency arrangements or adequately authenticate the reports supporting its balance. The case illustrates the need for the contract, reliable source reports and witnesses linking the claimed balance to the defendant’s obligation.[12]

Can a merchant dispute a chargeback?

Often the merchant can supply a response, but the available route depends on the case and its stage. Merchant chargeback rights depend on the applicable law, network stage and provider agreement. Ask the provider for the network, transaction type, reason code, dispute-processing date, governing edition, issuer material, submission deadline, evidence format and remaining escalation options. Preserve the notification and the provider’s receipt of the response.

For a non-delivery allegation, show what was promised, when it was due, which account received it and whether the agreed service was available or performed. For unauthorised use, show the evidence relevant to payment consent and the applicable authentication or liability-shift rules. An IP address, login or download can be useful without proving who authorised the card. For recurring payments, preserve the consent, billing terms, cancellation request and event history. For a duplicate or already-refunded transaction, link the original payment and credit by their processing references.

Keep the correct deadline and the correct evidence together

  • Visa 10.4: card-absent fraud. What the primary rules establish: The 24 October 2026 rules give the issuer a 120-calendar-day period from the Transaction Processing Date for this condition. Available answers and compelling evidence have additional requirements. Merchant action: Identify the precise defence and evidence elements; do not treat service use as conclusive authorisation.
  • Visa 13.1: non-receipt. What the primary rules establish: The issuer’s period can run from processing or expected receipt, subject to the stated outside limit and exceptions. A response can establish agreed receipt/performance, an earlier credit or another permitted ground. Merchant action: Tie evidence to the promised date, service and recipient; identify the undelivered portion rather than assuming the full sale is disputed.
  • Visa acquirer response stages. What the primary rules establish: The usual relevant acquirer stage is 30 calendar days. The rules substitute two business days for Nigeria domestic transactions in the relevant fraud/authorisation pre-arbitration and processing/consumer-dispute response stages. Merchant action: Confirm domestic versus cross-border treatment and the provider’s earlier merchant deadline immediately.
  • Mastercard. What the primary rules establish: The public detailed Merchant Edition cited here is dated 13 May 2025; the cited public general and security rules are later. Mastercard warns that public documents may not contain every current standard. Merchant action: Obtain the operative chargeback standard and bulletins from the acquirer before relying on a live second-presentment or escalation deadline.

These periods govern network participants at specified stages. Obtain the merchant’s separate portal or contractual deadline, which may require evidence sooner. Visa’s October 2026 book also contains provisions expressly effective in October 2027; an edition date alone does not make every paragraph operative.[1][2][13]

If a provider failed to transmit a timely response, preserve the packet, upload receipt, rejection message and its contractual handling promise. A damages claim still needs causation: the evidence must have supported an available response, and the loss must follow from the provider’s breach. A missed submission does not prove that the merchant would have won.

Consumer issuer rights can continue on a different timetable

In the United States, Regulation Z section 1026.13 covers specified consumer open-end credit billing errors, including goods or services not accepted or delivered as agreed. The consumer’s written notice ordinarily runs from the first statement, not the merchant’s dispute notice. Accepted-service quality complaints fall outside that particular provision, and the consumer need not first contact the merchant for its non-delivery branch. Section 1026.12(c) separately addresses claims and defences, with its amount, location, prior-contact and outstanding-credit conditions. Consumer debit error investigation follows Regulation E instead.[4][5][14]

In Quebec, the consumer regulator explains a specific distance-contract sequence: qualifying cancellation, the merchant’s failure to refund within 15 days, and then a written issuer request within 60 days of that default. The conditions and excluded transactions matter. It is not a nationwide Canadian right to reverse any unsatisfactory purchase.[15]

In the UK, qualifying linked-credit claims under Consumer Credit Act section 75 are separate from chargebacks. In the EU, unauthorised-payment refunds under the second Payment Services Directive (PSD2) are separate from conditional refunds of authorised payee-initiated transactions. The familiar eight-week direct-debit rule should not be imported into ordinary card non-delivery disputes. France and Germany apply their national implementing provisions, with specific business-user derogations rather than a blanket business exemption.[16][6][17][18]

In Singapore, the liability-allocation part of the Monetary Authority of Singapore’s E-Payments User Protection Guidelines excludes credit and charge cards and debit cards covered by the specified Association of Banks in Singapore Code of Practice for Banks: Credit Cards. In India, bank conduct directions distinguish unauthorised-payment liability by fault and notification, while the payment aggregator (PA) rules require the parties’ dispute and refund responsibilities to be documented. The Indian amendment applying to transactions from 1 January 2027 should not be applied to a November 2026 event.[19][8][20][21]

The same discipline applies elsewhere: South African sale remedies address the supplier; New Zealand’s Banking Ombudsman distinguishes the chargeback process from the merchant-bank contract; Australian ePayments Code coverage depends on the subscriber and facility; Mexican card-issuer rules and Brazil’s consumer invoice protections do not themselves decide a merchant’s reserve claim.[22][23][24][25][26][27][28]

Mexico supplies a specific connection between an issuer reversal and merchant liability. For the instructions covered by Circular 34/2010 section 3.4’s final paragraph, an acquirer’s recovery from the merchant under section 2.3 Bis requires the agreed provision of authentication means and the merchant’s failure to request the required factors. If the acquirer later receives the issuer’s returned funds under section 3.6, it must credit the merchant account by the next business day after receipt. Ask for the authentication arrangement and the issuer-to-acquirer receipt date; each can change the amount now due. A separate continuing reserve needs its own legal basis.[28]

Ask which power the provider used. Increasing a percentage under an existing reserve formula, adding a new contract term, suspending settlement, debiting an actual chargeback and terminating the relationship are different actions. A clause permitting one does not necessarily permit the others.

Published provider terms illustrate the point. Stripe’s terms modified on 28 September 2026 address reserve notice, funding, adjustment, application and release, with regional provisions that identify different entities and legal arrangements. Paystack’s South African and Nigerian merchant agreements contain different reserve and disclosure promises. These terms help identify questions to ask; the merchant must establish which entity, version and amendments it actually accepted. Mandatory law remains relevant even where a provider describes its discretion broadly.[3][29][10]

Held-funds review

  • Authority. Documents and evidence to obtain: Signed agreement, incorporated rules, reserve notice, later amendments and acceptance records. Legal test and practical request: Identify the power used and its conditions. Challenge an absent power, unmet trigger or invalid term on the applicable legal basis.
  • Calculation. Documents and evidence to obtain: Reserve base and rate, affected cohorts, actual chargebacks, contingent exposure, refunds, guarantees and other holds. Legal test and practical request: Reconcile the balance and remove double counting. Seek the amount exceeding a valid contractual or statutory risk basis.
  • Duration. Documents and evidence to obtain: Start date, review history, service-delivery dates, remaining dispute exposure and surviving liabilities. Legal test and practical request: Test the actual release condition. A network time limit is not automatically the contractual reserve period or the end of every possible claim.
  • Evidence and reasons. Documents and evidence to obtain: Programme notice, issuer cases, risk data, decision record and relevant provider correspondence. Legal test and practical request: Correct erroneous attribution and distinguish real liability from unsupported assumptions. Request reasons or records where contract or law requires them.
  • Notice. Documents and evidence to obtain: Delivery logs, amendment notice, termination notice and complaint instructions. Legal test and practical request: Distinguish exercising an existing power from changing terms. Apply the rule for that action, entity, contract date and customer class.
  • Release. Documents and evidence to obtain: Aged exposure schedule, matured settlement ledger and unresolved deductions. Legal test and practical request: Demand any legally due tranche; propose a supported partial release, reducing cap or substitute security for the contested balance.
  • Insolvency. Documents and evidence to obtain: Account title, trust or escrow terms, safeguarding method, beneficial records, bank statements and security documents. Legal test and practical request: Establish whether the claim concerns protected property, security or an ordinary debt, and the process for recovering it.

Where the balance remains a covered payment-execution amount credited to the payee’s PSP, statutory payment-availability duties also matter. PSD2 article 87, as implemented in the relevant EU state, and regulation 89 of the UK Payment Services Regulations 2017 (PSR) sit outside the ordinary listed business opt-outs, subject to territorial and currency conditions. Test the fund flow and any valid collateral or set-off arrangement. These duties do not decide every reserve structure; a corporate UK merchant still must identify an available enforcement route.[6][30]

This exercise should produce an amount and a legal reason for the requested remedy. A demand to “release all funds because chargebacks are unfair” leaves the provider’s strongest answer untouched: that the agreement permits security for a real remaining liability.

Where local law changes the challenge

Contractual discretion, business protections and the available claimant

  • United States, California-law branch. Material legal route: Civil Code section 1670.5 allows a court to refuse, sever or limit an unconscionable term. Condition that changes the result: The assessment concerns formation and commercial context. A painful reserve is not automatically unconscionable; other states require their own analysis.
  • Canada, common-law branch. Material legal route: Wastech requires contractual discretion to serve the purpose for which it was granted. Condition that changes the result: Show why the amount or continued hold is disconnected from the clause’s actual risk purpose. The rule does not guarantee profitability or rewrite the bargain.
  • UK. Material legal route: Contract enforcement and contextual control of a decision power; applicable payment-service notice duties; eligible Financial Ombudsman Service (FOS) complaints. Condition that changes the result: A corporate merchant generally cannot use PSR regulation 148’s private-person damages action for business loss. Contract rights and complaint eligibility remain separate.
  • France. Material legal route: Mandatory good faith and, within its scope, Civil Code article 1171 control of predetermined, non-negotiable adhesion terms. Condition that changes the result: Significant imbalance needs proof. A one-sided provision may reflect different obligations; special statutory regimes and the exclusion for subject matter/price adequacy matter.
  • Germany. Material legal route: Civil Code (BGB) sections 307/310 govern relevant standard terms; section 315 can control a qualifying unilateral performance determination. Condition that changes the result: Establish incorporation, the ordinary-business or special financial-counterparty branch, and whether the particular decision falls within section 315.
  • Singapore. Material legal route: Contract construction; a properly implied limit on a discretion; the Unfair Contract Terms Act (UCTA) for certain standard-term exclusions or substantially different performance. Condition that changes the result: Shipworks requires a genuine gap before implying a restriction. UCTA is not a general power to reduce any reserve, and its conflict-of-laws restrictions matter.
  • India. Material legal route: The Reserve Bank of India (RBI) PA settlement rule plus contract performance and damages. Condition that changes the result: The agreed settlement timeline must be fair, equitable and transparent. Apply the 2025 directions consolidated in November 2026, not the superseded general 2020 formula.
  • South Africa. Material legal route: Consumer Protection Act (CPA) unfair-term protections for an eligible customer; otherwise ordinary contract and public-policy principles. Condition that changes the result: The relevant CPA transaction protection excludes a juristic customer whose asset value or annual turnover equals or exceeds R2 million at the time of the transaction. Eligible customers must satisfy the Act’s territorial and service scope. Beadica governs the separate public-policy analysis of enforcement.
  • Brazil. Material legal route: Central Bank of Brazil (BCB) Resolution 264 article 8 controls specified captured-value reserves in Brazilian Payment System arrangements based on post-paid or demand-deposit accounts. Condition that changes the result: The reserve must match actual risks and have contractual terms, conditions and purposes. Constituted receivables already allocated to receivables-negotiation contracts have separate protection.
  • Mexico. Material legal route: Contractual performance, good faith, damages and conditional financial-user complaint mechanisms. Condition that changes the result: Prove the settlement obligation and the provider’s legal category. Registration as a network aggregator alone does not establish the jurisdiction of the National Commission for the Protection and Defence of Financial Services Users (CONDUSEF).

The sources for these routes differ in weight: statutes and regulations impose rules; judgments explain particular legal tests; regulatory complaint schemes have their own eligibility; private terms establish promises only where applicable. None supplies a universal maximum reserve percentage.[31][32][30][33][34][35][36][37][38][39][40][41][8][22][42][43][44][45][46]

Brazil’s rule supports a particularly concrete challenge: request the risk model and transaction reconciliation, identify actual versus contingent liabilities, and demonstrate the excess or a prohibited reduction of allocated receivables. Do not confuse it with the separate short deadlines in article 7 for cancelling certain receivables arrangements. Those provisions do not create a general two-day reserve-release right.[44]

Nigeria’s CBN Consumer Protection Regulations can cover an entity using a regulated institution’s services. Contract changes require express permission and notice. Where funds are withheld to secure repayment before it is due, section 3.2.9 requires written customer authorisation. A reserve agreement may provide that authorisation; identify its scope, the repayment being secured and its due date before alleging a breach. The separate unfair-terms rules also constrain notice and unspecified unilateral-change powers.[47]

Australia and New Zealand: similar fairness language, different routes

For a standard-form Australian financial-services contract, the small-business route in the Australian Securities and Investments Commission Act (ASIC Act) includes an upfront-price ceiling of A$5 million and the employee or turnover test: fewer than 100 employees or turnover below A$10 million for at least one qualifying business party. The expanded regime generally applies to contracts made or renewed from 9 November 2023 and, for an older contract, to terms varied or added from that date. An unchanged older term needs the earlier regime’s eligibility and remedy analysis.[48] The unfairness test requires all three elements: significant imbalance, lack of reasonable necessity to protect legitimate interests, and detriment if applied or relied on. Transparency and the whole contract matter; the benefiting party bears the statutory burden concerning necessity.[49]

An eligible party can seek a court declaration and the applicable statutory remedies. ASIC’s PayPal litigation concerned a term requiring merchants to notify fee errors within 60 days. It demonstrates scrutiny of merchant-facing terms; it is not a ruling that reserves are inherently unfair.[49][50]

In New Zealand, the relevant small-trade relationship must fall below NZ$250,000 including goods and services tax annually under the statutory initial-relationship test. The small-trade regime generally covers contracts entered into, varied or renewed from 16 August 2022; an unchanged earlier contract falls outside that extension.[51] The measure is contractual consideration, not automatically the merchant’s gross card sales. For ordinary small-trade contracts, the Commerce Commission must seek the unfair-term declaration; the merchant may ask it to do so. The private direct-application exception concerns grocery supply contracts. A merchant still may have a separate matured-debt or breach claim, but should not assume the Australian private declaration route applies.[52][53]

The Middle East: identify the regime before choosing the remedy

For the UAE onshore branch, the Civil Transactions Law effective 1 June 2026 requires contractual performance in good faith. Its adhesion route concerns uniform conditions closed to negotiation; article 223 allows a court to modify unfair conditions or exempt the adhering party. Earlier acts and facts need the law’s temporal analysis. For a change to retail-payment contract terms, article 14 of the Retail Payment Services and Card Schemes Regulation (RPSCS) requires at least 30 calendar days’ notice and the specified free exit. Covered small and medium-sized enterprise customers of banks and finance companies have a 60-calendar-day change-notice rule under a separate regulation effective 13 September 2026, which also prohibits abusive or unreasonable terms. Establish whether the provider changed a term or exercised an existing reserve clause.[54][55][56]

A Dubai International Financial Centre (DIFC) court clause does not itself make an onshore provider subject to Dubai Financial Services Authority (DFSA) money-services conduct rules. A DFSA-regulated service has its own client-money and payment-user requirements. ADGM (Abu Dhabi Global Market) likewise separates its courts’ jurisdiction from the regulatory coverage of its Financial Services Regulatory Authority (FSRA). The ADGM Conduct of Business Rulebook edition in force on 19 November 2026, dated 16 September 2026, has a defined list of written corporate-user opt-outs; safeguarding and its payment complaint rule are not on that list. The Virtual Assets Regulatory Authority’s perimeter concerns virtual-asset activity in Dubai outside DIFC; an ordinary fiat acquiring dispute requires the applicable payment-services regime.[57] Identify the actual regulated activity and the institution holding the money.[58][59][60][61]

For Saudi Arabia, article 67 of the Saudi Central Bank (SAMA) implementing regulations requires the covered PSP’s contracts to balance the parties’ rights and obligations and treat the payment-service user fairly. Article 73 specifies grounds for refusing a payment order or suspending an account; its refusal provisions require reasons, corrective information and restoration once the ground ends. Article 78 requires funds received by the payee’s PSP to become available immediately, subject to necessary currency conversion. Require the provider to identify the lawful basis for any separate reserve. The Saudi Civil Transactions Law adds relevant performance and adhesion principles. Covered payment disputes proceed to the Banking Disputes Committee’s special circuit after the prescribed amicable stage, which ordinarily lasts no more than 30 days unless extended by written agreement.[62][63][64][65]

A termination warning deserves its own review

Check whether the provider is merely warning, has suspended a service or has actually terminated a contract. Preserve the dates, reasons, notice clause, cure requirements and effect on remaining funds. Termination may stop new processing while chargeback and repayment obligations continue under valid terms.

The UK has an important date branch. The 2026 amendments distinguish qualifying indefinite framework contracts entered before 28 April 2026 from those entered on or after that date. The later branch generally requires 90 days’ notice with specific reasons and complaint information, subject to statutory exceptions and any permitted corporate opt-out; the earlier branch generally uses the two-month rule. These are not interchangeable rules for every reserve notice, and a reserve increase is not automatically termination.[30][66]

Test the monitoring calculation and the reserve separately

Ask whether the provider relies on a legal duty, a network identification, an acquiring-bank instruction or its own contract. Obtain the actual notice and identify the counted population, month, merchant ID, numerator, denominator, exclusions, regional version, assessment and exit criteria. Correct the inputs before debating the result.

Visa’s 2025 Acquirer Monitoring Program fact sheet is useful evidence of regional differences and a scheduled April 2026 change. It also expressly deferred implementation details for Brazil, Chile and India. It should not be treated as a complete November 2026 global rulebook. Mastercard’s August 2026 Security Rules refer excessive-chargeback criteria to another programme manual; the public text uses the current month’s chargebacks against the preceding month’s transactions for its basis-point calculation. A merchant should obtain the operative programme document from its acquirer before accepting a threshold or assessment.[67][13]

Even a correctly calculated ratio does not determine whether a specific customer was dishonest or whether the provider’s reserve complies with local law. Conversely, correcting a monitoring error does not remove an independently established contractual exposure. Remediation should address the actual cause: stronger payment authentication, reliable delivery, clear recurring-payment consent, effective cancellation, prompt refunds or better evidence handling.

Are held funds protected if the provider fails?

The answer turns on the money’s legal character and the institution holding it. “Reserve”, “balance” and “segregated” are not interchangeable legal conclusions.

  • EU, UK, France and Germany. Protection that may apply: Covered payment-institution execution funds have specified safeguarding requirements; national law determines insolvency implementation. Why a reserve still needs individual classification: A bank deposit, payment-execution fund, valid collateral transfer and ordinary intermediary debt differ. Outsourcing does not simply remove the regulated institution’s own duties.
  • Canada. Protection that may apply: Retail Payment Activities Act section 20 protects qualifying held end-user funds using prescribed arrangements. Why a reserve still needs individual classification: Bank of Canada guidance expressly treats money reserved specifically for chargeback or fraud risk as outside its interpretation of held funds requiring safeguarding.
  • Singapore. Protection that may apply: Payment Services Act section 23 and regulations impose safeguards on relevant money for covered merchant acquisition. Why a reserve still needs individual classification: Specified debts/fees are excluded; the foreign-entity merchant exemption requires both the statutory foreign-entity conditions and written notice that funds are not safeguarded.
  • India. Protection that may apply: Non-bank PAs must use the prescribed escrow arrangement, with restricted movements and reconciliation. Why a reserve still needs individual classification: Identify whether the balance is merchant-payable settlement, permitted refund/reversal money or another category; an escrow label does not settle every claim to distribution.
  • UAE and Saudi Arabia. Protection that may apply: Applicable onshore or financial-free-zone rules protect defined user funds; SAMA has specific safeguarding and insolvency-return provisions. Why a reserve still needs individual classification: The activity, licence, account, beneficiary and corporate elections matter. The UAE onshore RPSCS uses 24 hours to distinguish safeguarding methods; payout timing follows the separately applicable rule and contract.
  • Brazil and Mexico. Protection that may apply: Brazil protects specified payment-account and settlement resources; Mexico’s financial technology institutions (ITF) law separates specified undelivered client resources. Why a reserve still needs individual classification: Identify the exact settlement stage and institution. Mexico’s ITF provisions do not cover every aggregator or every reserve.
  • Australia and New Zealand. Protection that may apply: Particular licensed-service client-money or genuine trust arrangements can protect beneficial interests. Why a reserve still needs individual classification: Ordinary processor debts are not automatically within those regimes; New Zealand has no general payment-provider licence that itself guarantees every balance.

The applicable safeguarding provisions and official interpretations determine these classifications.[6][68][69][70][71][72][73][74][8][54][59][61][62][75][76][77][78][79]

The Canadian exception is especially relevant to a rolling reserve. The regulator’s interpretation does not establish that the reserve was lawfully imposed; it explains why a merchant cannot infer insolvency protection from the PSP’s registration. In Singapore, foreign incorporation alone is insufficient for the merchant exemption: the entity also must not carry on business in Singapore, and the prescribed written notice is required.[72][74]

For the United States, Bankruptcy Code section 541(d) distinguishes a debtor’s bare legal title from another party’s equitable interest. In South Africa, Directive 1/2007 does not itself establish that every reserve is an insolvency-protected trust. In Nigeria, first establish the settlement bank and whether the non-bank operator held any funds at all. Across these branches, obtain the account designation, trust or escrow document, beneficiary ledger, permitted deductions and reconciliation before claiming proprietary priority.[80][81][9]

Build one evidence dossier for the disputes and the hold

  • Identity and authority. Evidence to preserve: Legal entities, licences, signed agreements, amendments, agency documents, merchant IDs and payout account. What it proves or tests: Correct debtor, governing law, forum, accepted terms and representative authority.
  • Sale and payment consent. Evidence to preserve: Checkout terms, offer, order, recurring mandate, authentication result, account linkage and cancellation history. What it proves or tests: What was bought, who authorised payment and which obligations continued.
  • Service performance. Evidence to preserve: Delivery or activation events, access logs, usage, service status, promised dates and customer communications. What it proves or tests: Receipt or performance against the specific allegation; keep original timestamps and provenance.
  • Dispute handling. Evidence to preserve: Reason code, issuer material, notice, portal deadline, packet, upload receipt, rejection and stage decisions. What it proves or tests: Timeliness, available response and any provider handling breach.
  • Money and risk. Evidence to preserve: Transaction ledger, settlement statements, refunds, reversals, fees, reserve movements, assignments and guarantees. What it proves or tests: Net amount due, residual exposure, duplicate debits and collateral overlap.
  • Loss and urgency. Evidence to preserve: Cash forecast, imminent obligations, available liquidity, mitigation, lost contracts and enforcement-risk evidence. What it proves or tests: Caused recoverable loss and the separate grounds for interim relief.

Keep originals and a readable index linking every item to the transaction or reserve cohort. Record who exported the data and how the system generated it. Limit disclosure to material the recipient needs and use the provider’s approved secure channel; a dossier should not expose unnecessary card or customer data. South Africa’s electronic-evidence statute, Singapore’s processor litigation and the applicable procedural rules make reliability and provenance material to whether the evidence supports the claim.[23][12]

Escalate towards a remedy the forum can actually give

Begin with a formal notice to the correct obligor. State the accepted agreement and clause, amount and event challenged, factual error or legal objection, and requested result. Attach a concise reconciliation and indexed evidence. Ask separately for payment already due, correction of duplicates, reasons or accounts where owed, and a proposal for the remaining contested exposure. A defined review date and staged release can be negotiated without conceding liability for every dispute.

Complaint routes vary materially:

  • Canada: the payment-card Code provides provider/network escalation for a Code-related complaint. The Financial Consumer Agency of Canada (FCAC) supervises compliance rather than deciding individual compensation.
  • UK and Germany: eligible UK businesses may use FOS; Germany’s relevant conciliation arrangements can include business payment-service customers. Establish the provider, subject matter, limits and procedural exclusions before choosing the route.
  • Singapore and India: the Financial Industry Disputes Resolution Centre (FIDReC) requires the relevant business and subscriber eligibility; pure commercial-policy issues can be excluded. RBI authorisation of a PA does not by itself establish coverage under the 2026 Ombudsman scheme.
  • UAE and Saudi Arabia: Sanadak has its own customer, institution and procedural scope; DIFC and ADGM have separate gateways. Saudi covered payment disputes use the specialist committee route after the required preliminary process.
  • Nigeria: an entity using covered financial services can qualify under the CBN regulations. Begin with the institution’s internal dispute process. Section 6.4.1 permits escalation for failure to acknowledge within three days, sets a 90-day period after receipt of the institution’s decision, and limits overlap with alternative dispute resolution or litigation. Before seeking urgent relief, establish the court or arbitration route against the agreement, defendant and banking relationship.[47]
  • Mexico: for a qualifying financial institution and service, the user can approach the institution’s specialised user-service unit (UNE) or CONDUSEF. The UNE must answer in writing within 30 business days. CONDUSEF’s complaint period is generally two years under the statutory accrual branches; conciliation, consensual arbitration and an executable opinion have separate monetary and substantive conditions. An ordinary aggregator outside the statutory institution definition requires the contractual or commercial route.[45]
  • Australia and New Zealand: check the provider’s membership and the relevant dispute scheme. New Zealand’s Banking Ombudsman rules distinguish excluded commercial security judgments from complaints about misapplied policy or obligations. An unfair-term report to the Commerce Commission is a separate route.

These processes do not all suspend scheme deadlines, contractual notices or court limitation periods. Check the specific rule before relying on a pause.[82][83][84][85][86][87][88][89][90][62][47][45][91][52]

Court or arbitration: match the order to its proof

For a debt or release order, establish the correct debtor, due date, net sum and absence of a valid continuing retention right. For damages, identify the breached duty, causation, recoverable loss, mitigation and any valid limitation. For accounting or disclosure, identify the contractual, statutory or procedural basis. For interim protection, prove its additional conditions and address security or an undertaking for wrongful relief.

The differences are practical. France’s commercial provisional-payment route concerns an obligation that is not seriously disputable. Brazil’s urgent-relief test examines probability of the right and danger to the useful outcome, with reversibility and security considerations. German and Mexican attachment procedures principally secure recovery. For a UAE attachment ordered by the expedited-matters judge, article 250(2) requires the substantive claim within eight days of the attachment decision; the order preserves property pending determination of the claim.[92][93][94][95][96]

In US federal court, Grupo Mexicano limits an ordinary equitable freeze of unencumbered assets to secure a prospective contract money judgment. State-law attachment under Rule 64 and genuine proprietary claims require separate analysis. Winter adds the preliminary-injunction requirements. In Canada, an order compelling positive action uses the stronger prima-facie merits test for a mandatory interlocutory injunction, alongside irreparable harm and convenience. A threatened cash shortfall does not remove these requirements.[97][98][99][100]

In South Africa, interim relief requires a prima facie right, the relevant injury, balance of convenience and lack of adequate alternative protection. An urgent application also must explain why ordinary proceedings cannot give substantial redress. The actual contract can select arbitration: Paystack’s published South African Merchant Agreement chooses Arbitration Foundation of Southern Africa commercial arbitration seated in Johannesburg. A CPA enforcement claim has its statutory complaint and exhaustion conditions; an ordinary contractual claim needs its own jurisdictional basis.[22][101][29][102][103]

Where evidence establishes urgency or a threat to enforcement, assess an available interim application alongside the dispute and complaint tracks, while complying with any mandatory preliminary step. The whole route, from the first notice to release or court relief, runs in these steps:

  • Dispute or hold notice. Next: identify debtor, reason and deadlines.
  • Identify debtor, reason and deadlines. Next: live scheme response available?
  • Live scheme response available? Yes: submit reason-specific evidence and retain receipt. No: record final stage and any handling breach.
  • Submit reason-specific evidence and retain receipt. Next: reconcile reserve and test authority.
  • Record final stage and any handling breach. Next: reconcile reserve and test authority.
  • Reconcile reserve and test authority. Next: proved amount due or excess retained?
  • Proved amount due or excess retained? Yes: demand payment, accounts or partial release. Unresolved: obtain missing terms, risk data and fund classification.
  • Obtain missing terms, risk data and fund classification. Next: demand payment, accounts or partial release.
  • Demand payment, accounts or partial release. Next: agreement or eligible complaint resolves it?
  • Agreement or eligible complaint resolves it? Yes: record release, credits and surviving claims. No: choose competent court or arbitration.
  • Choose competent court or arbitration. Next: seek only supported final or interim relief.

Preserve surviving claims without collecting twice

A reversed card payment can leave a genuine price debt, but only where the sale obligation survives the customer’s defences and any binding resolution. A customer who validly cancelled, received no contracted service or never authorised the relevant obligation may owe nothing. A claim against the provider instead may concern an incorrect debit, breach in handling or unlawful delay. Identify the buyer separately from the cardholder: unauthorised use of someone else’s card does not by itself extinguish the buyer’s purchase obligation. Establish which claim exists before choosing the defendant.[6][5]

Maintain a single recovery ledger. Credit every refund, chargeback reversal, representment credit, settlement and payment against the relevant loss. Tell the acquirer when a customer refund has posted so it can be addressed in the dispute process. A negotiated release should state how later successful disputes, residual chargebacks, fees and final closure will be treated, and which claims are preserved or settled.[1][4][104]

Finally, compare the likely net recoverable amount and provable additional loss with legal fees, scheme escalation charges, security requirements, management time, adverse-cost exposure and collectability. An unsupported full-reserve fight may be less useful than a documented claim to an aged, undisputed tranche. Conversely, a recurring error or a material threat to the business can justify urgent action where the legal test is met. Use the actual contract, evidence and forum to make that decision; there is no reliable universal success rate or standard litigation price.

For the earlier procurement and contract-design decision, see Payment Processor Selection for IT Businesses. Different rails need different analysis: automated clearing house (ACH) return risk, Single Euro Payments Area (SEPA) direct debit models and stablecoin refunds after fiat settlement. Their return, refund and actor rules should not be imported into a card chargeback.

Sources

Each source identifies the authority and relevant provision. Network and provider documents retain their private contractual status. English summaries of foreign-language legislation are paraphrases; the identified controlling text governs.

  1. Visa Core Rules and Visa Product and Service Rules, 24 October 2026, §11.3, Tables 11-2 and 11-3, pp 675–680; §11.8.5.4, Table 11-30, p 712; §§11.11.2.4 and 11.11.2.6, Tables 11-93 and 11-95, pp 755–756 and 760–761.
  2. Mastercard Chargeback Guide, Merchant Edition, 13 May 2025, Dual Message cardholder disputes, pp 127 onward; non-receipt, pp 149 onward; unauthorised transactions, pp 410 onward; relevant regional and Single Message branches.
  3. Stripe Services Agreement: service terms, modified 28 September 2026, Financial Services §§3.3–3.4; applicable EEA, UK and US regional provisions in §5.
  4. CFPB Regulation Z §1026.13 and official interpretations, version 8 April 2026, §1026.13(a)(1), (a)(3), (b), (c); comments 13(a)(3)-1–3 and 13(c)(2).
  5. CFPB Regulation Z §1026.12 and official interpretations, version 8 April 2026, §1026.12(b)(1), (5); (c)(1)–(3), and the relevant official interpretations.
  6. Directive (EU) 2015/2366 (PSD 2), consolidated 17 January 2025, Arts 2, 4(5), (9), (10), (21), (44), 10, 19(6), 20, 38, 54–55, 61, 71–77, 87, 89, 101–102.
  7. Mastercard Rules, 2 June 2026, Chapters 5 and 7: acquiring, merchant, payment-facilitator and sponsored-merchant relationships.
  8. Reserve Bank of India (Regulation of Payment Aggregators) Directions, 2025, 4(i), (j); 5; 8; 9; 10; 13(g), (h); 14; 16/Table 1; 17; 18; 19–23/Annex 3.
  9. CBN Regulatory Framework for Non-Bank Acquiring 2021, §§2, 3, 5, 6, 12.
  10. Paystack Nigeria: Merchant Agreement, A§20, Dispute Resolution; B, Specific Payment Methods, card-payments paragraph 1(3); D§3(1)–(4), Settlement, Payout and Disputes; D§4(2), Reserves. Published provider terms as at 19 November 2026.
  11. SARB: payment-system-management transition Q&A, 7 September 2026, Questions 3, 8, 12, 17 and 22.
  12. B High House International Pte Ltd v MCDP Phoenix Services Pte Ltd [2023] SGHC 12, Paragraphs 1–6, 255–257, 298 and 301.
  13. Mastercard Security Rules and Procedures, Merchant Edition, 4 August 2026, §§6.2.2.9 and 8.3, pp 87–88; rules page.
  14. CFPB Regulation E §1005.11, §1005.11(a)–(d); scope in §1005.3.
  15. Quebec OPC: cancellation of online purchases, refunds and chargebacks, Qualifying cancellation, refund default, issuer request and transaction exceptions.
  16. Consumer Credit Act 1974 s 75, s 75(1)–(3), read with s 12(b), (c).
  17. Code monétaire et financier L 133-2, L 133-2.
  18. German Civil Code (BGB) §675e, Subsections (1)–(4).
  19. MAS E-Payments User Protection Guidelines, effective 16 December 2024, Paragraphs 1.2, 4.1, 5.1 and 6.1; footnotes 2–3.
  20. RBI (Commercial Banks: Responsible Business Conduct) Directions 2025, 3; 67–75.
  21. RBI (Commercial Banks: Responsible Business Conduct) Third Amendment Directions 2026, 3(2).
  22. Consumer Protection Act 68 of 2008, ss 1 (consumer/service/juristic person), 5–6, 48–52, 54, 69–70.
  23. Electronic Communications and Transactions Act 25/2002, s 15; ss 42–47; s 1 consumer definition.
  24. Banking Ombudsman chargebacks guide, Chargeback process; complaints from merchants.
  25. ASIC ePayments Code, cl 2.1 and unauthorised transactions chapter.
  26. Código de Defesa do Consumidor, Lei 8.078/1990 updated, arts 2–3, 20, 35, 49, 51, 54-G.
  27. Ley para la Transparencia y Ordenamiento de los Servicios Financieros, arts 2 Bis, 3, 4 Bis 3, 23, 49 Bis.
  28. Banco de México Circular 34/2010, compiled credit-card rules, §2.3 Bis, paragraphs 3–4; §2.6(a); §§3.3–3.6.
  29. Paystack South Africa: Merchant Agreement, A§19, Dispute Resolution; D§3(3), Payout Schedule; D§3(4), Reserve; D§1, Fees and Fines. Published provider terms as at 19 November 2026.
  30. Payment Services Regulations 2017, text as at 19 November 2026, Regulations 23, 40, 50–51D, 63, 76–77, 89, 101 and 148.
  31. California Civil Code §1670.5, Subsections (a)–(b).
  32. Wastech Services Ltd v Greater Vancouver Sewerage and Drainage District, 2021 SCC 7, Paragraphs 63 and 88–94, read with the contract and disposition.
  33. Braganza v BP Shipping Ltd [2015] UKSC 17, Paras 17–20, contextual contractual discretion doctrine.
  34. Code civil 1171, Art 1171.
  35. Code civil 1231-1, Art 1231-1.
  36. Cour de cassation, commerciale, 26 January 2022, no 20-16.782, Paras 4–7, 9–11; partial cassation.
  37. BGB 307, §307(1)–(3).
  38. German Civil Code (BGB) §310, Subsections (1) and (1a).
  39. BGB 315, §315(1)–(3).
  40. Unfair Contract Terms Act 1977, ss 3, 11, 13, 26, 27; First Schedule.
  41. Shipworks Engineering Pte Ltd v Sembcorp Marine Integrated Yard Pte Ltd [2026] SGHC(A) 22, Paragraphs 225–232, especially 226–228.
  42. GN 294, Determination of threshold under CPA, Determination and schedule; Gazette 34181, 1 April 2011.
  43. Beadica 231 CC v Trustees for Oregon Trust [2020] ZACC 13, Majority paragraphs 36–38 and 71–80.
  44. BCB Resolution 264/2022, version as at 19 November 2026, Articles 1, 7 and 8, especially article 8 §§1–4; article 7 as amended by Resolution 562/2026.
  45. Ley de Protección y Defensa al Usuario de Servicios Financieros, arts 2, 50 Bis, 63, 65–66, 68–68 Bis.
  46. Código Civil Federal, arts 1796–1797, 1949, 2108–2110.
  47. CBN Consumer Protection Regulations, 2019, Sections 2, 3.2.5, 3.2.8–3.2.9, 3.3, 6.3.19 and 6.4.1; glossary.
  48. Treasury Laws Amendment (More Competition, Better Prices) Act 2022, Section 2; Schedule 2 item 79, inserting ASIC Act §342(2)–(6); reform commencement 9 November 2023.
  49. Australian Securities and Investments Commission Act 2001, Sections 12BF–12BK, 12GD, 12GF, 12GJ, 12GM and 12GND–12GNG.
  50. ASIC v PayPal Australia Pty Limited [2024] FCA 762, Orders; paras 27–36, 45–56.
  51. New Zealand Fair Trading Act 1986, Schedule 1AA, Part 1 clause 1 and Part 2 clause 2; small-trade commencement 16 August 2022.
  52. New Zealand Fair Trading Act 1986, Sections 26B–26E, 37–43B and 46H–46M.
  53. Commerce Commission: unfair contract terms for businesses, Ordinary small-trade and grocery-supply routes; Commission applications.
  54. CBUAE Retail Payment Services and Card Schemes Regulation, C15/2021, Articles 1, 14(2)–(8), 14(15), 14(24)–(30) and 16; Annex I.
  55. UAE Federal Decree-Law No. 25 of 2025: Civil Transactions Law, Promulgation articles 2–3; law articles 4, 134, 221–223, 227 and 232–234.
  56. CBUAE SME Customer Protection Regulation, C2/2026, Scope; articles 3.10 and 4.12; complaints in article 6; effective 13 September 2026.
  57. Dubai Law No. 4 of 2022 Regulating Virtual Assets, Articles 2–3 and 16; official English translation, with Arabic controlling.
  58. Dubai Law No. 2 of 2025 Concerning DIFC Courts, Articles 7 and 14–15.
  59. DFSA Conduct of Business Module, version 51/07-26, Rules 1.1.1, 6.12.1–6.12.5, 13.1.2 and 13.5.1–13.5.3; Appendices 5 and 7, including A7.2.4, A7.2.6, A7.2.9, A7.2.12 and A7.2.14.
  60. ADGM Courts, Civil Evidence, Judgments, Enforcement and Judicial Appointments Regulations 2015, consolidated including 2025 amendments, ss 16, 34, 41, 48, 65–67, 79.
  61. ADGM FSRA Conduct of Business Rulebook (COBS), VER24.160926, 14.1–14.6; 19.1–19.2, 19.6.1, 19.7–19.10, 19.14–19.15, 19.17–19.22.
  62. SAMA Implementing Regulations of the Payments and Payment Services Law, Articles 48, 51, 53, 57–58, 67, 73, 78, 93–94 and 129–130.
  63. Saudi Law of Payments and Payment Services, Royal Decree M/26 of 22/3/1443H, Articles 13–14 and 20.
  64. Banking Disputes Committee: official jurisdiction page, اختصاص paragraph 2.
  65. Saudi Civil Transactions Law, Royal Decree M/191, 18 June 2023, Articles 1, 94–96, 104 and 107–108; Bureau of Experts English translation.
  66. Payment Services and Payment Accounts (Contract Termination) (Amendment) Regulations 2025, Regulations 1–2; insertion of PSR regulations 51–51D.
  67. Visa Acquirer Monitoring Program fact sheet, 2025, Regional table, scheduled changes and implementation footnotes.
  68. FCA: safeguarding requirements for payment and e-money firms, Requirements effective 7 May 2026; CASS 10A/15 and SUP 3A/16.
  69. Code monétaire et financier L 522-17, L 522-17 I–II.
  70. Zahlungsdiensteaufsichtsgesetz (ZAG), §§1(1), (9), 17, 26, 60–62.
  71. Canada Retail Payment Activities Act, Sections 2, 4–10 and 20; commencement provisions and scope exclusions.
  72. Bank of Canada: Safeguarding end-user funds, December 2024, Paragraphs 1.3–1.9, especially 1.8; paragraph 2.1.
  73. Payment Services Act 2019, section 23, s 23(1), (2), (6), (7), (14).
  74. Payment Services Regulations 2019, regs 14–17 and 32(1)–(5).
  75. Lei 12.865/2013 updated text, arts 6, 12, 12-A, 12-B, 12-C, 13.
  76. Ley para Regular las Instituciones de Tecnología Financiera, arts 4 II/XVI, 46–47.
  77. Corporations Act 2001, authorised compilation as at 19 November 2026, Sections 981A–981H.
  78. FMA e-money and payment service providers, Licensing/registration and trust versus debt sections.
  79. FMA: client money or property service providers, Scope and obligations; Financial Markets Conduct Act §§431W and 431ZC–431ZH.
  80. 11 USC §541, Subsections (a) and (d).
  81. SARB Directive 1/2007: payments to third persons, §§1.3.4, 2, 3.1.1–3.1.6, 4.3.
  82. Code of Conduct for the Payment Card Industry in Canada, 30 October 2024, Scope, policy 1, complaint-handling process and Annex A.
  83. FCAC: complaints under the payment-card Code, Complaint steps, response periods, network escalation and FCAC’s role.
  84. Financial Ombudsman: who we can help, Small business/micro-enterprise criteria; linked/partner enterprises.
  85. Bundesbank Schlichtungsstelle competence and leaflet, pp 2–5; competence webpage.
  86. FIDReC General FAQs, Questions 2, 3, 10, 12 and 19.
  87. FIDReC Jurisdiction, Mediation/adjudication limits; exclusions.
  88. RBI FAQs: Reserve Bank Integrated Ombudsman Scheme 2026, Coverage; eligibility; time bar; nonmaintainability; award/appeal.
  89. Sanadak: Complaint Eligibility, Eligibility questions/rejection grounds.
  90. Sanadak FAQs and regulations page, Eligibility, time bar, LFI disputes.
  91. Banking Ombudsman Scheme Terms of Reference, Definitions; clauses 2–9, 19–21, claims/remedies section.
  92. Code de procédure civile 873, Art 873 first and second paragraphs.
  93. Brazilian Code of Civil Procedure, Lei 13.105/2015, Articles 21, 25, 46, 63, 294–302, 373, 396–400 and 550–552.
  94. German Code of Civil Procedure (ZPO), §§916(1), 917 and 920; §916 and §920.
  95. Código de Comercio, arts 1092–1093, 1104, 1168, 1175, 1194, 1298-A; arbitration 1424–1425.
  96. UAE Federal Decree-Law No. 42 of 2022: Civil Procedure Code, Articles 247–263, especially article 250(2).
  97. Winter v Natural Resources Defense Council, 555 US 7 (2008), Page 20, preliminary-injunction requirements.
  98. Federal Rules of Civil Procedure, 1 December 2025, Rules 64 and 65, printed pp 88–89.
  99. Grupo Mexicano de Desarrollo v Alliance Bond Fund, 527 US 308 (1999), Pages 310, 318–333; holding at p 333.
  100. R v Canadian Broadcasting Corp, 2018 SCC 5, Paragraphs 15–18.
  101. MEC for Economic Development, Gauteng v Vilakazi [2024] ZASCA 126, Paragraphs 39–42 and 51; operative order.
  102. South African Uniform Rules of Court, Rule 6(12)(a)–(b), read with the January 2026 amendment to (c).
  103. South African GNR 6975, 24 December 2025, Sections 5 and 15; Rule 6(12)(c) amendment effective 30 January 2026.
  104. Brazilian Civil Code, Lei 10.406/2002, Articles 187, 389, 402–403, 421–424 and 884.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.