Docs

iOS and Android remote-signing SDKs

The iOS and Android SDKs let people sign PDFs on their phone with a remote certificate held by ITIDA, confirmed by a one-time password. No token is needed.

How it works

  1. Your app starts a signing session with the person's national ID and up to 3 PDFs.
  2. The SDK fetches the person's certificate from ITIDA's remote signing service.
  3. It checks each PDF, adds the visible signature stamp and prepares the PDF on the phone.
  4. The person confirms with an OTP sent by SMS or email; ITIDA signs the document hash with the person's remote key.
  5. The SDK sends the signature to the Signing API (/remote/pdf/embed), which embeds it into the PDF, then validates the result (/remote/pdf/validate).

Platforms

  • iOS and Android SDKs follow the same signing flow and call the same Signing API operations.
  • Each SDK is delivered per brand through a private package registry (an AAR for Android). Access is granted per partner, including white-label builds.

Android specifics

  • Before signing, the SDK checks every PDF: version 1.7 or later, not password-protected, structurally sound, not locked against changes, not modified after an existing signature, and no existing signature with a weak hash (SHA-1 or MD5).
  • Errors are grouped by range: 2xxx from ITIDA remote signing (for example an invalid OTP), 3xxx for PDF checks and embedding, 4xxx for device-security checks (rooted device, emulator, attached debugger).