To enroll your Merchant Identification Numbers (MIDs) with Chargebackhit, you must provide key
Guide
Essential parameters for an effective Chargebackhit onboarding guide.
MID parameters
such as BIN/CAID/MCC/Descriptors. Follow these steps for a smooth transition:
- Notify your current provider and remove the MIDs you plan to transfer.
- Request your provider to disable billing descriptors and BIN/CAIDs.
- Submit a complete list of MIDs to Chargebackhit and choose the necessary products.
- Chargebackhit will handle the Visa and Mastercard communication.
This process generally takes up to 10 business days, depending on your current provider’s response time and the number of MIDs being transferred.
Automating MID addition
You can automate the addition of MIDs to Chargebackhit using API or HUB.
The section provides an interface for managing MIDs, with capabilities for detailed inspection, data modification, filtering, and exporting. HUB interface. This provides a user-friendly way to manage and synchronize MIDs without the need for direct API integration.
You can monitor and troubleshoot the enrollment process using the status field. Each status gives specific details about the current progress or outcome of the import operation:
new- enrollment is queued but has not yet startedsuccess- enrollment completed successfully without errorserror- enrollment completed with errors detailed in theimport_messagerejected- enrollment is rejected for some reasonaccepted- enrollment is accepted and pending further action
For additional alerts after the initial MID setup or complete MID deactivation, contact the support team for assistance.
Failed enrollment reason
When attempting to connect a product to a MID, certain factors may prevent successful enrollment.
If a product or multiple products are requested, each has a product status along with a failure_reason for unsuccessful cases.
Understanding the reasons for failure helps to resolve such cases effectively.
| Failure reason | Description |
|---|---|
| enrolled-by-another-provider | The MID is already enrolled with a different provider and cannot be enrolled here until released. |
| generic-descriptor | The descriptor provided is too generic and must be updated for enrollment. |
| additional-descriptors-required | Additional descriptors on the MID are required to proceed with enrollment. |
| old-arn | The provided ARNs are older than 120 days. You need to submit newer ARNs. |
| invalid-arn | The provided ARNs could not be validated and more ARNs are needed to continue enrollment. |
| invalid-caid | The CAID information is invalid. Contact your payment provider to correct it. |
| invalid-acquirer-bin | The BIN information is invalid. Contact your payment provider to specify it. |
Enrollment tips
When implementing enrollments for
Guide
Resolve disputed Visa transactions before they get escalated.
RDR
,
Guide
Streamline merchant-issuer transaction verification to prevent disputes.
OI
, and
Guide
Leverage post-authorization fraud and dispute notifications to lower payment risk.
Inform
, you may encounter certain challenges. By understanding and addressing these issues, we can ensure a smooth and efficient enrollment process.
- CAID pattern issue
If banks use inconsistent CAID patterns, verify the correct pattern with the bank. - Multiple descriptors
Collect each BIN and CAID combination descriptors to ensure accurate enrollment. - No traffic on MID
Confirm any traffic on the MID with the merchant. If there is traffic, it is necessary to obtain VISA ARNs of the latest chargebacks or transactions, which should be no older than 120 days. The second digit of VISA ARNs must be 4, and an ARN should have 23 digits. Without ARNs, there is a risk of enrolling an incorrect combination. - Shared acquirer BINs/CAIDs
If sharing a BIN/CAID with another entity outside your business network, contact support team for help with enrollment in services such as Ethoca/CDRN.