Customers who cannot find a refund button open chargebacks. The form captures the payment or order reference, the reason, and who to pay back so finance can refund in Stripe or the bank instead of fighting a dispute.
SLA on that inbox should be faster than the chargeback window.
Train support not to waive it in chat without logging it here.
‘Need a refund?’ should not be a scavenger hunt.
Note the processor refund ID on the dashboard row.
A refund request is a finance ticket: they paid, they want the money back, they may or may not be sending goods back. US card networks push people toward chargebacks if you are slow; UK Faster Payments and card refunds have their own clocks. The form’s job is to get a reference that matches a charge—not a novel about feelings, though the details box can hold that too.
Never ask for the full card number. Last four plus order ID is enough. Full PAN collection on a marketing form is a PCI incident waiting to happen.
Unreferenced refund asks become a hunt through three processors and a PayPal.
Partial refunds should be explicit in the details. Guessing the amount is how you refund twice.
Chargebacks are the expensive path. A visible form is cheaper.
Linked from receipts and the footer before they hit the issuer.
You still need a public ticket so customers are not emailing random staff.
Apple and Google own those. Say so on the page if you are an app.
Worse than a chargeback. Offer this form in every dunning email.
Marketing sites stay static while billing lives in Stripe. Put the form so finance sees tickets without a Zendesk seat for every engineer.
US and UK buyers will mention ZIP or postcode when they cannot find the charge; it is a weak match key—prefer order ID—but it can disambiguate two John Smiths.
No. A human or a later Zap hits Stripe, PayPal, or the bank.
Tell them to stop using this form and reply in the issuer’s flow.
Usually yes. Say you cannot send a cheque to a new address without more checks.
Your accounting rules. Capture the amount they want in details.