When interfacing with Chargebackhit, consider nuances: provide accurate
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.
MID parameters that you need to provide to Chargebackhit when enrolling your
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
- Request your current provider to disable the billing descriptors and BIN/CAIDs
- Provide a complete list of MIDs for enrollment to the Chargebackhit team and select the required products
- Chargebackhit will guide you through the switching process as quickly as possible by contacting Visa and Mastercard directly
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
Using the 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.
While implementing enrollments for RDR, OI, and Inform, may encounter certain challenges.
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
BINshould ideally have a distinct
CAIDpattern. When the pattern is inconsistent, validation of the
MIDby the provider becomes difficult, which may result in incorrect enrollment.
There are situations where multiple descriptors are associated with a single
CAIDcombination. If we receive only one descriptor in such a case, the provider will not permit the enrollment of this
MIDmay not have any associated traffic, making it impossible for the provider to validate.
If your business shares an Acquirer
CAIDwith 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.