Flinks Capital is our dummy institution for you to test happy paths and edge cases while experimenting with different functionalities.

Username: "Greatday"
Password: "Everyday"
Institution: "FlinksCapital"

Security Questions and Answers
What city were you born in? : Montreal
What is the best country on earth? : Canada
What shape do people like most? : Triangle

Error handling

Disabled Account
Sometimes an account may be disabled on the institution's side. When that happens, Flinks Connect will return the DISABLED_LOGIN FlinksCode.

To test this, change the username to: test_disabled_account

Service Unavailable
Sometime the financial institution is doing maintenance and their service are not available. When that happens, Flinks Connect will return the RETRY_LATER FlinksCode.

To test this, change the username to: test_service_unavailable

Operation dispatched
When your request exceeds 210 seconds of processing, we will return you a 202 Accepted and a partial result of what had been processed so far. This means we have dispatched the process into a queue for long running operations. When that happens, Flinks Connect will return the OPERATION_DISPATCHED FlinksCode.

In order to retrieve the data, you will need to long poll the Async endpoint as explained in the GetAccountsDetail section.

To test this, change the username to: test_dispatched

Operation pending
When your request is not yet completed, we will return you a 202 Accepted and a partial result of what had been processed so far. This means we are still processing the operations. When that happens, Flinks Connect will return the OPERATION_PENDING FlinksCode.

In order to retrieve the data, you will need to long poll the Async endpoint as explained in the GetAccountsDetail section.

To test this, change the username to: test_pending

No MFA
Sometimes an account doesn't have MFA, when this happens an authenticated loginId will be issued after the username/password is validated by the FI.

To test this, change the username to: "greatday_nomfa"