Daily chargeback report

Daily chargeback reports help you review and manage chargeback cases. This is not a financial report. Both new chargebacks and updates for ongoing cases appear in the same report file.

You receive this report using the Secure File Transfer Protocol (SFTP). SFTP lets you receive and send information securely.

This report is generated automatically, and pushed to your assigned subfolder on the secure server, where you access it.

Important

SFTP must be set up before you create a report request with Cross River’s Data Team. This allows the reporting team to automate the delivery of Settlement and Reconciliation reports to the appropriate folders.

Contact p2p@crossriver.zendesk.com if you have any issues accessing your reports.

Report distribution

Recipients include user-partners only.

Report structure

The chargeback report filename uses this convention: PartnerName_CRB_Chargebacks_Details_YYYY-MM-DD.csv

The chargeback report structure includes the fields presented here.

	Field	Required	Default	Description
1	CRBChargebackId	✓		Unique reference number generated by CRB for each chargeback case, used as the name of the evidence artifact
2	ExternalVendorID	✓
3	ChargebackState	✓		First chargeback (new chargeback) Representment (merchant provided compelling evidence the next day etc) Incoming pre-arbitration (MC) Outgoing pre-arbitration (Visa) [out to the issuer]
4	OriginalTransactionRequestId	✓		ID of the automatically created transaction associated with this settlement day - ARN
5	ReasonCode			Network-specific reason code that identifies the evidence the merchant must provide to win the case
6	ReasonDescription			Description corresponding to the network Exception Code
7	ChargebackRequestedAt			Timing of the dispute request
8	DaysOutstanding			Days since dispute was opened
9	ResolutionType
10	AdjustmentType		Financial record	Debit Credit N/A
11	AdjustmentAmount		Financial record
12	ActionStatus
13	LastStatusDate			Date of most recent change in Action Status
14	CreditCardId	✓		Token for the signed-up card, received when you first sign up the card. One token per card holder.
15	ChargebackAmount			Amount disputed by cardholder. May differ from the Original Settled Amount in the case of a partial chargeback or due to differences in the exchange rate.
16	Network	✓		Card network the transaction was processed through
17	OriginalTransactionResponseCode	✓		Original transaction - Card networks return response codes to approve or decline a transaction. They follow the standards set by ISO 8583:1987, which defines a specific message format so that different systems can communicate. Every network can adapt the standard for their own use
18	OriginalTransactionResponseDescription	✓		Original transaction - Card networks return response codes to approve or decline a transaction. They follow the standards set by the International Organization for Standardization (ISO) 8583:1987, which defines a specific message format so that different systems can communicate. Every network can adapt the standard for their own use.
19	OriginalTransactionRequestedAt	✓		Time when the transaction was requested by the partner. Dates in UTC.
20	OriginalActualTransactionAt	✓		Time at which the transaction was processed by the network. Dates in UTC.
21	RetrievalReference	✓		RRN
22	NetworkIdentifier	✓		Network transaction identifier
23	OriginalTransactionAmount	✓		Transaction Amount. Passed in to Create Transactions APIs Push transactions are (-) Pull transactions are (+)
24	NetworkFee
25	InterchangeFee			Interchange fee
26	OriginalTransactionType	✓		Pull Push Reversal Chargeback
27	FirstName
28	LastName
29	CardBrand
30	CardProductType
31	First6
32	Last4
33	CustomInstructions			Default-Empty

Complex field values

This section presents possible values for specific fields when they include a large number of possible values.

Chargeback state types

This table shows you values for the ChargebackState field. The type explains the stage of processing the chargeback reached at report generation time.

	Dispute state type	CB Type Description	Financial	Comments
1	First Chargeback	Initial Chargeback	✓	Settlement file is already debited
2	Merchant Response Review	Merchant Response received and under review
3	Outgoing Pre-Arbitration	Merchant Response was accepted and Outgoing Pre-Arb was created and submitted to Issuer (Visa Allocation Disputes only)
4	Representment	Merchant Response was accepted and Representment was processed	✓
5	Incoming Pre-Arbitration	Issuer has responded to previously processed Representment and has submitted a Cardholder response via an Incoming Pre-Arbitration	✓
6	Arbitration	An Arbitration Ruling has been filed by either the Issuer or Acquirer
7	Outgoing Pre-Compliance	Acquirer has submitted a Pre-Compliance request to the Issuer
8	Incoming Pre-Compliance	Issuer has submitted a Pre-Compliance request to the Acquirer		If the merchant accept it - it becomes financial(step 5)
9	Compliance	A Compliance Ruling has been filed by either the Issuer or Acquirer
10	GFC	Good Faith Collection has been submitted by either the Issuer or Acquirer
11	Chargeback Reversal	See ARN and Internal Case# for reference to original Chargeback	✓	(The issuer recalled it within 3 days)
12	Duplicate Chargeback	See ARN and Internal Case# for reference to original Chargeback	✓	Imminently “fight” it and get the money back

Resolution types

This table shows you values for the ResolutionType field. Resolutions are different ways a chargeback case is finished.

	Resolution Type	Resolution Type Description
1	Resolved to Merchant	Merchant is liable - see ActionStatus for next steps
2	Resolved to Issuer	Issuer is liable - See ActionStatus for update
3	Resolved to Write Off	Acquirer/Processor is liable
4	Merchant Response Denied	Submitted Merchant Response has been denied - See Action Status and Custom Filed for Reason
5	Pending (see Action Status)	Case is pending an external action - See Action Status and Custom Field for Reason
6	Issuer Denied Pre-Arb/Comp	See Action Status and Custom Field for Reason and Next Steps
7	Issuer Accepted Pre-Arb/Comp	Issuer has accepted liability
8	Acquirer Denied Pre-Arb/Comp	Acquirer has denied incoming case. Pending response from Issuer
9	Acquirer Accepted Pre-Arb/Comp	Acquirer has accepted liability on behalf of the merchant
10	Arb/Comp Ruling in Issuer Favor	Issuer has been deemed liable for the dispute
11	Arb/Comp Ruling in Acquirer Favor	Acquirer has been deemed liable for the dispute
12	Arb/Comp Ruling Withdrawn by Issuer	Issuer has withdrawn request for case ruling and has accepted dispute liability
13	Arb/Comp Ruling Withdrawn by Acquirer	Acquirer has withdrawn request for case ruling and has accepted dispute liability on behalf of the merchant
14	GFC Accepted by Issuer	Issuer has accepted liability
15	GFC Accepted by Acquirer	Acquirer has accepted liability on behalf of the merchant

Actions

This table shows you values for the ActionStatus field. The action status inform you what you need to do next, or what was done last.

	Action	Action Description
1	Case Closed in Issuer's favor - No Further Recourse	See Custom Field for explanation
2	Case Closed in Merchant's favor - Time Elapsed	Merchant win
3	Merchant Response Needed - See Reason Code	Required Compelling Evidence can be inferred from Dispute Reason Code
4	Merchant Response Needed - See Custom Field	Specific information is required of the merchant - please see custom field
5	Outgoing Pre-Arb Sent to Issuer Pending Issuer Response	Issuer has up to 30 days to respond
6	Outgoing Pre-Comp Sent to Issuer Pending Issuer Response	Issuer has up to 30 days to respond
7	Representment Processed back to Issuer	Issuer has 30-45 days to repsonse with an incoming Pre-Arb
8	Merchant Response needed for Incoming Pre-Arb/Comp	See Custom Field for explanation
9	Reversal processed to offset most recent Process	See Chargeback Type (First Chargeback or Representment)