Financial Services · Managed platform (DocuSign)

Digital Transaction Management

DocuSign signing workflows for loan documents, built for ESIGN and UETA and run for you

Overview

What you are buying

Moraph resells, implements and runs DocuSign eSignature for lenders, banks and credit unions. We build signing workflows for loan documents with consumer consent, signer authentication, signing order and retention configured to your procedures, and DocuSign records each envelope's history and certificate of completion as evidence of who signed what and when. Moraph then operates the account: templates, changes, integrations, access and support, under your approval.

The problem it solves

Lenders adopt electronic signatures quickly, but the details that make an electronic record hold up are easy to get wrong: consumer consent under ESIGN before disclosures are delivered electronically, a reliable way to show the signer is who they claim to be, and a complete, tamper-evident record of the transaction kept for as long as the loan requires. Templates multiply across branches and loan products, senders improvise, and when a borrower disputes a signature or an examiner asks for evidence, the record is incomplete or hard to find.

  • Consumer consent to electronic records is captured inconsistently or not at all
  • Signer authentication varies by sender rather than by the risk of the document
  • Templates drift across branches and loan products, with no one owning them
  • Completed documents and their audit evidence are scattered across inboxes and shared drives

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

Requirements it supports

Electronic Signatures in Global and National Commerce Act (ESIGN, 15 U.S.C. 7001 et seq.)ESIGN consumer consent requirements (15 U.S.C. 7001(c))Uniform Electronic Transactions Act (UETA), as adopted by each stateRegulation Z (12 CFR Part 1026), including TILA-RESPA integrated disclosure timingGramm-Leach-Bliley Act and the Interagency Guidelines Establishing Information Security Standards

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

DocuSign runs the signing platform, Moraph configures and operates your account on it, and your institution owns the documents, the disclosures and the decisions.

