NEXT Alerts Setup
v0.4Updated Sep 28, 2026
To set up NEXT Alerts, give us every statement descriptor and map each one to its Payments account, store, and brand. We also need your legal and trading names, live customer-facing URLs, monitored support contacts, and a setup contact at your business. Once setup is complete, NEXT handles alerts automatically.
What NEXT Alerts does
A chargeback alert warns that a customer has disputed a purchase before it becomes a chargeback. NEXT receives the alert and handles it automatically, usually by refunding the transaction.
Three card network programs make up the service:
Ethoca Alerts
Covers Mastercard, and Discover and American Express where the issuer participates. NEXT refunds the disputed transaction on your behalf.
Verifi CDRN
Covers Discover and American Express through participating issuers. NEXT refunds the disputed transaction on your behalf.
Verifi RDR
Covers Visa. The network refunds qualifying disputes under rules you confirm with us in advance.
NEXT uses the applicable programs for the card brands you accept.
NEXT Alerts covers transactions processed through NEXT Payments. Volume you run through a third-party gateway is not covered, and you can keep whatever dispute-alert provider you already use for it.
Alerts reduce chargebacks but cannot prevent every one
Not every dispute generates an alert. Coverage depends on whether the cardholder's bank participates in an alert program. You must still monitor your chargeback rate and respond to chargebacks that reach the Payments portal.
Before we set it up
If your NEXT Payments account is already active, ask your NEXT contact to start Alerts setup.
Before we activate NEXT Alerts for your account:
- Confirm that your NEXT Payments account is active.
- Sign the NEXT Alerts Addendum. The agreement lists your per-alert fees, and we charge them only after it takes effect.
- Complete and verify the information in the next section.
To include RDR in your NEXT Alerts setup, you must also confirm the automatic refund rules in writing. NEXT verifies your account details and tells you when setup is complete for each program. You must keep the information you provide accurate and current.
What NEXT needs from you
Alerts are matched to your transactions through your billing descriptors. Cardholders also use your business details to recognize a purchase and contact you directly. Incomplete or stale information can prevent a match or let a dispute proceed. Send us all of the following:
| What we need | Why it matters |
|---|---|
| Every statement descriptor you use, exactly as it appears on a cardholder's statement | NEXT uses descriptors to match alerts to your business. Give us a unique descriptor for each store or brand so every alert maps to the right place. Include any campaign-level overrides, not just the store default. We cannot match disputes for a descriptor you have not given us. |
| Which Payments account, store, and brand each descriptor belongs to, with that store's URL | Tell us which NEXT Payments account each descriptor belongs to. We use your Payments records to verify every active account and descriptor. |
| Legal entity name and trading name for each store or brand | Card networks and their alert programs identify your business by these names. They must match the entity that holds the payments account. |
| Live customer-facing URLs: storefront, a product information page, your contact page, your customer support page, and your refund, shipping, and terms policy pages | A cardholder who cannot recognize a charge or contact you may go to their bank instead. These pages help customers identify the purchase, find product information, and reach support. Every link must open a live page, not a staging URL or a page behind a password. |
| Customer support contacts: the support email address and phone number your customers actually reach | A support route that bounces or goes unmonitored turns customer questions into disputes. |
| A setup contact at your business | We contact this person with setup questions and activation updates. |
Check your descriptors against a real statement
The descriptor you configured and the text a cardholder sees are not always identical because gateways and card networks can truncate or reformat it. Check a recent card statement or banking app entry before sending descriptors to us. If you use campaign-level overrides, check those in the Campaigns App too.
Confirming RDR refund rules
Verifi RDR works differently from the other programs. Visa's program rules and the refund parameters on your NEXT Payments account determine which disputes qualify. RDR refunds qualifying disputes automatically. The refund appears on the original order as an external refund, and there is no alert for you to work.
RDR may already be active on your NEXT Payments account when you start NEXT Alerts setup. Existing RDR refunds continue while we complete the setup. The NEXT Alerts Addendum sets your alert fees, and we agree the RDR refund parameters with you in writing before we confirm RDR as part of NEXT Alerts.
Approve changes that widen automatic refunds
Any change that could increase how much RDR refunds automatically, such as a higher transaction-amount ceiling or a longer window, takes effect only after you confirm it in writing. You can ask us for the current rules at any time.
RDR does not cover every Visa dispute
RDR does not refund a Visa dispute that falls outside your agreed rules. The dispute can then proceed to a chargeback. Narrower rules allow fewer automatic refunds.
How setup works
Sending us your information starts the setup. We will confirm when NEXT Alerts is ready for every applicable program.
You send us your setup information
Send every descriptor, its Payments account, store, and brand, your legal and trading names, customer-facing URLs, and support contacts.
We verify your account and submit the details
We use your Payments records to verify every active account and descriptor, then complete the setup with each program.
We confirm setup
We tell your setup contact when NEXT Alerts is ready for each program. One program may be ready while another is still pending.
Wait for our confirmation
Until NEXT confirms that setup is complete, continue working disputes through your existing process and monitor the Disputes tab, as described in Submitting chargeback defense evidence.
Coverage can begin at different times for each program and participating bank. Use the activation status from your NEXT setup contact rather than assuming that every program starts on the same day.
When an alert arrives
NEXT handles alerts automatically. If an alert matches an eligible transaction, we refund it and place the order on hold. You do not need to monitor an alerts queue.
What you will see
For a matched order, you may see a refund you did not issue and an order hold or canceled fulfillment. Do not reverse the hold or ship the order. If an alert does not require a refund, NEXT closes it without changing the order.
The refund appears differently depending on the program:
Ethoca and CDRN
We issue the refund against the disputed transaction for the amount still available on it, then report the outcome.
Verifi RDR
The card network has already refunded the payment. We record it against the order as an external refund rather than refunding a second time.
When alert fees apply
Your NEXT Alerts Addendum defines the fees and billing terms for matched alerts. Use the signed addendum when reconciling charges.
Alerts and chargebacks need different handling
NEXT handles alerts automatically. Chargebacks that are not prevented still appear in the Payments portal and require a response, as described in Submitting chargeback defense evidence.
Accurate descriptors help NEXT match alerts to your transactions. If we cannot match a transaction, we cannot refund it before the dispute becomes a chargeback. Keep the descriptor list in What NEXT needs from you complete and current.
Keeping details current
Alerts can stop matching when your descriptors or business details change. Tell us before any of these details change:
Tell us before the change
Contact us before you add, change, or retire a store, brand, campaign descriptor, domain, support contact, or policy page. Tell us about a rebrand, legal entity change, or new setup contact too.
NEXT updates the setup
We submit the new details and tell you when the change is active.
Tell us before a descriptor changes
A new descriptor is not covered until we confirm it is active. Contact us before a launch or rebrand so we can complete the update first.
Readiness checklist
- Confirm that your NEXT Payments account is active.
- Sign the NEXT Alerts Addendum and confirm your fees.
- List every statement descriptor, including campaign overrides, and check each one against a real card statement.
- Use a unique descriptor for each store or brand, then map it to its Payments account, store, and brand.
- Provide the legal entity and trading name for each store or brand.
- Check that every storefront, product, contact, support, and policy URL is live and correct.
- Confirm that customers can reach your support email address and phone number.
- Review and approve the RDR refund rules in writing.
- Wait for NEXT to confirm that setup is complete for every applicable alert program.
- Tell your finance and fulfillment teams that alert refunds and order holds are automatic. They must not reverse the hold or ship the order.
Key links
Submitting chargeback defense evidence
How to find a chargeback in the NEXT Payments portal, decide whether to accept or defend it, and submit a defense evidence document before the response deadline.
Notification examples
This guide shows example notification emails, sample subject lines, and when each message is sent so you can decide which ones your customers should receive from NEXT. New stores start with customer notifications turned off, so NEXT sends your customers almost no order, refund, or subscription emails until you turn those notifications on. The few exceptions are listed under Turn on the notifications you want.