Remittance app: build your own or license a platform?

What a remittance app actually contains

The screen your customer sees is the small part. Behind it sit:

• Customer registration with identity verification and sanctions screening
• Rates, fees and limits you can change without a developer
• Payment collection by card or open banking
• Payout integrations for each destination country
• A back office: compliance queue, manual review, holds, refunds
• A ledger, reconciliation and regulatory reporting
• iOS and Android apps, app store listings and ongoing updates

Building from scratch

You get exactly what you specify and you own the code. You also take on every integration, every compliance edge case and every app store update, and you need a development team for as long as the business runs. Expect many months before the first live transfer, and a monthly engineering cost that does not stop at launch.

Licensing a platform

You get a working product under your brand, with compliance, collection and payout partners already integrated. Launch is measured in weeks. You pay an onboarding fee and a monthly licence, and your provider maintains the software. The trade-off is that deep changes to how the product works go through the provider's roadmap or are quoted as custom work.

How to decide

• Launching your first corridor, or replacing a legacy portal: license. Speed to market and a known cost matter most.
• An established operator with unusual products and an in-house tech team: building, or licensing with custom modules, can make sense.
• Either way, check who owns the customer data, how you would migrate away, and which integrations are included.

Questions to ask any provider

• Which KYC, payment and payout partners are already integrated?
• Can I set my own rates, fees and limits?
• What does my compliance officer see, and is every decision logged?
• What is included in the monthly fee, and what counts as custom work?
• Can I see it running with my own corridors before I sign?