A client application identifies a caller requesting your Powens API. One client application is required at least per API. The definition of a client application lets you configure the associated Webview, a ready-to-use web interface to add connections to your domain. You can configure multiple client applications if you wish to propose webviews with different settings.
A connection materializes the link between an end user and one of the connector we support. Adding a connection requires the end user to authenticate on the connector. As long as the credentials stay valid, we take care of synchronizing user data. Product data are available through connections.
Credentials generally represents end user identifiers (login, password or other key fields). In the context of connections in Powens API, "credentials" is also the name we use for a specific authentication mechanism where the end user is filling a form with his identifiers in order to establish the connection with the institution. In this case, we store the credentials in an encrypted and secured device.
Payment Service User, the end-user of payment services.
In order to access institution information (bank accounts, transactions, billing contracts, documents…), we can use various channels. The channel allows us to establish a connection with the institution, it is called a connector source. We currently handle three types of source:
A subscription is a representation of a bill contract or group of documents. It is a parallel representation of accounts on the bank system.
"webauth" is the name we use for a specific authentication mechanism where the end user is redirected to the app or website owned by the institution on which he wants to connect. In this case, we do not store end user credentials, the login process is handled by the institution that just confirms or denies the authentication and calls us back.