Written by DROPS.ST.
Before approving a crypto refund transfer, confirm who is requesting it, which order it concerns and the destination the authorised customer intends to use. A copied address in a new message is not enough by itself. DROPS order and customer records give staff useful purchase context, while the shop’s refund approval and transfer process need their own clear controls.
Separate the three decisions
First decide whether a refund is due and its amount. Then establish the appropriate asset and destination through the shop’s verified service process. Finally, have the authorised person approve any transfer using the actual payment arrangement.
Combining those decisions into “customer sent an address, so pay it” gives an impersonator too much influence. An order reference can help locate a purchase, but knowing that reference does not necessarily establish authority over the refund.
The refund currency-policy guide covers the amount and exchange-rate basis. This article concerns where an approved refund is meant to go.
Treat a changed destination as a new instruction
Consider a fictional customer with an approved refund on order EXAMPLE-619. A second message arrives from a different account saying the first wallet is unavailable and asking the shop to use another destination urgently.
The request may be legitimate. It may also be an attempt to redirect the refund. Staff should confirm the change through the shop’s established authenticated or otherwise verified customer-service process, using known contact context rather than trusting the new message alone.
Do not ask for a recovery phrase or private key as proof. Those secrets are not a customer-service credential and should never be part of a refund conversation.
Use a short destination review
Keep the review focused on the transfer being considered.
| Question | What the team needs |
|---|---|
| Which purchase is involved? | The correct order and the refund decision attached to it |
| Who is making the request? | Confirmation through the established customer-service process |
| What asset is intended? | The approved refund asset, clearly named |
| What destination did the customer confirm? | The full current destination through the approved collection method |
| Has the instruction changed? | A fresh confirmation of the change, without losing the earlier context |
| Has this refund already been acted on? | The current refund state before another approval |
| Who may approve the transfer? | The responsible authorised person under the shop’s arrangement |
An address that passes a format check does not prove it belongs to the intended customer. Likewise, a screenshot of a wallet does not settle the customer’s authority to redirect an order refund.
Do not assume the incoming payment supplies the return address
Use the payment system’s supported refund method and destination requirements. Do not improvise a return by copying a field from an incoming transaction.
As an external example, BTCPay Server’s refund documentation asks the customer to supply a refund address and then describes merchant payout approval. That is evidence of a separate refund workflow in BTCPay, not a claim that DROPS uses the same interface or automation.
Bitcoin’s official introductory guidance explains that a completed payment is not undone through a central reversal service. That makes getting the intended destination right before approval particularly important.
Keep support clear while the request is reviewed
Tell the customer what needs confirmation and when the shop expects to provide its next update. Avoid saying “refunded” when the request has only been approved or queued. A clear status prevents customers from chasing a transfer that has not happened yet.
DROPS helps staff work from the order and customer context instead of unrelated messages. In a demo, inspect those records and establish the real refund responsibilities for your setup. Use payment-exception guidance for related underpayment or overpayment questions.
Explore DROPS payment and order management and give your team the context to handle refund questions accurately and confidently.