June 12, 2026
Money TLV ad
Issuer-side dispute investigator

Dispute Investigator Life: Issuer Judgement Calls vs. Network Rules

Sponsored Content

Winning the chargeback that no one believed was possible is the biggest success a dispute investigator can achieve. Knowing chargeback rules doesn’t make someone a dispute investigator. If it did, issuer-side training would take a week, and analysts could keep a cheat sheet open on their desk for every “interesting” case in the queue.

The reality is that most issuer-side disputes aren’t black and white. The gray category is where new investigators struggle and where experienced ones realize that network rules don’t equal judgment calls. The rules tell you what’s technically permissible. They don’t tell you what’s actually defensible when the case is examined later.

Here are two examples that make the gap visible.

Subscription cancellation disputes

The network rule says the customer should provide proof of cancellation for the chargeback to hold. The investigator who follows that rule strictly denies cases the customer has every right to win.

Consider a real pattern. The customer subscribed to a SaaS or streaming service eight months ago. Three months in, they tried to cancel. They reached the cancellation page but didn’t complete the multi-step cancel flow. The merchant kept charging. The customer filed a chargeback against one of those charges. The merchant represented successfully on procedural grounds – “the customer didn’t complete cancellation.” The merchant kept charging. The customer files again.

The investigator who follows the rule literally denies the second dispute. The investigator using judgment notes that the merchant was already in dispute communication with this customer through the prior chargeback. From the issuer’s perspective, the prior dispute creates constructive notice that the customer wants out of the relationship. Continued charging after that notice is the merchant’s operational decision. The investigator files the next chargeback citing the prior dispute date, and that’s the argument that holds up.

Hotel disputes that aren’t actually unauthorized

The same pattern shows up in a different domain. The customer calls in disputing a $480 hotel charge as unauthorized. The transaction shows a stay two states away. The customer’s statement: “I never authorized that amount.”

The investigator who follows the surface signal classifies it as unauthorized and starts working it that way. The investigator using judgment probes. Did you travel? Yes. Did you stay at this hotel? Yes. Did you check in, sign a registration card, hand over a card? Yes. Did the room rate match what you expected?

The real issue surfaces here: “The rate was fine. I didn’t know they were going to charge me $200 for the minibar.”

That’s not unauthorized. That’s a billing dispute about incidentals the customer technically consented to at check-in but didn’t understand the scope of.

The investigator who classifies this as unauthorized loses at representment. The merchant comes back with a signed registration card and the case collapses. The investigator who classifies it correctly writes a different decision note and works a different argument that the customer actually has standing to make.

The pattern in dispute investigator rulings

The customer’s language pointed one way in both cases. The rule book pointed one way. The investigator’s judgment landed somewhere else, and that somewhere else is where the case the investigator actually has lives.

This is what makes issuer-side disputes hard. The rules are necessary. They’re not sufficient. The investigator who learns to read the gap between what’s technically permissible and what’s actually defensible is the one who scales, and the one whose decisions hold up when the case gets examined later.

The teams that build durable dispute operations aren’t the ones with the most complete rulebooks. They’re the ones whose investigators learn to ask: what is this case actually about? What did the customer really do? Where does network logic stop and customer-behavior logic start?

Coaching to read between the lines is harder than enforcing the rule. It’s also the nature of the work.

Elephant Ad

ABOUT HAYKANUSH SHAHBAZYAN

Haykanush Shahbazyan is the founder of Dispute Academy, an issuer-side dispute operations training and consulting brand. Her more than a decade of operational experience spans traditional banking (beginning at Capital One) through four U.S. fintech startups across every stage from pre-seed to acquisition. Throughout, she has built dispute resolution organizations from scratch and run them from the inside, staffing the internal teams, leading both in-house and BPO operations, and owning the defensibility of every decision her teams produced.

Her work focuses on the operational layer of dispute decisioning: classification rigor, defensible decisioning, investigation logic, and the human judgment that handles the cases automation cannot. Through Dispute Academy, she translates that practice into frameworks for analysts, dispute leads, and fintech operations teams. She writes about where issuer-side dispute operations break down- classification errors, documentation gaps, QA inconsistency, and the limits of AI in ambiguous cases.

View All Haykanush Shahbazyan Latest Posts

Leave a comment

Your email address will not be published. Required fields are marked *