Daily exceptions

the daily exceptions report lists the transactions that contain irregularities this report includes unprocessed, incomplete, interrupted, or suspicious transactions it also contains transactions with unusual balances in addition, this report could hold mismatches or conflicts between data in the cross river and the card networks these could be, for example, transaction status, amounts, and so forth unlike the daily settlement report, where you trigger each transaction, exceptions are triggered by another person, event or action, and are unexpected cross river generates a daily exception report every day that we settle transactions with merchant partners 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 detailed daily exception reports have 2 structures basic and expanded the basic report filename uses this convention partnername crbpayments exceptions itemized yyyy mm dd the expanded report filename uses this convention partnername crb settlement exceptions expanded yyyy mm dd basic report structure no field default description 1 exceptionid ✓ 2 exceptioncode ✓ 3 originaltransactionrequestid ✓ id of the automatically created transaction associated with this settlement day 4 network ✓ 5 responsecode ✓ 6 transactiontype ✓ pull push chargeback reversal adjustment 7 responsedescription ✓ 8 transactionrequestedat ✓ 9 originaltransactionrequestedat ✓ 10 creditcardid ✓ 11 retrievalreference ✓ 12 tracenumber ✓ 13 destination ✓ for aft settlement for oct network 14 transactionamount ✓ 15 transactionindicator ✓ 16 originalcurrency ✓ 17 interchangefee ✓ 18 interchangefeeindicator ✓ 19 interchangecategorydescriptor ✓ 20 estimatednetworkfee ✓ 21 integritynetworkfee ✓ 22 integritynetworkfee ✓ 23 settlementdate ✓ 24 cutoffdate ✓ expanded report structure no field default description 1 exceptionid ✓ 2 exceptioncode ✓ 3 originaltransactionrequestid ✓ id of the automatically created transaction associated with this settlement day 4 network ✓ 5 responsecode ✓ 6 transactiontype ✓ pull push chargeback reversal adjustment 7 responsedescription ✓ 8 transactionrequestedat ✓ 9 originaltransactionrequestedat ✓ 10 creditcardid ✓ 11 retrievalreference ✓ 12 tracenumber ✓ 13 destination ✓ for aft settlement for oct network 14 transactionamount ✓ transaction amount 15 transactionindicator ✓ d debit the merchant c credit the merchant 16 originalcurrency ✓ 17 interchangefee ✓ 18 interchangefeeindicator ✓ 19 interchangecategorydescriptor ✓ 20 estimatednetworkfee ✓ 21 integritynetworkfee ✓ 22 integritynetworkfee ✓ 23 settlementdate ✓ crb settlement date 24 cutoffdate ✓ 25 cardholderfirstname ✓ cardholder first name 26 cardholderlastname ✓ cardholder last name 27 issuercountrycode ✓ card issuer country code 28 systemtraceauditnumber ✓ a unique cross river reference number created in card transactions 29 retrievalreference ✓ the transaction identifier vs all parties, including the card networks using this number, the partner can directly reach out to the network to get more info about the transaction 30 statementdescriptor an arbitrary string attached to the transaction, often useful for displaying to information users 31 cardtype ✓ debit/credit/prepaid 32 credit card id ✓ token for the signed up card the partner gets this id upon first time card sign up, per each card holder 33 first6 ✓ first 6 digits of the payment card 34 last4 ✓ last 4 digits of the payment card related topics daily settlement (detailed) daily settlement (summary) daily chargeback report send funds request funds