The product
Built for the forms nobody else will touch.
Two-page contracts are easy. A nine-page application about seven people, asking for the same ID number three times, is not. That's the form Vumasign was built around.

Subjects
It knows who Dependant 1 is.
A medical scheme application asks about a member, a spouse and their children. A plain signing tool sees 278 loose boxes. Vumasign sees the seven people the form is about, and knows whose details go in every box.
Who this form is about
Employer group application, 9 pagesEvery field found
Upload the PDF you already use.
Every field is found, named and placed for you, even the rows of little printed boxes most tools treat as a picture. You fix what's wrong instead of placing 278 boxes by hand.
Asked once
Asked once, even when the form asks three times.
An ID number on pages 2, 7 and 9 is one question and one answer. It's checked as an ID number while it's typed, not after someone presses Sign.
One answer, written everywhere
The record
Sealed when the last person signs.
The answers go into the document, a certificate of completion goes on the end, and the whole file is sealed with a trusted timestamp. Change one byte and the seal breaks, in the reader's own software, without asking us.
How the seal worksWho signed
Know exactly who signed.
A signing link proves someone opened an email. For the documents where that isn't enough, ask each signer to prove more before they sign: a code on their phone, or their ID and a live selfie. Whatever they proved is sealed into the document, on their signature and on the certificate.
- A level for each signer: the tenant shows their ID, the agent gets a code
- Codes on WhatsApp first, and by SMS when WhatsApp can’t reach them
- A South African ID, or a passport from about 190 countries
- No photos kept by Vumasign
Mobile codes are included on every plan. Identity checks are R59 a signer.
See pricingThree levels, chosen per signer
Email code
Level 1A one-time code to the signer’s email address, entered before they sign.
They can read that inbox.
Mobile code
Level 2A one-time code on WhatsApp, and the same code by SMS if WhatsApp can’t reach them. South African mobile numbers.
They have the phone.
Identity check
Level 3A mobile code, then a live photo of their ID and a live selfie, on their own phone. A South African ID is matched to the Home Affairs photo; a passport is checked for authenticity and matched to its own photo.
The person signing matches the person on the ID.
Smart ID cardGreen ID bookPassport, about 190 countriesLiveness checked
No level set? The signer signs with the signing link alone, as they always could.
12. Signed at the places and on the dates below. Each party confirms they have read and accept the terms of this lease.
Identity confirmed against Department of Home Affairs records for ID number •••••••••0087, read from the signer’s Smart ID card.
- Live selfie passed a liveness check
- Selfie matched the Home Affairs photo
- ID number read from the card, checksum valid
- Mobile code entered from •••• 4567
Confirmed with a one-time code sent on WhatsApp to •••• 2290 and entered before signing. Identity was not checked against an identity document.
Vumasign keeps no photos. The identity check is run by VerifyNow, and its result is kept with the document's record.What we keep
An identity check strengthens the evidence of who signed. It doesn't change the kind of signature it is.Is it legal?
Measured on real forms, not estimated.
South African benefit and insurance forms, counted as published. The scheme and fund names are withheld. The counts aren't.
| Document | Pages | Fields | Who it's about |
|---|---|---|---|
| Medical scheme application, employer group | 9 | 278 | member · spouse · dependants: 7 people, as setup found them |
| Retirement fund nomination of beneficiary | 6 | 127 | member · beneficiary 1–6 · witness |
| Funeral cover application | 4 | — | member · spouse · children · extended family |
| Group life insurance application | 4 | — | member · beneficiaries · employer |
| Group life beneficiary nomination | 2 | — | member · beneficiary 1–4 |
- Medical scheme application, employer group9 pages, 278 fieldsmember · spouse · dependants: 7 people, as setup found them
- Retirement fund nomination of beneficiary6 pages, 127 fieldsmember · beneficiary 1–6 · witness
- Funeral cover application4 pagesmember · spouse · children · extended family
- Group life insurance application4 pagesmember · beneficiaries · employer
- Group life beneficiary nomination2 pagesmember · beneficiary 1–4
The employer group count is the boxes setup placed on the real form; the others are as published in the source PDFs. Scheme and fund names withheld on this page.
And everything you'd expect.
Templates
Set it up once, send it every week. Text tags if you prefer to mark up the PDF.
Signing order
One after another, all at once, or a mix. Approvers who sign nothing but still say yes.
Bulk send
One template, a list of people, one batch.
Your brand
Your logo and colours on the emails and signing page, from your own sending domain.
Reminders and expiry
Chased and closed on their own, and both recorded.
Draw, type or upload
A signature drawn on a phone, typed, or photographed off paper.
Building signing into your own product? The API, embedded signing and webhooks
Priced by the envelope, on every plan.
R7 an envelope on Team, R5 on Business, published. Building signing into your own product? The API plan is R500 a month with 50 included, then R10 each.
Open one of your own forms.
Upload the worst one you have. What it finds, and what it misses, will tell you more than any feature list.
Signed, sealed, sorted. Lekker.