Skip to main content
-
Will this change have any negative effects on end users such as their consents will be invalidated and they will have to reauthenticate?
-
Why do recurring consents only allow today + 179 days instead of 180 days?
-
Can PSU involvement be tracked with the PSU-IP-Address to avoid unwanted consent “consumption”?
-
Is it possible to use more than one recurring consent at a time for specific (PSU, TPP, Bank) combination?
-
Does a new authorisation from the same PSU invalidate the previous consent/token when we are using the same certificate?
-
Can 2 data consents run at the same time under one TPP? E.g. If a PSU has an active data consent with one app, and then activates a new consent with with another app, will the original consent be unaffected?
-
Do you support one-time consent? Which parameters need to be configured?
-
It seems that when end user creates a new consent he get’s a new resourceId from GET /account list request for the same IBAN. Is this expected behavior?
-
Why do I get the following error message when the consent is still valid? error code 401 "CONSENT_INVALID","title":"The consent definition is not complete or invalid."
-
If we change our certificates, will all consents obtained with the old certificate expire?
-
For AIS endpoints, will the account ID assigned to each PSU change if they re-consent under new certificates?
-
Why we are not able to create consent using your API? {"code":"ROLE_INVALID","type":"https://berlingroup.com/error-codes/ROLE_INVALID","title":"The TPP does not have the correct PSD2 role to access this service.","status":401,"detail":"Required role was n