Electronic signature for banking, verified and tamper-evident.

In most cases, yes. Loan agreements, account-opening forms, disclosures, and authorization documents signed electronically carry the same legal weight as wet ink under the U.S. ESIGN Act of 2000 and state UETA laws, and under the EU's eIDAS regulation, provided the signer intended to sign, consented to sign electronically, the signature is attributed to them, and a record is retained. Document eSign captures all four on every envelope. A narrow set of instruments may carry specific regulatory or notarization requirements - certain mortgage notes and recorded instruments, for example - so confirm the rule with your regulator and jurisdiction for that document type. For the large majority of banking paperwork, an e-signature with a complete audit trail is binding and enforceable.

Yes. Require an emailed one-time passcode (OTP) so the applicant or borrower must enter a code sent to their email before the document opens, or set a per-signer access PIN that you share separately out-of-band so only the intended recipient can sign. For either method, the verification type, the time it happened, the signer's IP address, and their device are recorded on the certificate of completion next to the signature, so the proof of who signed travels with the document. This attribution supports your know-your-customer (KYC) record on account openings and loans where identity matters. SMS one-time-passcode verification is coming soon as an additional phone-based factor.

Not today. Signer verification is by emailed OTP or a per-signer access PIN, both captured on the audit trail with the time, IP, and device. Document eSign does not provide knowledge-based authentication (KBA) or full KYC identity proofing against public records, so where a regulator requires that level of identity verification, pair Document eSign with your existing KYC or identity-proofing process. The e-signature platform then handles the signing and the tamper-evident record: it documents that the verified party signed, when, and from where, while your KYC workflow handles the underlying identity check. Used together, you get a complete account-opening file with the signing evidence attached.

Yes. Add the borrower, a co-signer, a guarantor, and an internal approver as recipients, then set the signing order. Each party is released only when the previous one finishes, so the borrower signs first, the co-signer is notified next, and an internal loan officer signs last as the approval gate. The whole chain lands on one append-only audit trail and a single certificate of completion for the envelope, with every party's email, IP, timestamp, and verification method recorded. You can reassign or forward a step to another person mid-flight, and that change is audited too. This keeps a multi-party loan in one tamper-evident record instead of scattered across separate signed copies.

Every completed document is sealed with a SHA-256 hash and an embedded PAdES-B signature, so any change to a single character after signing breaks the seal and is flagged as altered in any standards-compliant reader such as Adobe Acrobat. On paid plans the seal also carries an independent TSA timestamp, anchoring the signing time to a trusted third party. The audit trail records each signer's verification method, IP address, device, and the timestamp for every action - sent, opened, consented, verified, and signed - so the proof of who did what travels with the file. That combination, identity verification plus a cryptographic seal plus the trail, is materially stronger than a scanned wet-ink copy for resisting and detecting fraud.

Before using electronic signatures and records with consumers, the ESIGN Act requires their affirmative consent to transact electronically, plus certain disclosures about their right to receive paper copies and how to withdraw consent. Document eSign lets you capture that consent - in your own wording rather than a generic default notice - before the document opens for signing, and writes the exact text, the timestamp, and the signer's IP address onto the certificate of completion. That means the consent itself becomes part of the defensible record rather than a separate step you have to evidence later. Banks commonly use this for account agreements, disclosures, and authorization forms where the consent language is part of what makes the signature compliant.

Yes. SAML and OIDC single sign-on, plus SCIM 2.0 provisioning for automated user provisioning and deprovisioning, are available on the Enterprise plan, alongside IP allowlisting and configurable session timeouts. That means your loan officers and branch staff sign in through your identity provider, you control access centrally, and a departing employee loses access the moment they are removed in your directory. SSO keeps the staff side of signing locked down to your security policy, while customers and borrowers still sign through a simple secure link with no account to create. Identity verification on the signer side is handled separately by OTP or access PIN, recorded on the audit trail.

Yes. Signing runs entirely in the mobile browser, so a borrower or account holder can review and sign a loan agreement, account-opening packet, or authorization from a phone or tablet with nothing to install and no account to create. The signer taps the secure link in their email, enters their OTP or access PIN if you required verification, reviews the document, agrees to your consent wording, and signs by typing or drawing - producing the same legally binding signature and audit trail they would get on a laptop. This is what makes remote account opening and lending practical: a customer can finish their part in a few minutes, and the signed, sealed document lands in your workspace the moment they complete it.

Yes. Nothing is auto-deleted or expired - a signed loan file or account agreement stays in your Document eSign workspace until you choose to remove it, so a document executed two years ago is still there with its certificate and seal intact. You can export any completed PDF and its audit trail at any time, and on Business and above completed documents mirror automatically to your own cloud storage, so you keep copies in whatever system your bank already uses for records retention. On paid plans the PAdES seal also carries an independent TSA timestamp, which anchors the signing time to a trusted third party - useful for long-lived loan and mortgage agreements that may be examined years after signing.

Yes, on the Enterprise plan. You can choose US or EU data residency for where your documents and audit data are stored, which matters when a regulator or internal policy requires data to remain in a specific region. Enterprise also adds bring-your-own-key (BYOK) encryption so you control the encryption keys, single sign-on with SCIM provisioning, IP allowlisting, and a dedicated account manager. On the Free, Business, and other paid tiers the signing, the PAdES seal, the identity verification, and the legal validity are identical - data residency, BYOK, and the deeper administrative controls are the Enterprise additions for banks with stricter regulatory and security requirements.

No. Document eSign provides electronic signatures with OTP or access-PIN identity verification and a tamper-evident certificate of completion, but it does not provide remote online notarization (RON), where a commissioned notary witnesses the signing over live video. For any banking instrument that must be notarized - certain mortgage documents, recorded deeds, and instruments your jurisdiction requires a notary to execute - you will need a separate RON provider or in-person notary, and you should confirm the exact requirement with your regulator for that document and state. For the large set of loan, account, disclosure, and authorization documents that do not require notarization, an e-signature with a full audit trail and PAdES seal is sufficient and defensible.

Yes. The Free plan includes unlimited envelopes and two reusable templates with a full audit trail on every document, which is enough to send and test a loan agreement, account-opening form, or authorization without paying or entering a card. As you scale, Business and Enterprise add team members, custom branding, custom consent and disclaimer wording, bulk send, in-person signing, automatic cloud backup, and - on Enterprise - SSO with SCIM, data residency, and BYOK. The core signing, the OTP and PIN verification, the PAdES seal, and the legal validity are identical on every plan, including Free. You are not buying enforceability on the higher tiers; you are buying scale, branding, and administrative control.