Payment information transmission system using a mobile terminal and payment information transmission method using the same

Abstract

To provide a settlement information transmission system using a mobile terminal and a settlement information method using this system.SOLUTION: A system according to the present invention provides effects that settlement can be processed with the same user interface regardless of settlement systems of various settlement business operators, by transmitting, from a user terminal to a settlement information transmission server, mobile settlement card number and a seller terminal ID for execution of on-line mobile settlement, and by transmitting, from the settlement information transmission server to the seller terminal, settlement information transmission message including the mobile settlement card number.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a payment information transmission system using a mobile terminal and a payment information transmission method using the same, and more particularly to a payment information transmission system and a payment information transmission method using the same that enable efficient transmission of payment information despite multiple smartphone payment applications provided by various payment providers. [Background technology]

[0002] Recently, personal communication devices such as smartphones have become widespread. Personal communication devices such as smartphones not only function as telephones for communicating with other parties, but have also evolved to connect to the Internet, enjoy multimedia content, and even perform payment functions.

[0003] In particular, as smartphones now provide payment functions for transactions, the demand for more convenient and secure payment methods has increased.

[0004] As a result, various payment providers are not only offering payment methods at online shopping malls, but are also expanding into the payment business at offline stores using smartphones, which has led to the emergence of various payment methods for each payment provider.

[0005] In particular, as the number of offline payment providers using smartphones increases, the number of payment methods also increases, but this has given rise to many problems.

[0006] In other words, to make an offline payment using a smartphone, the payment information stored on the smartphone must be sent to a merchant terminal such as a Point of Sales (POS). However, since there is no standardized interface for sending the payment information stored on the smartphone to the POS, the payment information is transmitted through an interface device unique to each payment service provider.

[0007] For example, some payment providers provide their own NFC readers to read payment information from smartphones, while others provide the MST (Magnetic Secure Transmission) method to use the existing magnetic card infrastructure.Some payment providers provide a method to read the QR code displayed on the user's smartphone with a reader, others provide a method to read the barcode displayed on the user's smartphone, and some payment providers use a combination of these methods.

[0008] As such, each payment service provider has to develop its own interface for communicating with smartphones, which increases confusion and inconvenience for users and is a major obstacle to the growth of the smartphone-based payment market.

[0009] Furthermore, from the seller's perspective, they have to upgrade their POS system software every time a new payment service provider appears, and they have to train their store staff on how to process each payment method.

[0010] Therefore, a unified interface method was needed that would allow payment information stored on a smartphone to be transmitted to the seller's POS system and processed regardless of the payment method used by the payment company. Summary of the Invention [Problem to be solved by the invention]

[0011] An object of the present invention is to provide a payment information transmission system and a payment information transmission method that transmits payment information stored in a user terminal to a seller terminal side to make a payment, regardless of the payment method of a payment provider. [Means for solving the problem]

[0012] In order to solve the above technical problems, a method for transmitting payment information using a mobile terminal according to the present invention includes the steps of receiving information necessary for payment from a mobile terminal, generating a payment information transmission message using the information necessary for payment, and transmitting the payment information transmission message to a seller terminal.

[0013] In addition, a payment information transmission system using a mobile terminal according to the present invention for solving the above technical problems includes a seller terminal ID storage unit, a user terminal which sends a payment request message including seller terminal ID information and a mobile payment card number acquired from the seller terminal ID storage unit, a payment information transmission server which generates a payment information transmission message for transmitting the mobile payment card number received from the user terminal to the seller terminal corresponding to the seller terminal ID, and a seller terminal which sends the mobile card number of the payment information transmission message received from the payment information transmission server to a payment authentication server. Effect of the Invention

[0014] The present invention has an effect of enabling payments to be processed through a unified payment system in an offline payment method using a user terminal, regardless of the payment methods of various payment providers.

[0015] By allowing the user interface and payment process provided by each existing payment provider to be used as is, the convenience of payment providers and users participating in the market is increased.

[0016] This has the advantage that offline payment can be performed using a user terminal without the need for an additional reader or scanner at the offline store. [Brief description of the drawings]

