TWM553460U - Mobile payment integration system - Google Patents

Description

Mobile payment integration system

This creation is about a payment system, especially a mobile payment integration system.

An existing payment method is to use a payment application (APP) in a mobile device (such as a smart phone) held by a consumer to scan a payment method provided by a merchant, such as a QR code, to obtain a merchant. Information and the amount of the purchased item, and then the payment application transmits the consumer's payment method information, merchant information and consumption amount to a third-party payment platform (such as a bank) for payment, after the payment confirmation is completed. The merchant can query the payment details of the third-party payment platform through the Internet, and then obtain the consumption amount paid by the consumer from the third-party payment platform.

With the development of electronic technology and network technology, the development of electronic wallet has made a clear breakthrough. Because of this, electronic wallets are gradually being valued by many merchants, using third-party payment methods to provide consumers with The online trading platform can complete the payment, eliminating the need for consumers to carry cash and credit cards.

However, with the continuous introduction of different network amount trading systems (such as Alipay, OU Bao, LINE PAY, etc.), the consumer can choose the network amount trading system that they can choose and trust. In order to satisfy the network amount trading system used by different consumers, the operator side must be individually set and confirmed with different network amount trading systems. The industry is cumbersome and inconvenient to build a network amount trading system.

To put it simply, mobile payment is the application of the user's portable electronic device as the payment authentication device, realizing the functions of stored value, credit payment and user identity authentication, using the cloud system to provide financial services, and working with the telecommunications provider to complete a kind of payment. E-commerce system. In this system, mobile devices such as smart phones and tablets play an important role as payment media. For example, a mobile device such as a stored value device or a credit payment device can use short-range communication functions such as Near Field Communication (NFC), BluetoothTM, etc., to read through a store. The payment can be completed after the signal is read.

According to the above problems, the present invention provides a mobile payment integration system, which provides a public to use the mobile device to make payment, and further provides the store device that the public is exposed to, and can obtain authorization information to facilitate the delivery or contact of the store. people.

One of the aims of the present invention is to provide a mobile payment integration system that transfers funds to a store device upon provision of a mobile device through payment integration and authorization.

For the above purposes, the present invention provides a mobile payment integration system including a store device, a mobile device, a payment integration server, an authorization server, and a database. The store device generates a first payment barcode according to a payment request message, and displays the payment barcode, and the mobile device scans the payment barcode and generates a payment confirmation message, and the payment integration server connects the mobile device to receive the mobile device. Generating the payment confirmation message, and correspondingly generating a transfer message, the authorization server is connected to the payment integration server, receives the transfer message, and authorizes the first account corresponding to the mobile device to transfer the corresponding account to the store device. A second account, a contact information corresponding to the mobile device is transmitted to the store device.

The present invention provides an embodiment in which the database stores a stored amount of the first account and the contact information.

The present invention provides an embodiment in which the authorization server authorizes the store device to the database to read the contact information.

The present invention provides an embodiment in which the authorization server further transmits the contact information to the mobile device, and the mobile device confirms the contact information and forwards the contact information to the store device.

The present application provides an embodiment in which the mobile device further controls the transfer of the contact information.

The present invention provides an embodiment in which the mobile device generates an information transfer confirmation message according to the payment barcode and transmits the information to the authorization server, and the authorization server transmits the contact information to the store device according to the information transfer confirmation message.

The present application provides an embodiment in that the contact information includes a name, a phone number, and an address.

The present invention provides an embodiment in which the payment integration server generates the payment request message.

The present invention provides an embodiment in which the authorization server generates the payment request message.

In order to give your reviewers a better understanding and understanding of the characteristics of the creation and the efficacies achieved, please provide a better example and a detailed description of the following:

In the following, the present invention will be described in detail by way of illustration of various embodiments of the present invention. However, the concept of the present invention may be embodied in many different forms and should not be construed as being limited to the illustrative embodiments set forth herein.

