This page is for banks that will collaborate with a broker and have not (or will not) start the collaboration process by requesting purchase contract from the broker.
...
If the bank or the broker changes their intentions, either from digital to paper or paper to digital, this can change the business flow on both sides and must be communicated to the other party. Both parties must check for changes regularly and act correspondingly. When a broker changes it’s intention, EPS will generate an event (INTENTION_CHANGED) for the bank. The bank must take appropriate actions when receiving this event.
About references
The bank’s reference should be a case number or any other number that can be identified with the loan application case in the bank system. It should not be a traceId, correlationId, messageId or similar IDs that just identifies the request. If this reference could be given to Ambita support in case of problems, it would make it much faster for us to find the request and data in our logs.
Sending an intention to the broker
...
Both 201 and 202 status codes will have a payload containing a field named uniqueIdentifier identifying your intention. The intention can be retrieved later by performing a GET /eps/v1/bankintentions/<uniqueIdentifier>. The response will also have a field named settlementUniqueIdentifier. This is the unique identifier of a settlement that you must keep for later retrieval of data. Also all events will reference a settlement (NOTE: if requesting a purchase contract, some new events will not have this settlement identifier).
...
Now the broker knows the bank’s intention and the bank knows the broker’s intention. Again. both parties must agree on DIGITAL for it to be a digital process.
Also keep in mind that the intention can be changed later on in the process. The bank does this by again sending a bankintention but with the new flowCapability. The bank is notified by reading events and receiving an INTENTION_CHANGED event referencing the settlement unique identifier.
...
A bad request signals a failed validation of the input data or, in case of an Ambita broker, the intention didn’t match any settlements. The error object returned in EPS all contains a field message that we work hard on being human understandable. In case of a bad request, this message should be presented to the person in the bank handling the case as either the input must be changed or the broker must be contacted to find out what went wrong.
States and codes
...
A bank intention can have the following states
State | Description |
|---|---|
PENDING | Awaiting response from external broker. Result is available when event |
ACCEPTED | Intention was successfully matched with a broker settlement. |
REJECTED | Intention was received by the broker, but didn’t match a unique settlement. |
SENT | Used when intention change is sent to external broker. |
Note that for external brokers, the event INTENTION_RESPONSE_RECEIVED has a human understandable explanation in the event.description field that should be presented to the person in the bank handling the case. Only intentions that are accepted by a broker will receive updates if the flow changed. If an intention is rejected, the bank must send a new intention to the broker after agreeing with the broker what the correct data is.
Listening for events
| Plantumlcloud | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
If the bank would generate a forutsetningsbrev outlining the requirements to the broker, the new webservice generateForutsetningsbrev must be used as the old one generatePrerequisite is deprecated. Se more: Generate forutsetningsbrev
Sending the pantedokument to the broker
After the signed pantedokument is set in Etinglysing.no, the pantedokument (and forutsetningsbrev if any) can be sent to the broker using the webservice in Etinglysing sendToRealEstateBroker. This webservice method is described in more detail here: Send to real estate broker