Getting Started

In compliance with , the instructions provided here are specifically designed for third-party provider () integration with the and Token.io-supported banks. So, whether you're a , or , getting you up and running as smoothly and efficiently as possible is our top priority.

Token.io's is designed for rapid implementation within your web/mobile app and is available in multiple programming languages, currently comprising , , and . Java is shown by default.

Click a different language tab to see the corresponding example and the respective links to its API technical references (, , or ). Partial examples also include SOURCE links to the larger code block from which the example was extracted.

Intended for developers familiar with embedding external SDKs within their application framework, the guidance presented here introduces you to the Token.io-supported services offered, shows you how to enroll (onboard) with Token.io as a registered TPP, then guides you through what's necessary to enable the payment initiation, account information, and/or card-based instrument services supported.

Remember, the SDK is essentially a library that assists you with shortcuts for developing code to communicate via API with Token.io-connected banks. But no SDK is a panacea. Here's two important tips to help you to integrate with the SDK successfully.

  1. Develop a clear game plan. The goal is to extend and expand your current application with real-time open banking functionality. Its value-added potential notwithstanding, before touching any new code, make sure you have a clear game plan. In relation to your existing application and system, ask yourself:
    • What are the metrics that determine SDK integration success?

    • How should these metrics be analyzed and recorded?

You shouldn't consider yourself ready to install, vet and test the SDK until you determine your overall integration strategy and how the SDK fits into your current processing paradigm.

  1. Commit time to review the SDK documentation provided. Before diving headlong into SDK integration, it’s important to keep in mind that Introducing new code into any environment carries a degree of risk. Most of these risks are mitigated by a clear understanding of what's required and when. Review the Token.io-provided SDK documentation thoroughly, then make sure all prerequisites are met before continuing.

Your review should mainly focus on project-versus-SDK dependencies and how to accommodate them. Completing this exercise will help you maximize the benefits and minimize issues in the long run.

Click the next button at the bottom of each page to continue — to return to the previous topic — or select a topic from the navigation panel to explore.