Wells Fargo Bank, N.a.

Ranganathan Kanchi

Imran Haider

Nathan C Freeling

Kumaran Perumal

Andrew-An Truong Luu

Nancy Y Mao

Shailesh Hedaoo

Ashish G Khapre

Upul D Hanwella

Chintan Mehta

Venkatesan Chinnaraju

Kapil Soni

Kunal Jha

Ramakrishna Swarup Pogalur

Michelle Moore

Ashish Bhoopen Kurani

James Christopher Noe

Jonathan Austin Hartsell

Daniel Sanford

Ramesh N Tejavath

Dinesh Arora

Udaya Isampalli

Jesse Owens

Greg J Hansen

Kiran Rapolu

This disclosure is directed to integrating unaffiliated applications, or the processes and/or subsystems (e.g., application interfaces) of unaffiliated applications, with client applications to enable the client applications to provide new capabilities not otherwise available through the client application. The disclosed approach allows users to access new functionality within the operating environment of the client application, without accessing unaffiliated applications and undergoing separate authentication and data exchange with each unaffiliated application. Functionality of an unaffiliated application can be integrated by, for example, incorporating such processes and subsystems as interactive user interfaces, widgets, applets, plugins, etc., of unaffiliated applications.

Networked portal for multidirectional integration of diverse unaffiliated processes and subsystems with client applications

Disclosed are methods, systems, and devices for facilitating secure and private communications, via a website or application of a third-party computing system (TPCS), between a user device and a service provider computing system (SPCS). The communications may be conducted via a frame in a website served by the TPCS. The TPCS may serve a website that incorporates a customizable SDK component provided by the SPCS. The communications allow the user to, for example, open a new account. The SDK component may be initialized via a script from the SPCS, and authenticated via a session token obtained from the SPCS via the TPCS. The SDK component may provide user information, input into the frame, to the SPCS via API calls to the SPCS. The user does not navigate away from the website while securely engaging the SPCS. The third-party/partner need not develop its own user interface, security protocols, etc.

Secure communications via third-party systems through frames

Systems and methods for providing access rights may include a first computing system that receives a request to link an enterprise account of the first computing system to a second computing system. The first computing system may authenticate a user, receive a selection of one or more access rights, and one or more accounts of the enterprise account, via an application interface of the second computing system, and generate an access token for transmission to a computing device of the user, where the access token identifies the one or more access rights and the one or more accounts. The first computing system may transmit the access token to the computing device, to provide the computing device access to the one or more accounts according to the one or more access rights, of the first computing system, via the second computing system.

Systems and methods for providing access rights of an enterprise account to an enterprise resource

Techniques are described that include detecting customer personal information within any appropriate set of data, such as customer communications produced by customer-facing services offered by an organization. Once detected, the customer personal information may be tokenized within the customer communications, making the data appropriate for external systems, such as cloud-hosted applications. The disclosed techniques include a masking service that may be plugged into an on-premises pipeline of any customer-facing service that makes requests to an off-premises, cloud-hosted application. The masking service may apply rule-based detection and/or machine learning-based detection to detect both structured and unstructured customer personal information included in customer communications. The masking service may further tokenize or otherwise obfuscate or replace the detected customer personal information. The tokenized customer communications may then be included in the requests to the cloud-hosted application or otherwise transmitted to external systems without exposing the customer personal information.

Protecting customer personal information in application pipeline

A method for responding to a content retrieval request at a server may include receiving the content retrieval request from a computing device; detecting, at a device aware controller, at least one device capability of the computing device; setting, at the device aware controller, a rule boundary for the content retrieval request based on the at least one device capability; forwarding the content retrieval request with the rule boundary to a device agnostic controller, wherein the content retrieval request does not include capability information associated with the computing device; receiving from the device agnostic controller at the device aware controller, data corresponding to the content retrieval request with the rule boundary applied; and providing the data with the rule boundary applied to the computing device for presentation on the computing device.

Separated device detection architecture

Growing community of inventors

Danville, CA, United States of America

Ranganathan Kanchi