What Is Singpass Integration for Mobile Apps?

Singpass is no longer just a government login tool. Over 5 million residents use it, and it now processes more than 41 million transactions every month across over 2,700 digital services, spanning both government agencies and private businesses. When an app integrates Singpass, it's plugging into infrastructure almost every adult in Singapore already trusts and already has installed on their phone.

For businesses, that trust is the real value. A new user doesn't need to invent another password or upload a photo of their NRIC. They authenticate with a fingerprint, face scan, or the Singpass app, and they're in.

Singpass vs Myinfo: What's the Difference

These two terms get used interchangeably, but they do different jobs, and understanding the split matters for planning an integration.

Why Singapore Businesses Are Rushing to Integrate Singpass Now

The FAPI 2.0 Deadline Explained: What Changes by 31 December 2026

FAPI 2.0, short for Financial-grade API 2.0, is a stricter, more secure authentication standard. GovTech has confirmed that all Singpass Login and Myinfo apps must be FAPI 2.0-compliant by 31 December 2026. Existing apps aren't being asked to rebuild from scratch, they can migrate their current integration to the new authentication API, and both the old and new API can run side by side during the transition so teams can test safely before switching over in production.

The practical changes to plan for include moving to pushed authorization requests, adopting a proper in-app browser flow using ASWebAuthenticationSession on iOS instead of an older WebView-based approach, and updating scope configuration in the Singpass Developer Portal if the app relies on foreign ID data, since that now lives in a separate identity claim.

Myinfo v3/v4 to v5 Migration Deadline (30 September 2026)

There's an earlier checkpoint for apps still running Myinfo v3 or v4: end of September 2026 to migrate to Myinfo v5. That's roughly two months out from today, and a separate, earlier deadline from the FAPI 2.0 one. Any new Myinfo integration built from now onward should skip v4 entirely and onboard straight onto v5.

One nuance worth flagging: Myinfo v5 apps are meant to serve a single purpose. A v4 app currently handling multiple use cases inside one integration will likely need to be split into several v5 apps during migration, rather than a simple one-to-one swap.

What Happens If You Miss the Deadline

GovTech hasn't published a dramatic public penalty structure, but the practical risk is straightforward: non-compliant Login and Myinfo integrations risk service disruption once the deadline passes. For a fintech onboarding flow, an insurance claims app, or a healthcare portal, even a short outage on the identity verification layer means users can't sign up, log in, or complete a claim. That's a direct hit to revenue and trust, and it's entirely avoidable with a bit of planning.

What You Can Build With Singpass & Myinfo APIs

Once an app is inside the Singpass ecosystem, there's a full suite of APIs available, and most businesses only ever use a fraction of what's on offer.

How Much Does Singpass & Myinfo Integration Cost in Singapore?

Login and Myinfo Free Tiers

Singpass runs on a freemium pricing model per UEN. The first 50,000 completed Login transactions per month are free, and the first 5,000 completed Myinfo Standard transactions per month are free. For most SMEs and even mid-sized apps, that covers a significant chunk of monthly activity before any usage fees apply. There are also no setup or onboarding fees for integrating with Singpass APIs; charges only apply once production usage exceeds the free thresholds.

Myinfo Standard vs Myinfo Plus Pricing

Pricing is determined by the highest-value data scope retrieved in a transaction, so requesting even one Myinfo Plus field bills the entire transaction at the Plus rate. It's worth being deliberate about which data scopes an app actually requests.

Development Cost to Integrate Singpass Into Your App

Government-side transaction fees are only part of the picture. The bigger cost variable is development effort: building the OIDC authentication flow, handling the in-app browser session correctly on both iOS and Android, managing token exchange securely, and going through GovTech's app approval and user journey review process. For a straightforward Login and Myinfo integration, most Singapore development teams budget a few weeks of dedicated engineering time. Adding Verify, Sign, or SGFinDex extends that timeline, since each API carries its own approval and testing requirements.

Industries Benefiting Most From Singpass Integration in 2026

Is Singpass Safe for Your Business to Integrate?

This is a fair question to ask before you build on top of any identity system. In a written parliamentary reply, Singapore's Ministry of Digital Development and Information confirmed there were no cybersecurity breaches detected in the Singpass system over the past five years. Myinfo data isn't stored in one central vault either. It sits across multiple government systems, each protected with end-to-end encryption and layered security controls.

The Real Threat: Phishing, Not System Hacks

Most Singpass account compromises don't come from a break-in on the government side. They come from scams. A user gets tricked into sharing an OTP or approving a login they didn't request. Security researchers have found stolen Singpass credentials for sale on the dark web, almost always traced back to phishing or social engineering, not a flaw in Singpass itself. This matters for how you design your app: your own anti-fraud messaging and clear consent screens do real work here, even though the underlying identity system is solid.

