DocuSign Integration

When a DocuSign envelope completes, Memora can attest the signed documents on the Canton Network automatically. The result is a tamper-evident record that the executed agreement existed in exactly this form at that moment, distinguishable from manual uploads by a DocuSign provenance badge.

Privacy trade-off

Manual uploads in the attestation app are end-to-end encrypted: your browser hashes and encrypts the document and we never see the plaintext. Automated DocuSign ingestion cannot work that way, because there is no browser in the loop. To hash a completed envelope, our service must fetch the signed document from DocuSign and compute the hash server-side, so the plaintext passes through our infrastructure at the moment of ingestion.

For that reason DocuSign auto-attestation is an explicit, per-customer opt-in, and documents that arrive this way are labeled so you can tell them apart. If your requirement is that we never handle plaintext, download the completed envelope and upload it manually. The attestation is identical, and you can still record the DocuSign provenance as metadata. See Privacy and Encryption.

What happens when an envelope completes

1. DocuSign sends a Connect event to us when an envelope reaches the completed state.
2. Our service fetches the envelope's documents from DocuSign.
3. The service hashes each document with SHA-256 and attests it on the Canton Network: a metadata contract records the hash and the originating party, and a signed-document contract records the signing parties you have mapped.
4. The document appears in your workspace with a gold DocuSign badge on its thumbnail and DocuSign in its Source column.

The service records the DocuSign envelope ID and signer details separately from the storage record, so parties that store the document do not see who signed it or which envelope it came from. Visibility of signer information follows the same selective-disclosure rules as other metadata.

What is recorded

Connect a DocuSign account

An administrator sets this up once per DocuSign account.

1. In your Memora workspace, open Settings and enable DocuSign attestation. Confirm the privacy trade-off above.
2. In DocuSign, open Settings, Connect and create a new Connect configuration.
3. Set the URL to publish to: Coming soon.
4. Under trigger events, select Envelope Completed. The service ignores other events.
5. Include document PDFs in the event payload if your DocuSign plan offers the option. Otherwise our service fetches them.
6. Save, then send a test envelope and complete it. Within a few minutes the document appears in your workspace with the DocuSign badge.

Whether we use your DocuSign API credentials or our own integration key: Coming soon.

Map signers to Canton parties

The service records signing parties on Canton as party IDs. In your workspace settings, map the DocuSign signer identities you use, by email, to the Canton party that should be recorded as the signer. Unmapped signers are recorded under your workspace's own party.

Verify a DocuSign attestation

Open the document in the app and choose Verify, then select the completed PDF you downloaded from DocuSign. The hashes match if the file is byte for byte the one attested. DocuSign can generate a PDF with a certificate of completion appended. Verify against the same form of the document that was ingested.

Troubleshooting

Disconnecting

Delete the Connect configuration in DocuSign, or disable DocuSign attestation in your Memora workspace. Documents already attested are unaffected.