See more projects

The customer chose to protect their confidential information

An Advanced BNPL Solution for an eCommerce Business

Financial Services
Customer rating
This ranking reflects our expertise and success
An Advanced BNPL Solution for an eCommerce Business

About the client

A European FinTech company that provides online financial services, including payments for online storefronts, direct payments, and post-purchase payments, approached Andersen. Operating across 15 countries with over 3,500 employees and handling approximately $35 billion in online sales annually, they needed a compliant, advanced, and user-friendly Buy Now, Pay Later (BNPL) solution to sustain their rapid growth. Andersen was selected as their technology partner for the task.

[object Object] on the map

Project overview

Mobile and web finance applications

Concept illustration
Introductory screens of the BNPL mobile app

The project is a solution for “buy now pay later” offers. It belongs to the type of short-term financial products that allow consumers to make purchases in stores and pay for them later.

The application offers a credit option at the checkout of partnered online stores that make it possible to pay the total over a period of time. To use the app, the customer performs a simple registration procedure and selects what they would like to buy from the partner stores. After that, users reach the check-out stage to pay later, with installments and terms fitting them best.

To make it safe, a 2-step approval decision-making module was integrated. It functions on an automated and manual basis. The automated one makes purchases simple for customers, owing to the absence of challenging credit record checks. At the same time, the manual mode helps responsible managers approve and decline some specific purchase requests.

Reminders and notifications module helps customers stay updated on their activities and purchases made via the application.

There are no hidden fees when one pays in a timele fashion. The idea behind the fees module is to help responsible managers to control the size of the fees to be paid in the case, for example, late payments. As soon as the store ships the order, the user receives an email from the application outlining the payment schedule details.

Duration13 months
Apache Kafka
Web and mobile versions of the BNPL solution
Web and mobile versions of the BNPL solution


    • 1 Domain architect
    • 1 Solution architect
    • Product owner
    • Scrum-master
    • 8 Back-end developers
    • 5 Kotlin developers
    • 1 DevOps
    • 3 Business analysts
    • 2 System analysts
    • 4 QA automation engineers
    • 4 QA manual engineers
    • 6 Front-end developers
    • 5 Swift developers
    • 1 AWS engineer

IT architecture structure

The Buy Now, Pay Later (BNPL) application was implemented with the use of microservices and event-driven architecture.

The application was implemented via microservices and event-driven architecture.

Various application modules expose corresponding functionalities to external consumers via APIs, with each API created as a container-based microservice. As for the APIs themselves, they are exposed to external consumers via the API gateway through which the authentication and authorization procedure is controlled. Finally, business processes within the modules are managed and orchestrated by the Business Process Management Engine.

Each of the Modules uses NoSQL Database for transactions and operational purposes. RDBMS is applied to manage structured data. Data caching is also performed, where applicable.

The Next Best Offering component of the Decision Making Module is built on the basis of ML capabilities.

Modules are completely decoupled and interact with each other via the Event Streaming Platform.

Concept illustration
BNPL architecture structure with module interaction
Concept illustration
BNPL card creation using biometric authentication
Concept illustration
The purchase confirmation and payment schedule

Registration and onboarding module

A fully compliant client onboarding process based on the rules for Client Classification API, Client Identification Natural Person API, and KYC API. The module tracks users and registration flows. It also tracks how users progress through them. This data can be analyzed directly in the platform. It can be alternatively exported for further analysis and integration with the rest of your event tracking features.

Concept illustration
Store locations shown on map

Decision-making module

The decision-making module is a control panel that enables one to approve purchase activities manually or automatically. If all defined rules are met, it will be done automatically. If anything fails to meet the applicable purchase rules, such a purchase would be transferred to the administrator. The manual approach requires two separate people to authorize a purchase.

The first person is responsible for creating the request (they are known as users), while the second person checks and approves such actions (they are known as administrators). This module helps specify a limit for the purchase order amount for the user. If the user tries to make a purchase order beyond the limit, this purchase order will automatically be directed to the 'To Approve' stage. That is where the admin can approve or refuse to approve this purchase order from 'Purchase Order Approval'. This module can help track approved or refused orders by such properties as "approved by", "refused by", "approval date", "refusal date", "refusal reason". It is possible to notify and alert about approvals via an email sent to a specific user or the manager responsible for approving a purchase limit.