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.
What the payment dispute process is
A cardholder who questions a payment may need an explanation, a merchant refund request, a pre-dispute inquiry or a formal dispute. Treating all four as the same chargeback path creates unnecessary cases and unclear promises. This template starts with one issuer-owned intake record for the transaction, concern, dates, contact details and prior service actions. Missing information returns to the cardholder, while a complete record first asks whether the issuer can explain or resolve the question as an inquiry.
If issuer inquiry does not resolve the question, the process checks whether a pre-dispute or merchant refund route is available for that transaction. The result can close without an adjustment, close with an agreed adjustment, or continue. Only an unresolved case reaches the separate formal eligibility gate, where the issuer applies the current case rules for the payment route. Keeping availability and eligibility separate prevents an unavailable early route from being mistaken for formal ineligibility, or an available inquiry from being treated as a guaranteed dispute right.
The formal branch is intentionally a compact handoff: open and route the case, notify the merchant, collect a focused response when needed, and review the outcome. Financial work is split after the decision. The issuer owns the cardholder account posting, while the processor or acquirer route carries the corresponding merchant-side adjustment. Issuer staff communicate the outcome, and finance reconciles case, account and settlement references. This customer-facing front door can hand detailed chargeback operations to the Chargeback Management Process without duplicating its case queue and portfolio controls.
What this flowchart covers
In this template
- Cardholder transaction questions, complete issuer-owned intake and a loop for missing transaction or contact details
- Issuer inquiry and explanation before a separate check for an available pre-dispute or merchant refund route
- Formal dispute eligibility only after early resolution does not close the question, using the applicable case rules
- Formal case routing, merchant acceptance or response evidence, completeness review and a recorded outcome
- Separate cardholder and merchant-side adjustments, issuer communication, financial reconciliation and closure
When to use this template
- Cardholder transaction questions move between service and dispute teams without a consistent issuer-owned intake record
- Simple transaction explanations, merchant refund requests and formal disputes are being opened through the same operational route
- Teams confuse availability of an inquiry or pre-dispute option with eligibility for a later formal case
- Outcome communication does not identify who owns the cardholder posting and who carries the merchant-side adjustment
- Your organization needs a vendor-neutral front-door flow before detailed chargeback case management begins
How it works
Build one front-door intake
List the transaction identifiers, cardholder concern, contact details, account context and prior refund or service actions needed for issuer review. Mark which missing fields pause the inquiry and keep the issuer team as owner while information is collected.
Define inquiry resolution
Document which transaction questions the issuer can explain or resolve from account and payment records. Record the explanation and outcome so a completed inquiry does not enter a pre-dispute or formal queue merely because the cardholder contacted the disputes team.
Separate route availability from eligibility
First map the pre-dispute inquiry or merchant refund routes available through each processor or acquirer. Then define the formal eligibility check used only when early resolution fails, including the current case rules and source for case-specific timing.
Keep the formal branch focused
Name who opens and routes the formal case, what the merchant receives, and which transaction, authorization, delivery and communication records address the issue. Return incomplete evidence for correction before the issuer records the formal outcome.
Assign adjustment ownership
Specify the issuer-side cardholder account entry and the corresponding processor, acquirer or merchant-side adjustment for each financial outcome. Keep issuer communication separate, then reconcile case, account and settlement references before closure.
Frequently asked questions
What are the main steps in a payment dispute process?
Record the cardholder's transaction question and complete missing intake information. Try issuer inquiry first, then check whether a pre-dispute inquiry or merchant refund route is available. If that route does not resolve the issue, assess formal eligibility, route the case, collect any merchant response and record the outcome. Apply separately owned account and merchant-side adjustments, communicate through the issuer, reconcile the records and close.
Does an available pre-dispute route mean a formal dispute is eligible?
No. Route availability asks whether an inquiry, merchant refund or pre-dispute exchange can be attempted for the transaction. Formal eligibility is a later and separate decision made only if early resolution does not close the question. It uses the rules and timing that apply to that case. One gate should not be reused as proof of the other.
How is a payment dispute process different from chargeback management?
The payment dispute process starts with the cardholder's question and includes issuer explanation, early inquiry or refund routes, and the decision to open a formal case. Chargeback management begins with an operational case and goes deeper on ownership, case dates, merchant outreach, response submission, status tracking and portfolio trends. The two can connect without using chargeback handling for every transaction question.
Who should communicate and post a payment dispute outcome?
The issuer or its designated disputes team should own communication with the cardholder. Financial responsibilities should be explicit: the issuer applies the cardholder account entry, while the processor or acquirer route handles the corresponding merchant-side adjustment when one is required. Finance or settlement operations then reconciles the case, account and settlement references before closure.
Where this process fits
In most operations this process hands off to Chargeback process flowchart (participant lifecycle).
It is one step in Disputes and chargebacks.
Step 1: Payment Dispute Process Flowchart You are here
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)
High-level chargeback process flowchart from cardholder formal dispute through issuer, network or processor, acquirer, merchant response, outcome, both-side posting and closure.