Testing

Testing is important to ensure that everything is set up correctly and works as expected. Flinks allows you to do testing in both your Flinks Dashboard and in Flinks Connect. Read the following passages to understand how to start testing with Flinks.

​

Test in your Flinks Dashboard

We provide dummy data that you can use to complete testing in your Flinks Dashboard. To start using dummy data, locate your sandbox credentials:

1. Click on the Settings screen and navigate to the Environments tab.
2. Locate the Sandbox environment, then expand the row. These are your sandbox credentials that you can use for testing.

​

Complete error testing in Flinks Connect

You can log in to Flinks Connect using our dummy institution for testing purposes. With the dummy institution Flinks Capital, you can test happy paths and edge cases while experimenting with different functionalities. The login credentials are as follows: Username: Greatday Password: Everyday Institution: FlinksCapital

​

Security Questions and Answers

The security questions for the testing environment differ depending which country you are logging in from.

​

Canada

In Canada, the account has three security questions and answers. Use the following answers when asked: What city were you born in?: Montreal What is the best country on Earth?: Canada What shape do people like the most?: Triangle

​

United States

In the United States, most of the security questions are basic arithmetic questions. Questions you will find may look like: How much is 2 + 2?: 4

​

List of errors to test for

The following is a list of errors that you can test for in Flinks Connect. To try testing, input the instructions to log in to the dummy institution Flinks Capital, but change the username to the one suggested under the error you’d like to test.

​

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

Sometimes the financial institution is doing maintenance, and its services 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 has 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 Asynchronous flow. 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 has 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 Asynchronous flow. To test this, change the username to: test_pending.

​

Delay in GetAccountsDetailAsync

The test user will add a 30-second delay in retrieving the data through our /GetAccountsDetailAsync endpoint. To test this, change the username to: greatday_delay

​

Expired Session

This test user will trigger a SESSION_EXPIRED message. To test this, change the username to: test_session_expired

​

Too Many Failed Attempts

If the user enters incorrect login credentials, or fails to successfully answer the MFA question(s) after a certain number of tries, they’ll be shown an error message. To test this screen, change the username to: test_too_many_failed_attempts

​

Complete Multifactor Authentication testing

Some banks have unique special flows that you may encounter while your end-user is attempting to connect to their bank account. It is possible to test them with FlinksCapital to ensure that you can support them correctly. Take note that all of the following usernames share the same password: Password: Everyday

​

Questions and image selection Multifactor Authentication

After answering the usual Multifactor Authentication (MFA) question, the client must select their personal image from a list. To test this, change the username to: test_laurentienne

​

Iterable Multifactor Authentication questions

Sometimes, the institution will ask the client to reset their MFA questions and answers during the account connection step. This situation happens when the bank has determined that a suspicious login attempt was recently made. To test this, change the username to: test_rbcsecurity

​

Trusted device or push notification flow

Some institutions have a flow in which a trusted user’s device receives a notification to confirm the authentication. To test this, change the username to: test_realtime

​

Different types of Multifactor Authentication

Similar to the iterable MFA questions, this flow happens when the user incorrectly answers their MFA question 3 times in their latest login attempt. The client will first have to confirm their identity by answering a question that only they should know the answer to. After this successful confirmation, the client must recreate a new set of 3 questions and answers. Here are all the possible types of questions:

• QuestionAndAnswer with prompt
• MultipleChoice with iterables
• MultipleChoiceMultipleAnswers with iterables
• QuestionandAnswer with iterables

To test this, change the username to: test_scotiasecurity

​

One Time Passcode

Some financial institutions have activated two-factor authentication, requiring the user to select a phone number and an action (text or call), then enter a security code also known as a One Time Passcode (OTP). To test this, change the username to: test_td