This creation provides a mobile payment integration system to solve the cumbersome and inconvenient problem of the previous industry to build a network amount transaction system. First, please refer to FIG. 1 , which is a system flowchart of an embodiment of the present invention, and the steps thereof include:

Step S1: generating a payment barcode;

Step S3: scanning the payment barcode;

Step S5: generating a payment confirmation message;

Step S7: transmitting a payment message;

Step S9 generates a transfer message;

Step S11: transmitting a transfer message;

Step S13: generating a first account number;

Step S15: generating a second account;

Step S17: transfer; and

Step S19: transmitting contact information.

Please refer to FIG. 2, which is a schematic diagram of a system according to an embodiment of the present invention. As shown, the present invention is a mobile payment integration system 1 comprising: a store device 100, a mobile device 200, a payment integration server 300, an authorization server 400, and a database 500. The payment integration server 300 is connected to the mobile device 200, and the authorization server 400 is connected to the payment integration server 300, and the database 500 is connected to the authorization server 400.

In step S1, the store device 100 generates a payment barcode 102 according to a payment request message 101, and displays the payment barcode 102 on the screen. The mobile device 200 scans the payment barcode 102 in steps S3 to S7 to generate a payment confirmation message. 201, and the payment confirmation message 201 is transmitted to the payment integration server 300. After the payment integration server 300 receives the payment confirmation message 201, the payment integration server 300 generates a transfer message 301, and transmits the transfer message 301 to the authorization. The server 400, after receiving the transfer message 301, the authorization server 400 transfers the corresponding first account 401 to a second account 402 corresponding to the store, and the database 500 includes a stored value. The amount 501 and a contact information 502 are finally transmitted to the store device 100 as in step S19.

Please refer to FIG. 3 , which is a system flowchart of an embodiment of the present invention. The difference between FIG. 3 and FIG. 1 is that FIG. 3 further discloses a step of transmitting contact information to the store, and the foregoing steps are not included. Narration. As shown in Figure 3, the steps further include:

Step S21: issuing authorization data;

Step S23: receiving authorization data;

Step S25: Read the contact information.

Please refer to FIG. 4 together, which is a schematic diagram of a system according to an embodiment of the present invention. The difference between FIG. 4 and FIG. 2 is that FIG. 4 further discloses a device and a server for transmitting the contact information to the store, and the device and the server are not described here. As shown in FIG. 4, in order to perform step S21 to step S25, the authorization server 400 sends an authorization data 403 to the store device 100, and the store device 100 is authorized to read the contact information in the database 500. 502.

Please refer to FIG. 5, which is a system flowchart of an embodiment of the present invention. The difference between FIG. 5 and FIG. 1 is that FIG. 5 further discloses a step of transmitting contact information to the store, and the foregoing steps are not described herein. As shown in Figure 5, its steps include:

Step S27: capturing contact information;

Step S29: transmitting contact information;

Step S31: confirm the contact information;

Step S33: Transfer the contact information.

Please refer to FIG. 6 together, which is a schematic diagram of a system according to an embodiment of the present invention. The difference between FIG. 6 and FIG. 2 is that FIG. 6 further discloses a device and a server for transmitting the contact information to the store, and the device and the server are not described here. As shown in FIG. 6, this is to perform step S27 to step S33, the authorization server 400 retrieves the contact information 502 in the database 500, and transmits the contact information 502 to the mobile device 200, which is confirmed by the mobile device 200. The contact information 502 is transmitted to the store device 100, at which time the mobile device 200 has the right to control the transfer of the contact information 502.

Please refer to FIG. 7, which is a system flowchart of an embodiment of the present invention. The difference between FIG. 7 and FIG. 1 is that FIG. 7 further discloses a step of transmitting contact information to the store, and the foregoing steps are not described herein. Its steps include:

Step S35: receiving a information transfer confirmation message;

Step S37: capturing contact information;

Step S39: transmitting contact information.

