How To Start a Money Transfer Business in 2026

Starting a money transfer business in 2026 can still be commercially attractive, but it is no longer a business that should be approached as a simple website, mobile application, or API integration. A serious money transfer company is a regulated operating system. It combines licensing, banking, safeguarding, liquidity, foreign exchange, compliance, technology, customer support, fraud controls, partner management, and continuous regulatory reporting.

The opportunity remains substantial. The World Bank estimated that officially recorded remittances to low- and middle-income countries reached approximately USD 685 billion in 2024, while the latest Remittance Prices Worldwide data available at the time of writing placed the global average cost of sending a remittance at 6.36% of the amount sent.^[1][2] The market is large, recurring, and socially important. It is also fragmented, highly regulated, operationally unforgiving, and increasingly competitive.

The central lesson is straightforward:

Do not start by selecting software. Start by defining the regulated activity, the corridor, the customer, the transaction, and the flow of funds.

This guide explains how to do that. It is written for entrepreneurs, fintech founders, existing money services businesses, payment companies, foreign exchange operators, banks, technology providers, and established businesses that want to enter remittances or cross-border payments.

Executive Summary

A money transfer business succeeds when six elements are designed together:

1. A commercially defensible corridor with identifiable customers, recurring demand, and sufficient margin.

2. A lawful market-entry structure: referral, white-label, sponsored or agent model, direct licensing, or acquisition subject to regulatory approval.

3. Banking and settlement access that matches the actual flow of funds.

4. A risk-based compliance program embedded into onboarding, transaction processing, monitoring, reporting, and partner oversight.

5. Auditable technology with a reliable ledger, reconciliation, transaction monitoring, reporting, and security architecture.

6. Enough capital and runway to survive licensing, integration, prefunding, operational losses, and a slower-than-expected launch.

Most failed payment ventures do not fail because the founders cannot build an application. They fail because the founders misunderstand licensing, cannot obtain or retain banking, select the wrong principal license holder, underestimate liquidity requirements, cannot reconcile funds, or discover that their transaction economics do not work after all partner charges are included.

A prudent founder should therefore answer the following questions before spending materially on technology:

• Who is sending the money?

• Who is receiving it?

• Why is the payment being made?

• In which countries and states are the parties located?

• Who receives customer funds first?

• Which legal entity holds or controls those funds?

• Which licensed entity is responsible at each stage?

• Which bank accounts are used?

• How is foreign exchange executed?

• How is the destination payout funded?

• Which party owns the customer relationship and data?

• What is the gross revenue and net contribution per transaction?

• What happens when a transaction fails, is recalled, is fraudulent, or is sanctioned?

Until those questions are answered, the business is not properly designed.

1. Define the Business Before Choosing a License

“Money transfer business” is an umbrella term. It may describe a consumer remittance service, a business payments company, a wallet, a foreign exchange service, a payout network, a stablecoin settlement platform, a payment facilitator, an agent network, or a combination of several activities.

Those businesses may appear similar to a customer, but they can have very different licensing, capital, safeguarding, compliance, and banking requirements.

1.1 Identify the precise product

Begin by choosing the actual service you intend to provide. Common models include:

• Person-to-person international remittances

• Domestic money transmission

• Business-to-business cross-border payments

• Freelancer, payroll, or contractor payouts

• Marketplace seller payouts

• Bill payment and airtime top-up

• Cash-in and cash-out through agents

• Bank-account-to-bank-account transfers

• Card-funded remittances

• Wallet or stored-value accounts

• Prepaid cards

• Foreign exchange and treasury services

• Stablecoin-based wholesale settlement

• Payment collection and disbursement for merchants

• White-label remittance infrastructure for other brands

Do not combine all of them in the first launch. Each additional customer type, funding method, payout method, corridor, currency, and regulated activity creates another layer of risk and operational complexity.

A founder who says, “We will offer P2P, B2B, wallets, cards, crypto, cash agents, bill payment, and merchant acquiring across ten countries,” has not designed a comprehensive platform. The founder has created a regulatory and operational scope that is unlikely to be executable by an early-stage team.

1.2 Define the transaction in one sentence

A useful discipline is to describe the first transaction in one sentence:

A consumer in Canada uses a bank transfer to send CAD 500 to a beneficiary’s bank account in Pakistan, with funds delivered in PKR within one business day.

That sentence identifies:

• The sender type

• The origin country

• The funding method

• The transaction amount

• The destination country

• The payout method

• The payout currency

• The promised delivery time

It also creates the foundation for licensing analysis, customer disclosures, partner selection, compliance rules, technology requirements, and unit economics.

1.3 Separate the customer proposition from the settlement rail

The customer proposition is what the user experiences. The settlement rail is how the regulated entities move value behind the scenes.

For example, the customer may see:

• CAD collected from a Canadian bank account

• A guaranteed PKR amount

• Delivery to a beneficiary’s bank account

Behind the scenes, the licensed providers may use:

• Domestic electronic funds transfer in Canada

• A safeguarded collection account

• A wholesale FX provider

• Prefunded liquidity in Pakistan

• A stablecoin for intercompany or partner settlement

• A local bank or payout network for final delivery

The customer does not necessarily need to see or interact with every internal rail. What matters is that each leg is lawful, contractually documented, operationally controlled, and fully reconcilable.

1.4 Decide whether the business is P2P, B2B, or both

P2P remittances and B2B cross-border payments are not interchangeable.

P2P remittances generally involve smaller values, higher transaction frequency, retail consumer disclosures, chargeback exposure, community marketing, and beneficiary support.

B2B payments usually involve larger values, more extensive KYB and beneficial ownership checks, invoice and trade-document review, source-of-funds analysis, sanctions risk, recurring corporate relationships, and more complex approval limits.

A company may eventually serve both, but the onboarding, monitoring, contracts, risk appetite, pricing, and support processes should be separately designed.

2. Select the Corridor and Validate the Market

A corridor is not merely a pair of countries. It is a complete commercial and operational route involving customer behavior, funding methods, foreign exchange, settlement, payout infrastructure, regulation, liquidity, and local trust.

2.1 Start with one corridor

A strong first corridor usually has several of the following characteristics:

• A meaningful diaspora or business relationship between the origin and destination markets

• Recurring payment demand

• Poor service, high friction, or weak coverage from incumbents

• A community or industry segment the founders can reach directly

• Reliable origin-side funding methods

• Reliable destination-side payout methods

• Sufficient foreign exchange liquidity

• A credible licensed partner on each side

• A pricing model that remains profitable after all costs

• A manageable fraud and sanctions profile

The best corridor is not necessarily the largest. The largest corridors attract the strongest incumbents and the highest advertising costs. A smaller corridor may be more commercially attractive if the founders have trust, distribution, language ability, or local operational knowledge that larger competitors cannot easily replicate.

2.2 Research actual customer behavior

Do not rely only on high-level remittance statistics. Interview customers and observe how they currently send money.

For the origin market, determine:

• Whether customers prefer bank transfer, debit card, cash, open banking, or wallet funding

• The average send amount

• The frequency of transfers

• The days and times when transfers peak

• Whether customers compare the fee, the exchange rate, or the final amount received

• How quickly they expect delivery

• What causes them to switch providers

• Whether they trust a new digital-only brand

• Which languages and support channels they expect

For the destination market, determine:

• Whether beneficiaries prefer bank deposits, mobile wallets, cash pickup, or home delivery

• Whether beneficiary names and identity records are consistent

• How often bank or wallet accounts reject payments

• Whether local payout systems operate on weekends and holidays

• How cash availability varies by location

• Whether local currency liquidity is reliable

• Which documents are needed for higher-value or business payments

2.3 Conduct a corridor scorecard

Score each proposed corridor against a consistent framework.

A corridor that scores highly on customer demand but poorly on banking, liquidity, or licensing is not launch-ready.

2.4 Identify the commercial wedge

A new entrant needs a specific reason to exist. “Cheaper, faster, and easier” is not sufficiently differentiated.

A defensible wedge may be:

• A neglected diaspora community

• A difficult payout geography

• A specialized B2B vertical

• Better local-language onboarding

• Superior cash or mobile-wallet reach

• Transparent delivery guarantees

• Stronger beneficiary support

• Integrated bill payment or school-fee payment

• A community distribution network

• Faster exception handling

• Better compliance for a customer segment that banks routinely reject

The company should be able to explain why customers will switch and why a larger competitor cannot immediately copy the advantage.

3. Choose the Correct Market-Entry Model

