Refund Request
Pronunciation: REE-fund ree-KWEST
Definition
A refund request is an instruction asking a payment provider or merchant system to return some or all funds from an earlier payment. Refund Request must define the resource or operation, HTTP method or invocation, path, authentication and authorization, request fields, response schema, errors, idempotency behavior, limits, and version.
Overview
Meaning and scope
A refund request is an instruction asking a payment provider or merchant system to return some or all funds from an earlier payment. Refund Request must define the resource or operation, HTTP method or invocation, path, authentication and authorization, request fields, response schema, errors, idempotency behavior, limits, and version.
Mechanism and operation
Applications should create a stable internal intent, verify eligibility and remaining amount, enforce authorization and approval policy, and use provider idempotency. The request usually identifies the original payment, amount, currency or asset, reason, reference, and sometimes a destination. It creates a refund lifecycle that may progress through review, acceptance, processing, completion, rejection, or failure. A timeout can leave the system uncertain whether the provider accepted it. They must store external identifiers, reconcile uncertainty before retry, track final settlement, and communicate status accurately to the customer. A successful transport result from Refund Request should not be interpreted beyond the exact API state documented by the provider.
Practical payment example
A customer asks to return funds for an overpaid order. The merchant records the original invoice, approved refund amount and recipient verification before passing the request to payout execution.
Operational checks
The Refund Request owner should publish stable error semantics and guidance on whether correction, retry, status lookup, or escalation is appropriate. Data handled by Refund Request should use documented types, units, timestamp rules, nullable fields, and enum behavior to prevent silent interpretation errors. The Refund Request contract should define identifiers, validation, authorization, status semantics, errors, limits, and version behavior at the same boundary.
Distinctions and limits
Submitting a request does not prove that money has returned. Duplicate requests, changed refundable balances, provider fees, exchange-rate differences, and irreversible crypto transfers complicate handling.
Related reading
Related definitions: refund, final settlement.
Example
A customer asks to return funds for an overpaid order. The merchant records the original invoice, approved refund amount and recipient verification before passing the request to payout execution.
Comparison
Duplicate requests, changed refundable balances, provider fees, exchange-rate differences, and irreversible crypto transfers complicate handling. A successful transport result from Refund Request should not be interpreted beyond the exact API state documented by the provider.
Key Takeaway
A refund request begins a controlled lifecycle; it needs authorization, amount checks, idempotency, cautious retry, tracking, and final reconciliation.
Sources
- IETF RFC 9110 — IETF (2026-07-30)
- OpenAPI Initiative Documentation: V3.2.0 — OpenAPI Initiative (2026-07-30)