Card Fraud and Dispute Incident Macro Standards Specification

Role: Senior Financial Crime Support Lead & Retail Banking Operations Specialist.

Context

• Banking Division: {{bank_division}}
• Card Network Regulations: {{card_network_rules}}
• Core Banking Platform: {{core_banking_system}}
• Primary Dispute Types: {{dispute_categories}}
• SLA Response Window: {{sla_target_minutes}}
• Statutory Disclosure Code: {{regulatory_disclosure_code}}

Task

Produce a comprehensive Dispute and Fraud Incident Macro Specification that equips customer service representatives to rapidly diagnose, secure accounts, and initiate chargeback workflows while adhering strictly to statutory dispute disclosure timelines.

Method

1. Deconstruct {{dispute_categories}} into discrete agent triage trees based on transaction state, merchant category, and cardholder authorization status.
2. Cross-reference {{card_network_rules}} and {{regulatory_disclosure_code}} to establish non-negotiable statutory timelines for provisional credit and investigation notices.
3. Draft deterministic response macros containing automated core status triggers compatible with {{core_banking_system}}.
4. Define strict tokenization rules for masked card identifiers, merchant dispute IDs, and dynamic case tracking links.
5. Engineer distinct macro variations for immediate account lock, partial merchant dispute, and complex account takeover workflows.
6. Incorporate mandatory agent script checkpoints that confirm oral or written intent required by {{regulatory_disclosure_code}}.
7. Establish automated transition triggers that post internal status notes to risk teams when {{sla_target_minutes}} risk thresholds are approached.
8. Set up quality assurance benchmarks to monitor agent macro adherence and dispute reason code accuracy.

Constraints

• MUST contain verbatim statutory dispute disclosures as mandated by {{regulatory_disclosure_code}}.
• MUST NOT permit free-form alteration of provisional credit timelines or cardholder liability clauses.
• All macros must state expected investigation horizons aligned with {{card_network_rules}}.
• Responses must explicitly confirm security actions taken on {{core_banking_system}}.

Output format

Deliver a formal operational specification containing:

1. Operational Workflow Diagram Description (text-based logic flow)
2. Dispute Macro Catalog (5 distinct scenario specifications with merge tokens, triggers, and exact client copy)
3. Core Banking State Change Mappings (table showing macro-to-system actions in {{core_banking_system}})
4. Regulatory & Network Compliance Matrix
5. Quality Assurance Review Rubric (5 scoring criteria)

Self-review

• Verify coverage of all inputs: {{bank_division}}, {{card_network_rules}}, {{core_banking_system}}, {{dispute_categories}}, {{sla_target_minutes}}, {{regulatory_disclosure_code}}.
• Ensure provisional credit disclosure language meets statutory standards without ambiguity.
• Check that each macro includes explicit token syntax and agent validation instructions.