fraud_prevention.mastercard_consumer_clarity.
Lookup channels
The channel that triggered the most recent lookup is recorded asmastercard_consumer_clarity.type.
DIGITAL accounts for the large majority of lookups. The enum is open—Mastercard may add channels without a version bump, and unrecognized values pass through verbatim.
First Party Trust lookups compare identity fields—device fingerprint, email, phone, billing details—across the three receipts. When enough fields match, the dispute is assessed as first-party fraud and deflected. Each of the three lookups is recorded on its own payment with
type: "FIRST_PARTY_TRUST".Subscription handling
A Consumer Clarity lookup is informational: it signals that a cardholder is checking a charge, not that a dispute has been filed. PayNext records the lookup on the payment but takes no automatic action on the subscription.This differs from Visa Order Insight, where an
OI (call-centre) lookup schedules the subscription for cancellation. Consumer Clarity lookups never change subscription state on their own.Setup
There is no integration work beyond keeping your Dashboard configuration current. The receipt PayNext serves is built from data you already provide.Required fields
These are required Dashboard fields—if your account is set up, they’re already filled in. Keep them current and Consumer Clarity works automatically.
Consumer Clarity enrolls by statement descriptor, not by CAID. Contact PayNext support to enroll; PayNext registers your descriptor with Mastercard end-to-end.
Captured automatically
Device data—IP address, geolocation, user agent—is captured by the Web SDK at checkout and is included in the receipt where available. No additional code is required.mastercard_consumer_clarity payload
Written every time Mastercard runs a Consumer Clarity lookup, regardless of channel. The latest lookup overwrites all three fields atomically.
This sub-object has no
status field. Mastercard never reports back what the cardholder did with the receipt, so there’s no terminal state to capture. Presence of mastercard_consumer_clarity means at least one lookup happened; type and updated_at describe the latest one.Read the payload
Once
mastercard_consumer_clarity is written, it is never cleared. A later lookup overwrites type, insight_id, and updated_at—last-write-wins.Webhook events
Updates tomastercard_consumer_clarity are delivered on the payment_v2.updated event. See Webhook event types and the Payment webhook object for the full schema.