Handled Errors in Flinks Connect

Modified on Mon, 15 Jul at 1:41 PM

Flinks Connect handles credentials validation, multi-factor authentication and errors for each supported financial institution.

For accessing their financial data, end-users must follow the authorization process and in this article we have the example of each error that a end-user could face during this process and what the interface looks like.


 


If you enter an invalid username you will receive this message:


  • Error message one the JS Event: INVALID_USERNAME


If you enter an invalid password, the error message will be the following:


  • Error message one the JS Event: INVALID_PASSWORD


Sometimes when you enter an invalid username or password, you may encounter a different message like the one bellow. We return the message that the financial institution returns ,so it's also possible that you get this:


  • Error message one the JS Event: INVALID_LOGIN


When a wrong answer to a security question is entered, you will get this message :


  • Error message one the JS Event: INVALID_SECURITY_RESPONSE


It's possible that sometimes the financial institution is under maintenance and its services are not available. In that case we will return this message:


  • Error message one the JS Event: RETRY_LATER


For the case where the account has been disabled by the financial institution, we will return "Deactivated Account". In this case, the bank temporarily disabled the end-users card. This can happen when a card is connected multiple times and the financial institution flagged the requests as suspicious. When this happens, the user needs to contact the bank:


  • Error message one the JS Event: UNAUTHORIZED


If the API returns the NEW_ACCOUNT Flinks Code, it means the user must take action on the bank's website before a successful connection with Flinks can be made. The user will see the following message in this case:



  • Error message one the JS Event: NEW_ACCOUNT

 


If an unexpected error occurs, typically on Flinks's end, the following screen will be displayed:

 

  • Error message one the JS Event: AGGREGATION_ERROR


  • Error message one the JS Event: DISABLED_INSTITUTION



  • Error message one the JS Event: DISABLED_LOGIN



In our Documentation, there is the Flinks Connect configurator where you will have access to these and several other scenarios within our frontend experience. This feature is available here: https://docs.flinks.com/docs/configure-and-install-flinks-connect.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article