Overview

[ { "title":"Overview", "link":"https://doc.chargebackhit.com/products/overview", "text":"System overview to alert merchants to potential chargebacks before they occur, allowing the merchant to prevent a chargeback by issuing a refund instead.", "imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/04/benefits-2.svg" } , { "title":"Matching alerts", "link":"https://doc.chargebackhit.com/integrate/matching_alerts/", "text":"Internal logic for quick matching of alert data by the system in real-time.", "imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/03/icon-06.svg" } , { "title":"Integration steps", "link":"https://doc.chargebackhit.com/integrate/integration_steps/", "text":"Step-by-step instructions for the technical integration of the chargeback system.", "imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/04/benefits-1.svg" } ]

Sign In
Authentication
Integration
Webhook
Alert
MIDs
Import
  1. Documentation
  2. /
  3. HUB
  4. /
  5. Overview
Overview
Chargebackhit system portal has a structured interface with features to provide information and manage chargeback alerts

To manage chargeback alerts in the Chargebackhit HUB , the following features are available:

  • Monitoring
    Comprehensively monitor alert notifications from different sources and their outcomes.
  • Analytics
    View a high-level overview of data and reports on chargebacks to identify trends and anomaly monitoring and activity. Receive a fast analysis for decision-making (for specialists and top management alike).
  • MIDs management
    After the new MID submission, Chargebackhit receives a notification and starts the enrollment process. Tracking the activity and status of MIDs refers to monitoring and recording data on the dashboard.
  • Case management
    Responding to alerts in manual mode. This means that the user must review each alert and take the appropriate action.
  • Support widget
    Features such as real-time notifications, in-app support, and secure communication enhance the user experience and help resolve any issues efficiently.

The Chargebackhit HUB consists of: cbh_hub_1.0

  • Header: Top fixed block always visible
    • Account selection (dropdown select)
    • “Support” icon
    • “Help” icon
      • Documentation
    • “Profile” icon
      • Profile
      • Logout
  • Subheader: Fixed section buttons of the portal
    • Portal sections one-level menu
      • Guide
        Dashboard in Chargebackhit is a graphical interface that provides an overview of key metrics and data related to chargebacks alerts, allowing merchants to quickly monitor and manage their chargeback risk         Dashboard
      • Analytics
      • MIDs
      • Alerts
      • Guide
        User management in Chargebackhit refers to the functionality that allows administrators to create, edit, and manage user accounts and their access to the system's features and data         User Management
      • Guide
        Page with settings for Chargebackhit users to configure their preferences         Settings

Account
anchor

The account user for Chargebackhit includes separate merchants, businesses, LEs, and groups of merchants.

An account must contain at least one MID and can be used for access separation for hub users.

User
anchor

This is a user account portal that includes an email, password, access to accounts, and access to functions (user roles). Admin users can have access to any account and can add new users inside those accounts.

The followings are the roles and responsibilities that an account user may have in an admin panel for alert management:

Access to user management, MID management, Alert responses, tech settings (URL/ API keys).
View alert responses.
Only view.
MID management, alert responses.

MID
anchor

The MID (Merchant ID) is a crucial parameter in a chargeback alert system. An MID is a unique identifier assigned to a merchant by a payment processor, and it is used to track transactions and link them to a specific merchant.

In a Chargebackhit, MID parameters identify and categorize transactions based on the merchant that processed them. This information is critical in tracking alerts and resolving chargebacks, as it helps to determine which transactions are associated with a specific merchant and which merchants are at higher risk for chargebacks.

By monitoring the MID parameters of transactions, Chargebackhit can detect patterns and anomalies that may indicate a high risk of chargebacks. This information can then be used to proactively address the issue and prevent future chargebacks from occurring.

In summary, MID parameters are important in Chargebackhit because they provide a way to identify and categorize transactions based on the merchant that processed them, which is critical in tracking and resolving chargebacks.
info

Main parameters identifying MID:

  • BIN/CAID - special parameters that are tied to MID
  • Payment descriptor - the core of MID

It has variations:

  • Descriptors
  • VISA BIN/CAIDs

Descriptor
anchor

A payment descriptor in Chargebackhit is a unique identifier that links a transaction to a specific store or merchant account. It is used to connect alerts or notifications of chargebacks to the correct transaction and merchant user.

The payment descriptor is usually included in the transaction details and helps payment processors quickly and accurately match the alert to the proper MID. This information is used in the alert process to determine the merchants responsibility and liability in the dispute.

Products
The guides section for products offers comprehensive information and resources to help merchants understand and effectively use the system to monitor and mitigate chargeback risk
Onboarding parameters
Essential parameters for an effective Chargebackhit's onboarding guide
Integrate
General steps for integration and definition about linking data
Get started–>