Every signer proves who they are. Every document shows if it was changed.
Document signing where each signer confirms a code sent to their email before they sign, and the finished PDF carries its own proof. Send from the console or from your own systems, to one signer or several.
Live today
Send it, sign it, prove it.
Everything in this section runs in production now.
Send a document
- From the console, or from your own systems through the API.
- To one signer or several, in order or all at once.
- With reusable templates: place name, NIC, date, text and signature fields.
Locked details
- Values your system sends (name, NIC, account number, loan amount…) fill named fields and are locked.
- The signer sees them but cannot change them.
- What the signer types comes back to your system.
Proving the signer
- A 6-digit code goes to the signer's email. It is valid for 10 minutes, with 5 attempts.
- Then a drawn or typed signature.
- A link alone never signs.
Delivery and languages
- Invitations by email, SMS or both.
- Reminders, and links that expire.
- In a verification journey, the signing step is in English, Sinhala and Tamil.
Location rules
- Optional. You set an area.
- The signer's location is checked against it when they sign.
Your systems, your data
- Webhooks carry your own reference.
- Your own data storage option.
- On-premises installation on request.
Already verifying with Verifia? A “Sign a document” step can end any verification journey, with fields filled from the checks that passed.
Proof on every document
The evidence travels with the file.
A Certificate of Completion
A page added to the PDF, with the envelope ID and the document’s SHA-256 fingerprint. For each signer:
- Name
- Last 4 NIC digits
- Masked email
- Time
- IP address
- How they signed
- Where, if a location rule is on
An activity trail
Every event on the document, recorded.
A public verification page
Anyone with the code can check a document. Any change to the file changes its fingerprint.
It shows
- Names
- Methods
- Times
- Fingerprints
It never shows
- The NIC
- The email
- The document
Use cases
Where it fits.
- Customer agreementsSent from your system, with the customer's name and NIC locked in.
- Loan and lease agreementsThe loan amount and account number filled in from your system, and locked.
- Insurance proposalsSent by email, SMS or both, with the proposal details filled in and locked.
- MandatesSeveral signers, in order or all at once, each proving who they are.
- Internal approvalsStaff sign with an email code, and every step lands in the activity trail.
What comes next
Built, and labelled for what it is.
Neither of these is generally available yet. Each one says where it stands.
AnybanQID Sign for teams
Staff, directors and authorised signatories approve and sign in the AnybanQID app on their own phone, with fingerprint or face. Their AnybanQID account is verified with their bank.
It is optional: without it, staff sign with an email code like anyone else.
Certified signatures with LankaSign
Every completed PDF will be sealed with a LankaSign certificate, and staff will be able to sign with their own LankaSign certificate.
LankaSign is a certification service appointed under the Electronic Transactions Act No. 19 of 2006.
How documents, signers and records are protected is set out on the security page.
Next step
See it with your own document.
Book a demo and bring a document you sign today. We will show you how it is sent, signed and checked.