Enrollment

Enroll your MIDs in Chargebackhit by providing essential parameters

When interfacing with Chargebackhit, consider nuances: provide accurate Guide
Essential parameters for an effective Chargebackhit's onboarding guide. MID parameters , adhere to the timeline for each step, account for potential delays from provider, and communicate effectively with the Chargebackhit team for a smooth transition.

The main MID parameters that you need to provide to Chargebackhit when enrolling your MIDs include BIN/CAID/MCC/Descriptors.

The timeline for switching to Chargebackhit can vary depending on several factors. Here is a breakdown of the estimated timeframes for each step:

Notify your current provider, and remove the MIDs you wish to transfer from their list

up to 5 business days

Request your current provider to disable the billing descriptors and BIN/CAIDs

up to 1 business days

Provide a complete list of MIDs for enrollment to the Chargebackhit team and select the required products

up to 1 business days

Chargebackhit will guide you through the switching process as quickly as possible by contacting Visa and Mastercard directly

up to 3 business days

Therefore, in total, it can take up to 10 business days (or two weeks) to complete the switch. Factors that can affect the timeline include how quickly your current provider responds and how many MIDs you need to transfer.

Automating the addition of MIDs

As an enhancement to the process, when creating MIDs in your system, you have two options for automating their addition to the Chargebackhit system

Both methods ensure that your MIDs are consistently and accurately reflected in the Chargebackhit system, minimizing potential errors and enhancing efficiency.

Using the enrollment api
Enrollment API allows for direct integration and seamless data transfer between your system and Chargebackhit. Once set up, any update or addition of MIDs in your system will be instantaneously reflected in Chargebackhit, streamlining the enrollment process and reducing manual effort.

Through the HUB
Alternatively, you can utilize the Guide
The section provides an interface for managing MIDs, with capabilities for detailed inspection, data modification, filtering, and exporting. interface of the HUB to automate the addition of MIDs. This provides a user-friendly way to manage and synchronize MIDs without the need for direct API integration.

For additional alerts after initial MID setup or for complete deactivation MID, please contact support team for assistance. This ensures that the customization and maintenance of your MID settings are handled expertly to meet your specific needs.

Enrollment tips

While implementing enrollments for RDR, OI, and Inform, may encounter certain challenges.

By understanding and addressing these issues, we can ensure a smooth and efficient enrollment process.

Issue with CAID pattern
It’s not uncommon for banks to assign CAIDs that do not follow a consistent pattern, leading to zeroes or extra digits at the beginning. Each BIN should ideally have a distinct CAID pattern. When the pattern is inconsistent, validation of the MID by the provider becomes difficult, which may result in incorrect enrollment.

Solution

In case of a pattern issue, we will need to verify the CAID pattern from the bank and enroll the corrected pattern.

Multiple descriptors issue
There are situations where multiple descriptors are associated with a single BIN and CAID combination. If we receive only one descriptor in such a case, the provider will not permit the enrollment of this MID.

Solution

For successful enrollment, we must gather all the descriptors corresponding to the BIN and CAID combination.

Absence of traffic on MID
Sometimes, a MID may not have any associated traffic, making it impossible for the provider to validate.

Solution

We will consult the merchant to confirm the existence of any traffic on the MID. If there is no traffic, we will register the MID as a new entity in the system. However, if there is traffic, it’s necessary to procure the VISA ARNs of the latest chargebacks or transactions, which should be no older than 120 days. For VISA ARN addresses, the second digit must be 4, and it’s important to note that an ARN always consists of 23 digits. If ARNs are not provided, there’s a risk of enrolling an incorrect combination. The provider can validate the correct combination using the ARN, allowing us to connect it. Please note, this process might take some additional time.

Shared acquirer BINs/CAIDs
If your business shares an Acquirer BIN/CAID with a different business entity that you do not have a business relationship with, we are unable to enroll that account in Verifi’s services. This may occur if you use a Payment Facilitator (PayFac) or a Payment Service Provider (PSP) for your acquiring or financial processing.

Solution

Chargebackhit’s support team can assist you with determining if you fall into this category. We would be able to enroll you only in products that use payment descriptors (Ethoca/CDRN).

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.

HUB

Chargebackhit is a user interface that provides a centralized platform for administrators to manage, and view chargeback alerts.

Onboarding parameters

Essential parameters for an effective Chargebackhit's onboarding guide.