There is no single correct route into the money transfer industry. The appropriate model depends on the founder’s capital, timeline, target jurisdiction, desired control, product scope, and willingness to assume regulatory responsibility.

3.1 The principal market-entry models

3.2 An API is not a license

One of the most persistent misconceptions in payments is that API access creates regulatory coverage. It does not.

An API is a technical interface. Regulatory coverage comes from the legal and contractual operating model.

Before relying on an API or white-label provider, determine:

• Which entity is the regulated service provider to the customer

• Whose name appears in the customer agreement

• Who receives and safeguards the funds

• Who performs KYC, sanctions screening, and transaction monitoring

• Who submits regulatory reports

• Who approves or rejects transactions

• Who handles complaints, refunds, recalls, and errors

• Whether your company is appointed as an agent, delegate, distributor, program manager, or mere marketing partner

• Whether the provider’s permissions cover the product, jurisdiction, funding method, payout method, and customer type

• Whether your company can appoint additional vendors or counterparties

• Who owns the customer data and whether it can be exported

Some managed programs allow the brand partner to perform meaningful operational functions. Others permit only marketing, customer acquisition, and first-line support. The contract, regulatory appointment, flow of funds, and operating procedures—not the sales presentation—determine the answer.

3.3 The agent or authorized delegate model

Under an agent, authorized delegate, authorized agent, or similar model, a licensed principal appoints another company to perform approved activities on its behalf. Terminology and legal rights vary by jurisdiction.

A properly structured agent model can allow a founder to:

• Launch before obtaining an independent license

• Operate within the principal’s permitted geography and product scope

• Build transaction history

• Test customer demand and corridor economics

• Develop operational experience

• Demonstrate performance to banks, regulators, and investors

However, the agent is not an independent license holder. The principal remains responsible for the regulated program and will impose controls over products, geographies, vendors, compliance, customer communications, technology, settlement, and risk appetite.

A useful selection rule is to choose a principal whose existing program already matches most of the intended business. A principal that covers 70% to 85% of the required product and corridor is often more useful than a nominally flexible principal that has never operated the relevant model.

The founder should expect to compromise on at least some of the following:

• Funding methods

• Payout methods

• Supported countries

• Customer categories

• Transaction limits

• Prohibited industries

• Technology providers

• Pricing

• Settlement timing

• Branding and disclosures

3.4 Applying for your own license

Direct licensing provides the greatest strategic control, but it also creates the greatest responsibility.

A directly licensed company must be prepared to manage:

• Regulatory capital and own-funds requirements

• Surety bonds or security deposits where applicable

• Governance and fit-and-proper standards

• A documented compliance program

• A qualified compliance officer or MLRO

• Safeguarding or permissible-investment obligations

• Independent audits and testing

• Regulatory reporting

• Cybersecurity and operational resilience

• Complaint handling and consumer protection

• Agent oversight

• Books, records, and examinations

• Banking, treasury, and reconciliation

The correct time to pursue an independent license is when the company has enough capital, a credible management team, a defensible business model, a documented operating plan, and sufficient runway to survive a lengthy application and implementation process.

3.5 Combining sponsorship and direct licensing

For many founders, the most practical strategy is sequential:

1. Design the product and corridor.

2. Launch under a suitable licensed principal.

3. Validate customer demand, operational performance, and unit economics.

4. Apply for an independent license in parallel.

5. Migrate customers and operations only after legal, contractual, privacy, and regulatory requirements are satisfied.

Customer migration is not automatic. Contracts, privacy notices, consent requirements, data-transfer restrictions, safeguarding arrangements, and regulator notifications must be reviewed before moving clients from a principal’s program to a newly licensed entity.

3.6 Buying a licensed company is not a shortcut

Acquiring a licensed entity may save time in selected cases, but it is not equivalent to buying a shelf company.

A change of ownership or control normally requires regulatory review. Regulators may examine:

• The buyer’s source of funds

• Owners and controllers

• Management fitness and experience

• The revised business model

• New products and geographies

• Capital and liquidity

• Compliance history

• Outstanding examinations or remediation

• Banking relationships

• Technology migration

• Customer protection arrangements

A poorly maintained license can be a liability rather than an asset. The acquisition agreement should be conditional on regulatory approval and detailed due diligence.

4. Understand Licensing by Jurisdiction

Licensing analysis must be performed for the exact activity and customer journey. The following overview is a strategic introduction, not a substitute for jurisdiction-specific legal advice.

4.1 United States

The United States has a dual federal and state framework.

At the federal level, businesses that meet the definition of a money services business may need to register with the Financial Crimes Enforcement Network, or FinCEN, and comply with the Bank Secrecy Act. FinCEN registration is not a nationwide money transmitter license.^[3]

At the state level, money transmission is generally licensed and supervised by state regulators. Applications are commonly processed through the Nationwide Multistate Licensing System, or NMLS, but NMLS is an application and reporting platform—not a federal license.^[4]

A U.S. launch may involve:

• FinCEN MSB registration

• State money transmitter licenses

• Surety bonds

• Minimum net worth or tangible net worth requirements

• Permissible investment requirements

• Background checks and fingerprints

• Audited financial statements

• Business plans and flow-of-funds diagrams

• AML policies and independent testing

• Cybersecurity documentation

• State call reports and examinations

• Consumer disclosure and complaint obligations

The exact state analysis depends on where customers are located, how money is received and transmitted, whether the company acts as an agent of a licensed entity, and whether an exemption applies.

Montana is not a nationwide shortcut

As of this 2026 update, the Montana Division of Banking and Financial Institutions states that Montana does not regulate money transmitters.^[5] That does not create a “Montana money transmitter license,” nor does it authorize a Montana company to transmit money in other states.

A Montana entity, FinCEN registration, or a private certificate cannot substitute for licenses required elsewhere.

State modernization does not create one national license

Many states have adopted versions of the Conference of State Bank Supervisors’ Money Transmission Modernization Act. This improves consistency in areas such as definitions, net worth, permissible investments, examinations, and change-of-control standards. It does not eliminate state licensing or create a single U.S. authorization.

U.S. consumer remittance rules

A company sending consumer remittances from the United States may also be subject to federal consumer-protection requirements under Regulation E, including disclosures, cancellation rights, error resolution, and receipt requirements for covered transfers.^[6]

4.2 Canada

A common misconception is that a Canadian money transfer company receives a “FINTRAC license.” It does not.

A business that meets the definition of a Canadian money services business or foreign money services business generally must register with FINTRAC before operating and must comply with Canada’s AML and terrorist financing requirements. FINTRAC expressly states that registration is not a license, certificate, endorsement, or approval.^[7]

Depending on the activities, the same company may also be required to register as a payment service provider with the Bank of Canada under the Retail Payment Activities Act, or RPAA. The Bank of Canada also states that RPAA registration is not a license.^[8]

A Canadian payment business may therefore have two separate federal regimes:

1. FINTRAC registration and AML obligations, and

2. Bank of Canada RPAA registration and operational-risk, safeguarding, incident, and reporting obligations, if the business is in scope.

Neither registration should be marketed as a government endorsement.

Canada can be an attractive jurisdiction for certain businesses, but the apparent simplicity of registration should not be confused with operational readiness. Banking, compliance, governance, RPAA implementation, privacy, safeguarding, and cross-border counterparty acceptance remain substantial workstreams.

4.3 United Kingdom

The United Kingdom distinguishes between payment institutions and electronic money institutions.

A payment institution provides regulated payment services. An electronic money institution can issue electronic money and provide payment services. Whether a company needs PI or EMI authorization depends on what the product legally does—not whether the marketing language uses the word “wallet.”

Under the current framework, initial capital for an authorized payment institution depends on the payment services provided and may be EUR 20,000, EUR 50,000, or EUR 125,000. An authorized electronic money institution generally requires EUR 350,000 of initial capital, together with ongoing own-funds requirements.^[9]

The statutory minimum is not the total launch budget. Applicants also need credible funding for:

• Personnel

• Compliance

• Technology

• Safeguarding

• Professional advisers

• Audit

• Insurance

• Premises and substance

• Banking

• Operational runway

The FCA introduced strengthened safeguarding requirements for payment and e-money firms effective from May 2026. Applicants and existing firms must account for the revised safeguarding, reconciliation, reporting, audit, and resolution-pack expectations.^[10]

A UK authorization does not provide EU passporting rights after Brexit. A company seeking both UK and EEA coverage must design separate authorization and operating strategies.

4.4 European Union and European Economic Area

