Automate loan closings, investment subscriptions, account opening, and financial disclosures. Every completed document is PKCS#7-sealed and backed by a tamper-evident audit trail that meets ESIGN, UETA, and PIPEDA requirements.
Personal and commercial loan docs, promissory notes, and security agreements. Sequential routing ensures borrower signs before lender co-signs.
Subscription agreements, PPMs, and investor accreditation forms. Parallel routing handles multiple co-investors simultaneously.
Customer onboarding packets — account applications, risk disclosures, terms acceptance. Automate the entire intake flow with one envelope.
High-value transaction authorizations requiring dual control. Mixed routing enforces sequential approval tiers with parallel approvers at each level.
Regulatory disclosures, fee schedules, and conflict-of-interest disclosures. Timestamped consent capture creates an auditable record of receipt.
Brokerage account agreements, options trading approvals, and margin account authorizations. Full audit trail from disclosure to signature.
E-signatures for financial documents are recognized under multiple jurisdictions.
The Electronic Signatures in Global and National Commerce Act gives e-signatures the same legal weight as wet signatures for loan documents, investment agreements, and account opening forms.
The Uniform Electronic Transactions Act, adopted in 49 states, provides state-level recognition. Financial contracts executed electronically under UETA are enforceable in the same manner as paper contracts.
Canadian federal legislation recognizes electronic signatures for financial documents. Provincial laws (Ontario's Electronic Commerce Act, etc.) provide additional recognition.
Each signing event captures IP address, timestamp, user agent, geolocation, and explicit consent — creating an evidentiary record that meets financial services requirements for proof of delivery and intent.
Generate the loan agreement, subscription doc, or disclosure from your data — using your existing PDF generation stack. Pass the bytes directly to the API.
Upload the PDF, declare signers (with routing order for sequential approval flows), and place fields. One POST to /send dispatches signing links immediately.
The envelope.completed webhook fires when all parties sign. Download the PKCS#7-sealed document, store it in your document management system, and update your records.
Yes, for most financial documents. Loan agreements, investment subscription documents, account opening forms, financial disclosures, and trading agreements are all covered by the US ESIGN Act, UETA, and Canada's PIPEDA. Exceptions vary by jurisdiction and document type — certain notarized instruments, court filings, and specific government forms may require wet signatures. Consult your legal counsel for jurisdiction-specific guidance on your specific document types.
Use routing_order to enforce approval sequences. Set the same routing_order value for parallel approvers at the same tier (e.g., both risk officers sign simultaneously), and increment it for the next sequential step (e.g., the CFO signs after both risk officers). The envelope only advances when all signers at the current routing_order complete. This creates a flexible approval matrix without requiring custom workflow logic in your application.
Every signing event is recorded in a hash-chained, append-only audit log: document view (with timestamp + IP), e-sign consent click, OTP verification event, signature application, and PKCS#7 sealing. This log is attached as an audit certificate page burned into the sealed PDF before the digital signature is applied. The hash chain means any tampering with audit records is mathematically detectable. The final document hash is also stored separately so the sealed file can be verified against the original.
Yes — via webhooks. Subscribe to the envelope.completed event, receive the signed document URL and envelope metadata, and trigger your downstream workflow: update the loan record, notify account managers, archive to your document management system, or trigger funding disbursement. GetSigned fires events and stays domain-agnostic; your system applies the business logic.
Document retention is configurable per tenant — you set the period based on your regulatory requirements (7 years is a common default for financial records). On retention expiry, the PDF blob is purged but the audit trail tombstone — including document hashes and all event metadata — is retained permanently, so you can verify the document's authenticity even after the file is deleted.
The signing page shows your brand name and logo by default. Full white-labelling — removing the Powered-by attribution and presenting only your brand — is available on the Enterprise plan. This is important for financial institutions where the end-customer relationship and brand trust are central to the signing experience.
This page is for informational purposes only and does not constitute legal or compliance advice. Consult qualified legal counsel regarding jurisdiction-specific requirements for electronic signatures in financial services.
Related: E-signature legality guide · Multi-signer routing · Audit trail guide · E-signatures for legal
Free tier includes 25 envelopes per month. Full API access, PKCS#7 sealing, and audit trails from day one.
Get free API keys →