Please refer to FIG. 8 together, which is a schematic diagram of a system according to an embodiment of the present invention. The difference between FIG. 8 and FIG. 2 is that FIG. 8 further discloses a device and a server for transmitting contact information to the store, and the device and the server are not described here. As shown in FIG. 8, this is the execution of step S35 to step S39. After receiving the information transfer confirmation message 202, the authorization server 400 retrieves the contact information 502 from the database 500 and transmits the contact information 502 to the store. Device 100. The contact information 502 described above includes the name, phone number and address.

The action payment integration system of the creation, the contact information of the user in the database is transmitted to the store device through the above three ways, and is directly transmitted to the store device together with the authorization of the gold flow as an example as shown in FIG. 1 to FIG. 2 The figure and the figures 7 to 8 further reveal the flow of the system. When the store device 100 receives the payment request message 101, a QRcode (payment bar code 102) is generated, and the QR code (payment bar code 102) is displayed on the screen, as in step S1; at this time, the user uses the APP to store the QR code (payment bar code 102). In step S3, after the user scans the QRcode (payment bar code 102), a payment confirmation message 201 will be generated, as in step S5; after the payment confirmation message 201 is generated, the payment confirmation message 201 will be transmitted by the APP to the payment integration server 300. After the payment integration server 300 receives the payment confirmation message 201, the payment integration message 201 corresponds to generate the transfer message 301. In step S9, the payment integration server 300 transmits the transfer message 301 to the authorization server 400, such as Step S11: After receiving the transfer message 301, the authorization server 400 correspondingly generates the first account 401, in step S13, and correspondingly generates the second account 402 of the store, corresponding to the transfer message 301, as in step S15; The account 401 transfers the amount to the second account 402, as in step S17; at this time, the APP will display a message transfer confirmation message 202, and the user agrees to transfer and press the confirmation, this information The confirmation message 202 will be transmitted to the authorization server 400. In step S35, after the authorization server 400 receives the information transfer confirmation message 202, the user's name, phone number and address will be retrieved from the database 500 (contact information). 502), in step S37, the authorization server 400 retrieves the user's name, phone number and address (contact information 502), and then transmits the result to the store device 100, as by step S39. In this embodiment, the user will decide whether to transmit the name, phone number and address (contact information 502) to the store device.

Please refer to FIG. 9 , which is a system flowchart of an embodiment of the present invention. The difference between FIG. 9 and FIG. 1 is that FIG. 9 further discloses a step of generating a payment request message, and the foregoing steps are not described herein. Its steps include:

Step S41: generating a payment request message;

Step S43: transmitting a payment request message.

Please refer to FIG. 10 and FIG. 11 together, which is a schematic diagram of a system according to an embodiment of the present invention. The difference between FIG. 10 and FIG. 11 and FIG. 2 is that FIG. 10 and FIG. 11 further disclose a server for generating a payment request message, which is not described herein. As shown in FIG. 10, the payment request message 101 is generated by the payment integration server 300 and transmitted to the store device 100. As shown in FIG. 11, the payment request message 101 is generated by the authorization server 400, and Transfer to the store device 100.

The above creation enables the user to reduce the inconvenience of first joining the member, frequently inputting the data, and repeatedly verifying the identity when the user is on the Internet or in the long-distance shopping, so that the user can have more convenient check and the way of obtaining the goods. For the user, the complexity and trouble of the purchase process can be reduced, and the desire to purchase can be improved, and the store family can increase the number of non-members and the degree of attraction, in addition to not deliberately exploring the source of the store.

Furthermore, the embodiments of the present invention may be a combination of the above embodiments.

However, the above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and the variations, modifications, and modifications of the shapes, structures, features, and spirits described in the scope of the patent application. , should be included in the scope of the patent application of this creation.

