5.1.5 "readAccountTransactionDetails" interface: Difference between revisions

Latest revision as of 16:56, 14 March 2019

Reads transaction details from a given transaction addressed by “resourceId” on a given account addressed by "account-id".

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.
resource-id	This identification is given by the attribute resourceId of the corresponding entry of a transaction list.

Output parameters

Attribute	Description
Result Code	Result of the read account transaction details.
Error Management	Object identifying the error.
transactionDetails	The details of the addressed transaction.

@@ Line 1: / Line 1: @@
-.1.5 ““readAccountTransactionDetails”” interface
 Reads transaction details from a given transaction addressed by “resourceId” on a given account addressed
@@ Line 21: / Line 20: @@
 |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)<br>
--PISP (Payment Initiation Service Provider)<br>
--PIISP (Payment Instrument Issuing 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'''
@@ Line 58: / Line 45: @@
 |The details of the addressed transaction.
 |}
+----
+<div class="prevpage">
+[[5.1.4 "readAccountTransactionList" interface|<< 5.1.4 "readAccountTransactionList" interface]]
+</div><div class="nextpage">
+[[5.1.6 "establishConsent" interface|5.1.6 "establishConsent" interface >>]]
+</div>