Open Banking
Supporting Open Banking
Listening for the OAuth signal
- iOS: The SDK will listen for the signal and launch the system browser when needed.
- Android: The SDK will listen for the signal and launch the system browser when needed.
-
JS SDK: When used in a browser the OAuth flow will be handled automatically. If integrating in a
different context when instantiating the SDK, provide the
openBankingRedirect
option with your custom app scheme or universal link. Once an OAuth flow is triggered, a message will be posted to the window with atype
property ofoauthUrl
and aurl
property containing the URL that needs to be launched.
Handling the return signal
The webview will continue polling while the user is going through the OAuth flow. The webview should not be destroyed when the OAuth URL is launched and should be returned to the screen once the return signal is received.
External Documentation
Setting up custom scheme
- iOS: Defining a Custom URL Scheme for your app
- Android: Create Deep Links to App Content
- React Native: Deep linking
Setting up Universal Link
- iOS: Supporting Associated Domains
- Android: Create Deep Links to App Content, and Verify Android App Links
- React Native: See above (Deep linking)
Testing Open Banking
To test enrolling via open banking, search the institution list for "DAG OAuth" and use the following credentials:
Description | Username | Password |
---|---|---|
Full account and routing number | Certegy.site16441.3 |
site16441.3 |
Missing account or routing number | Certegy.site16441.4 |
site16441.4 |