Abstract: Representative embodiments set forth techniques for verifying an identity of a primary user of a primary account on a client device. A method may include receiving, for the primary account, a request for identity verification responsive to an action of a secondary account associated with the primary account and identifying a payment registration characteristic of a payment registration associated with the primary account. The method also includes retrieving identity information associated with the primary account based on the payment registration characteristic and, in response to a determination that the identity information corresponds to a verification indicator, verifying an identity of a user of the primary account. The method also includes, in response to verifying the identity of the user of the primary account, generating a payment verification token and associating the payment verification token with an authorization indication for the action of the secondary account.

Abstract: The present disclosure generally relates to account recovery. An example method includes, at a computer system in communication with a display generation component and one or more input devices: performing a recovery contact set up process including providing a notification to a contact; after performing the recovery contact set up process, receiving, via the one or more input devices, a request to initiate an account recovery process; in response to the request to initiate the account recovery process and without providing a request to the contact, displaying, via the display generation component, a recovery code interface for receiving a set of recovery credentials; while displaying of the recovery code interface, receiving the set of recovery credentials; in accordance with a determination that the recovery credentials are valid, performing a recovery function; and in accordance with a determination that the recovery credentials are not valid, forgoing performing the recovery function.

Abstract: Embodiments described herein provide for a satellite device that can be associated with a user account of a minor aged (e.g., child or adolescent) user that does not have a smartphone that can be used as a companion device to the satellite device. The satellite device can be configured to be used as a primary device, without reliance upon a paired smartphone. Certain information can be synchronized with the satellite device via the association with the family account. During initial configuration, a set of cryptographic keys can be generated to associate the account of the satellite device with the set of accounts in the family. The satellite device can then access calendars, media, or other data that is shared with user accounts within a family of user accounts.

Abstract: Embodiments described herein provide for a satellite device that can be associated with a user account of a minor aged (e.g., child or adolescent) user that does not have a smartphone that can be used as a companion device to the satellite device. The satellite device can be configured to be used as a primary device, without reliance upon a paired smartphone. Certain information can be synchronized with the satellite device via the association with the family account. During initial configuration, a set of cryptographic keys can be generated to associate the account of the satellite device with the set of accounts in the family. The satellite device can then access calendars, media, or other data that is shared with user accounts within a family of user accounts.

Abstract: Embodiments described herein provide for a satellite device that can be associated with a user account of a minor aged (e.g., child or adolescent) user that does not have a smartphone that can be used as a companion device to the satellite device. The satellite device can be configured to be used as a primary device, without reliance upon a paired smartphone. Certain information can be synchronized with the satellite device via the association with the family account. During initial configuration, a set of cryptographic keys can be generated to associate the account of the satellite device with the set of accounts in the family. The satellite device can then access calendars, media, or other data that is shared with user accounts within a family of user accounts.

Abstract: Implementations of the subject technology provide for performing, by a device, a request for obtaining information related to a phone authentication certificate (PAC) that was generated for the device, the PAC authenticating that a particular phone number is associated with the device, the request including packets of data. The subject technology receives the information related to the PAC, the information including an indication that the PAC was generated for the device. The subject technology sends, from the device, a request for validating the PAC to a remote server based at least in part on the information related to the PAC. Further, the subject technology receives a confirmation of validating the PAC from the remote server based at least in part on the information related to the PAC.

Abstract: Representative embodiments set forth techniques for verifying an identity of a primary user of a primary account on a client device. A method may include receiving, for the primary account, a request for identity verification responsive to an action of a secondary account associated with the primary account and identifying a payment registration characteristic of a payment registration associated with the primary account. The method also includes retrieving identity information associated with the primary account based on the payment registration characteristic and, in response to a determination that the identity information corresponds to a verification indicator, verifying an identity of a user of the primary account. The method also includes, in response to verifying the identity of the user of the primary account, generating a payment verification token and associating the payment verification token with an authorization indication for the action of the secondary account.

Abstract: Embodiments described herein provide for a satellite device that can be associated with a user account of a minor aged (e.g., child or adolescent) user that does not have a smartphone that can be used as a companion device to the satellite device. The satellite device can be configured to be used as a primary device, without reliance upon a paired smartphone. Certain information can be synchronized with the satellite device via the association with the family account. During initial configuration, a set of cryptographic keys can be generated to associate the account of the satellite device with the set of accounts in the family. The satellite device can then access calendars, media, or other data that is shared with user accounts within a family of user accounts.

Abstract: Implementations of the subject technology provide for performing, by a device, a request for obtaining information related to a phone authentication certificate (PAC) that was generated for the device, the PAC authenticating that a particular phone number is associated with the device, the request including packets of data. The subject technology receives the information related to the PAC, the information including an indication that the PAC was generated for the device. The subject technology sends, from the device, a request for validating the PAC to a remote server based at least in part on the information related to the PAC. Further, the subject technology receives a confirmation of validating the PAC from the remote server based at least in part on the information related to the PAC.

Abstract: In accordance with an embodiment, an architecture for directly interfacing Business Object Documents (BODs) may include a BOD mapper which employs the BOD for input and output. A model object definable by class is created corresponding to the data contained in the BOD. System logic for the local domain is provided with communication with the BOD mapper through a BOD mapper application programming interface. The logic operates on the model object and a mapping configuration is provided for relating elements of the BOD to the model object. An addressing element communicates with the BOD mapper to define the mapping configuration for the BODs operated on by the BOD Mapper for input/output and mapping for a map call and parsing for a list call is accomplished for the contents from the BOD to the model object as defined by the BOD mapping configuration.

Abstract: In accordance with an embodiment, an architecture for directly interfacing Business Object Documents (BODs) may include a BOD mapper which employs the BOD for input and output. A model object definable by class is created corresponding to the data contained in the BOD. System logic for the local domain is provided with communication with the BOD mapper through a BOD mapper application programming interface. The logic operates on the model object and a mapping configuration is provided for relating elements of the BOD to the model object. An addressing element communicates with the BOD mapper to define the mapping configuration for the BODs operated on by the BOD Mapper for input/output and mapping for a map call and parsing for a list call is accomplished for the contents from the BOD to the model object as defined by the BOD mapping configuration.