Resources · 71

Returns and refunds: connect customer cases to payment state

Separate return approval, receipt, requested refunds and confirmed outcomes.

· 3 min

Empty intelligence archive with dossiers and maps AI-generated editorial illustration

What this guide helps achieve

  • Separate the objects
  • Define amounts
  • Handle uncertain states
  • Close with evidence

Quick check

  • Are return and refund states separate?
  • Has the already refunded total been checked?
  • Does the customer message reflect a confirmed outcome?

Step-by-step method

  1. 01

    Separate the objects

    Link orders, lines, returns, payments and refunds with identifiers. An approved return does not establish physical receipt or an executed refund. Define decisions and exceptions under the applicable commercial policy.

    Deliverable: object and transition map.

  2. 02

    Define amounts

    Record quantities, discounts, tax, fees and currency. Check previous partial refunds before another request. Verify provider rules for each payment method rather than generalizing them to every service.

    Deliverable: amount rules and partial cases.

  3. 03

    Handle uncertain states

    Retain the request and identifier before execution. After a timeout, reconcile provider state before retrying. Distinguish received requests, pending states, success and failure in support and customer messages.

    Deliverable: reconciliation protocol.

  4. 04

    Close with evidence

    Replay delayed notifications, repeated events and partial refunds. Check payment, accounting, order and customer information. Issuing a refund and its bank visibility can differ; communicate confirmed information and service-specific timing.

    Deliverable: closure evidence and exceptions.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "currency": "EUR",
    "captured": 100,
    "already_refunded": 30,
    "requested_refund": 80,
    "remaining": 70
}

Expected decision

EUR 70 remains refundable. Block the EUR 80 request and reconcile completed refunds.

Fictional variations to test

30 EUR refunded; two agents each request another 50 EUR.

Against 100 EUR captured, 30 + 50 + 50 = 130 EUR. Serialise the decision or reserve the available amount atomically.

A 30 EUR refund remains pending.

Reconcile it before releasing a reservation or starting a replacement. Pending is neither confirmed failure nor a second budget.

The payment is in EUR but the merchant payout in USD.

Compare the refundable limit in the payment currency. Do not reuse a payout amount expressed in another currency.

Evidence to retain

  • Payment, request and provider identifiers.
  • Executed, reserved and still uncertain amounts.
  • Original currency and final reconciliation result.

Verification procedure

  1. Reconcile payment, currency and completed refunds.
  2. Request more than the balance in a sandbox.
  3. Keep rejection, identifiers and final provider state.

Stripe — Refund and cancel payments

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
CaseOrder, line, return and owner
AmountCurrency, calculation and previous refunds
StateProvider identifier, outcome and customer message

Worked example

Illustrative situation

Fictional example: support retries a partial refund after a missing response.

Decision and expected evidence

Reconciliation finds the original operation. The service retains one effect, displays its actual state and checks order and accounting records.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
Cancellation before captureStop an uncaptured paymentDepends on method and payment state
RefundReturn an already collected amountRequest, outcome and receipt may differ

Management indicators

IndicatorWhat it measuresFirst action
Unreconciled casesRequests without confirmed external stateCheck before retrying
Amount differencesCase-to-payment differencesFix calculations and partial refunds

Common pitfalls

  • Retry without checking the original operation
  • Announce unconfirmed bank receipt

Frequently asked questions

Can a refund be announced when a return is approved?

Not as an executed result. State the confirmed step and next action.

Should repeated clicks create two refunds?

No. Protect against repetition and concurrency and check the amount already refunded.

Does this guide define return rights?

No. It describes operational tracking; commercial conditions and applicable obligations need separate verification.

API amount precision and exact units

Reconcile a refund in the correct unit

A refund amount must preserve the original capture’s currency code and unit. Exact representation alone establishes neither refund authorisation nor sufficient remaining refundable amount.

  • Retrieve the original operation and monetary contract.
  • Compare confirmed integers, currency and refund history.
  • Separate scale, step, rounding and payment state.

Check a unit in the workshop →

Adyen · Currency codes and minor units · Provider documentation · reviewed 2026-11-06

Stripe · Supported currencies and special cases · Provider documentation · reviewed 2026-11-06

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.