[0017] [Figure 1] FIG. 1 illustrates an embodiment of a process for downloading a payment application in the present invention. [Diagram 2] FIG. 2 illustrates an embodiment of a process for obtaining a mobile payment card number in the present invention. [Diagram 3] FIG. 3 shows an embodiment of a payment system according to the present invention. [Figure 4] FIG. 4 illustrates a process in which the payment information transmission software executes payment information transmission through a payment information transmission message in a POS system according to an embodiment of the present invention. [Diagram 5] FIG. 5 illustrates a process in which the payment information transmission software executes payment information transmission through a payment information transmission message in a POS system according to an embodiment of the present invention. [Figure 6] FIG. 6 is a signal processing diagram according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] FIG. 1 illustrates the process of downloading a payment application in the present invention.

[0019] As shown in Figure 1, a payment service provider develops a payment application with a smartphone payment function and uploads it to an application server. At this time, the uploaded payment application has the identifier information of the payment service provider and an execution file for transmitting payment information.

[0020] On the other hand, if the payment application has already been uploaded to the application server, the payment company connects to the application server and updates the payment application, where the updated payment application has the identifier information of the payment company and a payment information transmission execution file.

[0021] The payment information transmission execution file may be configured in a library format within a smartphone application.

[0022] A user can access an application server through his / her smartphone and download and install a payment application having identifier information of the payment business operator and an execution file for transmitting payment information.

[0023] Alternatively, if a payment application is already installed in the user's smartphone, the payment application is updated so that the payment application has the identifier information of the payment business operator and a payment information transmission execution file.

[0024] FIG. 2 illustrates the process of obtaining a mobile payment card number in the present invention.

[0025] As shown in FIG. 2, when a user executes a payment application on the smartphone 13 and performs user authentication, the user smartphone 13 sends a mobile payment card number generation request message including a card ID together with authentication information to the payment authentication server 17.

[0026] The card ID is generated to correspond to the user's actual credit card number in the process of registering credit card information to be used in the future through the payment application. The generated card ID is stored in the user's smartphone payment application and the payment authentication server 17.

[0027] The payment authentication server 17 uses the authentication information transmitted from the user smartphone 13 to authenticate whether the user who requested the generation of a mobile payment card number is a legitimate user, and checks whether the card ID received from the user smartphone 13 matches the card ID generated at the time of registration.

[0028] Once the authentication and card ID confirmation are completed, the payment authentication server 17 generates and stores a mobile payment card number corresponding to the card ID received from the user's smartphone 13. The mobile payment card number generated by the payment authentication server 17 is then transmitted to the user's smartphone 13.

[0029] The payment authentication server 17 determines whether the mobile payment card number transmitted from the user smartphone 13 matches the mobile payment card number transmitted from the seller terminal 16. If a match is confirmed, the payment authentication server 17 sends the actual card number corresponding to the received mobile payment card number to the payment approval server 18.

[0030] The mobile payment card number can be generated by leaving 6 digits of a 16-digit actual card number unchanged and changing only the remaining 10 digits, and the generated mobile payment card number is stored in the payment authentication server 17 so as to correspond to the actual card number and card ID. Since the mobile payment card number can be generated for each transaction in correspondence with the actual card number and card ID, the payment authentication server 17 can store multiple mobile payment card numbers corresponding to one actual card number and card ID, and if a future transaction is canceled, the transaction corresponding to the mobile payment card number is canceled.

[0031] Meanwhile, the mobile payment card number can be generated by adding a separate identification code indicating that it is a mobile payment card number to the suffix of the 16-digit card number.

[0032] Table 1 shows the method by which the mobile payment card number is stored in the payment authentication server 17. [Table 1]

[0033] A user can register a credit card to be used for future payments in the payment authentication server 17 using the payment application. When a user registers his / her credit card in the payment authentication server 17 using the smartphone payment application, a card ID corresponding to the actual credit card number is generated and stored as shown in Table 1.

[0034] In addition, as shown in Table 1, since a user can use multiple credit cards, multiple credit card numbers can be registered for one user, and since a mobile payment card number can be generated each time a payment is made, multiple mobile payment card numbers corresponding to one actual card number can be generated and stored.

[0035] FIG. 3 shows an embodiment of a payment system according to the present invention.

[0036] As shown in FIG. 3, the payment system according to an embodiment of the present invention may include a seller terminal ID storage unit 14, a smartphone 13, a payment information transmission server 15, a seller terminal 16, a payment authentication server 17, and a payment approval server 18.

[0037] The seller terminal ID storage unit 14 is a device that stores identifier information (ID) that is individually assigned to each seller terminal 16, and provides information for determining which seller terminal a transaction corresponds to.