Under the current EU framework, payment institutions are authorized under PSD2 and electronic money institutions under the Electronic Money Directive. Initial capital for payment institutions depends on the services provided, while electronic money institutions generally require EUR 350,000.

An authorization from an EU member state may support passporting across the EEA after the required notifications and host-state processes are completed. Passporting does not eliminate the need for local consumer, AML, tax, employment, data-protection, and operational analysis.

The EU’s PSD3 and Payment Services Regulation package reached provisional political agreement and was close to adoption in 2026. The new framework is expected to further harmonize authorization, supervision, consumer protection, fraud controls, and the treatment of payment and e-money services. Applicants should verify which regime applies at the time of filing and how transitional rules affect existing authorizations.^[11]

Jurisdiction selection within the EU should not be based only on the lowest quoted professional fee. Consider:

• Regulatory credibility

• Application quality expectations

• Management substance

• Local director requirements

• Availability of safeguarding banks

• Audit and reporting capacity

• Tax and employment implications

• Regulator experience with the intended product

• Passporting strategy

• Long-term counterparty acceptance

4.5 Crypto-asset authorization in the EU

MiCA created a harmonized authorization framework for crypto-asset service providers. The maximum EU transitional period for legacy virtual asset service providers ended on 1 July 2026. A business serving EU clients should not assume that an old national VASP registration remains sufficient.^[12]

A money transfer business using stablecoins may need both payment-related permissions and crypto-asset permissions, depending on custody, exchange, transfer, execution, and customer-facing activities.

4.6 Other jurisdictions

Jurisdictions such as Australia, Singapore, Hong Kong, the United Arab Emirates, Saudi Arabia, Japan, Brazil, South Africa, and others have their own payment, remittance, stored-value, foreign exchange, and digital-asset regimes.

The correct jurisdiction is not necessarily the cheapest or fastest. It is the one that supports:

• The actual product

• The required customer type

• The target corridors

• Acceptable banking

• Credible counterparties

• Sustainable regulatory compliance

• The company’s management substance

• The company’s long-term expansion plan

An inexpensive offshore license that banks and payment partners refuse to accept may have little commercial value.

5. Estimate the Real Capital Requirement

Founders often ask, “What is the minimum capital?” That is the wrong financial question.

The correct question is:

How much cash does the company need to become authorized, build the operating system, launch the corridor, fund settlement, absorb losses, and survive until recurring revenue covers fixed costs?

5.1 Separate five different capital requirements

1. Regulatory capital

This is the minimum capital, net worth, or own funds required by law or regulation. It may vary by license type, transaction volume, customer funds outstanding, or state.

2. Bonding, security, or collateral

U.S. states and other jurisdictions may require surety bonds, security deposits, guarantees, or other collateral. The face value of a bond is not necessarily the cash premium, but startups may be required to post substantial collateral.

3. Safeguarding and permissible investments

Customer funds may need to be held in segregated or safeguarding accounts or backed by eligible investments. These funds are not available to pay the company’s ordinary operating expenses.

4. Settlement liquidity and prefunding

Destination partners often require prefunding. Card-funded transactions may settle later than payouts. Foreign exchange providers may require margin. Refunds, recalls, chargebacks, and payout failures create timing mismatches.

5. Operating runway

The company must pay staff, advisers, software providers, auditors, banks, insurers, cloud providers, and partners while the license is pending and during the early launch period.

5.2 Use a complete funding formula

A practical planning formula is:

Total funding requirement =
Regulatory capital
+ bond or security collateral
+ application and professional fees
+ compliance and governance build
+ technology and integration build
+ banking and partner deposits
+ safeguarding and settlement liquidity
+ 12–18 months of operating expenses
+ launch marketing
+ contingency reserve

The statutory capital number may be one of the smaller components.

5.3 Illustrative planning envelopes

The following are commercial planning ranges, not legal requirements or quotations:

The range can be materially higher for cash networks, high-risk corridors, card-heavy acquisition, crypto components, large prefunding obligations, or multiple regulated entities.

5.4 What a larger raise should buy

A larger funding round should not merely produce more software features. It should buy structural advantages:

• Experienced compliance and operations leadership

• Stronger banking and treasury relationships

• More settlement liquidity

• Better redundancy

• Faster integrations

• Independent audits and testing

• Experienced sales personnel with real industry relationships

• Existing transactional traffic or contractual distribution

• More time to obtain licenses without accepting poor partner terms

A senior industry salesperson with established counterparties may create more value than an oversized engineering team building features customers did not request.

5.5 Build the financial model before applying

The model should include at least:

• Monthly transactions

• Average transaction size

• Gross send volume

• Fee revenue

• FX revenue

• Partner revenue share

• Collection costs

• Payout costs

• Banking costs

• Compliance costs

• Fraud and chargeback losses

• Customer support costs

• Marketing and CAC

• Headcount

• Regulatory and audit expenses

• Prefunding and working capital

• Capital requirements

• Base, downside, and severe-downside scenarios

The model should show how the company survives if approval takes six months longer than expected and transaction volume reaches only half the forecast.

6. Build the Business and Regulatory Plan

A regulator, bank, principal license holder, investor, and payout partner will each ask different questions, but they all need the same core operating story.

6.1 The two-page internal brief

Before producing a long business plan, write a two-page internal brief in plain language:

• Who the founders are

• What problem is being solved

• Who the customers are

• The first corridor

• The first transaction type

• The funding and payout methods

• The proposed legal entities

• The proposed licensing model

• The expected monthly volume

• The expected revenue and margin

• The current banking and partner status

• The available capital

• The expected launch date

This document should be candid, not promotional. It should expose weaknesses early.

6.2 The full business plan

A credible regulatory and operational business plan normally includes:

1. Executive summary

2. Ownership and group structure

3. Management and governance

4. Product and service description

5. Customer segments

6. Jurisdictions and corridors

7. Market and competitor analysis

8. Distribution and marketing plan

9. Flow of funds

10. Transaction sets

11. Revenue model

12. Financial projections

13. Banking and safeguarding

14. Technology architecture

15. Outsourcing and vendor management

16. Compliance program

17. Fraud and operational risk

18. Customer support and complaints

19. Business continuity and disaster recovery

20. Information security and privacy

21. Regulatory reporting

22. Wind-down plan

The business plan, AML manual, financial model, technology architecture, and contracts must tell the same story. Contradictions between documents are a common reason applications stall.

6.3 Define the risk appetite

The company should document what it will and will not do.

Examples include:

• Permitted and prohibited countries

• Permitted customer types

• High-risk industries

• Maximum transaction values

• Daily and monthly limits

• Cash acceptance

• Crypto exposure

• Third-party funding

• Business payments without invoices

• Politically exposed persons

• Sanctioned or high-risk jurisdictions

• Agent activity

• Non-face-to-face onboarding

A business with no defined exclusions does not have a risk appetite. It has an uncontrolled sales strategy.

6.4 Prepare the regulator and bank data room

Maintain a structured data room containing:

• Corporate documents

• Ownership chart

• Source-of-funds evidence

• Resumes and background documents

• Business plan

• Financial model

• Policies and procedures

• Enterprise risk assessment

• Flow-of-funds diagrams

• Transaction sets

• Product screenshots

• Technology architecture

• Vendor due diligence

• Contracts and term sheets

• Banking correspondence

• Insurance

• Audit and testing plans

• Board minutes and governance records

The same data room can support regulators, banks, investors, principals, and counterparties.

7. Design the Flow of Funds and Transaction Sets

The flow of funds is the most important diagram in the business. It shows who receives, holds, converts, transmits, safeguards, settles, and pays out money.

A product cannot be licensed, banked, or monitored correctly if the flow of funds is unclear.

7.1 A basic cross-border remittance flow

[Sender]
   |
   | 1. Funds transfer instruction and customer funds
   v
[Origin Licensed Provider]
   |
   | 2. Collection, KYC, screening, ledger posting
   v
[Origin Bank / Safeguarding Account]
   |
   | 3. Settlement and FX instruction
   v
[FX / Liquidity / Settlement Partner]
   |
   | 4. Destination liquidity or settlement
   v
[Destination Licensed Payout Partner]
   |
   | 5. Bank, wallet, or cash payout
   v
[Beneficiary]

This diagram is incomplete unless it also identifies:

• The legal entity at each box

• The applicable license or exemption

• The bank account owner

• Whether funds are customer funds or corporate funds

• The point at which fees are deducted

• The point at which FX is executed

• The data transmitted with the payment

• The party responsible for screening at each stage

• The settlement timing

• The reconciliation process