AreaMoraphDocuSignYour organization
LicensingResells DocuSign plans and add-ons, or works with licences you hold, and tracks usageSets plan terms, envelope allowances and the features each plan includesAgrees to DocuSign's terms and decides which plan and add-ons to license
Platform availabilityTracks DocuSign service notices and tells you when an incident affects youRuns, hosts and maintains the eSignature service under its own commitmentsKeeps a fallback procedure for urgent signings
Signing evidenceConfigures settings so envelope history and certificates are kept and delivered to your systemsRecords envelope events, produces certificates of completion and seals completed documentsKeeps completed records in your system of record for your retention period
Consumer consentConfigures the consumer disclosure and consent settings you approvePresents the disclosure and records consentWrites and approves the disclosure text and decides when consent is required
Templates and configurationBuilds and maintains templates and settings under change controlProvides the platform features and configuration optionsOwns each template's content and approves every change
Identity and accessMaintains groups, permission profiles and single sign-on settingsEnforces the configured permissions and signer authenticationDecides who may send and administer, and approves access
IntegrationsBuilds and monitors integrations and follows up failuresProvides the APIs, Connect notifications and connectorsOwns the loan and document systems on the other side
Incident responseTriages account and integration incidents and supports your investigationResponds to incidents in the DocuSign platform itselfLeads incident response and makes notification decisions
Platform updatesReviews DocuSign release notes and plans changes that affect your accountReleases updates on its own scheduleApproves any change needed in response
User supportSecond-line support for senders and liaison with DocuSign supportSupport to Moraph for platform defectsFirst-line support for your senders and help for borrowers, unless you hand it to Moraph

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of DocuSign itself, which belongs to its vendor.

  1. Step 1

    The onboarding tracker

    During implementation, every document package has a row showing its owner, authentication and where it stands.

    PackageOwnerAuthenticationCompliance reviewStatus
    Consumer installment closing (example)Consumer lendingAccess codeApprovedLive
    Home equity closing (example)Mortgage operationsID verificationApprovedTesting
    Initial mortgage disclosures (example)Mortgage operationsEmail and SMSChanges requestedOn hold
    Business loan agreement (example)Commercial lendingSMSNot startedPlanned
    Account opening forms (example)Retail operationsEmailApprovedLive
    During implementation, every document package has a row showing its owner, authentication and where it stands.
  2. Step 2

    The configuration baseline

    Account-wide settings that matter for evidence and consent are written down and approved before go-live.

    Signing baseline v2 · Example Federal Credit Union (fictional)

    Consumer disclosure
    Version 3, approved by compliance
    Certificate of completion
    Attached to completed documents
    Completed document delivery
    Returned to loan system
    Sender sign-in
    Single sign-on required
    Retention in DocuSign
    Not yet confirmed by records management

    Authentication by document type

    • Account opening: email
    • Consumer loan closing: access code sent separately
    • Home equity closing: ID verification
    • Business loan agreement: SMS
    Account-wide settings that matter for evidence and consent are written down and approved before go-live.
  3. Step 3

    A template change request

    A change that affects disclosures needs both your lending owner and your compliance officer before Moraph releases it.

    CR-3046 · Update home equity closing package

    1. Change requested with the new document versionLending operations owner
    2. Template updated in test accountMoraph DocuSign engineer
    3. Disclosure pages reviewedCompliance officer
    4. Test signing completed on phone and desktopLoan closer
    5. Change approvedLending operations owner
    6. Released and previous version retiredMoraph DocuSign engineer
    A change that affects disclosures needs both your lending owner and your compliance officer before Moraph releases it.
  4. Step 4

    Failure triage

    Moraph follows up envelopes that did not deliver or did not return to the loan system, so no file is left incomplete.

    EnvelopeLoanProblemNext stepStatus
    ENV-58302Loan 70214Completed document not returned to loan fileRetry deliveryResolved
    ENV-58297Loan 70188Signer email bouncedSender to confirm addressWaiting on you
    ENV-58291Loan 70175Envelope not created, missing fieldFix field mappingIn progress
    Moraph follows up envelopes that did not deliver or did not return to the loan system, so no file is left incomplete.
  5. Step 5

    A transaction evidence pack

    For a dispute or examination, Moraph gathers the completed document, certificate and history, and the template and disclosure in force.

    Loan 70102 · Consumer installment closing

    Requested by
    Compliance officer
    Signers
    Borrower and co-borrower
    Consent recorded
    Yes, disclosure version 3
    Authentication
    Access code
    Document seal
    Verified

    Included

    • Completed document
    • Certificate of completion
    • Envelope history
    • Template version in force
    • Consumer disclosure version in force
    For a dispute or examination, Moraph gathers the completed document, certificate and history, and the template and disclosure in force.
  6. Step 6

    The monthly service review

    Moraph and your team review changes, failures and open risks, and agree what comes next.

    Service review · Sample month

    Template changes released
    4, all approved
    Envelopes completed
    1,286
    Integration failures
    6, all resolved
    Templates without an owner
    2
    Open requests
    5

    Actions agreed

    • Assign owners to two templates or retire them
    • Confirm retention settings with records management
    • Plan business loan package for go-live
    Moraph and your team review changes, failures and open risks, and agree what comes next.

Workflows

The principal workflows

  1. 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.

    • Loan products and document packages inventoried with lending operations
    • Consumer consent disclosure reviewed by your compliance team
    • Signer authentication method set for each document type by risk
    • Retention and storage of completed envelopes agreed with records management
    • Design approved by your lending and compliance owners
  2. Build

    Moraph configures the DocuSign account to the approved design: account settings, consumer disclosure, templates, signing order, authentication and integrations with your loan systems.

    • Account settings, branding and the consumer disclosure configured
    • Templates built for each document package with fields, roles and signing order
    • Signer authentication applied per template, such as access codes, SMS or ID verification where licensed
    • Integration with your loan origination or document system built and tested
    • Templates tested with your loan staff before release
  3. 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.

    • Change requests for templates and settings raised by your team
    • Changes approved by the named owner, with compliance review where disclosures are affected
    • Changes tested in a DocuSign developer account or test template before release
    • Integration errors and failed envelope deliveries monitored and followed up
    • DocuSign release notes reviewed and relevant changes planned with you
  4. 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.

    • Completed documents and certificates delivered to your document system
    • Retention settings in DocuSign aligned to your records schedule
    • Envelope history retrieved on request for disputes or audits
    • Template and setting change history kept for examiners
    • Service review covering changes, issues and open risks

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Loan officer or closer

