Getting Started

In compliance with PSD2ClosedPSD2 stands for Payment Services Directive 2 and is a new EU regulation in effect since September 14, 2019. It governs electronic and other non-cash payments. The main provision of PSD2 is for Strong Customer Authentication (SCA), a process that seeks to make online payments more secure and reduce fraud while increasing authorisation rates. The European Banking Authority (EBA) recently extended the deadline for PSD2 compliance until December 31, 2020., the instructions provided here are specifically designed for third-party provider (TPPClosedThird-Party Provider – an authorised online service provider introduced as part of Open Banking. TPPs exist outside of the account holder’s relationship with their bank but may be involved in transactions carried out by the user.) integration with the Token CloudClosedTokenOS is the operating system for open banking. It provides turnkey PSD2 compliance and allows third-party developers to easily and securely develop applications that support payment initiation and account information retrieval. The core of TokenOS is the "smart token," providing authorization to access an underlying asset. Smart tokens define the conditions (rules) governing access to the asset. and Token-supported banks. So, whether you're a PISPClosedPayment Initiation Service Provider – a TPP that initiates a payment order at the request of the payment service user with respect to a payment account held at another payment service provider., AISPClosedAccount Information Service Provider – a TPP authorised to access consumer or business account data from the account holder's financial institutions with the account holder's explicit consent. or CBPIIClosedCard Based Payment Instrument Issuer – a payment services provider that issues card-based payment instruments and allows its customers to pay from bank accounts., getting you up and running as smoothly and efficiently as possible is our top priority.

Token's SDKClosedSoftware Development Kit – the set of software tools and programs used by developers to create applications for the Token platform. Token's SDK includes libraries, documentation, code samples, processes, and guides that developers integrate into their own apps. is designed for rapid implementation within your web/mobile app and is available in multiple programming languages, currently comprising JavaClosedProgramming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere!, JavaScriptClosedOften abbreviated as JS, JavaScript is an interpreted programming language that conforms to the ECMAScript specification — high-level, often just-in-time compiled, and multi-paradigm. It has curly-bracket syntax, dynamic typing, prototype-based object-orientation, and first-class functions. Alongside HTML and CSS, JavaScript is one of the core technologies of the World Wide Web. All major web browsers have a dedicated JavaScript engine to execute it., and C#ClosedGeneral-purpose, multi-paradigm programming language encompassing strong typing, lexically scoped, imperative, declarative, functional, generic, object-oriented (class-based), and component-oriented programming disciplines. It was developed around 2000 by Microsoft as part of its .NET initiative, and later approved as an international standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270:2018).. Java is shown by default.

Click a different language tab to see the corresponding example and the respective links to its API technical references (JavadocClosedStandard Java API documentation in HTML format; parses the declarations in a source file into documentation describing classes, methods, constructors, and fields., ESDocClosedDocumentation generator for JavaScript., or .NET SDKClosedOnline API docs containing the programmatic definitions of every type and method applied using the C# SDK.). 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-supported services offered, shows you how to enroll (onboard) with Token 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-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-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.