Cases — Codeminers

Case study

BURSA

A digital transfer platform for card-to-card, phone-based and link-based money movement, designed around fast user flows and operational clarity.

Project context

BURSA was shaped as a customer-facing money transfer service where users could send funds without navigating a full banking product. The interface had to support direct transfers, registration prompts, saved cards, payment history and clear confirmation states.

Client challenge

The product needed to make several payment scenarios feel simple while keeping the flow structured: non-registered transfers, registered cabinet usage, card management, transfer by phone number and receiving money through a link.

Scope

Payment flow engineeringCustomer-facing interfacesPlatform component developmentOperational workflow support

Outcomes

Clearer payment and transfer flowsMore reliable service interaction pointsRoom for continued product and platform evolution

Technology scope

Payment flowsService portalAPI integrationsOperational tooling

Product solution

A focused transfer experience outside the heavy banking interface.

We organized the product around a small set of high-frequency actions: start a transfer, choose the destination, confirm the payment, reuse a previous operation and manage cards after registration. This keeps the service useful for one-time users while giving returning users a faster cabinet experience.

Card-to-card transfer

Transfer to phone number

Transfer link receiving flow

Payment history and repeat payment

What the case includes

Transfer entry point

A public start page explains the offer, supported payment methods and the main transfer form without requiring registration first.

Registered cabinet

The cabinet adds payment history, saved card context, row controls and quick actions such as repeating a payment or downloading a receipt.

Receiving scenarios

The flow supports receiving money through a link with explicit success and error states, so the user can understand what happened without support involvement.

Product screens

The interface assets show the public transfer page, phone transfer flow, confirmation state, payment history and card-related onboarding.

Completed link-based transfer receiving flow

Product result

Clearer payment journey

The service separates transfer types and keeps the main action visible across public and registered flows.

Reusable user operations

History, repeat payment and receipt actions reduce friction for returning users.

Support-ready states

Success, error and link-receiving screens make operational states easier to understand and explain.

Looking for a technology partner for a banking or fintech product?

Let’s discuss your product scope, architecture needs and the most suitable delivery model.

Discuss a project