Home / Issuing / Generate Reports
Card Transaction Activity Report
This report contains all card transaction event activities across all financial accounts for the organization.
Data for this report is available as follows:
- Earliest available: 18 months from today
- Latest available: One (1) day from today
| Field Name | Data Type | Description |
|---|---|---|
| created_at | DateTime (ISO 8601: YYYY-MM-DDTHH:MM:SSZ) | UTC timestamp when the transaction was posted to the financial account; timestamped at the creation of the transaction record |
| authorization_date_time | DateTime (ISO 8601: YYYY-MM-DDTHH:MM:SSZ) | UTC timestamp when the transaction was first authorized on the financial account, if applicable |
| platform_settlement_date | Date | Date when the transaction was settled on the platform, with a cutoff of 5 PM Pacific Time (PT) |
| card_product_id | String | Unique identifier of the card product |
| card_product_name | String | Name of the card product associated with the ledger entry |
| card_profile_set_id | String | Unique identifier of the card profile for a given card product |
| network_name | String | Name of the card network provider (Visa, Mastercard) |
| classification | String | Classification of the network BIN product type (consumer, commercial, business, etc.) |
| funding_type | String | Card funding type of the network BIN product (credit, prepaid, debit) |
| account_holder_id | String | Unique identifier of the account holder |
| financial_account_id | String | Unique identifier of the financial account |
| payment_card_id | String | Unique identifier of the card |
| processing_network_code | String | Card transaction network. Possible values: VNT (Visanet), MCC (Mastercard Dual Message), MDS (Maestro Single Message), PUL (PULSE), or MPS (Moneypass) |
| financial_event_id | String | Unique identifier of the financial event |
| financial_event | String | Activity type of the financial event (e.g., AUTHORIZE, CLEAR, REVERSE, AUTHORIZE_AND_CLEAR) |
| transaction_id | String | Transaction lifecycle identifier. Example: Two transaction events (AUTH and CLEAR) make up one transaction lifecycle, so both events share the same transaction lifecycle ID. Multi-clearing transaction events with different financial_event_ids will share the same transaction_id. |
| merchant_id | String | Identifier of the merchant |
| merchant_category_code | String | 4-digit ISO 18245 code representing retail financial services. MCCs classify businesses by the type of goods or services they provide. |
| merchant_name | String | Name of the merchant where the transaction took place |
| merchant_description | String | Location of the merchant where the transaction took place |
| merchant_country | String | ISO 3166 Alpha-3 code representing the country where the card was accepted |
| response_code | Enum | Highnote response code |
| avs_response_code | Enum | Code representing the result of an address verification check |
| postal_code_response_code | Enum | Code representing the result of postal code verification check |
| cvv_response_code | Enum | Code representing the result of a card verification value (CVV) check |
| is_settlement | Boolean | Flag identifying cleared transactions to settle at the bank |
| approved_amount | Decimal | Funds approved and posted to the Highnote ledger for the transaction. Appears as responseCode in the GraphQL response |
| surcharge_fee | Decimal | Fee associated with the posted_amount for each transaction event type |
| requested_amount | Decimal | Funds requested from the network for the transaction, not including the surcharge fee |
| currency_code | String | ISO 4217 code representing the currency of the transaction |