Chargeback alerts notify you when a customer attempts to dispute a transaction. This helps you take action to avoid disputes and prevent fees, reduce processing costs, and protect your merchant account health.
To start receiving alerts, connect your Merchant IDs (MIDs) and select the alert products that match your needs.
If you use Stripe, Shopify, or Adyen, you can find the required information for the MID connection on their side. See onboarding parameters for step-by-step instructions.
Connect MIDs
You can add MIDs by specifying the required information in several steps.
To add a new MID manually
- Go to your Chargebackhit account > MIDs.
- Click on +Add MID.
- In the pop-up window, select products for the MID.
- Click on Continue to go to Settings.
Settings depend on the selected products. - Review information and click on Add to save the new MID.
If you need to enroll additional products for the added MIDs, you can enroll them directly from the MID details page.
To enroll more products in existing MID
- Go to your Chargebackhit account > MIDs.
- Find the needed MID and click on it.
- On the MID details page, click on Enroll next to the needed product.
- In the pop-up window, select the products you want to enroll.
- Review the MID information.
- Click on Add to apply changes.
When adding MIDs and filling in parameters, refer to:
- Product overview for information about the available products and alert typesPrevent product requires integration since alerts must be processed within seconds.
- Onboarding parameters for details on alert fields
- For RDR alerts, descriptor-BIN-CAID or descriptor-VISA ARNs are mandatory.
- For CDRN, Ethoca, and PayPal alerts, descriptors are mandatory.
- For PayPal alerts, descriptor and Merchant ID are mandatory.
Automate MID addition
You can automate the addition of MIDs to Chargebackhit using API or HUB.
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 started
- success - enrollment completed successfully without errors
- error
- enrollment completed with errors detailed in the
import_message - rejected - enrollment is rejected
- accepted - 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. |
| missing-payment-method | No active payment method is linked to the merchant account. A valid payment method is required to activate this product. |
| insufficient-balance | The merchant's balance is too low to activate this product. The balance must be topped up before onboarding can proceed. |
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, you 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, you need to provide Visa ARNs of the latest chargebacks or transactions, which not be 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 and CDRN. - American Express enrollment requirements
To enroll in American Express Fraud Extended Configuration through CDRN, merchants must provide a valid SE# (10 digits) and meet the following requirements:- Must be based in the U.S.
- Must not be Opt Blue
- Must have a direct relationship with American Express, not through third-party providers such as TSYS or Stripe