Posted Transactions
Overview
A posted transaction represents a finalized financial activity that has been processed and recorded on a cardholder’s account. These transactions reflect completed purchases, withdrawals, fees, or adjustments that have been authorized and officially posted to the ledger.
This section defines the required fields and data specifications for posted transaction records. Each transaction is uniquely identified and includes metadata necessary for financial reconciliation, reporting, and compliance monitoring.
Posted transaction data includes:
- Unique identifiers for the transaction, card, account, and cardholder
- Transaction timestamps, codes, descriptions, and monetary amounts
- Merchant details including name, location, and terminal information
- Currency, country, and device-level metadata
- Balance impact indicators and authorization references
These fields ensure that each transaction is accurately captured, categorized, and auditable, supporting secure financial operations and regulatory compliance across Newline’s card programs.
Posted Transaction Fields
Field | Required | Description | Character Length | Example |
---|---|---|---|---|
TRANSACTION ID | Yes | Unique identifier of the card transaction. | 20 | TXN1234567890 |
CARD NUMBER | Yes | Full 16-digit card number. | 16 | |
ACCOUNT NUMBER | Yes | Cardholder's account number. | 35 | 123456789012345 |
CARDHOLDERID | Yes | Unique identifier for the cardholder holding the card. | 35 | CUST123456 |
TRANSACTION DATE TIME STAMP | Yes | Date and time when the transaction occurred (local to the merchant for swiped payments, or web/non-swiped purchase timestamp). | DateTime | |
POSTED TRANSACTION DATE TIMESTAMP | No | Date and time when the transaction was posted to the account. | DateTime | |
TRANSACTION CODE | Yes | Code represents the transaction type posted, including internal and network-related activity. | 50 | ATM Withdrawal Fee |
TRANSACTION DESCRIPTION | No | Description of the transaction. | 100 | |
TRANSACTION AMOUNT SIGN | Yes | "+" if the transaction adds to the balance, "-" if it deducts, or " " if it doesn't affect the balance. | 1 | - |
TRANSACTION AMOUNT | Yes | The amount of the transaction posted to the account. | Decimal (10, 2) | 150.75 |
AUTHORIZATION CODE | No | The identification number is assigned to the approved transaction, or it is blank if declined. | 15 | 123456 |
TRANSACTION CURRENCY CODE | Yes | Currency code for the transaction (e.g., USD). | 3 | USD |
TRANSACTION ORIGINATED CITY | No | The city where the transaction originated. | 50 | Chicago |
TRANSACTION ORIGINATED COUNTRY CODE | Yes | Country where the transaction took place (use ISO 3166-1 Alpha-2 country code). | 2 | US |
TRANSACTION IP ADDRESS | No | The IP address from which the transaction took place. | 39 | |
TRANSACTION DEVICE ID | No | Unique number related to the device or mobile phone from which the transaction occurred. | 50 | |
MERCHANT TERMINAL NUMBER (TID) | Yes | An 8-digit alphanumeric code identifying the point-of-sale (POS) terminal where the transaction occurred. | 8 | |
MERCHANT CATEGORY CODE | Yes | Code representing the merchant's line of business. | 4 | |
MERCHANT NAME | Yes | Name of the merchant accepting the transaction. | 100 | ABC Store |
MERCHANT ACCOUNT NUMBER | Yes | Number identifying the merchant submitting the transaction. | 35 | MER1234567890 |
MERCHANT ADDRESS LINE 1 | Yes | The primary address of the merchant. | 35 | 456 Elm St |
MERCHANT ADDRESS LINE 2 | No | Additional address information for the merchant. | 35 | Suite 300 |
MERCHANT CITY | Yes | The city where the merchant is located. | 50 | San Francisco |
MERCHANT STATE | Yes | State where the merchant is located (for U.S. merchants). | 2 | CA |
MERCHANT ZIPCODE | Yes | ZIP code of the merchant. | 10 | 94107 |
MERCHANT COUNTRY CODE | Yes | Country code where the merchant is located (use ISO 3166-1 Alpha-2 code). | 2 | US |
MERCHANT PRIMARY PHONE NUMBER | Yes | Primary phone number of the merchant. | 15 | 1-415-555-1234 |
Updated 6 days ago