TW201721540A - Settlement system and method using mobile terminal - Google Patents

Abstract

A settlement system wherein: a vendor terminal receives an input billing amount, converts the billing amount into a two-dimensional code, and displays the two-dimensional code on a display; a user mobile terminal captures an image of the two-dimensional code and displays the billing amount on a display, and if this billing amount is approved, the user mobile terminal transmits card identification information and a user identification ID to a management company server; and the management company server performs a security check on the user mobile terminal on the basis of user identification information, and then performs a procedure for settling the transaction with a financial institution on the basis of card information that is obtained based on the card identification information.

Description

Using the settlement system and settlement method of the mobile terminal

The present invention relates to a settlement system and a settlement method using a mobile terminal, and more particularly to a settlement system and a settlement method for performing a user security check using a mobile terminal such as a smart phone and performing payment settlement.

In normal business transactions, users often use cash, credit cards or debit cards to purchase goods and enjoy the service and food. When a payment card such as a credit card or a debit card is used for payment, the user's payment card is read by the magnetic card reader/writer unit of the merchant terminal provided in the store, and the product name, the amount, the transaction date, and the like are input, and the output is printed. A piece of paper for this information. Merchant terminals generally use computers and sometimes mobile terminals. A password is usually required to enter the payment card. At this time, the store will simultaneously save the payment card information such as the password and the credit card information, and thus there is a risk that the password or the payment card information is maliciously used. Once the password is stolen, it can be illegally used only by pressing the button. Especially in the illegal use of payment cards, there are certain security risks in the forgery.

On the other hand, a QR code system is known in which a coded information is two-dimensionally arranged to obtain a QR code, the QR code is captured by a camera, and the captured image is decrypted into a character or the like (see Patent Document 1). The QR code has a feature that greatly increases the amount of information compared to a bar code or the like which is usually used for a payment card. In addition, there is a method of using a system or a security token for image registration and personal authentication of a human fingerprint or a venous blood vessel.

As another payment card settlement method, there is a method of reading information of a payment card used from a payment card reading device provided in a store, receiving the payment card information by a smart phone held by a store clerk, and transmitting it to a settlement server for settlement. The request, the settlement server transmits the settlement result to the employee's smartphone, the smartphone receives the settlement result and displays the recordable, and the customer photographs with his own mobile terminal and obtains the displayed settlement result (refer to Patent Document 2).

As another payment card settlement method, there is a method of carrying credit card information including a credit company name, a credit card number, an expiration date, and the like in a user's smart phone, so that it is not necessary to carry a credit card, and when the commercial transaction is performed, the credit card information is transmitted to the store for reception. terminal. The receiving terminal sends the received credit card information to the credit company server to request credit card settlement. The credit company judges based on the credit card information, and if the personal authentication result is correct, the credit card settlement is performed (refer to Patent Document 3).

For payment card settlement, it is very important to maintain security. In particular, in order to prevent passwords, passwords, and payment card information from being stolen, a system for simultaneously performing personal authentication and payment card settlement has been proposed (see Patent Document 4).

In addition, there is a system for converting the payment card data read by the card reader into a one-time use code to the merchant terminal according to a prescribed rule, and simultaneously transmitting the payment card data to the financial institution, and the financial institution will receive the payment card. Data is converted to single-use code by the same rules when it exists When a payment request is made from a merchant, the one-time use code received from the merchant is compared with the one-time use code converted by the financial institution, and if appropriate, the transaction is authorized to the merchant (refer to Patent Document 5).

[Prior Art Literature] [Patent Literature]

Patent Document 1: Japanese Laid-Open Patent Publication No. 2009-187198

Patent Document 2: Japanese Laid-Open Patent Publication No. 2013-206256

Patent Document 3: Japanese Laid-Open Patent Publication No. 2005-128899

Patent Document 4: International Gazette WO-A1-2013/168815

Patent Document 5: US2009/0222383A1

For the above settlement method using a smart phone, sometimes the settled amount information does not arrive at the user immediately, the user only visually confirms the amount, and the store side does not have evidence that the user has confirmed the settlement amount, so the transaction is not clear. Moreover, there is no adequate countermeasure against the hidden dangers of passwords for illegal use or theft of credit card information by others.

In order to eliminate these problems, a method is considered in which after the payment card information recorded on the user mobile terminal is transmitted to the merchant terminal of the store, the amount information is requested to be confirmed from the merchant terminal to the user mobile terminal, and the user confirms and approves the amount and then returns the feedback. Shop. But this method requires 3 passes. The letter process, so the settlement process is complicated.

A first object of the present invention is to provide a settlement system and a settlement method using a mobile terminal: only one round-trip communication is performed between a user mobile terminal and a store merchant terminal, and the user can record the transaction amount on his mobile terminal, and On the one hand, the merchant is able to obtain the user's promise of the transaction and the promise of the transaction amount.

A second object of the present invention is to provide a settlement system and a settlement method using a mobile terminal: it is possible to prevent others from illegally using a password and payment card information, and has high security.

