Chargeback process flowchart (participant lifecycle)
High-level chargeback process flowchart from cardholder formal dispute through issuer, network or processor, acquirer, merchant response, outcome, both-side posting and closure.
What the chargeback process flowchart (participant lifecycle) process is
This chart starts when a cardholder submits a formal payment dispute. The issuer records the claim and prior handling, then tests whether the matter meets the applicable chargeback entry requirements. An ineligible matter returns to complaint, inquiry or refund handling rather than being forced into a formal financial case.
For an eligible case, the issuer opens the formal record, the network or processor routes it to the acquirer, and the acquirer notifies the merchant. The merchant's accept-or-contest decision is visible, but a contested case is handed to the appropriate case-management or representment subprocess instead of duplicating its internal evidence and submission procedure here.
This Chargeback Process is the high-level participant lifecycle and ends only after the issuer's cardholder-account posting and the acquirer's merchant-funding posting match the recorded outcome. Use the Chargeback Management Process for internal queue ownership, deadlines, merchant outreach, status control, quality assurance and portfolio trends. Use the Chargeback Representment Process for detailed contest approval, evidence mapping, package review, submission and permitted follow-on action.
What this flowchart covers
In this template
- Cardholder formal dispute entry and issuer chargeback eligibility
- Case routing across issuer, network or processor, acquirer and merchant
- Merchant accept-or-contest authority with a high-level subprocess handoff for contested cases
- A recorded cardholder-favoring or merchant-favoring formal outcome
- Separate issuer and acquirer postings, participant notifications and reconciled closure
When to use this template
- Participants need one shared view of the formal chargeback lifecycle without internal case-management detail
- Complaint, inquiry and refund handling are being confused with formal chargeback entry
- Issuer, network or processor, acquirer and merchant handoffs are missing from the process map
- The merchant's accept-or-contest decision is not connected to the formal outcome
- Cardholder-account and merchant-funding postings are treated as one unexplained event or close before they reconcile
How it works
Define formal dispute entry
State what creates a formal cardholder dispute, what the issuer records and which matters remain in complaint, inquiry or refund handling. Preserve the transaction reference and prior handling.
Map participant routing
Name the issuer, network or processor, acquirer and merchant roles in the actual payment arrangement. Keep each case notice, response and outcome handoff visible even when one provider performs several roles.
Set merchant response authority
Define who records the merchant's accept-or-contest decision. Send contested cases to the applicable case-management or representment subprocess rather than embedding its detailed procedure in this participant map.
Define the formal outcome
Identify the event and responsible participant that record whether the formal outcome supports the cardholder or merchant position. Keep acceptance and a reviewed contested outcome distinguishable.
Reconcile both postings
Match the formal outcome to the issuer's cardholder-account debit or credit and the acquirer's merchant-funding adjustment. Resolve mismatches, notify both sides and close each participant record.
Frequently asked questions
Where does the formal chargeback process begin?
It begins when a cardholder submits a formal payment dispute and the issuer tests it against the applicable chargeback entry requirements. Complaints, refunds and transaction inquiries remain outside this flow unless they create a qualifying formal case.
What are the main steps in a chargeback case?
A high-level flow records the cardholder claim, confirms eligibility, opens and routes the case through the issuer, network or processor and acquirer, records the merchant response and formal outcome, posts both financial sides, reconciles them, notifies the parties and closes the participant records.
How do the three chargeback templates differ?
The Chargeback Process maps the high-level lifecycle across cardholder, issuer, network or processor, acquirer and merchant through both-side posting and closure. The Chargeback Management Process covers internal queue ownership, deadlines, outreach, status, quality assurance and portfolio trends. The Chargeback Representment Process covers the detailed contest, evidence, review, submission and follow-on procedure.
Why are cardholder and merchant postings separate?
The issuer owns the resulting cardholder-account debit or credit, while the acquirer owns the corresponding merchant-funding adjustment. Timing, provisional entries and fees can differ, so one posting does not prove the other completed. Reconcile both to the formal case result.
Where this process fits
In most operations this process follows Payment Dispute Process Flowchart and hands off to Chargeback Management Process Flowchart.
It is one step in Disputes and chargebacks.
Step 1: Payment Dispute Process Flowchart
Payment dispute process template for transaction questions, issuer inquiry, pre-dispute or refund attempts, formal eligibility, case response, adjustments and closure.
Step 2: Chargeback process flowchart (participant lifecycle) You are here
High-level chargeback process flowchart from cardholder formal dispute through issuer, network or processor, acquirer, merchant response, outcome, both-side posting and closure.
Step 3: Chargeback Management Process Flowchart
Chargeback management process template for case intake, ownership, classification, merchant outreach, evidence QA, submission, status, reconciliation and trend feedback.