5.2.4 "readCardAccountTransactionList" interface

Reads account data from a given card account addressed by account-id. This account-id can be a tokenised identification due to data protection reason since the path information might be logged on intermediary servers within the ASPSP sphere.

Input parameters

Attribute	Description
tpp-signature-certificate	This is a X509 certificate that the TPP uses for signing the request, in base64 encoding. This certificate is in PEM format without the "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----". Must be contained if a signature is contained, see above.
signature	A signature of the request by the TPP on application level. This might be mandated by ASPSP.
digest	Is contained if and only if the “Signature” element is contained in the header of the request. The “digest” Header contains a Hash of the message body. The only hash algorithms that may be used to calculate the digest within the context of this specification are SHA-256 and SHA-512.
consent-id	The identifier of the consent resource authorizing the operation to perform.
account-id	This identification is denoting the addressed account. The account-id is the UUID related to the account structure. Its value is constant at least throughout the lifecycle of a given consent.

Output parameters

Attribute	Description
Result Code	Result of the read card account transaction list.
Error Management	Object identifying the error
account	Payment account details.
balances	The list of balances amount details.
transactions	The transactions of the addressed accounts or all of the accessible accounts. This may be restricted in a PSU/ASPSP authorization dialogue.

---

<< 5.2.3 "readCardAccountBalance" interface

5. Informative flow >>