In order to achieve the above first object of the present invention, a two-dimensional code including at least a merchant ID and a request amount for determining the merchant itself is created on the merchant terminal and displayed on the display, and the two-dimensional code is read by the user's mobile terminal and interpreted. The request amount and the like are displayed on the display of the user's mobile terminal, and after the user confirms and approves the amount, the operator company server returns the feedback to the merchant terminal.

In order to achieve the above second object of the present invention, the user and the merchant's required items are separately registered in the operator's server in advance, and the application is downloaded in the user's mobile terminal and the merchant terminal, respectively. During the transaction, based on the downloaded application, communication is performed between the user mobile terminal, the merchant terminal, and the operating company server, and the operating company server is executed only between the operating company and the financial institution such as the credit company when it is judged to be appropriate by the security check. The settlement procedure is notified to the user terminal and the merchant terminal after the settlement is completed. The security check here includes personal authentication and use of the user. All or part of the security check of the mobile terminal and the credit check of the user's payment card information.

According to the settlement system and the settlement method of the mobile terminal according to the present invention, it is possible to appropriately perform the meaning confirmation and the amount confirmation of the purchase at the time of the minimum operation, and if the user security check judges that it is appropriate, the payment card information does not need to be delivered. To the merchant terminal, it is possible to carry out approval processing between the operating company and the financial institution, and to conduct commercial transactions under strict security and conservative conditions.

1‧‧‧User mobile terminal

2‧‧‧Input device

3‧‧‧ display

4‧‧‧ processor

5‧‧‧ memory

6‧‧‧ camera

8‧‧‧Business terminal

9‧‧‧ Input device

10‧‧‧ display

11‧‧‧ Processor

12‧‧‧ memory

14‧‧‧Operating company server

15‧‧‧ database

16‧‧‧ Temporary storage device

17‧‧‧Processor

19‧‧‧Credit Company Server

20‧‧‧ database

Fig. 1 is a view showing the overall configuration of an embodiment of a credit card settlement system according to the present invention.

FIG. 2 is a flowchart showing an example of a procedure for a user to perform member registration.

3 is a flow chart showing an example of a procedure for a merchant to perform a merchant registration.

4 is a flow chart showing an example of a case where a user operates an operator company server after the member registers.

FIG. 5 is a flow chart showing an example of a case where a merchant operates an operation company server after the merchant registers.

6 is a flow chart showing one embodiment of the steps of performing a credit card settlement transaction between a user and a merchant.

Fig. 7 is a flowchart showing an embodiment of a processing procedure between a user mobile terminal and an operator company server, following the (1) of Fig. 6.

Fig. 8 is a flowchart showing an embodiment of a processing procedure between a merchant terminal and an operator company server, following (2) of Fig. 6.

Fig. 9 is a flowchart showing an embodiment of the processing procedure between the company server and the merchant terminal, following the step (3) of Fig. 8.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

In FIG. 1, 1 is a user mobile terminal held by a user, and is usually a smart phone having an input device 2, a display 3, a processor 4, a memory 5, and the like. The input device also includes a camera 6. 8 is a merchant terminal provided by a merchant such as a store, and has an input device 9, a display 10, a processor 11, a memory 12, and the like. The merchant terminal is preferably a smart phone or a desktop terminal. 14 is an operation company server, and includes a database 15, a temporary storage device 16, a processor 17, and the like. 19 is a credit company server with a database 20. These user terminal devices 1, merchant terminals 8, carrier company servers 14, and credit company servers 19 are connected by a communication medium 22 such as an Internet line. Incidentally, the credit company server 19 is illustrated as a financial institution in FIG. 1, but is not limited thereto, and may be a financial institution such as a bank. In the following description, a credit card and a credit card issued by the company will be described as an example. In the present invention, a debit card issued by a financial institution or a cash card having a debit function can be used for settlement.

In order to use the system of the present invention, the user must register for membership. FIG. 2 is a flowchart showing an operational procedure of the processor 4 for the user to register the member using the user mobile terminal. Should be given Note that the member registration also performs processing in cooperation with the processor 17 of the carrier company 14.

In FIG. 2, the user performs the member registration 25 using the mobile terminal 1. In step 26, the operating company server of the operating company using the system is accessed, and the member website is opened from the homepage of the operating company. In step 27, clicking on the "New Member Registration" option on the member's website will display the input form for new member registration. The input projects in this form include address, name, phone number, user ID, password, email address, 1 credit card name, credit card information, credit card name ID, and so on. The new member can arbitrarily set the user ID and password under the specified conditions for personal authentication and determination of the user. The credit card name is a concise name for the new member to determine the credit card. When you register, please select a representative credit card and decide its name. The credit card information is information necessary for credit card settlement of the credit card name, credit card number, expiration date, and owner name of the selected credit card. In order to read and display the credit card name, it is required to input a credit card name ID to make the display of highly confidential credit card information highly secure. In step 28, the new member registrant inputs the above project as the new member registration data.

Next, in step 29, the new member registration data that has been entered is sent to its own email address. Thus, the user mobile terminal 1 can receive the transmitted new member registration data. Check the registration content of the new member registration data received to confirm whether the new member registration information is correctly sent and received. Next, in step 30, the company server 14 is commissioned to create a member ID and a security ID. The security ID is a reference ID for determining and authenticating the user's mobile terminal.