[0038] The seller terminal 16 generally corresponds to a POS (Point Of Sale) installed in an offline store.

[0039] The seller terminal ID storage unit 14 is for providing the seller terminal ID, and may be a simple barcode or QR code capable of storing the seller terminal ID, or may be a pad-type or sticker-type NFC tag capable of providing seller terminal ID information through a near field communication method. Furthermore, various methods capable of providing the seller terminal ID through smartphone communication, scanning or reading may be applied, but for convenience of use, it is preferable to use an NFC tag.

[0040] The seller terminal ID storage unit 14 stores seller terminal ID information for identifying the seller terminal 16, and only performs the function of providing this to the smartphone 13 and does not transmit any information directly to the seller terminal 16, so the seller terminal ID storage unit 14 does not necessarily need to be connected to the seller terminal 16 by wire or wirelessly.

[0041] When a user executes a payment service provider application installed on his / her smartphone 13 to make a payment and completes authentication, a mobile payment card number is transmitted from the payment authentication server 17 to the smartphone.

[0042] Then, the user uses his / her smartphone 13 to obtain the seller terminal ID information from the seller terminal ID storage unit 14. For example, if the seller terminal ID storage unit 14 is in the NFC format, the user can obtain the seller terminal ID information by tagging his / her smartphone 13 to the seller terminal ID storage unit 14.

[0043] The payment service provider application executed on the user's smartphone 13 executes the payment information transmission executable file to send a payment request message including the seller terminal ID information, the payment service provider identifier information, and the mobile payment card number to the payment information transmission server 15 via the wireless network.

[0044] The seller terminal ID information, the payment business identifier information, and the mobile payment card number are preferably transmitted using a payment request message, but may be transmitted separately.

[0045] In this case, the wireless network may be a cellular network, a Wi-Fi network, or any other network to which the smartphone 13 can wirelessly connect.

[0046] When the payment information transmission server 15 receives the identifier information of the payment business operator through a payment request message from the user's smartphone 13, it generates a payment information transmission message using the received identifier information. The payment information transmission message has the mobile payment card number transmitted from the user's smartphone. The payment information transmission message also has the execution details of the operation to be performed by the payment information transmission software 19 installed in the seller terminal 16.

[0047] The mobile payment card number and transaction details are preferably transmitted through a payment information transmission message, but may also be transmitted separately.

[0048] Here, the payment information transmission software 19 refers to software installed in the seller terminal 16 to execute the execution details included in the payment information transmission message and transmit payment information such as a mobile payment card number to the payment authentication server.

[0049] Generally, the seller terminal 16 is equipped with payment software for transmitting payment information to the payment authentication server 17 in a manner predetermined by the payment provider, but there is a problem that the manner of transmitting payment information differs depending on the payment software provided by each payment provider.

[0050] However, the payment information transmission software 19 provided in the seller terminal 16 of the present invention transmits the mobile payment card number according to the execution details provided by the payment company, and the execution details are generated to reflect the payment information transmission method corresponding to the payment company, so that it can accurately transmit payment information in response to various payment companies individually.

[0051] For example, even if the user interface (UI) formats executed on the seller terminal 16 differ among various payment providers, the payment information transmission server 15 according to the present invention generates execution details that allow the payment information to be transmitted according to the user interfaces of various payment providers, so that the payment information can be transmitted adaptively according to the payment provider.

[0052] For example, if the payment information transmission server 15 recognizes that the payment provider is “Business A” through the identifier information of the payment provider, the payment information transmission server 15 can generate execution details such that the payment information transmission software 19 installed in the seller terminal 16 executes the payment software of “Business A” to pop up a payment window and input the mobile payment card number in the card number input position of the popped up window.

[0053] Alternatively, if the payment information transmission server 15 recognizes that the payment provider is “Business B” through the payment provider’s identifier information, it can generate execution details for the payment information transmission software 19 of the seller terminal 16 to input the mobile payment card number into the card number input position of the “Business B” payment window.

[0054] The execution details included in the payment information transmission message can be determined to correspond to the payment information transmission method of each payment business operator and can be stored in the payment information transmission server 15 in advance.

[0055] Therefore, even if a payment service provider changes the payment information transmission method, such as changing the user interface on the seller terminal 16, or if a new payment service provider adds a new user interface to the seller terminal 16, this can be accommodated by changing the execution details stored in the payment information transmission server 15.

