Home / Issuing / Generate Reports
Card Interchange Activity Report
Note: ATM and manual cash-related transactions, such as withdrawals, deposits, and balance inquiries, are excluded from this report because they are billed differently.
This report contains transaction-level card interchange and settlement activity across all financial accounts for your organization.
Data for this report is available as follows:
- Earliest available: September 1, 2023 and after
- Latest available: Five (5) days from today
| Field Name | Data type | Description |
|---|---|---|
| posted_date_time | DateTime (ISO 8601: YYYY-MM-DDTHH:MM:SSZ) | UTC timestamp when the transaction was posted to the financial account |
| 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) |
| 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 share the same transaction_id. |
| transaction_settlement_amount | Decimal | Amount of the transaction that was settled. A positive entry is a debit transaction, for example, purchases. A negative entry is a credit transaction, for example, returns. |
| transaction_settlement_amount_currency_code | String | ISO 4217 code representing the currency of the settlement amount |
| interchange_amount | Decimal | Interchange amount of the transaction: positive for income, negative for expense |
| interchange_amount_currency_code | String | ISO 4217 code representing the currency of the interchange amount |
| network_interchange_rate_code | String | Code provided by the card network that denotes the interchange category or rate applied to the transaction. Only available for VNT and MCC. |
| 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 merchant is located |