In step 32, the operator company server 14 that receives the member ID and the security ID creation request is set. The member ID and the authentication ID 1 are registered in the database 15 in units of members. Next, in step 33, the authentication ID 1 is converted to a security ID using the conversion logic and registered. As described in Patent Document 4, the conversion logic can convert the authentication ID into a security ID by the same method as the method of converting the ID bit data into the authentication ID using the ID mapping address. However, other conversion logic can also be used to convert the authentication ID to a secure ID. Each member's conversion logic is different and is registered in the database as a member. In step 34, the member ID and the security ID are sent to the user mobile terminal.

In step 36, the user mobile terminal receives the member ID and the security ID and registers in the memory 5. Then, in step 37, the user terminal ID1 which is the individual identification number unique to the mobile terminal assigned to each mobile terminal is obtained. In step 38, the user mobile terminal entrusts the operating company server to register the member ID, the security ID, the user terminal ID1, and the new member registration data.

In step 40, the carrier company associates the member ID, the authentication ID 1, the security ID, the user terminal ID 1, the new member registration data, and registers it in the database 15, and ends the process. It should be noted that the result obtained by using the conversion logic conversion user terminal ID1 may be registered as the user terminal ID1c.

The user registration of the user has been described above. Next, the operation procedure of the processor 11 when the merchant is registered in the store or the like will be described with reference to FIG.

In FIG. 3, the merchant performs merchant registration 45 using the merchant terminal 8. First, in step 46, the merchant accesses the operating company server of the operating company that uses the system, and opens the merchant website from the operating company homepage. In step 47, click on the "new member registration" option in the merchant website, which will display the new Input form for member registration. The input project in this form has the name, branch name, address, representative name, phone number, email address, merchant account information, user ID, password, and so on. The new member registration merchant can arbitrarily set the user ID and password under the specified conditions for authentication and determination of the merchant. In step 48, the new merchant registrant inputs the input project segment as the new member registration data. After the new member registration information is output, the new member registration data is transmitted to the carrier server 14 in step 49.

In step 51, the carrier company server 14 receives the new member registration data and registers it in the database 15.

On the other hand, in step 53, if the merchant terminal 8 delegates the approval of the merchant to the operating company server, then in step 55, the operating company server creates the merchant ID, and in step 56, attaches the merchant ID to the merchant terminal to send the approval email.

In step 58, the merchant terminal 8 receives the approval email, and in step 59, the merchant ID attached to the approval email is registered in the memory of the merchant terminal, and the processing ends.

According to FIG. 4, the member operation 62 of the operating company server by the user after registering the member will be described.

In FIG. 4, if the user operates the user mobile terminal to open the member website of the operating company server in step 63, and inputs in the user ID and password input fields in step 64, then in the step 65 will display the "Download Member Application", "Change Member Information", "Additional ‧ Change Credit Card Information", "Billing History", "App Stop" and other options.

In step 65, if the "member application download" is clicked, the member ID and the user terminal ID1 are read in step 67, and the member ID and the user terminal ID1 are attached to request the company server 14 to download the member application. It should be noted that the member application includes member information and programs required for the user to perform credit card settlement in a commercial transaction with the merchant.

The company server 14 selects the member application created based on the member information corresponding to the received member ID in step 69, and compares the received user terminal ID1 with the user terminal ID1 registered in step 40 in step 70 to determine whether or not Consistent security checks. If the security check is OK, the member application is sent to the user mobile terminal 1 in step 71. If the security check determines that it is unqualified NO, the user is notified that the mobile terminal cannot download the member application. Since the user terminal ID1 is an individual identification number unique to the user mobile terminal, the member application is downloaded only for the same terminal license as the mobile terminal used for registration.

The user mobile terminal 1 registers it with the receiving member application in the memory 5 in step 73, and the icon for creating the member application in step 74 is displayed on the display 3 to end the processing. It should be noted that, in step 76, when receiving the notification that the download is impossible, it is confirmed whether or not the terminal different from the user mobile terminal operated in FIG. 2 is used to operate, and the member application is downloaded again. Thereby, it is possible to prevent the member application from being downloaded based on the operation of the non-legitimate user. In addition, it is also possible to prevent the member application from being downloaded to a terminal other than the user mobile terminal used when the member registers. Thereby, the original use registered by the member can be protected Users and their mobile terminals are not illegally used or stolen.

In step 65, when "change member information" is selected, the company server 14 can change the name, address, telephone number, email address, user ID, or password. In step 65, when "additional change credit card information" is selected, up to five credit card names and related credit card information can be additionally registered in step 80, and the registered partial credit card name and credit card information can be changed or deleted. Up to 5 additional registrations make it impossible to add credit card information without restriction, and it is convenient to set a maximum of five. When "settlement history" is selected in step 65, the past credit card settlement history can be read and browsed from the database 15 in step 84. When "Application Stop" is selected in step 65, the use of the downloaded member application can be stopped in step 84.

The operation 86 of the operator company server 14 that can be performed by the merchant terminal 8 after the merchant is registered will be described based on FIG.

