Abstract: A method for encapsulating transaction instrument information in a transaction includes storing, in association with a first transaction and by a processor of the primary transaction processor server, payment data associated with a payment instrument used to settle a cost of a first transaction. The primary transaction processor server transmits the transaction data to a payment network processor. The primary transaction processor server receives an authorization package from the payment network processor that includes a cryptograph and a first network token. The processor of the primary transaction processor server generates a secondary token, and stores a correlation record to a computer-readable memory. The correlation record associates the secondary token to a second object stored by the primary transaction processor. The processor of the primary transaction processor server transmits a second transaction package including at least one of the network token and the secondary token to a merchant device.

Abstract: A method for encapsulating transaction instrument information in a transaction includes storing, in association with a first transaction and by a processor of the primary transaction processor server, transaction data associated with a transaction instrument for a first transaction. The primary transaction processor server transmits the transaction data to a payment network processor, and receives an authorization package in response that includes a cryptograph and a first network token. The primary transaction processor server generates a second token that includes a changeable alpha-numeric string associated with the transaction instrument used in the first transaction, and transmits the second token to a merchant device. The second token indicates that a transaction associated with the second token is either i) a customer-initiated transaction or ii) a merchant-initiated transaction. The secondary transaction processor may approve or reject a transaction using the second token without a cryptogram.

Abstract: A brain-machine interface (BMI) system includes one or more implantable or non-implantable sensors, each being configured to detect or measure electrophysiological activity of motor units and to transmit an electrophysiological activity signal; one or more wearable apparatuses configured to be worn by or attached to a user and configured to receive and process the one or more electrophysiological activity signals transmitted by the sensors, and configured to transmit the processed signals to one or more processing units, which are configured to produce control signals based on the received processed signals using one or more machine learning algorithms; and one or more effectors configured to receive the control signals and configured to transduce the control signals into a haptic, tactile, chemical, mechanical, auditory, visual, and/or electrical stimuli so as to provide feedback to a user and/or to control operation of an external effector.

Abstract: Techniques and arrangements for dynamically modifying a cardholder verification method (CVM) implemented at a point-of-sale (POS) device. In some instances, the techniques instruct a POS device to determine an attribute associated with a received payment instrument and determine, based on this information and via the issuing entity, whether to implement a default or static CVM or whether to apply a modified or dynamic CVM such that the POS device requests different verification information than if the POS device did not modify the CVM. The modified or dynamic CVM may be implemented if a customer's device, present at the location of the payment transaction, has installed thereon an application of the entity that has issued the payment instrument.

Abstract: A payment service is configured to support purchase transactions generated by merchant point-of-sale (POS) devices, wherein each purchase transaction may comprise multiple transaction requests such as authorization requests and capture requests. Each transaction request may be sent to a different one of multiple data centers of the payment service. Upon successfully receiving an acknowledgement from one of the data centers for a transaction request, the POS device designates that data center as the primary data center. Subsequently, all transaction requests for that transaction identify the primary data center, even when the transaction requests are sent to other data centers. At the payment service, the data centers synchronize requests such that the primary data center is informed of all authorizations and is made responsible for performing the capture of the transaction. This allows the primary data center to detect duplicate authorizations and to prevent duplicate captures.

Abstract: In some examples, methods and systems may process one or more payment transactions between a merchant and a buyer by detecting buyer's communication device as an instrument to approve or reject a payment transaction in offline mode. The method includes detecting at least one transaction activity associated with a payment system, establishing a communication channel between the POS terminal an RF communication device in proximity to the POS terminal to obtain at least one device characteristic of the communication device, related to the operational or physical features of the communication device; generating a digital fingerprint based in part on the obtained device characteristic and the information related to received payment object; determining whether the digital fingerprint substantially compares to an existing fingerprint in a database and if the existing fingerprint is substantially similar to the digital fingerprint, rejecting the payment transaction through presence of the communication device.

Abstract: Techniques and arrangements for dynamically modifying a cardholder verification method (CVM) implemented at a point-of-sale (POS) device. In some instances, the techniques instruct a POS device to determine an attribute associated with a received payment instrument and determine, based on this information and via the issuing entity, whether to implement a default or static CVM or whether to apply a modified or dynamic CVM such that the POS device requests different verification information than if the POS device did not modify the CVM. The modified or dynamic CVM may be implemented if a customer's device, present at the location of the payment transaction, has installed thereon an application of the entity that has issued the payment instrument.

Abstract: A mobile point-of-sale terminal includes a payment card reader having a card interface configured to read data from a payment card and transmit the payment card data, along with other transaction information, via a non-internet communication channel to a payment processing system to process the point-of-sale transaction. The mobile point-of-sale terminal may be configured to run a register application configured to receive transaction information, including payment card information from the payment card reader, determine whether an internet connection is available, and, if an internet connection is not available, transmit the transaction information to the payment processing system using a non-internet communication channel.

Abstract: A payment service is configured to support purchase transactions generated by merchant point-of-sale (POS) devices, wherein each purchase transaction may comprise multiple transaction requests such as authorization requests and capture requests. Each transaction request may be sent to a different one of multiple data centers of the payment service. Upon successfully receiving an acknowledgement from one of the data centers for a transaction request, the POS device designates that data center as the primary data center. Subsequently, all transaction requests for that transaction identify the primary data center, even when the transaction requests are sent to other data centers. At the payment service, the data centers synchronize requests such that the primary data center is informed of all authorizations and is made responsible for performing the capture of the transaction. This allows the primary data center to detect duplicate authorizations and to prevent duplicate captures.