SignDex API v2.0 is now live. Read the release notes

EN

FAQ

SignDex Frequently Asked Questions

Find quick answers to common questions about SignDex accounts, signing, billing, security, and document workflows.

Browse by Category

FAQ should be short, direct, and easy to scan.

Getting Started with SignDex

Basic questions for new users, buyers, and invited signers
What is SignDex?
SignDex is a digital signing platform that helps organizations prepare, send, sign, approve, track, and store documents electronically.

SignDex can be used by business users, signers, approvers, administrators, and external guests who are invited to take action on a document.

Not always. SignDex supports guest signing when the sender invites an external signer.

You will receive an email notification with a secure link. Open the link, review the document, complete the required fields, and submit your action.

SignDex does not currently offer a permanent free plan. However, new users is eligible for a free trial to explore SignDex features before subscribing to a paid plan.

Yes. SignDex may provide a trial period for 30 days where users can create, send, sign, approve, and track document workflows. The exact trial duration and available features depend on the subscribed trial plan.

SignDex currently supports offline payment for B2B customers. Payment details and billing arrangements will be provided during the subscription or onboarding process.

Digital Signature & Legal Use
General information about digital signatures, legal recognition, validation, and audit evidence
What is a digital signature?

A digital signature is a secure, certificate-based method used to verify who signed a document and whether the document was changed after signing.

A handwritten signature is a physical mark written by a person. A digital signature uses cryptographic technology, a digital certificate, and validation information to help prove signer identity and document integrity.

An electronic signature is a broad term for signing electronically, such as clicking to sign or placing a signature image. A digital signature is a stronger type of electronic signature that uses a digital certificate and cryptographic protection to make the signed document tamper-evident.

Digital signatures help reduce paper handling, speed up approvals, protect document integrity, and provide stronger evidence of who signed and when the signing took place.

If a signed PDF is modified after signing, the PDF viewer may show that the signature is invalid or that the document has been changed. This helps recipients detect tampering.

SignDex is designed to support long-term validation features such as timestamping and certificate revocation information, where enabled. This helps signed PDFs remain verifiable over time.

You can open the signed PDF using a PDF reader that supports digital signature validation, such as Adobe Acrobat Reader. The PDF reader will show whether the signature is valid, whether the document has been changed after signing, and whether the signing certificate can be trusted.

No. Once a document is digitally signed, the signature remains embedded in the PDF. SignDex uses PKI-based digital signing with timestamp information to help verify who signed the document and when it was signed.

Even if the signer’s digital certificate expires later, the signed document can still be validated, provided the signature, timestamp, and certificate information remain valid and the document has not been altered after signing.

Qualified digital signatures may not be accepted for certain documents that require physical signing, notarisation, witnessing, stamping, or specific legal procedures. Users should confirm the requirements based on the document type and applicable law before signing digitally.

For example, under Malaysia’s Electronic Commerce Act 2006, electronic execution does not apply to certain documents, such as power of attorney, wills and codicils, trusts, and negotiable instruments.

Malaysia recognizes digital signatures under the Digital Signature Act 1997 and electronic signatures under the Electronic Commerce Act 2006.
The legal effect of an electronic or digital signature depends on the country, document type, signing method, identity assurance, and certificate framework. SignDex may support international signing use cases, but customers should confirm local legal requirements before relying on a signature for cross-border transactions.
No. Some documents may require wet-ink signatures, witnesses, notarization, stamping, or a specific regulated signing method. The sender should confirm whether the document is suitable for digital signing before sending it through SignDex.
A Certificate of Completion or audit trail records key events in the signing process, such as when the envelope was created, when participants were notified, when actions were completed, and when the envelope was completed. It helps provide evidence of the transaction.
PAdES stands for PDF Advanced Electronic Signatures. It is a PDF signing standard that supports advanced validation features for signed PDF documents.
Long-term validation helps preserve evidence needed to validate a signature after certificates expire or revocation information changes. It commonly involves timestamping and certificate validation data embedded in the signed PDF.
Signing Documents
Questions for users who receive, review, sign, approve, or reject documents
How do I sign a document in SignDex?

