Myinfo v3/v4 Retired After 30 Sep 2026: Fix Your Singpass Forms

What Singpass announced about Myinfo v3/v4

On 29 September 2026 the Singpass Partner Experience team posted a notice to partners saying the legacy Myinfo v3 and Myinfo v4 /com services will be permanently decommissioned after 30 September 2026. This was not a surprise date. Singpass first set it in a May 2025 notice that extended the earlier migration deadline to 30 September 2026.

The notice splits partners into three groups:

Singpass also asks partners to remove or disable any remaining v3/v4 buttons so users are not sent into a flow that no longer exists.

Who is affected: custom forms, plugins and older apps

Myinfo is used by businesses that onboard customers, tenants, members or job applicants and want verified details instead of typed ones. Typical places where an old integration hides:

• A custom application or KYC form built by an agency a few years ago and never touched since.
• A WordPress or form-builder plugin that offered a Myinfo button and has not been updated for v5.
• A mobile app or member portal where the Myinfo call sits in the back end.
• A staging copy of the site that still calls the old endpoint and confuses your logs.

If you only use Singpass Login (no data retrieval) you were not affected by this specific switch-off, but the FAPI 2.0 deadline below still applies to you.

How to check which Myinfo version your form uses

You do not need to read code to answer this. Singpass gives two checks in its FAQ:

1. 1

   Log in to the Singpass Developer Portal

   Open developer.singpass.gov.sg with the Corppass account that owns the app and look at the application details. If the app type is listed as Myinfo v3/v4, it needs migrating.

2. 2

   Look for the old person endpoints

   Ask your developer, or search the code, for calls to `/v3/person` or `/v4/person`. Singpass names these as the legacy endpoints.

3. 3

   Test the live flow

   Click the Myinfo button on your live site with a real Singpass account. If it errors or returns nothing after 30 September 2026, you are on the old service.

4. 4

   Check who receives Singpass emails

   Singpass sends these notices to the support email on the app profile. If that is a former staff member or an agency you no longer use, update it so the next deadline does not catch you.

Moving to Myinfo v5: what the migration involves

Myinfo v5 is the current version of the API. Its integration guide describes it as fully compliant with OpenID Connect and the FAPI 2.0 security profile, and suggests using an OpenID-certified client library rather than writing the security code by hand.

In plain terms, the work usually looks like this:

1. New app record. Singpass provides a migration wizard on the developer portal (live since 23 February 2026, per the FAPI 2.0 notice) that duplicates a v3/v4 app into the new format.
2. New login flow. The redirect and token exchange change. FAPI 2.0 adds stronger checks such as DPoP, which proves the token belongs to your server.
3. Data item mapping. Field names and structure differ, so the code that fills your form fields needs updating.
4. Staging test, then production. Test with Singpass staging accounts, then switch the live button over and delete the old entry point.

For a simple form that pre-fills name, address and contact details, this is a small, well-defined development job. For a portal with many data items or a mobile app, budget more testing time.

Two more Singpass deadlines: FAPI 2.0 and Myinfo Business

The v3/v4 switch-off is the first of several dates. Plan for these at the same time so you only pay for one round of changes.

Myinfo Business is the corporate version that pulls company data from government sources after a Corppass login. Since May 2026 it runs on the Corppass Authorization API with FAPI 2.0. If an earlier Myinfo v5 app was built before 11 February 2026, it may not be FAPI 2.0 compliant yet, so ask your developer to confirm before December.

Use the migration to collect less personal data

A rebuild is a good moment to ask which Myinfo data items you really need. Under the PDPA, PDPC's advisory guidelines on NRIC numbers say organisations should generally not collect, use or disclose NRIC numbers unless the law requires it or it is needed to establish identity to a high degree of fidelity.

Myinfo makes identity checks accurate, but that does not mean every form should pull the full NRIC, date of birth and address. Drop items you never use, avoid storing the NRIC in plain text in emails or spreadsheets, and check who in the business can see the submissions. Our NRIC collection rules guide has the details. This is general information, not legal advice.

Do it yourself or get help?

If your form comes from a maintained plugin or SaaS form tool, check whether the vendor already supports Myinfo v5 and FAPI 2.0, update it, and test. If the integration is custom code, you will need a developer who can work with OpenID Connect libraries and the Singpass staging environment.

We can migrate a custom Myinfo form or portal as a fixed-price Custom Tool or Dashboard job (from S$1,990), or check what your current set-up uses in a Quick Fix (1 hour) session (S$119). If you also need to sign documents with Singpass, see our e-signature comparison.