Card Issuing Specific File Specs
Overview
This section outlines file specifications unique to the Card Issuing Sponsorship program. It includes structured formats for Cardholder, Card, and Posted Transactions data, which are essential for supporting operational workflows that extend beyond API-based integrations.
These specifications are designed to ensure accurate data capture, regulatory compliance (e.g., KYC, AML), and seamless reconciliation across card-based financial activities. While tailored for Card Issuing, they align with the broader data standards used across the platform.
A cardholder is a legal individual or business entity authorized to hold and use a payment card. Cardholder records contain all necessary personal, business, and account-related information required for identity verification, regulatory compliance (e.g., KYC, AML), and secure transaction processing.
A card is a payment instrument issued to a cardholder under a specific account. It contains all the necessary attributes to support secure transaction processing, lifecycle management, and network compliance. Each card is uniquely identified and linked to a cardholder and account, and includes metadata such as issuance details, status, and product type.
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 account adjustments that have been authorized and officially posted to the ledger.
Transaction types define the nature and purpose of financial activities initiated using a card. Each transaction type represents a distinct classification of card-based activity—such as purchases, refunds, withdrawals, bill payments, or chargebacks—and includes a standardized set of required and optional data fields. These definitions ensure consistent data capture, processing, and reporting across all card transactions within the platform.
Related Resources
These resources provide essential guidance for implementing and maintaining your program across EDAS and Card Issuing. Refer to each for entity definitions, file formats, and operational requirements.
-
Common File Specs Defines shared data structures for accounts, businesses, and beneficial ownership. Required for BSA/AML compliance and sanctions screening.
-
Summary File Specifications Requirements This guide provides detailed information about the fields required for Card Balance File Requirements specific to Account Reconciliation.
-
Detail File Specifications Requirements This guide provides detailed information about the fields required for Card Details File Requirements specific to Account Reconciliation.
.
Updated 5 days ago