Daily settlement (detailed)

daily pre settlement reports help you match payments with the batches of transactions they relate to the detailed daily settlement report provides a breakdown of all the individual transactions occurring during a date range that you specify 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 sftp docid\ s9kgwknc0xzfugkme2lws 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 detailed daily settlement reports have 2 structures basic and expanded the basic report filename uses this convention partnername crb settlement details yyyy mm dd the expanded report filename uses this convention partnername crb settlement expandeddetails yyyy mm dd basic report structure this table presents the basic report structure no field default description 1 transactionrequestid ✓ id of the automatically created transaction associated with this settlement day 2 network ✓ card network the transaction was processed through 3 responsecode ✓ 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 4 responsedescription ✓ 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 5 transactionrequestedat ✓ time at which the transaction was requested by the partner dates in utc 6 actualtransactionat ✓ time at which the transaction was processed by the network dates in utc 7 creditcardid ✓ token for the signed up card the partner gets this upon the first card sign up, per each cardholder 8 retrieval reference number ✓ the transaction identifier vs all parties, including the card networks with the rrn, the partner can reach out directly to the network to get more info about the transaction 9 tracenumber ✓ crb reference number it is a unique number created in card transactions 10 statementdescriptor ✓ an arbitrary string attached to the transaction often useful for displaying to users 11 destination ✓ for purchases aft settlement for disbursements oct network 12 transaction amount ✓ transaction amount passed in to create transactions apis push transactions ( ) debit the account pull transactions (+) credit the account 13 interchangefee ✓ the fee paid to the issuer for each payment made with the card network every time a transaction is made via a card network (for example, visa or mastercard), the acquirer https //www adyen com/knowledge hub/acquiring bank pays the cardholder’s bank an interchange fee the merchants then pays the interchange fee back to the acquirer 14 interchangefeeindicator ✓ d debit c credit 15 interchangecategorydescriptor ✓ interchange fee rate description (defined by the card networks) 16 estimatednetworkfee ✓ the fee paid to the card scheme for using their network the fee is an accumulation of a set of charges based on the specific ac 17 networkfeecode ✓ visa network fees 18 integritynetworkfee the transaction integrity fee (tif) is assessed on debit and prepaid card transactions that do not qualify for custom payment service (cps) the most common transaction to incur the transaction integrity fee will be keyed in debit card transactions that are processed without address verification information (avs) 19 settlementdate ✓ crb settlement date 20 cutoffdate ✓ the network cutoff date, according to each network 21 transactiontype ✓ pull transfers funds from a funding account push transfers funds to a receiving account reversal dispute expanded report structure this table presents the expanded report structure no field default description 1 transactionrequestid ✓ id of the automatically created transaction associated with this settlement day 2 network ✓ card network the transaction was processed through 3 responsecode ✓ 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 4 responsedescription ✓ 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 5 transactionrequestedat ✓ time at which the transaction was requested by the partner dates in utc 6 actualtransactionat ✓ time at which the transaction was processed by the network dates in utc 7 creditcardid ✓ token for the signed up card the partner gets this upon the first card sign up, per each cardholder 8 retrievalreferencenumber ✓ the transaction identifier vs all parties, including the card networks with the rrn, the partner can reach out directly to the network to get more info about the transaction 9 tracenumber ✓ crb reference number it is a unique number created in card transactions 10 statementdescriptor ✓ an arbitrary string attached to the transaction often useful for displaying to users 11 transactiontype ✓ pull transaction to transfer funds from a funding account push payment transaction to transfer funds to a receiving account reversal dispute 12 destination ✓ 13 transaction amount ✓ transaction amount passed in to create transactions apis push transactions ( ) debit the account pull transactions (+) credit the account 14 transactioncurrency ✓ the beneficiary currency 15 interchangefee ✓ the fee paid to the issuer for each payment made with the card network every time a transaction is made via a card network (for example visa ormastercard), the acquirer pays the cardholder’s bank an interchange fee the merchants then pays the interchange fee back to the acquirer 16 interchangefeeindicator ✓ d debit c credit 17 interchangecategorydescriptor ✓ interchange fee rate description (defined by the card networks) 18 estimatednetworkfee ✓ the fee paid to the card scheme for using their network the fee is an accumulation of a set of charges based on the specific ac 19 networkfeecode ✓ visa network fees 20 integritynetworkfee the transaction integrity fee (tif) will be assessed on debit and prepaid card transactions that do not qualify for custom payment service (cps) the most common transaction to incur the transaction integrity fee will be keyed in debit card transactions that are processed without address verification information (avs) 21 settlementdate ✓ crb settlement date 22 cutoffdate ✓ the network cutoff date, according to each network 23 cardbrand ✓ the brand of the card used in the transaction 24 cardproducttype ✓ the type of card used in the transaction unknown credit debit prepaid combo charge card deferred debit 25 firstname the cardholder's first name 26 lastname the cardholder's last name 27 first6 the first 6 digits of the card used in the transaction (same as bin) 25 last4 the last 4 digits of the card used in the transaction 26 issuercountrycode the country of the card’s issuer related topics daily settlement (summary) docid\ dq2yyaaxm4ftwjmrjlstd daily exceptions docid\ vo1s3lksbwaa7cqpsqios daily chargeback report docid\ plyd5ihqt razdstrin08 transaction management docid\ wboa2sa1cfmr2woynicv8 transaction management docid\ wboa2sa1cfmr2woynicv8