Open the signing link from your email, review the document, complete all required fields, apply your signature, and submit the signed document.

Yes. SignDex signing is web-based. You can sign using a supported browser without installing a desktop application.

Yes, SignDex can be accessed from supported mobile browsers. Dedicated mobile applications may be introduced separately.

No. SignDex requires an internet connection to open the secure signing session and submit the completed action.

Yes. If you are not willing or not able to sign or approve a document, you may reject it. Rejection may stop the workflow depending on the workflow setup.

Yes. Users may update their signature or initials image. For consistency, the same selected signature image should be used within the same envelope once signing starts.

Signature and initials images should be uploaded in supported image formats such as PNG or JPG. The maximum image size is 2 MB.

Yes. Users may download the document before the workflow is completed, but the downloaded file will be the original unsigned document. The final signed document will only be available after the workflow is completed.

The envelope is marked as completed. Participants can be notified and the completed signed PDFs can be downloaded according to the organization’s settings.

For security, some signing links may expire. If your link has expired, request a new link from the signing page or contact the sender or support team.

Envelopes & Workflows
Questions about files, envelopes, participant roles, workflow types, reminders, and expiry
What file type does SignDex support?

SignDex supports PDF documents for signing workflows.

The current expected limit is 25 MB per PDF file.

The current expected limit is up to 5 PDF documents in one envelope.

Completed documents are provided as signed PDF files.

No, this should be avoided since uploading a previously signed PDF may affect the existing signature validity.

SignDex supports common workflow types such as sequential signing, parallel signing, approval workflows, quorum workflows, and mixed workflow arrangements where supported.

In a sequential workflow, participants take action in a defined order. The next participant is notified only after the previous required participant completes their action.

In a parallel workflow, multiple participants can take action at the same time.

In a quorum workflow, the sender sets the minimum number of required participants who must complete the action. Once the required number is reached, the remaining participants may no longer be required.

Common roles include Signer, Approver, and Receives a Copy. A signer signs the document, an approver approves or rejects the document, and a copy recipient receives the completed document or notification.

Yes. A sender can invite multiple participants to one envelope.

The current expected limit is up to 10 participants per envelope, including signers and approvers.

Yes. An approver may approve or reject a document without placing a signature, unless the sender assigns required fields to the approver.

No. Recipients who only receive a copy do not sign or approve. They are notified after completion.

Yes. A signer can reject the document. Rejection may stop the workflow, depending on the workflow type and product configuration.

Yes. SignDex can send reminders based on the envelope expiry date and reminder settings configured by the sender or organization.

Yes. The sender can set an expiry date for the envelope. The current expected expiry range is 3 days to 3 months. If the sender does not configure an expiry date, the default expiry period will be 30 days.

Document deletion depends on user role, document status, and organization policy. For example, an initiator is allowed to delete an in-progress envelope, while completed document deletion is open to both initiator and administrators.

Deleted documents are not recoverable. Users should confirm their retention, backup, and audit requirements before deleting documents.

Certification Authority & eKYC
Questions about identity verification, digital certificates, Certification Authorities, and timestamping
What is eKYC?

eKYC means electronic Know Your Customer. It is an online identity verification process used to verify a person’s identity before allowing certain signing actions.

eKYC may be required when a signing transaction requires higher identity assurance, a regulated certificate, or compliance with a specific legal framework such as Malaysia’s Digital Signature Act process.

eKYC verification is usually completed within 2 minutes for most users.

However, it may take longer if the submitted photo is unclear, the required document is incomplete, or additional review is needed due to issues such as facial mismatch or an expired ID.

Accepted identity documents may include MyKad for Malaysian users and passport for non-Malaysian users.

The accepted document type may vary depending on the user’s country, verification provider, and applicable regulatory requirements.

Requirements depend on the country and identity verification provider. For Malaysia, this may include MyKad images and a selfie. For non-Malaysian users, passport information and a selfie may be required.

If eKYC is required for that document, you may not be able to continue signing until verification is completed. If eKYC is not required, the sender may allow a lower-assurance signing method.

1 year, but this depends on the identity verification policy, certificate requirement, and retention rules.

