React · Redux · Business payment solutions

Centralising OTP confirmation across Nexi Business workflows.

The project

Project context

Nexi provides businesses with digital tools for payments, cards, and operational management. Within Nexi Business, several sensitive journeys required confirmation through a One Time Password.

The challenge was not displaying a single OTP screen. Business registration, account management, and payment operations could reach confirmation after different sequences, states, and checks.

We were contracted to design and develop a centralised component that could fit into these journeys without duplicating the same logic for every feature. It had to work within the existing React architecture and implement the designs supplied in Figma.

The result was one frontend entry point for the OTP experience, while each business process retained its own steps and requirements before confirmation.

Platform: React · Redux
Area: Business payment solutions
Client: Nexi Business
Delivered solutions: 01
Delivery evidence: One reusable OTP component serving three workflow categories: registration, account management, and payments.
Our role: Frontend design and development of the shared OTP component, integration with the existing architecture, and implementation of the Figma designs.
Authored by: Klajdi SharkaFounder & Technical Lead

Delivered solutions

Distinct solutions for concrete needs.

Each solution addresses a specific technical or operational constraint. Together, they show how we contribute through custom development, integrations, migrations, replatforming, or engineering capacity embedded in the team.

Reusable OTP component for different business workflows

Engineering challenge

Multiple Nexi Business journeys required OTP verification, while each could have different states, confirmations, and preceding steps. Implementing OTP separately in every flow would have duplicated logic, validation, and interface behaviour.

Delivered solution

We developed a centralised React component that could be used by different business processes. Redux coordinated application state, while Redux Form handled form state and validation. The component implemented the interface defined in Figma and integrated with the existing architecture, which we analysed and corrected where needed to support the new shared flow.

Operational value

Registration, account-management, and payment processes could converge on the same OTP experience without losing the rules specific to their individual journeys. Nexi therefore had a consistent, reusable foundation for extending OTP confirmation to additional workflows.

Facing a similar need?

Let’s discuss your next software project.

Share the objective, stack, and constraints. We can assess either a scoped solution or continuous engineering capacity embedded in your team.

Discuss your project