Payments Licensing Strategy in Singapore

Payment services licensing in Singapore: the short answer

In Singapore, payment-services licensing is an activity-driven decision under the Payment Services Act 2019 (PSA). The Monetary Authority of Singapore (MAS) regulates seven defined payment-service types and issues three principal licence classes: money-changing, standard payment institution (SPI) and major payment institution (MPI). MAS states that applications are assessed case by case, based on the specific activities, customer exposures and controls of the applicant. The correct route is therefore determined by a mapping exercise across your product, the transaction flow and the counterparties involved—before any licence class is selected or any MAS Notice is applied.

Boards and sponsors should start with classification before compliance. Identify: (i) what service is supplied in functional terms, (ii) whether it matches one or more MAS service types or an exclusion, (iii) whether an exemption applies, (iv) the licence class and threshold implications, and (v) the admission and ongoing obligations that follow. This analysis determines whether you need an SPI or MPI licence, a money-changing licence, or whether a different MAS framework such as the Financial Services and Markets Act 2022 (FSMA) is relevant for parts of your model—particularly for digital token services linked to digital payment tokens (DPTs). It is common for complex propositions to straddle more than one service type and for aggregated exposures to move a proposition from SPI to MPI.

MAS’s official material emphasises that the regulatory perimeter follows flows and functions rather than product labels. For example, a programme branded as a “wallet” can, depending on its mechanics, amount to account issuance, e-money issuance and domestic money transfer; a merchant solution could involve merchant acquisition and cross-border money transfer; and a crypto-asset venue could trigger DPT service while also touching transfer services for fiat legs. The label on a token or card does not decide the licence.

Timelines and outcomes are inherently case-specific. MAS does not guarantee processing time and it evaluates governance, financial resources, technology risk management and anti-financial crime controls in the context of the precise services proposed. Public announcements and guidelines can inform expectations, but the current PSA, applicable subsidiary legislation and any in-force MAS Notices remain the legal baseline. When in doubt, seek a pre-application discussion focused on the transaction flow, not the marketing description. For perspectives on how leading firms shape that discussion and govern execution risk across jurisdictions, see our latest perspectives.

Scope, authority and distinctions that change the route

The PSA is the primary statute for payment services in Singapore. MAS publishes an overview of the seven service types—account issuance, domestic money transfer, cross-border money transfer, merchant acquisition, e-money issuance, digital payment token (DPT) service and money-changing—together with licensing information for SPI, MPI and money-changing licences. Each service type has a defined scope and exclusions. The analysis turns on functional reality: who holds value, who initiates and executes transfer instructions, whose money is moved, and where customers and counterparties are located.

Activity mapping and exclusions

Start by documenting the end-to-end transaction flow. Identify each step that could fall within a PSA service type. Test apparent “edge” features against MAS’s published descriptions and exclusions. Relevant exclusions may include activities performed by certain financial institutions under other MAS frameworks, limited network arrangements, or activities where the service provider never receives or controls money or DPTs. Because an offering can involve multiple service types, the mapping should cover every customer journey (onboarding, loading, paying, withdrawing, settling) and every instrument or token used.

Account issuance captures the provision of a payment account, including a stored-value facility or card-linked account, and often sits alongside e-money issuance where stored value is denominated in fiat and accepted by others. Domestic and cross-border money transfer services focus on executing or arranging transfers within Singapore or across borders; the analysis must follow the instruction and settlement legs, including use of intermediaries. Merchant acquisition covers contracting with merchants to accept and process payment transactions. Money-changing is a separate licence class limited to the business of buying or selling foreign currency notes.

DPT service concerns dealing in or facilitating the exchange of digital payment tokens, among other specified activities. A DPT may be, but is not automatically, a stable-value token or a token used primarily for exchange or settlement. Where a proposition touches DPTs, boards should determine whether it triggers DPT service under the PSA and whether any activities also fall to be considered under FSMA. The FSMA creates additional regulatory tools for digital token services, and the analysis depends on the exact activity, customer geography and any cross-border element. The PSA and FSMA regimes are not interchangeable; an activity may require compliance with one, both or separate obligations. The statutory text should be checked directly where classification is close to the perimeter.

