PREREQUISITESSign up for a developer account on the Client Dashboard.
1. Install the SDK
Install the SDK at the root of your project using your preferred package manager.- npm
- yarn
2. Generate the Widget URL
There are two options to generate the widget URL:- Option A: Using a Platform API endpoint
- Option B: Using a proxy server
a. Platform API
Use the Request Widget URL endpoint to get a URL. Note that thisurl expires after ten minutes or upon first use, so you may need to request it again while following this guide.
- Request
- Response
b. Proxy Server
The SDK can make requests on your behalf to your backend service that calls the Platform API. Pass the proxy URL to a widget component via theproxy prop.
When using a proxy server, pass the widget’s configurations directly to the widget component.
Configurations List
Configurations List
| Configuration option | Description |
|---|---|
colorScheme | Load the widget with the specified color_scheme; options are light and dark. Defaults to light. |
currentInstitutionCode | Load the widget into the credential view for the specified institution. |
currentInstitutionGuid | Load the widget into the credential view for the specified institution. |
currentMemberGuid | Load the widget into a specific member that contains an error or requires multifactor authentication. The widget will determine the best view to load based on the member’s current state. current_member_guid takes precedence over current_institution_code and current_institution_guid. |
disableInstitutionSearch | This determines whether the institution search is skipped within the Connect Widget. This option must be used with current_institution_code, current_instituion_guid, or current_member_guid. You must listen to the backToSearch postMessages to intercept the user navigating back to search during the flow. Defaults to false. |
includeTransactions | This determines whether transaction data are retrieved. Defaults to true in aggregation mode and false in verification mode. This can be set in either aggregation or verification mode. This option does not affect future foreground or background aggregations. |
language | Load the widget in the specified language. Defaults to en-US. For more info, Language Support. |
uiMessageWebviewUrlScheme | This is a client-defined scheme used in OAuth redirects in WebViews; also used in URL updates when these replace postMessages in WebViews. Defaults to mx. |
updateCredentials | Load the widget into a view that allows them to update the current member. Optionally used with current_member_guid. This option should be used sparingly. The best practice is to use current_member_guid and let the widget resolve the issue. |
Proxy
3. Import the SDK and Render the Widget
Now that you can generate a widget URL, import components from@mxenabled/react-native-widget-sdk and render them in your application.
SUCCESSYou’ve set up the SDK and embedded the Connect Widget!
Props
You can configure the state and behavior of a widget with the following component props:| Component prop | Description |
|---|---|
proxy | Proxy server URL. |
style | Styles applied to the view containing the widget. See React Native’s style documentation. |
url | Widget URL. This prop is required. |
OAuth Redirects
To properly handle OAuth redirects from the Connect Widget back to your application when using the React Native SDK, you need to:- Update your application and enable deeplinking from native code into the React Native layer. See Linking for instructions.
- Ensure your application has a scheme. You can install and use the URI scheme package to manage your application’s schemes.
- Provide your application’s scheme to the widget component with the
uiMessageWebviewUrlSchemeprop. Expo applications that are not deployed as standalone applications should useclientRedirectUrlinstead (see note below).
Scheme
Handling Events
If you’re using the React Native SDK, you’ll listen for widget events by passing callback props in the widget component. The prop names follow the naming scheme below.| Event | Prop |
|---|---|
| Widget | on<event name> |
| Entity | on<entity><action> |
user_guid (string) and session_guid (string) fields.
The following is an example integration that lets you listen to the events we send.
Troubleshooting
If widget events aren’t triggered, check the following:- Ensure your widget URL request is correctly configured for the React Native SDK:
ui_message_versionis set to4is_mobile_webviewis set totrue
- Ensure you use the corresponding widget component for the
widget_typein the widget URL request. For example, if you setwidget_typetoconnect_widget, use theConnectWidgetcomponent.

