LogoLogo
Explore with DeepWikiJoin Slack CommunityContact Us
  • About Hyperswitch
    • Exploration Guide
    • Overview
    • Payments Suite
    • Payments Modules
      • Cost Observability
      • Revenue Recovery
      • Vault
        • Server to Server Vault tokenization
        • Vault SDK Integration
        • Hyperswitch Vault: Pass Through Proxy Payments
      • Intelligent Routing
      • Reconciliation
        • Getting Started with Recon
      • Alternate Payment Method Widgets
        • Hyperwidget Integration Guide
    • Roadmap - Q2 2025
      • Previous Roadmap - Q1 2025
      • Previous Roadmap - Q4 2024
      • Previous Roadmap - Q3 2024
      • Previous Roadmap - Q2 2024
      • Previous roadmap - Q1 2024
      • Previous roadmap - Q4 2023
  • Use-Cases
    • For SaaS Businesses
    • For B2B SaaS Businesses
    • For E-Commerce Businesses
    • For Marketplace/Platforms
  • Explore Hyperswitch
    • Payment Orchestration
      • Accept Payments
        • Connectors
          • Activate Connector on Hyperswitch
          • Try a Payment
          • Available Connectors
            • ACI
            • Adyen
            • Airwallex
            • Authorizedotnet
            • Bambora
            • Bank of America
            • Billwerk
            • Bluesnap
            • Braintree
            • Checkout
            • Coinbase
            • Cybersource
              • Apple Pay
              • Google Pay
            • dLocal
            • Fiserv
            • GlobalPayments
            • GoCardless
            • Klarna
            • Mollie
            • MultiSafepay
            • Nuvei
            • OpenNode
            • Paypal
            • PayU
            • Prophetpay
            • Rapyd
            • Shift4
            • Stripe
            • TrustPay
            • Volt
            • Worldline
            • Worldpay
            • Zen
            • Netcetera
              • Authenticating Payments via Netcetera Through HyperSwitch SDK
        • Setup Payment Methods
          • Cards
          • Wallets
            • Apple Pay
              • Web Domain
              • iOS Application
            • Google Pay
            • PayPal
          • Pay Later
          • Banks
            • Bank Debits
            • Bank Redirects
            • Bank Transfers
            • Open Banking
          • Crypto
          • Test Credentials
        • Payment Links
          • Configurations
          • Create Payment Links
          • Secure Payment Links
          • Setup Custom Domain
        • Save a Payment Method
        • Manual Capture
        • Incremental Authorization
        • Tokenization & Card Vault
          • Network Tokenisation
        • Supported Payment Workflows
        • Co-badged Cards
        • Webhooks
      • Process Payouts
        • Getting Started with Payouts
        • Using Saved Payment Methods
        • Smart Router for Payouts
        • Smart Retries in Payout
        • Payout Links
      • Smart Routing
        • Rule Based Routing
        • Volume Based Routing
        • Default Fallback Routing
      • Smart Retries
        • 3DS Step-up Retries
      • 3DS / Strong Customer Authentication
        • Setting up 3DS Decision Manager
        • Native 3DS Authentication
        • External Authentication for 3DS
      • Fraud & Risk Management
        • Activating FRM in Hyperswitch
        • Fraud Blocklist
      • Subscriptions
        • PG Agnostic Card Forwarding
        • Zero Amount Authorization
      • Split Payments
        • Stripe Split Payments
        • Adyen Split Payments
        • Xendit Split Payments
    • Checkout Experience
      • Customizable and Native Integrations
        • Web
          • Node And React
          • Customization
          • Error Codes
          • Node and HTML
          • Vanilla JS and REST API Integration
        • Android
          • Kotlin with Node Backend
          • Customization
          • Features
        • iOS
          • Swift with Node Backend
          • Customization
          • Features
        • React Native
          • React Native with Node Backend
          • Card Widget
          • Customization
        • Flutter
          • Flutter with Node Backend
          • Customization
        • Headless SDK
        • Server Setup
      • Click To Pay
        • Visa Click to Pay: V1 to V2 Migration
      • Payment Methods Management
    • Payment Operations
      • Managing Accounts and Profiles
        • ⚙️Control Centre Account setup
        • Hyperswitch Account Structure
      • Manage Your Team
      • Analytics & operations
        • Exporting payments data
      • Disputes / Chargebacks
      • Surcharge
        • Surcharge Setup guide
      • Multi-Tenancy
      • Data migration
        • Import data to Hyperswitch
        • Export data from Hyperswitch
    • Security and Compliance
      • PCI Compliance
      • Data Security
      • GDPR compliance
      • Identity and Access Management
    • E-commerce Platform Plugins by Hyperswitch
      • 🔌WooCommerce Plugin
        • Setup
        • Roadmap
        • Compatibility
        • FAQs
      • Saleor App
        • Setup
      • Automatic Tax calculation for Express Checkout wallets
  • Hyperswitch open source
    • Overview
      • Run Hyperswitch Locally Using Docker
        • Run Additional Services
      • Development Environment Setup
        • Backend
          • Configure and Run the Application
          • Try out APIs
        • SDK (Frontend)
        • Control Center
    • Deploy on AWS
      • Deploy on AWS using CloudFormation
      • Component-wise Deployment
        • Deploy app server
        • Deploy Control Center
        • Deploy web client
          • Production ready deployment
          • Integrate web client on your web app
          • Playground deployment for prototyping (optional)
        • Deploy Card Vault
          • Production ready deployment on AWS
          • Cloud setup guide
    • Deploy on Kubernetes
      • Deploy on GCP Using Helm Charts
      • Deploy on Azure Using Helm Charts
    • Account setup
      • Using Hyperswitch Control Center
      • Test a payment
      • Using postman
    • Troubleshooting
  • Testing Payments
  • Check list for Production
    • Going live
      • For SaaS Setup
      • For On-Prem Setup
        • Monitoring
        • PCI compliance
          • Get started
          • Completing the SAQ
        • Data Security
        • Updates
  • Learn more
    • API Reference
    • Connectors Supported
    • SDK Reference
      • React
      • JS
      • Custom Events
    • Hyperswitch architecture
      • Router
      • Storage
      • A Payments Switch with virtually zero overhead
    • Payment flows
    • Blog
  • Community Guidelines
