Home / Wiki / D / Dispute Resolution

Dispute Resolution

Legal Law and EnforcementUpdated 05 Nov 2026

Dispute resolution is the set of processes used to settle a disagreement between parties, for example over whether a payment was authorised, whether goods arrived or whether a contract was performed. In financial services it ranges from informal negotiation and internal complaints handling to card-scheme chargebacks, statutory error-resolution rules, ombudsman services, arbitration and court proceedings. Every payment system needs some way of deciding who bears a loss when something goes wrong.

Methods are often grouped as alternative dispute resolution (ADR), meaning negotiation, mediation and arbitration, versus litigation in court. Payments add scheme-specific processes, such as the chargeback for card transactions, and regulator-backed schemes for consumers. In crypto and peer-to-peer markets, dispute resolution is often the main trusted element that remains after software has taken over custody and settlement.

01

Dispute resolution in plain terms

When two people disagree about a purchase, they first try to sort it out between themselves. If that fails, they may ask the shop manager, then a consumer body, and as a last resort a judge. Each step is slower and more formal than the one before, but each has more power to make the other side comply.

Financial dispute resolution follows the same ladder. A customer complains to the bank or app; if unhappy, they may dispute the charge with the card network, take the case to an ombudsman, or go to arbitration or court. Good systems settle most cases on the lowest rungs, quickly and cheaply.

02

Main methods

  • Negotiation. The parties settle directly, often through a provider's complaints team.
  • Mediation. A neutral mediator helps the parties reach their own agreement but cannot impose one.
  • Arbitration. An arbitrator hears the case and issues a binding award, enforceable internationally under the 1958 New York Convention.
  • Ombudsman schemes. Free, independent services decide consumer complaints against financial firms; the UK Financial Ombudsman Service, set up under the Financial Services and Markets Act 2000, is a well-known example.
  • Litigation. Court proceedings, which are public and appealable but usually slow and costly.
03

Disputes in payment systems

Card networks run structured dispute cycles. A cardholder disputes a transaction with the issuer, which raises a chargeback against the acquirer using a reason code; the merchant can respond with evidence, and unresolved cases can go to network arbitration. Merchants with high dispute ratios face monitoring programmes and fees.

Bank transfers rely more on law than on scheme rules. In the United States, Regulation E sets error-resolution duties for electronic fund transfers: a consumer generally has 60 days after a statement to report an error, and the institution must investigate within 10 business days, or up to 45 days if it gives provisional credit. Push payments such as wire and instant transfers are harder to unwind, which is why authorized push payment (APP) fraud has driven new reimbursement rules in some countries. In the EU, payment service providers must answer complaints within 15 business days, extendable to 35 in exceptional cases, under PSD2 (Second Payment Services Directive).

04

Disputes in crypto and peer-to-peer trading

On-chain transfers are final, so there is no chargeback. Disputes instead arise when one leg of a trade happens off-chain. On P2P trading platforms, the platform holds the seller's crypto in escrow while the buyer pays by bank transfer, and staff decide "appeals" when the seller says the money never arrived. Proposed designs such as bilateral collateral escrow and stablecoin escrow make the process explicit: stablecoin collateral stays locked in a smart contract until an adjudicator rules, and the contract then enforces the ruling.

These systems face hard evidence problems. A screenshot of a bank receipt can be forged, a transfer can be recalled, and money can come from a mule (bank) account. A blockchain oracle or a bank API can supply some facts automatically, and a proof of delivery helps in goods trades, but judgment is still needed. That is why even well-designed crypto markets are not a fully trustless system.

05

Design principles

  • Clear rules agreed in advance. Deadlines, acceptable evidence and remedies should be fixed before a transaction starts.
  • Security for the outcome. A decision is only useful if it can be enforced, which is why disputes are often backed by collateral, reserves or a performance bond.
  • Proportionality. Small claims need fast, cheap routes; large commercial disputes justify formal arbitration.
  • Independence and appeal. Users trust a process more when the decision-maker is neutral and serious errors can be reviewed.

Strong dispute resolution reduces counterparty risk and supports fraud prevention, because cheating becomes less rewarding when losses are reliably reversed or compensated.

Last updated 05 Nov 2026