FAQs about Signify Decommissioning
Signify Phase-out
docCentral will be transitioning from Signify to Sign with Singpass to provide users with Secure Electronic Signatures (SES). This change follows the decommissioning of Signify in Q4 2025, (opens in a new tab) which will no longer be resourced to support ongoing maintenance and future development.
There will not be any change in workflow for docCentral users using Signify, until Q4 2025. After which, users will still be able to generate documents and send them out for signatures using Singpass (via Sign instead of Signify).
What is Sign with Singpass?
Sign with Singpass (opens in a new tab) allows Singpass users to sign documents such as contracts and other agreements remotely, via their Singpass App. Like Signify, digital signatures created through Sign with Singpass are regarded as Secure Electronic Signatures (SES) under the Electronic Transactions Act (2010) (ETA).
What this means for docCentral users
Action required:
- No immediate changes are required for existing docCentral projects with Signify integration
- However, users are strongly encouraged to download any required documents from the Signify platform before early Q4 2025
Support from docCentral:
- All docCentral users will still be able to use Signify as an output destination until late Q4 2025
- The docCentral team will work closely with users to ensure a smooth and seamless transition to Sign with Singpass
For users who have never used Signify before June 2025:
- docCentral users using Signify as an output destination for the first time will need to be whitelisted by Signify.
- Please inform the docCentral team via our contact form (opens in a new tab) if you wish to use Signify as an output destination.
Timeline
Specific dates will be released closer to Q4 2025.
| Period | |
|---|---|
| 3 June 2025 | docCentral users using Signify for the first time must request access via our contact form (opens in a new tab) |
| Q3 2025 | All users can continue using Signify as an output destination as per usual. |
| Early Q4 2025 | docCentral will release documentation on the new workflow integrating Sign with Singpass. Users can begin transitioning to the new workflow, while Signify remains available for a limited time to ease the transition. docCentral will send out reminders on the transition and help users ease into the new workflow. |
| Late Q4 2025 | Signify is removed from the docCentral platform and all Signify flows will not be valid. |
Comparison of Workflow
Users can expect a largely similar process for their document signing workflows, with some key enhancements.
| Signify | Sign with Singpass | ||
|---|---|---|---|
| 1 | Data source | Indicate signer(s)' email address | Indicate signer(s)' email address and NRIC (new!) |
| 2 | Output destination | Select Signify | Select Sign with Singpass |
| 3 | API integration | Copy over the Signify API key from Signify's portal | No API integration is required (new!) |
| 4 | Signing order | No fixed order | Define the sequential order of signatures (new!) |
| 5 | Signature request | All signers receive an email from Signify at the same time | Individual signers receive an email from docCentral, based on the specified signing order |
| 6 | Signing method | Sign using Singpass, through Signify's PDF viewer | Sign using Singpass, through Sign with Singpass' PDF viewer |
| 7 | When all parties have signed | All signers and the project owner will receive an email from Signify containing a button to download the final signed document | All signers and the project owner will receive an email from docCentral with the final signed document attached (new!) |
| 8 | View status of signatures | View on the Signify project page | TBC |
FAQs
About the transition to Sign with Singpass
1. Is there anything I need to do if I'm using Signify now?
From now till early Q4 2025, no action is required from users with existing docCentral projects integrated with Signify.
By early Q4 2025, users can start transitioning to Sign with Singpass. Signify will still be available until end Q4 2025 to support the transition, and docCentral will provide support to our users.
2. What do I need to do during the transition in Q4?
Template Document
- No change required
Data Source
- CSV: Indicate signer(s)’ NRIC in the CSV file
- FormSG: Add a field for user to indicate the signer(s)’ NRIC
docCentral Portal
- Update project’s output destination to Sign with Singpass, and state the intended order of signing
3. I have never used Signify before, but I want to create a signing workflow now.
From 3 June to late Q4 2025, users who have never used Signify with docCentral must fill up our contact form (opens in a new tab) to request access to Signify's API.
Note: This applies even if you have used Signify separately but not within docCentral.
About the Sign with Singpass Integration
1. Why do we now need to indicate the signer(s)' NRIC?
The NRICs provide an additional layer of authentication to ensure only designated signer(s) can view and sign the document.
With this, there is no need for agencies to check if it has been signed by the right person.
It is especially important for documents with sensitive information (e.g. patient particulars or salary details).
2. What if I am unable to obtain my signer(s)' NRICs?
This is not advisable as:
- there is a risk of unauthorized viewing and signing of the documents.
- the document signing URL will have a very short validity period (30 minutes). It is recommended to obtain and indicate the signer(s)’ NRICs if you are unsure that the generated document can be signed within this validity period.
3. Will there be costs for using docCentral?
docCentral remains free for WOG agencies to use, even with the use of Sign with Singpass.
4. What are the changes to docCentral’s signing flow?
Signature placeholder setup remains the same
- No change to existing templates required.
Collection of signer(s)’ NRIC required
- CSV: Indicate signer(s)’ NRIC in the CSV file.
- FormSG: Add a field for user to indicate the signer(s)’ NRIC.
All emails come from docCentral instead of Signify
- This includes emails sent out to request signatures and download the signed document.
Signing method remains the same
- Signing is still done using Singpass, but now on Sign with Singpass’s platform instead of Signify’s.
5. Is there still an expiration period to download documents signed by Sign with Singpass?
No, the final signed document will be sent as an email attachment to all signers and project owners. You may download the document at any time, as long as you retain the email.
6. If using NRICs for authentication, how long are users given to sign the document?
This has not been firmed up yet. Let us know if you have any requirements on this.
7. What will my signer(s) see in the signature request email from docCentral?
The email from docCentral to signer(s) will be very similar to the current email sent from Signify.
You can still provide a customised message to your signer(s), and have different messages for different groups of signers. If no custom message is written, a default message will just be sent to the recipient.
For more information, please refer to this section of the User Guide.
9. Other than Sign with Singpass, what are the alternatives for digital signatures?
docCentral will only support Sign with Singpass as a Secure Electronic Signature (SES) provider.
For non-docCentral projects, you can explore other Sign with Singpass service providers (opens in a new tab).
Contact Us
If you require more information how the transition would affect your docCentral workflows, feel free to let us know in this form: Contact and Feedback Form. (opens in a new tab)