Overview
MoneyKit Connect emits certain events during the flow which enables partner applications to gain further insight into what is going on as their user goes through the linking flow. The events will be surfaced to you through the onEvent callbacks that MoneyKit Connect provides.
The events returned will provide three pieces of data:
Event Names
The first piece of information that an event will return is a name. This is how you identify what type of event occurred. Here the the options for event names:
open
The user has opened the Link flow.
exit
The user has exited without completing the Link flow and the onExit
callback is fired.
success
The user has exited Link after successfully linking.
error
An error occurred in the Link flow. See Errors for more details.
change_screen
The user has moved from one view to the next.
select_institution
The user selected an institution.
search_institution
The user has searched for an institution.
acknowledge_institution_alert
The user has tapped continue on the institution alert.
Note: This can be shown when institutions that have regular downtime or require special information during login
dismiss_institution_alert
The user has tapped to dismiss / close the institution alert.
open_institution_website
The user has tapped to open the institution website from the institution alert screen.
submit_credentials
The user has submitted credentials.
select_help
The user has selected the help button on the credentials screen.
select_reset_password
The user has selected the reset password button from the help sheet.
open_oauth
The user has navigated to a third-party website or mobile app in order to complete the OAuth login flow.
submit_otp_device
The user has submitted their preferred device to receive the OTP.
submit_otp
The user has submitted the one time password.
submit_mfa
The user has submitted MFA.
submit_permissions
The user has agreed to the set of permissions prompted for data access.
submit_accounts
The user has submitted the accounts which they want to link.
select_report_issue
The user has selected the report issue feature.
submit_report_issue
The user has submitted an issue to MoneyKit.
Event Properties
The second piece of information that an event will return is the properties. The properties are a collection of key value pairs related to the event and will provide you extra detail related to the event.
For example, when you receive a change_screen
event, the properties will inform you which screen was loaded:
Another example is when you search for an institution, the properties will inform you what the end user’s search term was:
Event Meta
The final piece of information that an event will return is meta, which is another collection of key value pairs with extra detail related to this linking session. For example:
The meta will return you the link_type
which will inform you if the user is creating a new link or is relinking an existing, broken link. It will also return you the link_session_id
in question and the timestamp of the event.
Default properties
All Events
All events should have the following default properties inside the meta
node:
All Link Events
Once an institution has been selected and a link has been started all events should have the following properties available in the meta
node: