Today, we officially release the Tikkie API. Sandbox access is now open, so you can view the documentation and start experimenting. Whenever you are ready, reach out to go to production.
 

 

The road so far

In November 2017, we launched our first product, the Tikkie Payment Request API. It was the first product published on the ABN AMRO Developer Portal. Since that time, we have watched the Tikkie Payment Request API being used in many innovative ways, and saw it provide solutions to many business propositions.

Over the last two years we have been assessing what worked well with the API, and what could be improved. Based on what we have learned, and feedback from our customers, we decided to rethink the API and redesign it from the ground up. This redesign involved creating and launching a new product — the Tikkie API. This redesign allows us to easily extend and add new functionality in the future.

What’s new

During the redesign, we went back to the drawing board and determined what the building blocks should be. The resource structure in the Tikkie Payment Request API was complex, and not easily understood. For example, when a user wanted to go to production, a manual step was involved on our end. We also needed to add a long-requested feature to refund payments.

At its core, the Tikkie API has three resources:

• Payment requests: requests to be paid a fixed or open amount.
• Payments: execution of payments relating to payment request.
• Refunds: refunds on executed payment requests.

These resources are nested and have a zero to many relationship, meaning one payment request can have zero to many payments, and each payment can have zero refunds.

In the Tikkie API, an app is created in the Tikkie Business Portal and contains a token. This token is used, in combination with the API key from the ABN AMRO Developer Portal, in API requests. You can have multiple apps for different systems and you can assign specific permissions to each app. You control all permissions regarding your apps and do not require any manual intervention from the Tikkie Team to work with an API.

The Tikkie API already provides more functionality than the Tikke Payment Request API, but there is even more to come. In addition to payment requests and refunds, a module is in development which will enable business customers to collect their bundled payout file in CAMT.053 format, similar to in the Tikkie Business Portal. This module will also enable the retrieval of transaction details, which can be used, for example, in accounting systems.

Whenever additional functionality is released, we will notify all existing users so that they can make use of it.

Decommissioning of the Tikkie Payment Request API

In launching the Tikkie API, we are also announcing the future decommissioning of the Tikkie Payment request API. As this is the first API that will be depreciated on the ABN AMRO Developer Portal, we have given this considerable thought. Our aim is to encourage developers to start working with the Tikkie API, while also ensuring that the time spent developing with the Tikkie Payment Request API will not go to waste. Our decommissioning approach involves the following three time lines.

Months 0–3

• From today, it is not possible to use the Tikkie Payment Request API in the sandbox environment. You can now use the Tikkie API instead.
• Developers who are currently building their solution in the sandbox with the Tikkie Payments API, and would like to go to production, can do so. However, to ensure that you can make use of the new functionality as it is released, we strongly advise that you start using the Tikkie API now.
• Developers who are using the Tikkie Payment Request API in production will not experience any changes, however, you are advised to start looking into the new API and to plan a migration.

Months 3–9

After three months, it will not be possible to go to production on the Tikkie Payment Request API. Any new developers, or developers who have not gone to production before the three-month mark, can start directly with the Tikkie API.

Month 9 and onward

After 9 months, at the end of 2020, we will officially retire the Tikkie Payment Request API. This means all current implementations will cease to work. Therefore, developers are advised to plan ahead and decide when they will migrate to the Tikkie API.

We’re proud to release the new Tikkie API. To get started and use this API, go to the sandbox.