Abstract: A method for electronic receipt transfer via ultra-wideband electronic (UWB) radio technology may include: causing, by a payment terminal computer program, an UWB radio to transmit a range request signal from a first antenna; receiving, by the payment terminal computer program and one or more customer electronic devices, a pair of replies to the range request signal, each comprising a first reply signal received at the first antenna and a second reply signal received at a second antenna; determining, by the payment terminal computer program, a distance between the UWB radio and each customer electronic device based on a time of flight; selecting, by the payment terminal computer program, the customer electronic devices having the distance that is closest to the UWB radio; and communicating, by the payment terminal computer program, an electronic receipt for a transaction to the selected customer electronic device.

Abstract: A method for electronic receipt transfer via ultra-wideband electronic (UWB) radio technology may include: causing, by a payment terminal computer program, an UWB radio to transmit a range request signal from a first antenna; receiving, by the payment terminal computer program and one or more customer electronic devices, a pair of replies to the range request signal, each comprising a first reply signal received at the first antenna and a second reply signal received at a second antenna; determining, by the payment terminal computer program, a distance between the UWB radio and each customer electronic device based on a time of flight; selecting, by the payment terminal computer program, the customer electronic devices having the distance that is closest to the UWB radio; and communicating, by the payment terminal computer program, an electronic receipt for a transaction to the selected customer electronic device.

Abstract: A payment terminal computer program may track entry to, presence in, and exit from an area using ultrawideband (UWB) radio technology by: receiving, from an UWB radio, first information to determine a first distance between a UWB radio-enabled mobile electronic device and the UWB radio or a first position of the UWB radio-enabled mobile electronic device; determining that the UWB radio-enabled mobile electronic device is at an entrance to the area based on the first distance or position; receiving, from the UWB radio, second information to determine a second distance between the UWB radio-enabled mobile electronic device and the UWB radio or a second position of the UWB radio-enabled mobile electronic device; determining that the UWB radio-enabled mobile electronic device is at an exit from the area based on the second distance or position; and determining a fee based on the first communication and the second communication.

Abstract: Systems and methods for alternative payment mechanism payments using ultra-wideband radio technology are disclosed. A method may include a payment terminal computer program executed by a payment terminal selecting a customer electronic device that is conducting the payment transaction with the payment terminal; communicating, via a payment terminal UWB radio to the selected customer electronic device, payment transaction details for the payment transaction comprising a merchant identifier and a transaction amount; receiving, from the selected customer electronic device via the payment terminal UWB radio, an APM payment message for an APM payment provider; communicating the APM payment message to the APM payment provider, wherein the APM payment provider is configured to decision the transaction based on the APM payment message; and receiving, from the APM payment provider, a payment confirmation for the payment transaction.

Abstract: A method for electronic receipt transfer via ultra-wideband electronic (UWB) radio technology may include: causing, by a payment terminal computer program, an UWB radio to transmit a range request signal from a first antenna; receiving, by the payment terminal computer program and one or more customer electronic devices, a pair of replies to the range request signal, each comprising a first reply signal received at the first antenna and a second reply signal received at a second antenna; determining, by the payment terminal computer program, a distance between the UWB radio and each customer electronic device based on a time of flight; selecting, by the payment terminal computer program, the customer electronic devices having the distance that is closest to the UWB radio; and communicating, by the payment terminal computer program, an electronic receipt for a transaction to the selected customer electronic device.

Abstract: Systems and methods for alternative payment mechanism payments using ultra-wideband radio technology are disclosed. A method may include a payment terminal computer program executed by a payment terminal selecting a customer electronic device that is conducting the payment transaction with the payment terminal; communicating, via a payment terminal UWB radio to the selected customer electronic device, payment transaction details for the payment transaction comprising a merchant identifier and a transaction amount; receiving, from the selected customer electronic device via the payment terminal UWB radio, an APM payment message for an APM payment provider; communicating the APM payment message to the APM payment provider, wherein the APM payment provider is configured to decision the transaction based on the APM payment message; and receiving, from the APM payment provider, a payment confirmation for the payment transaction.

