Dispute workflows

  • Release version: Xanadu
  • Updated August 1, 2024
  • 4 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Dispute workflows

    Dispute workflows enable card dispute agents or agent connectors to manage credit and debit card dispute cases efficiently. When a transaction is disputed, a dispute service case is initiated, triggering a structured flow of tasks tailored to each transaction involved. This workflow guides agents through stages of Initiate, Review, Investigation, Chargeback, and Closure to investigate, manage, and resolve dispute requests based on inputs and decisions from cardholders, card networks, merchants, and banks.

    Show full answer Show less

    Key Features

    • Initiate Stage: Agents identify disputed transactions, add additional transactions for fraud disputes, complete questionnaires, and upload supporting documents. Integration with services such as Ethoca Consumer Clarity provides additional transaction details. Business rules evaluate each transaction to generate specific tasks (e.g., blocking and reissuing cards for fraud cases).
    • Review Stage: Applicable when disputes are submitted by customers via a portal. Agents review dispute details, answer outstanding questions, and the system generates tasks based on updated dispute categories and policy rules.
    • Investigation Stage: Involves collaboration among card networks, issuing banks, merchants, and acquirers to make final determinations. Agents can alert merchants and handle merchant refusals through manual investigation tasks. Business rules decide outcomes such as deny, immediate final credit, provisional credit, or no credit, dictating subsequent case flow.
    • Chargeback Stage: The dispute is escalated to the card network and acquirer. Fraudulent transactions are reported, chargebacks initiated, and agents review representments to accept or reject proof. Appropriate credit reversals occur if provisional credit was issued. Card blocking and reissuing processes run concurrently with dispute management.
    • Closure Stage: After final decisions on all disputed transactions, cases move to closure. Agents enter resolution codes and notes before marking cases as closed complete. Cases denied by policy rules may move directly to closure.

    Key Outcomes

    • Streamlined handling of credit and debit card disputes through a guided, task-driven process.
    • Clear stages enable agents to systematically gather information, interact with relevant parties, and apply policy rules effectively.
    • Integration with external services enhances transaction insights supporting dispute resolution.
    • Automated decision-making via business rules ensures consistent application of policies such as issuing provisional or final credits, or initiating chargebacks.
    • Concurrent card management (blocking, reissuing) improves security and customer satisfaction during dispute resolution.
    • Comprehensive closure process ensures all dispute outcomes are documented and finalized properly.

    As a card dispute agent or agent connector, you can work on a credit or debit card dispute cases 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 card transactions 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, Investigation, Chargeback, and Closure stages of a dispute case.

    Initiate

    When a dispute agent initiates a case, the case begins in the Initiate stage.

    During this phase, you can identify the disputed transaction, add more transactions (if the dispute category is Fraud), complete the dispute questionnaire, and upload any supporting documentation.

    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.

    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.

    Investigation

    During this stage of the case, 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 refuses a transaction dispute, the case may also move to the manual investigation task.

    The business rules engine initiates decisions for the transaction such as:
    • 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.

    Chargeback

    During the Chargeback stage, the dispute is forwarded to the card network. The card network then forwards the dispute to the acquirer.

    In this stage, the following actions take place:
    • 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.

    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.