Abstract: 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.

Abstract: A first device and a second device may establish wireless pairing, and based on that wireless pairing, establish wireless bonding. During the wireless bonding, the two devices may have multiple connections during which information is exchanged. One of the devices may also attempt to pair with a third device. The wireless bond between the first device and the second device may be broken, and a wireless bond may then be formed with the third device.

Abstract: A payment reader and a merchant device may communicate over a wireless connection. Reliable and unreliable packets may be transmitted over a single messaging path. Each of a plurality of unreliable packet may include a data payload and a packet identifier. The unreliable packets and a reliable packet may be transmitted over the single messaging path during a first connection event. A response to the reliable packet may be received during the second event and may include a received packet listing. If the received packet listing indicates that any of the unreliable packets were not received, any unreliable packet that was not received may be retransmitted.

Abstract: 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.

Abstract: A payment reader and a merchant device may communicate over a wireless connection. Reliable and unreliable packets may be transmitted over a single messaging path. Each of a plurality of unreliable packet may include a data payload and a packet identifier. The unreliable packets and a reliable packet may be transmitted over the single messaging path during a first connection event. A response to the reliable packet may be received during the second event and may include a received packet listing. If the received packet listing indicates that any of the unreliable packets were not received, any unreliable packet that was not received may be retransmitted.

Abstract: A first device and a second device may establish wireless pairing, and based on that wireless pairing, establish wireless bonding. During the wireless bonding, the two devices may have multiple connections during which information is exchanged. One of the devices may also attempt to pair with a third device. The wireless bond between the first device and the second device may be broken, and a wireless bond may then be formed with the third device.

Abstract: A payment reader and a merchant device may communicate over a wireless connection. The payment reader may establish a wireless bond with a first merchant device and exchange payment information. After the payment information is exchanged, the payment reader and merchant device may disconnect while remaining bonded. The payment reader may send a request message and bond to a second merchant device, while breaking the bond with the first merchant device if a bond with the second merchant device is established. The payment reader may then exchange payment information with the second merchant device.