These endpoints provide the PISP possibilities for initiating payments, requesting a payment status and cancelling a payment.
You can use the production host when you want to go live:
psd2.b2b.belfius.be:8443
psd2.b2b.banx.be:8443
Click the button below to download the open API specification.
DownloadThe PISP checks the details of a payment initiation. Only the following **payment products** are allowed: - ***sepa-credit-transfers*** - ***instant-sepa-credit-transfers*** - ***cross-border-credit-transfers*** Please note that the Authorization header is mandatory & must be provided with a bearer token. Caller receives the bearer token by standard OAuth2 authorization code grant flow, calling /token API with the authorization_code received at the end of payment initation request. Please refer to documentation in the "flow" section of the portal for details.
The single payment products. The following **payment products** are supported: - sepa-credit-transfers - instant-sepa-credit-transfers - cross-border-credit-transfers
Payment reference.
example:
"1234-wertiq-983"
The access token. Note that access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Type of Payment ID. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post payment API. - EXTERNAL: Usage of the reference provided by the PISP when initiating the payment.
example:
""
{ "debtor_account": { "iban": "BE54063301200997", "currency": "EUR" }, "creditor_account": { "iban": "BE54063301200998", "bban": "123456789FW999999999", "country": "SE", "currency": "EUR", "bic": "BBVAESMM", "bank_national_id": "XXXXXXXXX" }, "instructed_amount": { "currency": "EUR", "amount": "5877.78" }, "creditor_name": "Creditor Name", "creditor_address": { "street": "string", "building_number": "string", "city": "string", "postal_code": "string", "country": "SE" }, "purpose_code": "string", "remittance_information_unstructured": "Ref Number Merchant", "remittance_information_structured": { "reference": "string", "reference_type": "string", "reference_issuer": "string" }, "charge_bearer": "string", "requested_execution_date": "2020-09-18", "endtoend_identification": "1232424kw54u1iu12o4141", "instruction_priority": "string", "psu_name": "Francois Dupont" }
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
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
{ "debtor_account": { "iban": "BE54063301200997", "currency": "EUR" }, "creditor_account": { "iban": "BE54063301200998", "bban": "123456789FW999999999", "country": "SE", "currency": "EUR", "bic": "BBVAESMM", "bank_national_id": "XXXXXXXXX" }, "instructed_amount": { "currency": "EUR", "amount": "5877.78" }, "creditor_name": "Creditor Name", "creditor_address": { "street": "string", "building_number": "string", "city": "string", "postal_code": "string", "country": "SE" }, "purpose_code": "string", "remittance_information_unstructured": "Ref Number Merchant", "remittance_information_structured": { "reference": "string", "reference_type": "string", "reference_issuer": "string" }, "charge_bearer": "string", "requested_execution_date": "2020-09-18", "endtoend_identification": "1232424kw54u1iu12o4141", "instruction_priority": "string", "psu_name": "Francois Dupont" }
{ "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" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
The PISP checks the transaction status of a payment initiation. Only the following **payment products** are allowed: - ***sepa-credit-transfers*** - ***instant-sepa-credit-transfers*** - ***cross-border-credit-transfers***
The single payment products. The following **payment products** are supported: - sepa-credit-transfers - instant-sepa-credit-transfers - cross-border-credit-transfers
Payment reference.
example:
"1234-wertiq-983"
The access token. Scope of this access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Type of Payment ID. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post payment API. - EXTERNAL: Usage of the reference provided by the PISP when initiating the payment.
example:
""
{ "transaction_status": "RCVD" }
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
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
{ "transaction_status": "RCVD" }
{ "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" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
The PISP initiates a payment at the ASPSP. Only the following **payment products** are allowed: - ***sepa-credit-transfers*** - ***instant-sepa-credit-transfers*** - ***cross-border-credit-transfers*** Please note that there's a conditional check between Authorization header and PKCE headers (Code-Challenge + Code-Challenge-Method). If Authorization header is provided, PKCE headers are not taken into account. If Authorization header is not provided, PKCE headers become mandatory. In this later case, the PKCE headers are used to prepare an OAuth2 authorization code which can then be used to request OAuth2 access token. This access token can then be passed as Bearer token in APIs which accept an Authorization header. Please note that Authorization header is mandatory for Payment details & Payment cancellation APIs. That means in order to call any of the Payment details or Payment cancellation APIs, you must obtain an access token as mentioned above. Please refer to documentation in the "flow" section of the portal for details.
The single payment products. The following **payment products** are supported: - sepa-credit-transfers - instant-sepa-credit-transfers - cross-border-credit-transfers
The access token. Scope of this access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=3].
example:
"application/vnd.belfius.api+json; version=3"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
It should be application/json.
example:
"application/json"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Redirect-URI from the PISP. URI to which Belfius/Banx will redirect the PSU after redirection in Belfius/Banx environment.
example:
"https://www.clientapp.com/someurrl"
Signature of the request created by the PISP using its QSeal certificate (draft-cavage-http-signatures-10). Please see the docs for more details.
SHA256 of the body (draft-cavage-http-signatures-10). Please see the docs for more details.
Current date in HTTP Date RFC format (https://tools.ietf.org/html/rfc7231#section-7.1.1.2). We will tolerate a drift of +-1 minutes. Please note that drift is the allowed difference between the exact time when the call was received at Belfius’ side, and the content of DATE header. If the DATE headers' time value differs by more than +-1 minute, request will be considered as Invalid.
example:
"Tue, 15 Nov 1994 08:12:31 GMT"
PKCE code-challenge-method as per RFC https://tools.ietf.org/html/rfc7636.
PKCE code-challenge as per RFC https://tools.ietf.org/html/rfc7636.
Name | Type | Description | |
---|---|---|---|
debtor_account | object | Debtor Account Information. This is no longer mandatory. If filled the given account will be used to initiate the payment. If not filled the PSU will receive an account list while redirected to Belfius/Banx environment. | optional |
iban | string | IBAN of an account. Note that the 2 letters identifying the IBAN's country should be upper case. | required |
currency | string | The currency of the account compartment the PSU wants to use. * sepa-credit-transfers : MUST be EUR. EUR is default if not provided. * instant-sepa-credit-transfers : MUST be EUR. EUR is default if not provided. * cross-border-credit-transfers : The currency of the account compartment the PSU wants to use. EUR is default if not provided. | optional |
creditor_account | object | Creditor Account Information. | required |
iban | string | IBAN of an account. Note that the 2 letters identifying the IBAN's country should be upper case. * sepa-credit-transfers : required. * instant-sepa-credit-transfers : required. * cross-border-credit-transfers : conditional. Please refer to documentation in the "flow" section of the portal for details. | optional |
bban | string | Basic Bank Account Number. * sepa-credit-transfers : n/a. * instant-sepa-credit-transfers : n/a. * cross-border-credit-transfers : conditional. Please refer to documentation in the "flow" section of the portal for details. | optional |
country | string | ISO 3166 ALPHA2 country code. | optional |
currency | string | The currency of the account compartment the PSU wants to use. * sepa-credit-transfers : MUST be EUR. EUR is default if not provided. * instant-sepa-credit-transfers : MUST be EUR. EUR is default if not provided. * cross-border-credit-transfers : The currency of the account compartment the PSU wants to use. EUR is default if not provided. | optional |
bic | string | Bank Identifier Code. * sepa-credit-transfers : optional. * instant-sepa-credit-transfers : optional. * cross-border-credit-transfers : conditional. Please refer to documentation in the "flow" section of the portal for details. | optional |
bank_national_id | string | Bank National ID. * sepa-credit-transfers : optional. * instant-sepa-credit-transfers : optional. * cross-border-credit-transfers : conditional. Please refer to documentation in the "flow" section of the portal for details. | optional |
instructed_amount | object | required | |
currency | string | Payment currency for payment initiation. * sepa-credit-transfers : MUST be EUR. EUR is default if not provided. * instant-sepa-credit-transfers : MUST be EUR. EUR is default if not provided. * cross-border-credit-transfers : required. Please refer to documentation in the "flow" section of the portal to find the currencies accepted by Belfius. | required |
amount | string | The amount given with fractional digits, where fractions must be compliant to the currency definition. The decimal separator is a dot. **Example:** Valid representations with up to two decimals are: * 1056 * 5768.2 * 5877.78 | required |
creditor_name | string | Creditor name. | required |
creditor_address | object | Creditor address. * sepa-credit-transfers : n/a. * instant-sepa-credit-transfers : n/a. * cross-border-credit-transfers : required. | conditional |
street | string | optional | |
building_number | string | optional | |
city | string | optional | |
postal_code | string | optional | |
country | string | ISO 3166 ALPHA2 country code. | required |
purpose_code | string | Reason of Payment. * sepa-credit-transfers : n/a. * instant-sepa-credit-transfers : n/a. * cross-border-credit-transfers : conditional. Please refer to documentation in the "flow" section of the portal for accepted purpose code. | conditional |
remittance_information_unstructured | string | Unstructured remittance information. * sepa-credit-transfers : optional. * instant-sepa-credit-transfers : optional. * cross-border-credit-transfers : conditional. Please refer to the ""flow"" section of the portal for countries where remittance information is required. | optional |
remittance_information_structured | object | Structured remittance information. Only Belgian structured is accepted. * sepa-credit-transfers : optional. * instant-sepa-credit-transfers : optional. * cross-border-credit-transfers : n/a. | optional |
reference | string | required | |
reference_type | string |
|
required |
reference_issuer | string |
|
required |
charge_bearer | string |
Conditional: Charge Bearer. ChargeBearerType1Code from ISO20022.
* sepa-credit-transfers : n/a.
* instant-sepa-credit-transfers : n/a.
* cross-border-credit-transfers : required.
|
conditional |
requested_execution_date | string | Payment execution date. Sender may choose a specific future date on which payment has to be executed in ISO_8601 UTC date format [YYYY-MM-DD]. Default will be today or the next open business day. * sepa-credit-transfers - optional. * instant-sepa-credit-transfers - n/a. * cross-border-credit-transfers - optional. | optional |
endtoend_identification | string | The reference provided by the PISP when initiating the payment. It has to be unique with maximum length of 35 chars. It will be returned back in the response. | required |
instruction_priority | string |
Priority of Payment. Some of these offered services are paying services for the PSU. You can consult our website to know the exact charges due.
* sepa-credit-transfers - optional.
* instant-sepa-credit-transfers - n/a.
* cross-border-credit-transfers - optional.
|
optional |
{ "transaction_status": "RCVD", "payment-id": "1234-wertiq-983", "endtoend_identification": "1234-wertiq-983", "_links": { "sca_redirect": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "status": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
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
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
{ "debtor_account": { "iban": "BE54063301200997", "currency": "EUR" }, "creditor_account": { "iban": "BE54063301200998", "bban": "123456789FW999999999", "country": "SE", "currency": "EUR", "bic": "BBVAESMM", "bank_national_id": "XXXXXXXXX" }, "instructed_amount": { "currency": "EUR", "amount": "5877.78" }, "creditor_name": "Creditor Name", "creditor_address": { "street": "string", "building_number": "string", "city": "string", "postal_code": "string", "country": "SE" }, "purpose_code": "string", "remittance_information_unstructured": "Ref Number Merchant", "remittance_information_structured": { "reference": "string", "reference_type": "string", "reference_issuer": "string" }, "charge_bearer": "string", "requested_execution_date": "2020-09-18", "endtoend_identification": "1232424kw54u1iu12o4141", "instruction_priority": "string" }
{ "transaction_status": "RCVD", "payment-id": "1234-wertiq-983", "endtoend_identification": "1234-wertiq-983", "_links": { "sca_redirect": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "status": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
{ "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" }
{ "error": "string", "error_code": "string", "error_description": "string" }
The PISP sends a cancel payment message in order to delete a payment initiation. Only payment initiation in status RCVD, PATC and PNDG (only for sepa-credit-transfers) can be cancelled. Only the following **payment products** are allowed: - ***sepa-credit-transfers*** - ***instant-sepa-credit-transfers*** Please note that the Authorization header is mandatory & must be provided with a bearer token. Caller receives the bearer token by standard OAuth2 authorization code grant flow, calling /token API with the authorization_code received at the end of a payment initation request. Please refer to documentation in the "flow" section of the portal for details.
The single payment products. The following payment products are supported: - sepa-credit-transfers - instant-sepa-credit-transfers
Payment reference.
example:
"1234-wertiq-983"
The access token. Note that access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=2].
example:
"application/vnd.belfius.api+json; version=2"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Type of Payment ID. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post payment API. - EXTERNAL: Usage of the reference provided by the PISP when initiating the payment.
example:
""
No definition found.
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
{ "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" }
The PISP checks the details of a periodic payment initiation. Only the following **payment products** are allowed: - ***sepa-credit-transfers*** Please note that the Authorization header is mandatory & must be provided with a bearer token. Caller receives the bearer token by standard OAuth2 authorization code grant flow, calling /token API with the authorization_code received at the end of a periodic-payment initiation request.
The single payment products. The following **payment products** are supported: - sepa-credit-transfers - instant-sepa-credit-transfers - cross-border-credit-transfers
Payment reference.
example:
"1234-wertiq-983"
The access token. Note that access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Type of Payment ID. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post payment API. - EXTERNAL: Usage of the reference provided by the PISP when initiating the payment.
example:
""
{ "debtor_account": { "iban": "BE54063301200997", "currency": "EUR" }, "creditor_account": { "iban": "BE54063301200998" }, "periodic_payment_type": "string", "instructed_amount": { "currency": "EUR", "amount": "5877.78", "minimal_amount": "5877.78", "maximal_amount": "5877.78" }, "creditor_name": "Creditor Name", "creditor_address": { "street": "string", "building_number": "string", "city": "string", "postal_code": "string", "country": "SE" }, "remittance_information_unstructured": "Ref Number Merchant", "remittance_information_structured": { "reference": "string", "reference_type": "string", "reference_issuer": "string" }, "endtoend_identification": "1232424kw54u1iu12o4141", "start_date": "2020-09-18", "end_date": "2020-09-18", "frequency": "string", "day_of_execution": "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
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
{ "debtor_account": { "iban": "BE54063301200997", "currency": "EUR" }, "creditor_account": { "iban": "BE54063301200998" }, "periodic_payment_type": "string", "instructed_amount": { "currency": "EUR", "amount": "5877.78", "minimal_amount": "5877.78", "maximal_amount": "5877.78" }, "creditor_name": "Creditor Name", "creditor_address": { "street": "string", "building_number": "string", "city": "string", "postal_code": "string", "country": "SE" }, "remittance_information_unstructured": "Ref Number Merchant", "remittance_information_structured": { "reference": "string", "reference_type": "string", "reference_issuer": "string" }, "endtoend_identification": "1232424kw54u1iu12o4141", "start_date": "2020-09-18", "end_date": "2020-09-18", "frequency": "string", "day_of_execution": "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" }
{ "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" }
The PISP checks the transaction status of a periodic payment initiation. Only the following **payment product** is allowed: - ***sepa-credit-transfers***
The periodic payment products. The following payment products are supported: - sepa-credit-transfers
Payment reference.
example:
"1234-wertiq-983"
The access token. Scope of this access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Type of Payment ID. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post payment API. - EXTERNAL: Usage of the reference provided by the PISP when initiating the payment.
example:
""
{ "transaction_status": "RCVD" }
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
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
{ "transaction_status": "RCVD" }
{ "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" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
The PISP initiates a periodic payment at the ASPSP. Only the following **payment product** is allowed: - ***sepa-credit-transfers*** Please note that there's a conditional check between Authorization header and PKCE headers (Code-Challenge + Code-Challenge-Method). If Authorization header is provided, PKCE headers are not taken into account. If Authorization header is not provided, PKCE headers become mandatory. In this later case, the PKCE headers are used to prepare an OAuth2 authorization code which can then be used to request OAuth2 access token. This access token can then be passed as Bearer token in APIs which accept an Authorization header. Please note that Authorization header is mandatory for Payment details & Payment cancellation APIs. That means in order to call any of the Payment details or Payment cancellation APIs, you must obtain an access token as mentioned above. Please refer to documentation in the "flow" section of the portal for details.
The periodic payment products. The following payment products are supported: - sepa-credit-transfers
The access token. Scope of this access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=2].
example:
"application/vnd.belfius.api+json; version=2"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
It should be application/json.
example:
"application/json"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Redirect-URI from the PISP. URI to which Belfius/Banx will redirect the PSU after redirection in Belfius/Banx environment.
example:
"https://www.clientapp.com/someurrl"
Signature of the request created by the PISP using its QSeal certificate (draft-cavage-http-signatures-10). Please see the docs for more details.
SHA256 of the body (draft-cavage-http-signatures-10). Please see the docs for more details.
Current date in HTTP Date RFC format (https://tools.ietf.org/html/rfc7231#section-7.1.1.2). We will tolerate a drift of +-1 minutes. Please note that drift is the allowed difference between the exact time when the call was received at Belfius’ side, and the content of DATE header. If the DATE headers' time value differs by more than +-1 minute, request will be considered as Invalid.
example:
"Tue, 15 Nov 1994 08:12:31 GMT"
PKCE code-challenge-method as per RFC https://tools.ietf.org/html/rfc7636.
PKCE code-challenge as per RFC https://tools.ietf.org/html/rfc7636.
Name | Type | Description | |
---|---|---|---|
debtor_account | object | Debtor Account Information for periodic payment initiation. | optional |
iban | string | IBAN of an account. Note that the 2 letters identifying the IBAN's country should be upper case. | required |
currency | string | The currency of the account compartment the PSU wants to use for periodic payment initiation. * sepa-credit-transfers : MUST be EUR. EUR is default if not provided. | optional |
creditor_account | object | Creditor Account Information for periodic payment initiation. Variable standing orders are only possible in favour of Belfius saving accounts. | required |
iban | string | IBAN of an account. Note that the 2 letters identifying the IBAN's country should be upper case. | required |
periodic_payment_type | string |
Periodic Payment Type. Indicates whether the amount to be transferred will be the same each execution ("FIXED") or change depending on other variables ("VARIABLE").
|
optional |
instructed_amount | object | required | |
currency | string | Payment currency for periodic payment initiation. * sepa-credit-transfers : MUST be EUR. EUR is default if not provided. | required |
amount | string | Amount to be transferred. It is mandatory when periodic_payment_type is FIXED. The amount given with fractional digits, where fractions must be compliant to the currency definition. The decimal separator is a dot. **Example:** Valid representations with up to two decimals are: * 1056 * 5768.2 * 5877.78 | optional |
minimal_amount | string | Minimum amount to keep on the orderer account. It is only applicable if periodic_payment_type is VARIABLE. If neither minimal nor maximal amount is filled in, the entire amount present on the account will be transferred in case of variable standing order. The amount given with fractional digits, where fractions must be compliant to the currency definition. The decimal separator is a dot. **Example:** Valid representations with up to two decimals are: * 1056 * 5768.2 * 5877.78 | optional |
maximal_amount | string | Maximum amount to transfer to beneficiary account. It is only applicable if periodic_payment_type is VARIABLE. If neither minimal nor maximal amount is filled in, the entire amount present on the account will be transferred in case of variable standing order. The amount given with fractional digits, where fractions must be compliant to the currency definition. The decimal separator is a dot. **Example:** Valid representations with up to two decimals are: * 1056 * 5768.2 * 5877.78 | optional |
creditor_name | string | Creditor name. | required |
creditor_address | object | Creditor address for periodic payment initiation. * sepa-credit-transfers : n/a. | conditional |
street | string | optional | |
building_number | string | optional | |
city | string | optional | |
postal_code | string | optional | |
country | string | ISO 3166 ALPHA2 country code. | required |
remittance_information_unstructured | string | Unstructured remittance information for periodic payment initiation. * sepa-credit-transfers : optional. | optional |
remittance_information_structured | object | Structured remittance information for periodic payment initiation. Only Belgian structured is accepted. * sepa-credit-transfers : optional. | optional |
reference | string | required | |
reference_type | string |
|
required |
reference_issuer | string |
|
required |
endtoend_identification | string | The reference provided by the PISP when initiating the payment. It has to be unique with maximum length of 35 chars. It will be returned back in the response. | required |
start_date | string | Start date of the standing order. Sender may choose a specific date on which the first payment of the standing order has to be executed in ISO_8601 UTC date format [YYYY-MM-DD]. This date should be in the future. Default will be the next open business day. This date will also determine the recurring execution date for all frequencies other than "WEEKLY", e.g. if "2020-09-18" if used as start date with frequency "MONTHLY" the order will be executed on the 18th of each month (if open business day). | required |
end_date | string | End date of the standing order. Sender may choose a specific date on which the last payment of the standing order has to be executed in ISO_8601 UTC date format [YYYY-MM-DD]. This date should be in the future. Please refer to documentation in the "flow" section of the portal for more information on how to correctly use the end date. | optional |
frequency | string |
Periodicity of the standing order.
|
required |
day_of_execution | string |
Day of execution of standing order. It is mandatory if frequency is WEEKLY.
|
optional |
{ "transaction_status": "RCVD", "payment-id": "1234-wertiq-983", "endtoend_identification": "1234-wertiq-983", "_links": { "sca_redirect": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "status": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
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
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
{ "debtor_account": { "iban": "BE54063301200997", "currency": "EUR" }, "creditor_account": { "iban": "BE54063301200998" }, "periodic_payment_type": "string", "instructed_amount": { "currency": "EUR", "amount": "5877.78", "minimal_amount": "5877.78", "maximal_amount": "5877.78" }, "creditor_name": "Creditor Name", "creditor_address": { "street": "string", "building_number": "string", "city": "string", "postal_code": "string", "country": "SE" }, "remittance_information_unstructured": "Ref Number Merchant", "remittance_information_structured": { "reference": "string", "reference_type": "string", "reference_issuer": "string" }, "endtoend_identification": "1232424kw54u1iu12o4141", "start_date": "2020-09-18", "end_date": "2020-09-18", "frequency": "string", "day_of_execution": "string" }
{ "transaction_status": "RCVD", "payment-id": "1234-wertiq-983", "endtoend_identification": "1234-wertiq-983", "_links": { "sca_redirect": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "status": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
{ "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" }
{ "error": "string", "error_code": "string", "error_description": "string" }
The PISP sends a cancel payment message in order to delete a periodic payment initiation. Periodic payment contracts in status RCVD, PATC, PNDG and ACWP can be cancelled. Note that ongoing payment execution will not be cancelled when cancelling the periodic payment contract. Please note that the Authorization header is mandatory & must be provided with a bearer token. Caller receives the bearer token by standard OAuth2 authorization code grant flow, calling /token API with the authorization_code received at the end of a periodic-payment initiation request.
The periodic payment products. The following payment products are supported: - sepa-credit-transfers
Payment reference.
example:
"1234-wertiq-983"
The access token. Note that access-token is limited to a given type of request [here PIS]. The token itself should be passed as bearer token in Authorization header, like: "Bearer 987tghjkiu6trfghjuytrghj".
example:
"Bearer 987tghjkiu6trfghjuytrghj"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Type of Payment ID. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post payment API. - EXTERNAL: Usage of the reference provided by the PISP when initiating the payment.
example:
""
No definition found.
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
{ "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" }
The PISP checks transaction status of a bulk payment initiation. Only the following **bulk payment products** are allowed : - ***pain.001*** - ***csv***
The bulk payment products The following payment products are supported: - "pain.001" - "csv"
Payment file reference provided by Belfius.
example:
"1234-wertiq-983"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Redirect-URI from the PISP. URI to which Belfius/Banx will redirect the PSU after redirection in Belfius/Banx environment.
example:
"https://www.clientapp.com/someurrl"
Type of Payment file reference. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post bulk payment API. - EXTERNAL: Usage of the external transaction reference provided by the PISP when initiating the bulk payment.
example:
""
{ "payment_file_status": "RCVD", "bulk_payment_list": "[]", "_links": { "payment_file_sca": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "payment_file_cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
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
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
{ "payment_file_status": "RCVD", "bulk_payment_list": "[]", "_links": { "payment_file_sca": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "payment_file_cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
{ "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" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
{ "error": "string", "error_code": "string", "error_description": "string" }
The PISP initiates a bulk payment at the ASPSP. Only the following **bulk payment products** are allowed : - ***pain.001*** - ***csv***
The bulk payment products The following payment products are supported: - "pain.001" - "csv"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
It should be application/xml (for XML based payload) or text/csv (for CSV based payload).
example:
"application/xml"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Redirect-URI from the PISP. URI to which Belfius/Banx will redirect the PSU after redirection in Belfius/Banx environment.
example:
"https://www.clientapp.com/someurrl"
Signature of the request created by the PISP using its QSeal certificate (draft-cavage-http-signatures-10). Please see the docs for more details.
SHA256 of the body (draft-cavage-http-signatures-10). Please see the docs for more details.
Current date in HTTP Date RFC format (https://tools.ietf.org/html/rfc7231#section-7.1.1.2). We will tolerate a drift of +-1 minutes. Please note that drift is the allowed difference between the exact time when the call was received at Belfius’ side, and the content of DATE header. If the DATE headers' time value differs by more than +-1 minute, request will be considered as Invalid.
example:
"Tue, 15 Nov 1994 08:12:31 GMT"
The reference provided by the PISP when initiating the bulk payment. It has to be unique with maximum length of 35 chars. It will be returned back in the response.
example:
"12345-id"
Name | Type | Description |
---|
{ "payment_file_status": "RCVD", "payment_file_id": "1234-wertiq-983", "payment_information_id": "1234-wertiq-983", "_links": { "payment_file_status": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "payment_file_cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
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
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
MIPI-123456789RI-123456789 2017-02-14T20:23:34.000Z 1 123 PaymentInitiator DE10000000012 PISP BIPI-123456789RI-123456789 TRF 1 123 SEPA 2017-02-15 PSU Name DE87200500001234567890 SLEV RI-123456789 123 Merchant123 DE23100120020123456789 Ref Number Merchant-123456
{ "payment_file_status": "RCVD", "payment_file_id": "1234-wertiq-983", "payment_information_id": "1234-wertiq-983", "_links": { "payment_file_status": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" }, "payment_file_cancel": { "href": "/payments/sepa-credit-transfers/1234-wertiq-983" } } }
{ "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" }
{ "error": "string", "error_code": "string", "error_description": "string" }
The PISP sends a cancel payment message in order to delete a bulk payment initiation. Only payment initiation in status RCVD, PATC and PNDG can be cancelled. Only the following **bulk payment products** are allowed : - ***pain.001*** - ***csv***
The bulk payment products The following payment products are supported: - "pain.001" - "csv"
Payment file reference provided by Belfius.
example:
"1234-wertiq-983"
ID of the request. Must be unique. It has to be a valid UUID in V04 format.
example:
"99391c7e-ad88-49ec-a2ad-99ddcb1f7721"
It must be of type application/json including the API version number. [Accept:application/vnd.belfius.api+json; version=1].
example:
"application/vnd.belfius.api+json; version=1"
Language. It can include language in ISO 639-1 format [example: fr]. Note that during redirection, Belfius screens are only available in French (fr) and Dutch (nl).
example:
"fr"
Client ID of registered PISP received after the onboarding.
example:
"l7957ffbdbcbf4496a8a406702aacbf539"
Type of Payment file reference. Following Types are supported: - INTERNAL: Usage of the reference provided by Belfius in the response of the post bulk payment API. - EXTERNAL: Usage of the external transaction reference provided by the PISP when initiating the bulk payment.
example:
""
No definition found.
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
{ "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" }