Refund Transaction

Overview

A refund transaction is the distinct financial record used to return value against an original payment. It has its own identifier, amount, currency, destination, route, status, timestamps, fees, and settlement evidence while preserving an immutable link to the payment being refunded.

For Refund Transaction, the workflow must preserve the original payment, eligible amount, reason, destination, rail rules, fees, exchange-rate treatment, approval, refund transaction, provisional postings, and final customer or merchant balance. A Refund Transaction records execution, routing, status, and financial effect; a Refund Receipt only communicates evidence about that transaction and cannot establish completion independently. The record should remain linked to the original payment and preserve eligibility, amount, reason, destination, approvals, deadlines, execution reference, fees, and settlement outcome.

Refund Transaction should remain distinct from Refund and Refund Processing, because each can represent a different stage, record, control, or financial outcome.

For Refund Transaction, the principal failure modes are wrong destinations, duplicate returns, missed dispute deadlines, excessive amounts, unsupported reversibility assumptions, exchange-rate differences, fees not returned, unauthorized manual action, and provisional postings treated as final. Important failure modes include excessive amounts, wrong destinations, missed deadlines, unauthorized manual action, unsupported reversal assumptions, fee differences, and provisional postings treated as final.

Controls should prevent duplicate returns, verify the destination and refundable balance, record exchange-rate treatment, and distinguish a requested refund from a submitted or finally settled transaction. For Refund Transaction, the authoritative record and completion rule should be documented before any irreversible operational, customer, or accounting action is released. Teams using Refund Transaction should preserve the evidence behind each decision so retries, corrections, support reviews, and audits can reproduce the final outcome.