SPI vs MPI and aggregation

MAS issues SPI and MPI licences for specified payment services other than money-changing. The class depends in part on prescribed thresholds and aggregate exposures across service types at the entity level. It is not unusual for a business plan that appears to fit SPI initially to move to MPI once customer volumes, stored value or transaction values are aggregated across products or jurisdictions within the same legal entity. Because these thresholds and aggregation mechanics are subject to legislative detail and change, do not rely on marketing volume projections or a single product silo. Use conservative estimates and stress cases; when threshold uncertainty persists, plan for MPI-class governance and capital, even if you apply as SPI.

Stablecoins and labelling

MAS has announced a regulatory framework for stablecoins. However, before claiming that a particular framework requirement is legally in force, or that a token may use an MAS-regulated label, reconcile the announcement with the current PSA and any implementing instruments in force at the time. Treat public communications as directional; the statutory and regulatory text, as in force, remains determinative. Labels used in marketing should avoid implying MAS approval or authorisation beyond your actual licence and permissions.

These distinctions—functional mapping, SPI vs MPI, and the status of any stablecoin-related arrangements—are typically the decision gates that change an applicant’s route, governance design and timing expectations.

Process, documents and evidentiary expectations

MAS evaluates applications case by case. A strong filing is factual, specific to the services applied for, and anchored in demonstrable governance and control evidence. The process below reflects what MAS publicly signals and what experienced applicants prepare in practice; it is not a promise of outcome or timing.

Classify, then prepare

Begin by finalising the classification memo. Set out the service types you believe you conduct, the exclusions you rely on, and why other MAS regimes (including FSMA) do or do not apply. Support the memo with annotated process maps and legal analysis referencing PSA definitions. This memo frames all subsequent submissions and management attestations. Without it, subsequent compliance mapping of MAS Notices and guidelines can drift from the actual business model.

The core application narrative

The narrative should be consistent across corporate, operational and risk documents. Boards typically assemble the following materials, tailored to the services sought:

• Corporate information, group structure charts and ultimate beneficial ownership declarations.
• Business plan with detailed descriptions of each proposed service, target customers, jurisdictions and projected volumes, including conservative and adverse cases.
• Transaction-flow diagrams from initiation to settlement, showing when the applicant or its agents receive, control or transmit money or DPTs, and where funds or tokens reside at each step.
• Customer terms, merchant agreements, issuer or acquirer contracts, and arrangements with banking, custody and technology partners.
• Governance statements covering board oversight, senior manager responsibilities and three-lines-of-defence arrangements.
• Risk assessments for operational, technology and outsourcing risks, and documented mitigants aligned with MAS’s published expectations.
• Anti-financial-crime framework proportionate to the services and geographies, including customer due diligence designs, suspicious transaction reporting procedures and sanctions screening. Refer to the applicable statutory obligations under current law.
• Financial resources, liquidity plans and, where relevant, arrangements for safeguarding customer money or e-money float consistent with PSA requirements.

Evidence MAS typically tests

Applicants can expect MAS to probe areas that go to prudential soundness and customer protection. Illustratively:

• Whether the applicant’s board and key executives are accountable, fit and proper, and sufficiently skilled in payments and relevant technologies.
• Whether technology risk is governed end to end, including access controls, change management, incident response, data protection and business continuity consistent with MAS’s technology risk expectations.
• Whether outsourcing (including to cloud providers and affiliates) is subject to due diligence, contract controls and ongoing monitoring commensurate with the materiality of the service.
• Whether the anti-financial-crime programme is tailored to the service mix (for example, e-money vs DPT service), including trigger events for enhanced measures and the handling of cross-border scenarios.
• Whether financial resources and safeguarding arrangements match the applicant’s scale and service types, and whether customer monies are appropriately segregated and protected.
• Whether customer disclosures, complaint handling and error-resolution processes meet MAS’s fairness expectations, with terms that do not create misleading impressions about regulatory approval.

