Refund communication, not payment execution
Make refund status wording clear without overstating settlement
Review refund communication in your product while leaving actual money movement and settlement verification to your payments systems.
- ✓Whole-order language covers partial work
- ✓Dates sound like guarantees
- ✓Help actions lack state context
Status-screen evidence with financial limits
Partial-refund scope preserved
Keep the refunded item and amount beside the heading that describes them.
Status language with an owner
Have payments stakeholders approve what each visible state means before handoff.
No implied settlement proof
Distinguish a captured confirmation from evidence that funds reached an account.
Treat this as your product's status screen
This review concerns refund information shown in your customer's product, not a refund service provided by Retick. Prepare synthetic orders showing requested, approved, and completed display states, including a partial refund. Capture the amount, currency, item scope, status explanation, and next-step guidance. Record which wording your payments owner has approved. A screen that says Completed does not independently establish that funds reached a customer's account or that a payment provider accepted the transaction.
Capture the change in refund scope
Record switching between an order summary and the detail for one partially refunded item. Include a narrow viewport where explanatory text wraps. A distinctive issue is Partial refund detail uses a heading that says Entire order refunded. Show both the item-level amount and the misleading heading. Keep an inconsistent label separate from a discrepancy in the displayed amount; neither observation by itself identifies a ledger or settlement defect.
Approve wording for each visible state
Upload supported screenshots or recordings into Retick, or capture the browser screen. Compare AI candidate issues with the evidence, edit payment assumptions, reject claims that money was returned, and annotate the scope mismatch. Example acceptance criteria: the heading identifies a partial refund when appropriate; the amount and currency remain visible beside the status; and the help action explains the product-approved next step without promising a bank arrival date. The payments owner must approve status meanings and customer-facing expectations.
Follow up with controlled examples
After implementation, manually check a full refund, multiple partial refunds, and a pending state with no completion date. Inspect long payment-method labels using safe fixtures. Verify payment records, settlement, and customer support procedures in authorized systems outside Retick. Retick does not issue refunds, connect to arbitrary payment providers, reconcile balances, or verify bank processing. Avoid real financial details in captures and remove sensitive values yourself because automatic redaction is not part of this process.
Download reviewed findings as a file handoff, or export selected issues from the individual media item to a connected Trello board and list. Preserve the distinction between the screen's wording and independently verified payment facts so engineering receives a UI task rather than an unsupported financial conclusion.
Review a refund status message
Bring a safe example of the amount, scope, and wording customers see.