Expere Transaction XPaths for eOriginal
The following Expere Txn Xpaths should be used when working with eOriginal transactions to ensure proper eNote creation and execution.
| Txn Xpath | Xpath Option/Description |
|---|---|
| /Txn/EClosingType | 1 = eNote only 2 = Full eClosing (not currently supported) |
| /Txn/EOriginalEsignInd | 0 (F) = eSign is NOT configured within eOriginal 1 (T) = eSign is configured within eOriginal |
| /Txn/EOriginalDestructionType | 0 = Do NOT execute Destruction 1 = Destruct managed doc profiles only 2 = Destruct ALL doc Profiles 3 = Destruct Transaction |
| /Txn/EOriginalTransactionTypeName | (String data) Specifies the transaction type template for an eOriginal transaction. Transaction types are reusable transaction templates. Data, settings, and document types are pre-configured and saved in a transaction type, alleviating the need to input data and add documents each time a transaction is created. This is a preconfigured value setup within eOriginal. |
| /Txn/EOriginalUploadInd |
|
| /Txn/EOriginalTransactionBusinessProcessName | Can be included when creating an enote through the
eoCreateTransaction method and is used to filter
transactions by line of business. This Xpath contains a string value
that limits the transactions visible to the financial institution's
employees so they only have access to the transactions that pertain to
their group. |
| /Txn/EOriginalUploadTransactionType | Specifies to which eOriginal vault documents should be uploaded.
|
| /Txn/EOriginalPreviewOnDemandEnvironmentInd | Indicates the environment the lender wants to send their
transaction:
Note: This data point is only applicable in the CT
environment. |
| /Txn/EClosingNoPDFCopyInd | indicates whether or not to print a PDF copy of the eNote:
Note: If a XPath value is not provided, the
PDF Copy will be created. Users do NOT need to provide a
value. |
| /Txn/EOriginalNotUsedInd | Indicates whether or not to send an Expere-generated eNote:
|
| /Txn/EOriginalMERSReverseRegistrationInd | Indicates whether or not to reverse register Expere Enotes.
|
| /Txn/EClosingNoteInd | Indicates the lender wants to include the full eNote and not the
placeholder eNote.
|
| /Txn/EOriginalIncludeUniquePasscodeInd | Indicates if the user is sending a Unique Passcode in their
transaction. If true, the unique passcode should be sent to eOriginal
|
| /Txn/EOriginalIncludeSmartDocXHTMLInResponseInd | Indicates if the user wants the SmartDocXHTML included in the
response if EOriginalNotUsedInd = 0, Blank or Does not exists. If true,
the SmartDocXHTML is included in the response file.
|
| /Txn/OrgExemptInd | This is an optional element used to determine if a financial
institution is exempt from state licensing requirements.
|
| /Txn/FHAAmendedGSEInd | Determines whether to provided 2023 amended FHA documents.
Note:
Note:
|
Signer types
Note: the Signer types below are supported with the eNote; all other other documents
will support anyone who is eSigning.
The following Signer types are supported:
- /Txn/CoSigners/CoSigner
- /Txn/CoSigners/CoSigner/PowerOfAttorneyName
- /Txn/CoSigners/CoSigner/PowerOfAttorneyEmailAddress
- /Txn/EOriginalAdditionalItems/EOriginalAdditionalItem/UniquePasscodeDesc
- /Txn/Borrowers/Borrower
- /Txn/Borrowers/Borrower/PowerOfAttorneyName
- /Txn/Borrowers/Borrower/PowerOfAttorneyEmailAddress
- /Txn/EOriginalAdditionalItems/EOriginalAdditionalItem/UniquePasscodeDesc
Note: The following elements are required for each Party on the eNote:
- FirstName
- LastName
- SSNNote: for all other parties where we don't collect a SSN; we require that our users pass in the override that utilizes the unique passcode description. Refer to Password Override for more information.
- EmailAddress
- RembrandtID or SignerID