- Q1. If I want to migrate an existing application to the new Difitek platform, how long will it take?
A1. The functionality of the new API is almost identical to the older API which is running on the existing architecture. However, there are some important differences which we made to improve the functionality, bring more consistency to the API, and to give more power to developers to build the workflow processes that their customers require.
We would expect that a migration of a front-end application from using the existing API to the new API may take a couple of months, depending on the complexity of the application.
- Q2. Will all features of existing platforms be available on the Difitek platform?
A2. At first there may be some integrations and features that are not available in the new API, on which front-end applications relied when using the existing API.
This may be because the features are handled in a different way with the new architecture, for example, it does not send out emails and so developers are encouraged to use webhooks alongside their own online mail service. In this case there may not be an exact equivalent of an existing function in the new API.
It may also be because other features have been prioritised higher but the required feature will still be implemented as early as possible.
Please get in touch with your Difitek support contact if you have any specific questions about an existing feature.
- Q3. What volume of API calls will the new version be able to handle?
A3. Difitek's new technology will allow customers to build powerful and elegant platforms without worrying about scalability. The new API will be able to handle a potentially unlimited amount of calls per second asynchronically, allowing you to perform different actions simultaneously and virtually in real time.
- Q4. What SDKs will be provided for the API?
Since the API is RESTful and follows standard market practices, developers can also easily use the Postman application to generate code in other languages to consume the API.
- Q5. Is there any reason to build a new platform on v3 now?
A5. The existing architecture remains available for new accounts and it is still the fastest way to get a new prototype application to market: it has more integrations available, it does not require setting up your own Back Office application or online mail service, and it is proven with hundreds of FinTech applications using it in the market.
However for longer-term and stable applications we would recommend using the latest technology as early as possible so as to get all the benefits of the latest technologies and services.
- Q6. We are supporting an existing Difitek customer. Will we need to change anything?
A6. No. The existing architecture will still be maintained for the foreseeable future.
You may however want to discuss with your customer the benefits of using Difitek's new distributed architecture in order to improve the functionality of your applications and also to benefit from being able to connect other online services to your operational processes and workflows.
- Q7. How easy it is to integrate our processes with other applications?
A7. Difitek's new product enables webhook events that can notify third-party application any time an event occurs on your account. This is particularly useful for events that are not triggered by a direct API request, such as returning the result of a KYC check. You can then use any application aggregator (such as Zapier) to connect your favourite CRM or mailing system to our API events.