Singpass & Myinfo Integration: What Singapore Businesses Should Know

If onboarding a customer means asking them to type their details and upload documents, Singpass and Myinfo can make that almost frictionless — and far more trustworthy. With consent, you pull verified data straight from government sources instead of re-keying it. This guide explains what these services actually do, when integration is worth the effort, what the build involves, and the costs and compliance points to weigh before you commit. The timing is relevant: Myinfo Business v3 opened for onboarding in May 2026, so the corporate side is newly worth a look.

Key takeaways

• Singpass underpins almost everything — it has roughly 5 million users and handles tens of millions of transactions a month across thousands of services (GovTech).
• Myinfo pre-fills people; Myinfo Business pre-fills entities — different APIs, different onboarding.
• It is worth it for high-volume or identity-heavy onboarding, and overkill for a simple contact form.
• Pricing is freemium with no setup fees, but Myinfo is not a complete KYC solution.

What are Singpass and Myinfo, exactly?

Singpass is Singapore’s national digital identity, used by around 5 million people across thousands of government and private services (GovTech). Myinfo sits on top of it: with the user’s consent, it shares verified personal data so they never re-type details your business can trust. Two products often get confused, so it helps to separate them early.

• Singpass Login — lets a user authenticate with the national digital identity they already use for IRAS, CPF and HDB.
• Myinfo (personal) — pulls an individual’s verified profile (name, NRIC, address, income, CPF) into your forms, sourced from agencies such as ICA, IRAS and CPF Board.
• Myinfo Business — pulls verified corporate data (entity profile, appointments, shareholders, financial highlights) authorised through Corppass rather than personal Singpass.

The distinction matters because most SME confusion lives here. If you onboard people (patients, members, applicants), you want Myinfo. If you onboard companies (suppliers, corporate clients, partners), you want Myinfo Business. Plenty of flows end up using both.

What do they actually enable for a business?

Myinfo Business alone exposes 118 verified data items across entity and person categories, drawn from agencies including ACRA, IRAS, CPF Board, ICA, MOM and BCA (Singpass). In practice, that turns a long manual form into a one-tap, consent-based pull of trustworthy data. The wins fall into three buckets.

• Less typing, fewer errors — verified details flow into your forms, so customers don’t re-type and your staff don’t re-key.
• Fewer documents — when data comes from government sources, you can drop a lot of the upload-a-scan-and-wait steps.
• Stronger trust — the data is government-sourced and identity-bound, which cuts impersonation and manual checking.

Does pre-fill actually move the needle on completion? There’s no published Singapore-specific Myinfo figure, so treat this as general context: vendor research on onboarding suggests pre-filling known details can lift submission rates meaningfully, against typical online-form abandonment that one industry roundup puts near 68%. The direction is intuitive: shorter forms get finished more often.

When is the integration actually worth it?

The payoff is biggest where onboarding is high-volume or identity matters. With Myinfo recognised by MAS as a reliable, independent source for verifying customer identity, financial institutions are not required to separately collect physical ID documents or a customer photograph (MAS). That removes real friction from regulated sign-ups. Here’s a simple decision guide.

• Strong fit: regulated or KYC-heavy onboarding (financial services, lending, insurance), high signup volume, and flows where drop-off from manual entry is costing you conversions.
• Worth considering: membership or account sign-ups where speed and data accuracy improve experience, or B2B onboarding that needs verified company details via Myinfo Business.
• Usually overkill: a simple contact form, a newsletter signup, or any low-volume flow where the build and review effort outweighs the saved minutes.

In our experience the honest test is volume times friction. If you onboard a handful of people a month, manual entry is fine. If you onboard hundreds and each abandoned form is lost revenue, the case writes itself. If identity verification is part of the picture, it pairs naturally with a proper KYC process.

Myinfo vs Myinfo Business vs manual onboarding

The three approaches differ on what they verify, where the data comes from, and what they cost to run. The table below summarises the trade-offs. Note that Myinfo Business v3 adopts the FAPI 2.0 security profile over OAuth 2.0 and OpenID Connect, built on the Corppass Authorization API (Singpass Partner Support, 18 May 2026).

