7.1 “fundsConfirmation” interface

6.1 “fundsConfirmation” interface

Creates a confirmation of funds request at the ASPSP.

Input parameters

Attribute	Description
tpp-registration-number	A unique registration number for TPP identification
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) PISP (Payment Initiation Service Provider) PIISP (Payment Instrument Issuing Service Provide )
aspsp-code	The account servicing payment service provider code
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.