Note: This case study is a composite illustration based on patterns we observe when advising fintech teams in Singapore. Names, figures, and timelines are fictionalised, but the regulatory steps and licensing considerations reflect real MAS and ACRA requirements.
Singapore remains the jurisdiction of choice for fintech founders who need a credible regulatory regime and a launchpad into Southeast Asia. The city-state offers a single payments regulator, a statutory licensing framework under the Payment Services Act, and a commercial environment that international investors and counterparties readily understand.
The following walkthrough follows a fictional B2B cross-border payments platform—we will call it PayForge—as it moved from ACRA incorporation to MAS licence approval. The scenario is designed for founders, venture capital investors, and compliance leads who are evaluating Singapore as a base for a regulated fintech business.
1. Why Singapore and the initial incorporation decisions
The founders' rationale
PayForge's two founders had spent their early careers in transaction banking and enterprise software. One was based in Southeast Asia, the other in Europe. After validating demand for a corporate cross-border payments wallet, they needed a headquarters that would satisfy three audiences at once: enterprise clients, venture investors, and regulators in the markets they planned to serve.
They chose Singapore for four reasons:
- Regulatory coherence: MAS oversees payment services under one statute, the Payment Services Act 2019, rather than fragmented rules across multiple agencies.
- Investor confidence: A Singapore-incorporated, MAS-licensed entity sits comfortably in most fund due-diligence frameworks.
- Regional reach: Singapore's network of trade and tax treaties, combined with its position as an ASEAN financial hub, made it a natural base for cross-border B2B flows.
- Operating environment: English common law, reliable dispute resolution, and a deep pool of compliance and engineering talent reduced execution risk.
ACRA incorporation choices
PayForge was incorporated as a private limited company. The founders reserved the company name through ACRA, drafted a shareholder structure that included an employee share option pool, and appointed a Singapore-resident director to meet ACRA's statutory requirement that every company has at least one ordinarily resident director.
They also engaged a corporate secretarial provider early. Singapore law requires a company secretary within six months of incorporation, and the same provider could later support ongoing compliance such as annual returns and board resolutions. A registered office address was selected in the central business district to align with MAS expectations of a substantive local presence.
2. Selecting the correct MAS licence class
The Payment Services Act regulates seven payment service types. PayForge's model involved holding customer funds in a wallet and executing cross-border money transfers for corporate clients. That mapping placed them in two service categories: account issuance and cross-border money transfer service.
Because their projected transaction volumes exceeded the statutory thresholds, they needed a Major Payment Institution (MPI) licence rather than a Standard Payment Institution (SPI) licence. The distinction matters for capital, audit, and compliance intensity.
| Factor | Standard Payment Institution (SPI) | Major Payment Institution (MPI) |
|---|---|---|
| Activity threshold | Below statutory activity thresholds | Above statutory activity thresholds |
| Capital requirements | Lower base-capital requirement | Higher base-capital and operational-risk requirements set by MAS |
| Audit | Annual audit generally required | Annual audit and additional assurance obligations |
| Compliance intensity | Baseline AML/CFT and technology risk controls | Enhanced controls, dedicated officers, and more granular reporting |
PayForge deliberately excluded digital payment token services from its initial licence scope. Limiting the first application to fiat payment services simplified the compliance build and reduced the time needed to prepare the technology risk and outsourcing documentation.
3. Building the compliance and technology risk framework
AML/CFT policies and governance
Before filing the licence application, PayForge implemented a complete AML/CFT programme. This included a written risk assessment, customer due-diligence and enhanced due-diligence procedures, transaction monitoring rules, sanctions screening, suspicious-transaction reporting workflows, and record-keeping policies.
MAS expects licensees to appoint a compliance officer and a money laundering reporting officer with sufficient seniority and independence. PayForge recruited these roles locally rather than trying to cover them from overseas, which accelerated both the application and the regulator's comfort with the firm's operational control.
Technology risk management controls
The technology risk workstream was treated as a product requirement, not a post-build afterthought. PayForge documented its system architecture, data flows, access controls, encryption standards, and incident-response procedures. It also prepared an outsourcing policy because key parts of its infrastructure were hosted with cloud providers.
MAS's Technology Risk Management Guidelines and cyber hygiene notices formed the reference points for these controls. The firm engaged an independent third party to review its controls before submission, which helped surface gaps in logging and privileged-access management before MAS asked about them.
4. Capital, resident directors, and local team
MAS sets capital requirements according to licence class and the payment services applied for. For an MPI, the firm must maintain base capital and hold resources to cover operational risk in line with MAS rules. PayForge modelled its pro forma capital around these thresholds and ensured the funds were unencumbered and available in the Singapore entity.
Resident director requirements operate on two levels. ACRA requires at least one ordinarily resident director for the company. MAS additionally expects at least one executive director to be based in Singapore and actively involved in the licensed business. PayForge appointed a senior local executive as a full-time executive director and supported the foreign founders' Employment Pass applications so they could join the board once approved.
The local team ultimately included the executive director, a compliance officer, an MLRO, an operations lead, and a technology risk manager. Having these roles in place before licence approval allowed PayForge to begin operations almost immediately after receiving the licence.
5. Timeline from incorporation to licence approval
The full journey, from ACRA incorporation to MAS approval, took roughly nine months in PayForge's case. Actual MAS processing times vary with application quality, scope, and the firm's responsiveness to queries.
| Phase | Approximate timeline | Key milestones |
|---|---|---|
| Incorporation | Weeks 1–3 | ACRA company registration, resident director, bank account opening |
| Foundation | Months 1–2 | Hire compliance and operations leads; confirm licence scope |
| Application preparation | Months 2–5 | Draft AML/CFT policies, TRM controls, business plan, financial projections |
| MAS review | Months 5–8 | Application submission, regulator queries, supplementary documents |
| Approval and launch | Month 9 | Licence granted; operational readiness confirmed |
Lessons learned
- Start compliance early. Policies written after the product is built are harder to defend and slower to implement.
- Hire experienced local compliance talent. A regulator-facing officer who understands MAS expectations reduces query cycles materially.
- Treat technology risk as a product feature. Logging, access control, and incident response should be designed in, not retrofitted.
- Keep capital clean and documented. MAS will ask for evidence that capital is unencumbered and attributable to the licensee.
- Limit initial scope. A narrower licence application can be expanded later; an over-ambitious first filing often delays approval.
Practical takeaways for fintech founders and investors
- Incorporate through ACRA with the licence end-state in mind: resident director, registered office, share structure, and capital all feed into the MAS application.
- Map each payment service type to the Payment Services Act before drafting the application; misclassification is a common source of delay.
- Budget for a 9–12 month journey from incorporation to licence approval, with contingency for MAS queries and internal readiness gaps.
- Build the AML/CFT and technology risk programmes in parallel with product development, not after it.
- Plan the local team carefully: executive director, compliance officer, MLRO, and technology risk capacity should be in place before submission.
- For financing and scaling the Singapore entity, consider how the capital and operational budget align with both MAS requirements and growth milestones. Lansoln's local business financing and scaling support can help structure this.
Closing
PayForge's journey illustrates that Singapore fintech licensing is less about finding shortcuts and more about disciplined preparation. Founders who treat incorporation, compliance, and technology risk as a single integrated programme typically move faster and with fewer surprises than those who sequence them sequentially.
The regulatory landscape continues to evolve as MAS refines its guidance on digital payments, cyber risk, and outsourcing. Teams that build adaptability into their governance frameworks from the outset will find it easier to respond to new requirements without disrupting operations.
If you are planning a Singapore fintech launch and need support with structure, incorporation, or MAS licensing strategy, contact us to discuss how Lansoln can work alongside your team.
