Refund Callback
Pronunciation: REE-fund KAWL-bak
Definition
A refund callback is an asynchronous server-to-server notification reporting a change in a refund request’s processing or settlement status.
Overview
Context and purpose
Durable processing, status queries, replay tools, and reconciliation should resolve remaining delivery gaps across systems. Marking a refund settled from an unauthenticated event can create financial misstatement. Applications use the event to update orders, customer communication, support tools, and accounting workflows. A callback may also describe provider completion before a bank, network, or blockchain reaches the merchant’s desired finality. The Refund Callback path should preserve ordering and duplicate evidence so delayed delivery cannot silently overwrite a newer state. Receivers should verify authenticity, validate refund and original-payment identity, compare amount and currency, deduplicate atomically, and enforce legal state transitions. The provider may notify the merchant when a refund is accepted, processing, completed, failed, rejected, or canceled. Callbacks can be forged, duplicated, delayed, or delivered out of order. Business actions triggered by Refund Callback should be idempotent and should verify the current object state before fulfillment or accounting updates.
How it works
A refund callback reports a refund operation’s status; it does not reverse the original crypto transaction. The new transfer may use a different destination and carry its own network fees and confirmation stages.
Practical checks and failure points
Link original charge, refund ID, authorization, recipient address and outgoing transaction; deduplicate callbacks.
Related concepts
Example
A $30 refund request produces a callback saying processing. The merchant should not tell the customer that funds arrived until the actual refund transfer is confirmed.
Comparison
Refund status and original invoice paid status can both remain true at the same time.
Key Takeaway
Link original charge, refund ID, authorization, recipient address and outgoing transaction; deduplicate callbacks.
Sources
- IETF RFC 9110 — IETF (2026-07-30)
- OpenAPI Initiative Documentation: V3.2.0 — OpenAPI Initiative (2026-07-30)
- OxaPay Documentation: Webhook — OxaPay (2026-07-30)