Sign with Singpass
Singpass Developer DocsAsk a Question
  • START HERE
    • Overview of Sign
    • How do our Digital Signatures work?
    • Frequently Asked Questions
  • FOR USERS
    • How to sign
    • Verifying Sign with Singpass Signatures
      • Loading Singpass Root Signing Certificate
  • FOR RELYING PARTIES
    • Use Cases
    • Getting Started
      • How to Onboard our API
      • Digital Signing Partners
        • Docusign
        • Tungsten Automation
        • OneSpan
        • Tessaract Technologies Pte Ltd
        • Netrust Pte Ltd
        • Modus Consulting
        • Redoc.co by Real Estate Doc Pte Ltd.
        • CrimsonLogic
        • Zoho Sign
        • Securemetric Technology Pte. Ltd.
        • Rently Pte. Ltd.
    • API Documentation
      • Document Signing V3
        • Initiate Sign Request
        • Redirect From Sign with Singpass
        • Accept Success Signing Webhook
        • Get Signing Result
        • JWKS Specification
        • Sign Portal
      • Document Signing V1
      • Transaction Signing
        • Embedding Singpass JS
        • Init Transaction Signing
        • Exchange Transaction Signature
    • UX Guidelines
      • User Journey Illustration
    • Support
Powered by GitBook
On this page
  • Transaction Signing API Specifications
  • Flow Diagram

Was this helpful?

  1. FOR RELYING PARTIES
  2. API Documentation

Transaction Signing

PreviousDocument Signing V1NextEmbedding Singpass JS

Last updated 22 days ago

Was this helpful?

Transaction Signing API Specifications

This document outlines the technical specifications for the Singpass Transaction Signing API, designed to enable secure and seamless transaction signing for applications integrating with Singpass. It details the API endpoints, authentication mechanisms, request/response structures, and security protocols to ensure integrity, confidentiality, and user trust.

This specification serves as a guide for developers and system integrators to facilitate smooth implementation and interoperability.

Flow Diagram

Refer to this diagram for an overview of the transaction signing flow and the interactions between RP, Singpass and other dependencies.

RPs are expected to implement the following steps referenced from the flow diagram above:

Step(s)
Component
Summary
Specifications

1

Frontend

Retrieve Singpass transaction signing javascript (Singpass JS)

2

Frontend

Initialise a transaction signing session via Singpass JS

6

Backend

After receiving the sign code, invoke Singpass API to exchange it for the user-signed transaction hash

Embedding Singpass JS
Init Transaction Signing
Exchange Transaction Signature