Paddle merchants · Refunds · Customer support
Refund tickets are high-emotion and time-sensitive. The best support workflow is boring: ask for the right info, verify quickly, issue the refund, confirm to the customer, and close the loop — without bouncing between dashboards.
The avoidable mistake
If you handle refunds in a separate billing dashboard, you create delays and mistakes (like refunding the wrong transaction). Put the billing action next to the ticket, and refunds become a 60-second job.
Userscom is built for Paddle merchants. Open the Paddle panel inside a billing ticket, look up the customer by email, view subscriptions and transactions, and issue refunds — without leaving your support inbox.
Yes. The process is the same at a support level. The exact screens and terminology differ by API, but the inputs you need from the customer and the decision-making are consistent.
Ask for the email used at checkout and any identifying reference you can match: subscription details, invoice/transaction info, and the reason for the refund. Keep it short and structured to avoid back-and-forth.
Use a workflow where the refund action sits beside the ticket. In Userscom, the Paddle panel lives inside the ticket so you can look up a customer by email, view transactions, and issue a refund while replying.
Not always. For suspicious patterns, chargeback risk, or policy violations, you may need clarification first. The goal is fast resolution, not automatic approvals.