From choosing your business model to obtaining your license and deploying a compliant payments platform — everything operators need before they go live.
The decision to start a cross-border payments business is rarely impulsive. For most founders, it follows years of watching money move slowly, expensively, and opaquely across borders. In 2024, global remittance flows reached $905 billion according to the World Bank's Migration and Development Brief 40 — a figure that underlines both the scale of the opportunity and the scale of the infrastructure already in place. Starting a remittance business today means entering a market with real regulatory depth, serious compliance obligations, and customers who have options. That is not a reason to hesitate — it is a reason to plan precisely.
In This Article
A cross-border payments business is a licensed financial services operation that facilitates the transfer of funds between senders in one country and recipients in another. It works by accepting value in a source currency, converting it at a defined exchange rate, and delivering it to a beneficiary account or mobile wallet in the destination country — net of fees and FX spread. For regulators and operators alike, what distinguishes a legitimate cross-border payments business from an informal value transfer is the presence of a license, a verifiable audit trail, and a functioning AML/CTF programme.
The term "cross-border payments business" covers several overlapping models. A retail remittance operator sends money for individual consumers — typically migrant workers supporting families abroad. A B2B cross-border settlement provider handles payments between businesses in different jurisdictions. A Remittance-as-a-Service (RaaS) operator provides the underlying infrastructure for other licensed operators to run their own branded products. Each model carries its own regulatory classification, capital requirement, and compliance obligation. Choosing the right model before you apply for a license is not a minor detail — it determines which regulator you answer to, what capital you must hold, and how your transaction volume thresholds are calculated.
What ties all these models together is the core obligation under FATF Recommendation 14: money or value transfer services must be licensed or registered in every country where they operate, subject to AML/CTF controls, and monitored by a competent authority. There is no jurisdiction where operating an unlicensed cross-border payments service is a grey area. The question is not whether you need a license — it is which license, in which market, obtained in which sequence.
The macroeconomic argument for entering cross-border payments has strengthened every year for the past decade. In 2024, remittances to low- and middle-income countries reached $685 billion — growing at 5.8% year-on-year, according to the World Bank's Migration and Development Brief 40 published in June 2024. That single figure surpasses global foreign direct investment flows to those same countries. India alone received $129 billion in inbound remittances during 2024, making it the world's largest remittance recipient by a significant margin.
Figure 1: Key global remittance market figures. Sources: World Bank Migration and Development Brief 40 (June 2024); World Bank Remittance Prices Worldwide Database (Q1 2024, Issue 49).
The cost dimension is just as instructive as the volume figures. The World Bank's Remittance Prices Worldwide database recorded a global average cost of 6.49% to send $200 as of Q1 2024 — more than double the UN SDG 10.c target of 3% by 2030. That gap between where costs are and where they should be is exactly where well-designed, technology-first operators compete and win. Established send markets — USA, UK, Canada, Gulf states, Australia — still rely heavily on legacy players whose pricing reflects bank-correspondent overhead rather than API-driven transaction economics. The operators capturing market share in these corridors are the ones who built for unit economics from day one.
What makes 2026 a particularly practical year to launch is the maturity of white-label infrastructure. The compliance stack that would have taken a team two years and millions of dollars to build from scratch in 2018 is now available as a deployable platform. Licensing remains the genuine barrier — not technology, and certainly not demand.
The launch sequence for a cross-border payments business is not linear in practice — licensing, technology selection, and banking partnership conversations overlap. But there is a logical priority order that minimises wasted spend. Operators who try to build their technology stack before they have a clear view of their target market's licensing requirements often find themselves rebuilding compliance modules once they understand what the regulator actually requires.
Figure 2: Six-step launch framework for a cross-border payments or remittance business. Timelines for each step vary by jurisdiction and business model.
The technology decision every cross-border payments founder faces early in the process is whether to build a proprietary platform or deploy an existing white-label solution. This is not purely a cost question — it is a time, risk, and compliance question simultaneously. Operators who choose to build in-house typically discover that the compliance modules — transaction monitoring logic, sanctions API integrations, Travel Rule data flows — are where timelines and budgets slip most severely, precisely because these components carry regulatory consequences if misconfigured.
Figure 3: Trade-off comparison between deploying a white-label remittance platform and building a proprietary system from scratch.
The build-versus-buy decision also has a secondary effect on the banking partnership timeline. Correspondent banks conducting due diligence on a new money transfer operator want to see a working, documented technology platform before they approve an account. A live, well-documented white-label platform clears that hurdle faster than a roadmap deck and a prototype. Operators running on established infrastructure also find it easier to demonstrate transaction monitoring capability during early-stage compliance reviews — a point that often shortens regulator approval timelines.
Licensing is where most remittance startup timelines break. The gap between when a founder decides to launch and when they can legally process a transaction is almost entirely determined by how quickly they move through the regulatory approval process — and how well prepared their application is when they file it. Every information request from a regulator resets the review clock. In practice, operators applying for a UK FCA Payment Institution authorisation frequently wait 6–12 months regardless of the FCA's stated 3-month target, because applications require amendment after the initial review.
| Market | Regulator | License / Registration Type | Typical Timeline | Approx. First-Year Cost |
|---|---|---|---|---|
| USA | FinCEN + State Regulators | MSB Registration + MTL (49 states) | 3–18 months | $240K–$475K+ |
| United Kingdom | FCA | Payment Institution / SPI Authorisation | 6–12 months | £75K–£150K est. |
| EU / EEA | National Competent Authorities | EMI License (PSD2-compliant) | 6–18 months | €500K–€750K (incl. capital) |
| Australia | AUSTRAC | REMIT Registration | 6–12 weeks | Free reg. + A$5K–A$30K compliance |
| Canada | FINTRAC | MSB Registration | 4–8 weeks | Free + provincial requirements |
| UAE | CBUAE | Payment Service Provider License | 3–6 months | AED 100,000+ |
Figure 4: Licensing requirements, timelines, and estimated first-year costs by major market. Sources: FinCEN MSB Registration Fact Sheet; FCA Authorisation and Registration Fee Schedule; AUSTRAC Enrol or Register guidance; industry advisory estimates.
One operational reality that licensing advisors often understate: the 90-day assessment window used by regulators like AUSTRAC does not run continuously from submission. If the regulator requests additional information — a common occurrence for first-time applicants without compliance counsel — the 90-day clock pauses and resets after the operator responds. An application that should take three months can easily run to six if document requests are not anticipated and prepared in advance. The same dynamic applies in the UK and EU — the stated timeline is the floor, not the ceiling.
AML compliance in cross-border payments is not a checkbox exercise. It is an operational system that runs in parallel with every transaction your business processes, flags anomalies in real time, generates reports that regulators review, and creates the documentary evidence trail that protects your license when an audit occurs. Operators who treat compliance as a one-time setup task typically encounter their first enforcement action within two years of going live — not because they were running illicit funds, but because their monitoring system failed to generate the reports their regulator expected.
Figure 5: The six core AML/CTF compliance pillars required for cross-border payments operators under FATF standards and major jurisdiction-level regulations.
Remittance startup costs are highly variable and depend on three independent factors: the market you are licensing in, the technology approach you choose, and the quality of compliance advisory you engage. Founders who underestimate compliance setup costs consistently — treating licensing fees as the total compliance budget — are the ones who run short of capital during the authorisation process. The application fee is rarely the largest cost. Legal preparation, capital requirements, and the ongoing operational costs of running a compliant AML programme typically exceed the filing fees by a significant margin.
| Cost Category | Estimated Range | Notes |
|---|---|---|
| USA — Multi-State MTL Licensing | $240,000 – $475,000+ | Application fees ($250–$10K per state) + surety bonds ($10K–$1M per state). Nationwide coverage approaches $1M+ over 2 years. |
| UK — FCA Authorisation | £75,000 – £150,000 est. | FCA fee £1,090–£2,140 + legal advisory £25K–£75K + minimum working capital £50K–£125K |
| EU — EMI License (first year) | €500,000 – €750,000 | Application fee €5K–€15K + €350K minimum capital + legal, compliance, and operational setup |
| Australia — AUSTRAC Registration | A$5,000 – A$30,000+ | Registration is free. Costs are in AML/CTF programme setup, transaction monitoring tools, and IFTI reporting infrastructure |
| Technology Platform (White-Label) | $7,499 – $77,999 one-time | PaaS deployment vs. full source code license. Monthly support tiers from $99–$499 |
| AML/Compliance Infrastructure | $5,000 – $50,000/year | Transaction monitoring, sanctions screening, KYC tools — depending on volume and vendor |
| Legal and Compliance Advisory | $20,000 – $100,000 | Ongoing compliance counsel, AML programme documentation, regulatory correspondence |
Figure 6: Estimated startup cost breakdown by category. USA MTL data: Brico.ai MTL Cost Guide (2025). FCA fees: FCA Authorisation and Registration Fee Schedule (2025). EU EMI costs: industry advisory estimates. Australia: AUSTRAC guidance.
One cost that consistently surprises first-time operators is the banking partner requirement. Most correspondent banks conducting AML due diligence on a new money transfer operator expect the operator to demonstrate a minimum operational runway — often 12–18 months of expenses in accessible funds — before they approve an account. This de-risking requirement exists independently of your licensing costs and is not negotiable. Operators who approach banks with a license approval but minimal working capital often find account opening timelines extending significantly.
The technology requirements for a cross-border payments business are more interconnected than most startup checklists suggest. A customer-facing mobile app with a clean UI is the visible layer — but the back-end components that determine whether a transaction completes in seconds or stalls for minutes, whether an AML alert is caught before settlement, and whether a regulator receives an accurate IFTI report are where the real technical complexity sits. Each component below is operationally independent but must integrate cleanly with the others to function as a compliant payment pipeline.
Figure 7: Core technology stack components required to operate a compliant cross-border payments business across major markets.
For operators reviewing how to choose remittance software in 2026, the technology selection criteria should be weighted heavily toward compliance depth, not just UI quality. Regulators do not audit the customer-facing experience — they audit the back-end controls. A platform with a polished mobile app but weak transaction monitoring infrastructure will eventually generate enforcement action regardless of how well the customer experience was received.
RemitSo is a white-label remittance software platform built specifically for licensed money transfer operators — from first-time founders applying for their initial MSB registration to established MTOs migrating from legacy systems. The platform provides the full technology stack described above as a deployable product: customer-facing mobile apps (Flutter) and web portal (Vue.js/React), a core payments engine built on Laravel 12 and PHP 8.3, and a compliance infrastructure layer covering 55+ AML transaction monitoring indicators calibrated for corridor-level risk, real-time sanctions screening against 40,000+ records across eight or more global watchlists with fuzzy matching and alias detection, tiered KYC/eKYC from standard CDD through full Enhanced Due Diligence, Travel Rule compliance infrastructure, and AML case management with a timestamped, audit-ready record trail. The platform is certified ISO/IEC 27001:2022 and PCI-DSS, covering the security and data handling requirements that regulators in the USA, UK, EU, and Australia expect as a baseline.
Operators across the USA, UK, Canada, EU, UAE, and Australia deploy RemitSo as a fully branded, independently licensed product — carrying their own regulatory identity while running on infrastructure that has already passed compliance scrutiny across multiple jurisdictions. The platform's RaaS model also supports operators who need to go live quickly in a specific market while their own license application is in progress, giving them a compliant path to revenue without bypassing regulatory requirements. Regardless of which market you are entering first, the timeline from deployment to live transactions is weeks — not the 18–36 months that building a proprietary stack consistently requires. Explore RemitSo's full platform features or compare your options with the remittance software buyer's guide for 2026.
RemitSo gives licensed operators a complete, compliant platform — deployed in weeks, not years.
A cross-border payments business is a licensed financial services operation that facilitates the transfer of value from a sender in one country to a recipient in another, converting currencies and delivering funds via bank transfer, mobile wallet, or cash payout. It operates under a regulatory license — such as a Money Transmitter License in the USA, FCA authorisation in the UK, or AUSTRAC registration in Australia — and is required to maintain AML and CTF controls throughout every transaction it processes. The distinction between a compliant cross-border payments business and an unlicensed money transfer operation is not merely technical — operating without a license in any jurisdiction where you have customers is a criminal offence in most countries. The business model covers retail remittance (consumer-to-consumer), B2B cross-border settlement, and Remittance-as-a-Service (providing infrastructure for other operators).
The cost to start a remittance business depends primarily on your target operating market. In the USA, multi-state Money Transmitter Licensing can cost between $240,000 and $475,000 in application fees and surety bonds alone, with nationwide coverage approaching $1 million over two years (source: Brico.ai MTL Cost Guide, 2025). UK FCA authorisation adds legal and advisory costs that typically bring total first-year spend to £75,000–£150,000. An EU EMI license carries a minimum capital requirement of €350,000 plus application and operational costs, bringing first-year totals to €500,000–€750,000. Australia is the most accessible entry point — AUSTRAC registration is free, with compliance setup costs of A$5,000–A$30,000. Technology platform costs for a white-label deployment range from $7,499 to $77,999 one-time, significantly below the 18–24 month build cost of a proprietary system.
The license you need to start a money transfer business depends on where you operate and where your customers are located. In the USA, you need federal MSB registration with FinCEN plus a Money Transmitter License (MTL) from each state where you have customers — 49 states require an MTL. In the UK, you need FCA authorisation as a Payment Institution or Small Payment Institution. In the EU, an Electronic Money Institution (EMI) license from a national competent authority provides passporting rights across EU/EEA member states. In Australia, AUSTRAC registration is required as a Remittance Service Provider. In Canada, federal MSB registration with FINTRAC is mandatory. Most jurisdictions apply FATF Recommendation 14, which requires all money or value transfer services to be licensed or registered — operating without the relevant authorisation is a criminal offence in virtually every regulated market.
Money transmitter license timelines range from 4–8 weeks (Canada FINTRAC, Australia AUSTRAC for straightforward applications) to 3–18 months (USA state MTLs) and 6–18 months (UK FCA, EU EMI). A critical operational reality: regulatory review clocks reset after each information request from the regulator. An application that should take three months can run to six or nine if document requests are not anticipated and prepared in advance. First-time applicants without compliance counsel typically experience the longest timelines because they respond to information requests reactively rather than proactively. In the USA, pursuing licences in all 49 states requiring MTLs simultaneously is not realistic for most startups — experienced operators typically sequence state applications by transaction volume priority, starting with the highest-volume states first.
The Travel Rule — formally FATF Recommendation 16 — requires that originator and beneficiary information travel with every cross-border wire transfer above the applicable threshold throughout the entire payment chain. Under FATF guidance, the threshold is EUR/USD 1,000; the EU implemented this requirement via its Transfer of Funds Regulation effective December 30, 2024. The USA applies a higher threshold of $3,000 under current FinCEN rules. Switzerland applies Travel Rule requirements to all transactions regardless of amount. FATF published an updated explanatory note for Revised Recommendation 16 in June 2025 clarifying data field requirements across different payment rail types. For cross-border payments operators, Travel Rule compliance requires your technology platform to capture, transmit, and store full originator and beneficiary data fields — name, account number, and address or other identifier — for every qualifying transaction. Non-compliance can result in license suspension in the EU and significant civil penalties in the USA.
A remittance startup needs seven core technology components: a customer-facing front end (mobile app and web portal), a core payments engine for transaction routing and FX management, a KYC/eKYC identity verification system, an AML transaction monitoring engine with corridor-calibrated thresholds, real-time sanctions screening against global watchlists, payout network integrations for each target receive corridor, and a back-office compliance and reporting system with case management. These components must integrate cleanly into a single, auditable pipeline — not function as independent tools with manual handoffs between them. The compliance-facing components (monitoring, screening, reporting) are where regulators focus during examination, and gaps in their integration are the most common cause of enforcement action against early-stage operators.
Most remittance startups lose banking relationships early because they pass the initial due diligence review but fail to maintain the compliance documentation standard their bank expects on an ongoing basis. Correspondent banks conduct periodic reviews of money transfer operators — typically annually but sometimes triggered by transaction volume spikes or adverse media coverage — and operators who cannot produce current AML programme documentation, up-to-date risk assessments, and evidence of functioning transaction monitoring are de-banked regardless of whether any actual illicit transactions occurred. A second common cause is transaction volume growth into corridors the bank did not specifically approve during the original onboarding. Entering a new high-risk corridor without notifying your correspondent bank is treated as a material change in risk profile — and banks routinely exit the relationship rather than conduct a new due diligence cycle on a small operator. Maintaining banking relationships requires treating your bank as an ongoing compliance audience, not a one-time approval process.
For most new operators, a white-label remittance platform is the correct starting point — and the economics are clear. Building a proprietary cross-border payments platform from scratch typically requires 18–36 months and a full engineering team before the first live transaction. A white-label platform from a vendor with existing corridor integrations and pre-built compliance modules can be deployed in weeks. The compliance depth question is particularly important: regulators in every major market expect your AML programme, transaction monitoring system, and KYC processes to be documented and operational before your license is approved, not assembled after. A white-label platform with a verifiable compliance track record across multiple regulated markets gives first-time applicants a credible compliance answer during the licensing process. The correct question to ask any white-label vendor is not just "how fast can we go live?" — it is "what documentation can you provide to support our regulatory application?"
