Order Insight is a chargeback prevention solution that allows issuers and merchants to communicate in real time, share information that helps clear up any confusion about a purchase, and resolve disputes without a chargeback.
But what information is passed from your business to the cardholder’s issuing bank?
Want a high-level overview of Order Insight and how it works? Check our complete guide first.
Order Insight API Data
The Order Insight API can pass hundreds of different data points. Data is organized into different objects — some are required and some are not.
Here’s an overview of each object in the Order Insight response.
SOME THINGS TO NOTE
Before we dive into the specifics, there are a couple generalizations to note.
- Some fields are required. If a required field is not included in the response, the entire response will be terminated and no data will be shared with the issuer.
- In theory, the only information you have to share is the required fields. However, the more data you share, the better the chance of preventing a chargeback.
- The information provided here reflects the 2024 API documentation and is intended for educational purposes only. Changes may have been made since publication. Please refer to Verifi’s official API documentation for development work.
Receipt Object
The receipt object is required. The following elements can be included.
Payment Information Object
The payment information object is not required but is highly recommended. The following elements can be included.
Purchased Product Object
The product purchased object is required. The following elements should be provided for each item purchased.
Customer Information Object
If you want CE 3.0 protections, the account ID field may be required. If you are not seeking CE 3.0 protections, this object is recommended by not required. The following elements can be included.
Address Object
If you want CE 3.0 protections, the fields in this object (except address 2) may be required. If you are not seeking CE 3.0 protections, this object is recommended by not required. The following elements can be included.
NOTE
Data in this object needs to be carefully managed.
In order to qualify for Visa CE 3.0 protections, you must be able to match the disputed transaction to two previously undisputed transactions. The address fields across all three should match.
Spelling errors or abbreviations can negatively impact transaction matching. For example, “ST” does not necessarily equal “street”. If you are interested in CE 3.0 protections, you will probably want to use a service to verify and standardize the address at checkout.
Merchant Information Object
The merchant information object is required. The following elements can be included. The goal is to provide information that will help the cardholder recognize your business.
Store Details Object
The store details object is required. If you have multiple stores or locations where purchases are made, describe where the actual purchase happened. The following elements can be included.
Delivery Details Object
The delivery details object is recommended but not required. The following elements can be included.
Location Object
The location object is commonly used to identify a location with geolocation coordinates or address. The following elements can be included.
Geolocation Object
This object is not required. However, if you include one field, you must include the other. Both fields are required if a response is sent.
The following elements can be included.
Device Object
The device object is recommended but only required if you are seeking CE 3.0 protections. The following elements can be included.
Industry Specific Objects
Industry-specific objects allow merchants in certain verticals to share information that might not be applicable to all businesses. If these objects don’t apply to your business, you can ignore them.
Specified industries include:
- Flights
- Hotels
- Rideshares
- Car rentals
Flight Details Object
The following elements can be included.
Hotel Details Object
The following elements can be included.
Rideshare Details Object
The following elements can be included.
Car Rental Details Object
The following elements can be included.
For more than a decade, Jessica Velasco has been a thought leader in the payments industry. She aims to provide readers with valuable, easy-to-understand resources.
