SendWise — Money Transfer App

Overview

SendWise is a peer-to-peer money transfer app we designed and built as a product. It is for people who send money to friends, family and regular contacts and want to be certain a payment reaches the right person for the right amount. The interface is deliberately quiet, since calm visuals build more confidence in a financial app than clever ones.

The Challenge

Mistakes are expensive when money moves and often hard to undo. The familiar failure points are a wrong recipient picked from a list of similar names, a fee the sender did not notice, and an amount confirmed without a proper look. The design had to cut those errors without making a transfer feel slow or bureaucratic, and had to give the app a visual identity that reads as dependable.

Who Uses It and How

A typical sender opens the app, picks a saved contact, types an amount and confirms. Regular transfers, such as a monthly contribution to family, repeat the same steps, so speed and recognisability matter. A first-time recipient needs extra care at the moment of adding them. Behind the product, a support agent investigates disputed or failed transfers, and a compliance or operations role reviews flagged activity. Those roles use internal tools separate from the customer app.

Our Approach

Safety became part of the flow rather than a warning bolted on. Each transfer passes through an explicit review screen that shows the amount, the fee and the total in one place, so nothing is revealed after the user has committed.

To reduce mis-sends we added recipient nicknames, giving users their own memorable labels. Visually we chose restraint, with plain typography and minimal layouts. We built natively in Swift and Kotlin so each platform feels correct and can use system security features, with a Node.js service holding the transfer logic.

What We Built

The journey runs from choosing a recipient, to entering an amount, to the review screen, to final confirmation. Nicknames appear from the contact list through to the review step. Both native apps call the same Node.js backend, so fee rules and validation live in one place rather than being copied into two codebases.

Architecture and Data

Core entities are users, recipients, transfers, fees and a ledger of transaction states such as created, pending, completed and failed. Each transfer request carries a unique idempotency key so a retry after a dropped connection can never send the money twice. The backend calculates the fee and total, and the review screen displays what the server returned, so the app cannot show one figure and charge another. Movement of actual funds would go through a licensed payment provider or bank partner.

Security, Privacy and Quality

Financial products carry the strictest expectations. Sign-in should support biometrics and a device passcode, sensitive values belong in the platform's secure storage, and all traffic uses encryption. Amounts should be handled as integers in the smallest currency unit, not floating point numbers. Testing focuses on rounding, fee calculation, duplicate submissions, timeouts mid-transfer and permission of each role, with device checks on both platforms.

Technology

Native development is a considered choice for a money app. Swift and Kotlin give direct access to secure storage, biometrics and the conventions users already trust, and a shared Node.js backend keeps both apps behaving identically.

Outcome

SendWise gives users a flow where the important facts are visible before money moves and where recipients are easy to tell apart. For the business, that means a product designed to lower the risk of wrong-transfer mistakes and one that feels dependable from the first screen.

Frequently asked questions

How much does it cost to build a money transfer app?

Cost is driven far more by compliance and partners than by screens: licensing or working under a licensed provider, identity verification, fraud monitoring, payment rails, supported currencies and countries, plus security testing. Native versus cross-platform development and back-office tooling for support and operations add to the total. A regulated payment product needs a longer discovery phase than most apps.

Why do money transfer apps use idempotency keys?

An idempotency key is a unique identifier sent with each transfer request. If the network fails and the app retries, the server recognises the key and processes the transfer only once, preventing accidental duplicate payments.

Should a finance app be native or cross-platform?

Both can work, but native Swift and Kotlin give the most direct access to biometrics, secure storage and platform security features, which is why some teams prefer it for payments. Cross-platform is often cheaper to maintain, so the decision depends on budget, team skills and how demanding your security requirements are.