fraud_prevention.visa_cdrn_alert.
Case types
The kind of case that landed on the payment is recorded asvisa_cdrn_alert.type.
DISPUTE is the only case type PayNext acts on and the only one recorded on a payment, so visa_cdrn_alert.type always reads DISPUTE.
CDRN also defines cancellation and notice case types. PayNext doesn’t record these—they are advisory, and the same underlying dispute normally arrives as an actionable
DISPUTE case anyway.How CDRN cases work
1
Verifi sends the case
The cardholder disputes the charge with their bank. Verifi’s network raises a case and notifies PayNext.
2
PayNext matches the case to your payment
PayNext matches the case to your payment automatically, using the transaction identifiers the network provides. In the rare event a case can’t be matched, nothing changes on your payments.
3
PayNext refunds and cancels
The payment is refunded in full, and the customer’s active subscriptions at your account are cancelled immediately.
4
PayNext reports the outcome to Verifi
Once the refund succeeds, PayNext reports the case as resolved. Verifi closes it, and the dispute never becomes a chargeback.
refund_reason of fraud_prevention.
Expect more than one alert on the same payment: a cardholder dispute can be reported through more than one network. The payment always shows the most recent case.
Subscription handling
When a case lands on a payment that belongs to an active subscription, PayNext cancels the subscription immediately. A dispute filing is a strong signal that the cardholder no longer wants the charge to recur. The subscriptionstatus becomes cancelled.
All of the customer’s active subscriptions at your account are acted on. Subscriptions the same customer holds at other merchants are not affected. Track changes via the subscription_v2.cancelled webhook.
Both actions are attributed automatically as
fraud_prevention: the refunded payment’s refund_reason and the cancelled subscription’s cancellation_details.reason are set to fraud_prevention, with trigger_payment_id pointing at the disputed payment—so you can distinguish case-driven activity from merchant_initiated actions.Set up
1
Contact PayNext support
Request CDRN enrollment and list the statement descriptors to cover.
2
PayNext enrolls your descriptor with Verifi
CDRN enrolls by statement descriptor, not by CAID. PayNext handles the registration end-to-end.
3
Done
No code changes required. Cases appear on the
fraud_prevention.visa_cdrn_alert sub-object of every affected payment.visa_cdrn_alert payload
Written when Verifi raises a case on the payment. All five fields are always present.
Read the payload
Once
visa_cdrn_alert is written, it is never cleared. A later case on the same payment replaces the whole sub-object—last-write-wins.Where you see results
A case is recorded on the payment it matched, so the payment is where you look for it—there’s no separate alerts screen. To check a single payment, open Dashboard → Payments, select the payment, and read its timeline: an entry reads Visa CDRN Alert (Dispute), next to the refund and the subscription cancellation the case triggered. To find every affected payment, filter the Payments list by CDRN case Type or Reason Code. In your own systems, readfraud_prevention.visa_cdrn_alert from the payment.
Related products
CDRN’s primary coverage is the Visa network. Mastercard Ethoca Alerts is the Mastercard-network counterpart—enroll in both for full pre-dispute coverage across networks.Webhook events
Updates tovisa_cdrn_alert are delivered on the payment_v2.updated event. See Webhook event types and the Payment webhook object for the full schema.