This article explains billing descriptor statuses in the Chargeback.io dashboard. It applies to merchants using Chargeback.io. It does not explain how to add a new billing descriptor or how to unenroll one.
Descriptor Statuses That Don't Require Action
These billing descriptor statuses do not require action in Chargeback.io:
Status | Meaning |
Pending | Onboarding finished but not yet enrolled. |
In Progress | Descriptor activation pending. |
Active | Prevention alerts are turned on. |
Pending Unenroll | Pending deactivation, you may still receive alerts until fully unenrolled. |
Unenrolled | Fully unenrolled. Descriptor released. |
Banned Descriptor | Ineligible descriptor. |
Further reading:
Why is My Descriptor Stuck in Pending?
If your descriptor is stuck in Pending, then the enrollment request wasn't sent.
This usually happens for one of these reasons:
Website not working: Your account must have a valid, live website for verification.
Balance issues: Top up your balance to at least the Minimum threshold
If Support contacted you about a website issue, then reply after you fix the website.
If you topped up your balance, then you do not need to contact Support. The system sends the enrollment request automatically after the balance is updated.
If your website blocks visitors from certain countries, then tell Support which country your business operates from.
That lets the team verify your website with a VPN.
Further reading:
Descriptor Statuses That Require Action
These billing descriptor statuses require action before the descriptor can be activated:
Status | Meaning | What to Do |
Enrolled Elsewhere | Descriptor is enrolled with another provider. | Release or transfer the descriptor from the previous provider. |
Generic Descriptor | Descriptor is too similar to descriptors used by other businesses. | Update it to a more unique and recognizable billing descriptor. |
Verification Needed | Verifi needs an older billing descriptor to verify the account. | Wait for Support to contact you with instructions. |
Need Assistance | No RDR IDs added | Add your RDR IDs. |
Invalid Descriptor | Category for issues not covered by other statuses. | Wait for Support to contact you with more details. |
Invalid ARNs | The ARNs you submitted could not be used. | Add new ARNs. |
You’ll get an email whenever a billing descriptor status changes. That email tells you whether action is required.
Further reading:
How Do I Release My Descriptor From Another Alerts Provider?
If your status is Enrolled Elsewhere, then you need to release the descriptor from the provider that currently has it enrolled.
Step 1: Contact Your Previous Provider
Send this message to their support team:
Hello. Please release my billing descriptor, BINs, and CAID, and send me the Ethoca and Verifi case IDs for those unenrollments. Please let me know once this is complete.
Step 2: Tell Chargeback.io Support
If your previous provider confirms the release, then contact Chargeback.io Support so the enrollment can be sent again.
If You Never Used Another Provider
If you never used another alerts provider, then check with your payment gateway.
Some gateways, including Authorize.net, can enroll merchants in RDR automatically. If your gateway enrolled the descriptor, then contact the gateway’s support team and send the same message above.
Why Are My ARNs Invalid?
If your status is Invalid ARNs, then Verifi could not find an account linked to the ARNs you submitted.
This usually means the ARNs are more than 90 days old.
If you need new ARNs, or if you have fewer than 4 ARNs, then follow the guide for creating new ARNs.
If Support asked you to send new ARNs, then tell them whether the ARNs are newly issued. Verifi asks for that detail during review, so adding it in your reply can help avoid delays.
If you don't want to use ARNs, then you can activate RDR by adding acquiring BINs and CAID instead.
Further reading:
💬 Still need help? Contact Chargeback.io support.