# Confluence Extract — Chargebacks

**Exported:** 2026-03-28 08:00 UTC
**Space:** CB
**Pages included:** 3

## Chargeback SOP

**Space:** CB | **Last updated:** 2026-01-18 by F. Johnson

### Overview
This page covers the standard process for handling chargeback sop within the Chargebacks team.

### Steps
1. Review 11.1 - card recovery status in Confluence
2. Verify 12.6 - processing error records in Jira
3. Verify 10.4 - fraud configuration in Confluence
4. Review 11.1 - card recovery documentation in Zendesk
5. Update 13.1 - merch dispute configuration in Tableau

### Key Thresholds
- Items pending > 7 days: Escalate to manager
- Pending + Disputed = Status conflict, investigate before proceeding

### Contacts
- Team Lead: K. Walker
- Escalation: F. Johnson

---

## Visa Reason Code Reference

**Space:** CB | **Last updated:** 2026-02-04 by A. Smith

### Overview
This page covers the standard process for handling visa reason code reference within the Chargebacks team.

### Steps
1. Document 13.1 - merch dispute compliance in Tableau
2. Escalate 13.1 - merch dispute status in Tableau
3. Document 12.6 - processing error status in Jira
4. Verify 10.4 - fraud records in Tableau

### Key Thresholds
- Items pending > 7 days: Escalate to manager
- Lost + Disputed = Status conflict, investigate before proceeding

### Contacts
- Team Lead: D. Brown
- Escalation: S. King

---

## AMEX Deadline Policy

**Space:** CB | **Last updated:** 2026-01-08 by J. Roberts

### Overview
This page covers the standard process for handling amex deadline policy within the Chargebacks team.

### Steps
1. Document 13.1 - merch dispute configuration in Zendesk
2. Verify 11.1 - card recovery status in Zendesk
3. Review 12.6 - processing error configuration in Jira
4. Review 10.4 - fraud status in Confluence

### Key Thresholds
- Items pending > 7 days: Escalate to manager
- Expired + Closed = Status conflict, investigate before proceeding

### Contacts
- Team Lead: I. Thomas
- Escalation: P. Young

---