Where a proposition includes DPT service, MAS may test whether product risk disclosures are fair and balanced in light of the token characteristics and whether marketing aligns with the service actually licensed. If your model references stable-value tokens, expect questions on the governance of reserves and redemption mechanics, while recognising that the status of any stablecoin framework requirements depends on in-force instruments at the time.

Finally, MAS may ask how the applicant will ensure that additional services will not be rolled out without prior regulatory engagement. A staged permissions approach, documented in the application, can help manage perimeter drift while the business scales.

Operational and commercial implications of authorisation

Authorisation does not end with the licence letter. It sets an operating standard for the life of the business and typically informs counterparties’ risk decisions. The implications below affect strategy, pricing, contracts and the board’s oversight calendar.

Counterparty confidence. A clear licence position can accelerate access to banking, card network participation, merchant onboarding and institutional partnerships. Many counterparties require evidence of authorisation and scope before negotiating limits, settlement cycles or collateral. Public statements must be accurate: avoid implying MAS approval of products or partners where none exists.

Control build versus commercial timing. The controls MAS expects—technology resilience, financial safeguards, and anti-financial-crime measures—take time to build and test. Commercial launches paced ahead of control readiness increase regulatory and reputational risk. Align capital deployment and hiring with the most likely licence class; for example, MPI-grade governance and resources may be prudent even if you enter as an SPI where growth is expected to be rapid.

Product design constraints. Functional classification can shape product architecture. For instance, features that move a “closed-loop” store card into broader e-money issuance or domestic transfer services can change safeguarding and reporting obligations. Similarly, adding fiat on‑ and off‑ramps to a DPT platform can introduce transfer-service analysis for the fiat legs. Designing to the perimeter early can reduce the need for costly re‑engineering after MAS feedback.

Marketing and fair dealing. Advertising and digital engagement must be fair and balanced and should not create a false impression of guarantees or safety. Customer onboarding journeys should reflect the product risk profile and service type. Phrases like “approved”, “sanctioned” or “guaranteed” should be avoided unless you are describing a status that is factually and legally accurate. For broader practice context relevant to financial services and fintech, see our practices.

Board cadence and evidence. Ongoing reporting and audit trails matter. Minutes should show the board regularly reviewing compliance with licence conditions, resource adequacy, technology incidents, outsourcing performance, customer complaints and anti-financial-crime metrics. Documented decisions—such as risk appetite settings or the rationale for adding a new feature—can be decisive in regulatory interactions.

Change management. Business development teams should treat any move into a new service type—or a change that materially affects thresholds or aggregation—as a governed change that triggers legal review. A short internal paper should explain the classification, expected impact on SPI/MPI status, and the plan for regulatory engagement. This avoids unplanned breaches via product experiments or cross-border pilots.

Payment services licensing in Singapore: how the mapping exercise plays out

Most payments licensing problems are not caused by misreading the Payment Services Act 2019. They are caused by choosing a licence class early, describing the business loosely, and then trying to fit the evidence to that choice. The scenario below shows how the route should actually be decided.

The discipline is simple to state: identify the service in functional terms, match it to MAS service types or exclusions, test exemptions, then let licence class and obligations follow.

Illustrative scenario: a marketplace adds a wallet

Illustrative only; the facts are invented to show the decision points.

A regional online marketplace plans to launch in Singapore. Its product team describes the feature set as "seller payouts plus a customer wallet". Leadership has already told investors it will hold an SPI licence.

