Card Transaction File
A list of debit card transactions which have settled for a given day, containing data specific to debit card transactions. Intended to be paired with the Posted Transaction File for a complete view of the entire transaction detail.
Card Transaction File Definition
This file is created by CorePro on a daily basis. It has the following properties:
- Fixed-length. Header row is 129 bytes excluding line endings. Each content row is 384 bytes excluding line endings.
- ANSI encoded
- Line endings are Windows-style CarriageReturn + LineFeed (
\r\n, or0x0D0A) - File will be available in the relative directory of
/PostedTransaction - File name follows a specific, case-sensitive pattern of:
yyyyMMddhhmm_DEBITCARDTRANSACTION.TXT - Root-relative path on
sftp.corepro.iofor that file would be:/PostedTransaction/201809110304_DEBITCARDTRANSACTION.TXT
Format Disclaimer
Q2 Open reserves the right to append new field(s) to the end of any Header or Content line without notice. This is to allow new data points to be added as needed in a timely fashion.
Your code should be written such that unexpected characters after the "last" field but prior to the end of each line should be ignored. That is, if the file is documented as being 872 bytes per line, receiving a file with 984 bytes per line should not disrupt your processing.
This applies to both Header and Content lines.
The date in file name should be used as a guideline for human eyes only. Any date-related programmatic dependencies should rely on the FileCreatedDate or FileEffectiveDate contained within the header line of each file, as these will be precise to the second and will be in the appropriate timezone.
Header Row
| Property | Alignment | Start Position | Description | |
|---|---|---|---|---|
RecordType |
string (1) | Left | 1 | The flag for the header row. Will always be H. |
FileName |
string (50) | Left | 2 |
The name of this request file excluding path. Will be named following this pattern:
|
RecordCount |
integer (10) | Right | 52 | The number of records represented within the file. NOTE: This field is zero-padded on the left side. e.g.: 0000000872 |
FileCreatedDate |
datetime (34) | Right | 62 |
The date the file was created. Follows same format as API e.g.: 2014-10-20T10:30:31.456-05:00. See date format details.
|
FileEffectiveDate |
datetime (34) | Right | 96 |
The date to which the data in the file pertains. Follows same format as API e.g.: 2014-10-20T23:59:59.999-05:00. See date format details.
|
Content Row
| Property | Alignment | Start Position | Description | |
|---|---|---|---|---|
TransactionId |
long integer (19) | Right | 1 | The unique identifier for a transaction. NOTE: This field is zero-padded on the left side. e.g.: 0000000000000000872 |
MasterId |
long integer (19) | Right | 20 | The unique identifier for a group of related transactions. NOTE: This field is zero-padded on the left side. e.g.: 0000000000000000872 |
CardId |
integer (10) | Right | 39 | The unique identifier for the card that the transaction occurred against. NOTE: This field is zero-padded on the left side. e.g.: 0000000872 |
PANLastFour |
string (4) | Left | 49 | The rightmost four digits of the 16-digit card number. |
CardHolderFirstName |
string (64) | Left | 53 | The first name of the card holder. |
CardHolderMiddleName |
string (64) | Left | 117 | The middle name of the card holder. |
CardHolderLastName |
string (128) | Left | 181 | The last name of the card holder. |
CardAcceptorLocation |
string (25) | Left | 309 | The location of the merchant where the transaction originated. |
CardAcceptorCity |
string (13) | Left | 334 | The city of the merchant where the transaction originated. |
CardAcceptorState |
string (2) | Left | 347 | The two character state code of the merchant where the transaction originated. |
CardAcceptorZip |
string (9) | Left | 349 | The nine digit postal code of the merchant where the transaction originated. |
RetrievalReferenceNumber |
string (12) | Left | 358 | The Retrieval Reference Number (Field #37 from the ISO-8583 specification) as defined by the network provider. Useful when interfacing with the network provider's support tools or staff. |
SystemTraceAuditNumber |
string (6) | Left | 370 | The System Trace Audit Number (Field #11 from the ISO-8583 specification) as defined by the network provider. Useful when interfacing with the network provider's support tools or staff. |
MerchantId |
string (15) | Left | 376 | The Merchant Identifier (Field #42 from the ISO-8583 specification) as defined by the network provider. Useful to help identify a specific merchant uniquely. |
SubTypeCode |
string (6) | Left | 391 |
The Merchant Category Code of the merchant where the transaction originated. Categorizes merchants with similar lines of business together. Merchant Category Codes (and the Merchant Groups to which they belong) |
MerchantGroupCode |
string (6) | Left | 397 |
The Merchant Group Code of the merchant where the transaction originated. This is a higher-level grouping construct for various Merchant Category Codes that all belong to the same "group" of businesses.Merchant Group Codes |
TerminalId |
string (15) | Left | 403 | The identifier of the terminal at the merchant where the transaction originated. |
CashbackAmount |
int (10) | Right | 418 |
The amount of cash given to the user as part of the transaction. NOTE: This field is zero-padded on the left side, and two decimals will be assumed. e.g.: 0000002000 represents an amount of $20.00. |
SurchargeAmount |
int (10) | Right | 428 |
The amount of the surcharge applied as part of the transaction. NOTE: This field is zero-padded on the left side, and two decimals will be assumed. e.g.: 0000000250 represents an amount of $2.50. |
UnverifiedDepositAmount |
int (10) | Right | 438 |
The amount of the check deposit for this transaction. NOTE: This field is zero-padded on the left side, and two decimals will be assumed. e.g.: 0000005275 represents an amount of $52.75. |
CashDepositAmount |
int (10) | Right | 448 |
The amount of cash deposited for this transaction. NOTE: This field is zero-padded on the left side, and two decimals will be assumed. e.g.: 0000010000 represents an amount of $100.00. |
Example Card Transaction File
Content: See 201809071036_DEBITCARDTRANSACTION.TXT
NOTE: Your browser or text editor may wrap the text to fit the window. Actual source file does not wrap.