— What we did > We aggregated a large number of third-party payment services into a single interface by suggesting an API design that balanced integration effort and the complex logic on the orchestration platform itself.

— The value > Offering a balanced API design led to the sustainability of the solution working in multiple regions with a many different third parties.

— What we did >As subscription modules can be immensely rich in features development, Qaiware’s product team suggested a design based on both our experience in software design and specific knowledge of the Card-on-File framework. The solution leveraged a number of existing systems in the client’s landscape, treating the module as a part of an offering and not a standalone product by itself.

— The value > The customers, and even developers integrating the system, would have the same experience and would potentially have a better overview of the complete offering by the client. In addition, the approach improved time to market.

— What we did > A microservice architecture was chosen for the platform from the very beginning of the project, which enabled Qaiware to easily suggest and implement a performant solution that fits the client’s business needs. Via carefully time-boxed research, the team suggested а number of improvements addressing performance and technical debt in general. Among these was the introduction of the CQRS pattern and improvements to the data model.

— The value > After implementing the solution the system witnessed a significant performance boost.

— What we did > Qaiware organised its autonomous agile delivery process which had to interface with the client’s complex business environment in order to collect requirements and feedback, as well as to efficiently drive the software through UAT and towards a productive environment. To do this, the delivery team of the company suggested a set of scheduled events with the participation of only their relevant stakeholders. Among the events were refinement meetings, steerco meetings, regular status updates, and roadmap revision events.

— The value > Having a well-defined interface with the Client organisation did not stand in the way of the agile process, but successfully made it easier to address issues on time.