FAQs

Customers
  • Q1. Will I need to pay more to continue my existing service?
  • A1. No. The release of the new Difitek distributed architecture does not affect your existing commercial terms.



  • Q2. Does my contract automatically include access to the new Difitek platform?
  • A2. No. The Difitek distributed architecture may be subject to new commercial arrangements. Please get in touch with your Difitek support contact for further information.



  • Q3. Will the current system ever be retired? Will I be forced to move to the new Difitek platform eventually?
  • A3. The current system will continue to be supported for the foreseeable future and it is not our intention to force customers to move to using the new architecture. Due to the nature of online technologies, certain third-party elements of the current stack will naturally be retired as and when they become depreciated. At some point in the future the tools and frameworks that this architecture uses will, therefore, inevitably fall out of use. Difitek will continue to maintain the older architecture for as long as it is still being actively used by customers; however, our hope and expectation is that all customers will want to use the latest technologies and features well before the point at which such maintenance becomes impossible due to other technology libraries expiring.



  • Q4. Is the update to the Difitek platform automatic or can we continue using the current system?
  • A4. No. Existing Difitek clients will be able to decide what technology is best for their needs. We also provide secure and stable product versions without requiring any updates, so that clients will be able to run to a specific release of the Difitek API in their applications.



  • Q5. Why should I make the move to the Difitek platform if my existing system is already live?
  • A5. The new Difitek architecture streamlines many more of your operational processes. Moving to our new distributed, connected architecture allows you to make much more sophisticated automated workflows both in your applications and in the way your team works. Thanks to the new support for webhooks and asynchronous data exports Difitek customers can trigger other online services using any API trigger point, such as when a new User signs up, or when an Investment is made. This means that customers can send emails from their own domain by connecting to their own online mail service, or SMS messages, or internal notifications to their teams through Slack or JIRA.