E-signature for client onboarding
Sign once, seal the whole pack
A client signs one time at the end of an onboarding flow, and that signature applies a native PAdES seal across every document generated for their case. There is no separate e-signature vendor to add, no second seat to buy and no signature record living apart from the data it belongs to.
- One signature, one seal, across the whole document pack
- Native PAdES seal, applied inside the flow
- Evidence page: consent time, device, identity method, decisions
What kind of e-signature is this
It is an advanced electronic signature with a PAdES seal applied directly by Braigest. It is not a vendor add-on: there is no separate e-signature product to license or configure, because signing is a step in the same workflow that collected the data. The seal is applied to the finished PDF and can be checked for integrity afterwards.
How does one signature cover several documents
A client's onboarding case can generate more than one document, a service agreement and a data-processing addendum, for instance. Instead of signing each one separately, the client signs once and that signature seals the whole pack, because every document was built from the same case and the same dossier of answers.
What is on the evidence page
Every signed pack carries an evidence page recording the time of consent, the device used, which identity method (if any) ran before signing, and any reviewer decisions made on the case. It is the record you show if anyone later asks how a signature was obtained and by whom.
- Consent time and device
- Identity method used before signing, if any
- Reviewer decisions on the case
- Full audit history of the run
How do I know the signed PDF has not been altered
The PAdES seal is checked against the document each time it is opened in a compliant viewer, which reports whether the seal is intact or has been broken by a later edit. A sealed, intact document is exactly what it was when the client signed it.
What this signature is not
This is an advanced electronic signature, not a qualified electronic signature under eIDAS. Notarial deeds and any document your national law reserves specifically for a qualified signature are out of scope for this feature, and should be routed through a qualified signing process instead.
Where does signing sit in the onboarding flow
Signing runs after the form and document steps have collected everything needed, and after identity verification when the flow includes one. By the time a client reaches the signature step, the documents are already filled and ready, so signing is the last action, not a separate errand afterwards.
Frequently asked questions
Is this a qualified electronic signature?
No. It is an advanced electronic signature with a native PAdES seal. Documents your national law reserves for a qualified signature, such as certain notarial deeds, are out of scope.
Do I need a separate e-signature subscription?
No. Signing is a native step inside the onboarding workflow, so there is no separate vendor seat or subscription to add for e-signature.
Can one signature cover multiple documents?
Yes. A client signs once and the seal applies across the whole pack of documents generated for their case, because they were built from the same set of answers.
What proves the signature is valid later?
The evidence page records consent time, device, identity method used and reviewer decisions, and the PAdES seal itself shows whether the document has stayed intact since signing.
Where in the flow does signing happen?
After the form, documents and any identity check are complete. Signing is the final step, applied once the whole pack is ready.
Explore more of the platform
See the seal and the evidence page on a real document
Book a 30-minute call and we will walk through a signed, sealed pack end to end.