Versions Compared

Version Old Version 1 New Version Current
Changes made by

Bjørn Hamre

Bjørn Hamre

Saved on

Key

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

At eAt present time the bank probably receives more events than it should. Early 2023 we will change how events are created and fetched som that we can be more accurate.

...

These are the events that are related to communicating the intended flow/registration method (Paper og Digital) between the bank and the broker. The table below lists and describe the relevant events for the bank.

Event type

Description

Comments

Event code

INTENTION_SENT

Used for two cases:

  • Intention from bank sent to broker via Altinn

  • Intention change sent from bank to broker.

We should probably introduce an INTENTION_CHANGE_SENT to be used for intention changed messages.

INTENTION_RESPONSE_RECEIVED

Intention response received from broker via Altinn

Event code can be used to determine if intention was accepted or rejected. In both cases description will give a human readable information about the result. In case of accepted, the settlement is updated with broker’s flow and must be read to see if it’s paper or digital.

  • EPS_EV0001, accepted.

  • EPS_EV0002, rejected

INTENTION_CHANGED

Intention changed

This event type is only used when the registration method (DIGITAL | PAPER) is changed.

PURCHASE_CONTRACT_RESPONSE_RECEIVED

Response from external broker on request for purchase contract is received

Need new query parameter contractevents=true to receive this event.

  •  Bjørn Hamre Describe the use of event codes in these events

Will not reference a settlement.

PURCHASE_CONTRACT_CHANGED

Some significant data in the purchase contract has changed

settlementChanges will have a list of categories for what has changed