Tw Ecom Payment Dispute

Name: Tw Ecom Payment Dispute
Author: asgard-ai-platform

ASecurity

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.

228 stars
0 votes
0 copies
2 views
Added May 27, 2026

data-aigo

Works with

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add asgard-ai-platform/skills --skill tw-ecom-payment-dispute --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tw Ecom Payment Dispute?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Tw Ecom Payment Dispute

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/asgard-ai-platform-tw-ecom-payment-dispute/badge)](https://www.skillsdirectory.com/skills/asgard-ai-platform-tw-ecom-payment-dispute)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: "tw-ecom-payment-dispute"
description: "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."
metadata:
  category: "WP-05 台灣創業"
  domain: "ecommerce-tw"
  layer: "payment"
  related_mcps: []
  related_skills: ["tw-payment-integration", "tw-ecom-payment-newebpay", "tw-ecom-payment-ecpay", "tw-ecom-invoice-void", "tw-ecom-compliance-consumer"]
  last_verified: "2026-04"
  status: "skeleton"
  tags: ["taiwan", "payment", "dispute", "chargeback"]
---

# 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

TODO.

## Related

- `tw-ecom-compliance-consumer`
- `tw-ecom-invoice-void`

_Last verified: 2026-04_