Managing dispute workflows
Summarize
Summary of Managing dispute workflows
This guide explains how card dispute agents and agent connectors manage credit or debit card dispute cases using ServiceNow. When a dispute is initiated—either by an agent or a customer via Virtual Agent—it triggers a dispute service case and a workflow that includes various stages and tasks tailored to the dispute details. The process supports handling multiple disputed transactions within a case, guiding agents through investigation, decision-making, and resolution activities involving cardholders, card networks, merchants, and banks.
Show less
Dispute Workflow Stages
- Initiate: Agents start the dispute case by identifying disputed transactions, adding related transactions (especially for fraud), completing questionnaires, and uploading documentation. Cases initiated via Now Assist for Financial Services Operations (FSO) automatically populate information from Virtual Agent interactions. Integration with systems like Ethoca Consumer Clarity can provide extra transaction details. The system evaluates decision and policy rules to generate appropriate tasks, such as blocking and reissuing cards for fraud cases.
- Review: For customer-submitted disputes via service portal, this stage involves reviewing intake details, verifying disputed transactions and amounts, answering outstanding questions, and updating dispute categories as needed. Policy rules continue to drive task creation here.
- Processing: Agents monitor and manage the overall status of each disputed transaction, presented individually with key details like dispute amount, transaction date, merchant type, and current activity. This stage offers a comprehensive view of case progress.
- Investigate: Each disputed transaction moves through this stage where involved parties review and decide outcomes. Agents can alert merchants to disputes and handle cases of friendly fraud. Automated internal policy decisions may deny disputes, grant immediate final credit, provisional credit, or no credit, triggering further manual investigation if merchants refuse the dispute.
- Chargeback: Disputes are escalated to the card network and acquirer to initiate chargebacks. Agents manage representment reviews to accept or reject merchant responses, reverse provisional credits if necessary, and handle advanced Visa dispute processes like pre-arbitration and arbitration. Card blocking or reissuing tasks run concurrently with transaction dispute workflows.
- Closure: After final determinations on all disputed transactions, cases progress to closure. Agents record resolution codes and notes before moving the case to a closed state. Disputes denied by policy rules may go directly to closure.
Practical Benefits for ServiceNow Customers
- Structured dispute management: The workflow ensures agents follow consistent, policy-driven steps tailored to each transaction’s dispute category, improving accuracy and efficiency.
- Integration support: Automations and integrations with external systems enrich case data and enable informed decision-making.
- Comprehensive case tracking: Visibility into each transaction’s status and activities facilitates proactive dispute resolution and timely case closure.
- Automated decision-making: Internal policy rules reduce manual effort by automatically determining credit eligibility and next steps.
- Support for advanced dispute scenarios: The workflow accommodates complex activities like friendly fraud detection, chargeback representment, and Visa arbitration processes.
ServiceNow customers can leverage this dispute workflow to streamline dispute handling, enforce compliance with business policies, enhance collaboration among involved parties, and ultimately improve customer satisfaction by resolving card disputes efficiently and accurately.
As a card dispute agent or agent connector, you can work on a credit or debit card dispute case by investigating and resolving dispute requests for cardholders.
When an agent disputes a transaction on behalf of a customer, it initiates a dispute service case and triggers the dispute transaction flow. This flow includes various tasks specific to the case details.
For credit or debit card dispute management cases, tasks are generated for each transaction that has a dispute request. The playbook guides you through these tasks, ensuring you effectively manage and fulfill them based on investigations and decisions made by parties involved, such as the cardholder, card network, or merchant. With input or decisions from these parties, you, as a dispute agent, will complete activities and tasks within the Initiate, Review, Processing, Investigate, Chargeback, and Closure stages of a dispute case.
Initiate
When a dispute agent initiates a case, the case begins in the Initiate stage. Dispute cases created using Now Assist for Financial Services Operations (FSO) with the Disputes intakes via Virtual Agent skill will also begin in the Initiate stage.
During this phase, you can identify the disputed transaction, add more transactions (if the dispute category is Fraud), select associated transactions, complete the dispute questionnaire, and upload any supporting documentation. Dispute cases created using Now Assist for FSO are populated with information collected and inferred from the customer's responses in the Virtual Agent chat.
When a transaction is selected for dispute, you can obtain additional information about the transaction with an integration, such as Ethoca Consumer Clarity and Order Insight Digital Management.
The system evaluates decision rules and determines policy rules for each transaction in the case (for example, which transaction qualifies for a provisional credit as opposed to a final credit).
The system generates tasks based on the policy rules that are evaluated when a case is submitted. For instance, when a case has a dispute category of Fraud, the system creates a task to block and reissue the card.
For information about configuring business rules, see Exploring Decision Tables.
For information about Now Assist for FSO, see Now Assist for Financial Services Operations (FSO).
Review
If a dispute case was submitted by a customer via a service portal, the case begins at the Review stage. If the case was initiated by an agent, this stage will be skipped.
The dispute agent reviews the dispute intake, including the disputed transactions, the dispute amount, and the reasons for dispute.
The agent provides answers to any additional questions not answered by the cardholder and to any questions they are expected to address. If the dispute category changes, the system will produce a questionnaire for the newly selected category, which is then filled out by the agent.
After review, the agent submits the case and continues with the subsequent lanes and activities in the case.
The system generates tasks based on the policy rules that are evaluated when a case is submitted. For instance, when a case has a dispute category of Fraud, the system creates a task to block and reissue the card.
Processing
After the case is submitted, an agent can monitor and progress the disputed transactions in the Processing stage. This stage presents an overview of the overall case and tracks the status of each transaction and its related tasks.
- Card disputes transaction number
- The stage at which the disputed transaction is at (Investigate, Chargeback, or Complete)
- Whether the transaction is card present or card not present
- Dispute amount
- Transaction date
- Merchant type
- Transaction status
- Current activity
- Activity SLA
Investigate
This stage applies for each disputed transaction in a case. You can access this stage by opening a disputed transaction in the Processing stage of the playbook.
During this stage, the card network, card issuing bank, merchant bank or acquirer, and merchant engage in review processes to make final determinations for each transaction. In this stage, you can alert the merchant to a card transaction dispute. If a merchant declines a disputed transaction, then a task to Investigate transactions is created.
- Deny: The dispute for the transaction is denied.
- Immediate final credit: This decision provides final credit immediately to the cardholder. For example, if the disputed transaction amount is below $25 USD, a bank's business rule may choose to initiate immediate final credit. If immediate final credit is decided, the dispute case progresses through the workflow to determine whether to initiate a chargeback, write off the amount, or deny credit and reverse the chargeback, returning the credit to the cardholder.
- Provisional credit: This decision provides temporary credit to the cardholder. If the merchant refuses the dispute, the case undergoes manual investigation.
- No credit: This decision provides no credit. If the merchant refuses the dispute, the case undergoes manual investigation.
In this stage, agents can also work on transactions identified as friendly fraud. For more information, see Detect friendly fraud.
Chargeback
This stage applies for each disputed transaction in a case. You can access this stage by opening a disputed transaction in the Processing stage of the playbook.
During the Chargeback stage, the dispute is forwarded to the card network. The card network then forwards the dispute to the acquirer.
- The fraudulent transaction is reported to the card network.
- A chargeback is initiated. There is a wait period to see if there is a representment. At the Review Representment task, the agent determines if the proof is sufficient and accepts or rejects the representment.
- If the agent accepts the representment and provisional credit has been issued, reverse provisional credit to refund the merchant if a chargeback has been initiated with the acquiring bank.
- In card dispute playbooks integrated with Visa, agents can also progress a disputed transaction through pre-arbitration, arbitration, and appeal in the Chargeback stage. They can review responses to each of these, and create filings in response as required.
The block card or reissue card flows run in parallel with the rest of the dispute management flow running for the various transactions being disputed.
Closure
After a case is processed according to the final determinations for all dispute transactions associated with the case, the case progresses to Closure.
If the evaluated policy rules deny the transaction, it will move directly to Closure.
Agents can enter the Resolution code and any Resolution notes before the case is moved to Closed Complete state.