Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

How To...

Connect OAuth provider with Client Keys

Salt Edge now supports Account Information Services channels, which can be used with PSD2 and Open Banking compliant APIs. Read about it in Salt Edge Documentation.

  1. Register application deep-link in Manifest.

              <action android:name="android.intent.action.MAIN" />
              <category android:name="android.intent.category.LAUNCHER" />
          <intent-filter android:label="@string/app_name">
              <action android:name="android.intent.action.VIEW" />
              <category android:name="android.intent.category.DEFAULT" />
              <category android:name="android.intent.category.BROWSABLE" />
              <!-- Accepts URIs that begin with "custom_scheme://custom_host/custom_path" -->
  2. Init SDK with returnToUrl as application deep-link

      String returnToUrl = "custom_scheme://custom_host/custom_path";
  3. Fetch providers and select one

  4. Create Connect Session

  5. Open received connectUrl in external app

        private void loadConnectUrl(String connectUrl) {
            if (provider.isOAuth()) {
                this.startActivity(new Intent(Intent.ACTION_VIEW, Uri.parse(connectUrl)));//Open in external app
            } else {
                SEWebViewTools.getInstance().initializeWithUrl(this, webView, connectUrl, this);//Open in WebView
  6. All connect operations (Authorizations, Fetching, etc.) will be performed in external app.

  7. If deep-link is received (bu Activity declared in Manifest), then extract customer_secret from params.

        String dataString = getIntent().getDataString();
        if (dataString != null) {
            Uri uri = Uri.parse(dataString);
            String connectionSecret = uri.getQueryParameter(Constants.KEY_CONNECTION_SECRET);
            if (connectionSecret != null && !connectionSecret.isEmpty()) {
                //Save received `connection secret` for future operations

App-2-App redirect

The most common case of Salt Edge Connect usage is when TPP application initiate connect of Account and opens Salt Edge Connect url in WebView. There are a lot of banks which require authentication/authorization in bank applications, but in that case redirection outside of will remain in WebView and flow will get stuck.

First solution is to open all Salt Edge Connect URL's (or URL's for oauth providers) in external browser.
app-2-app redirect base flow

Second solution is to open Salt Edge Connect in the WebView and handle all redirections outside Salt Edge ( and open them in external browser/application.
app-2-app redirect hybrid flow

Instead of WebView you can open url in ChromeCustomTab, but you should be ready for exceptions, then no browsers which supports ChromeCustomTab.

After successful authentication user will be redirected back to TPP app. We propose to use deep-link with custom scheme (like: mytpp:// as return url. Same type of deeplink uniquely identify your application in the system and eliminate doubts where to redirect, as well as they are easy to implement.

Copyright © 2014 Salt Edge Inc.