5.1.9 "getConsent" interface: Difference between revisions
From CBI GLOBE Wiki
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Returns the content of an account information consent object. | Returns the content of an account information consent object. | ||
| Line 11: | Line 10: | ||
|'''consent-id''' | |'''consent-id''' | ||
|The consent identification assigned to the created resource. | |The consent identification assigned to the created resource. | ||
|- | |- | ||
|'''tpp-signature-certificate''' | |'''tpp-signature-certificate''' | ||
| Line 27: | Line 23: | ||
request. | 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. | 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. | ||
|} | |} | ||
| Line 76: | Line 63: | ||
|Status information of the SCA in Decoupled or Redirect SCA Approach. | |Status information of the SCA in Decoupled or Redirect SCA Approach. | ||
|} | |} | ||
---- | |||
<div class="prevpage"> | |||
[[5.1.8 "getConsentStatus" interface|<< 5.1.8 "getConsentStatus" interface]] | |||
</div><div class="nextpage"> | |||
[[5.1.10 "deleteConsent interface|5.1.10 "deleteConsent interface >>]] | |||
</div> | |||
Latest revision as of 16:58, 14 March 2019
Returns the content of an account information consent object.
Input parameters
| Attribute | Description |
|---|---|
| consent-id | The consent identification assigned to the created resource. |
| 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. |
Output parameters
| Attribute | Description |
|---|---|
| Result Code | Result of the get consent. |
| Error Management | Description of the type of error obtained in the event that the outcome is negative. |
| access | Requested access services. |
| recurringIndicator | Indicates if the consent is for recurring access to the account data or if the consent is for one access to the account data. |
| validUntil | This parameter is requesting a valid until date for the requested consent. |
| frequencyPerDay | This field indicates the requested maximum frequency for an access per day. |
| consentStatus | Possible output values:
- received |
| scaStatus | Status information of the SCA in Decoupled or Redirect SCA Approach. |
