[
{
"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/09/Fraud-prevention-tool-960x320-1.png"
}
,
{
"title":"Products",
"link":"https://doc.chargebackhit.com/products/",
"text":"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.",
"imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/09/Fraud-prevention-tool-960x320-1.png"
}
,
{
"title":"HUB",
"link":"https://doc.chargebackhit.com/hub/",
"text":"Chargebackhit is a centralized platform for administrators to manage and view chargeback alerts.",
"imgSrc":"https://chargebackhit.com/wp-content/uploads/2022/09/Fraud-prevention-tool-960x320-1.png"
}
]
Checklist of changes to all Chargebackhit’s components
Our external changelog for Chargebackhit provides detailed updates on features, security measures, compliance standards, and interface changes, offering valuable insights for users to stay updated and informed about the latest developments in our chargeback prevention services.
It helps to understand how these changes impact business processes and guides in making necessary adjustments to systems and procedures.
Alongside, the Chargebackhit API Reference also includes a dedicated changelog, specifically documenting updates related to API functionalities, ensuring users can track changes and adapt their integrations effectively.
2024
July
Added the
Guide
Common error responses and recommended actions.
Error handling
page for understanding of common integration errors.
API
Added additional fields to the alert object in the
webhook
API
:
mcc - merchant category code
descriptor - original payment descriptor
reason_code - alert reason code
June
Expanded the description for
Guide
Responses summarize complex Chargebackhit API outcomes and responses, ensuring accurate transaction reconciliation.
outcome types
, detailing scenarios for each type: reversed, previously-reversed, decline, reverse-error, not-found, acknowledged, pending, and shipped
Added information about alerts being billable and updated
Guide
Rapid Dispute Resolution allows addressing Visa transaction disputes preemptively using an automated decision-making engine, preventing escalations and ensuring fast resolutions for cases that fall under defined conditions.
RDR
merchant-defined rules, including requirements for unique rule names, up to eight conditions per rule
API
Added the ability:
to edit the internal ID (description under MID) via API, allowing to correct mistakes without notification
to request product disenrollment by MID, enabling merchants to selectively disenroll products like RDR while setting the product status to in-process-of-disenrollment and allowing for monitoring and request tracking
validation for chargeback type, status, and amount to ensure correct data during manual import, preventing unexpected statuses
May
Updated guide on
Guide
Rapid Dispute Resolution allows addressing Visa transaction disputes preemptively using an automated decision-making engine, preventing escalations and ensuring fast resolutions for cases that fall under defined conditions.
Rapid Dispute Resolution
rules, featuring auto-decision engine for Visa pre-disputes that allows enforcing automated real-time resolution.
April
HUB
Improved HUB,
Guide
User management enables administrators to create, edit, and assign permissions to user accounts, controlling their access to system features and data.
user management
functionality, to exclude deleted accounts from the display.
Implemented pagination reset upon filter changes to ensure consistent and relevant data presentation.
January
Introduced
Guide
Enables account grouping for easy data analysis and aggregation.
account groups
to facilitate data analysis and aggregation by grouping accounts, enabling simultaneous data analysis across Dashboard, Analytics, MIDs, and Alerts, with options for group management and account settings.
2023
December
HUB
Added
Guide
Explore the stages each product experiences when connected to a MID. It assists in tracking progress, anticipating operational requirements, and addressing challenges efficiently, all crucial for smooth transaction handling and effective decision-making.
status for products
to provide insights into various stages a MID undergoes, including enrollment, transitional phases, and alert statuses, facilitating efficient tracking.
Configured template-based notifications for both first alerts and enrollment-related actions.
November
API
Added the rdr object to the
event
Webhook
for enhanced tracking and data transfer capabilities.
October
HUB
Resolved the issue with copying parameters to ensure accurate data transfer and prevent any inconsistencies or errors in the process.
Add
multilingual function support for Spanish and Portuguese
account search functionality in user management
filters on the
Guide
HUB section for alert management with filtering, exporting, and customization.
Alerts
tab added filters for “BIN,” “Last four,” and “Product,” etc.
Fixed filtering by an amount in the
Guide
HUB section for alert management with filtering, exporting, and customization.
Alerts
-
Guide
The section provides an interface for managing MIDs, with capabilities for detailed inspection, data modification, filtering, and exporting.
MIDs
functionality.
API
Implemented a filter to exclude auth_code with invalid lengths (not equal to 6), ensuring that only codes meeting the specified length criteria are processed.
September
HUB
Added a new “Card Brand” filter and optimized existing filters on the
Guide
HUB section for alert management with filtering, exporting, and customization.
Alerts
-
Guide
The section provides an interface for managing MIDs, with capabilities for detailed inspection, data modification, filtering, and exporting.
MIDs
for more accurate data filtering.
Fixed:
the issue where the select dropdown was being obscured by parent elements, as described in point 1 of the comments
dates, now import accurately in the YYYY-MM-DD format
incorrect alert count issue
API
Added:
alert_date_from and alert_date_to filter fields for enhanced date-based alert filtering