You’re trying to set up government access for your company. The form asks for Singpass. Your screen tells you you need Corppass. You log in with the same app on the same phone — but the system says you’re missing something. The two services aren’t the same. Here’s the clean distinction, with examples for Singapore businesses.
At a glance
| Dimension | Singpass | Corppass |
|---|---|---|
| What it answers | Who are you? | Are you authorised to act for this company? |
| Identity scope | Individual (citizen, PR, work-pass holder) | Individual + their authority over a registered entity |
| App used | Singpass app | Singpass app, with Corppass authorisation layered on |
| Operated by | GovTech Singapore | GovTech Singapore, validated against ACRA records |
| Used for, typically | Customer onboarding, age and identity verification, NRIC-replacement logins | Filing GST, work-pass applications, government licence renewals, business banking authority |
| Required for a Singpass.biz integration? | Yes — that is the integration | Usually no, unless you maintain your own GovTech Developer Portal account |
What Singpass does
Singpass is the national digital identity for individuals in Singapore. When someone taps “Sign in with Singpass” on any service — government or commercial — Singpass confirms their identity by asking them to authenticate on their phone, with biometrics or a passcode. The receiving service gets a verified identity assertion: this is the right individual.
Singpass also unlocks MyInfo, the verified-personal-data service that returns the user’s name, NRIC, address, date of birth, CPF history, and other government records — with the user’s consent, every time. For business integrations that verify customers, this is the surface our customers use.
What Corppass does
Corppass is the entity-authorisation layer that sits on top of Singpass. It answers a different question: not who the user is, but what they are allowed to do on behalf of a registered Singapore company.
A user signs in to a government service with their individual Singpass; Corppass then tells that service which companies the user can act for, and what specific permissions they have inside each company. Permissions are configured by the company’s Corppass admin and validated against ACRA’s record of directors and authorised personnel.
Practical examples of Corppass in action:
- A finance manager files monthly GST through IRAS using Singpass plus a Corppass GST permission for the company.
- An HR manager applies for a Work Pass with MOM using Singpass plus a Corppass MOM-portal permission.
- A director authorises a payment-services licence application with MAS using Singpass plus Corppass admin authority for the licensee entity.
When you need Singpass only
Most customer-facing Singpass integrations need only Singpass — Corppass doesn’t enter the picture. You need Singpass on its own when:
- Your customers sign in to your service to use it as themselves — retail age verification, gym membership signup, clinic patient intake, beauty-clinic age check, property viewing KYC.
- You are replacing an NRIC-based login ahead of the 2027 PDPC deadline with a consumer-facing Singpass login.
- You need MyInfo data — verified name, NRIC, address, CPF, employment — for KYC, signup, or licence-application packaging. MyInfo runs on Singpass; Corppass is not involved.
When you need Corppass only
Corppass on its own (without a customer-facing Singpass integration) is what your own staff use to manage your company’s government interactions. You need Corppass when:
- You file GST, corporate income tax, or other IRAS submissions for your company.
- You apply for or renew a licence directly with SPF, MAS, MOM, CEA, or another regulator using your own GovTech access (rather than letting an integrator host it).
- You manage your company’s GovTech Developer Portal account for an in-house Singpass / MyInfo integration. If you use a trusted aggregator like us, this Corppass layer stays on our side.
- You administer an inter-bank corporate transfer that requires a named director to authorise via Corppass.
When you need both
Most regulated industries end up using both — Singpass for customer-facing identity, Corppass for the regulator-facing compliance layer behind it. Examples:
- A licensed moneylender verifies the borrower with Singpass + MyInfo (KYC) and the moneylender’s own staff submit quarterly returns to MAS using Corppass.
- A property agency verifies the buyer or tenant with Singpass + MyInfo (CEA AML) and uses Corppass to renew the agency’s CEA licence each year.
- A clinic group verifies patients with Singpass + MyInfo and uses Corppass to apply for the operator licence under the Healthcare Services Act.
Common misconceptions
A few patterns we see repeatedly in scoping calls:
- “We’ll use Corppass to log our customers in.” You can’t. Corppass authorises an individual to act for a company; it doesn’t replace customer login. Even if your customer is a business owner, they log in to your service with their personal Singpass.
- “I need a corporate Singpass account.” That phrase usually means Corppass. Companies don’t hold Singpass accounts; individuals hold Singpass accounts and Corppass tells systems which companies that individual is authorised to act for.
- “If we use Corppass to apply, we don’t need Singpass at all.” Every Corppass session is built on top of an underlying Singpass authentication. You can’t use Corppass without first proving who you are with Singpass.
The practical pattern for most SMEs
For an SME running a clinic, a salon, a bar, a tuition centre, or a retail shop, the typical setup looks like:
- Customer-facing Singpass — used at signup and identity verification. Plug it in once via a managed integration and customers tap to verify.
- Corppass behind the scenes — used by you and your accountant or HR person to file GST, manage employee work passes, and renew any licences. Configured once with ACRA-validated permissions.
- MyInfo data on top of Singpass — verified personal data at signup, the second step that makes Singpass customer onboarding actually fast.
If that’s the shape you want, the implementation guide walks through the customer-facing Singpass + MyInfo build end-to-end.
The short version
Singpass verifies an individual. Corppass verifies that the individual is authorised to act for a company. They are layered services that use the same Singpass app, not two names for the same thing. Most customer-facing Singpass integrations (the kind we run for SMEs) need Singpass and MyInfo, not Corppass.
Want to verify your customers? You need Singpass. Want to manage your own company’s filings, licences, or staff? You need Corppass. Most established businesses end up using both every month, just for different jobs.
For an SME-focused walk-through of a customer-facing Singpass build — scoping, GovTech application, integration shape, cost — see our implementation guide. Or book a free 20-minute scoping call and we’ll tell you which combination your specific use case needs.