Skip to main content
Version: v2

Consent services

Consent services are LinX services aimed to help our partners create, manage, and delete their customers consents.

Something about the context for a developer.

To use the PSD2 functionalities in LinX, the account owner must give consent first. There are two different endpoints to use. Additionally, there is an endpoint for fetching overviews of submitted consents.

Submitted consents are grouped through a ConsentCollectionId. This is a GUID that must be provided by the LinX client and will be used to link one or more consents to the same context (i.e.: a user, or a session).

PSD2 consents can be collected in two different ways:

  • By using the Consent wizard where the user submits their consent
  • By requesting the consent directly for a bank and sending a user to the bank's website.

Account info​

The Account info endpoint is used to request an overview of submitted accounts for ConsentCollectionId's.

The Consent wizard is a website where users can give consent for one or more banks at the user's own choice. To get access to this wizard a URL must be generated using the ConsentWizard endpoint. This URL is valid during the wizard session. When users have given consent, they are returned to the provided URL when generating the Wizard URL.

The Consent url endpoint consent can be requested at a bank and send the user to the bank's website to confirm consent. After receiving consent, users are returned to the provided URL when generating the bank URL.

The Consent info endpoint is used to request an overview of submitted consents for ConsentCollectionId's. It contains, among other things, the IBANs for which consent has been given.

Clear collection​

The Clear collection endpoint can be used to remove all IBAN's in Consent Collection's.