Deflection tools (OI + CE 3.0)
Deflection Tools (Order Insight & CE 3.0)
Automatic dispute deflection managed entirely from the Justt Hub. API integration is needed in order to enrich your transactions data and increase the chances to deflect dispute succefully.
Not sure which applies to you? If you want to receive and act on early fraud/dispute alerts, use Pre-Chargeback Alerts. If you want Justt to answer issuer order-lookups on your behalf to prevent disputes, that's Order Insight & CE 3.0 - turn it on in the Hub and you're done.
How to enable it
Order Insight & CE 3.0 is managed entirely from the Justt Hub.
- In the Hub, open Deflection tools.
- Request activation (your Justt contact completes the setup).
- To optimize chances of deflecting your disputes, enriching your transactions is highly recommended.
Data points list, per Verifi - Per transaction:
Required data to match between OI/CE 3.0 inquiry and Transaction:
If you grant Justt permission to fetch all transactions, no further work is needed on your side. Otherwise, you'll need to send the transaction data to Justt through our Transaction endpoint.
Deflection Tools (Order Insight & CE 3.0)
Automatic dispute deflection, managed entirely from the Justt Hub. An API integration is needed to enrich your transaction data and increase the chances of deflecting disputes successfully.
Not sure which applies to you? If you want to receive and act on early fraud/dispute alerts, use Pre-Chargeback Alerts. If you want Justt to answer issuer order lookups on your behalf to prevent disputes, that's Order Insight & CE 3.0 - turn it on in the Hub and you're done.
How to enable it
Order Insight & CE 3.0 is managed entirely from the Justt Hub.
- In the Hub, open Deflection tools.
- Request activation (your Justt contact completes the setup).
- To optimize your chances of deflecting disputes, enriching your transactions is highly recommended.
Data points per transaction (per Verifi)
If you grant Justt permission to fetch all transactions, no further work is needed on your side. Otherwise, send the transaction data to Justt through the Transaction endpoint.
Required data to match an OI/CE 3.0 inquiry to a transaction
| Data point | Status | Field in the Transaction endpoint |
|---|---|---|
| BIN (first 6) + last 4 | Required | transactionCardBin + transactionCardLastFourDigits |
| Transaction amount + currency | Required | transactionAmount + transactionCurrency |
| Transaction date/time | Required | transactionCreatedDate |
| Auth code | Recommended | transactionAuthorizationCode |
| ARN (or TX ID) | Highly recommended | transactionArn (or transactionId) |
CE 3.0 - Required data per transaction
The general Visa CE 3.0 rule: the transactions prior to the CE 3.0 inquiry must match the disputed one on at least 2 of these 4 fields, and at least one of the two must be IP address or device ID.
| CE 3.0 field | Field in the Transaction endpoint |
|---|---|
| IP address | transactionOrderIpAddress |
| Device ID / fingerprint | transactionOrderDeviceId or transactionOrderDeviceFingerprint |
| Account / login ID | transactionCustomerCustomerId |
| Shipping address | transactionShippingToAddressLine1, transactionShippingToAddressLine2, transactionShippingToCity, transactionShippingToState, transactionShippingToZipCode, transactionShippingToCountryCode |
OI - Recommended data (per vertical)
Vertical 1: Delivery Goods
| Data point | Recommended? | Notes | Field in the Transaction endpoint |
|---|---|---|---|
| Customer IP address at purchase | Highly recommended | Key CE 3.0 field | transactionOrderIpAddress |
| Customer device ID | Highly recommended | Key CE 3.0 field | transactionOrderDeviceId or transactionOrderDeviceFingerprint |
| Customer ID / account ID | Highly recommended | transactionCustomerCustomerId | |
| Delivery address | Highly recommended | CE 3.0 matching field | transactionShippingToAddressLine1, transactionShippingToAddressLine2, transactionShippingToCity, transactionShippingToState, transactionShippingToZipCode, transactionShippingToCountryCode |
| Product name, description, quantity, unit price | Highly recommended | Per line item | transactionOrderItemsProductName, transactionOrderItemsProductDescription, transactionOrderItemsProductQuantity, transactionOrderItemsProductPriceValue |
| Order created date | Highly recommended | transactionOrderCreatedDate | |
| Shipping tracking code | Recommended | transactionShippingTrackingCode | |
| Shipping date | Recommended | transactionShippingDate | |
| Expected / actual delivery date | Recommended | transactionShippingDeliveryDate |
Vertical 2: Digital Goods
| Data point | Recommended? | Notes | Field in the Transaction endpoint |
|---|---|---|---|
| Customer IP address at purchase | Highly recommended | Key CE 3.0 field | transactionOrderIpAddress |
| Customer device ID | Highly recommended | Key CE 3.0 field | transactionOrderDeviceId or transactionOrderDeviceFingerprint |
| Customer ID / account ID | Highly recommended | transactionCustomerCustomerId | |
| Download IP address | Highly recommended | IP used to access/download the digital good | transactionOrderDigitalItemDownloadIpAddress |
| Account registration IP address | Highly recommended | transactionOrderAccountRegistrationIpAddress | |
| Account registration device ID | Highly recommended | transactionOrderAccountRegistrationDeviceId | |
| Last account access IP address | Recommended | transactionCustomerLastAccessIpAddress | |
| Product / service name and description | Highly recommended | transactionOrderItemsProductName, transactionOrderItemsProductDescription | |
| Subscription ID, start date, end date, plan, unit cost | Recommended | If subscription-based | transactionSubscriptionId, transactionSubscriptionStartDate, transactionSubscriptionEndDate, transactionSubscriptionPlan, transactionSubscriptionUnitCost |
Vertical 3: Airlines
| Data point | Recommended? | Notes | Field in the Transaction endpoint |
|---|---|---|---|
| Customer IP address at booking | Highly recommended | Key CE 3.0 field | transactionOrderIpAddress |
| Customer device ID | Highly recommended | Key CE 3.0 field | transactionOrderDeviceId or transactionOrderDeviceFingerprint |
| Customer ID / account ID | Highly recommended | transactionCustomerCustomerId | |
| Booking confirmation number | Highly recommended | transactionIndustryFlightPnr | |
| Passenger name(s) | Highly recommended | Per traveler on booking | transactionIndustryFlightTicketsPassengerFirstName, transactionIndustryFlightTicketsPassengerLastName |
| Flight number(s) | Highly recommended | transactionIndustryFlightTicketsFlightNumber | |
| Departure and arrival date/time | Highly recommended | transactionIndustryFlightTicketsDepartureTimestamp, transactionIndustryFlightTicketsArrivalTimestamp | |
| Origin and destination airports (IATA codes) | Highly recommended | transactionIndustryFlightTicketsDepartureLocation, transactionIndustryFlightTicketsArrivalLocation | |
| Ticket class | Recommended | Economy, Business, First, etc. | transactionIndustryFlightTicketsClass |
Vertical 4: Hotels
| Data point | Recommended? | Notes | Field in the Transaction endpoint |
|---|---|---|---|
| Customer IP address at booking | Highly recommended | Key CE 3.0 field | transactionOrderIpAddress |
| Customer device ID | Highly recommended | Key CE 3.0 field | transactionOrderDeviceId or transactionOrderDeviceFingerprint |
| Customer ID / account ID | Highly recommended | transactionCustomerCustomerId | |
| Booking confirmation number | Highly recommended | transactionIndustryTourismReservationKeyCode | |
| Hotel / property name | Highly recommended | transactionIndustryTourismListingTitle | |
| Check-in date | Highly recommended | transactionIndustryTourismReservationCheckIn | |
| Check-out date | Highly recommended | transactionIndustryTourismReservationCheckOut | |
| Guest name | Highly recommended | May differ from billing name | transactionIndustryTourismReservationGuestFullName |
| Room type | Recommended | transactionIndustryTourismListingRoomType | |
| Total stay amount | Recommended | transactionIndustryTourismReservationGuestTotalPrice |
Updated 7 days ago