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 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 [email protected] if you have any issues accessing your reports.
Recipients include user-partners only.
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
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:
|
12 | Transaction Amount | ✓ | Transaction Amount. Passed in to Create Transactions APIs:
|
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 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 | ✓ |
|
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 | ✓ |
|
12 | Destination | ✓ | |
13 | Transaction Amount | ✓ | Transaction Amount. Passed in to Create Transactions APIs:
|
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:
|
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 |