• The refund and return path

7.2 Separate four flows

A mature architecture distinguishes four parallel flows:

1. Money flow – where value moves

2. Data flow – where customer and transaction information moves

3. Instruction flow – who tells each party what to do

4. Accounting flow – how each party records the transaction

A transaction may appear to settle successfully while the ledger, bank statement, and payout report disagree. That is an operational loss waiting to happen.

7.3 Build transaction sets

A transaction set is a worked example showing every step of a transaction from initiation to completion.

Prepare transaction sets for:

• Successful transaction

• Failed customer funding

• Failed payout

• Refund before settlement

• Refund after settlement

• Chargeback

• Duplicate payment

• Sanctions alert

• Suspicious activity escalation

• Incorrect beneficiary details

• Partial payout

• FX rate expiration

• Customer complaint

Each transaction set should include:

• Amount sent

• Fee

• FX rate

• Amount received

• Timestamps

• Ledger entries

• Bank movements

• Partner movements

• Compliance checks

• Customer notifications

• Responsible staff role

• Reconciliation outcome

7.4 Avoid opaque and nested payment chains

A chain of intermediaries is not automatically unlawful, but every party must have a legitimate role, appropriate authorization, clear contracts, required customer and transaction data, and an auditable flow.

The danger appears when:

• One intermediary conceals another

• The final payout partner is not disclosed

• Customer funds are passed through unrelated accounts

• Transaction data is stripped or summarized incorrectly

• A company provides settlement services beyond its permissions

• The origin provider cannot reconstruct the complete path

• The destination regulator sees an unauthorized payout route

Do not use the term “firewall” as a substitute for legal analysis. A corporate or contractual layer does not isolate regulatory responsibility if the transaction remains opaque or improperly structured.

7.5 Trace the transaction from origin to final beneficiary

The compliance obligation does not stop merely because funds leave one provider’s platform. The business should understand the origin, intermediate parties, and final termination point.

For every corridor, the company should be able to answer:

• Who is the originator?

• Who is the beneficiary?

• What is the purpose?

• Which licensed entities participate?

• Which accounts are used?

• Where is the transaction screened?

• Where is the transaction monitored?

• Where does it finally terminate?

• Can the full audit trail be reconstructed?

8. Secure Banking, Safeguarding, Treasury, and Liquidity

A license without banking is not an operating business. Banking access should be treated as a parallel workstream from the beginning, not as a final task after licensing.

8.1 Why banks reject money transfer companies

Banks commonly view money transfer and remittance businesses as higher risk because they may involve:

• Large numbers of third-party transactions

• Cross-border activity

• High transaction velocity

• Cash funding or payout

• High-risk jurisdictions

• Fraud and chargebacks

• Sanctions exposure

• Complex agents and counterparties

• Crypto or stablecoins

• Rapid growth

• Weak reconciliation

• Inadequate compliance staffing

A bank’s concern is not solved by showing a license alone. The bank needs to understand the complete operating model and determine whether it can monitor the account safely.

8.2 Prepare a bank-ready package

The banking package should include:

• License and registration status

• Ownership and management

• Business plan

• Flow of funds

• Transaction sets

• Customer types

• Corridors

• Funding and payout methods

• Expected monthly volume

• Average and maximum transaction values

• AML and sanctions framework

• Transaction monitoring approach

• Source-of-funds controls

• Partner list

• Financial statements

• Safeguarding arrangements

• Reconciliation process

• Complaint and fraud controls

The company should be able to explain every expected bank-statement entry.

8.3 Distinguish operating accounts from customer-funds accounts

A regulated payment company may require several account types:

• Corporate operating account

• Customer collection account

• Safeguarding or segregated account

• Settlement account

• Prefunding account

• Chargeback or reserve account

• Foreign currency account

• Agent settlement account

Do not commingle customer funds with ordinary operating money unless the applicable law and program structure expressly permit it.

8.4 Design liquidity by corridor

Liquidity is often required before customer volume arrives.

For each corridor, calculate:

• Daily send volume

• Peak-day volume

• Settlement delay

• Payout speed

• Prefunding requirement

• Weekend and holiday exposure

• FX margin requirements

• Refunds and returns

• Chargeback exposure

• Partner reserve requirements

• Emergency liquidity

A payout partner may require three to seven days of expected volume to remain prefunded. A fast-growing company can therefore become more cash-constrained as volume increases.

8.5 Use redundancy carefully

The company should avoid dependence on a single bank, payout partner, FX provider, or cloud region. However, redundancy must be transparent and approved. Secretly routing transactions through an undisclosed backup account or intermediary can create a more serious compliance problem than the outage it was intended to solve.

8.6 Reconcile every day

At minimum, daily reconciliation should compare:

• Customer ledger

• Bank statements

• Processor reports

• FX trades

• Settlement reports

• Payout reports

• Refunds

• Chargebacks

• Fees

• Suspense items

Unreconciled balances should be aged, assigned, investigated, and escalated. A payment company that cannot reconcile does not know whether it is profitable, solvent, or holding the correct customer funds.

9. Build the AML, Sanctions, and Fraud Program

Compliance is not a document prepared for the regulator and stored on a shared drive. It is the operating logic that determines who may use the service, which transactions are allowed, which transactions require review, and which activity must be reported.

9.1 Core components of the compliance program

A credible program generally includes:

• Board and senior-management oversight

• A qualified compliance officer or MLRO

• Enterprise-wide risk assessment

• Customer identification and verification

• Business verification and beneficial ownership

• Customer risk rating

• Enhanced due diligence

• Sanctions and PEP screening

• Transaction monitoring

• Fraud controls

• Suspicious activity investigation and reporting

• Recordkeeping

• Regulatory reporting

• Agent and partner oversight

• Training

• Independent testing

• Issue management and remediation

9.2 Build a risk-based customer program

Customer onboarding should be proportionate to risk.

For consumers, controls may include:

• Identity verification

• Address and contact validation

• Device and IP analysis

• Sanctions and PEP screening

• Funding-source checks

• Transaction limits

• Occupation and purpose questions

• Enhanced review for higher-risk activity

For businesses, controls may include:

• Legal existence

• Registered address

• Directors

• Ultimate beneficial owners

• Ownership percentages

• Business model

• Expected activity

• Source of funds and wealth where appropriate

• Bank-account verification

• Licenses and registrations

• Adverse media

• Contracts, invoices, and trade documents

9.3 Create a corridor risk matrix

Each corridor should be assessed for:

• Country risk

• Sanctions exposure

• Corruption

• Terrorist financing

• Fraud typologies

• Cash intensity

• Informal value transfer systems

• Currency controls

• Regulatory stability

• Payout transparency

• Data quality

• Agent risk

• Expected transaction purpose

The risk matrix should influence onboarding, transaction limits, monitoring scenarios, staffing, pricing, and whether the corridor is launched at all.

9.4 Transaction monitoring should match the product

Generic monitoring rules produce too many false alerts and miss product-specific risk.

Examples of remittance monitoring scenarios include:

• Rapid increase in frequency or value

• Multiple senders to one beneficiary

• One sender to many unrelated beneficiaries

• Structuring below reporting or review thresholds

• Repeated failed or reversed funding

• High-risk corridor changes

• Third-party funding

• Unusual device or location behavior

• Multiple accounts using the same device or bank account

• Activity inconsistent with occupation or business

• Business payments lacking commercial rationale

• Repeated cash pickup by connected individuals

Rules should be calibrated using actual transaction data and reviewed regularly.

9.5 Sanctions screening is more than name matching

The program should address:

• Customer names

• Beneficiary names

• Business names

• Beneficial owners

• Banks and counterparties

• Wallet addresses where relevant

• Countries and regions

• Payment references

• Vessels, goods, or trade parties for B2B payments where applicable

Screening should occur at onboarding and again at the transaction stage. Lists and customer records must be refreshed.

9.6 Compliance cannot be outsourced completely

A startup may use external advisers, fractional compliance leadership, managed screening, or outsourced alert review. The regulated company or principal still owns the risk and must retain sufficient knowledge, oversight, documentation, and decision-making authority.

The founder should know:

• Who writes the rules

• Who investigates alerts

• Who files reports

• Who approves high-risk customers

• Who validates the system

• Who reports issues to the board

• Who responds to regulators and banks

9.7 Integrate fraud and AML

Fraud and money laundering teams often investigate the same activity from different perspectives. Shared data, case management, and escalation improve both functions.

Important fraud risks include:

• Account takeover

• Synthetic identity

