User guide
Learn each key app flow in order, from sign-in to refunds.
Contact support
Checklist for self-service, three-party refund delays, and links to FAQ and About.
Description
Support can move faster when you send identifiers and context up front—especially for refunds that touched your bank, Store Credit, and a business payout, where tracing takes longer than a single tap.
Refunds vs after-sales vs Customer Support
| Topic | Where to start | Quick rule |
|---|---|---|
| Money back on an order or unused voucher | Refunds, expirations, and support — Cancel, Request Refund, eligibility | Focus on payment reversal and policy windows. |
| Service problem after you already visited (wrong dish, rude staff, etc.) | After-sales requests | Focus on what happened at the venue inside the app’s stated window. |
| You are not sure which applies | Customer support or FAQ | Include screenshots of both screens you tried. |
What to include
| Field | Why it helps |
|---|---|
| Order ID | Identifies the transaction quickly |
| Merchant name | Speeds up investigation |
| Screenshot | Clarifies the current app screen (error text, voucher state, Refund Processing / Refund Rejected, etc.) |
| Attempt time | Helps staff align with processing or redemption logs |
| What you already tried | For example Cancel with Store Credit vs Original Payment, or Request Refund with reason chosen |
If something goes wrong
- You are unsure whether you qualify for a refund → read How refunds work, Refund eligibility, and Legal, then reach out with the table above.
- You already submitted a refund request → include any request ID shown in the app, order ID, and the status label (for example Refund Processing) so support can match the pipeline step.
- After redemption cases often need evidence (receipt, chat with merchant, photos)—attach what the form allows before escalating.
Support entry points: FAQ and About & contact.