Versions Compared

Version Old Version 9 New Version Current
Changes made by

Ronny Opsahl

Bjørn Hamre

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Figure 7 Collaboration overview

For more information about detailed flows and error cases see scenarios for sending pantedokument to broker.

New, easier flow with Etinglysing version 51.38

From version 51.38 of Etinglysing, the new method sendToRealEstateBroker makes it transparent for the integrator (bank) whether the broker is an Ambita broker or not. Banks can always use flow DOKUMENT_TIL_OPPGJOER when generating the pantedokument and the new method sendToRealEstateBrokerwhen sending it to the broker.

If the signed document is set in Etinglysing, it can be sent to broker with the sendToRealEstateBroker service where only the documentId and broker’s organization number is needed. Any associated prerequisite letter will be sent together with the pantedokument.

sendToRealEstateBroker( long documentId, String brokerOrganizationNumber, Base64 pantedokumentSdo, Base64 prerequisiteDocument, String prerequisiteDocumentMimeType )
Code Block
languagexml
<dok:sendToRealEstateBroker>
   <documentId>123456</documentId>
   <brokerOrganizationNumber>111222333</brokerOrganizationNumber>
</dok:sendToRealEstateBroker>

It is also possible to set the signed document (and optionally prerequisite letter) and send it to the broker in one action:

Code Block
languagexml
<dok:sendToRealEstateBroker>
   <documentId>123456</documentId>
   <brokerOrganizationNumber>111222333</brokerOrganizationNumber>
   <pantedokumentSdo>"Base64 encoded signed pantedokument"</pantedokumentSdo>
   <prerequisiteDocument>"Base54 encoded prerequisite letter"</prerequisiteDocument>
   <prerequisiteDocumentMimeType>PDF</prerequisiteDocumentMimeType>
</dok:sendToRealEstateBroker>

Input:

Parameter

Required

Description

documentId

true

The unique id returned from the generatePantedokument action

brokerOrganizationNumber

true

This is the organization number of the broker that the pantedokument should be sent to..

pantedokumentSdo

false

The Signed Data Object representation of the pantedokument. Only needed if it is not set previously using setSDO or setSDOList actions.

prerequisiteDocument

false

The terms from the bank to the broker as PDF or as an XML document according to the standard defined by DSVE If the generatePrerequisite has been called prior, there is no need to specify this unless you want to override the prerequisite previous generated.

prerequisiteDocumentMimeType

false

Format of prerequisite document. Must be set if prerequisiteDocument is present. Supported types are “XML” and “PDF”.

This service requires the documentID from the generatePantedokument call and the broker’s organization number. When called www.etinglysing.no will push the signed document to the relevant EPS settlement, if found (for Ambita’s brokers). If no settlement process is found when sendToRealEstateBroker is called, the pantedokument (and prerequisite letter, if any) will be sent to the broker using the Afpant channel (Non-Ambita brokers).

...

See here for more info about document flow and statuses

The pantedokument will get the status “SAMHANDLING_FEILET” if:

...

  1. Get the status for the document. How to get status.
    Then in documentMessages the errorCode will be “9999” and in detail you will find the reason for failure.

    Example of a get status response xml where the pantedokument has mismatch in buyer:

    Code Block
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <ns2:getStatusResponse xmlns:ns2="http://dokument.ws7.etinglysing.no/">
         <return>
            <status>
               <created>2020-12-17T15:00:00.306+01:00</created>
               <documentStatusTinglysing/>
               <id>15759414</id>
               <statusCode>SAMHANDLING_FEILET</statusCode>
               <description>Pant - 4601/121/45// [G]</description>
               <reference>Mona 167</reference>
            </status>
            <type>PANTEDOKUMENT</type>
            <documentVersion>KARTVERKET</documentVersion>
            <documentMessages>
               <documentMessage>
                  <detail>Kjøper mangler: Fant ikke oppgjør for angitt kjøper</detail>
                  <errorGroup>EKSTERNFEIL</errorGroup>
                  <message>Samhandling feilet</message>
                  <errorCode>9999</errorCode>
               </documentMessage>
            </documentMessages>
         </return>
      </ns2:getStatusResponse>
   </soap:Body>
</soap:Envelope>

  2. or if you are monitoring events. How to monitor events.
    Read the events of type “STATUSOVERGANG” for the document where ny_status is “SAMHANDLING_FEILET” and you will find out the reason for failure in beskrivelse.

    Example of listHendelser response xml for event type “STATUSOVERGANG”. This is an event for dokument with id 15759414 where ny_status is “SAMHANDLING_FEILET”:

    Code Block
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <soap:Body>
      <ns2:listHendelserResponse xmlns:ns2="https://ws.etinglysing.no/hendelse/v6">
         <return>
            <id>805097</id>
            <type>STATUSOVERGANG</type>
            <dokumentId>15759414</dokumentId>
            <eksternEierId/>
            <nyStatus>SAMHANDLING_FEILET</nyStatus>
            <gammelStatus>SENDT_TIL_MEGLER</gammelStatus>
            <beskrivelse>Fant ikke oppgjør for angitt kjøper</beskrivelse>
            <opprettet>2020-12-17T15:37:35.705+01:00</opprettet>
            <eksterntOpprettetDokument>true</eksterntOpprettetDokument>
            <dokumentRef>Mona 167</dokumentRef>
            <dokumentType>PANTEDOKUMENT</dokumentType>
         </return>
      </ns2:listHendelserResponse>
   </soap:Body>
</soap:Envelope>

...