Set up your Tink Console account

Tink Console is where you create, configure, and manage your apps. It's also the place where you find analytics.

Create and verify a Console account

To get started, you must sign up for a Console account. When you've signed up, open the email we've sent you. Use the link in the email to verify your account and then log in to Console.

Before you start, we want to let you know a few important things.

Product availability

By default all our products are available to test in our sandbox environment. You can access it by creating a sandbox app.

Once you’re ready to move to production, please follow the instructions below to send your request.

⚠️ Please note that all those steps are mandatory in the following order:

  1. Reach out to our business team via the contact sales form
  2. Create a production app
  3. Go to Console > Products and request production access
  4. Complete KYB

After completing KYB our internal team will review your application and we will reach out to you when your production access is available.

What is an app?

Apps are a data bucket and security concept in the Tink platform. An app allows you, the customer, to gather multiple users and their data, and access the data with a set of keys. Our recommended app setup is as follows:

  • Sandbox app: Sandbox apps allow you to perform tests by only using test credentials and test data. Create one sandbox app per product, which you can use with our Demo Bank feature.
  • Pre-production app (optional): Many developers like to run tests using real credentials, with the most common scenario being developers using their own or a colleague's bank credentials to test how an end user would experience their Tink integration. In this case, we suggest creating a production app and giving it a name that clearly shows it's a pre-production app. This allows you to separate test and production data.
  • Production app: Production apps only connect with live banks and allow you to store real end-user data. This is the app you should use once you’ve tried and tested your integration and are ready to go live.

Create your first app

To get started we encourage you to create a sandbox app to be able to test the products your are interested in.

Your app settings are available after you've created your first app.

Note: once your app is created you can’t change the app type, so choose wisely.

  1. Log in to Console.
  2. Select Create your first app.

    The Create a new app view appears.
    console create a new app
  3. Enter an App name. This name is only available to other Console users who are part of your organization. This name can be changed later.
  4. Enter a Display name (public). This name is seen by your customers as part of the Tink flow. This name can't be changed later, so be careful.
  5. Select your App type: sandbox or production. The app type can't be changed later, so be careful here too.
  6. Select Create app.

Your app is now created and ready to configure.

Access your API credentials

Your API credentials are used to authenticate your app with the Tink API. This is how you find your credentials.

set-up-your-tink-console-account-02

Your API credentials are found in [your_app] > App settings > API client.

In this view, there are two important keys:

  • client_id: this is the unique ID for your app. This key is public and is instantly available once you create an app.
  • client_secret: this is a secret key for your app. This key authenticates your app with the Tink API. Handle it confidentially. You can create up to five secrets, which you can revoke at any time. Client secrets don't exist by default, so you must create them.

Create a client secret

  1. Log in to Console.
  2. From the top dropdown menu, select an app.
  3. Select App settings.
  4. Select the API client tab.
  5. Select Create new client secret.
  6. Enter your Console account password.
  7. Select Create.

    Your new client secret key is displayed.
  8. Copy your new secret and store it in a secure location as it can't be revealed later.