Card API Level 2
The term “cards” refers to both physical and virtual credit or debit cards issued by banks or financial institutions.
Physical cards are the traditional plastic cards that holders carry with them.
Virtual cards, on the other hand, only exist in digital form and are often used for online payments. These virtual cards have a card number, expiration date and security code like physical cards.
The term “card tokens” refers to the DPAN (Digital Primary Account Number) of a credit or debit card that is stored in digital wallets, wearables or with merchants (e.g. for click-to-pay). The “card token” serves as a replacement for the PAN and is used for transactions instead of the real card number. This reduces the risk of data misuse or fraud, as the sensitive card data is not transmitted directly.
The term “transactions” refers to payments made with physical or virtual cards or with card tokens. These transactions are displayed on the cardholder's account and include all authorized and recorded payments entered by the cardholder.
Transactions can include various types of payments, such as retail purchases, online payments, transfers between accounts, etc.
Each transaction undergoes authorization and clearing, meaning it has been approved by the cardholder and the payment amount has been debited from the cardholder's account.
At present, only financially relevant transactions are within scope. Declined authorizations and non-financial authorizations may be included at a later stage if the need arises.
The term “card-accounts” refers to the account on which card-related transactions are recorded, settled and managed. Depending on the card product, this can be a debit or credit account used for billing, balance management and repayment.
A “card-account” provides the financial context for one or more cards and serves as the basis for statements, balances and other account-related information.
The term “person” refers to a natural person associated with the card product ecosystem, such as a cardholder, account holder, joint holder or other entitled party. This resource contains the personal master data required to identify and manage that person in relation to cards, card-accounts and contracts.
A single person may be linked to multiple cards, accounts or contractual relationships.
The term “statements” refers to periodic account statements generated for a card-account. These statements summarize financially relevant information for a defined billing period, such as transactions, fees, interest, repayments and balances.
Statements can be provided in electronic or other formats and may only exist where the corresponding card product supports statement generation.
The term “card-contracts” refers to the contractual agreements governing the issuance and use of cards and their related card-accounts. A “card-contract” defines the legal and commercial framework of the product relationship, for example the applicable terms, fees, limits, liability rules and product conditions.
Depending on the setup, one contract can be associated with multiple card-accounts and card-accountbundles, but only one person.
The term “card-accountbundles” refers to logical groupings of card-accounts that belong together from a product, contractual or operational perspective.
This resource can be used to represent bundled account structures, for example where several card-accounts are managed as part of the same product offering or package.
If supported by the data provider, “card-accountbundles” may also be used to model hierarchical bundle structures.
| Identifier | Description |
|---|---|
| PFM/BFM | Everything from level 1, plus consideration of account-based transactions. |
| Card overview | Everything from level 1, plus more extensive information on card account data. |
| Expense Management | Share data with expense management providers including structuring options, i.e. end customers can map internal structures (organizational units) and contracts, for example. |
none so far