S1‧‧‧ Generate payment barcode
S3‧‧‧ scan payment barcode
S5‧‧‧ Generate payment confirmation message
S7‧‧‧Transfer payment message
S9‧‧‧ Generate transfer information
S11‧‧‧Transfer transfer message
S13‧‧‧ Generates the first account number
S15‧‧‧Generate second account
S17‧‧‧Transfer
S19‧‧‧Transfer contact information
Authorized by S21‧‧
S23‧‧‧ Receiving authorization
S25‧‧‧Read contact information
S27‧‧‧Select contact information
S29‧‧‧Transfer contact information
S31‧‧‧Confirm contact information
S33‧‧‧Return contact information
S35‧‧‧ Receive information transfer confirmation message
S37‧‧‧Select contact information
S39‧‧‧Transfer contact information
S41‧‧‧ Generate payment request message
S43‧‧‧Transfer payment request message
1‧‧‧Activity Payment Integration System
100‧‧‧Store installation
101‧‧‧ Payment message request
102‧‧‧Payment barcode
200‧‧‧ mobile device
201‧‧‧Payment confirmation message
202‧‧‧Information transfer confirmation message
300‧‧‧Payment Integration Server
301‧‧‧Transfer message
400‧‧‧Authorized server
401‧‧‧ first account
402‧‧‧Second account
403‧‧‧Authorized information
500‧‧‧Database
501‧‧‧ stored value
502‧‧‧Contact Information

1 is a flow chart of an embodiment of the present invention; FIG. 2 is a schematic diagram of a system of an embodiment of the present invention; FIG. 3 is a flow chart of an embodiment of the present invention; Figure: is a schematic diagram of a system of an embodiment of the present invention; Figure 5: a flow chart of an embodiment of the present invention; Figure 6: a schematic diagram of a system of an embodiment of the present invention; Figure 7: A flow chart of an embodiment of the present invention; FIG. 8 is a schematic diagram of a system of an embodiment of the present invention; FIG. 9 is a flow chart of an embodiment of the present invention; FIG. 10: A schematic diagram of a system of an embodiment of the present invention; and FIG. 11 is a schematic diagram of a system of an embodiment of the present invention.

1‧‧‧Activity Payment Integration System

100‧‧‧Store installation

101‧‧‧ Payment message request

102‧‧‧Payment barcode

200‧‧‧ mobile device

201‧‧‧Payment confirmation message

202‧‧‧Information transfer confirmation message

300‧‧‧Payment Integration Server

301‧‧‧Transfer message

400‧‧‧Authorized server

401‧‧‧ first account

402‧‧‧Second account

403‧‧‧Authorized information

500‧‧‧Database

501‧‧‧ stored value

502‧‧‧Contact Information

Claims (9)

An action payment integration system, comprising: a store device, which generates a payment barcode according to a payment request message and displays; a mobile device scans the payment barcode to generate a payment confirmation message; and a payment integration server that connects the The mobile device receives the payment confirmation message and correspondingly generates a transfer message; and an authorization server connected to the payment integration server to receive the transfer message, authorizing the mobile device to transfer the first account corresponding to the store device to the store device Corresponding to one of the second accounts, one of the contact information corresponding to the mobile device is transmitted to the store device. The mobile payment integration system of claim 1, further comprising: a database connected to the authorization server, the database storing the stored value of the first account and the contact information. The mobile payment integration system of claim 2, wherein the authorization server further authorizes the store device to the database to read the contact information. The mobile payment integration system of claim 1, wherein the authorization server further transmits the contact information to the mobile device, and the mobile device confirms the contact information and forwards the contact information to the store device. The mobile payment integration system of claim 4, wherein the mobile device further controls transmission of the contact information. The mobile payment integration system of claim 1, wherein the mobile device generates a information transfer confirmation message according to the payment barcode and transmits the information to the authorization server, and the authorization server transmits the contact according to the information transfer confirmation message. Information to the store's home device. The mobile payment integration system of claim 1, wherein the contact information includes a name, a phone number and an address. The mobile payment integration system of claim 1, wherein the payment integration server generates the payment request message. The mobile payment integration system of claim 1, wherein the authorization server generates the payment request message.