The signing page in GetAccept is designed to be simple, secure, and fully guided for every recipient. This article explains how the signing experience works across languages, devices, identity requirements, and certificate generation.
Language Detection
The signing page automatically adapts to the recipient’s web browser language.
If the browser language matches one of GetAccept’s supported signing languages, the signer will see all buttons, instructions, and prompts in that language.
Supported languages include:
English (US), English (UK), Swedish, Danish, Norwegian, German, Spanish, Finnish, French, Italian, Dutch, Polish, Portuguese, Russian, and Chinese.
If the browser language is not supported, the signing page defaults to English.
Multi-Device Signing
Recipients can sign documents on any device:
Desktop
Laptop
Mobile browser
Tablet
The signing page automatically adjusts to the device screen size.
All signing methods (click-to-sign, drawn signature, initials, and eID when enabled) work across supported devices.
SMS on Open vs SMS on Sign
Depending on the sender’s configuration, recipients may be prompted for SMS verification:
SMS on Open
The recipient must verify their identity via SMS before accessing the document.
This is often used when security or compliance requires strong authentication.
SMS on Sign
The recipient reviews the document normally but must verify via SMS before completing the signature.
Used for added verification at the signature step.
The sender decides which method is required when preparing the document.
Certificate Creation Flow
When the document is signed, GetAccept automatically generates a Signature Certificate containing:
Signer identity details
Signing method (click-to-sign, drawn, eID, SMS verification, etc.)
Timestamp
IP address
Browser type
Device used
All signing events
Document hash
Chat history and interactions
Completion status
This certificate is included with the completed document unless the sender disables the attachment.
Each signer receives their own certificate entry in the final audit log.
How a Recipient Signs the Document
When a document is sent for signing, the recipient receives an email or SMS with a link to open it.
1. Review and Fill Required Fields
Once the document opens, the signing page guides the recipient through any required fields — text fields, checkboxes, initials, or signature inputs.
The recipient cannot finish signing until all required fields are completed.
2. Signing Methods
Available methods depend on the sender’s settings and the recipient’s region:
Click-to-Sign – Press a button to sign.
Drawn Signature – Draw using mouse, trackpad, or touchscreen.
Initials – Add initials where required.
Electronic ID (BankID or equivalent) – Identity verification before signing.
Each method creates a legally binding entry in the signature certificate.
3. After Signing
Once all parties sign:
The document becomes finalized and sealed.
The recipient receives:
A PDF of the signed document
A Signature Certificate (if enabled by the sender)
The audit trail updates for every participant.
Key Takeaways
The signing page language is based on the recipient’s browser.
Signing works on any device through a responsive signing interface.
SMS verification may be required before opening or before signing.
A complete signature certificate is created automatically for legal compliance.
The signing page guides recipients step-by-step through required fields and signing methods.