Home Case StudiesRemittance App

FinTech

Client name and project details are withheld under NDA. Visuals on this page are illustrative, not the client's product.

Web, iOS and Android Apps for an Australian Cross-Border Payments Startup

Industry

FinTech

Role

Technical Partner

Stack

Flutter & PHP API integration

Region

Australia

Mobile Apps
Web Platforms
Integrations

Result

Customer apps on the web, iOS and Android, live with customers sending money from Australia

Key Results

Mobile app for iOS and Android from one Flutter codebase
Separate web app for desktop senders
Live quotes with the rate held while the customer confirms
In-app ID verification during onboarding

Engagement

Several months

Stack Highlights

FlutterPHP API integration

The Challenge

"An Australian remittance startup helps people send money from Australia to family and friends overseas, with payouts to bank accounts, mobile wallets and cash pickup. It had a backend in place and needed customer apps that made sending money feel fast, clear and trustworthy on phones and on the web."

Money apps get no second chances. Every rate, fee and status has to be clear, identity checks have to happen without losing people at sign-up, and accounts have to be protected, all while working with an existing backend rather than replacing it.

Our Approach

We built the mobile app in Flutter from one codebase for iOS and Android, and a separate web app for desktop senders, both integrated with the client's existing PHP API. We built the send flow around what customers need to trust: the rate and fee up front, a quote that holds while they decide, and a clear status for every transfer.

What we built

The customer apps on all three platforms: onboarding with in-app ID verification, recipients and payout method selection, live quotes, pay-in, transfer tracking with push notifications, and account security with one-time codes and session timeouts.

Onboarding with in-app ID document and selfie capture

Recipient management

Payout by bank transfer, mobile wallet or cash pickup

Live exchange rates and fees before confirming

Quotes held for a set time while the customer decides

Pay-in handling with payment status

Transfer tracking with push notifications

One-time codes and automatic session timeouts

How DevForge's apps connect to the client's existing backend, KYC provider and payment partners. Illustrative diagram drawn by DevForge.

Architecture: two front ends, one existing API

The mobile app is built in Flutter from a single codebase for iOS and Android, and a separate web app serves people who prefer to send from a computer. Both talk to the client's existing PHP backend over its REST API, so the apps focus on the customer experience while quotes, transfers and account data stay in one place.

One Flutter codebase for iOS and Android
A separate web app for desktop senders
Integration with the client's existing PHP REST API
Transfer status and push notifications flow back to the app

Money movement: from quote to delivery

Sending money is a sequence the customer has to trust at every step. The apps show the live exchange rate and fee up front, hold the quote for a set time while the customer confirms, handle how they pay in, then track the transfer through each stage until it's delivered.

Live exchange rate and fee shown before the customer commits
Quote held for a set time while the customer confirms
Payout method selection: bank transfer, mobile wallet or cash pickup, with the right details for each method and country
Pay-in handling, including payment status
Transfer tracking through each stage, with push notifications

Compliance by design: verification inside onboarding

Remittance providers in Australia have to verify who their customers are. We built identity verification into onboarding, capturing ID documents and a selfie in the app through the client's KYC provider, so verification happens as part of sign-up.

ID document and selfie capture inside the app
Integrated with the client's KYC provider
Verification as part of the sign-up flow

Security: protecting accounts and sessions

The apps use one-time codes for login and sensitive actions, and end sessions automatically after a period of inactivity, asking customers to authenticate again before sensitive actions.