• Stolen cards

• Friendly fraud

• Chargeback abuse

• Social engineering

• Mule accounts

• Beneficiary impersonation

• Refund fraud

• Promotion abuse

• Agent collusion

A transaction may be economically fraudulent, suspicious for AML purposes, or both.

10. Build or Select the Technology Stack

Technology should implement the licensed operating model. It should not determine it.

10.1 The core architecture

A modern money transfer platform commonly includes:

• Customer mobile and web applications

• Customer onboarding

• KYC and KYB orchestration

• Sanctions and PEP screening

• Customer risk rating

• Transaction limits

• Pricing and FX engine

• Payment initiation

• Funding integrations

• Payout integrations

• Double-entry ledger

• Wallet or balance management where permitted

• Transaction monitoring

• Fraud engine

• Case management

• Customer support tools

• Notifications

• Reconciliation

• Regulatory reporting

• Data warehouse and analytics

• Audit logs

• Access control

• Incident monitoring

The double-entry ledger and reconciliation system are more important than the customer interface. A visually polished application with an unreliable ledger is not a payment platform.

10.2 Build, buy, or combine

White-label platform

Best for speed and a controlled initial product. The trade-off is limited customization, provider dependence, and reduced control over vendors and roadmaps.

API-first architecture

Best for a company that wants modularity and has a capable technical team. The company can combine KYC, payments, FX, payout, and compliance providers, but it must own orchestration, monitoring, reconciliation, and failure handling.

Full custom build

Best for a well-funded business with unique requirements and experienced payments engineers. It is slow, expensive, and risky if the team lacks regulatory and ledger expertise.

Hybrid architecture

Often the most practical approach. Use specialized vendors for identity, screening, payment rails, and payouts, while retaining control of the ledger, orchestration, customer experience, reporting, and data.

10.3 Non-negotiable technology requirements

The platform should provide:

• Immutable audit logs

• Role-based access control

• Maker-checker approval for sensitive actions

• Encryption in transit and at rest

• Secure secrets management

• Multi-factor authentication

• Transaction idempotency

• Duplicate-payment prevention

• Real-time and batch reconciliation

• Clear transaction status states

• Retry and reversal logic

• Complete error reporting

• Data retention controls

• Privacy and consent management

• Disaster recovery

• Vendor failover plans

• Monitoring and alerting

• Regulatory data extraction

10.4 Design transaction states carefully

A payment should not be represented only as “pending” or “complete.” Typical states include:

• Created

• Awaiting funding

• Funded

• Compliance review

• Approved

• Rejected

• FX booked

• Sent to payout partner

• Accepted by payout partner

• Paid

• Failed

• Returned

• Refunded

• Chargeback received

• Reconciled

• Closed

Every state transition should have a timestamp, actor, reason, ledger effect, and customer communication.

10.5 Avoid vendor lock-in

Contracts and architecture should provide:

• Data export rights

• Transition assistance

• Clear termination rights

• Access to transaction history

• Documented APIs

• Service-level commitments

• Subprocessor transparency

• Security incident notification

• Business continuity commitments

• Ownership of customer data

• Reasonable migration periods

A provider that controls the customer agreement, funds, data, and technology may be difficult to replace even if its service deteriorates.

11. Select and Contract with Partners

A money transfer business is a network of counterparties. The quality of those counterparties determines whether the company can launch, remain compliant, and survive disruptions.

11.1 Main partner categories

• Principal license holder or sponsor

• Banks and safeguarding institutions

• Card acquirers and processors

• Open-banking or account-funding providers

• Foreign exchange providers

• Liquidity providers

• Payout banks

• Mobile-wallet providers

• Cash networks

• Identity-verification vendors

• Sanctions-screening vendors

• Transaction-monitoring vendors

• Fraud providers

• Cloud and cybersecurity providers

• Stablecoin issuers, custodians, exchanges, and on/off ramps

• Customer support providers

11.2 Partner due diligence checklist

Before signing, verify:

• Exact legal entity name

• License or registration status

• Regulatory permissions

• Jurisdictions covered

• Products covered

• Customer types permitted

• Bank accounts and safeguarding arrangements

• Financial condition

• Regulatory and enforcement history

• Compliance program

• Security certifications and testing

• Subcontractors

• Settlement process

• Prefunding requirements

• FX methodology

• Service levels

• Incident history

• Complaint handling

• Reconciliation files

• Data ownership

• Audit rights

• Termination rights

• Change-of-control provisions

Do not accept a license screenshot as due diligence. Verify the entity directly in the regulator’s public register and confirm that the permissions match the proposed activity.

11.3 Test the operational details before signing

Ask the partner to demonstrate:

• A complete successful transaction

• A failed transaction

• A return

• A refund

• A sanctions hold

• A duplicate transaction

• The daily settlement report

• The reconciliation file

• The customer receipt

• The complaint workflow

• The escalation process

A commercial proposal can look attractive until the company discovers that the partner provides no beneficiary confirmation, no usable reconciliation file, or a five-day refund process.

11.4 Contract for the bad day

Contracts should address what happens when:

• The bank closes an account

• The payout partner is offline

• A regulator intervenes

• Funds are frozen

• A data breach occurs

• A customer makes a complaint

• A transaction is sanctioned

• A reserve is increased

• The partner changes pricing

• The partner exits the corridor

• The company terminates the relationship

The termination and transition clauses may be more important than the launch clause.

12. Use Stablecoins Carefully

Stablecoins can improve settlement speed, operating hours, transparency, and capital efficiency in selected corridors. They do not eliminate licensing, banking, sanctions, AML, custody, or consumer-protection obligations.

12.1 Stablecoin as an internal settlement rail

A wholesale settlement model may look like this:

Customer funds in origin currency
        |
        v
Origin regulated payment provider
        |
        v
Licensed fiat-to-stablecoin conversion
        |
        v
Stablecoin transfer between approved institutional wallets
        |
        v
Licensed destination off-ramp
        |
        v
Local currency payout to beneficiary

The customer may still receive a normal fiat remittance. The stablecoin is an internal settlement rail between regulated parties.

12.2 Questions that must be answered

• Who converts fiat into the stablecoin?

• Who has custody?

• Who controls the wallets and private keys?

• Which entity initiates the blockchain transfer?

• Which entity screens the wallet addresses?

• Which travel-rule obligations apply?

• Who converts back into fiat?

• Is the off-ramp licensed?

• How is the transaction reconciled to the customer ledger?

• What happens if the stablecoin depegs or redemption is delayed?

• How are sanctions and blocked-property obligations handled?

• What disclosures are made to customers?

• How is chain congestion handled?

• How are accounting and tax consequences recorded?

12.3 Stablecoins do not cure a defective corridor

A stablecoin cannot compensate for:

• No lawful payout partner

• No origin-side license

• No destination-side permission

• Weak KYC

• Undisclosed intermediaries

• Poor reconciliation

• Unreliable local liquidity

• Sanctions exposure

• A business model that loses money

12.4 EU MiCA implications

As of July 2026, the maximum MiCA transitional period for legacy EU virtual asset providers has ended. A company providing crypto-asset services in the EU should confirm whether it requires CASP authorization and whether the stablecoin itself is permitted and properly issued under MiCA.^[12-1]

12.5 Do not assume a U.S. state of formation creates crypto permission

Forming a company in Wyoming, Delaware, or another state does not by itself create permission to exchange, transmit, custody, or settle digital assets nationwide. The activity may trigger federal MSB obligations, state money transmission laws, digital-asset licensing, securities or commodities rules, sanctions requirements, consumer-protection laws, and banking restrictions.

13. Model Revenue, Margin, and Unit Economics

Money transfer is generally a volume business. Gross revenue can appear attractive while net contribution remains weak.

13.1 Main revenue sources

• Customer transfer fee

• Foreign exchange spread

• Partner revenue share

• Subscription or service fee

• Bill-payment or airtime commission

• Business account fee

• API or white-label fee

• Ancillary services

Revenue from customer-funds float or interest should never be assumed without confirming the legal, safeguarding, accounting, and contractual treatment.

13.2 Main variable costs

• Customer funding cost

• Card interchange and processing

• Bank transfer fees

• Payout partner fee

• FX and hedging cost

• Sponsor or principal fee

• KYC and screening cost

• Transaction monitoring cost

• Messaging and notifications

• Customer support

• Fraud loss

• Chargebacks

• Refunds and returns

• Agent commission

13.3 Contribution formula

