Digital Transaction Management

Principal workflows

• Design: Moraph works with your lending, compliance and IT teams to decide which documents are signed electronically, how signers are authenticated, how consent is captured and how completed records are kept.
• Build: Moraph configures the DocuSign account to the approved design: account settings, consumer disclosure, templates, signing order, authentication and integrations with your loan systems.
• Operate: Moraph runs the account day to day: template changes, user and permission changes, integration monitoring, second-line support and liaison with DocuSign, with every change approved by your named owner.
• Evidence and retain: Each completed envelope keeps DocuSign's envelope history and certificate of completion. Moraph makes sure they reach your system of record and helps you produce them for disputes, audits and examinations.

Who uses it

• Lending and loan operations leaders at banks, credit unions and mortgage lenders
• Loan officers and closers who send documents for signature
• Compliance officers responsible for ESIGN, UETA and disclosure delivery
• IT teams who need DocuSign integrated with loan origination and document systems
• Internal audit and examiners reviewing electronic signature evidence

Reporting

• Envelopes sent, completed, declined and outstanding
• Integration and delivery failures with follow-up
• Template inventory with owners and versions
• Template and setting changes with approvers
• Consumer disclosure versions and when each was in force
• Transaction evidence packs for disputes and examinations

Features

• Consumer consent under ESIGN: DocuSign presents your consumer disclosure and records the signer's consent before they can view and sign, with the disclosure text you approve.
• Envelope history: DocuSign records each event in an envelope's life, such as sent, delivered, viewed, signed and completed, with the time and the signer's IP address.
• Certificate of completion: Each completed envelope has a certificate of completion summarizing the signers, their authentication and the signing events.
• Tamper-evident documents: DocuSign seals completed documents with a digital signature so later changes to the document can be detected.
• Signer authentication by risk: Templates require the authentication your design sets for each document, such as email, access code, SMS or phone, or ID verification where licensed.
• Loan document templates: Templates for each loan product and package with signer roles, signing order, required fields and conditional fields, maintained by Moraph.
• Template governance: One owner and one approved version for each template, with a record of every change, who requested it and who approved it.
• Loan system integration: Envelopes created from your loan origination or document system and completed documents returned to it, using DocuSign's API, Connect notifications or existing connectors.
• Retention settings: DocuSign retention and purge settings aligned with your records schedule, with completed records kept in your own system of record.
• Managed change control: Every template and setting change goes through a request, approval, test and recorded release.
• Sender access and permissions: Permission profiles and groups so senders use the templates for their role and branch, and only administrators change account settings.
• Dispute and audit support: On request, Moraph retrieves the completed document, certificate and envelope history for a transaction, and the template version and settings in force at the time.

Integrations

• Loan origination system: Envelopes created from loan data and completed documents returned to the loan file, through an existing DocuSign connector for your system where one exists, or DocuSign's eSignature API.
• Document management: Completed documents and certificates of completion delivered to your document or imaging system for retention.
• DocuSign Connect: Envelope events sent to your systems as they happen, so status updates without polling.
• CRM: Documents sent from your CRM, such as Salesforce, with status returned to the client record.
• Single sign-on: Your staff sign in to DocuSign through your identity provider using SAML, so your MFA and leaver process apply.
• Identity verification: Where licensed, DocuSign's ID verification checks a signer's government ID before they can sign higher-risk documents.

Deployment

• Licences through Moraph: Moraph resells the DocuSign plan and add-ons and runs the account as one service, subject to DocuSign's terms.
• Your existing DocuSign account: If you already use DocuSign, Moraph reviews templates and settings against a new design and takes over operation of the account.
• Co-managed: Your team keeps some administration, such as user management or simple template edits, and Moraph runs the rest; the split is written into the responsibilities.

Security and privacy

• Single sign-on: Your staff sign in through your identity provider, so your password, MFA and leaver policies apply.
• Role-based access: What each person can see and do follows their permission profile and group; sending is separate from changing templates and settings.
• Complete audit trail: DocuSign's envelope history records signing events, and Moraph's change record links each template and setting change to its request and approval.
• Encryption and keys: Service records Moraph holds are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.
• Limited Moraph access: Moraph engineers use named accounts with only the rights they need, and open completed documents only for an authorized support reason.
• Audited company-wide: Moraph is audited to SOC 2 Type II and ISO/IEC 27001 across the company, including the teams that run this service. DocuSign's own attestations cover the platform.

Limitations

• Moraph is not DocuSign. DocuSign operates the platform, and DocuSign's own service commitments, roadmap, maintenance and outages apply.
• Licences are subject to DocuSign's terms. Features such as ID verification and some connectors need their own plans or add-ons.
• Moraph configures signing to support ESIGN and UETA, but whether a particular record is enforceable is a legal question for your institution and its counsel.
• Some documents and transactions are excluded from ESIGN and UETA or need wet signatures, notarization or other formalities under state law; those are identified with your counsel and kept out of electronic workflows unless permitted.
• Transferable records such as eNotes, and remote online notarization, are outside this service unless scoped separately.
• Disclosure timing under Regulation Z depends on when your loan system generates and sends documents; Moraph configures delivery but does not decide timing.
• Moraph does not write your disclosures or loan documents; their content is your institution's responsibility.
• Records kept only in DocuSign are subject to the retention settings and plan you choose; your system of record should hold completed documents for your full retention period.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/digital-transaction-management. Purchasing routes and company information: www.moraph.com/how-to-buy.