5.2.2 "readCardAccountDetails" interface
5.2.2 “readCardAccountDetails” interface
Reads details about a card account. It is assumed that a consent of the PSU to this access is already given and stored on the ASPSP system. The addressed details of this account depends then on the stored consent addressed by consentId. 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. |
| tpp-role | The third party payment service provider can have one or more of the following roles:
AISP (Account Information Service Provider) |
| aspsp-code | The account servicing payment service provider code |
| consent-id | The identifier of the consent resource authorizing the operation to perform. |
| tpp-registration-number | A unique registration number for TPP identification |
| 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 details |
| Error Management | Object identifying the error |
| cardAccounts | Card account detail objects. |
