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) set up 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 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 no field required default description 1 crbchargebackid ✓ unique reference number generated by cross river for each chargeback case, used as the name of the evidence artifact 2 externalvendorid ✓ 3 daily chargeback report /#chargeback state types ✓ 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 daily chargeback report /#resolution types 10 adjustmenttype → when is populated recon should consume financial record debit\credit 11 adjustmentamount → when is populated recon should consume financial record adjustmentamount >2000 chargebackamount >5000 transactionamount >7000 12 daily chargeback report /#actions 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 originaltranscationtype ✓ pull push reversal dispute 27 firstname 28 lastname 29 cardbrand 30 cardproducttype 31 first6 32 last4 33 evidenceinstructions 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 no 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 no 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 no 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) related topics daily settlement (detailed) daily settlement (summary) daily exceptions send funds request funds