Singpass Passkeys: What's Rolling Out in 2026

To cut phishing risk even further, GovTech began rolling out passkey login for Singpass on 1 July 2026, starting with iPhone users. Passkeys use a device-bound credential instead of a password or OTP, which makes it much harder for a scammer to remotely take over an account, even if they trick a user into giving up other details. If your app uses Singpass Login, your users benefit from this improvement automatically, with no extra work needed on your end.

MAS Compliance for Financial Institutions

If you're a bank, insurer, or fintech, there's good news on the compliance side too. The Monetary Authority of Singapore has confirmed that outsourcing arrangements which are wholly provided by GovTech, or by agents appointed by GovTech, are not subject to MAS's usual Outsourcing Guidelines. In plain terms: using official Singpass and Myinfo APIs doesn't trigger the same outsourcing risk review that a third-party vendor normally would.

How to Integrate Singpass Into Your Mobile App: Step-by-Step

Step 1 — Register Your App on the Singpass Developer Portal

Every integration starts here. Register your business, define your app's purpose, and select the specific data scopes needed. GovTech reviews this to ensure only genuinely relevant data is being requested.

Step 2 — Choose Your Integration Type (OIDC, In-App Browser)

Singpass uses the OpenID Connect (OIDC) protocol for authentication. For mobile apps, GovTech requires a proper in-app browser implementation rather than a basic embedded WebView, using ASWebAuthenticationSession on iOS or the Android equivalent, to keep the authentication session secure and separate from the app's own storage.

Step 3 — Build and Test in the Singpass Sandbox

Once your app is registered, you get access to a staging environment. This is where you build and test safely, before anything touches real user data. GovTech provides ready-made test personas that simulate real Myinfo responses, so you can test your onboarding flow end to end without needing a live Singpass account. You'll also find OIDC libraries and sample code in several programming languages on GovTech's public GitHub, including working examples for the FAPI 2.0 flow, which saves your dev team from building the authentication layer from a blank page.

Step 4 — Build for FAPI 2.0 Compliance From Day One

For any integration starting in the second half of 2026, there's no reason to build on the older API and migrate later. Build directly on the FAPI 2.0-compliant flow with pushed authorization requests from the start, and avoid a second migration project entirely.

Step 5 — Submit for Approval and Go Live

Once your staging tests pass, you submit your app for production approval. GovTech typically takes up to two weeks to review a production app, so it's worth building this into your project timeline rather than assuming an instant turnaround. Once approved, the new integration can run alongside any legacy flow during a transition window, which makes for a much safer rollout than a hard cutover.

Common Mistakes Businesses Make With Singpass Integration

Why Businesses Choose Inno Panda for Singpass & Myinfo Integration

We build mobile apps and handle API integrations for Singapore businesses across fintech, healthcare, and insurance, including Singpass, Myinfo, and SGFinDex integrations built to current GovTech standards from day one. Whether it's a fresh integration or a migration ahead of the FAPI 2.0 deadline, the work is far more manageable when it's planned rather than rushed in December.

Building In-House vs Working With an Integration Partner

Quick Glossary: Key Singpass Terms Explained

Before the FAQs, here's a fast reference for the terms used throughout this guide.

Singpass

Singapore's national digital identity system, used to authenticate users across government and private-sector digital services.

Myinfo

The data-sharing layer built on top of Singpass, letting users consent to share government-verified personal data with a business.

FAPI 2.0

Financial-grade API 2.0, a stricter authentication security standard that all Singpass Login and Myinfo apps must comply with by 31 December 2026.

OIDC (OpenID Connect)

The authentication protocol Singpass uses to verify a user's identity and issue a signed ID token to the integrating app.

Pushed Authorization Request (PAR)

A more secure way of sending authorization request parameters, required as part of the FAPI 2.0-compliant flow.

Myinfo Standard vs Myinfo Plus

Standard covers non-financial profile data; Plus covers financial data such as income, and is billed at a higher rate.

SGFinDex

A service that consolidates a user's financial data, including bank accounts, insurance, and CPF, into a single consented view.

UEN

Unique Entity Number, Singapore's business registration identifier, used to track a business's free transaction tiers on Singpass APIs.

Passkey

A device-bound login credential that replaces passwords and OTPs. Singpass began rolling passkeys out on 1 July 2026, starting with iPhone users, to reduce phishing risk.

Sandbox / Staging Environment

A safe testing environment where a business can build and test its Singpass integration using test personas, before going live with real user data.

MAS Outsourcing Guidelines

Rules from the Monetary Authority of Singapore governing how financial institutions manage third-party vendor risk. Services provided directly by GovTech, including Singpass and Myinfo, are exempt from this review.

Frequently Asked Questions