PVPDF Vision
Se connecterCommencer gratuitement
Electronic signature

Get a PDF signed online

Prepare an envelope, place the fields, send it — and collect a document whose every later change becomes detectable.

PDF Vision turns a PDF into a document to be signed. You place the fields on the page — signature, initials, date, text — and assign each one to a specific recipient, which stops one person signing in another's place. Every signer gets their own link, fills their own fields and nothing else. When everything is filled, the server redraws the fields onto the document and seals it with a PAdES cryptographic signature: from that point, any modification of the file becomes detectable.

How to get a PDF signed

  1. Upload the document

    Load the PDF to be signed and add the recipients with their email addresses.

  2. Place the fields

    Signature, initials, date, text fields — each assigned to one specific recipient, so nobody can sign in someone else’s place.

  3. Send and track

    Sequential or parallel order, an access code per signer, an expiry date, and automatic reminders for those who are slow.

  4. Collect the sealed document

    Once every field is filled, the PDF is sealed with a cryptographic signature that makes any later modification detectable.

What it can do

Enforced signing order

In sequential mode each recipient is notified only once the previous one has signed — a director receives the document after the team that had to review it.

Access code per signer

A code can be required on top of the emailed link. Codes are stored only as hashes on the server.

Expiry and reminders

An envelope can expire on a set date, and slow recipients get automatic reminders. A signer can also decline explicitly.

Reusable templates

Field positions are stored on a standard document and reapplied on every send: employment contract, purchase order, consent form.

Bulk send

The same document goes out to a list of recipients; each gets an independent envelope while the batch stays trackable as a whole.

Cryptographic sealing

The finished document carries a PAdES (PKCS#7) signature that makes any later modification detectable, with the signing time bound to the signature.

What the signature proves, and what it does not

The seal establishes two things: that the content has not changed since signing, and when our server sealed it. It is a real PAdES signature — Adobe Reader will confirm the document has not been altered and show who signed it.

The certificate, however, is self-signed: no public Certificate Authority vouches for it, so readers display the signature as « not trusted ». This is not a qualified signature under eIDAS. Likewise the signing time is attested by our server rather than an independent Time Stamp Authority: it is cryptographically bound to the signature, but it is not defensible against a third party.

For ordinary agreements between parties who know each other, the integrity proof and the recipient trail are usually enough. An act that requires a qualified signature needs a certificate from a recognised authority — which the infrastructure is ready to use as soon as one is supplied.

Frequently asked questions

Is the signature legally binding?
The document is sealed with a PAdES (PKCS#7) cryptographic signature proving it has not been modified since signing, carrying the signing time and the signer's identity. The certificate, however, is self-signed: no public Certificate Authority vouches for it, so Adobe Reader will show the signature as "not trusted". This is not a qualified signature under eIDAS. For ordinary agreements between parties who know each other, the integrity proof and the recipient trail are usually enough; an act requiring a qualified signature needs a certificate issued by a recognised authority.
What exactly does the seal prove?
Two things: that the content has not changed since signing, and when our server sealed it. The signing time is embedded as a signed attribute, so it is cryptographically bound to the signature — but it is attested by us, not by an independent third party. An RFC 3161 timestamp from a Time Stamp Authority would make that date defensible; it is not enabled today.
Can several people sign in a fixed order?
Yes. In sequential mode each recipient is notified only once the previous one has signed, so a director receives the document only after the team that had to review it. In parallel mode everyone receives it at the same time.
Can I require a code from each signer?
Yes, an access code can be required per signer on top of the emailed link. Codes are stored only as hashes on the server.
What happens if nobody signs?
An envelope can carry an expiry date, and automatic reminders go to recipients who have not signed yet. A recipient can also decline explicitly rather than leaving the envelope hanging.
Can I send the same document to fifty people?
Yes, through bulk send: a template is applied to a list of recipients and each gets their own independent envelope, while the batch stays identifiable so it can be tracked as a whole.
How many signatures are included?
E-signature runs on a monthly allowance, refilled each period. Gold plans are not metered. See the pricing page for what your plan includes.
Can I reuse a field layout?
Yes. A template stores where the fields sit on a standard document — employment contract, purchase order, consent form — and reapplies them on every send instead of placing each field again.

Get started

E-signature runs on a monthly allowance, refilled each period, and is not metered on Gold plans.