Net contribution per transaction =
Customer fee
+ FX revenue
+ ancillary revenue
- funding cost
- payout cost
- FX and hedging cost
- sponsor or partner share
- compliance variable cost
- fraud and chargeback provision
- customer support cost

13.4 Illustrative transaction economics

Assume a customer sends USD 500.

If customer acquisition costs USD 35, the company needs approximately eleven similar transactions merely to recover acquisition cost, before fixed overhead is considered.

This example is illustrative, but it demonstrates why retention is critical.

13.5 Model each corridor separately

A company should not use one blended margin for all corridors. Each corridor has different:

• Funding costs

• Payout costs

• FX spreads

• Fraud rates

• Customer behavior

• Average transaction size

• Refund rates

• Liquidity requirements

• Support costs

• Marketing costs

A profitable corridor can subsidize a loss-making corridor without management realizing it unless contribution is measured separately.

13.6 Include liquidity cost

Prefunding has an economic cost even if the partner does not charge an explicit fee. Capital tied up in destination accounts cannot be used elsewhere.

Measure:

• Average prefunding balance

• Peak prefunding balance

• Days of liquidity held

• Cost of capital

• FX exposure

• Idle balances

• Emergency funding costs

13.7 Define commercial kill criteria

Before launch, set conditions under which the corridor will be paused or closed.

Examples:

• Contribution remains negative after a defined volume

• Fraud exceeds a threshold

• Customer acquisition does not recover within a target period

• Payout failure exceeds a threshold

• Reconciliation remains unresolved

• Banking cost becomes uneconomic

• Partner service levels deteriorate

• Regulatory risk changes materially

A corridor should not continue merely because the company has already spent money building it.

14. Acquire and Retain Customers

Customer acquisition in remittances is built on trust, relevance, and repeated behavior. Generic advertising is rarely enough.

14.1 Use corridor-specific acquisition

The marketing message should identify the exact use case:

• Send money from Canada to Bangladesh

• Pay suppliers in China from Nigeria

• Send school fees from the UK to Ghana

• Pay contractors in Kenya from the United States

• Deliver funds directly to a mobile wallet in the Philippines

High-intent landing pages should clearly disclose:

• Fee

• Exchange rate

• Amount received

• Delivery method

• Expected delivery time

• Eligibility

• Limits

• Required documents

• Customer support contact

14.2 Build community distribution

Effective channels may include:

• Diaspora associations

• Community centers

• Religious organizations

• Ethnic grocery stores

• Business associations

• Accountants and immigration professionals

• Freight forwarders and trade groups

• Universities

• Employer partnerships

• Local agents

• Influencers with genuine community credibility

Community distribution must comply with advertising, referral, agent, and incentive rules.

14.3 Use referrals carefully

Referral programs can lower acquisition cost, but they are vulnerable to abuse.

Controls may include:

• Identity verification before rewards

• Reward after a completed transaction

• Device and bank-account checks

• Limits per customer and household

• Detection of self-referrals

• Promotion-specific monitoring

• Clear terms and expiration

14.4 Retention drivers

Customers remain when the service is reliable and predictable.

Important retention factors include:

• Transparent pricing

• Accurate delivery estimates

• Fast transaction tracking

• Reliable beneficiary payout

• Effective exception handling

• Multilingual support

• Easy repeat transactions

• Saved beneficiaries with appropriate security

• Loyalty rewards

• Relevant bill payment or top-up services

• Trustworthy complaint resolution

A slightly higher-priced service can outperform a cheaper competitor if it delivers consistently and resolves problems quickly.

14.5 B2B acquisition is relationship-driven

B2B customers require:

• Consultative sales

• KYB support

• Pricing proposals

• Service-level commitments

• Treasury and settlement discussions

• Integration support

• Account management

• Credit and prefunding analysis

• Contract negotiation

A senior salesperson with a credible network can be more valuable than broad digital advertising.

15. Operate the Business Every Day

Licensing allows the company to operate. Operations determine whether it survives.

15.1 Daily operational functions

A mature daily operating cycle includes:

• Opening liquidity review

• Bank balance review

• Safeguarding calculation

• Prefunding review

• Transaction queue monitoring

• Compliance alert review

• Sanctions holds

• Failed funding review

• Failed payout review

• Refund and return processing

• Chargeback processing

• Customer complaints

• Partner incidents

• Reconciliation

• Suspense-account review

• End-of-day reporting

15.2 Exception management

The company should have written procedures for:

• Incorrect beneficiary details

• Duplicate transfers

• Payment timeouts

• Delayed settlement

• Partial payouts

• Bank rejections

• Wallet rejections

• Cash unavailability

• FX rate expiration

• Customer cancellation

• Regulatory hold

• Sanctions match

• Fraud claim

• Deceased beneficiary

• Partner outage

Every exception should have an owner, service-level target, escalation path, and customer communication template.

15.3 Customer complaints are regulatory data

Complaints should be categorized, analyzed, and reported to management.

Useful categories include:

• Pricing or exchange rate

• Delayed transfer

• Failed payout

• Refund delay

• Account closure

• Identity verification

• Fraud

• Customer support

• Agent behavior

• Technical error

• Disclosure issue

Repeated complaints often identify a control failure before an audit does.

15.4 Business continuity

The company should plan for:

• Bank outage

• Payout-partner outage

• Cloud outage

• Cyber incident

• Data corruption

• Staff unavailability

• Natural disaster

• Regulatory order

• Sudden de-risking

• Liquidity shortfall

• Stablecoin or exchange disruption

• Telecommunications failure

The continuity plan must be tested, not merely documented.

15.5 Regulatory change management

Payments regulation changes continuously. The company should maintain:

• A legal and regulatory inventory

• Named owners for each obligation

• A change log

• Impact assessments

• Policy updates

• System changes

• Training records

• Board reporting

• Implementation evidence

Regulatory monitoring may be supported by counsel, advisers, associations, and software, but management remains accountable.

16. Build the Right Team and Governance

A small money transfer company does not need a large corporate hierarchy, but it does need clear accountability.

16.1 Core leadership roles

• Chief Executive Officer

• Chief Compliance Officer or MLRO

• Head of Operations

• Finance and treasury lead

• Product and technology lead

• Information security lead

• Customer support lead

• Partnerships or business development lead

Some roles may be fractional or combined initially, subject to regulatory expectations and conflicts of interest.

16.2 Compliance must have authority

The compliance officer should have:

• Direct access to the board

• Authority to stop transactions

• Authority to reject customers

• Adequate staffing and systems

• Independence from sales pressure

• Access to all relevant data

• A documented escalation route

A compliance officer who cannot challenge revenue decisions is not functioning effectively.

16.3 Board oversight

The board should regularly review:

• Regulatory status

• Capital and liquidity

• Safeguarding

• Compliance metrics

• Suspicious activity

• Fraud losses

• Complaints

• Partner performance

• Cybersecurity

• Audit findings

• Reconciliation breaks

• Regulatory changes

• Major incidents

Minutes should document decisions, challenges, and remediation.

16.4 Hire corridor expertise

Local corridor managers can provide knowledge of:

• Customer behavior

• Language

• Payout systems

• Banking practices

• Fraud patterns

• Local regulation

• Community distribution

• Competitor pricing

They may begin as contractors or advisers, but sensitive operational and compliance functions require appropriate supervision and confidentiality controls.

17. Follow a Phased Launch Roadmap

The exact timeline varies by jurisdiction and model. A sponsor-led launch may move faster than direct licensing, while a complex multi-jurisdiction application can take well beyond one year.

Phase 0: Founder readiness — Weeks 1–4

Deliverables:

• Two-page business brief

• Founder and ownership profile

• Capital assessment

• One target corridor

• One target customer segment

• One defined transaction

• Initial risk appetite

• Commercial kill criteria

Decision: Is the business sufficiently defined and funded to proceed?

Phase 1: Regulatory and commercial design — Months 1–3

Deliverables:

• Jurisdiction and licensing analysis

• Market-entry model

• Corporate structure

• Flow of funds

• Transaction sets

• Initial financial model

• Partner requirements

• Banking package

• Compliance gap assessment

Decision: Sponsor, direct license, acquisition, or staged combination?

Phase 2: Partner selection and pre-application — Months 2–6

Deliverables:

• Principal or sponsor RFP

• Bank outreach

• Payout-partner selection

• Technology selection

• Compliance vendors

• Draft contracts

• Business plan

• AML and risk documentation

• Governance appointments

• Data room

Decision: Are the partners, capital, and controls credible enough to submit or launch?

Phase 3: Application, implementation, and integration — Months 4–12+