Loan officer, mortgage loan originator, closer, loan processor

Sends loan documents for signature and follows them to completion.

Sees

  • Templates available to their role and branch
  • Envelopes they sent, or their team's envelopes where shared
  • Envelope status and history for their transactions

Does

  • Sends envelopes from templates or from the loan system
  • Fills in transaction details the template asks for
  • Corrects or voids their own envelopes before completion, as procedures allow
  • Resends reminders and answers borrower questions

Cannot

  • Create or change templates
  • Change signer authentication required by a template
  • Change the consumer disclosure or account settings
Approvals
None in DocuSign; loan approvals follow your own procedures before documents are sent.
Notified about
Envelopes viewed, signed, completed or declined, and delivery failures.

Lending operations owner

Head of loan operations, mortgage operations manager, closing manager

Owns the signing processes and templates for the institution's loan products.

Sees

  • All templates, their versions and owners
  • Envelope volumes and failures by product and branch
  • Change requests and their status

Does

  • Approves template changes and new templates
  • Sets which templates each role and branch can use
  • Signs off template testing before release
  • Attends the service review

Cannot

  • Approve changes to the consumer disclosure without the compliance officer
  • Approve a change they requested themselves where a second approver is named
Approvals
Approves template and process changes; changes affecting disclosures or authentication also need the compliance officer.
Notified about
Changes waiting for approval, templates ready for testing and integration failures.

Compliance officer

Compliance officer, consumer compliance manager, chief compliance officer

Makes sure electronic signing meets ESIGN, UETA and disclosure requirements.

Sees

  • The consumer disclosure and its version history
  • Authentication rules by document type
  • Template change history and envelope evidence

Does

  • Approves the consumer disclosure text
  • Approves authentication requirements by document type
  • Reviews template changes that affect disclosures or their timing
  • Requests envelope evidence for complaints, disputes and examinations

Cannot

  • Change templates or settings directly
  • Send or void envelopes unless also given a sender role
Approvals
Required approver for changes to the consumer disclosure, authentication rules and disclosure templates.
Notified about
Changes needing compliance review and requests for envelope evidence.

Client DocuSign administrator

IT administrator, loan systems administrator

Manages users and first-line support within the delegated scope the institution keeps.

Sees

  • Users, groups and permission profiles
  • Open requests and tickets

Does

  • Adds, changes and closes sender accounts, or maps them from single sign-on
  • Assigns users to groups and permission profiles
  • Handles first-line sender questions
  • Raises change requests

Cannot

  • Change templates, the consumer disclosure or authentication settings
  • Grant themselves account administrator rights
Approvals
User changes follow your access procedures; changes they request to templates or settings are approved by the owners.
Notified about
Requests they raised, planned changes and DocuSign service notices.

Moraph DocuSign engineer

Moraph DocuSign engineer, Moraph integration engineer

Builds and maintains templates, settings and integrations under approved changes, and provides second-line support.

Sees

  • Account settings, templates and integration configuration
  • Envelope status and errors needed to support you
  • Document content only where a support task needs it and you have authorized it

Does

  • Builds and changes templates and settings under approved requests
  • Builds and monitors integrations with your loan systems
  • Follows up delivery failures and integration errors
  • Retrieves envelope evidence on request
  • Raises platform issues with DocuSign support

Cannot

  • Release a change without approval
  • Send envelopes to your customers on your behalf
  • View completed documents without an authorized support reason
Approvals
Every change needs approval from the lending operations owner, and from the compliance officer where disclosures or authentication are affected.
Notified about
Approved changes, integration failures and DocuSign service notices.

Moraph service manager

Moraph service manager, client success manager

Accountable for the service: requests, escalations, reporting and the service review.

Sees

  • All tickets, change requests and escalations
  • Service reports and open risks

Does

  • Runs the service review and records actions
  • Tracks requests to closure
  • Coordinates with DocuSign on platform issues
  • Raises risks such as templates without an owner

Cannot

  • Change templates or settings
  • Accept a risk on your behalf
Approvals
None of their own; decisions go to your owners.
Notified about
Escalations, overdue requests and DocuSign incidents affecting you.

Auditor or examiner (read-only)

