Tw ecom payment dispute

Skill charlieviettq/awesome-agent-skill/.claude/skills/tw-ecom-payment-dispute

"Handle Taiwan e-commerce payment disputes — credit card chargebacks (扣款爭議), refund across bimonthly boundaries (retro 折讓 trigger), acquirer dispute timelines, and evidence packets. Use when a customer files a chargeback, when issuing cross-period refunds that affect invoices, or when building internal dispute SOP. Do NOT use for simple in-period refunds (gateway-specific skills handle those). STATUS: SKELETON — body pending.".From its SKILL.md

Install

npx -y skills add charlieviettq/awesome-agent-skill --skill tw-ecom-payment-dispute

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

24 stars24 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, 263 tokens by cl100k_base, as published. Nobody here has run it

Payment Dispute Handling

STATUS: SKELETON — body pending.

When to use this skill

A customer has filed a credit card chargeback
Issuing a refund that crosses the bimonthly invoice boundary
Building an internal dispute-handling SOP
Preparing evidence packets for acquirer review
Reconciling dispute outcomes against invoice state

Do NOT use when

Simple same-period refund → gateway-specific skill
Consumer-law-level dispute (鑑賞期) → tw-ecom-compliance-consumer

Core concepts

TODO: chargeback vs 退刷 vs 折讓, typical acquirer timelines, reason codes.

Decision tree

TODO: given reason code → response path.

Implementation guidance

TODO: evidence packet structure, 折讓 triggering logic, accounting entries.

Gotchas

TODO: 5-6 pitfalls (bimonthly boundary, dual-refund double-charge, reason-code mismatch, evidence deadline, acquirer dialect differences).

IRON LAW

TODO.

Output Format