Mobile SDK Orchestration Helps Banks Achieve 3 Strategic Goals

Mobile Banking

The mobile channel doesn’t grow itself. It requires a strategy, a team committed to execution, and constant care and grooming.

As financial services organizations embark on mobile-first initiatives or offer more and more mobile services to their customers, they prioritize three goals:

1. Optimize both user convenience and security
2. Stay ahead of the curve on mobile security and authentication
3. Increase developer productivity to accelerate time to market

As the mobile channel grows, it ripens as a target for attackers – and consumers know this. In fact, the Federal Reserve reports that non-users said their concerns about the security of mobile banking (73 percent) and mobile payments (67 percent) were barriers to adoption. Consumers are looking for security in their mobile banking apps, and financial institutions want to provide that reassurance.

Tech-savvy early adopters also appreciate mobile apps that take advantage of the latest and greatest technology available on their devices, including those that remove friction from the authentication experience. Different people want and accept different biometrics and many want a choice in the matter. For example, which mobile banking app is an iPhone X user more likely to choose – one that supports Apple Face ID or one that doesn’t?

Today’s mobile-first consumers also want the latest features as quickly as possible. Development teams feel the pressure to code and ship mobile apps and new features faster – or risk losing users to more agile competitors. Tools that reduce complexity and make developers more productive are a win-win. The line of business can release new mobile apps and features faster, and developers can reduce some of the more menial tasks in their queue.

Growing Mobile Faster with Orchestration

No matter how fast your cadence of mobile app releases, you’ll never stop asking yourself whether you can go faster.

Orchestration can help developers simplify the integration of authentication and related capabilities into mobile applications. VASCO recently introduced the Orchestration SDK for the DIGIPASS for Apps developer toolkit to empower organizations with new mobile app projects. With the Orchestration SDK, banks and financial services organizations can offer users more authentication choices, increase developer productivity, and accelerate time to market.

Streamlining Mobile App Development Efforts

The Orchestration SDK consolidates and automates a number of services to minimize the development efforts necessary to integrate DIGIPASS for Apps authentication and security features into new mobile app projects. By significantly reducing the number of API calls required to execute a number of functions, the Orchestration SDK makes mobile app development easier, reduces development costs, and helps increase release frequency.

Orchestration also future-proofs apps. It prevents future rework (i.e., technical debt) by reducing the development efforts necessary to adopt the latest biometric technology. By building in plug-and-play support for new biometric options, developers don’t have to recode the app, resubmit it to app stores, or persuade users to update when new biometric technology becomes available.

This becomes all the more important with users wanting more intuitive and convenient authentication options that take advantage of the latest and greatest technology available on their mobile devices. The DIGIPASS for Apps Orchestration SDK makes it simple for developers to quickly adopt new authentication technology within their app, using a command issued via the server side – preventing costly redevelopment.

Orchestration also reduces the development efforts required to integrate remote authentication via PIN, fingerprint or facial recognition. This allows for policy changes to a specific user’s authentication journey from the server side, without costly changes to the mobile app. Such use cases embed authentication scenarios inside the mobile app that are triggered on the server side via an authentication server such as VASCO’s IDENTIKEY Authentication Server on the back-end, along with the Server Orchestration SDK.

Advanced Capabilities: Server-side Risk Analysis

The DIGIPASS for Apps Orchestration SDK also streamlines the integration of server-side risk analysis into a financial institution’s apps for more accurate fraud detection and a higher quality user experience.

False negatives mean fraud occurs undetected and false positives result in a poor user experience. Client-side and server-side DIGIPASS for Apps Orchestration SDKs, along with a risk analysis engine such as IDENTIKEY Risk Manager, significantly reduce both false positives and false negatives. The risk analytics engine and orchestration technology enable the consumption, analysis and scoring of vast risk data from disparate sources including from a user’s mobile device (e.g., device risk, geolocation, etc.) to simplify enforcement of a bank’s authentication policies.

Increase Productivity and Accelerate Time to Market

Financial institutions, developers, and end-user customers all have something to gain from a streamlined mobile development process. The Orchestration SDK underpins this by:

  • Improving customer experience: Offer users easy transitions between authentication scenarios and make it easy to adopt new authentication methods as they become available
  • Removing complexity for developers: Simplify mobile authentication integration by consolidating API calls and SDKs
  • Supporting advanced server-side risk management use cases: Gather identity, device, and app context from an end-user’s device to make risk-based authentication decisions

Put simply, the Orchestration SDK and related components help developers code faster – so businesses can ship new features faster and accelerate growth by bringing new services to market sooner.

Learn more about optimizing the user authentication experience while preventing fraud in this behavioral biometrics whitepaper.

Behavioral Biometrics: Improve Security and the Customer Experience

This is a Security Bloggers Network syndicated blog post authored by Samuel Bakken. Read the original post at: VASCO Data Security – Blog