This document defines the Banking CSV format for integrating ATM / teller transaction data into Solink. Data is delivered with CSV files.
File Details
When sending data for this Solink integration, please ensure you follow the file naming conventions outlined below:
File Naming Format
File Name breakdown | Details |
|
|
|
|
File Part details
File name part | Additional details |
<datestamp> | Required unique date stamp without separators
|
<locationid> | Optional Unique identifier representing the physical location of your store.
|
Samples
Refer to the samples below for information on formatting CSV if you need to log banking transactions:
Examples of data files from the retail industry:
Banking Sample (TBD)
File Content Formatting
Refer to the table below for information on formatting your CSV file for the banking industry standard integration.
Column Name | Required | Data Type | Examples | Purpose |
dataType | ✱ Required | Picklist | 'teller' 'atm'
| Indicates the data type. Any value containing "teller" (case-insensitive) is treated as a teller transaction. Any value containing "atm" (case-insensitive) is treated as an ATM transaction. |
branchID | ✱ Required | String | '1001'
'BR1001'
| Branch unique ID. Maps to locationId internally. |
terminalId | ✱ Required | String | '1002'
'TS1002'
| Teller station or ATM terminal unique ID. Maps to dataSourceId internally. |
sequenceNumber | ✱ Required | String | '10004'
'SQ1004'
| Record unique ID. |
transactionType | ✱ Required | String | 'Deposit'
'Withdrawal'
'Inquiry'
'Check Deposit'
'Cash Back'
'Transfer'
| Text description of the action taken by the teller or the customer at the ATM. |
transactionDate | ✱ Required | Date/Time | YYYY-MM-DDTHH:MM:SS.sss±HH:MM
"2024-06-15T06:15:00.000-06:00"
YYYY-MM-DDTHH:MM:SS.sssZ
"2024-06-15T06:15:00.000Z"
| Date/Time the transaction occurred. ISO-8601 datetime string. T is required to separate date and time. ±HH:MM represents timezone offset; Z indicates UTC. Used as both start and end time unless startTime/endTime are provided. |
transactionAmount | ✱ Required | Number | 23.5
11.95
| Transaction amount. Must be a plain numeric value — no currency symbols or commas. |
transactionStatus | Optional | Picklist | 'Success'
'Fail'
| Status of the transaction.
• Values containing "pass" or "success" (case-insensitive) → success
• Values containing "fail" (case-insensitive) → fail
• All other values → unable to process
|
employeeId | Optional | String | '1003'
'EMP1003'
| Employee unique ID. |
employeeName | Optional | String | 'John Smith'
'Jane S.'
| The employee name. |
accountNumberLast4 | Optional | String | '0552'
'2203'
| Last four digits of the customer account number. |
cardNumberLast4 | Optional | String | '0552'
'2203'
| Last four digits of the ATM card number. |
fromAccountLast4 | Optional | String | '0552'
'2203'
| Last four digits of the source account number (e.g., for transfers). |
toAccountLast4 | Optional | String | '0552'
'2203'
| Last four digits of the destination account number (e.g., for transfers). |
transactionTypeCode | Optional | String | 'WD'
'DEP'
'TR'
| Optional transaction type code. |
transactionStatusCode | Optional | String | 'SUCCESS'
'FAIL'
| Optional transaction status code. |
notes | Optional | String | 'Customer requested receipt' | Optional free-text notes associated with the transaction. |
startTime | Optional | Date/Time | "2024-06-15T06:15:00.000-06:00"
"2024-06-15T06:15:00.000Z"
| Optional override for transaction start time. If omitted, transactionDate is used. Same ISO-8601 format as transactionDate. |
endTime | Optional | Date/Time | "2024-06-15T06:15:00.000-06:00"
"2024-06-15T06:15:00.000Z"
| Optional override for transaction end time. If omitted, transactionDate is used. Same ISO-8601 format as transactionDate. |
Picklist Values
Below are the Picklist Values.
Result Field
Value | Description |
Success | The access attempt or operation completed successfully. |
Failure | The operation did not succeed. |