Internal auditor, external auditor, regulatory examiner (under temporary access)

Reviews electronic signature evidence and controls without changing anything.

Sees

  • Envelope evidence for sampled transactions
  • Template versions, the consumer disclosure and change history
  • Evidence packs within the scope granted

Does

  • Reads evidence within their scope
  • Requests more evidence through the compliance officer

Cannot

  • Change, send or void anything
  • Keep access after it expires
Approvals
Their access is approved by your institution with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionLoan officerLending opsComplianceClient adminMoraph eng.Moraph serviceAuditor
Send envelopes from templatesOwn work onlyFullNo accessNo accessNo accessNo accessNo access
Correct or void an envelopeOwn work onlyFullNo accessNo accessNo accessNo accessNo access
Create or change a templateNo accessApprovesApprovesNo accessFullNo accessNo access
Change the consumer disclosureNo accessView onlyApprovesNo accessFullNo accessView only
Change signer authentication rulesNo accessApprovesApprovesNo accessFullNo accessNo access
Change account settingsNo accessApprovesView onlyNo accessFullNo accessNo access
Manage users and permission profilesNo accessView onlyNo accessFullFullNo accessNo access
Configure integrationsNo accessApprovesNo accessView onlyFullNo accessNo access
Retrieve envelope evidenceOwn work onlyFullFullNo accessFullNo accessView only
View change historyNo accessView onlyView onlyView onlyView onlyView onlyView only
Run the service reviewNo accessView onlyView onlyNo accessNo accessFullNo access
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Senders use templates; they do not build them. Template, disclosure and authentication changes are made by Moraph engineers and approved by your owners.
  • Changes to the consumer disclosure, authentication rules or disclosure templates need your compliance officer's approval as well as the lending operations owner's.
  • Moraph engineers work through named accounts with the permissions their tasks need. They do not send envelopes to your customers, and they open completed documents only for an authorized support reason.
  • Roles, groups and permission profiles are agreed during implementation; every change to them is recorded, and auditors get read-only evidence with a scope and an end date.

Features

What it does

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

How it connects to your systems

Connects toHowWhat flows
Loan origination systemEnvelopes 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.Out to DocuSign: documents, signer details and fields. In: envelope status and completed documents.
Document managementCompleted documents and certificates of completion delivered to your document or imaging system for retention.In to your system: completed documents, certificates and envelope identifiers.
DocuSign ConnectEnvelope events sent to your systems as they happen, so status updates without polling.Out: envelope and recipient status events.
CRMDocuments sent from your CRM, such as Salesforce, with status returned to the client record.Out: documents and signer details. In: status and completed documents.
Single sign-onYour staff sign in to DocuSign through your identity provider using SAML, so your MFA and leaver process apply.In: user identity, with provisioning where configured.
Identity verificationWhere licensed, DocuSign's ID verification checks a signer's government ID before they can sign higher-risk documents.In: verification result recorded in the envelope history.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

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.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Service operations

Change log

For lending operations owner and compliance officer

Every template and setting change in the period with its request, approvers, test result and release date.

Break down by
Change type, Template, Approver, Period
Delivered as
Moraph service portal; CSV and PDF export
Used for
Confirming every change was approved, including compliance review where required.

Requests and tickets

For lending operations owner and Moraph service manager

Open and closed requests and tickets with their age, status and who is waiting on whom.

Break down by
Request type, Status, Age band, Branch
Delivered as
Moraph service portal; CSV export
Used for
Keeping requests moving and seeing where decisions are needed.

Integration and delivery failures

For lending operations owner and IT

Envelopes that failed to create, deliver or return to your systems, with the cause and follow-up.

Break down by
Failure type, Integration, Template, Period
Delivered as
Moraph service portal; service report
Used for
Making sure no loan file is missing its completed documents.

Signing activity

Envelope volumes and status

For lending operations owner

Envelopes sent, completed, declined, voided and outstanding.

Break down by
Template, Branch, Sender, Status, Period
Delivered as
Service report; CSV export
Used for
Spotting stalled signings and where senders need help.

Declined and voided envelopes

For lending operations owner and compliance officer

Envelopes declined by signers or voided by senders, with the reasons recorded.

