Skip to main content

Bank integration flows

While Open Banking defines a standard way to connect to a bank or financial service, it is just that: a defined standard. The APIs to connect to the bank or financial service is not standardized and can be in various shapes and forms.

While Fliqa provides a single unified API, the payment confirmation / account consent flow might differ from bank to bank, thus providing a slightly different end-user experience.

The difference is noticeable from the point where the end-user starts the payment / account consent process with the bank.

Depending on the bank selected, we distinguish between:

  • Redirect flow
  • Embedded flow
  • Decoupled flow
info

See: Sandbox banks for various flow simulations scenarios.

Redirect flow​

Redirected flow is likely the most commonly used method. It involves redirecting the end-user to a bank-specific user interface, managed by the bank and outside Fliqa's control. The end-user completes all necessary steps to confirm or deny a payment or account access within the bank's interface and is then redirected back.

Depending on the bank Fliqa might ask for the end-user account IBAN number before redirecting the user to the bank.

image

Embedded flow​

Embedded flow is not commonly used and is mostly found in smaller German banks.

In this scenario, the entire confirmation process occurs within Fliqa's system. The bank does not offer any public user-facing interface. All necessary data, such as for instance user ID, account PIN, and more, are collected through Fliqa's interface or must be provided via an API endpoint.

image

Decoupled flow​

Decoupled flow occurs when the payment or account confirmation takes place in a separate confirmation application, similar to an Authenticator app. Once the payment or account consent process begins, Fliqa waits for the end-user's confirmation.

The end-user completes the confirmation using their bank's authentication application, which is decoupled from the bank itself.

image