The Avoka Platform

Building exceptional customer journeys for financial services and banking

As a front-end developer, you want to build user experiences that differentiate your digital properties from your competition. Unfortunately, that also means that you need to handle many things that cross from front-end to back-end services and develop features that a front-end cannot always manage. That’s where a platform that gives you the ability to “create” while providing and orchestrating the services to support your front end comes in.

The Avoka Platform is designed to create a seamless orchestration between the acquisition of customer data and the back-end system of record.

Avoka architecture diagram

Avoka solves 4 key architectural challenges in building omnichannel customer acquisition and onboarding systems:

  • Interoperability with existing Systems of Record.
  • Interoperability with 3rd party systems for actions like ID verification, risk scoring, and fraud detection.
  • Creation and maintenance of functionality common to any acquisition process, such as security, scalability, save & resume, receipt generation, attachments, and bundling of multiple forms.
  • Behavioral Analytics for measurement and continuous improvement of the CX.

The Avoka Platform supports all the key facets of the customer acquisition process, by providing features to the front-end channels as functions, and simplifying the omnichannel experience for the end consumer. Avoka delivers the ability to maintain a loose coupling of the state, user data, and input actions of the consumer to the back-end system, which allows rapid deployment of customer initiatives without complex and costly changes to existing systems.

What is the Avoka Platform?

Avoka acts as a PaaS, providing a service platform on which banks can deploy their web applications. Inside the platform there are multiple services that run independently of one another, providing the platform functionality such as security, front-end services, management, and reporting and operational monitoring. These services can be independently scaled and adjusted to fit the need of the customer’s applications. The Avoka PaaS architecture allows rapid and simple deployment and scaling of services needed to deliver complex user experience orchestrations.

The Avoka Platform is most often deployed as a cloud-based system, configured as a private secure environment for each bank. End users engage in the customer acquisition journey through the Avoka Platform’s server, and application data is exchanged to and from bank systems of record via API services. The Avoka configuration in the Amazon AWS cloud provides for the highest levels of security, reliability, scalability and data integrity.

Avoka Cloud Architecture Diagram

Interacting with the Avoka PaaS is made simple through the ability to make API calls from the front-end framework of choice, meaning that the complexity of building multiple platform services is reduced to a set of standard REST API calls. This allows the bank development team to dictate the terms of engagement with the platform, choosing to either leverage in-house skills to build experiences or using Avoka’s tools for building customer interaction workflows, saving time and expense against having to build the entire set of services from scratch.

You can read in-depth about the complete Avoka platform in our documentation library.