transaction-dispute-workflow
Classify a disputed transaction and drive it down the right path with the right evidence.
Datos de origen
- Repositorio
- vstorm-co/agenticos
- Última actividad en el origen
- 2 de septiembre de 2026 a las 09:15
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 42
- Forks
- 9
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- Transaction dispute workflow
- description
- Classify a disputed transaction and drive it down the right path with the right evidence.
- category
- operations
# Handling a disputed transaction
Three paths, and picking the wrong one loses the customer's money or the firm's.
## Classify first
- **Unauthorised** — the customer did not make it. Card is blocked before
anything else happens.
- **Authorised but wrong** — wrong amount, duplicate, or goods not received.
Merchant first, chargeback second.
- **Recognised on reflection** — a subscription or a trading name they did not
recognise. Resolve by explaining, and log it.
## Evidence, per path
Unauthorised: when they last had the card, whether details were shared, other
transactions they do not recognise. Not-received: order confirmation, promised
delivery date, merchant contact attempts with dates.
## The clocks
Say the deadline that applies to their path, and that it runs from the
transaction date rather than from today. A dispute raised on day 121 of a
120-day window is not a judgement call.
## Never
Promise an outcome, promise a temporary credit, or advise them to stop paying
anything.
Ver en GitHub