Dispute Extract File Details for Online Payments in Lighthouse Business Manager

Description: The dispute extract file provides a daily account of activities related to dispute cases and cycles (e.g., retrieval requests, chargebacks, representments, etc.).

For more information on Enterprise Extracts, refer to the Enterprise Extracts Guide.

---

The data elements provided reflect information specific to the nature of disputes (cardholder / Issuer’s claim), the actions performed, and some of the more pertinent details related to the original authorization/transaction and how they were initiated.

How to Use the Extract

Merchants and/or other parties who receive the dispute data extract use this information primarily in support of (a) submitting a response to our dispute processing team (b) and for dispute reporting purposes.

Key events reflected but not limited to include notifications of dispute cycles and activities that have occurred:

• Chargeback 
  • A chargeback has been received and is pending a response from you for representment consideration.
• Chargeback Recall
  • A chargeback recall initiated by an Issuer has been received, negating a previously received chargeback.
  • Merchant response is no longer required.
• Chargeback Resolution
  • A chargeback has either been resolved to your account (debit) or it’s been represented back to the issuing bank on your behalf (e.g., identified a merchant-initiated credit for the related sale).
•  Reversal Request
  • Confirmation that your response/reversal request for a chargeback has been received and that it’s now pending dispute analyst review.
• Reversal Request Review 
  • A merchant’s reversal request has either been approved for representment generation (credit back to your account), or it’s been declined (subsequent/additional response required from you).
• Pre-arbitration Case
  • A pre-arbitration case was received from an issuer as they are continuing to dispute the related charge following their receipt of a representment.
  • A subsequent response from you is required.
• Retrieval Request
  • A retrieval request has been received and is pending a response from you.
  • Response required to help prevent receipt of a chargeback and associated debit.
• Retrieval Request Still Pending
  • Follow up notification that a previously received retrieval request is still pending a response from you which again is still required to help prevent receipt of a chargeback and associated debit.

While dispute-based notifications may be sent to you via other means, the dispute data extract provides a consolidated mechanism for keeping you informed of dispute activities in a timely manner.

The data provided can be used for consumption of dispute-related data via merchant systems/platforms in support of their handling and participation in the dispute process.

File Name 

• EnterpriseCustomer_YYYYMMDD_Enterprise_Dispute_Extract.csv
  • EnterpriseCustomer  is the given customer’s name
  • YYYYMMDD  is the given date for the file generated; it is based on the previous day’s date and will represent the data that was provided by the various card acquirer systems within Shift4.

Location

• Shift4 SFTP / Customer-Specific Folder / Prod

File Format

• Comma Separated Values (CSV)

Frequency

• Daily, based on the reception of data from the various card acquirer systems within Shift4. We are currently expecting all data to be available by 4:00 a.m. ET and the extracts should be available within the SFTP sites by 11:00 a.m. EST.

Content

#	Data Element	Data Type	Description
1	MerchantId	nvarchar(20)	Your acquirer's identification number
2	NetworkReferenceNumber	nvarchar(30)	Identification number for a credit card transaction assigned by the acquirer.
3	CardAccountNumber	nvarchar(20)	Masked value of the credit card number used for the transaction.
4	DisputeAmount	money	The amount being disputed. This may not always be equal to the amount of the associated sales transaction
5	MerchantCategoryCode	nvarchar(4)	The Merchant Category Code, which is the standard industry code for a specific industry or business. See Shift4 MerchantCategory reference table for values
6	DisputeRecordNumber	nvarchar(13)	Unique number assigned by the system Format:YYYYJJJ###### YYYY is the year JJJ is the 3-character Julian day  ###### is the 6-character case number.
7	ChargebackReferenceNumber	nvarchar(23)	Value assigned by the Card Issuer (Visa) referencing the issuer's internal case number, or assigned by the Card Association (MasterCard, Discover, American Express), referencing the dispute management systems case number. Value passed on MasterCard's Clearing and Settlement system file (T112/IPM) Field DE 95 as Card Issuer Reference Number, and in the MasterCard Dispute Resolution TQR4 file as Cycle ID.
8	InitialReportDate	date	Date case was loaded into the dispute system once received from the card association. Format: YYYY-MM-DD
9	TransactionType	nvarchar(2)	Indicates the type of transaction being disputed. See Shift4 TransactionType reference table for values.
10	CardBrand	nvarchar(2)	Type of card used in the transaction. See Shift4 CardBrand reference table for values.
11	AdjustmentType	int	Indicates the dispute cycle. Also referred to as the type of case. E.g. Retrieval request, chargeback, pre-arbitration See Shift4 AdjustmentType reference table for values.
12	OriginalTransactionDate	date	Transaction date as reported by the issuer Format: YYYY-MM-DD
13	DBAName	nvarchar(100)	Your DBA Name
14	ChargebackActionCode	nvarchar(2)	Indicates the type of action that has occurred for the current dispute cycle. E.g. Chargeback received, merchant debited for chargeback, chargeback represented See Shift4 ChargebackActionCode reference table for values
15	IssuerAdjustmentReasonCode	nvarchar(6)	Issuer designated reason code identifying why the transaction is being disputed
16	CurrencyCode	nvarchar(3)	International standard 3 digit currency code
17	ResolutionTo	nvarchar(1)	The receiving party to which the case cycle was resolved. E.g. Representment to Issuing bank, chargeback debit to merchant See Shift4 ResolutionTo reference table for values.
18	DebitCreditIndicator	nvarchar(1)	Indicates whether or not the dispute cycle presented any financial impact in the form of a debit or credit preceding the bulleted values. Possible values: D: Debit C: Credit N: Non Financial
19	RecordType	nvarchar(1)	Indicates that case is a chargeback reversal initiated by the issuer (value "R") in order to recall/counter a previously received chargeback (value SPACE).
20	FirstChargeBackFlag	nvarchar(1)	Type of Case Involved.  If AdjustmentTypeCode is 1, then it is the first chargeback See Shift4 Adjustment Type reference table for possible values.
21	ResolvedDate	date	Date that a case cycle has been resolved/actioned which may or may not result in financial impact to you. Format: YYYY-MM-DD
22	IssuingBank	nvarchar(10)	Issuing Bank of the Card used in initial transaction.
23	MerchantAmount	money	Amount posted to you in the event that a dispute based action resulted in a financial impact. Typically the same as DisputeAmount but may differ if case resolution is split.
24	TransactionID	nvarchar(15)	Unique card association identifier per transaction
25	Provider	nvarchar(5)	Identifies the payment provider
26	CountryCode	nvarchar(2)	Two letter country code, e.g. US, GB
27	DueDate	Date	Date when a dispute expires
28	PartialRepresentment	nvarchar(1)	Y/N field that will indicate if there was only a partial payout from the full dispute amount
29	VendorReference	nvarchar(256)	Reference received from the Gateway
30	OriginalReferenceNumber	nvarchar(30)	Reference number previously provided within the original sales transaction by the merchant or their vendor for customer / purchase reference purposes upon receipt of a dispute
31	ReasonDescription	nvarchar(50)	Descriptive explanation of the card brand dispute reason code referenced within this extract as Issuer AdjustmentReasonCode
32	VISARDRIndicator	nvarchar(1)	For merchant’s enrolled within Visa’s Rapid Dispute Resolution program, this field may indicate that the merchant previously accepted dispute liability as part of the RDR process. Possible Values: Y - Visa RDR Case (response not required) space filled - Standard Chargeback Case
33	CorrelationID	nvarchar(12)	Universal transaction identifier allowing linking among Transaction, Authorization, and Dispute data

Please proceed to the next article on this topic: Interchange Extract File Details.