System and method for mobile device limits
US-2017061433-A1 · Mar 2, 2017 · US
US10210507B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10210507-B2 |
| Application number | US-201414286163-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 23, 2014 |
| Priority date | May 23, 2014 |
| Publication date | Feb 19, 2019 |
| Grant date | Feb 19, 2019 |
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.
Performing transactions using virtual card values is disclosed, including: generating a virtual card value corresponding to a transaction; sending a request to a card management server, wherein the request includes the virtual card value and a transaction amount corresponding to the transaction; receiving an indication from the card management server that the virtual card value and the transaction amount have been successfully stored; generating a merchant-related locator based at least in part on identifying information associated with a merchant server and the virtual card value; sending the merchant-related locator to a client device; and receiving, from the card management server, a request to transfer the transaction amount from a user account associated with a cardless payment server to a funds account associated with the merchant server.
Opening claim text (preview).
What is claimed is: 1. A cardless payment server, comprising: one or more computer processors configured to: receive, from a web browser associated with a client device, a payment request associated with a transaction and a merchant server, wherein the payment request includes a transaction amount corresponding to the transaction, wherein the transaction is initiated from the client device in response to a user selection at a website associated with the merchant server, wherein the user selection includes a user request to complete the transaction using an online payment associated with the cardless payment server; generate a virtual card value that identifies the transaction, wherein the virtual card value comprises a series of characters, wherein the virtual card value is generated for the transaction between the client device and the website associated with the merchant server, wherein the virtual card value is a unique value specific to the transaction between the client device and the website associated with the merchant server; send a storing request to a card management server for the card management server to store the virtual card value and the transaction amount, wherein the storing request includes the virtual card value and the transaction amount; receive a first indication from the card management server that the virtual card value and the transaction amount have been successfully stored; in response to the first indication from the card management server, generate a merchant-related locator that includes the virtual card value and identifying information associated with the merchant server; send the merchant-related locator to the client device, wherein the merchant-related locator comprises at least the virtual card value, the transaction amount, and a signature associated with the merchant server, wherein the signature associated with the merchant server comprises encrypted data, wherein the merchant-related locator is used to: redirect the web browser associated with the client device to a page associated with the merchant server, wherein the redirect is configured to cause the web browser associated with the client device to send to the merchant server a second indication that includes the virtual card value, the transaction amount, and the signature, wherein the second indication is used by the merchant server to: authenticate a source that generated the merchant-related locator by decrypting the signature associated with the merchant-related locator using a locally stored key; and send a pre-authorization request to the card management server to cause the card management server to complete the transaction including by storing data indicating an authorization of a charge determined based at least in part on the transaction amount on the virtual card value; and receive, from the card management server, a request to transfer the transaction amount corresponding to the transaction identified by the virtual card value from a user account at a payment platform associated with the cardless payment server to a funds account associated with the merchant server; and one or more memories coupled to the one or more computer processors and configured to provide the one or more computer processors with instructions. 2. The cardless payment server of claim 1 , wherein the one or more computer processors are further configured to: determine a source of funds associated with the user account associated with the cardless payment server to be applied to the transaction; and issue a request to transfer the transaction amount from the determined source of funds to the funds account associated with the merchant server. 3. The cardless payment server of claim 1 , wherein the one or more computer processors are further configured to: send login page data to the web browser associated with the client device; in response to the sending login page data, receive, from the web browser associated with the client device, credentials associated with the user account associated with the cardless payment server; and authenticate the credentials prior to generating the virtual card value that identifies the transaction, wherein the virtual card value is generated in response to the credentials associated with the user account being authenticated. 4. The cardless payment server of claim 1 , wherein generating the virtual card value that identifies the transaction includes: determining a first value based at least in part on information associated with the user account at the payment platform associated with the cardless payment server; determining a second value based at least in part on information of an issuer, wherein the issuer is associated with the cardless payment server; determining a third value such that a concatenation of the first value, the second value, and the third value is a unique value; and generating the virtual card value based at least in part on the first value, the second value, and the third value. 5. The cardless payment server of claim 1 , wherein the one or more computer processors are further configured to store a transaction identifier corresponding to the virtual card value. 6. The cardless payment server of claim 1 , wherein the storing request to the card management server includes authentication information associated with the cardless payment server. 7. The cardless payment server of claim 1 , wherein the card management server is configured to store the virtual card value and the transaction amount as information associated with a new virtual card, wherein a limit associated with the new virtual card is set to the transaction amount. 8. The cardless payment server of claim 1 , wherein the merchant server is configured to receive a pre-authorization confirmation from the card management server in response to the pre-authorization request and wherein the merchant server is configured to store transaction completion information in response to the pre-authorization confirmation. 9. The cardless payment server of claim 1 , wherein the one or more computer processors are configured to: receive a refund request associated with the transaction, wherein the refund request includes the virtual card value; determine a transaction identifier corresponding to the virtual card value based at least in part on stored mappings between transaction identifiers and virtual card values; retrieve stored data associated with the transaction identifier; and generate a request to transfer funds from the funds account associated with the merchant server to a source of user funds based at least in part on the retrieved data. 10. The cardless payment server of claim 1 , wherein the merchant-related locator comprises a uniform resource locator (URL). 11. A method, comprising: receiving, from a web browser associated with a client device, a payment request associated with a transaction and a merchant server, wherein the payment request includes a transaction amount corresponding to the transaction, wherein the transaction is initiated from the client device in response to a user selection at a website associated with the merchant server, wherein the user selection includes a user request to complete the transaction using an online payment associated with a cardless payment server; generating a virtual card value that identifies the transaction, wherein the virtual card value comprises a series of characters, wherein the virtual card value is generated for the transaction between the client device and the website associated with the merchant server, wherein the virtual card value is a unique value specific to the transaction between the client device and the website associated with t
Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists · CPC title
Payment protocols; Details thereof · CPC title
Virtual cards · CPC title
specially adapted for electronic shopping systems · CPC title
Use of certificates or encrypted proofs of transaction rights · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.