Deliverables:

• Regulatory submissions

• Sponsor onboarding

• Banking onboarding

• Technology build

• Partner integrations

• Ledger and reconciliation

• Compliance configuration

• Policies and procedures

• Training

• Security testing

• Operational testing

Decision: Has the business passed legal, compliance, operational, security, and financial readiness testing?

Phase 4: Controlled pilot — Months 6–15+

Begin with:

• Limited customers

• Limited transaction values

• One funding method

• One payout method

• Manual oversight

• Daily reconciliation

• Daily compliance review

• Clear incident escalation

Do not scale until the company can demonstrate stable processing, predictable payout, accurate reconciliation, acceptable fraud, and positive contribution economics.

Phase 5: Scale and independent licensing — Months 12–24+

Potential actions:

• Expand transaction limits

• Add a second payout method

• Add a second corridor

• Add B2B or value-added services

• Apply for additional licenses

• Build redundancy

• Migrate from sponsor to own license where appropriate

• Strengthen governance and audit

Expansion should follow evidence, not ambition alone.

18. Avoid the Most Common Traps

Trap 1: “FinCEN registration means we are licensed across the United States.”

It does not. FinCEN registration is a federal AML registration. State licensing analysis remains necessary.

Trap 2: “FINTRAC gave us a Canadian license.”

FINTRAC registration is not a license or endorsement. RPAA registration may also be required.

Trap 3: “The API provider’s license automatically covers us.”

Only the legal structure, appointment, contract, and regulated operating model determine coverage.

Trap 4: “We can rent a license.”

Use accurate terminology such as agent, authorized delegate, program manager, distributor, or sponsored entity. A legitimate principal does not simply rent a license while ignoring the program.

Trap 5: “Montana gives us a U.S. money transmitter license.”

Montana’s lack of a money transmitter licensing regime does not authorize activity elsewhere.

Trap 6: “A Wyoming company gives us a crypto exemption everywhere.”

State formation does not override federal or other state laws.

Trap 7: “Stablecoins remove the need for licensing.”

They do not. They change the settlement rail and may add crypto-specific obligations.

Trap 8: “Buying a licensed company lets us launch immediately.”

Change-of-control approval, banking consent, remediation, and product review may be required.

Trap 9: “Technology is the main challenge.”

Licensing, banking, compliance, liquidity, reconciliation, and partner acceptance are usually harder.

Trap 10: “The cheapest license is the best license.”

A license with weak banking and counterparty acceptance may be commercially useless.

Trap 11: “We will solve the corridor after licensing.”

The corridor determines the license, banking, compliance, technology, and economics. It must be designed first.

Trap 12: “One bank and one payout partner are enough.”

Single points of failure create existential risk. Redundancy should be planned and approved.

Trap 13: “Customer funds can finance operations.”

Customer funds are often safeguarded or restricted and should not be treated as working capital.

Trap 14: “Compliance can be fully outsourced.”

Vendors can support compliance. Accountability cannot be outsourced.

Trap 15: “Correspondent banking is just another payment product.”

Do not market a non-bank as a settlement bank or correspondent bank. Describe the actual regulated payment and settlement service accurately and confirm that the permissions support it.

Trap 16: “Volume will fix negative margins.”

More volume magnifies a negative contribution margin and increases prefunding requirements.

19. Use the Readiness Checklist

A founder should not proceed to a material build or application until most of the following can be answered clearly.

Strategy

• One primary customer segment is defined.

• One launch corridor is selected.

• The customer problem is validated.

• The commercial wedge is specific.

• The first transaction can be described in one sentence.

Licensing and structure

• The regulated activities have been identified.

• The origin and destination jurisdictions have been analyzed.

• The market-entry model is selected.

• The legal entities and ownership are defined.

• The principal or sponsor fit has been assessed.

• Customer migration rights have been considered.

Flow of funds

• Every entity touching funds is identified.

• Every bank account is identified.

• Customer funds and corporate funds are separated appropriately.

• FX and settlement points are documented.

• Refund, return, and chargeback flows are documented.

• Money, data, instruction, and accounting flows are mapped.

Banking and liquidity

• Banking requirements are documented.

• Safeguarding requirements are understood.

• Prefunding is modeled.

• Peak liquidity is modeled.

• Backup partners are planned.

• Daily reconciliation is designed.

Compliance

• A compliance officer or MLRO is identified.

• The enterprise risk assessment is drafted.

• KYC and KYB requirements are defined.

• Sanctions and PEP screening is designed.

• Transaction monitoring scenarios are defined.

• Suspicious activity reporting procedures are defined.

• Agent and partner oversight is documented.

• Independent testing is planned.

Technology

• The ledger architecture is defined.

• Transaction states are defined.

• Audit logs are available.

• Reconciliation files are available from partners.

• Data ownership and export rights are documented.

• Security and business continuity are tested.

Economics

• Revenue is modeled by corridor.

• All variable costs are included.

• Fraud and chargeback provisions are included.

• CAC and retention are modeled.

• Liquidity cost is included.

• Downside scenarios are funded.

• Commercial kill criteria are defined.

Operations

• Failed funding procedures exist.

• Failed payout procedures exist.

• Refund procedures exist.

• Complaint procedures exist.

• Incident management exists.

• Daily and monthly management reporting exists.

If several of these items are unresolved, the company is still in concept design—not launch execution.

20. Frequently Asked Questions

Can I start a money transfer business without obtaining my own license?

Yes, in some jurisdictions and operating models. A business may launch as a properly appointed agent, authorized delegate, distributor, program manager, or white-label partner of a licensed principal. The exact rights and obligations depend on law, contract, regulatory appointment, and flow of funds.

Is FinCEN MSB registration a U.S. money transmitter license?

No. FinCEN registration is a federal AML registration. State money transmitter licensing requirements must be analyzed separately.

Is FINTRAC registration a Canadian license?

No. FINTRAC states that MSB registration is not a license, certificate, or endorsement. A payment service provider may also need Bank of Canada registration under the RPAA.

How long does it take to launch?

A managed or sponsor-led program may launch in several months if the business, compliance, banking, and integration are straightforward. An independent license commonly requires a substantially longer period. Complex or multi-jurisdiction programs may take 12 to 24 months or more. Timelines begin when the application and supporting materials are complete—not when the founder first decides to apply.

How much money is needed?

There is no universal figure. The budget must include regulatory capital, bonds or collateral, professional fees, compliance, technology, banking, prefunding, staff, marketing, and at least 12 to 18 months of runway. A sponsor-led pilot may require a six-figure budget, while a multi-state or multi-jurisdiction licensed business may require several million dollars.

Should I build my own technology?

Not necessarily. Most early-stage companies should use a hybrid model: buy specialized infrastructure where appropriate and retain control of the ledger, orchestration, data, reporting, and customer experience. A full custom build is justified only when the company has unique requirements, sufficient capital, and experienced payments engineers.

What is the difference between a payment institution and an electronic money institution?

A payment institution provides regulated payment services. An electronic money institution can issue electronic money and also provide payment services. A wallet product may require EMI authorization if it creates stored monetary value, but the legal analysis depends on the product design.

Can stablecoins be used for settlement?

Yes, in selected structures and jurisdictions. The company must still address licensing, custody, AML, sanctions, travel-rule obligations, wallet screening, issuer risk, off-ramp licensing, liquidity, reconciliation, tax, and customer disclosures.

Can I buy an existing licensed company?

Yes, but the acquisition generally requires regulatory change-of-control approval. The buyer must conduct detailed regulatory, financial, compliance, banking, technology, and litigation due diligence.

Should I launch several corridors at once?

Usually not. Launch one corridor, one customer segment, one funding method, and one payout method. Prove compliance, operations, reconciliation, and economics before expanding.

Do I need banking before applying for a license?

Requirements vary, but regulators and principals usually expect a credible banking and safeguarding plan. Banks may also require evidence of licensing. The two workstreams should therefore be pursued in parallel.

Can I earn interest on customer funds?

Do not assume so. The treatment of income on safeguarded or customer funds depends on the jurisdiction, account structure, customer agreement, accounting treatment, and partner contract.

What should I prepare before speaking to a licensing or payments consultant?

Prepare:

• A two-page business brief

• Flow-of-funds diagram

• Two or three transaction sets

• Target jurisdictions and corridors

• Customer types

• Expected volumes and values

• Funding and payout methods

• Available capital

• Ownership and management details

• Current partner and banking status

This allows the discussion to focus on structure and execution rather than basic definitions.