[0056] Table 2 shows an example of an execution breakdown corresponding to a payment service provider according to the present invention. [Table 2]

[0057] The payment information transmission server 15 generates a payment information transmission message including the execution details and the mobile payment card number as shown in Table 2, and transmits it to the seller terminal 16. At this time, the seller terminal 16 to which the payment information transmission message is to be sent is determined based on the seller terminal ID information received from the user's smartphone 13.

[0058] As mentioned above, the seller terminal 16 is pre-installed with payment information transmission software 19 that can execute the execution details of a payment information transmission message received from the payment information transmission server 15, such as displaying a user interface window in response to the payment software corresponding to the payment provider and inputting a mobile payment card number at a specific position in the window.

[0059] The payment information transmission software 19 can be installed by the seller by downloading it through a network to which the POS system is connected, or by copying a file from a storage device such as a flash memory and executing it.

[0060] At this time, it is preferable that the payment information transmission software 19 is a software agent linked to the payment information transmission server 15. Here, the payment information transmission software 19, i.e., the software agent, is executed with priority over general software installed in the seller terminal.

[0061] The payment information transmission software 19 can also function as a virtual input device that provides the same effect as pressing a specific keyboard when executing the execution details included in the payment information transmission message.

[0062] The software agent is linked to the payment information transmission server 15, so that if an update is required, the software agent can perform the update through communication with the payment information transmission server 15.

[0063] 4 and 5 show a process in which the payment information transmission software 19 transmits payment information to the POS terminal 16 according to an embodiment of the present invention.

[0064] When the seller terminal 16 receives a payment information transmission message from the payment information transmission server 15, as shown in FIG. 4, the payment information transmission software 19 executes the payment software corresponding to the payment provider according to the execution details included in the received payment information transmission message, and activates a pop-up window.

[0065] Next, as shown in FIG. 5, the payment information transmission software 19 of the seller terminal 16 transmits the mobile payment card number to the cursor position of the pop-up window according to the execution details included in the payment information transmission message.

[0066] When the seller terminal 16 receives the mobile payment card number and sends it to the payment authentication server 17, the payment authentication server 17 checks whether the mobile payment card number received from the seller terminal 16 matches the mobile payment card number generated by the payment authentication server 17 and sent to the user's smartphone 13.

[0067] If a match is confirmed, the payment authentication server 17 sends the actual card number information corresponding to the corresponding mobile payment card number to the payment approval server 18.

[0068] FIG. 6 is a signal processing diagram according to one embodiment of the present invention.

[0069] Referring to FIG. 6, in order to download a mobile payment application of a payment provider, a user's smartphone 13 sends an application download request to an application server (S601), downloads the mobile payment application including the payment provider's identifier information and a payment information transmission executable file (S602), and installs it (S603).

[0070] When the user executes the smartphone payment application and performs user authentication for payment (S604), the payment application of the smartphone 13 sends a mobile payment card number generation request message including user authentication information and card ID to the payment authentication server 17 (S605).

[0071] The payment authentication server 17 that receives the mobile payment card number generation request message performs user authentication (S606), generates a mobile payment card number corresponding to the received card ID, stores it (S607), and sends the generated mobile payment card number to the user smartphone 13 (S608).

[0072] When the user's smartphone 13 receives the mobile payment card number from the payment authentication server 17 (S608), the user uses the smartphone 13 to obtain seller terminal ID information from the seller terminal ID storage unit 14 (S610).

[0073] Since the step of receiving the mobile payment card number (S608) and the step of obtaining seller terminal ID information (S610) are mutually independent steps, it is also possible to receive the mobile payment card number (S608) after obtaining the seller terminal ID information (S610).

[0074] The mobile payment application installed in the user's smartphone 13 sends a payment request message including the seller terminal ID information, the mobile payment card number, and the payment company's identifier information to the payment information transmission server 15 (S611).

[0075] The payment information transmission server 15 generates a payment information transmission message for accurately transmitting the mobile payment card number to the payment information transmission software 19 based on the identifier information of the payment company included in the payment request message (S612).

[0076] The payment information transmission server 15 determines to which seller terminal the payment information transmission message should be sent using the seller terminal ID information included in the payment request message (S613), and sends the payment information transmission message to the seller terminal 16 corresponding to the seller terminal ID (S614).