In FIG. 5, the merchant operates the merchant terminal to open the merchant website of the operating company server in step 87, and after inputting the information in the user ID and password input fields in step 88, the "download merchant application" and the "change merchant information" are displayed. And other options. The merchant application includes functions required for the merchant to use the system for commercial transactions, such as a function of QR encoding the request information including the requested amount, a program for performing the timing function and the communication function, and information required for the commercial transaction.

Click "Download Merchant Application" in step 89 to display the input field of the merchant ID. In step 90, the merchant ID is input to the operator company server 14 to download the merchant application in the input field.

The carrier company server that has received the merchant application download request checks in step 92 whether the received merchant ID matches the merchant ID registered in the database 15. If the result is OK, the merchant application is sent to the merchant terminal in step 93.

The merchant terminal 8 receives the merchant application in step 95 and registers in the memory 12, and in step 96 creates an icon for the merchant application and displays it on the display. On the other hand, if the result of the check in step 92 of the company server is NO, the step 98 of the merchant terminal indicates that the download cannot be performed. Thus, the check of step 92 prevents the merchant application from being illegally downloaded.

Next, a procedure for performing credit card settlement 100 when a user purchases a product at a store will be described with reference to FIGS. 6 to 9.

In FIG. 6, in the case where the user and the store agree on the commercial transaction, the user terminal 8 may display the user ID and password input screen in step 102 after clicking the merchant application icon displayed on the display in step 101. Enter the merchant's user ID and password to log in. The option of "Enter settlement amount" and "Create QR code" is displayed on the screen after login, and the merchant inputs the request amount in the "Enter settlement amount" column in step 103, and clicks "Create QR code" in step 104. As a result, the request information including the merchant ID, the requested amount, and the detailed number is QR coded and the QR code is displayed in step 105.

On the other hand, when the commercial transaction is agreed, the user mobile terminal 1 is at step 107. Clicking on the member application icon displayed on the display displays the option to include the user ID, password, and login. In step 108, a user ID and password are entered for login. Here, personal authentication is performed as described in WO-A1-2013/168815, and the description thereof is omitted here. Next, when the credit card name ID is input in step 109, one or more credit card names registered in the database 15 of the carrier company 14 are displayed, and it is displayed that the payment is selected in one-time payment or installment payment, and the installment payment is divided into several installments. The "Payment Method" option and the "Read QR Code" option are available.

Next, in step 110, up to five credit card names are displayed on the display. In step 111 the user specifies the credit card name to be used for payment, and the number of payments is entered in step 112. It should be noted that since the payment is made by using the debit card, the step is skipped and the step is skipped.

The credit card name and the number of payouts are confirmed and determined in step 113. Next, in step 114, the QR code reader of the memory and the user's mobile terminal is activated, and the camera 6 is activated. In step 115, the QR code displayed in the merchant terminal 8 in step 105 is captured and read by the camera 6. The read QR code is parsed in step 117, and it is judged in step 118 whether the parsing result is OK. Here, if NO, return to step 115 again to reread the QR code. If it is OK in step 118, the operation of the processor 4 of the user mobile terminal 1 proceeds to the flow of Fig. 7 . Steps 107-114 of the user mobile terminal and steps 101-104 of the merchant terminal are usually performed in parallel at the same time. Incidentally, the above description has been made using the QR code, but the present invention is not limited thereto, and may be a barcode if it is a two-dimensional code. Alternatively, the request information that the user can visually display may be displayed without displaying the OR code, and the user inputs the request information into the user mobile terminal.

In FIG. 7, if the analysis result of the QR code is OK, in step 120, the request amount, the tip amount input field, the total payment amount, and the approval button of the total payment amount acquired from the merchant terminal are displayed. The tip amount input field initially displays 0, and the total payment amount column displays the requested amount. In the case where the user pays the tip, the amount of the tip to be paid is entered in the tip amount input field, and the total amount of the payment shows the total amount of the requested amount and the tip amount.

In step 121, when the user confirms the total payment amount and agrees to pay, the user clicks the approval button. The settlement processing procedure after step 122 is started with the click operation of the approval button as a trigger.

In step 122, the individual identification number inherent to the user mobile terminal, that is, the user terminal ID2 is acquired. Then, in step 123, the user terminal ID2, the merchant ID, the requested amount, the tip amount, the total payment amount, the detailed number, the credit card name, the number of payments, and the security ID are transmitted as settlement data to the operating company server. It should be noted that the user terminal ID2 and the security ID are used to determine and authenticate the user mobile terminal. The security ID is registered in the memory 5 in step 36. When the settlement information is transmitted, the security ID registered in the memory 5 is attached to the settlement data.

The carrier company server 14 registers the settlement data received from the user mobile terminal 1 in the temporary storage device 16 in step 125. Next, in step 126, the credit card name registered in the temporary storage device is read, the corresponding credit card information is obtained and sent to the credit company server 19, which is requested to perform a credit check of the user credit card. The credit company server 19 performs a credit check in step 191, and returns the result of the check as a credit result to the carrier company 14. The carrier company receives the credit result in step 127, registers it in the temporary storage device 16, and transmits it to the user mobile terminal. The user mobile terminal receives the credit result in step 124 and registers it as a settlement data, ending the process.

