Apollo Education Group, Inc.

Square, Inc.

Block, Inc.

Ted Wong

Manish Upendran

Jongwoo Lee

David Le

Isabel George

Shannon-Lee Eng

Sravanthi Deshmukh

Aditya Nagpal

Bhavishyavani Ravi

Locke David Berkebile

Bryce Griner

Jo-Jo Lin

Gradated access to services based on identity verification (IDV) is described herein. In an example, a computing device can receive identifying information of a user and can select, from a plurality of IDV paths and based at least in part on the identifying information of the user, an IDV path for verifying an identity of the user using one or more factors. Based at least in part on the one or more factors, the computing device can determine a score indicative of whether the identifying information provided by the user accurately identifies the user. The score can be used for the benefit of one or more service providers to verify an identity of the user and/or determine gradated access to one or more services of the one or more service providers.

Gradated service access based on identity verification (IDV)

Identity verification (IDV) using a payment processing platform is described herein. In an example, a computing device can receive identifying information of a user. The computing device can request payment information of a payment instrument of the user and can receive the payment information of the payment instrument of the user. The computing device can prompt the user to present the payment instrument at a point-of-sale (POS) of a trusted merchant and can verify the identity of the user based at least in part on verification information received from a merchant device operable by the trusted merchant at the POS.

Identity verification (IDV) using a payment processing platform

Techniques for detecting and addressing performance issues related to a mobile application are provided. Examples of performance issues include a backend service (to which the mobile application is configured to transmit requests) becoming unavailable or overloaded, a third-party service that the mobile application relies on for data pertaining to the backend service becoming unavailable, and security vulnerabilities or code irregularities in the code of the mobile application. A fallback service that is separate from the backend service detects the performance issues and sends fallback data to the mobile application. The fallback data may cause the mobile application to operate in an offline mode, where the mobile application requests locally stored data instead of transmitting data requests to the backend service. The fallback data may reference page views that the mobile application downloads and displays instead of other page views that are based on data from the backend service.

Service response detection and management on a mobile application

Techniques are described for resolving document change conflicts based on state information. A document management system records, at a client device, changes that a user made to a root client-side instance of a document bundle to create a modified client-side instance of the document bundle, wherein the changes were made while the client device was not connected to a remote storage service. After the changes are recorded, the client device is connected to the remote storage service. In response to determining that a conflict has occurred, the document management system selects a particular resolution action, based, at least in part, on state information associated with at least one of: a user that made the changes, an instance of the document bundle, or the client device on which the changes were made. The document management system then resolves the conflict by performing the particular resolution action.

Resolving synchronization conflicts based on state information

Techniques are provided for navigating through a hierarchy of views while generating a bread-crumb display that continues to provide an indication of each ancestor view even when the labels for all ancestor views do not fit within the bread-crumb display. When the bread-crumb display does not have sufficient room remaining to accommodate the label of a view to which the user has navigated, the current content of the bread-crumb display contracts, like an accordion, to make room for the new label. The contracted version of the bread-crumb display continues to have an indication of all traversed levels, though the labels for some or all of the ancestor views may be partially or completely obscured. The contracted version of the bread-crumb display may be expanded, and used to navigate back up the hierarchy.

Accordion style bread crumbing for mobile applications

Growing community of inventors

San Francisco, CA, United States of America

Ted Wong