7.1 “fundsConfirmation” interface: Difference between revisions
From CBI GLOBE Wiki
(Creata pagina con "6.1 “fundsConfirmation” interface Creates a confirmation of funds request at the ASPSP.") |
No edit summary |
||
(6 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Creates a confirmation of funds request at the ASPSP. | Creates a confirmation of funds request at the ASPSP. | ||
'''Input parameters''' | |||
{|class="wikitable" | |||
! style="text-align:left;width:30%" | Attribute | |||
! style="text-align:left;" | 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. | |||
|- | |||
|'''account''' | |||
|The account identification which can be used on payload-level to address specific accounts. | |||
|- | |||
|'''cardNumber''' | |||
|Card Number of the card issued by the PIISP. Should be delivered if available. | |||
|- | |||
|'''payee''' | |||
|The merchant where the card is accepted as an information to the PSU. | |||
|- | |||
|'''instructedAmount''' | |||
|Transaction amount to be checked within the funds check mechanism. | |||
|} | |||
'''Output parameters''' | |||
{|class="wikitable" | |||
! style="text-align:left;width:30%" | Attribute | |||
! style="text-align:left;" | 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. | |||
|- | |||
|'''fundsAvailable''' | |||
|Indicates if sufficient funds are available at the time of the request. | |||
|} | |||
---- | |||
<div class="prevpage"> | |||
[[7. “Funds verification” flow|<< 7. “Funds verification” flow]] | |||
</div> |
Latest revision as of 15:22, 17 April 2019
Creates a confirmation of funds request at the ASPSP.
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. |
account | The account identification which can be used on payload-level to address specific accounts. |
cardNumber | Card Number of the card issued by the PIISP. Should be delivered if available. |
payee | The merchant where the card is accepted as an information to the PSU. |
instructedAmount | Transaction amount to be checked within the funds check mechanism. |
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. |
fundsAvailable | Indicates if sufficient funds are available at the time of the request. |