You are seeing this error because the limit for non-actively requested account information access, as defined by the provider's policy under SCA RTS Article 36.5.b, typically 4, has been reached. This policy restricts the number of requests for account information that can be made without active engagement from the Payment Service User (PSU).
What to do next?
To resolve this issue, you need to include the end-user’s IP address in your API requests. This helps to indicate whether the request is actively made by the PSU and whether they are logged in with the Third-Party Provider (TPP).
Here’s how you can fix it:
- Obtain the PSU’s IP Address: Ensure you have the IP address of the end-user (PSU) making the request.
- Include the IP Address in Your Request:
- Add the
token-customer-ip-addressheader to your API request. - Ensure that this header contains the PSU's IP address.
For detailed instructions on how to include the token-customer-ip-address header, please refer to our API documentation.