Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.paynext.com/llms.txt

Use this file to discover all available pages before exploring further.

PayNext integrates with Visa and Mastercard dispute-prevention programs natively. Once your merchant account is enrolled, the integration is fully managed—PayNext receives every inquiry and notification, supplies the data the network needs, and writes the outcome to the payment payload, the timeline, and webhook events. You read results the same way you read every other payment field.

​
Supported products

Each product is a separate enrollment. Enable any combination via PayNext support.
ProductStatusWhat it does
Visa Order Insight (OI / OID)AvailableShares transaction details with the issuing bank so the cardholder can recognize the charge—delivered live to the agent during a call (OI) or inside the cardholder’s banking app (OID). Reduces fraud notifications and friendly-fraud disputes.
Visa Compelling Evidence 3.0 (CE)AvailableWhen a dispute is filed, Visa evaluates merchant evidence; eligible cases are deflected automatically before they become chargebacks.
Visa Rapid Dispute Resolution (RDR)AvailableVisa evaluates incoming disputes against your refund rules and auto-refunds eligible cases.
Visa (Verifi) Chargeback AlertsComing soonPayNext auto-refunds incoming disputes before they become chargebacks. Covers both Visa and Mastercard networks, with primary coverage on Visa.
Mastercard (Ethoca) AlertsComing soonPayNext auto-refunds incoming disputes across Mastercard and Visa networks, with primary coverage on Mastercard. Complements Verifi alerts—enroll in both for full network coverage.
Mastercard Consumer ClarityComing soonMastercard’s equivalent of Visa Order Insight—transaction details surfaced to cardholders inside the issuer’s banking experience.

​
How it works

1

The network sends a request or notification

Visa or Mastercard sends an inquiry (cardholder lookup) or a notification (CE outcome, RDR decision, alert) to PayNext.
2

PayNext ingests and matches the event to your payment

The event is matched to a PayNext payment using the network payment ID and other identifiers.
3

PayNext resolves the query

For inquiries, PayNext serves the receipt data the network needs. For notifications, PayNext applies the outcome to the payment.
4

The outcome appears on the payment

The fraud_prevention block is updated, an event is written to the payment timeline, and a payment.updated webhook fires.

​
Subscription handling

When a fraud prevention event lands on a payment that belongs to an active subscription, PayNext acts on the subscription that paid for that charge.
EventSubscription action
OI lookup (visa_order_insight.type = "OI")Scheduled for cancellation at the end of the current billing period; status becomes scheduled_for_cancellation
OID lookup (visa_order_insight.type = "OID")No action—self-service lookups are not treated as a dispute signal
CE lookup (visa_order_insight.type = "CE")Scheduled for cancellation at the end of the current billing period
CE terminal outcome (visa_compelling_evidence written)Cancelled immediately; status becomes cancelled
RDR outcome (visa_rdr written)Cancelled immediately; status 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 standard subscription.updated webhook.

​
Where you see results

SurfaceWhat you get
Payment payloadThe fraud_prevention block on every payment that received an inquiry, decision, or alert. See Visa Order Insight & CE and Visa RDR for the full schema.
Payment timelineEvery inquiry and outcome is recorded on the payment’s timeline in Dashboard → Payments → [payment].
WebhooksThe payment.updated event delivers the updated fraud_prevention block. See the Payment webhook object.
AnalyticsProgram effectiveness is tracked in the Dashboard analytics views.
FiltersDashboard → Payments filters let you narrow by OI lookup, OI channel (OI / OID / CE), CE outcome, and RDR outcome—built on the same payload fields.

​
fraud_prevention block

Each available product writes to its own sub-object. Sub-objects are independent—any subset can be present. 
{
  "id": "pay_ac147ba9-d16f-40ba-829a-242968e9b7fe",
  "fraud_prevention": {
    "visa_order_insight": {
      "type": "CE",
      "insight_id": "4bfe0233-7b19-4e82-9c0a-1e8d2f3c5b11",
      "updated_at": "2026-04-23T12:45:51Z"
    },
    "visa_compelling_evidence": {
      "status": "accepted",
      "case_id": "a6cf8f35-d753-4a66-8e09-65b451c96eed",
      "updated_at": "2026-04-23T12:45:54Z"
    },
    "visa_rdr": {
      "status": "accepted",
      "case_id": "3d2ec10c-8a6c-4ef2-b7e9-0c7b1a9f23ea",
      "reason": {
        "code": "10.4",
        "name": "Other Fraud — Card Absent Environment",
        "category": "fraud"
      },
      "updated_at": "2026-04-23T12:45:51Z"
    }
  }
}
Presence of a sub-object means the corresponding signal fired for this payment. Absence means nothing has fired (or, for CE, that a terminal outcome has not landed yet). Don’t assume any sub-object is present.

​
Enroll

1

Contact PayNext support

Request enrollment for the products you want and list the integrations to enable them on.
2

PayNext enrolls your merchant with the network

OI, OID, CE, and RDR enroll by per integration. Chargeback alerts and Consumer Clarity enroll by statement descriptor. PayNext handles the registration end-to-end. For RDR, PayNext also coordinates rule configuration with Visa.
3

Confirm your Dashboard configuration is complete

The data PayNext supplies to the network is built from your existing Dashboard fields—Organization and Integrations. Keep these up to date and the integration runs automatically.
Once enrolled, the integration is automatic—no code changes are required.