Onboarding

Note: licensing requirements dictate that a TPP using a bank's APIs must be and remain a in good standing. are regulated to provide trusted digital certificates under the electronics Identification and Signature (eIDAS) regulation. A list of QTSPs supplying PSD2-compliant qualified certificates is available from Open Banking Europe.

To become QTPSP-eligible to use a bank's APIs, you must:

  1. obtain authorization from a National Competent Authority to operate as a Payment Services Provider under each of the roles services you will provide (AIS, PIS, and/or CBPII).
  2. obtain an -compliant or certificate or both.

In the meantime (presuming you don't yet have the necessary license and certificate), you can still work on SDK integration in our sandbox, a virtual testing environment in which you can interact with notional banks and money to validate your SDK integration before accessing real accounts in production. Then, when you're ready to go into production, you can provide Token.io with both a valid license and a certificate, both of which are electronically rechecked and verified throughout each business day, or you can choose to use Token.io's licence.

As previously mentioned, Token.io provides a virtual testing environment called the sandbox. This is where you can test your integration with notional banks and money before accessing real accounts at real banks.

Seven essential tasks comprise the initial onboarding process:

  1. Download and install the SDK in your IDE
  2. Set up the client
  3. Create a business member
  4. Add and verify an alias
  5. Load an existing member
  6. Set up a business member profile
  7. Manage your keys

Click a link in the list above to learn more about each step.