System and method for providing third party payments with non-integrated merchants
US-2019026711-A1 · Jan 24, 2019 · US
US2019251529A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2019251529-A1 |
| Application number | US-201916396486-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 26, 2019 |
| Priority date | Jul 29, 2016 |
| Publication date | Aug 15, 2019 |
| Grant date | — |
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.
Integrating payment processing functionality into a third-party application via software development kit (SDK) instructions is described. In an example, a payment card reader can include reader instructions executable on the payment card reader to configure the payment card reader to read payment card data from a payment card and transmit the payment card data to a mobile device for processing by SDK instructions on the mobile device. The SDK instructions can be executable on the mobile device to configure the mobile device to process the payment card data from the payment card reader. The SDK instructions, which can be provided by a payment processor, can be configured to be integrated into a third-party payment application on the mobile device, wherein the third-party payment application is provided by an entity distinct from the payment processor.
Opening claim text (preview).
1 - 23 . (canceled) 21 . A system comprising: a payment card reader including reader instructions executable on the payment card reader to configure the payment card reader to read payment card data from a payment card and transmit the payment card data to a mobile device for processing by software development kit (SDK) instructions on the mobile device; and the SDK instructions executable on the mobile device to configure the mobile device to process the payment card data from the payment card reader, wherein: the SDK instructions are configured to be integrated into a third-party payment application on the mobile device, the SDK instructions are provided by a payment processor, and the third-party payment application is provided by an entity distinct from the payment processor. 22 . The system as claim 21 recites, wherein the SDK instructions are further executable to configure the mobile device to (i) receive the payment card data from the payment card reader and (ii) process a card-present payment transaction via the payment processor. 23 . The system as claim 21 recites, wherein the SDK instructions are further executable to configure the mobile device to: determine transaction data associated with a transaction, the transaction data including at least an amount of the transaction; cause, based at least in part on determining the transaction data, the payment card reader to read the payment card data; and responsive to receiving the payment card data from the payment card reader, transmit the payment card data to the payment processor to process payment for the amount of the transaction. 24 . The system as claim 23 recites, wherein the SDK instructions are further executable to configure the mobile device to associate additional transaction data with the transaction, wherein the additional transaction data includes at least one of a geolocation associated with the transaction, an identity of an entity associated with the transaction, a payment method associated with the transaction, or a descriptor of an item associated with the transaction. 25 . The system as claim 21 recites, wherein the SDK instructions are further executable to configure the mobile device to instruct the payment card reader to read the payment card data. 26 . The system as claim 25 recites, wherein the SDK instructions are further executable to configure the mobile device to authenticate the third-party payment application with the payment processor at least partly prior to at least one of instructing the payment card reader to read the payment card data or processing the payment card data. 27 . The system as claim 21 recites, wherein the reader instructions are further executable to configure the payment card reader to transmit the payment card data to the mobile device via at least one of: a short-range wireless communication network; or a wired connection. 28 . The system as claim 21 recites, wherein the SDK instructions are further executable to configure the mobile device to (i) receive additional payment card data associated with an additional payment card without the additional payment card having interacted with the payment card reader, and (ii) process a card-less payment transaction via the payment processor. 29 . The system as claim 21 recites, wherein the SDK instructions are further executable to configure the mobile device to present a user interface for procuring a signature in association with a transaction, the user interface being configurable by a user of the mobile device. 30 . The system as claim 21 recites, wherein the SDK instructions are further executable to configure the mobile device to transmit, in association with the payment card data, information via a uniform resource locator to the payment processor. 31 . The system as claim 21 recites, wherein the SDK instructions are further executable to configure the mobile device to determine, at a first time, that the mobile device is associated with an offline state and, sending the payment card data to the payment processor at a second time after the first time. 32 . A point-of-sale (POS) application comprising: first instructions compiled into the POS application by an application developer and generated by the application developer, wherein the first instructions are executable by a mobile device to configure a function of the mobile device including the POS application; and second instructions including a mobile device portion compiled into the POS application by the application developer and generated by a software development kit (SDK) developer, wherein the mobile device portion of the second instructions are executable to configure the mobile device to communicate with a payment card reader including a payment reader portion of the second instructions further generated by the SDK developer. 33 . The POS application as claim 32 recites, wherein the mobile device portion of the second instructions are further executable to configure the mobile device to (i) receive payment card data from the payment card reader and (ii) process a card-present payment transaction via a payment processor associated with the SDK developer. 34 . The POS application as claim 32 recites, wherein the mobile device portion of the second instructions are further executable to configure the mobile device to: determine transaction data associated with a transaction, the transaction data including at least an amount of the transaction; cause, based at least in part on determining the transaction data, the payment card reader to read payment card data; and responsive to receiving the payment card data from the payment card reader, securely transmit the payment card data to a payment processor to process payment for the amount of the transaction. 35 . The POS application as claim 34 recites, wherein the mobile device portion of the second instructions are further executable to configure the mobile device to associate additional transaction data with the transaction, wherein the additional transaction data includes at least one of a geolocation associated with the transaction, an identity of an entity associated with the transaction, a payment method associated with the transaction, or a descriptor of an item associated with the transaction. 36 . The POS application as claim 32 recites, wherein the mobile device portion of the second instructions are further executable to configure the mobile device to instruct the payment card reader to read payment card data. 37 . The POS application as claim 36 recites, wherein the mobile device portion of the second instructions are further executable to configure the mobile device to authenticate the POS application with a payment processor at least partly prior to at least one of instructing the payment card reader to read payment card data or processing the payment card data. 38 . The POS application as claim 32 recites, wherein the mobile device portion of the second instructions are further executable to configure the mobile device to (i) receive payment card data associated with a payment card without the payment card having interacted with the payment card reader, and (ii) securely process a card-less payment transaction via a payment processor. 39 . The POS application as claim 32 recites, wherein the mobile device portion of the second instructions are further executable to configure the mobile device to present a user interface for procuring a signature in association with a transaction, the user int
involving remote charge determination or related payment systems · CPC title
Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR · CPC title
Point-of-sale [POS] network systems · CPC title
Receipt-giving machines · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.