Transaction dispute workflow

Classifies disputed transactions and routes each case through the correct evidence and deadline path.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill transaction-dispute-workflow-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Transaction dispute workflow
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/finance/transaction-dispute-workflow
Command: npx skills add https://github.com/vstorm-co/agenticos --skill transaction-dispute-workflow-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Disputed card transactions follow three very different resolution paths, and picking the wrong one loses the customer's money or the firm's. This Skill gives an agent a consistent decision procedure for classifying a dispute, gathering the right evidence, and stating the correct deadline. ## Core Features & Use Cases - Three-path classification: Distinguishes unauthorised transactions, authorised-but-wrong transactions (wrong amount, duplicate, goods not received), and recognised-on-reflection cases such as forgotten subscriptions. - Path-specific evidence checklists: Specifies what to collect per path, such as card possession history for unauthorised claims or order confirmations and merchant contact dates for not-received claims. - Deadline and conduct guardrails: States that dispute windows run from the transaction date, and prohibits promising outcomes, temporary credits, or advising customers to stop payments. - Use Case: A customer reports a charge they do not recognise. The agent classifies it as unauthorised, confirms the card is blocked first, then collects evidence about when the customer last had the card and whether details were shared. ## Quick Start A customer disputes a 49.99 charge from a merchant name they do not recognise; classify the dispute and tell me what evidence to gather and what deadline applies.

Frequently Asked Questions about Transaction dispute workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle a disputed card transaction?▼

First classify the dispute into one of three paths: unauthorised, authorised but wrong, or recognised on reflection. Each path has its own evidence requirements and resolution order, such as blocking the card before anything else for unauthorised claims.

What evidence is needed for an unauthorised transaction dispute?▼

Collect when the customer last had the card, whether card details were shared, and any other transactions the customer does not recognise. The card must be blocked before any other step is taken.

How do I dispute a charge for goods not received?▼

Gather the order confirmation, the promised delivery date, and records of merchant contact attempts with dates. The merchant is contacted first, and a chargeback is the second step if that fails.

When does the dispute deadline start for a chargeback?▼

The dispute window runs from the transaction date, not from the date the customer raises the issue. A dispute raised on day 121 of a 120-day window is out of time, not a judgement call.

What should an agent never promise during a transaction dispute?▼

Never promise an outcome, promise a temporary credit, or advise the customer to stop paying anything. These commitments exceed what the dispute process can guarantee.