Introduction to Payments


The Payment Initiation product enables you to seamlessly integrate real-time access to an end user's bank account, facilitating rapid, secure payment initiations, and effectively eliminating traditional challenges.

Present your users with an effortless method to initiate a bank transfer, specifically Single Euro Payments Area (SEPA) Credit Transfers within the EU. This provides a stellar alternative to conventional online payments through credit or debit cards. Our Payment Initiation product comes with two primary capabilities tailored for varied use cases:

  1. One-time Payments: A single access payment model where the user's payment account is reached through the PSD2 API, with each transfer contingent on the end user's explicit consent and authentication.
  2. Ongoing Payments: This model facilitates the storage of creditor details and user account credentials, meaning end-users only need to authorize their payment with a TAN for succeeding payments from their bank accounts. This substantially trims down the steps involved for the user. Please note, that this should not be misconstrued with standing orders, which are currently outside our service scope.

Connectivity via the finX API

The finX API provides Payment services to over 2000 Financial Institutions. Here's a breakdown of the supported countries:

Supported Countries:

  • Germany
  • Italy

How it Works

You can find a Step-by-Step guide depending on your use case in the following sections: Onetime Payments & Ongoing Payments.


API Access & Authentication

The finX API is a restful API that is accessed using HTTP Basic Authentication with a Client ID as username and a Client Secret as password. Therefore each customer receives a Client ID and Client Secret from Qwist to access the finX API, which has a specific set of Scopes attached to it. Scopes define the usage rights of each Client ID on the finX platform.

If you want to get started with your dedicated credentials, please reach out to us!

Widget Integration

Before continuing with the implementation guide, please view our Widget Integration best practices.