Typical use case

The Payer PSP must invoke this API in the following situations:

After presenting the MyBank Login page: the API must be invoked passing in keys the key "LANDING_URL_CONSUMED".
After the Payer's successful authentication: the API must be invoked passing in keys the key "AUTHORISING_USER_AUTHENTICATED".
After presenting the MyBank Authorisation page: the API must be invoked passing in keys the key "TRANSACTION_DATA_DISPLAYED".

Request body attributes

All attributes in the request body are mandatory:

institute, token : needed to identify the transaction
keys : list of "key" values indicating the events (typical use will require to send one key at a time)

Typical use of the response

n/a

IMPORTANT: as this API only serves as a complementary source of information, useful for diagnostics, it is recommended to trap/catch any error that might occur from its invocation, to prevent the transaction flow from being interrupted. For example, in case of network timeout or any other communication error in the invocation of this API, the application flow should continue (i.e., the status of a MyBank Transaction should NOT be set to ERROR because of such errors).