Singpass Developer Docs
Verify API (legacy)
Verify API (legacy)
  • Introduction
    • Overview
  • Key Principles
  • Verify API Data Catalog
  • Brand Guidelines and Resources
  • FAQ
  • Technical Specifications
    • Verify API
    • Technical Requirements
  • Testing with Test Personas
  • Error Code
Powered by GitBook
On this page
  • 1. Requesting for Data
  • 2. Designing your User Journey
  • 3. Possible Enhancements

Was this helpful?

Key Principles

PreviousOverviewNextVerify API Data Catalog

Last updated 1 month ago

Was this helpful?

1. Requesting for Data

Request only what you need

  • Do not over-collect data, where this is not required for business purposes or legal reasons.

PDPA & Applicable Regulations/Legislation

  • Protect, retain, transfer and dispose of data retrieved according to the rules of the Personal Data Protection Act (PDPA), relevant industry regulations and applicable legislation.

  • For collection of National Identification Numbers, refer to the advisory guidelines from PDPC

Use for lawful purposes

  • Use the data items retrieved for lawful purposes only.


2. Designing your User Journey

Display As-Is

  • Data items retrieved from our APIs should be displayed as-is on digital forms (exception of Mobile Number and Email Address) so as to assure users that the correct data items have been retrieved.

  • This minimises clarifications on the data retrieved and encourage users to update the relevant Government data source agency if any information is outdated.

Store only if submitted

  • Data should be purged if form is not successfully submitted.

  • If ‘Save-as-draft’ feature is available, unsubmitted data should be purged periodically.

Provide non-Verify alternative

  • Partners are encouraged to support customers who prefer to use a non-Verify alternative.

Showing customers the benefits of using Verify

  • Indicate that Verify service is available for your service and clearly state the target users (e.g. for SC/PR and/or Foreigners).

  • Present the benefits of using Verify option (e.g. time saving, does not require ID cards or documents).

Remove collection and retention of physical NRIC or other identification documents.

  • Data from Government sources which are uneditable on your form should be assessed as an alternative to collection and retention of identification documents for verification (e.g. NRIC, Work Pass (EP, PEP, EntrePass, S-Pass), Dependent Pass, Visit Pass (LTVP, LTVP+), selected Work Permit, driver's licence, and passport).

Display & Technical Requirements


3. Possible Enhancements

Visitor Registration and Access

  • Use Verify data items to replace collection and retention of physical NRIC or other identification document.

Customer Acquisition

  • Use Verify QR scanning to speed up customer acquisition in the roadshows or seminars.

Scenarios where Collection of NRIC Numbers is Not Required by Law

  • Use Verify Partial NRIC/FIN for use cases, such as redemption of free parking or signing up for retail membership and lucky draw.

Design your application according to our .

here.
technical requirements