Is a money transfer business still worth starting in 2026?

It can be, if the company solves a real corridor problem, has distribution, obtains credible regulatory coverage and banking, builds strong compliance and operations, and achieves positive unit economics. It is not attractive as a generic “send money anywhere” application with no regulatory or distribution advantage.

21. Glossary

AML — Anti-Money Laundering: Controls intended to prevent and detect the use of financial services for money laundering.

Authorized Delegate / Authorized Agent: A person or company appointed by a licensed principal to perform approved activities on the principal’s behalf.

BSA — Bank Secrecy Act: The principal U.S. federal framework for AML recordkeeping, reporting, and compliance obligations.

CASP — Crypto-Asset Service Provider: An entity authorized under the EU MiCA framework to provide specified crypto-asset services.

CDD — Customer Due Diligence: The process of identifying customers, understanding their activity, and assessing risk.

CFT — Countering the Financing of Terrorism: Controls intended to prevent and detect terrorist financing.

Chargeback: Reversal of a card transaction initiated through the cardholder’s bank or card scheme.

Corridor: The complete route between an origin and destination market, including customers, regulation, funding, FX, settlement, payout, and operations.

EDD — Enhanced Due Diligence: Additional checks applied to higher-risk customers or transactions.

EMI — Electronic Money Institution: A regulated institution authorized to issue electronic money and provide payment services.

FinCEN — Financial Crimes Enforcement Network: The U.S. Treasury bureau responsible for administering and enforcing the Bank Secrecy Act.

Flow of Funds: A diagram and narrative showing how money moves between the customer, regulated entities, banks, processors, FX providers, and payout partners.

FX — Foreign Exchange: Conversion from one currency into another.

KYC — Know Your Customer: Identity verification and customer-risk controls for individuals.

KYB — Know Your Business: Verification and risk assessment of companies, owners, directors, and business activity.

Ledger: The accounting system that records customer balances, transaction movements, fees, settlements, refunds, and adjustments.

MiCA — Markets in Crypto-Assets Regulation: The EU framework regulating crypto-asset issuance and crypto-asset service providers.

MLRO — Money Laundering Reporting Officer: The person responsible for AML oversight and suspicious activity reporting in jurisdictions using this title.

MSB — Money Services Business: A regulatory category that can include money transmitters, currency exchangers, check cashers, and other specified services.

MTL — Money Transmitter License: A state-level U.S. license authorizing money transmission within its scope.

MTO — Money Transfer Operator: A company providing money transfer or remittance services.

NMLS — Nationwide Multistate Licensing System: The platform used by many U.S. state regulators for licensing and reporting.

Payout Partner: A bank, wallet, cash network, or regulated payment company that delivers funds to the beneficiary.

PEP — Politically Exposed Person: A person whose public function may create elevated corruption or bribery risk, along with relevant family members and associates as defined by applicable rules.

PI — Payment Institution: A regulated institution authorized to provide specified payment services.

Prefunding: Money deposited with a partner in advance so that beneficiary payouts can be made quickly.

Principal License Holder: The licensed entity that appoints and supervises agents or delegates and remains responsible for the regulated program.

PSP — Payment Service Provider: A broad term for an entity that performs payment functions.

Reconciliation: Comparison of ledger, bank, processor, FX, and payout records to confirm that all balances and transactions match.

RPAA — Retail Payment Activities Act: Canada’s federal framework for supervision of in-scope payment service providers by the Bank of Canada.

Safeguarding: Protection of customer funds, commonly through segregation, eligible investments, guarantees, insurance, or other legally prescribed arrangements.

SAR / STR — Suspicious Activity Report / Suspicious Transaction Report: A regulatory report concerning activity suspected to involve money laundering, terrorist financing, or other reportable conduct.

Settlement: Final transfer of value between financial institutions or payment counterparties.

Stablecoin: A crypto-asset designed to maintain value relative to a reference asset, often a fiat currency.

Transaction Set: A detailed example showing the operational, financial, compliance, and accounting treatment of a transaction from initiation through completion or failure.

Travel Rule: Requirements to transmit specified originator and beneficiary information with certain transfers, including qualifying virtual-asset transfers in relevant jurisdictions.

22. Conclusion

Starting a money transfer business in 2026 is difficult because every part of the business depends on every other part.

The license determines what the company may do. The corridor determines which license and partners are needed. The banks determine how funds can be collected and safeguarded. The payout partners determine delivery quality. The compliance program determines which customers and transactions can be accepted. The technology must implement those rules and produce a complete audit trail. The unit economics determine whether the company can survive long enough to scale.

The founders who succeed are generally not those who find the cheapest API or the fastest license advertisement. They are the founders who define a narrow problem, design the flow of funds correctly, obtain credible regulatory coverage, secure banking and liquidity, build an effective compliance program, reconcile every transaction, and expand only after the first corridor works.

The correct order is:

1. Define the customer and transaction.

2. Select the corridor.

3. Map the flow of funds.

4. Determine the required permissions.

5. Choose the market-entry model.

6. Secure banking and partners.

7. Build compliance and operations.

8. Implement the technology.

9. Pilot with strict limits.

10. Scale after the economics and controls are proven.

That sequence will not make the business easy. It will make it executable.

Need Help Starting a Money Transfer Business?

Faisal Khan LLC is a cross-border payments, banking, licensing, and deal-facilitation consultancy. We help fintechs, remittance operators, payment companies, money services businesses, and digital-asset businesses evaluate market-entry structures, licensing strategies, sponsor and authorized-delegate models, banking access, flow-of-funds design, compliance planning, technology requirements, and partner selection.

If you are planning to start a money transfer business—or need to restructure an existing one—get in touch.

© 2026 Faisal Khan LLC. All rights reserved.

Faisal Khan LLC operates as an independent business intelligence, marketing, lead-generation, consulting, and deal-facilitation firm. It is not a bank, financial institution, money transmitter, money services business, broker-dealer, investment adviser, law firm, or any other regulated financial entity. This article is for general informational purposes only and does not constitute legal, tax, financial, investment, compliance, or regulatory advice. Licensing and regulatory requirements change and depend on the exact facts, jurisdiction, product, customer, and flow of funds. Readers should obtain advice from appropriately licensed legal, tax, accounting, and regulatory professionals before acting.

Regulatory and Market References

1. World Bank, “In 2024, remittance flows to low- and middle-income countries are expected to reach $685 billion”: https://blogs.worldbank.org/en/peoplemove/in-2024--remittance-flows-to-low--and-middle-income-countries-ar↩︎

2. World Bank, Remittance Prices Worldwide, Q3 2025 global average cost: https://remittanceprices.worldbank.org/↩︎

3. FinCEN, Money Services Business Registration and related guidance: https://www.fincen.gov/resources/money-services-business-msb-registration↩︎

4. Conference of State Bank Supervisors, state money transmitter supervision and NMLS: https://www.csbs.org/reality-money-transmission-secure-convenient-and-trusted-under-state-supervision↩︎

5. Montana Division of Banking and Financial Institutions: https://banking.mt.gov/↩︎

6. Consumer Financial Protection Bureau, remittance-transfer protections: https://www.consumerfinance.gov/ask-cfpb/what-is-a-remittance-transfer-and-what-are-my-rights-en-1161/↩︎

7. FINTRAC, Money Services Business Registry and registration statement: https://fintrac-canafe.canada.ca/msb-esm/reg-eng↩︎

8. Bank of Canada, Retail Payment Activities Act frequently asked questions: https://www.bankofcanada.ca/2026/01/frequently-asked-questions-about-retail-payments-supervision/↩︎

9. Financial Conduct Authority, Payment Services and Electronic Money – Our Approach: https://www.fca.org.uk/publication/finalised-guidance/fca-approach-payment-services-electronic-money-sept-2017.pdf↩︎

10. Financial Conduct Authority, changes to the safeguarding regime for payment and e-money firms: https://www.fca.org.uk/publications/policy-statements/ps25-12-changes-safeguarding-regime-payments-and-e-money-firms↩︎

11. European Parliament, legislative status of PSD3 and the Payment Services Regulation: https://www.europarl.europa.eu/legislative-train/theme-economic-and-monetary-affairs-econ/file-revision-of-eu-rules-on-payment-services↩︎

12. Commission de Surveillance du Secteur Financier, “MiCA: Transition period for virtual asset service providers ended on 1 July 2026”: https://www.cssf.lu/en/2026/07/mica-transition-period-for-virtual-asset-service-providers-ended-on-1-july-2026/↩︎↩︎