5.2.1 "readCardAccountList" interface: Difference between revisions
No edit summary |
No edit summary |
||
Line 42: | Line 42: | ||
'''Output parameters''' | '''Output parameters''' | ||
{|class="wikitable" | {|class="wikitable" | ||
! style="text-align:left;width:30%" | Attribute | ! style="text-align:left;width:30%" | Attribute |
Revision as of 12:10, 28 February 2019
5.2.1 “readCardAccountList” interface
Reads a list of card accounts with additional information, e.g. balance information. It is assumed that a consent of the PSU to this access is already given and stored on the ASPSP system. The addressed list of card accounts depends then on the PSU ID and 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) |
tpp-registration-number | A unique registration number for TPP identification |
consent-id | The identifier of the consent resource authorizing the operation to perform. |
aspsp-code | The account servicing payment service provider code |
Output parameters
Attribute | Description |
---|---|
Result Code | Result of the read card account list. |
Error Management | Object identifying the error. |
cardAccounts | Array of card account detail objects. |