Powered by GitBook

Compliance

  • Vulnerability Disclosure
  • PCI DSS 4.0
  • ISO 27001:2022

Community

  • Slack
  • Discord
  • GitHub Discussion
On this page
  • Disputes Lifecycle on Hyperswitch
  • Pre-Dispute stage
  • Dispute stage
  • Pre-Arbitration stage
  • Managing Disputes on Hyperswitch through Dashboard
  • 1. Viewing Disputes on Hyperswitch dashboard
  • 2. Generating Dispute Reports:
  • 3. Viewing a Dispute
  • 4. Accepting/Challenging a Dispute

Was this helpful?

  1. Explore Hyperswitch
  2. Payment Operations

Disputes / Chargebacks

Use Hyperswitch's unified Disputes module to track and manage disputes across multiple processors

Last updated 1 year ago

Was this helpful?

A dispute occurs when a customer contacts their payment method issuer (card issuer/bank/wallet) to question or challenge a particular transaction so that the payment can be reversed.

When a card payment is reversed, and the processor debits the merchant's account, it's termed a 'chargeback.' Hyperswitch uses the term 'Disputes' interchangeably to refer to 'Chargebacks' in the context of card payments.

The merchants receive notifications from their payment processor when a dispute is raised by their customers against a payment made at their site.

After receiving a dispute notification, merchants are given an opportunity to provide evidence or documentation to support their side of the transaction. The resolution can involve a chargeback, where the funds are reversed from the merchant's account and returned to the cardholder, or a decision in favor of the merchant if the dispute is deemed invalid.

Each processor has their own standards or processes around how they notify about disputes and how merchants can challenge/accept them and thus it becomes cumbersome for a merchant using multiple processors to manage disputes across different processors on their own.

Hyperswitch unifies all the dispute notifications from all your different processors and makes it easier for you to track, accept and as well as challenge them by uploading evidences across different processors from one place.

Disputes Lifecycle on Hyperswitch

Hyperswitch's unified disputes module uses the following stages and statuses to track your disputes:

Pre-Dispute stage

Some payment method issuers start an investigation before creating a dispute on a transaction challenged by a customer. Such transactions are grouped under the 'Pre-Dispute' stage and these transactions could go through the following states:

dispute_state
description

Opened

Occurs when an investigation is opened and a dispute is created on Hyperswitch

Challenged

Occurs when a merchant uploads evidence to support the original transaction

Expired

Occurs when a merchant doesn't respond in time or if the investigation is closed

Visa or Mastercard do not open an investigation before creating a dispute and so most of your transactions would skip the Pre-Dispute stage

Dispute stage

In most cases, the processors directly debit your account while reversing the payment made by a customer after a transaction has been challenged.

For transactions that go through 'Pre-Dispute' stage, they will end up moving to 'Dispute' stage if the merchant's evidence was deemed not satisfactory.

dispute_state
description

Opened

Occurs when a dispute is opened and your processor has debited your account

Challenged

Occurs when a merchant uploads an evidence to support their case

Expired

Occurs when a merchant doesn't respond in time interval before which an issuer expects a response after the dispute was opened

Cancelled

Occurs when a customer withdraws their challenge

Accepted

Occurs when a merchant accepts a dispute as valid

Won

Occurs when the merchant's challenge was accepted successfully. Known as 'chargeback reversal' in cases of card payments

Lost

Occurs when a merchant's challenge was deemed not satisfctory

Pre-Arbitration stage

Even after a successful dispute challenge, a payment method issuer might deem the evidence 'not satisfactory' and raise another review appeal. Such payments transition to 'Pre-Arbitration' stage.

dispute_state
description

Opened

Occurs when the issuer opens a review appeal after deeming the evidence unsatisfactory

Won

Occurs when the merchant is successful in the pre-arbitration appeal prcoess

Lost

Occurs when the merchant loses during the pre-arbitration appeal. Also, known as 'second_chargeback'

Managing Disputes on Hyperswitch through Dashboard

1. Viewing Disputes on Hyperswitch dashboard

You can view all your disputes by going to Operations -> Disputes section on your Hyperswitch dashboard

2. Generating Dispute Reports:

'Generate Reports' button here will generate a report containing details of all your disputes

3. Viewing a Dispute

Clicking one of the dispute will take you to a page where you can see further information about the particular dispute

4. Accepting/Challenging a Dispute

This feature is currently not present in Hyperswitch. Request for this feature .

here