Snap mobile payment apparatuses, methods and systems
US-10586227-B2 · Mar 10, 2020 · US
US11100490B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-11100490-B1 |
| Application number | US-202017079946-A |
| Country | US |
| Kind code | B1 |
| Filing date | Oct 26, 2020 |
| Priority date | Sep 10, 2020 |
| Publication date | Aug 24, 2021 |
| Grant date | Aug 24, 2021 |
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.
Application integration for contactless payments is described. In an example, a payment making platform can provide a transaction code to a payment processing platform. The transaction code can be presented at a point-of-sale of a transaction between a customer and a merchant associated with the payment processing platform. Upon detecting an interaction between the transaction code and a computing device of the customer, the payment making platform and the payment processing platform can exchange data to enable the customer to participate in the transaction via the computing device of the customer. In some examples, the payment making platform and the payment processing platform can process a contactless payment for the transaction by transferring funds associated with an account of the customer from the payment making platform to the payment processing platform for depositing into an account of the merchant.
Opening claim text (preview).
What is claimed is: 1. A payment processing platform configured to process a transaction by interaction with a peer-to-peer (P2P) payment platform, the payment processing platform comprising: a point-of-sale (POS) device comprising: a touchscreen configured to face a customer for customer selection of a payment type using the touchscreen; and a POS application configured to: generate transaction data associated with the transaction, wherein the transaction is between a merchant and the customer; receive a Quick Response (QR) code associated with the P2P payment platform; present, via the touchscreen, the QR code to the customer before presenting a payment type selection user interface to the customer; and after receiving selection of the payment type via the touchscreen or an indication, from the payment processing platform, that the customer captured the QR code using a computing device of the customer, complete the transaction via one or more server computing devices associated with the payment processing platform; and the one or more server computing devices associated with the payment processing platform configured to: receive an indication, from one or more server computing devices associated with the P2P payment platform, that the customer captured the QR code using the computing device of the customer; transmit the indication that that the customer captured the QR code using the computing device of the customer to the POS application; in response to receiving the indication that the customer captured the QR code using the computing device of the customer, send an authorization request to the one or more server computing devices associated with the P2P payment platform to authorize payment for the transaction; and in response to receiving an authorization response to the authorization request, settle funds between the merchant and the customer by depositing funds received from the P2P payment platform into a merchant account of the merchant, wherein the funds were associated with a customer account of the customer of the P2P payment platform before being deposited into the merchant account. 2. The payment processing platform as claim 1 recites, wherein the QR code is received via an Application Programming Interface (API) of the P2P payment platform. 3. The payment processing platform as claim 1 recites, wherein the QR code is received via the one or more server computing devices associated with the payment processing platform, and wherein the one or more server computing devices associated with the payment processing platform are configured to (i) obtain the QR code via an Application Programming Interface (API) of the P2P payment platform and (ii) send the QR code to the POS application. 4. The payment processing platform as claim 1 recites, wherein the QR code is specific to at least one of the transaction or the merchant. 5. The payment processing platform as claim 1 recites, wherein the one or more server computing devices associated with the payment processing platform are further configured to: receive the transaction data from the POS application; compare the transaction data with context data associated with the indication that the customer captured the QR code using the computing device of the customer to determine that the customer is associated with the transaction; and transmit the indication that the customer captured the QR code using the computing device of the customer to the POS application based at least in part on a determination that the customer is associated with the transaction. 6. A method, implemented at least in part by a payment processing platform, the method comprising: generating, by a point-of-sale (POS) application associated with the payment processing platform, transaction data associated with a transaction between a merchant and a customer; receiving, at the POS application, a transaction code associated with a payment making platform; presenting, by the POS application, the transaction code associated with a payment making platform; causing, by the POS application, the transaction code to be presented via a user interface of a computing device of the merchant; receiving, by one or more server computing devices associated with the payment processing platform, an indication, from one or more server computing devices associated with the payment making platform, of an interaction between the transaction code and a computing device of the customer; based at least in part on receiving the indication of the interaction: transmitting, from the one or more server computing devices associated with the payment processing platform, the indication of the interaction to the POS application; sending, by the one or more server computing devices associated with the payment processing platform, an authorization request to the one or more server computing devices associated with the payment making platform to authorize payment for the transaction; based at least in part on receiving the indication of the interaction, causing, by the POS application, at least a portion of the transaction data to be presented via a mobile payment application associated with the payment making platform on the computing device of the customer; and in response to receiving an authorization response to the authorization request, settling, by the payment processing platform, funds between the merchant and the customer by depositing funds received from the payment making platform into a merchant account of the merchant, wherein the funds were associated with a customer account of the customer of the payment making platform before being deposited into the merchant account. 7. The method as claim 6 recites, wherein the transaction code is associated with a resource locator to a location of the payment making platform. 8. The method as claim 6 recites, wherein the transaction code is associated with a deep link to the mobile payment application. 9. The method as claim 6 recites, wherein if the mobile payment application is not installed on the computing device of the customer, causing the mobile payment application to be installed on the computing device of the customer or enabling use of the mobile payment application on the computing device of the customer via an instant application. 10. The method as claim 6 recites, wherein the user interface is a cart building user interface for adding one or more items to a virtual cart. 11. The method as claim 10 recites, wherein the portion of the transaction data comprises an indication of the one or more items, wherein the indication of the one or more items is presented via another cart building user interface presented by the mobile payment application in near-real time. 12. The method as claim 6 recites, wherein the transaction code is presented before a payment type selection user interface. 13. The method as claim 6 recites, wherein the user interface is a payment type selection user interface. 14. The method as claim 6 recites, wherein the portion of the transaction data comprises a total cost of the transaction and wherein the total cost of the transaction is presented via a tipping user interface, a reward user interface, or a feedback user interface presented by the mobile payment application. 15. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: generating, by a point-of-sale (POS) application associated with a payment processing platform, transaction data associated with a transaction between a m
electronically operated · CPC title
comprising security or operator identification provisions, e.g. password entry · CPC title
involving fraud or risk level assessment in transaction processing · CPC title
using a pictured code, e.g. barcode or QR-code, being read by the M-device · CPC title
Managing shopping lists, e.g. compiling or processing purchase lists (shipping orders G06Q10/083; order filling G06Q10/087) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.