Questions about e-Notes (SMART Documents)

Hi Ryan, I just received updates on this issue from our our R&D team, and this is the reply: "regarding the status, it is pending because registering a SMARTDoc with the MERS eRegistry failed. The root cause is that the MIN number for the document is too long, it must be 18 digit long. The MIN number for a document is specified in the JSON payload when you create the transaction. Please review the MIN number you provided when you created the transaction. Note: It is expected to have a pending status when it failed as explained." And there's some rules on this 18 digits MIN(Mortgage Identification Number):

MIN Details
MINs are exactly 18 digits.

A MIN has the following three sections (in order starting from the left most digits).

The 7 digit MERS Member ORG ID
The 10 digit unique sequence for the eNote
Check digit: The 1 digit that is calculated based on all the other digits to help prevent typos or transcription errors in MINs. (Note: our test harness will generate a new MIN with the correct check-digit value so any value for this digit can be used in the encoded JSON.)
For example, if you had the MIN 100316212345678903 the three sections would be: 

1003162 | 1234567890 | 3

1003162 is the MERS Org ID,

1234567890 is the unique part of the MIN,

and 3 is the check digit.

The attachment is the c# code to generate the whole MIN with 7 digits OrgID and 10 digits sequence number. Hope this could help you! Duo

Hi Ryan, First, to be able to use e-Mortgage, please make sure you have an ESL account belonging to e-mortgage tenant(must be a different account from your e-lending account cause one account be only belong to one tenant). You can contact our support team at [email protected] with necessary information to have your account settled. Then, you'd follow the similar steps as e-lending. The "enote_data_sectoin" and "enote_attribute" fields should also be under the "data" field in your package JSON. Please refer to attachment for a standard payload. There're few places I want to make a supplementation to the document site: For "enote_attribute": 1. please include "enote_template_name": "template_3200_enote.xml/template_3244-1_enote.xml" this attribute, as it tells OneSpan Sign which template to use to match your XML in "enote_data_section" For "enote_data_section": 1. please make sure the "BorrowerID" in field of XML matches your signer ID 2. please make sure , the value is unique to your vault. Once your package is created, a Loan template file will be created and uploaded to transaction automatically with your XML content injected and this loan already contains the signature as you has told OSS which signer to match in your XML. It is this file which will be sent to vault after the package is finished. Hope this could help you! Duo

Duo - Thanks for the response. Just so that everything is clear, both the enote_attribute and enote_data_section should both contain the data in an Encoded Base64 string value, correct?

Hi Ryan, Yes, both of these fields should be encoded into Base64 string just like e-lending process. enote_attribute includes the encoded basic information of the loan and enote_data_section includes the encoded XML. Duo

Once your package is created, a Loan template file will be created and uploaded to transaction automatically with your XML content injected and this loan already contains the signature as you has told OSS which signer to match in your XML. It is this file which will be sent to vault after the package is finished.

Is this something that can be viewed by the party once the signing has been completed or even before the signing has started?

Hi Ryan, Yes, you can this file directly from your web portal or through API call as the attachment shows. This loan file doesn't has a default name and all contents and signatures have been already created for you. Hope this could help you! Duo

Duo, I've tried a few different times but it appears that I am not getting the SMART Note created. I am getting no errors from the JSON package that I am sending and all documents are being pushed with proper positions. I get someone to look at my JSON and see if I am doing something wrong? I'll be sending it to the development email here shortly.

Hi Ryan, Have you had your account added under the e-mortgage tenant through our support team? Duo

Duo, We were told earlier that it was setup that way. We've reached out to support a day or so ago but I do not know the results. Is there a way we can speed up the process on their check to see if it is set up correctly?

Hi Ryan, Can you send your ticket number to [email protected]? Duo

For “enote_data_section”: 1. please make sure the “BorrowerID” in field of XML matches your signer ID 2. please make sure , the value is unique to your vault.

Duo - I am going back and testing this but this makes me wonder. Are you saying that if I use the term Borrower01 for any signer across any package, I can only use it once?

Hi Ryan, #1. BorrowerID just needed to be unique within the package, so “Role1” “Role2” is fine to use #2. “MERS MERS_MINNumber” this number needed to be unique within all transaction in your vault, that’s why only one smart doc goes to your vault. And if the original smart doc didn’t go to the vault, I guess this mortgage trade won’t take effect. #3. The name problem seems a known issue and I will also write this down in ticket. Hope this could help! Duo

Duo - Thanks for the update.