FIG. 8 is a flow chart showing the operation of the processor 11 subsequent to the step 127 of displaying the QR code in the step 105 of the merchant terminal in FIG.

In Figure 8, the 60 second timer is started in step 128. Then, in step 129, it is checked whether the elapsed time has reached 60 seconds. If the elapsed time has not reached 60 seconds in step 129, the determination here is OK, and the process proceeds to step 130. In step 130, the merchant ID, the total payment amount, and the detailed number included in the QR code included in step 104 of FIG. 6 are requested to acquire the settlement data including the information from the operating company server 14. It should be noted that the attached information is the minimum information that can determine the transaction.

The operator company server 14 retrieves the settlement data including the merchant ID, the requested amount, the consumption, the total payment amount, and the detailed number from the material stored in the temporary storage device 16 in step 132 in step 132. In step 133, the search results are sent to the merchant terminal. When the settlement information is not found in the search in step 132, the search result not including the settlement data is transmitted to the merchant terminal.

The search result is received in step 135 of the merchant terminal, and in step 136, it is judged whether or not the settlement data having the user terminal ID2 or the like is included in the received search result. Here, if it is judged as NO, it returns to step 129. Thus, the data retrieval of the temporary storage device is repeated within 60 seconds, and after the elapsed time reaches 60 seconds, the timeout is stopped in step 138 and the operation is stopped.

The result of the search in step 132 is that when the settlement information is found, the settlement data is sent to the merchant terminal 8 in step 133. In step 136, when it is determined that the settlement data such as the user terminal ID2 is included, the flow proceeds to step 137. Here, the merchant terminal 8 requests the operating company server 14 to perform a security check.

When receiving the security check request in step 139, the carrier server 14 reads the user terminal ID1 registered in step 40, and reads the user terminal ID2 from the settlement data retrieved in step 133, and proceeds to step 141 of FIG. 9, where , compare ID1 and ID2. It should be noted that, when the user terminal ID1 is logically converted into the user terminal ID1c and registered in step 40, the user terminal ID2 is converted into the user terminal ID2c using the same logic, and ID1c and ID2c are compared in step 141.

In step 141 of FIG. 9, it is judged whether or not the registered user terminal ID1 and the user terminal ID2 in the settlement data are compared. Here, if they do not match, in step 142, a notification that the credit card cannot be settled is transmitted to the merchant terminal (Fig. 8) by (4). Then, the merchant terminal displays in step 143 that the credit card cannot be settled on the display 10 and ends the process. In this case, operate again. As a result, it is not possible to perform settlement from a terminal other than the user mobile terminal that the user originally used at the time of registration of the new member, and it is possible to prevent illegal use by others. This security check is a check for performing user mobile terminal authentication.

When it is determined in step 141 that ID1 and ID2 are identical, the reading in the settlement data is performed in step 14. The security ID, which is converted to the authentication ID2 using conversion logic. The conversion logic uses the same conversion logic as the conversion logic in step 33 of FIG. In step 33, the authentication ID1 is converted into a security ID, but here the security ID is reversely converted into the authentication ID2. This designing the transformation logic to be available for reverse conversion is readily available to those skilled in the art.

In step 144, the authentication ID 1 registered in step 40 is further read from the database 15. Then, in step 145, it is judged whether or not the read authentication ID 1 coincides with the converted authentication ID 2. Here, if it is determined that there is no match, the process proceeds to step 142, and a notification that cannot be settled is transmitted to the merchant terminal in the same manner as described above. Thus, in the case of inconsistency, the security ID transmitted from the user mobile terminal 1 to the carrier server 14 and stored in the temporary storage device 16 is different from the security ID registered in the first step 36 of the new member registration for some reason. This means that during the time the user's mobile terminal is used, the security ID has sent a change for some reason. The change in the security ID transmission causes some trouble, and by having this detection function, transactions can be avoided when trouble occurs. Thereby, the security of credit card settlement can be improved.

On the other hand, if it is determined in step 145 that the match is made, it can be determined that the security ID originally designated by the user mobile terminal in the new member registration is still correct and functions normally. Next, in step 146, a notification that the result of the security check is OK is sent to the merchant terminal. At this time, the credit result and the credit card name read from the temporary storage device can be attached to the notification of the security check OK.

On the other hand, when the merchant terminal receives the notification of the security check OK in step 150, Step 151 reads the credit result registered in step 124. It should be noted that the credit result received in step 135 may be omitted using step 124. Then, in step 152, it is determined whether the credit result is an approval. If the determination in step 152 is NO, then in step 155, the operating company server credit result is notified to be NO. Upon receiving the notification of the credit result NO, the carrier company server transmits a notification that cannot be settled to the merchant terminal in step 142. The merchant terminal displays in step 143 that the display 10 cannot be settled and ends the action. This enables a credit check of the user's debit account to ensure transaction security. If credit is not granted, use another credit card for settlement or cash payment.

On the other hand, when it is determined to be OK at step 152, the settlement information including the credit card name is attached in step 157 to request payment from the carrier company 14. The payment request is automatically made, but the merchant may request payment by clicking the confirmation button after confirming the confirmation of the security check OK including the credit check and confirming the transaction content.

