Launching Cross-Border Payments in Singapore: MAS Licenses, Platform Costs, Timelines
Singapore is one of the strongest hubs for cross-border payments, but your license class, safeguarding duties and technology-risk obligations shape your platform choice and budget more than any vendor demo. Here's what to plan for, what it typically costs and how long it takes.
Which Payment Services Act license a cross-border platform actually needs
If you plan to move customer money into or out of Singapore, your first decision isn't the vendor. It's the license, because that sets your capital, safeguarding duties, audit load and most of the platform requirements that follow. Any cross-border payments platform Singapore regulators will accept is designed around that answer.
The Payment Services Act (PSA), in force since 2020, regulates seven payment services. Cross-border money transfer is one. Most remittance, B2B payout and treasury-collection businesses also touch account issuance (holding customer balances), domestic money transfer (paying out over FAST or PayNow) or e-money issuance (stored value). Each counts as a separate service on your application. Map your product honestly before you file. Understating what you do is a common cause of extra MAS clarification rounds.
The PSA has three license classes:
- Money-changing license: physical currency exchange only. Irrelevant for a digital transfer platform.
- Standard payment institution (SPI): for firms below set volume thresholds. MAS has historically set these at a monthly average of around S$3 million for any single service, about S$6 million across two or more services, and a daily average e-money float of about S$5 million.
- Major payment institution (MPI): required once you exceed those thresholds, and the realistic target for any business planning meaningful corridor volume.
Our position: if your business case shows you crossing the SPI thresholds within 18 to 24 months, apply for the MPI from the start. Upgrading later means a second application, a second review cycle and possibly a growth freeze while you wait. Thresholds and their application have been revised before, so confirm current figures with MAS guidance and your adviser.
Two exceptions matter. Banks licensed under Singapore's Banking Act are generally exempt from PSA licensing for these services, so a bank launching a cross-border product works under its existing license and supervisory relationship. And a fintech that never takes possession of customer funds, acting only as a technology provider to a licensed entity, may fall outside licensing altogether. That line is fact-specific. Who contracts with the customer, who controls the funds and whose name appears on the flow all matter. This is where a licensed Singapore adviser earns their fee.
Capital, security deposit and the people MAS expects to see
The financial thresholds are modest next to an EU electronic money license or a multi-state money transmitter footprint in the US. The people requirements are where applications stall.
| Requirement | SPI | MPI |
|---|---|---|
| Base capital | S$100,000 | S$250,000 |
| Security deposit with MAS | Not required | Typically S$100,000, rising to S$200,000 at higher volumes |
| Safeguarding of customer funds | Generally not required | Required for relevant money; amendments to the PSA have widened the scope, so confirm which of your services are covered |
| Annual audited financials and AML/CFT audit | Yes | Yes, with more extensive regulatory returns |
| Technology risk obligations | Cyber hygiene baseline | Cyber hygiene plus incident reporting and system availability duties |
These figures reflect the PSA framework as generally applied. Confirm current amounts, fees and safeguarding scope with MAS and your adviser before budgeting. In USD, MPI base capital plus deposit comes to roughly US$260,000 to US$340,000 that you must hold and can't spend on growth.
On people, MAS expects a Singapore-incorporated company (or registered foreign company) with a permanent place of business locally. You'll need at least one executive director who meets MAS's local residency expectations, usually a Singapore citizen or permanent resident; check the current position on other pass holders. You also need a compliance officer with genuine AML/CFT experience, plus fit-and-proper declarations for directors, the CEO and substantial shareholders.
Foreign groups routinely underestimate this. Say a hypothetical Indian or UAE remittance company plans to run its Singapore entity from head office, with a nominee director and compliance outsourced. MAS will likely question whether that entity can manage its risks locally. Budget for at least two to four genuinely senior people based in Singapore before you file.
AML/CFT and technology risk duties that decide your platform shortlist
Once licensed, three sets of obligations define what your software must do. Treat them as hard filters in vendor evaluation, not features to discuss after signing.
AML/CFT under MAS Notice PSN01
Licensees providing cross-border money transfer must run customer due diligence, ongoing monitoring, sanctions screening and suspicious transaction reporting to Singapore's Suspicious Transaction Reporting Office. Wire transfer rules require originator and beneficiary information to travel with the payment, with fuller data required above a low threshold set in the notice. Your platform therefore has to:
- Capture and pass structured payer and payee data on every corridor, including through payout partners that use different message formats.
- Screen names in real time against UN, MAS-designated and other relevant sanctions lists, with documented alert handling.
- Run scenario-based transaction monitoring tuned to remittance typologies: structuring, rapid in-and-out flows, high-risk corridors.
- Keep records retrievable for at least five years.
Technology risk and cyber hygiene
MAS's Technology Risk Management Guidelines set expectations on governance, outsourcing, access control and testing. Binding notices sit on top. The cyber hygiene notice applies to all licensees and covers multi-factor authentication, patching, malware protection and administrative account security. MPIs also face incident notification deadlines measured in hours (historically as short as one hour from discovery) and availability expectations for critical systems. If a vendor can't show you its uptime history, its recovery time and recovery point objectives, and how it would hand you incident data inside that window, it isn't suitable for an MPI.
Safeguarding and outsourcing
Safeguarding usually means a bank undertaking or guarantee, or a trust account with an eligible safeguarding institution. Your ledger must reconcile customer money against safeguarded balances daily, which rules out platforms that only reconcile in batch at month-end. MAS outsourcing guidelines also expect audit and access rights over material service providers. Write them into every contract, including your cloud provider and core platform vendor.
Build, buy or partner: three operating models compared
Most Singapore launches fall into one of three models. The right one depends on how many corridors you need in year one and whether payments are your product or a feature of something else.
| Model | What you own | Best fit | Main trade-off |
|---|---|---|---|
| Full build on own MPI license | License, ledger, compliance stack, direct bank and network connections | Well-funded remittance or B2B payments specialists planning 10+ corridors | Typically 18 to 30 months and the highest cost before revenue |
| Own license plus licensed payout network | License, customer relationship, compliance; payouts via a network provider | Most fintechs and regional banks | Per-transaction fees and dependence on the network's corridor quality |
| Embedded or partner model | Customer experience; the partner holds the license and funds | Platforms, ERPs and marketplaces adding payouts as a feature | Thin margins, less control, partner concentration risk |
The middle option is the right default for most readers, because it gets you a license and customer ownership without spending two years wiring bank connections. Payout and collection networks with a Singapore presence include Thunes, Nium, Wise Platform, Airwallex, Rapyd, TerraPay and Visa's Currencycloud. Corridor depth and pricing differ: some are stronger in Southeast Asian and South Asian wallet payouts, others in Europe and the Americas. Contract with two. It gives you pricing leverage and a fallback if one partner exits a corridor.
For the core, look at ledger and payments-hub vendors such as Thought Machine, Mambu, Temenos or Volante, or a specialist remittance platform if your flows are consumer-to-consumer. Pair the core with screening and monitoring from providers such as LSEG World-Check, Dow Jones, ComplyAdvantage or Napier, and identity verification from Sumsub, Jumio or similar.
Don't ignore local rails. FAST and PayNow handle domestic legs cheaply, and PayNow's bilateral links with Thailand's PromptPay, India's UPI and Malaysia's DuitNow can lower cost on specific retail corridors. Multilateral instant-payment linkage through the Nexus initiative may widen that over time. Ask your payout partner or sponsor bank exactly how you'd get access.
Indicative setup and running costs
The ranges below are typical 2026 market ranges for an MPI-licensed cross-border money transfer platform on the own-license-plus-network model. Contracts vary widely by volume, corridor mix and negotiation, and Singapore pricing can differ from global list rates. Confirm every line with vendors.
| Cost item | One-off (USD) | Annual running (USD) |
|---|---|---|
| Licensing adviser and legal (application, policies, MAS responses) | $60,000 to $200,000 | $20,000 to $60,000 ongoing counsel |
| Capital and security deposit (held, not spent) | $260,000 to $340,000 | Opportunity cost only |
| Core ledger and payments platform | $50,000 to $400,000 implementation | $80,000 to $500,000 licenses or SaaS |
| KYC, sanctions screening, transaction monitoring | $20,000 to $80,000 integration | $40,000 to $250,000, often per-check |
| Payout network fees | Minimal setup, sometimes minimum commitments | Per-transaction, commonly $0.50 to $5 plus FX margin share |
| Local team (directors, compliance, ops, tech lead) | Recruitment fees | $600,000 to $1.5 million |
| External audit, AML/CFT audit, penetration testing | $15,000 to $40,000 readiness | $50,000 to $150,000 |
| Safeguarding arrangements and banking fees | Variable | $10,000 to $60,000 |
Take a hypothetical B2B payouts fintech launching five corridors. Year-one cash spend lands somewhere around US$1.2 million to US$3 million, excluding the capital it must hold. A full in-house build would typically double the platform line and add about a year.
Headcount and the number of day-one corridors drive most of that spread. Screening is the line that surprises people: it scales with transaction count, not value, which punishes low-ticket remittance models. Ask screening vendors for tiered pricing against your projected volume curve rather than a flat per-check rate.
A realistic month-by-month timeline to first live corridor
MAS doesn't commit to a fixed review period, and incomplete applications stall. Plan on 12 to 18 months from kickoff to first live corridor for an MPI. Treat anything faster as upside.
| Months | Workstream | Key outputs |
|---|---|---|
| 0 to 2 | Scoping and structure | Service mapping, entity setup, adviser engaged, business plan and three-year projections |
| 2 to 4 | Hiring and documentation | Executive director and compliance officer hired; AML/CFT, risk, outsourcing and technology risk policies drafted; vendor shortlist |
| 4 to 5 | Application filing | Submission through MAS's licensing portal with fit-and-proper forms, policies and any required independent assessments |
| 5 to 12 | MAS review and platform build | Responses to MAS clarification rounds; core, screening and payout integrations built and tested in parallel |
| 9 to 14 | In-principle approval and conditions | Capital injected, security deposit lodged, safeguarding arrangement signed, pre-launch audits completed |
| 12 to 18 | License grant and launch | First corridor live at controlled volume; monitoring thresholds tuned on real data |
Two things decide where in that range you land. The first is how quickly you answer MAS's questions. Expect several rounds; each slow or partial answer can add weeks. The second is whether your build runs alongside the review or waits for approval. Run it in parallel. Contracting vendors before license grant carries some risk, so negotiate termination rights tied to the licensing outcome, but the overlap commonly saves several months.
Banks using an existing license skip most of the application phase. They usually spend six to nine months on vendor selection, outsourcing notifications, integration and internal risk sign-off.
Red flags and a go/no-go rule before you file
Before committing budget to a cross-border money transfer platform in Singapore, check your plan against these warning signs:
- A vendor that calls itself "MAS-compliant." MAS doesn't certify software; compliance sits with the licensee. Ask for evidence of how the vendor supports specific notice obligations and outsourcing audit rights.
- No local substance. A Singapore entity run entirely from another country invites long reviews or a withdrawn application.
- One payout partner for every corridor. If that partner loses a banking relationship or exits a market, you keep your license but lose your product.
- Flat per-check screening with no volume tiers. It will erode margins on low-value transfers.
- An adviser promising a fixed approval date. Nobody can guarantee MAS timing.
- Safeguarding left until late. Banks can take months to open safeguarding and operating accounts for new payment institutions. Start those conversations around month two, not month ten.
The decision rule: file your own MPI application only if you can fund at least US$1.5 million of runway on top of regulatory capital, hire a Singapore-based executive director and compliance officer before filing, and name two payout partners covering your first five corridors. Miss any one of the three and you should start on an embedded partner model, then revisit licensing once volume justifies it. Either way, have a licensed Singapore adviser review your service mapping before you sign platform contracts. Getting wrong which PSA services you provide is the most expensive mistake to unwind.
Quick answers
Can a foreign fintech serve Singapore customers without a MAS license by using a licensed partner?
Often yes, provided the licensed partner contracts with the customer, controls the funds and carries the regulatory obligations, while you act only as a technology or distribution provider. Where the line falls depends on how the arrangement is built, including whose name appears in the customer journey and who handles money. Have a licensed Singapore adviser review the structure before launch.
How long does a MAS major payment institution license usually take?
Plan for roughly 12 to 18 months from project kickoff to a live corridor, with the MAS review itself commonly running six months or more after filing. A complete application, a strong local team and fast answers to clarification rounds shorten it. MAS doesn't commit to fixed timelines, so build buffer into investor and launch plans.
Do banks need a separate license to launch cross-border payments in Singapore?
Banks licensed under Singapore's Banking Act are generally exempt from PSA licensing for payment services, so they don't file a new application. They still have to meet MAS expectations on AML/CFT, technology risk and outsourcing, including notifying or consulting MAS on material outsourcing of the platform. Expect six to nine months for vendor selection, integration and internal approvals.
Does the choice between SPI and MPI change which platform vendors are suitable?
Yes. An MPI carries safeguarding, incident notification and system availability obligations that an SPI largely doesn't. That means daily reconciliation of customer funds against safeguarded balances, documented recovery objectives and fast incident data from your vendors. If you expect to reach MPI scale within two years, choose vendors that already meet MPI-level requirements so you don't have to re-platform later.
Written by the Trustdeskapp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.