Square, Inc.

Invensense, Inc.

Block, Inc.

Rodion Steshenko

Kartik Lamba

Jianliang Zhao

Timothy Kordas

Jesse Lee Dorogusker

Jeremy Wade

Dan Post

Nicholas Hebner

Max Joseph Guise

David Terra

John L Kelley

Todor Ristov

Davis Gallinghouse

A method and system for multi-account payment processing are described. An example method includes: receiving, at a computing system and for a payment transaction involving one or more items, information associated with a purchaser, wherein the information is associated with a plurality of accounts, and wherein each of the plurality of accounts is associated with distinct account information; determining, at the computing system and based on one or more account selection criteria, one or more accounts of the plurality of accounts to use for processing the payment transaction, wherein the one or more account selection criteria include at least one of merchant type or available funds in the plurality of accounts; and processing, at the computing system, a respective aspect of the payment transaction corresponding to a respective item of the one or more items using a respective account of the determined one or more accounts.

Associating an account with a card

A method and apparatus for associating an account with a proxy card are disclosed. The proxy card can be associated with account data from multiple other cards, such as account data from a driver's license and from various payment cards, such as a credit card, a debit card, and a pre-paid gift card. In some embodiments, a card-holder can associate an additional card with the proxy card using a mobile device. The mobile device associates the additional card with the proxy card by causing updating of stored association information, that represents an association between the card and the account data of the multiple cards, with the account information.

A payment service system may include a server that manages firmware updates for payment devices such as payment readers. A payment reader may access a firmware manifest including a listing of current firmware assets stored at the payment reader, and send the firmware manifest to the server. The server may compare the firmware manifest to available firmware bundles, which are ordered combinations of firmware assets that have been released for usage by payment readers. Some of the bundles may be blocking bundles, while some are non-blocking. If a payment reader is to be updated with a blocking bundle, it cannot process payments during the update. If the update is not a blocking bundle, the payment reader may continue to process payments.

Blocking and non-blocking firmware update

Techniques for implementing policy-based anti-rollback techniques on a computing device are described herein. As an example, a remote service may provide the computing device with a boot policy which indicates, for each boot stage of a software bootloader process, what software versions are permitted to execute. Prior to providing the computing device with the boot policy, the remote service may sign the boot policy with a private key, and include of an identifier corresponding to the computing device. At each boot stage of the bootloader process, components of the computing device may verify, using a public key, that the boot policy was signed with the private key, and that the boot policy corresponds to the computing device. After verification, the components may analyze the boot policy to determine whether each boot stage is permitted to execute a software version and boot to the next boot stage.

Update policy-based anti-rollback techniques

A payment reader includes a power management system to control the power mode of the payment reader. The power management system can transition the payment reader between a sleep mode, a low power mode and a full power mode. The power management system can use a low power mode reference counter to determine when to transition from the full power mode to the low power mode and a sleep mode reference counter to determine when to transition from the low power mode to the sleep mode. When the low power mode reference counter reaches zero, the power management system deactivates a payment processing subsystem to transition to the low power mode. Similarly, when the sleep mode reference counter reaches zero, the power management system deactivates a payment reader system to transition to the sleep mode.

Multi-chip reference counting power management

A system and method for maintaining authentication of a user of a wearable device. The wearable device can include an electrical circuit, an accelerometer, a capacitive sensor, or other wearable detection module that can determine that the wearable device has been in continuous contact with, or continuous use by, the wearer. A first payment transaction can be initiated between the wearable device and a first payment terminal. A user credential is then received at either the wearable device or a mobile device coupled to the wearable device. The user credential is verified and the first payment transaction is authorized. A second payment transaction is then initiated between the wearable device and a second payment terminal. If the wearable device is determined to have been in continuous use by the user, then the second payment transaction can be completed without requiring re-authentication of the user.

Persistent authentication of a wearable device

It may be determined that a payment reader requires a firmware update, which may be transmitted to the payment reader as compressed firmware update blocks. The payment reader may receive a first portion of set of the compressed firmware update blocks. The payment reader may decompress the first portion and determine a partial firmware offset associated with the first portion. If the firmware update is incomplete, the payment reader may transmit that partial firmware offset to a second device. Based on this partial of firmware offset and an offset table that associates compressed firmware offsets with decompressed firmware offsets, the payment reader receive a second portion of compressed firmware update blocks to send to the payment reader. The payment reader may determine that entire update has been received and update its firmware.

Compressed firmware update

Aspects of the subject disclosure provide a reader device for managing operation of an automatic gain control (AGC) sub-circuit on a host device computing device. In some implementations, a reader device of the subject technology can include a controller, a noise generator, noise coupling circuitry, and a 3.5 mm audio plug including an audio bus that is configured for insertion into a headphone port of a host device, such as a smart phone or tablet computer. Upon connection of the reader device to the host computing device, the reader device can provide an intentional noise signal to the host device via a signal path where the intentional noise signal is configured to establish a substantially stable gain amount at the AGC sub-circuit.

Growing community of inventors

Union City, CA, United States of America

Rodion Steshenko