The first decision point is classification. Mapping the flows shows that the wallet stores value that customers can spend with third-party sellers, which raises e-money issuance and account issuance questions. Payouts to overseas sellers raise cross-border money transfer questions. Card acceptance for sellers is handled by a third-party acquirer, so merchant acquisition may sit with that partner rather than the marketplace.

The second decision point is aggregation. Volume projections had been prepared only for the wallet. Once seller payouts were added and modelled across services at entity level, the business was approaching the thresholds that distinguish SPI from MPI within its planning horizon. The board was asked to choose between capping scope or preparing MPI-grade governance from the outset.

The third decision point is communications. Draft launch copy described the wallet as "MAS-licensed". That was premature and also imprecise, because a licence covers only the services recorded on it. The copy was held until the licensing position was settled and could be described accurately.

Questions that decide the outcome

For support with the mapping exercise or the application itself, see our payment services practice. Handled with discipline, payment services licensing in Singapore becomes a predictable workstream rather than a source of late surprises, and the same evidence base serves diligence, audit and future variations. Firms that treat payment services licensing in Singapore as an architecture decision, not a form, tend to reach market with fewer surprises.

Common mistakes

Experienced sponsors avoid predictable missteps that complicate MAS engagement and increase time to revenue.

• Starting with a licence label, not the activity. Teams sometimes pick “SPI” or “MPI” before mapping the flows. That reverses the analysis and leads to re-work when legal classifications surface late in diligence.
• Underestimating aggregation. Projections that consider only a flagship product can miss the entity-level aggregation that moves an applicant from SPI to MPI. Early planning for MPI-grade governance avoids rushed upgrades later.
• Assuming brand dictates perimeter. A “wallet”, “super-app” or “stablecoin” label does not control classification. MAS follows functional reality; mapping flows is the first task.
• Conflating PSA and FSMA. Digital-token activities can engage FSMA in addition to, or instead of, PSA requirements in specific contexts. Treat them as distinct regimes with different triggers.
• Overstating stablecoin status. Using language that implies MAS-regulated labels or in-force requirements without cross-checking the current PSA text and implementing instruments can mislead customers and counterparties.
• Copying controls from another jurisdiction. Importing a control set designed for another regulator can leave PSA-specific obligations unaddressed. Tailor to MAS’s expectations and your service mix.
• Thin evidence on technology governance. Assertions about security and resilience without artefacts (policies, runbooks, test results, incident post‑mortems) invite further MAS queries and delay.
• Marketing ahead of permissions. Launching campaigns that imply services outside current permissions or that oversimplify risk disclosures can create supervisory friction and require corrective communications.
• Neglecting partner oversight. Outsourcing and partnership risks, including with group affiliates, are often material in payment flows. Contracts, SLAs and monitoring should reflect that materiality.

Action plan and decision points

Decision-maker checklist

• Have we documented an activity-first classification that maps each customer journey to PSA service types and exclusions?
• Do we understand how aggregation across products and entities affects SPI vs MPI status, and have we stress-tested growth scenarios?
• Have we determined whether any element of our model triggers DPT service under the PSA, and whether FSMA applies to any digital token activities or cross-border features?
• Are technology risk and outsourcing arrangements evidenced to a standard that aligns with MAS’s expectations for our chosen licence class?
• Have we locked down safeguarding arrangements, bank partners and settlement constructs consistent with the PSA service mix?
• Do our customer and partner contracts reflect accurate licensing language, clear risk disclosures and appropriate liability allocation?
• Is our marketing fair and balanced, avoiding language that implies MAS approval or stablecoin labels beyond our exact permissions and in-force law?
• Have we planned for post-licensing reporting, board oversight and evidence retention that can withstand supervisory review?
• Do we have a change-management process that triggers legal review before we add features that could change classification or thresholds?

Sources and official materials

Sources checked 17 October 2026. Current law and MAS guidance should be checked before acting.

• Types of Payment Services
• Licensing for Payment Service Providers
• Payment Services Act 2019