Abstract: The present disclosure relates to systems and methods of implementing rate limiting in a representational state transfer (REST) application programming interface (API) system. A method of operating an instance of a REST API server, includes: receiving a REST API request that matches a rate limit rule associated with the instance of the REST API server; preparing a REST API response that includes rate limiting response headers. The method includes determining whether a rate limit violation exists that corresponds to the rate limit rule and, when it does, adding an error message to the REST API response. Otherwise, the REST API request is fulfilled and corresponding data is added to the REST API response. The method includes sending the REST API response including the rate limiting response headers and either the error message or the corresponding data.

Abstract: A computing system may be configured to store a master session context of a HyperText Transfer Protocol (HTTP) session, and a queue of HTTP transactions. A middleware module of the computing system may be executable by the processor to: (i) select a first HTTP transaction from the queue, (ii) execute an exclusive phase of the first HTTP transaction, including copying the master session context into a first local session context, (iii) cause a web server to execute a non-exclusive phase of the first HTTP transaction using a first thread and the first local session context, (iv) select a second HTTP transaction from the queue, and (v) execute an exclusive phase of the second HTTP transaction, including copying the master session context into a second local session context. Execution of the exclusive phase of the second HTTP transaction and the execution of the non-exclusive phase of the first HTTP transaction occur concurrently.

Abstract: The present disclosure relates to systems and methods of implementing rate limiting in a representational state transfer (REST) application programming interface (API) system. A method of operating an instance of a REST API server, includes: receiving a REST API request that matches a rate limit rule associated with the instance of the REST API server; preparing a REST API response that includes rate limiting response headers. The method includes determining whether a rate limit violation exists that corresponds to the rate limit rule and, when it does, adding an error message to the REST API response. Otherwise, the REST API request is fulfilled and corresponding data is added to the REST API response. The method includes sending the REST API response including the rate limiting response headers and either the error message or the corresponding data.

Abstract: The present disclosure relates to systems and methods of implementing rate limiting in a representational state transfer (REST) application programming interface (API) system. A method of operating an instance of a REST API server, includes: receiving a REST API request that matches a rate limit rule associated with the instance of the REST API server; preparing a REST API response that includes rate limiting response headers. The method includes determining whether a rate limit violation exists that corresponds to the rate limit rule and, when it does, adding an error message to the REST API response. Otherwise, the REST API request is fulfilled and corresponding data is added to the REST API response. The method includes sending the REST API response including the rate limiting response headers and either the error message or the corresponding data.

Abstract: A computing system may be configured to store a master session context of a HyperText Transfer Protocol (HTTP) session, and a queue of HTTP transactions. A middleware module of the computing system may be executable by the processor to: (i) select a first HTTP transaction from the queue, (ii) execute an exclusive phase of the first HTTP transaction, including copying the master session context into a first local session context, (iii) cause a web server to execute a non-exclusive phase of the first HTTP transaction using a first thread and the first local session context, (iv) select a second HTTP transaction from the queue, and (v) execute an exclusive phase of the second HTTP transaction, including copying the master session context into a second local session context. Execution of the exclusive phase of the second HTTP transaction and the execution of the non-exclusive phase of the first HTTP transaction occur concurrently.

Abstract: The present disclosure relates to systems and methods of implementing rate limiting in a representational state transfer (REST) application programming interface (API) system. A method of operating an instance of a REST API server, includes: receiving a REST API request that matches a rate limit rule associated with the instance of the REST API server; preparing a REST API response that includes rate limiting response headers. The method includes determining whether a rate limit violation exists that corresponds to the rate limit rule and, when it does, adding an error message to the REST API response. Otherwise, the REST API request is fulfilled and corresponding data is added to the REST API response. The method includes sending the REST API response including the rate limiting response headers and either the error message or the corresponding data.