This topic contains 11 replies, has 2 voices, and was last updated by  Duo_Liang 1 week, 4 days ago.

  • Author
    Posts
  • Participant
    Ryan_Coleman
    Regular Member
    Member since: 16.07.2018
    Number of posts: 44

    Guys,

    I am looking over this page on the package settings for when we need to have a SMART Note created.

    https://docs.esignlive.com/content/c_integrator_s_guide/rest_api/package_settings_for_mortgages.htm

    Here it says that we need to include the following two fields.
    enote_data_section
    enote_attribute

    Is it safe to assume that these need to go at the root JSON element when sending them? Also, do you guys have any better examples then what is posted on the page?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 398

    Score

    0

    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 sign.support@onespan.com 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 Liang
    OneSpan Junior Technical Evangelist

    • This reply was modified 2 weeks, 4 days ago by  Duo_Liang.
    Attachments:
    You must be logged in to view attached files.
    Participant
    Ryan_Coleman
    Regular Member
    Member since: 16.07.2018
    Number of posts: 44

    Score

    0

    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?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 398

    Score

    0

    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


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    Ryan_Coleman
    Regular Member
    Member since: 16.07.2018
    Number of posts: 44

    Score

    0

    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?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 398

    Score

    0

    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 Liang
    OneSpan Junior Technical Evangelist
    Attachments:
    You must be logged in to view attached files.
    Participant
    Ryan_Coleman
    Regular Member
    Member since: 16.07.2018
    Number of posts: 44

    Score

    0

    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.

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 398

    Score

    0

    Hi Ryan,

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

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    Ryan_Coleman
    Regular Member
    Member since: 16.07.2018
    Number of posts: 44

    Score

    0

    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?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 398

    Score

    0

    Hi Ryan,

    Can you send your ticket number to developer@esignlive.com?

    Duo


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    Ryan_Coleman
    Regular Member
    Member since: 16.07.2018
    Number of posts: 44

    Score

    0

    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?

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 398

    Score

    0

    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 Liang
    OneSpan Junior Technical Evangelist
    • This reply was modified 1 week, 3 days ago by  Duo_Liang.

You must be logged in to reply to this topic.