This endpoint provide the possibility for a TPP to check if enough funds are available at a given IBAN.
You can use the production host when you want to go live:
Click the button below to download the open API specification.
DownloadChecks whether a specific amount is available at point of time of the request on an account addressed by IBAN and TPP respectively.
Amount which has to be queried. It must be a positive number >0. For decimal seperator, only '.' is allowed. It is currency-independent. Thousands seperators are not supported. Precision is available upto 2 decimal.
Currency of the amount which has to be queried. ISO 4217 3-letter alphabatic Currency-codes.
Encrypted Logical ID of the account which is mapped to IBAN.
Access token to be passed as a header. Scope of this access-token is limited to CAF and given IBAN. Token itself should be passed as bearer token in Authorization header like:"Bearer 987tghjkiu6trfghjuytrghj".
Request id to be passed as custom header. It will be used as sort of correlation id for logging and tracting purposes.
It must be of type application/json including version number.[Accept:application/vnd.belfius.api+json; version=1].
Accept-Language header field sent by the Client terminal. It can include language in ISO 639-1 format [example-:fr]. If no Accept-Language header is present or if it is present with a language which is not at all known to server, HTTP 406[Not Accepted] will be returned.
example:
"fr"
Client ID of registered TPP.
Redirect-URI of the client.
{ "funds_available": "True" }
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
example:
{ "error": "string", "error_code": "string", "error_description": "string" }
Fixed-form error tokens mapping to specific errors.
example:
string
Error specific code, could be used directly by consumer's software.
example:
string
Full description of the error.
example:
string
{ "funds_available": "True" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }