Secure in-line payments
US-12106300-B2 · Oct 1, 2024 · US
US10055740B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10055740-B2 |
| Application number | US-201113170121-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 27, 2011 |
| Priority date | Jun 27, 2011 |
| Publication date | Aug 21, 2018 |
| Grant date | Aug 21, 2018 |
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.
When making a payment with an electronic payment type, a user may provide additional verification of ownership through communications with the user's mobile computing device. For example, the user may swipe her bank card at a retailer's store. The retailer may authorize the bank card through an issuing party (“host”). The host may transmit a request to the user via a mobile application running on the mobile computing device, which may request the user to approve or decline the purchase request. In various embodiments, the host's request may require the user to enter personal and/or authorization information (e.g., a PIN, password, biometrics, etc.) via the mobile application to approve the request. In some aspects, the host may allow the user to split or allocate a payment amount across one or more electronic payment types available to the user from the host via the mobile application during the authorization process.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving, by one or more computing devices, one or more predetermined rules for payment authorization from a mobile device, the one or more predetermined rules including a time threshold, wherein at least one computing device of the one or more computing devices includes an authorization manager; receiving, by the one or more computing devices, a request to authorize a payment from a merchant device, the request including at least a payment identifier and an amount of a transaction; receiving, by the at least one computing device, the request; executing, by the at least one computing device, the authorization manager; identifying, by the at least one computing device via the authorization manager, the mobile device with the payment identifier; associating, by the at least one computing device via the authorization manager, a plurality of known locations with the mobile device based at least in part on the identifying the mobile device; determining, by the at least one computing device via the authorization manager, a current location of the mobile device; comparing, by the at least one computing device via the authorization manager, the current location of the mobile device with the plurality of known locations; determining, by the at least one computing device via the authorization manager, an authorization requirement, the authorization requirement including the one or more predetermined rules and at least one requirement prompting additional verification information associated with the mobile device; determining, by the at least one computing device via the authorization manager, that the mobile device is unavailable to receive an authorization message at a current time based at least in part on the current time being within the time threshold; transmitting, by the one or more computing devices, a first message to the merchant device based on the one or more predetermined rules; determining, by the at least one computing device via the authorization manager, a delay for a second message transmission based the time threshold; determining, by the at least one computing device via the authorization manager, that the delay has expired and transmitting the authorization message to the mobile device, wherein the authorization message includes a first prompt and a second prompt; receiving, by the one or more computing devices, a user response via the mobile device corresponding to the first prompt and the second prompt; determining, by the at least one computing device via the authorization manager, that the user response corresponding to the first prompt satisfies the at least one requirement of the authorization requirement; transmitting, by the one or more computing devices, a response to the merchant device including an acceptance of the payment based at least in part on the user response corresponding to the second prompt; and transferring, by the one or more computing devices, the amount of the payment to an account of a merchant associated with the merchant device. 2. The method as recited in claim 1 , wherein the additional verification information includes biometric data. 3. The method as recited in claim 1 , wherein the authorization requirement includes an additional rule that indicates that the payment is to be declined utilizing a black list or to be accepted utilizing a white list. 4. The method as recited in claim 1 , wherein the authorization requirement includes an additional rule prompting additional user input of biometric data, in response to determining that the mobile device is located at one of the plurality of known locations associated with the mobile device. 5. The method as recited in claim 1 , wherein the plurality of known locations associated with the mobile device includes at least one of a home address associated with the mobile device, a work address associated with the mobile device, or a school address associated with the mobile device. 6. A method, comprising: receiving, by one or more computing devices, a request to authorize a payment from a merchant device, the request including at least a payment identifier and an amount of a transaction, wherein at least one computing device of the one or more computing devices includes an authorization manager; retrieving, by the one or more computing devices, one or more predetermined rules for payment authorization from user data associated with the payment identifier, the one or more predetermined rules including a time threshold; receiving, by the at least one computing device, the request; executing, by the at least one computing device, the authorization manager; identifying, by the at least one computing device via the authorization manager, a mobile device with the payment identifier; associating, by the at least one computing device via the authorization manager, a plurality of known locations with the mobile device based at least in part on the identifying the mobile device; determining, by the at least one computing device via the authorization manager, a current location of the mobile device; comparing, by the at least one computing device via the authorization manager, the current location of the mobile device with the plurality of known locations; determining, by the at least one computing device via the authorization manager, an authorization requirement, the authorization requirement including the one or more predetermined rules and at least one requirement prompting additional verification information associated with the mobile device; determining, by the at least one computing device via the authorization manager, that the mobile device is unavailable to receive an authorization message at a current time being within the time threshold; determining, by the at least one computing device via the authorization manager, a delay for a message transmission based the time threshold; determining, by the at least one computing device via the authorization manager, that the delay has expired and transmitting the authorization message to the mobile device, wherein the authorization message includes a first prompt, a second prompt, and a third prompt; receiving, by the one or more computing devices, a user response via the mobile device corresponding to the first prompt, the second prompt, and the third prompt; determining, by the at least one computing device via the authorization manager, that the user response corresponding to the first prompt satisfies the at least one requirement of the authorization requirement; and transmitting, by the one or more computing device, a response to the merchant device including an acceptance of the payment based at least in part on the user response corresponding to the second prompt and the third prompt. 7. The method as recited in claim 6 , further comprising causing the amount of the payment to be transferred to an account of the merchant device in response to the transmitting the response to the merchant device including the acceptance of the payment. 8. The method as recited in claim 6 , wherein the receiving the user response corresponding to the first prompt, the second prompt, and the third prompt is performed in communication with a payment application that is different than an application used to transmit the payment to the merchant device. 9. The method as recited in claim 1 , wherein the authorization message to the mobile device includes a third prompt enabling a selection of an electronic payment type, and further comprising: requesting financial data associated with the electronic payment type; determining that the electronic payment type has sufficient funds to accommodate an amount of the transaction; and wherein transmitting
Related publications grouped by family.
Answers are generated from the same data shown on this page.