fraud_prevention.mastercard_ethoca_alert.
Alert types
The kind of alert that landed on the payment is recorded asmastercard_ethoca_alert.alert_type.
Both types are actionable, and PayNext treats them the same way: refund in full, cancel the customer’s subscriptions, report the outcome. No other value appears in
alert_type.
How Ethoca alerts work
1
Ethoca sends the alert
The issuer confirms fraud, or the cardholder disputes the charge. Ethoca notifies PayNext.
2
PayNext matches the alert to your payment
PayNext matches the alert to your payment automatically, using the transaction identifiers the network provides. In the rare event an alert can’t be matched, nothing changes on your payments.
3
PayNext refunds and cancels
The disputed payment is refunded in full, and the customer’s active subscriptions at your account are cancelled immediately.
4
PayNext reports the outcome to Ethoca
Ethoca expects a response within 24 hours. PayNext reports the outcome once the refund succeeds. The response is write-once—it cannot be amended afterwards.
refund_reason of fraud_prevention.
Expect more than one alert on the same payment: the issuer and the network can both report the same charge. The payment always shows the most recent alert.
Subscription handling
When an Ethoca alert lands on a payment that belongs to an active subscription, PayNext cancels the subscription immediately. Both alert types are strong signals 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 alert-driven activity from merchant_initiated actions.Set up
1
Contact PayNext support
Request Ethoca enrollment and list the statement descriptors to cover.
2
PayNext enrolls your descriptor with Ethoca
Ethoca alerts enroll by statement descriptor, not by CAID. PayNext handles the registration end-to-end.
3
Done
No code changes required. Alerts appear on the
fraud_prevention.mastercard_ethoca_alert sub-object of every affected payment.mastercard_ethoca_alert payload
Written when Ethoca raises an alert on the payment.
Read the payload
Once
mastercard_ethoca_alert is written, it is never cleared. A later alert on the same payment replaces the whole sub-object—last-write-wins.Where you see results
An alert 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 Mastercard Ethoca Alert (Issuer alert), next to the refund and the subscription cancellation the alert triggered. To find every affected payment, filter the Payments list by Ethoca alert Type or Reason Code. In your own systems, readfraud_prevention.mastercard_ethoca_alert from the payment.
The same alert type is worded differently across surfaces: payment filters and the timeline show Issuer alert, while the analytics chart shows Confirmed fraud. Both refer to
issuer_alert.Related products
Ethoca’s primary coverage is the Mastercard network. Visa CDRN Alerts is the Visa-network counterpart—enroll in both for full pre-dispute coverage across networks.Webhook events
Updates tomastercard_ethoca_alert are delivered on the payment_v2.updated event. See Webhook event types and the Payment webhook object for the full schema.