Systems and methods for bridging transactions between eft payment networks and payment card networks
US-2017364878-A1 · Dec 21, 2017 · US
US11775957B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11775957-B2 |
| Application number | US-202117332703-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 27, 2021 |
| Priority date | Dec 21, 2018 |
| Publication date | Oct 3, 2023 |
| Grant date | Oct 3, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A point of sale (POS) system comprising: a payment reader having a first application-layer payment kernel for processing payment transactions, the first application-layer payment kernel for performing at least one payment processing function for processing and sending payment information for payment transactions to at least one payment server for approval; and a networked device external to the payment reader, the networked device having a second application-layer payment kernel for processing payment transactions, the second application-layer payment kernel configured to perform the at least one payment processing function for processing and sending payment information for payment transactions to the at least one payment server for approval, wherein the payment reader is configured to receive first payment information for a first payment transaction from a payment device and to obtain a first payment kernel selection of whether to transmit at least a portion of the first payment information to the first application-layer payment kernel or the second application-layer payment kernel for processing and sending the portion of the first payment information to the at least one payment server for approval, and wherein the payment reader is configured to transmit the portion of the first payment information to the first application-layer payment kernel of the payment reader or to the second application-layer payment kernel of the networked device in accordance with the payment kernel selection obtained by the payment reader, and wherein the payment kernel selection is based on a detected condition of the payment reader. 2. The POS system of claim 1 , wherein the payment reader is configured to receive second payment information for a second payment transaction and to obtain a second payment kernel selection of whether to transmit at least a portion of the second payment information to the first application-layer payment kernel or the second application-layer payment kernel for processing and sending the portion of the second payment information to the at least one payment server for approval, and wherein the payment reader is configured to transmit the portion of the second payment information to the first application-layer payment kernel of the payment reader or to the second application-layer payment kernel of the networked device in accordance with the second payment kernel selection obtained by the payment reader, and wherein the second payment kernel selection is based on a second detected condition of the payment reader. 3. The POS system of claim 2 , wherein the payment reader is configured to transmit the portion of the first payment information to the first application-layer payment kernel for processing in accordance with the first payment kernel selection, and wherein the payment reader is configured to transmit the portion of the second payment information to the second application-layer payment kernel for processing in accordance with the second payment kernel selection. 4. The POS system of claim 3 , wherein the payment reader is configured to wirelessly transmit the portion of the second payment information to the networked device. 5. The POS system of claim 1 , wherein the networked device is a mobile phone, and wherein the payment reader is communicatively coupled to the mobile phone. 6. The POS system of claim 1 , wherein the payment reader has a battery, and wherein the first payment kernel selection is based on a measurement of a power level for the battery. 7. The POS system of claim 1 , wherein the wherein the first payment kernel selection is based on a detection of a tamper event associated with the payment reader. 8. A payment reader comprising: a payment module for receiving first payment information for a first payment transaction from a payment device; at least one processor having a first application-layer payment kernel and a kernel director, the first application-layer payment kernel for performing at least one payment processing function for processing and sending payment information for payment transactions to at least one payment server for approval; a communications interface configured to transmit information from the payment reader to a second application-layer payment kernel of a networked device, the second application-layer payment kernel for performing the at least one payment processing function for processing and sending payment information for payment transactions to the at least one payment server for approval; and the kernel director configured to, in accordance with the receipt of the first payment information from the payment device, (a) obtain a payment kernel selection of whether to transmit at least a portion of the first payment information to the first application-layer payment kernel of the payment reader or to the second application-layer payment kernel of the networked device for processing and sending the portion of the first payment information to the at least one payment server for approval, and (b) control the payment reader to transmit the portion of the first payment information to the first application-layer payment kernel of the payment reader or to the second application-layer payment kernel of the networked device in accordance with the payment kernel selection obtained by the kernel director, wherein the payment kernel selection is based on a detected condition of the payment reader. 9. The POS system of claim 8 , wherein the networked device is a mobile phone, and wherein the payment reader is communicatively coupled to the mobile phone. 10. The payment reader of claim 8 , wherein the payment reader has a battery, and wherein the payment kernel selection is based on a measurement of a power level for the battery. 11. The payment reader of claim 8 , wherein the wherein the payment kernel selection is based on a detection of a tamper event associated with the payment reader. 12. The payment reader of claim 8 , wherein the second payment kernel is configured to provide payment functions for the first payment information not provided by the first payment kernel. 13. The payment reader of claim 8 , wherein the detected condition indicates at least one of (1) whether hardware of the payment reader is compatible with the first payment transaction, (2) whether an occurrence of a security threat to the payment reader is detected, or (3) whether a power level of a power source in the payment reader is below a threshold. 14. A method for use in a point of sale system, comprising: receiving, by a payment reader, first payment information from a payment device for a payment transaction; detecting a condition of the payment reader; performing, by a first application-layer payment kernel at least one payment processing function for processing and sending payment information for payment transactions to at least one payment server for approval; obtaining, by the payment reader based on the detected condition, a payment kernel selection of whether to transmit at least a portion of the first payment information to a first application-layer payment kernel of the payment reader or a second application-layer payment kernel of a device external to the payment reader, the second application-layer payment kernel for performing the at least one payment processing function for processing and sending payment information for payment transactions to the at least one payment server for approval; and transmitting, by the payment reader, the portion of the first payment information to the first application-layer payment kernel of the payment reader or to the second application-layer payment ke
RFID or NFC payments by means of M-devices · CPC title
Point-of-sale [POS] network systems · CPC title
Device specific authentication in transaction processing · CPC title
comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit · CPC title
Contactless payments by cards · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.