Refund
DEFINITION
A refund reverses all or part of a previous subscription charge back to the customer, always tied to the original transaction it is refunding.
TABLE OF CONTENTS
RELATED TERMS
A refund is a transaction that returns all or a portion of the money collected in a previous transaction back to the customer. In subscription billing, a refund is always tied to the original charge it is reversing, not treated as a standalone payment.
Refunds can be full, returning the entire amount of the original transaction, or partial, returning only a portion of it. Every refund transaction references the original transaction it is refunding, which keeps the two linked in the merchant's records and on the customer's statement. A refund can start in more than one way: a merchant can issue it directly through the billing platform, an application can trigger it through the API, it can follow from a chargeback, or a transaction can be marked as refunded because it was already handled outside the system.
Why it matters
Refunds are where customer experience and financial reconciliation meet. Handled well, a refund resolves a billing dispute or service issue without the customer needing to escalate, which protects the relationship and reduces the chance of a chargeback. Left unprocessed or handled poorly, a refund can turn into a disputed charge, which usually costs the merchant more in fees and reputational risk than the refund itself would have. Refunds also touch revenue reporting, so accurate refund records matter for reconciling what a business actually collected in a given period. Recurly ties every refund transaction back to its original transaction by ID, so the reversal is traceable to the specific charge it affects rather than sitting in the books as a disconnected credit.
How a refund is processed
To issue a refund, a merchant reverses all or part of a previously collected transaction on the associated invoice. A few situations are worth understanding before processing one:
A standard refund attempt sends the reversal to the payment gateway, which processes it against the original charge.
If the money has already been returned to the customer at the gateway, or the gateway has another reason it cannot process the refund, the gateway returns a decline instead of completing the refund.
That decline generates an open credit invoice on the customer's account rather than a completed refund.
The merchant then reviews the credit invoice and manually adjusts it to reflect how the refund should actually be recorded, so the financial reporting stays balanced.
This matters most in edge cases, such as a chargeback where the funds already left the merchant's account through a different path and a normal refund would double up the reversal.
Benefits and examples
Consider a subscriber who was billed for a renewal they meant to cancel. The merchant issues a refund for that invoice, which reverses the charge back to the original payment method. If the gateway confirms the reversal, the credit invoice created for that refund closes and the refund completes normally. If the gateway instead declines the attempt, perhaps because the money was already returned through a separate chargeback process, an open credit invoice appears on the account instead, and the merchant resolves it manually so the customer's balance and the merchant's books agree.
Because Recurly generates that open credit invoice automatically at the point of decline rather than letting the refund fail silently, the merchant gets a clear record to reconcile instead of a gap in the books.
Frequently asked questions
What is the difference between a full refund and a partial refund? A full refund returns the entire amount of the original transaction. A partial refund returns only a portion of it, while the rest of the original charge stays with the merchant.
Does a refund always relate back to a specific charge? Yes. A refund transaction includes a reference to the original transaction it is refunding, so the two stay linked in the account's transaction history.
What happens if a refund is declined by the payment gateway? Instead of completing the refund, the gateway decline results in an open credit invoice on the customer's account. The merchant then reviews and manually adjusts that credit invoice to reflect the correct outcome.
Can a refund be issued for a transaction affected by a chargeback? This is one of the situations where a straightforward refund can be declined, since the funds may have already been returned to the customer through the chargeback process. The resulting open credit invoice lets the merchant reconcile it correctly rather than refunding money twice.
Who can initiate a refund? A refund can be triggered by the merchant directly, through the API, or as part of handling a chargeback, depending on how the reversal originated.
