Disputes, Claims, Returns and Recalls: The Payment After the Payment
It is tempting to think a payment is done the moment it settles. In practice, settlement is just the point where the money moved — what happens after is where a real payment system earns its keep. Goods don't arrive. An amount is entered wrong. A payment turns out to be unauthorised, or simply duplicated. Every mature scheme has a governed way to unwind or correct these, and the vocabulary matters.
Disputes and claims
A dispute (or claim) is a request to review a payment: someone asserts that it should not stand as-is. Common types are unauthorised, goods not received, duplicate, and wrong amount. A dispute doesn't move money by itself — it opens a case. An operator (or an automated rule) works it through a lifecycle: open, under review, and then a resolution — upheld or rejected.
Returns and recalls
When a dispute is upheld, the money often has to go back. Two mechanisms do this. A return sends funds back to the original payer, typically after the payment has settled — in ISO 20022 this is a pacs.004 Payment Return. A recall is a request to claw back a payment, often used when a payment was made in error and hasn't yet been made available to the beneficiary (for example, the SEPA and CHAPS recall flows, or camt.056). The distinction is timing and consent: a return is a new, opposite movement; a recall asks the receiving side to send it back.
How Kibipay models it
In Kibipay, any payment can have a dispute raised against it — from the payment detail screen or via the API — with a type and a reason. Operators work a queue: move a claim to under review, then uphold or reject it. Upholding with a return flips the original payment to RETURNED and records the outcome on the dispute, so the payment's history tells the whole story — settled, disputed, returned — in one place. Because the lifecycle transitions are operator-gated, who did what is auditable.
Why it belongs in the platform, not a spreadsheet
Disputes are where payment operations usually fall back to email threads and manual ledger entries. Pulling them into the same system that moved the money means the claim, the resolution, and the return are one linked record — not three disconnected ones. That is the difference between a payment rail and a payment platform: it doesn't just move money forward, it can govern moving it back.