Block, Inc.

Square, Inc.

Gokhan Aydeniz

Murat Cat

Conrad Rushing

Murtaza Munaim

Afshin Rezayee

Jesse Wilson

Malcolm Smith

David Terra

Shawn Zurbrigg

Yasser Zabuair

Lev Kusman

Anthony Newpower

Systems, devices, and methods for embedded card reader security include configuring a personal account number (PAN) application installed on a device to utilize an embedded card reader (ECR) and receiving, at the PAN application and based at least in part on an interaction between the ECR and the device, a PAN for a transaction. The PAN may be sent to a payment processing service and a personal identification number (PIN) application may render a PIN user interface. The PIN may be received at the PIN application and sent to the payment processing service. The transaction may be completed based at least in part on an indication from the payment processing service that the PAN and the PIN have been accepted.

Embedded card reader security

A device may run an application having information with multiple accounts associated with processing of transactions. The application may provide account information that is used to process the transactions. At the same time, a background application may operate on the device. The background application may be compatible with a second device, and when within range of the second device, may communicate background messages relevant to the transaction. The transaction may then be processed based on the account information and the background messages.

Multi-source transaction processing

A payment reader can have one or more kernels capable of performing certain payment processing functions but not capable of performing certain, more processing-intensive payment processing functions. The payment reader may be designed to selectively assign processing tasks to application layer kernels located on a mobile device and/or a cloud-based device external to the payment reader, the mobile device having more or different processing resources than the payment reader. The selective assignment may be made dynamically based on the measurement of a condition of the reader or an occurrence of an event, such as a determination that the payment reader cannot process a transaction, that the payment reader does not have sufficient battery strength to process the transaction, or that there has been a tampering attempt at the payment reader. The payment reader also has a physical layer module, which module maintains its processing on the payment reader. By these means, the processing related to a payment transaction is conducted on a hybrid system, using resources both local to and remote from the payment reader.

Point of sale (POS) systems and methods with kernel selection

Techniques described herein are directed to embedded card reader security. In an example, personal account number data read from a payment instrument may be temporally and/or spatially separated from personal identification number data utilized to complete a payment for products. Temporal separation may include removing the personal account number data from a merchant device prior to request personal identification number data. Spatial separation may include utilization of trusted execution environments, separated embedded card reader applications, intermediary applications, and/or trust routines, for example to enable different components of a merchant device, and/or components of other devices and systems to handle personal account number data and personal identification number data.

A payment reader can have one or more kernels capable of performing certain payment processing functions but not capable of performing certain, more processing-intensive payment processing functions. The payment reader may be designed to selectively assign processing tasks to application layer kernels located on a mobile device and/or a cloud-based device external to the payment reader, the mobile device having more or different processing resources than the payment reader. The selective assignment may be made dynamically based on the measurement of a condition of the reader or an occurrence of an event, such as a determination that the payment reader cannot process a transaction, that the payment reader does not have sufficient battery strength to process the transaction, or that there has been a tempering attempt at the payment reader. The payment reader also has a physical layer module, which module maintains its processing on the payment reader. By these means, the processing related to a payment transaction is conducted on a hybrid system, using resources both local to and remote from the payment reader.

Point of sale (POS) systems and methods with dynamic kernel selection

Payment readers can variously have kernels of different generations, capable of performing different (or different suites of) payment processing functions. A payment reader may be designed to obtain raw payment data from a payment device, process that data if appropriate, and transmit the data to a mobile device external to the payment reader, the mobile device having similar, more, or different processing resources than the payment reader. A mobile device is capable of determining the type and source of payment data received, for example on whether the data is processed or raw (processed data). The mobile device may then selectively determine whether and how to process the payment data and to transmit it to a payment server for approval of a payment transaction.

Growing community of inventors

Mississauga, Canada

Gokhan Aydeniz