[0077] When the seller terminal 16 receives a payment information transmission message from the payment information transmission server 15, the payment information transmission software 19 executes the payment software corresponding to the payment company installed in the seller terminal 16 to activate the payment window and performs operations according to the execution details of the payment information transmission message, such as entering the mobile payment card number in a specified position (S615).

[0078] The seller terminal 16 sends the entered mobile payment card number to the payment authentication server 17 (S616), and the payment authentication server 17 compares the mobile payment card number received from the seller terminal 17 with the mobile payment card number generated by the payment authentication server 17 and sent to the user smartphone 13, and if they match, determines that the transaction is normal (S617).

[0079] If the payment authentication server 17 confirms that the transaction is normal, it transmits the actual credit card number corresponding to the mobile payment card number to the payment approval server 18. [Explanation of symbols]

[0080] 11 Application Server 12 Payment Service Provider Server 13 User's smartphone 14 Seller terminal ID storage section 15 Payment information transmission server 16 Merchant Terminal 17 Payment authentication server 18 Payment Authorization Server 19 Payment information transmission software

Claims

1. A step in which a payment information transmission server receives a payment request message including a mobile payment card number, a seller terminal ID, and a payment service provider identifier from a mobile terminal device, the payment service provider identifier being an identifier of a payment service provider that provides a payment method; determining a seller terminal by using the seller terminal ID; the payment information transmitting server identifying a corresponding payment provider using the payment provider identifier; generating an execution detail for transmitting the mobile payment card number to the payment software installed in the seller terminal by the payment information transmission server, the execution detail reflecting a transmission method of the mobile payment card number that changes according to the identified payment business operator, the execution sequence is executed by a software agent installed on the merchant terminal to communicate the mobile payment card number to payment software; the payment software is dedicated to an identified payment service provider and configured to receive the mobile payment card number and communicate the received mobile payment card number to a payment authentication server; the payment information transmission server generates a payment information transmission message including the mobile payment card number and the transaction details, and transmits the payment information transmission message to the seller terminal; A method for transmitting payment information using a mobile terminal including:

2. A step of transmitting the mobile payment card number to the payment software by the software agent executing the execution details; the seller terminal transmitting the mobile payment card number to the payment authentication server; The method of claim 1 , further comprising:

3. A step in which the payment authentication server transmits to a payment approval server an actual credit card number corresponding to the mobile payment card number transmitted to the mobile terminal when the mobile payment card number received from the seller terminal matches the payment card number transmitted to the mobile terminal; The payment information transmitting method according to claim 2 , further comprising:

4. Before receiving the payment request message, sending a mobile payment card number request message including a card ID and user authentication information selected by a user to the payment authentication server; the payment authentication server generates a mobile payment card number corresponding to the card ID after performing user authentication, and transmits the generated mobile payment card number to the mobile terminal; acquiring the seller terminal ID from a seller terminal ID storage unit by the mobile terminal; generating a payment request message including the seller terminal ID, the mobile payment card number, and the payment business identifier, and sending the payment request message to the payment information transmission server; The payment information transmitting method according to claim 1 , further comprising:

5. The payment information transmission method described in claim 2, wherein the merchant terminal ID storage unit includes an NFC (Near Field Communication) tag.

6. A seller terminal; A seller terminal ID storage unit configured to store a seller terminal ID that identifies the seller terminal; A payment information transmission server, receiving a payment request message including a mobile payment card number, a seller terminal ID, and a payment provider identifier from the mobile terminal, the payment provider identifier being an identifier of a payment provider that provides a payment method; determining a merchant terminal using the merchant terminal ID; Identifying a corresponding payment service provider using the payment service provider identifier; The payment information transmission server generates an execution detail for transmitting the mobile payment card number to the payment software installed in the seller terminal, reflecting a transmission method of the mobile payment card number that changes according to the identified payment business operator; the execution sequence is executed by a software agent installed on the merchant terminal to communicate the mobile payment card number to payment software; the payment software is dedicated to the identified payment business operator and is configured to receive the mobile payment card number and transmit the received mobile payment card number to a payment authentication server; The payment information transmission server is configured to generate a payment information transmission message including the mobile payment card number and the execution details, and to transmit the payment information transmission message to the seller terminal; A payment information transmission system using a mobile terminal including:

7. The payment information transmission system of claim 6, wherein the merchant terminal ID storage unit includes an NFC (Near Field Communication) tag.

Images