Upon receipt of the payment request, the carrier company server reads the credit card information registered in the database 15 based on the received credit card name in step 160. Then, in step 161, a credit card settlement procedure is performed between the credit card information and the settlement information with the credit company server 19. That is, the credit company performs credit card settlement and returns settlement completion data based on the settlement request from the operating company server. Then, after receiving the credit card settlement completion information from the credit company, the process proceeds to step 163, where the settlement completion data is transmitted to the merchant terminal 8 and the user mobile terminal 1, and the settlement completion data is registered as the settlement history in the database 15, and the flow is ended. Here, the credit card settlement completion information includes the merchant ID, the settlement amount, the tip amount, the total payment amount, the detailed number, the letter Use card name, number of payments, and security ID. It should be noted that the user can browse the relevant settlement history data of the user from the database 15 in steps 65 and 82 of FIG. The merchant can also view the relevant billing history data of the merchant registered in the database. This content is described in International Publication No. WO-A1-2013/168815.

The merchant terminal receives the settlement completion data received from step 163 at step 165 and displays the settlement completion on the display 10. On the other hand, the user mobile terminal receives the settlement completion data transmitted from step 163 in step 167 and displays the settlement completion on the display 3.

In order to conduct a commercial transaction using the system explained above, the user mobile terminal 1 and the merchant terminal 8 must separately download a member application or a merchant application that performs an action based on the system from the carrier company server 14, respectively. Users and merchants cannot download a member application or a merchant application to their user mobile terminal or merchant terminal without using the user ID and password registered on the operating company server, so others cannot download the member application or the merchant application. Thereby, illegal commercial transactions can be prevented from happening in the first place.

In the commercial transaction using the system described above, the user registers the credit card name as a representative in association with the credit card information when the new member is registered and the credit card information is additionally registered thereafter. In a subsequent commercial transaction, there is no need to prompt the merchant for credit card information, and the credit card name can be used for the settlement transaction. Therefore, credit card information that needs to be kept confidential will not be notified to the merchant terminal, and thus can be prevented from being distributed. As a result, the risk of illegal use of credit card information by others can be greatly reduced.

Further, in the above embodiment, when the user performs new member registration, the operator company server is entrusted to create the member ID and the security ID, and as a result, the member ID and the security ID are registered in the company server and the user mobile terminal, and thus the member The ID or security ID can be used as a user's personal authentication or information for determining the user's mobile terminal.

In addition, when the user performs a new member registration, the individual identification number uniquely assigned to the user's mobile terminal itself is read, and is registered as a user terminal ID1 in the database of the operating company server, and is automatically generated in each commercial transaction performed thereafter. The individual identification number is read as the user terminal ID2, and the ID1 and the ID2 are compared, whereby the user mobile terminal is authenticated and checked, and therefore only the transaction permission credit card using the predetermined user mobile terminal is settled. Therefore, even if the other party steals the member ID, password, or security ID, the mobile terminal other than the mobile terminal having the user terminal ID1 cannot perform credit card settlement.

Further, in the commercial transaction using the system described above, after the merchant purchases the desired amount of money, the merchant terminal creates a QR code including the product data required for the transaction such as the requested amount and the merchant ID. Wait for the QR code and display it on the display. The user mobile terminal captures the displayed QR code using the built-in camera, and displays the requested amount on the display after parsing. When the user confirms the click of the approval button such as the requested amount, the settlement data to which the credit card name or the like of the user is attached to the product data is registered in the temporary storage device of the company server. Then, the operating company reads the credit card information based on the credit card name registered in the temporary storage device, and sends it to the credit company to request a credit approval check. The operating company obtains credit as a credit company The credit result of the inspection result is approved, and the credit result is used to confirm the credit of the user's debit account, and then the settlement transaction is performed, thereby ensuring the security of the settlement transaction.

In the above embodiment, the user's operation is only to read the QR code click approval button, and the operation of the merchant is only to prompt the product information, so that the communication steps between the user mobile terminal, the merchant terminal, and the operating company server can be simplified. The minimum required, especially to simplify the communication between the user and the merchant to complete the credit card settlement only once.

In the above description, credit card settlement has been exemplified, but the present invention is not limited thereto, and a debit card or a cash card having a debit card function may be used. In addition, the case where the operating company server performs the settlement transaction with the credit company is described, but it is not limited to the credit company, and may be a general financial institution including the bank.

Incidentally, in the embodiment, credit card settlement has been described as an example. Therefore, the term of the credit card information is used, but the term of the payment card information may be used as a concept including the debit card information. However, since the system of the present invention can be executed by downloading information equivalent to the payment card information to the user mobile terminal without issuing a payment card such as a credit card, even if the payment card is not issued, Information is called payment card information. Similarly, when one of a plurality of payment cards is designated, the term specifying the payment card is used even if the payment card is not issued. Further, although the term of the credit card name is used in the above description, the term of the payment card name is used as an alias for the settlement information representing the debit card, the cash card, and the like and the settlement information of the non-issued payment card.

In the above embodiment, the description has been made in the case of purchasing goods at a store, but the present invention is also applicable to payment in restaurants and service industries, and is also applicable to online transactions via the Internet.

