Connect Web SDK 2.0
The Connect Web SDK allows you to embed Finicity Connect into an iFrame, or you can add Connect into its own popup window. See Connect Web Popup Window. Either implementation method allows you to add Connect anywhere you want within your own web applications.
New and enhanced features for Connect 2.0 include:
Connect 2.0-SDK, Route, and User Events
All events are sent from the Connect application through the SDK to your web and mobile applications. There are three different event types:
- 1
Web SDK 2.0 Events help you monitor the Connect application. You’ll receive a notification when the following events are triggered:
– loaded
– canceled
– errored
– resize - 2
Route Events 2.0 (optional) provides visibility into which screen the user is currently interacting with as they navigate through the Connect application.
- 3
User Events 2.0 (optional) allows visibility into what action a user could take within the Connect application, including alerts.
Connect 2.0 Error Codes
Error codes display when something interrupts the process flow of the Connect application. The error code number and description help you know what the issue is and how to resolve it.
| Code # | Description |
|---|---|
| 100 | User exited out of Connect |
| 200 | Success |
| 401 | Unauthorized |
| 500 | Unexpected error |
| 1201 | Connect Fix initiated without accounts |
| 1403 | OAuth popup blocked |
| 1412 | Invalid SDK implementation |
| 1440 | Timeout, the user is logged out after being inactive for 5 mins |
| 10039 | Tampered Connect link |