IP Library Granted Patent US 11,645,642
Granted Patent B2
US 11,645,642 · App. 16/172,156 · Granted May 9, 2023

Mobile payment system and method using a mobile payment device without an installed application

Inventors: Jack Shauh (San Diego, CA); Andrew Vinh Banh (Irvine, CA)
G06Q20/3226G06Q20/3674G06Q20/401
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,645,642
App. No.
16/172,156
Granted
May 9, 2023
Kind
B2
Abstract

A mobile payment method includes the steps of providing a mobile payment device having mobile payment capability and a mobile identity. Providing transaction information for a transaction and sending the transaction information to a server. The server prepares a URL link containing the transaction information and sends the URL link to the mobile payment device using the mobile identity. Clicking on the URL link sets up a HTTPS session and program script and validation token are downloaded to the mobile device. The payment can then proceed.

Claims (44)

1. A mobile payment method comprising the steps of:

providing a mobile payment device having mobile payment capability and a mobile identity;

providing transaction information for a transaction;

providing a server including a Uniform Resource Locator (URL) Generation module;

sending the transaction information to the URL Generation module of the server;

the URL Generation module of the server creating a URL link containing the transaction information, the transaction information including a transaction identity, a transaction amount, a currency code, a merchant identity, supported networks and a message signature;

the server sending the URL link to the mobile payment device using the mobile identity;

displaying the URL link by the mobile payment device;

a user clicking on the URL link to set up a Hypertext Transfer Protocol Secure (HTTPS) session by the mobile payment device;

downloading a program script and validation token to the mobile device in the HTTPS session; and

confirming payment transaction by the mobile payment device, the step of confirming payment transaction includes the program script retrieving the payment related information embedded in the URL, interacting with a mobile payment core of the mobile device to generate encrypted payment data and sending the encrypted data to one of the online merchant and the server.

2. A mobile payment method as claimed in claim 1 wherein the step of providing transaction information for a transaction includes the step of making a purchase at an online merchant and checking out using a web browsing capable device.

3. A mobile payment method as claimed in claim 2 wherein the step of sending the transaction information to a server includes sending the transaction information to the server from one of the online merchant and the web browsing capable device.

4. A mobile payment method as claimed in claim 1 wherein the step of providing transaction information for a transaction includes the steps of creating a bill for goods or services by a provider of the goods or services, the bill including transaction information.

5. A mobile payment method as claimed in claim 4 wherein the step of sending the transaction information to a server includes sending the transaction information to the server from the provider of the goods or services.

6. A mobile payment method as claimed in claim 1 wherein the step of preparing a URL link containing the transaction information includes information required by a mobile wallet Application Programming Interface (API) used in the transaction.

7. A mobile payment method as claimed in claim 1 wherein the step of sending the URL link to the mobile payment device using the mobile identity includes using one of Short Message Service (SMS) and Email.

8. A mobile payment method as claimed in claim 3 wherein the step of the user clicking on the URL link to set up a HTTPS session includes setting up a session between the mobile payment device and one of the online merchant and the server.

9. A mobile payment method as claimed in claim 1 wherein the step of downloading a program script and validation token to the mobile device in the HTTPS session includes downloading the program script and the validation token from one of the online merchant and the server.

10. A mobile payment method comprising the steps of:

providing a web browsing capable device;

providing a mobile payment device having mobile payment capability and a mobile identity;

providing a server connectable to the web browsing capable device and the mobile payment device, the server including a Uniform Resource Locator (URL) Generation module;

using the web browsing capable device in communication with the Internet to make an online purchase at an online store and receiving payment information;

sending transaction information from one of the online merchant and the web browsing capable device to the URL Generation module of the server;

the URL Generation module of the server creating a URL link containing the transaction information, the transaction information including a transaction identity, a transaction amount, a currency code, a merchant identity, supported networks and a message signature;

the server sending the URL link to the mobile payment device using the mobile identity;

displaying a URL link by the mobile payment device;

a user clicking on the URL link by the mobile payment device to set up a Hypertext Transfer Protocol Secure (HTTPS) session between the mobile payment device and one of the server and the online merchant;

downloading a program script and validation token to the mobile payment device from the one of the server and the online merchant in the HTTPS session;

sending a token indication from the mobile device to one of the server and the online merchant; and

one of the server and the online merchant authorizing the transaction with a payment network.

11. A mobile payment method as claimed in claim 10 wherein the step of preparing a URL link containing the transaction information includes information required by a mobile wallet Application Programming Interface (API) used in the transaction.

12. A mobile payment method as claimed in claim 10 wherein the step of sending the URL link to the mobile payment device using the mobile identity includes using one of Short Message Service (SMS) and Email.

13. A mobile payment system comprising:

a server receiving transaction information, the server including a Uniform Resource Locator (URL) link generator for creating a URL link including the transaction information, the transaction information including a transaction identity, a transaction amount, a currency code, a merchant identity, supported networks and a message signature;

a mobile payment device having a mobile payment capability;

wherein the mobile payment device receives the URL link with the transaction information, displays the URL link on the mobile payment device for selection by a user, and establishes a Hypertext Transfer Protocol Secure (HTTPS) session using the URL link when selected by the user; and

program script and validation token are downloaded to the mobile payment device in the HTTPS session, wherein the program script retrieves the payment information embedded in the URL, establishes a payment protocol with the payment capability of the mobile payment device.

14. A mobile payment system as claimed in claim 13 further including:

an online merchant; and

a web browsing capable device communicating with the online merchant to create the transaction information and send the transaction information to the server.

15. A mobile payment system as claimed in claim 13 further including an online merchant to create the transaction information and send the transaction information to the server.

16. A mobile payment system as claimed in claim 13 further including a mobile payment core of the mobile payment device interacting with the program script to generate encrypted payment data sent to the server.

Continuity (3)
Provisional Application 62585525 · Nov 13, 2017
Provisional Application 62577685 · Oct 26, 2017
Related Publication 20190130384A1 · May 2, 2019