Further, in the above embodiment, the case of performing payment settlement using the user mobile terminal has been described, but for example, a desktop computer can be used when performing online transactions at home. At this time, the user can display the QR code sent from the merchant terminal on the computer display in the home, and perform the transaction by the user mobile terminal reading the displayed QR code. In this way, the QR code can be displayed on the display of the merchant terminal, the user's computer display or a third-party computer display, and the business based on the system of the present invention can be completed by capturing the QR code displayed on any computer by using the user mobile terminal. transaction.

It should be noted that various modifications can be made without departing from the spirit of the invention.

Claims (27)

A settlement system using a mobile terminal, comprising: a merchant terminal (8) that converts request information including a request amount into a two-dimensional code and displays it on a display; and a user mobile terminal (1) that captures and parses the two-dimensional code Displaying the request information on the display, and when the request information is approved, transmitting the settlement data required for settlement including the user-determined ID to the operating company server; operating the company server (14) having the database (15) and temporary storage a device (16) having registered business information of the merchant terminal and member information of the user mobile terminal, the temporary storage device (16) storing the settlement received from the user mobile terminal Data, the operating company server performs a security check of the user mobile terminal according to the user determination ID stored in the settlement data of the temporary storage device and member information registered in the database, if the security check If the result is appropriate, the settlement procedure is performed between the financial institution and the financial institution according to the settlement data, and the settlement completion notification is sent when the settlement is completed. The merchant terminal. The settlement system according to claim 1, wherein the user determines that the ID is a user terminal ID2 related to an individual identification number of the user mobile terminal, and the security check is performed by comparing the user terminal ID2 and the user terminal ID1, The user terminal ID1 is included in the member information, and is acquired in advance from the user mobile terminal and registered in a database of the company server. The settlement system according to claim 1, wherein the user determines that the ID is a security ID given by the operating company server and stored in the memory of the user mobile terminal at the time of registration of the new member, the security check is compared by the storage The security ID of the temporary storage device and the security ID registered in the database when the operating company gives it are performed. The settlement system according to claim 1, wherein the operation company server sets an authentication ID1 when the user performs a new member registration, converts the authentication ID1 into a security ID using a prescribed conversion logic, and the authentication ID1 and the security ID Associated with the new member registration data, registered as the member information in the database, and transmitting the security ID to the user mobile terminal, the user mobile terminal registering the received security ID in the memory The user determines that the ID is a security ID that has been registered in the memory, and the operating company server uses the conversion logic to convert the security ID into an authentication ID 2, by comparing the authentication ID 2 with reading from the database The authentication ID 1 is taken to perform a security check. The settlement system according to claim 1, wherein the operating company server associates one or more payment card information of the user with a payment card name referring to each payment card information in advance, and registers the member information as In the database, the settlement data includes payment card designation information specifying one of one or more payment card names, and the operating company server obtains payment from the database according to the payment card designation information in the settlement data. The card information performs a settlement procedure with the financial institution based on the payment card information. The settlement system according to claim 5, wherein the user mobile terminal is registered in advance with a payment card name ID, and when the payment card name ID is input, a screen designating the payment card name is displayed on the display. The settlement system according to claim 1, wherein the operating company server creates a merchant ID when registering the merchant, registers the merchant information as a merchant information, and generates the merchant ID to the merchant terminal, and the merchant terminal receives the merchant ID Registering in the memory, displaying the two-dimensional code including the merchant ID, attaching the request amount and the merchant ID to the operating company server, requesting to retrieve the settlement registered in the temporary storage device The data, when the search result can confirm that the settlement data exists, entrust the security check, and when the operation company server receives the security check request, perform the security check. The settlement system according to claim 7, wherein the operating company server retrieves the existence of the settlement data including the requested amount and the merchant ID upon receipt of the retrieval request, and then receives the When the security check is commissioned, the security check is performed based on the user-determined ID in the settlement data. The settlement system according to claim 1, wherein the two-dimensional code is a QR code (104, 105, 115). The settlement system according to claim 1, wherein, when the user mobile terminal performs an operation of approving the request information, the operation company is triggered by the operation, and the operating company is at the merchant terminal and the financial institution The settlement process begins. The settlement system according to claim 1, wherein the operating company server receives the settlement data from the user terminal, the knot Calculating the data in the temporary storage device, and entrusting the financial institution to perform the credit check involved in the settlement data, registering the credit result fed back from the financial institution in the temporary storage device, and the credit result is suitable In the case of the settlement, the settlement procedure is executed. The settlement system according to claim 11, wherein the merchant terminal acquires the credit result from a temporary storage device of the operating company server, and sends the requested amount to the operating company when the credit result is appropriate The payment request is made when the operating company receives the payment request. The settlement system according to claim 11, wherein, when the merchant terminal acquires the credit result and the settlement data from the temporary storage device, the server of the operating company is entrusted to perform a security check, and when the security check is received When the result is a suitable feedback, the payment request is sent. A settlement method using a mobile terminal, comprising the steps of: a merchant terminal (8) converting a request information including a request amount into a two-dimensional code and displaying the same on a display; the user mobile terminal (1) photographing and parsing the two-dimensional code And displaying the request information on the display, and when the request information is approved, transmitting the settlement data required for settlement of the user-determined ID to the operating company server; the operating company server (14) having the business terminal registered a database (15) relating to the merchant information and the member information related to the user mobile terminal, and a temporary storage device (16) storing the settlement data received from the user mobile terminal, according to the temporary storage device (16) a step of performing, by the user determination ID and the member information registered in the database, the security check of the user mobile terminal in the settlement data of the storage device; When it is determined that the result of the security check is appropriate, the step of performing a settlement procedure with the financial institution based on the settlement information; and the step of transmitting the settlement completion notification to the merchant terminal upon completion of the settlement. The settlement method according to claim 14, comprising the step of: when the operating company server receives the settlement information from the user terminal, registering the settlement information in the temporary storage device, and entrusting the financial a step of the credit check involved in the settlement information; a step of registering a credit result fed back from the financial institution in the temporary storage device; the merchant terminal obtaining the credit result and the location from the temporary storage device In the case of the settlement information, the step of entrusting the server of the operating company to perform a security check; receiving the appropriate feedback of the security check result, and then, when the credit result is appropriate, performing the request for payment of the requested amount to the operating company a step; and when the operating company receives the payment request, performing the settlement procedure. A merchant terminal is a merchant terminal in a settlement system using a mobile terminal, and has: a memory (12) for holding a merchant application that previously contains programs and materials required for settlement, and determining a merchant ID of the merchant; (11), the merchant terminal is actuated according to a program held in the memory; an input device (9) for inputting a request amount; and a display (10) containing at least the requested amount and the merchant ID The request information is converted into a two-dimensional code and displayed on the display; the user mobile terminal (1) recognizes the requested amount displayed by capturing the two-dimensional code, and appends the user identification ID and the payment card designation to the request information. The settlement information of the information is sent to the operating company After the server, the processor requests the operating company server to perform a security check, and when the security check has appropriate feedback, makes a payment request to the operating company server, and as a result, the operating company performs settlement with the financial institution. formalities. A user mobile terminal device is a user mobile terminal device in a settlement system using a mobile terminal, comprising: an input device (2) having a camera (6); and a memory (5) for maintaining a pre-included settlement required a member application of the program and data, and a user identification ID determining the user; a processor (4) that causes the user mobile terminal device to operate according to a program held in the memory; and a display (3) using the camera Taking a two-dimensional code displayed after converting the request information input from the merchant terminal, parsing the two-dimensional code to display the request information on the display; and clearing the data unit (123), when the recognition is displayed on the display When requesting the information, the settlement information to which the one of the payment card name and the user-determined ID is attached is sent to the operating company server, and the operating company server performs the security check according to the user-determined ID, when the security check is performed. a merchant terminal that permits the operating company server or receives payment card information obtained by the operating company server according to the payment card name, as appropriate Perform settlement procedures with the payment card information. The user mobile terminal according to claim 17, wherein the settlement data unit inputs a tip amount in the request information displayed on the display, displays a total amount of the request amount and the tip amount, and recognizes the amount . The user mobile terminal according to claim 18, wherein the payment card name has one or more, and one payment card name designated for settlement is attached to the settlement data. The user mobile terminal according to claim 19, wherein the payment card name is a name assigned to one payment card information or a plurality of payment card information, and each payment card name corresponds to each payment card information, and is associated in advance. The registration is in the database of the operating company server. If the user mobile terminal specifies the payment card name, the operating company server can read the corresponding payment card information. The user mobile terminal of claim 20, wherein the payment card name and payment card information can be added, deleted, or modified to the operating company server. The user mobile terminal according to claim 17, wherein, when the payment card name ID is input from the input device, one or more payment card names are displayed on the display, and one payment card name can be designated. An operating company server is an operating company server in a settlement system using a mobile terminal, and has: a database (15) for registering merchant information including a merchant ID involved in the merchant terminal, and a user involved in the user mobile terminal Determining the ID and the member information of the at least one payment card information; the temporary storage device (16) receiving from the user mobile terminal that captured the two-dimensional code including the request information of the merchant ID displayed on the display by the merchant terminal And storing the settlement information with the user identification ID and the payment card designation information added to the request information; a unit performing a settlement procedure, performing a security check according to the user-determined ID included in the settlement data, and reading the payment card information of the user according to the payment card designation information if the result of the security check is appropriate , perform settlement procedures. The carrier company server according to claim 23, wherein the user determines that the ID is a security ID, and the security ID is registered in the database as the member information in advance, and is given to the user mobile terminal. The carrier company server according to claim 24, wherein the security ID is obtained by converting conversion certificate ID registered in the database as the member information in advance using conversion logic. The operating company server according to claim 25, wherein the conversion ID is used to convert the security ID in the settlement data to obtain an authentication ID 2 by comparing the authentication ID 2 with the authentication registered in the database IDI is used for security checks. The operating company server according to claim 23, wherein the user determines that the ID is the user terminal ID2 involved in the individual identification information of the user mobile terminal, by using the user terminal ID2 and the user mobile terminal obtained in advance The user terminal ID1 related to the individual identification information, that is, the user terminal ID1 registered as the member information in the database, is compared to perform security check.