eKYC helps reduce identity fraud, improves confidence in the signer’s identity, and supports higher-assurance signing use cases.

eKYC information is submitted securely and protected using encryption. The information is used only for identity verification and digital certificate registration purposes, where required. SignDex may use trusted eKYC providers with liveness detection and anti-spoofing checks to help prevent identity fraud.

No. eKYC is charged per verification and may not be included by default in all plans.

A Certification Authority, or CA, is a trusted entity that issues digital certificates used to identify signers and support digital signatures.

A CA helps establish trust by issuing and managing certificates. In digital signing, the certificate helps connect a signer’s identity to the digital signature.

SignDex may support certificates issued by SignDex-managed CA infrastructure and/or integrated public or licensed Certification Authorities, depending on the customer setup and signing requirement.

A SignDex certificate is used for general signing use cases, while a regulated DSA certificate is issued through a licensed CA process for transactions that require that level of assurance.

Digital certificates commonly use the X.509 standard. Confirm the exact profile and certificate policy before publishing technical claims.

Yes, SignDex is designed to support timestamping where configured. Timestamping helps prove when a document was signed and supports long-term validation.

If a certificate expires, SignDex or the integrated CA will issue or renew a certificate seamlessly before the next signing action.

Account & Security
Questions about roles, permissions, document access, storage, security, and audit logs
Can users manage their own profile?

Yes. Users can manage personal profile details.

The common roles are Member and Administrator.

Administrators may manage users, roles, organization settings, subscription and billing settings, security settings, File storage configuration, API credentials, and activity logs.

Yes. Users can reset or change their password using the account recovery or password settings flow.

No, changing a registered email address is restricted for security and audit reasons.

Account deletion depends on organization policy, document ownership, audit requirements, and retention rules. Only administrators can perform user deletion.

A deleted user may be able to register again, depending on organization policy and whether the email address is allowed to be reused.

No. only Administrators are allowed to create templates for repeated document workflows.

Yes. SignDex shows document and workflow status so users can track pending, waiting, completed, rejected, expired, or other relevant states.

How does SignDex protect signed documents?

SignDex uses secure workflow controls, access controls, audit logs, digital signing technology, and document integrity checks to help protect signed documents.

Yes. Digital signatures help make signed PDFs tamper-evident. If a signed PDF is changed after signing, the signature validation status will show that the document has been modified.

Yes. SignDex records important activity events such as document creation, participant notification, signing, approval, rejection, completion, expiry, and deletion where applicable.

SignDex documents are stored securely in cloud storage hosted in Malaysia. Depending on the client company’s configuration, documents may also be stored in the client’s own file storage such as S3-Bucket or Azure Blob Storage.
An organization administrator can configure an S3 bucket file storage for document storage such as S3-Bucket or Azure Blob Storage. This is a one-time setup and is locked after saving to protect storage continuity.

Only participants who included in the same workflow can access the document during the signing process. After the document is completed, the organization administrator can also access and manage the completed documents.

No. API credentials should be restricted to organization administrators only.

Enterprise & Integrations
Questions for enterprise buyers, IT teams, and integration teams
Does SignDex offer SaaS deployment?

Yes. SignDex is a SaaS solution.

SignDex may support on-premises or private deployment for enterprise customers, subject to commercial and technical assessment.

SignDex can support Malaysia-based hosting depending on the deployment model and customer requirement.

SignDex provides standard 8×5 SLA support, during business hours on business days. Support requests can be submitted through the official support email.

SignDex is intended to support enterprise signing workflows. For global use, customers should review local legal, privacy, identity verification, and data residency requirements.

SignDex aims to support international compliance requirements, but customers should confirm whether their specific use case, certificate type, and signing workflow meet the applicable regulation

Can SignDex integrate with my company’s application?

Yes. SignDex can support integration through APIs, subject to the subscribed plan and available API scope.

SignDex supports REST API integration.

Organization administrators can generate or access API credentials from the SignDex admin settings, depending on the subscribed plan.

Not currently supported, cloud storage integrations is roadmap for future releases.

Where supported, completed documents may be stored in configured organization S3 storage based on the organization account’s file configuration.