Break down by
Template, Reason, Branch, Period
Delivered as
Service report; CSV export
Used for
Finding templates or processes that confuse borrowers.

Controls

Template inventory

For lending operations owner and compliance officer

Every template with its owner, current version, authentication requirement and last change.

Break down by
Loan product, Owner, Authentication method, Last change
Delivered as
Moraph service portal; CSV export
Used for
Keeping templates owned, current and consistent with the design.

Consumer disclosure history

For compliance officer

Each version of the consumer disclosure, when it was in force and who approved it.

Break down by
Version, Effective dates, Approver
Delivered as
On request; PDF
Used for
Showing which disclosure a borrower consented to at the time.

User and permission review

For lending operations owner and information security

Users with their groups, permission profiles, administrator rights and last sign-in.

Break down by
Group, Permission profile, Branch, Last sign-in
Delivered as
On the review schedule you set; CSV export
Used for
Confirming or removing access and evidencing the review.

Regulatory and audit

Transaction evidence pack

For compliance officer, internal audit, examiners

For selected transactions, the completed documents, certificate of completion, envelope history and the template version and disclosure in force.

Break down by
Transaction, Template, Date range
Delivered as
On request; PDF bundle
Used for
Answering disputes, complaints and examiner requests.

Service review summary

For lending operations owner, compliance officer and management

Changes, failures, incidents and open risks for the period, with actions agreed.

Break down by
Period, Topic
Delivered as
PDF after each service review
Used for
Giving management a record of how the signing service was run.

Exports, access and evidence

  • Service reports are prepared by Moraph from DocuSign's reports and envelope data and from Moraph's change and ticket records.
  • DocuSign's own reports remain available in the account to the administrators and senders you authorize.
  • Evidence packs are assembled from DocuSign's envelope history and certificates; Moraph does not alter them.
  • Reports respect each viewer's role, and auditors receive evidence within the scope and dates you grant.
  • Retrieving and exporting evidence is itself recorded, so you can show what was given to whom.

Deployment

Where and how it runs

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 controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Discovery

We inventory loan products, document packages, current signing practices and the systems documents come from and go to.

Signing design

We agree the consumer disclosure, authentication by document type, signing order, retention and who owns each template, with your lending and compliance teams.

Account configuration

The DocuSign account is configured: settings, branding, groups, permission profiles, single sign-on and the consumer disclosure.

Templates

Templates are built for each document package and tested with your loan staff, including borrower-side signing on common devices.

Integrations

Integrations with your loan origination, document and CRM systems are built and tested end to end.

Training and go-live

Senders are trained on their templates, products go live in an agreed order, and change control, approvers and reporting move into day-to-day operation.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • 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.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. List your loan document packages and agree which can be signed electronically with your counsel
  2. Review the consumer disclosure and consent flow as a borrower would see it
  3. Send a test package and review the envelope history and certificate of completion
  4. Check that completed documents and certificates arrive in your loan or document system
  5. Walk through a template change that affects disclosures, from request to release
  6. Confirm the split of responsibilities between Moraph, DocuSign and your team

Questions

Frequently asked questions

Are DocuSign signatures valid for loan documents?

ESIGN and UETA give electronic signatures and records legal effect for most transactions, subject to exceptions and conditions such as consumer consent. Your institution and its counsel decide which documents to sign electronically; Moraph configures the workflows to that decision.

What evidence is kept for each signing?

DocuSign keeps an envelope history of each event and a certificate of completion, and seals completed documents so changes can be detected. Moraph makes sure these reach your system of record.

Can Moraph see our loan documents?

Moraph engineers open completed documents only for an authorized support reason, through named accounts, and do not send envelopes to your customers.

Do you support eNotes or remote online notarization?

Not as part of this service by default. They involve further requirements and products, and can be scoped separately.

How is it priced?

DocuSign plans are priced under DocuSign's terms, and the managed service and implementation are quoted separately. See Working with Moraph for what drives a quotation.

Can we leave the service?

Yes. The account, templates and records are yours. Moraph hands over documentation and change history and removes its accounts at the end of the agreement.

Next steps

Evaluate Digital Transaction Management

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Digital Transaction Management guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Digital Transaction Management support guide.