Payment API

Initiate payments from a payment account.

Which type of account can be used to initiate a payment within a TPP application?

All Belfius and Banx payment accounts can be used to initiate a payment. Business, Corporate and Public Segment accounts as well.

Note that to be eligible for PSD2, a payment account should be managed in one of the Belfius electronic channel (Belfius Mobile, Belfius Direct Net – Business, Belfius Web) or in the Banx Mobile application. If this is not the case, the account cannot be used to initiate a payment.

Also note that if the PSU blocked one of the digital channel abonnements, the payment initiation may not be possible for security reasons. The PSU should deblocked its digital channel to continue enabling PSD2. The PSU can contact Belfius contact center or Belfius branches to guide him/her trough the procedure

Is it required to provide an account IBAN in input for the payment initiation?

Yes, it is mandatory to provide an account IBAN as debtor_account to initiate a payment.

The PSU account is a payment account, but the payment initiation is in error?

There can be several causes of this error. Please note that each client can choose its payment security parameters for each account. Payment initiation to a non-Belgian account are not accepted by most of our clients by default.

Using version 1 of PIS API, we are getting the error 302 -signature_required. What does that mean?

The payment initiation should be signed by the PSU. To do so, the TPP should redirect the PSU to the Belfius/Banx environment using the url present in the API response to which it adds a “state”. The PSU will be able to sign its payment initiation in the Belfius/Banx secure environment.

The PSU has signed its payment initiation successfully in Belfius/Banx environment, does that means that the payment will be executed?

As in the Belfius/Banx channels, after a successful payment initiation signature, the payment is recorded and will be executed only if the balance on the PSU account is sufficient.

A successful payment initiation signature by the PSU is therefore not a guarantee that the payment will be executed.

Should we pass an access-token in the Authorization header when posting a payment initiation?

This is your choice.

  • If you are passing an access-token in the Authorization header: Belfius/Banx will not sent back an authorization code at the end of the flow. In case the PSU wants to cancel the payment initiation, you will need to use the refresh-token previously retrieved for this PSU and this scope to get a valid access-token
  • If you are not passing an access-token in the Autorization header: Belfius/Banx will sent back an authorization code at the end of a successful redirection flow. In case the PSU wants to cancel the payment initiation, you will need to use this authorization code to retrieve a valid access-token.

Previously, passing an access-token in the Authorization header enabled a “lighter” authentication flow for the PSU when being redirected in the Belfius web environment. Belfius has improved its web flows and today, passing an access-token, is not required anymore to access a flow with only one PSU’s authentication.