App2app redirect consistency in iOS

The simplest way to implement app2app redirection in iOS is to shift responsibility to the browser application. But what about user experience? How can the flow be seamless and consistent? The iOS system gives us pretty clear answers on that.


Diagram 1. Redirection steps in app2app and app2web flow

Let’s review how the iOS app can handle at its best the redirection from TPP app to either bank’s website or application. In the below videos that present examples of app2app or app2web redirect methods, Fentury represents a TPP application that is integrated with Salt Edge Connect widget.

Redirect to Salt Edge Connect widget

iOS application can trigger Salt Edge Connect widget to open in 2 ways. Both methods together with examples are reviewed below.

1. Redirect via Browser app

When the end-user is redirected from the TPP app to the Salt Edge Connect widget, the last is simply opened in a browser tab, Safari by default. After the end-user gives their explicit consent to the action on the Salt Edge Connect page (e.g. sharing account information), Safari redirects the end-user to the bank’s mobile application.

The consequence of this approach is an opened browser tab with a dead session of the Salt Edge Connect widget (after the first step in the above diagram), whilst a small modification can eliminate this unwanted inconvenience completely.

Method applicability advice: The redirect via Safari is not a preferable method to be used. Three applications are participating in the flow and it might confuse the user why the browser app has been opened. There is a high chance for users to abandon the flow altogether.

The below video shows an example of this method being used.

2. Redirect via SFSafariViewController

Unlike Android, iOS applications should always open the Salt Edge Connect widget with SFSafariViewController. It is a simple technology and doesn’t require much time for implementation. SFSafariViewController opens the Salt Edge Connect page and then handles all redirects correctly. End-user is redirected to the bank’s website (app2web), while the entire flow is kept within one session. This behavior is familiar for iOS users and brings a seamless user experience.

Method applicability advice: Redirect via SFSafariViewController is a method preferable to be used for opening Salt Edge Connect widget as well as for redirection to the bank website.

The most efficient and user-friendly method of app2web redirection flow is presented in the diagram below.


Diagram 2. iOS app2web redirection steps, best practice

The below video shows an example of the redirection flow that uses the SFSafariViewController method.

Best app2app redirect method

Given the fact that redirection via browser method offers a bad user experience, the SFSafariViewController technology is a perfect match for all the redirection needs. Hence, it is considered the best approach to handle app2app redirection for iOS. Salt Edge Connect widget is opened with SFSafariViewController, and then the end-user is redirected to the bank’s mobile app.

The most efficient and user-friendly method of app2app redirection flow is presented in the diagram below.


Diagram 3. iOS app2app redirection steps, best practice

The below video shows an example of the redirection flow from the Salt Edge Connect widget (opened with SFSafariViewController) to the bank’s mobile app.

The below video shows an example of the redirection flow from the Salt Edge Connect widget (opened with SFSafariViewController) to the bank’s mobile app.

Salt Edge team is always eager to help you on the journey to the best user experience, so feel free to contact us.

About Salt Edge

Salt Edge – a financial API platform with PSD2 and open banking solutions. The company has two main vectors of activity: enabling third parties to get access to bank channels via a unified gateway, and developing the technology necessary for banks to become compliant with the directive’s requirements. ISO 27001 certified and AISP licensed under PSD2, the company employs the highest international security measures to ensure stable and reliable connections between financial institutions and their customers. The company is integrated with 5000+ financial institutions in 50+ countries.

More information:  www.saltedge.com
Phone number: +1-437-886-3969
Email: press@saltedge.com

Salt Edge report

Discover what is the current state of open banking payments in Europe in 2021

Download now

Related articles

5 min read Jul 2020

Unfolding the new design of Salt Edge client dashboard

Design brainstorming sessions, UX/UI research, hours of prototyping, and deep analysis of clients’ feedback have kept us busy lately and resulted in a newly improved client dashboard. Considering clients’ suggestions, we’ve shaped a friction-less dashboard to show critical and pertinent data at-a-glance. Our top priority was not only to create…

4 min read Oct 2020

Finom selects Salt Edge to simplify finance management for European SMEs

The B2B financial service Finom joined hands with Salt Edge, a leader in offering open banking solutions, to innovate business management processes for SMEs and professionals all over Europe. Today open banking technology helps entrepreneurs manage their money more efficiently with their smartphones only. Finom is a B2B financial service…

3 min read Mar 2021

Salt Edge joins openFinance Advisory Group & Board powered by Berlin Group

Being a pioneer in developing open banking solutions, Salt Edge’s main goal is making headway toward open banking expansion and accessibility. That’s why joining the Berlin Group’s openFinance Advisory Group & Board was a natural step. The consultative panel was established by The Berlin Group – a pan-European initiative aiming…

8 min read Jan 2020

Why PISPs should not be required to perform AML checks toward PSUs

According to PSD2, a payment initiation service provider (PISP) represents a payment institution, and thus falls under the Anti-Money Laundering (AML) and Anti-Terrorist Financing (ATF) regulations. Yet, for many market participants, the setup of these checks from PISP’s side is not clear. I think this is an interesting topic that…