Sources: Singpass, MAS and Singpass Partner Support. Confirm current data items, security requirements and pricing on the official Singpass Developer Portal before scoping, as terms change.

What does the integration actually involve?

The build is a well-trodden path, but it has gates you can’t skip: you connect to official APIs under terms and review set by GovTech. Myinfo Business v3 runs on the FAPI 2.0 security profile (Singpass Partner Support, 18 May 2026), so identity, consent and token handling must follow the spec. The typical sequence looks like this.

1. Prerequisites — a registered UEN and a valid Corppass account for your organisation.
2. Register your app — create your application on the Singpass Developer Portal and configure your callbacks and keys.
3. Submit for review — share your user journey and data items so GovTech can review how you collect consent and use the data.
4. Build in the sandbox — implement authentication (OAuth 2.0 / OpenID Connect), the consent screen, and the mapping of returned fields into your system.
5. Go to production — once approved, switch to production credentials and monitor.

The part teams underestimate

The OAuth flow is the easy bit. What takes time is consent design, error handling (users who decline, or whose data is incomplete), and mapping fields cleanly into your data model. The returned information is personal data, so PDPA duties — consent, security, retention — apply from day one, not after launch. Gauge your data practices with the PDPA Readiness Check before you build.

What does it cost, and what should you watch for?

The government services use a freemium model with no setup or onboarding fees: a free monthly transaction tier per UEN, then per-transaction charges above it, with Myinfo split into Myinfo Standard (non-financial profile data) and Myinfo Plus (financial profile data). Specific free-tier counts and rates change, so confirm them on the Singpass Developer Portal rather than relying on any figure quoted here. Beyond the government fees, weigh these considerations.

• Development cost — the real spend for most SMEs is the build, testing and consent design, not the government fees.
• Myinfo is not full KYC — it verifies identity and entity data, but does not cover source of funds, purpose of relationship, or beneficial-ownership checks. Regulated firms still need those.
• Migration deadlines — GovTech has set staged migration deadlines through 2026 to 2027 (including FAPI 2.0 compliance). Sources cite different dates, so check the Developer Portal for the current one that applies to you.
• PDPA design — clear consent language, minimal retention, and secure storage are obligations, not nice-to-haves.

One funding note, framed carefully: custom integration work may be partially supported by the Productivity Solutions Grant (PSG), which funds up to 50% of qualifying costs, capped at S$30,000 per company per financial year, only for pre-approved solutions and vendors (EnterpriseSG). Bespoke builds are usually not pre-approved, so verify eligibility first. For how grants map to off-the-shelf versus custom work, see our PSG vs EDG guide.

When should you build a custom integration instead?

For a simple flow, the lightest path wins, and you shouldn’t build what a plugin already does. Custom work earns its keep when Singpass or Myinfo has to slot into a larger system: a bespoke onboarding journey, a KYC workflow with downstream checks, or an account flow that feeds your CRM, billing and operations. That orchestration, not the OAuth handshake, is where engineering effort goes. It’s also where a poorly wired integration quietly creates compliance and data-quality debt.

That’s the work we do. Our API integration practice connects Singpass and Myinfo into your stack, maps consent and data correctly, and ties the verified data into the rest of your workflow. If the goal is to automate the steps after verification — routing, approvals, record creation — our Automiq workflow-automation platform handles that side. And because this touches personal data, the same KYC and PDPA discipline applies throughout.

Disclaimer: Singpass, Myinfo and Myinfo Business are national digital services governed by GovTech and the relevant Singapore government agencies; e-KYC obligations are governed by MAS, and PDPA by the PDPC. AppTech System is an independent software developer, not affiliated with or endorsed by these agencies, and access, eligibility, pricing and terms are determined by them and subject to change. Figures and deadlines here should be re-verified on the official Singpass Developer Portal and agency pages before any decision.

About AppTech System — AppTech System is a Singapore custom-software team and the people behind the Automiq and BooknGo platforms, building web, mobile, AI and enterprise software for businesses in regulated industries. Talk to us.