How do I install the "tw Ecom Payment Dispute" skill?

Run npx skillmds@latest add charlieviettq/tw-ecom-payment-dispute in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is "tw Ecom Payment Dispute" safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with "tw Ecom Payment Dispute"?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is "tw Ecom Payment Dispute" free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published "tw Ecom Payment Dispute"?

charlieviettq (@charlieviettq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

"tw Ecom Payment Dispute" by charlieviettq

Name: "tw Ecom Payment Dispute"
Author: charlieviettq

"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.".

charlieviettq Updated Sep 17, 2026

File contents

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