Built on affaan-m/ECC by @affaan-m (252,536 stars, MIT). All credit for the original idea to them. This fork improves and repackages it; upstream license preserved in UPSTREAM_LICENSE.
A Claude Code skill that helps support teams review refunds, failed payments, canceled plans, and other billing issues safely.
Billing work can affect real money and trust.
A wrong refund can send money twice. A wrong cancel can end the plan a customer wants to keep. Two records may look like one person but belong to different people.
This skill gives Claude Code a clear set of checks. It helps support staff find the right account, learn what happened, pick the safest fix, and write a short reply.
It fits into your current support flow. It works best with a connected billing tool such as Stripe.
Run one command:
mkdir -p ~/.claude/skills/customer-billing-ops && curl -fsSL https://raw.githubusercontent.com/billing-rescue-plus/billing-rescue-plus/main/skill/SKILL.md -o ~/.claude/skills/customer-billing-ops/SKILL.mdThe skill is a single file. It has no added package steps.
Ask Claude Code about a real billing case:
A customer says they were charged twice. Review the billing account for
alex@example.com. Do not refund or cancel anything without my clear approval.
Expected output:
Account: Alex, al***@example.com
Issue: Two active personal plans may cover the same product.
Checks needed: Confirm both plan IDs, charges, dates, and any open disputes.
Proposed fix: Keep the valid plan. Review the extra charge for a refund.
Action taken: None. Approval is still needed.
Customer reply: Draft ready.
Claude should answer four questions:
- Who is the customer?
- What happened?
- What is the safest fix?
- What message should the customer get?
It should mask private data, check key facts, and stop when records do not match. It should state the amount, currency, charge, and plan before any money change.
- Rewritten from Japanese into clearer, simpler English with shorter sections, bullets, and explicit four-question framing.
- Added stronger authorization safeguards: verify the exact account and transaction, obtain clear user approval, and propose rather than execute changes when approval is missing.
- Expanded privacy and identity checks by masking email addresses, avoiding unnecessary calls, matching two facts when possible, and pausing on conflicting records.
- Broadened billing coverage to include fraud, chargebacks, disputes, prior refunds, trials, coupons, taxes, credits, and prorated plan changes.
- Added explicit ECC author credit and more detailed requirements for recording decisions, checking policies, and setting accurate refund expectations.
This repo uses the MIT License. The upstream MIT license and author notice are preserved in UPSTREAM_LICENSE.
