# Design Refund Support Flow

> Design the customer and entitlement consequence of a refund, cancellation, dispute, or chargeback. Use when spent value, access, and support action must stay consistent with payment truth. Do not use to own the money ledger.

- Skill: `sylphxai/design-refund-support-flow` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sylphxai/design-refund-support-flow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sylphxai/design-refund-support-flow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: SylphxAI (https://skillmd.com/u/sylphxai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sylphxai/design-refund-support-flow

---


# Design Refund and Support Flow

Do not silently rewrite spent consumables. Do not trade refunds for review deletion. Payment truth, access, and support action that disagree are the defect.

Open [refund support flow patterns](references/refund-support-flow-patterns.md) when entitlement consequence needs depth.

Use `build-payment-readiness` for the ledger. Use `resolve-customer-support-case` for one ticket.

