Payment information transmission system using mobile terminals and methods for using the system

Abstract

This application discloses a method for transmitting payment information using a mobile terminal. The method includes transmitting the mobile payment card number (used for offline mobile payment) and the seller terminal ID from the user terminal to a payment information transmission server. The payment information transmission server then transmits a payment information transmission message, including the mobile payment card number, to the seller terminal. This allows for payment processing through a single user interface, even with various payment service providers offering different payment methods. This application also provides a corresponding payment information transmission system using a mobile terminal.

Description

Technical Field

[0001] This application relates to a payment information transmission system using a mobile terminal and a payment information transmission method using the system. The system and method have the following features: they can effectively transmit payment information even when various payment service providers offer multiple smartphone payment applications. Background Technology

[0002] Recently, personal communication terminals such as smartphones have been widely used. These terminals have been developed to not only perform mobile phone functions for communicating with another party, but also to connect to the internet, enjoy multimedia, and even make payments.

[0003] In particular, smartphones can provide payment functions for transactions, thus increasing the demand for more convenient and secure payment methods.

[0004] Accordingly, various payment service providers are not only offering payment methods in online shopping malls, but also for offline stores using smartphones, thus each payment service provider offers services with a variety of payment methods.

[0005] In particular, the increasing number of offline payment service providers using smartphones, along with the increase in the types of payment methods, has created numerous problems.

[0006] In other words, in order to make payments offline using a smartphone, the payment information stored on the smartphone must be transmitted to a seller terminal such as a POS (Point of Sales). However, the interfaces used to transmit the payment information stored on the smartphone to the POS are not standardized. Therefore, each payment service provider can only transmit payment information through its own interface equipment.

[0007] For example, some payment service providers offer their own dedicated NFC readers to read payment information from smartphones, while others offer the MST (Magnetic Secure Transmission) method to use the existing magnetic card infrastructure as is. Furthermore, some payment service providers offer methods for reading QR codes displayed on consumers' smartphones, while others offer methods for reading barcodes displayed on consumers' smartphones, and still others use a combination of these methods.

[0008] As mentioned above, the fact that each payment service provider establishes its own interface for communicating with smartphones increases consumer confusion and inconvenience, and is a major obstacle to the growth of the smartphone payment market.

[0009] Furthermore, from the seller's perspective, whenever a new payment service provider emerges, the POS system software must be upgraded, which leads to the problem that sales staff working at the seller's business premises must be trained to handle each payment method.

[0010] Therefore, a unified interface is needed so that, regardless of the payment method used by the payment service provider, the payment information stored in the smartphone can be transmitted to the seller's POS system and the payment can be processed. Summary of the Invention

[0011] Technical issues

[0012] The purpose of this application is to provide a payment information transmission system and a payment information transmission method, characterized in that, regardless of the payment method used by the payment service provider, the payment information stored in the consumer terminal is transmitted to the seller terminal for payment.

[0013] Technical solution

[0014] The payment information transmission method using a mobile terminal according to this application, which is used to solve the aforementioned technical problem, is configured to include: a step of receiving payment-required information from a mobile terminal; a step of generating a payment information transmission message using the payment-required information; and a step of transmitting the payment information transmission message to a seller terminal.

[0015] Furthermore, the payment information transmission system using a mobile terminal according to this application, used to solve the above-mentioned technical problems, is configured to include: a seller terminal ID storage unit; a user terminal that transmits a payment request message including seller terminal ID information obtained from the seller terminal ID storage unit and a mobile payment card number; a payment information transmission server that generates payment information transmission messages; and a seller terminal that transmits the mobile card number of the payment information transmission message received from the payment information transmission server to a payment authentication server.

[0016] Invention Effects

[0017] The advantage of this application is that, in offline payment methods using consumer terminals, despite the existence of various payment service providers, payments can be processed through a unified payment system.

[0018] Another benefit of this application is that it allows the user interface and payment procedures provided by payment service providers to be used as is, thereby increasing the convenience for both payment service providers and consumers participating in the market.

[0019] Another benefit of this application is that offline payments can be made using a consumer terminal, even in offline stores without the use of additional readers or scanners. Attached Figure Description

[0020] Figure 1 This is a diagram illustrating one embodiment of the process of downloading a payment application in this application;

[0021] Figure 2 This is a diagram illustrating an embodiment of the process for obtaining a mobile payment card number in this application;

[0022] Figure 3 This is a diagram showing an embodiment of the payment system according to this application;

[0023] Figures 4 to 5 This is a diagram illustrating the process by which payment information transmission software according to an embodiment of this application performs payment information transmission based on payment information transmission messages in a POS system;

[0024] Figure 6 This is a signal processing diagram according to an embodiment of this application.

[0025] Explanation of reference symbols in the attached drawings

[0026] 11: Application Server 12: Payment Service Provider

[0027] 13: Smartphones 14: Seller Terminal ID Storage Department

[0028] 15: Payment information transmission server; 16: Seller terminal

[0029] 17: Payment authentication server 18: Payment approval server

[0030] 19: Command execution software installed on the seller's terminal Detailed Implementation

[0031] Figure 1 This is a diagram illustrating one embodiment of the process of downloading a payment application in this application.

[0032] like Figure 1 As shown, a payment service provider develops a payment application with smartphone payment functionality and uploads it to an application server. At this point, the uploaded payment application contains the payment service provider's identifier information and a payment information transmission execution file.

[0033] On the other hand, if the payment application has already been uploaded to the application server, the payment service provider connects to the application server to update the payment application. At this point, the updated payment application contains the payment service provider identifier information and the payment information transmission execution file.

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

[0035] Consumers can connect their smartphones to the application server to download and install a payment application containing the payment service provider identifier information and payment information transmission execution file.

[0036] Additionally, if a payment application is already installed on a consumer's smartphone, the payment application is updated to include payment service provider identifier information and payment information transmission execution files.

[0037] Figure 2 This is a diagram illustrating one embodiment of the process for obtaining a mobile payment card number in this application.

[0038] like Figure 2 As shown, if a user drives the payment application and performs user authentication on smartphone 13, the user's smartphone 13 will transmit a request message for generating a mobile payment card number, including card ID and authentication information, to the payment authentication server 17.

[0039] During the process of registering future card information through the payment application, a card ID corresponding to the user's actual card number is generated. The generated card ID is stored in the user's smartphone payment application and the payment authentication server 17.

[0040] The payment authentication server 17 uses the authentication information transmitted from the user's smartphone 13 to authenticate whether the user requesting the generation of a mobile payment card number is a legitimate user, and to confirm whether the card ID received from the user's smartphone 13 is consistent with the card ID generated during registration.

[0041] If 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. Furthermore, the mobile payment card number generated by the payment authentication server 17 is transmitted to the user's smartphone 13.

[0042] Payment authentication server 17 determines whether the mobile payment card number transmitted from the user's smartphone 13 matches the mobile payment card number transmitted from the seller's terminal 16. If they match, payment authentication server 17 transmits the actual card number corresponding to the received mobile payment card number to payment approval server 18.

[0043] The mobile payment card number can be generated by keeping 6 digits of the actual card number (composed of 16 digits) unchanged and changing only the remaining 10 digits. The generated mobile payment card number is stored in the payment authentication server 17, corresponding to the actual card number and card ID. The mobile payment card number, corresponding to the actual card number and card ID, can be generated for each transaction. Therefore, the payment authentication server 17 can store multiple mobile payment card numbers corresponding to one actual card number and card ID, and in the event of a future transaction cancellation, the transaction corresponding to the mobile payment card number will be cancelled.

[0044] On the other hand, the mobile payment card number can be generated by adding a separate identification code to the last few digits of the 16-digit card number.

[0045] Table 1 shows how mobile payment card numbers are stored in the payment authentication server 17.

[0046] Table 1

[0047]

[0048] Users can register their cards for future payments with the payment authentication server 17 using a payment application. If a user registers their card with the payment authentication server 17 using a smartphone payment application, as shown in Table 1, a card ID corresponding to the actual card number is generated and stored.

[0049] In addition, as shown in Table 1, since users can use multiple cards, multiple card numbers can be registered for one user. Furthermore, 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.

[0050] Figure 3 This is a diagram showing an embodiment of the payment system according to this application.

[0051] like Figure 3 As shown, a payment system according to an embodiment of this application is configured to 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.

[0052] 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 transaction corresponds to.

[0053] Seller terminal 16 typically corresponds to a POS (Point of Sale) installed in an offline store.

[0054] Since the seller terminal ID storage unit 14 is used to provide the seller terminal ID, it can be a simple barcode or QR code that stores the seller terminal ID, and it can also be a sticky or adhesive NFC tag that provides seller terminal ID information via Near Field Communication (NFC). Furthermore, various methods of providing the seller terminal ID via communication and scanning or reading through a smartphone can also be applied, but for ease of use, an NFC tag is preferred.

[0055] The seller terminal ID storage unit 14 stores seller terminal ID information to identify the seller terminal 16, but only performs the function of providing it to the smartphone 13, without transmitting any information to the seller terminal 16, so that the seller terminal ID storage unit 14 does not need to be connected to the seller terminal 16 in a wired or wireless manner.

[0056] If a consumer completes authentication by driving a payment service provider application installed on their smartphone 13 for payment, the mobile payment card number is transmitted from the payment authentication server 17 to the smartphone.

[0057] Furthermore, consumers can obtain seller terminal ID information from seller terminal ID storage unit 14 using their own smartphones 13. For example, if seller terminal ID storage unit 14 is in NFC format, users can obtain seller terminal ID information by tagging their smartphones 13 in seller terminal ID storage unit 14.

[0058] As the payment information transmission execution file is executed on the consumer's smartphone 13, the payment service provider application transmits a payment request message, including the seller's terminal ID information, payment service provider identification information, and mobile payment card number, to the payment information transmission server 15 via a wireless network.

[0059] At this time, the wireless network can be a cellular network or a Wi-Fi network, or it can be another network that other smartphones 13 can wirelessly connect to.

[0060] If the payment information transmission server 15 receives payment service provider identifier information via a payment request message, it generates a payment information transmission message using that identifier information. The payment information transmission message includes the mobile payment card number transmitted from the user's smartphone. Furthermore, the payment information transmission message includes the execution content of the operations to be performed by the payment information transmission software 19 configured on the seller's terminal 16.

[0061] Here, payment information transmission software 19 refers to software installed in the seller terminal 16, which is configured to transmit payment information of the mobile payment card number to the payment authentication server by means of execution content included in the execution payment information transmission message.

[0062] Typically, the seller terminal 16 is equipped with separate software for transmitting payment information to the payment authentication server 17 in a predetermined manner according to the payment service provider, which creates the problem that the method of transmitting payment information is different for each type of software.

[0063] However, the payment information transmission software 19 configured on the seller terminal 16 of this application operates to transmit payment information according to the payment information transmission message received from the payment information transmission server 15. This software generates the payment information transmission message by reflecting the payment information transmission method of the payment service provider, thereby enabling accurate transmission of payment information by corresponding to various payment service providers.

[0064] For example, in cases where the user interface (UI) executed in the seller terminal 16 varies depending on the payment service provider, the payment information transmission server 15 of this application generates a payment information transmission message that transmits payment information according to the user interface of the various payment service providers, thereby enabling the adaptive transmission of payment information based on the different payment service providers.

[0065] When the payment information transmission server 15 identifies the payment service provider as "Provider A" through the payment service provider identifier information, the payment information transmission server 15 generates a payment information transmission message that, after the payment information transmission software 19 of the seller terminal 16 pops up the payment window of "Provider A", the mobile payment card number is entered in the card number input position of the pop-up window.

[0066] Alternatively, if the payment information transmission server 15 identifies the payment service provider as "Provider B" through the payment service provider identifier information, the payment information transmission software 19 of the seller terminal 16 generates a payment information transmission message that commands the mobile payment card number to be entered in the card number input position of the "Provider B" payment window.

[0067] The execution content included in the payment information transmission message is defined to correspond to the payment information transmission method of each payment service provider, and can be pre-stored in the payment information transmission server 15.

[0068] Accordingly, in cases where the payment service provider terminal 16 changes its payment information transmission method, such as a change in the user interface, or when a new payment service provider adds a new user interface to the seller terminal 16, the execution content stored in the payment information transmission server 15 is changed to respond accordingly.

[0069] Table 2 shows examples of the implementation content corresponding to the payment service provider according to this application.

[0070] Table 2

[0071]

[0072] The payment information transmission server 15 generates a payment information transmission message including the execution content and the mobile payment card number, and transmits it to the seller terminal 16. At this time, the seller terminal ID information received from the user's smartphone 13 determines which seller terminal 16 to which the payment information transmission message is transmitted.

[0073] As described above, payment information transmission software 19 is pre-installed on the seller terminal 16. This transmission software can execute the input of payment information transmission messages received from the payment information transmission server 15, such as the mobile payment card number, into the display of the user interface window corresponding to the payment service provider, at a specific location within the window.

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

[0075] At this point, preferably, the payment information transmission software 19 is an agent program that is linked to the payment information transmission server 15.

[0076] The payment information transmission software 19 can be used as a virtual input device, which, when executing content included in the payment information transmission grid, can exhibit the same effect as pressing a specific keyboard.

[0077] Since the agent program is connected to the payment information transmission server 15 via a link, updates can be performed through communication with the payment information transmission server 15 when updates are required.

[0078] Figures 4 to 5 This is a diagram showing the process by which payment information transmission software according to an embodiment of the present application performs payment information transmission based on payment information transmission messages in a POS system.

[0079] like Figure 4As shown, if the seller terminal 16 receives a payment information transmission message from the payment information transmission server 15, the payment information transmission software activates a pop-up window corresponding to the payment service provider based on the execution content included in the received payment information transmission message.

[0080] Subsequently, as Figure 5 As shown, the payment information transmission software of the seller terminal 16 transmits the mobile payment card number to the cursor position of the pop-up window according to the execution content included in the payment information transmission message.

[0081] Once the seller terminal 16 receives the mobile payment card number, it transmits the mobile payment card number to the payment authentication server 17. The payment authentication server 17 then checks whether the mobile payment card number received from the seller terminal 16 is consistent with the mobile payment card number generated by the payment authentication server 17 and transmitted to the consumer's smartphone 13.

[0082] If the match is confirmed, the payment authentication server 17 will transmit the actual card number information corresponding to the mobile payment card number to the payment approval server 18 and complete the payment process.

[0083] Figure 6 This is a signal processing diagram according to an embodiment of this application.

[0084] Reference Figure 6 In order to download the payment service provider's application, the consumer's smartphone 13 transmits an application download request to the application server (S601), and downloads (S602) and installs (S603) the mobile payment application, which includes the payment service provider's identifier information and the payment information transmission execution file.

[0085] If a consumer performs application-driven and user authentication for smartphone payment (S604), the payment application of smartphone 13 will request the generation of a mobile payment card number including user authentication information and card ID and transmit it to payment authentication server 17 (S605).

[0086] Upon receiving a message requesting the generation of a mobile payment card number, the payment authentication server 17 performs user authentication (S606), generates and stores a mobile payment card number corresponding to the received card ID (S607), and transmits the generated mobile payment card number to the consumer's smartphone 13 (S608).

[0087] If the consumer's smartphone 13 receives the mobile payment card number from the payment authentication server 17 (S608), the consumer obtains the seller terminal ID information from the seller terminal ID storage unit 14 by using the smartphone 13 (S610).

[0088] Since the steps of receiving the mobile payment card number S608 and obtaining the seller terminal ID information S610 are independent steps, the mobile payment card number S608 can be received after obtaining the seller terminal ID information S610.

[0089] The payment application installed on the consumer's smartphone 13 transmits a payment request message, including the seller's terminal ID information, the mobile payment card number, and the payment service provider identifier information, to the payment information transmission server 15 (S611).

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

[0091] The payment information transmission server 15 uses the seller terminal ID information included in the payment request message to determine which seller terminal the payment information transmission message should be transmitted to (S613), and thus transmits the payment information transmission message to the seller terminal 16 corresponding to the seller terminal ID (S614).

[0092] If the seller terminal 16 receives a payment information transmission message from the payment information transmission server 15, the payment information transmission software 19 activates the payment window corresponding to the payment service provider installed in the seller terminal 16, and performs the operation of entering the mobile payment card number according to the execution content of the payment information transmission message at a predetermined position (S615).

[0093] The seller terminal 16 transmits the input 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 transmitted to the consumer's smartphone 13. If they match, it is determined to be a normal transaction (S617).

[0094] If the payment authentication server 17 confirms that the transaction is normal, the payment process is completed by transmitting the actual card number corresponding to the mobile payment card number to the payment approval server 18.

Claims

1. A method for transmitting payment information using a mobile terminal, characterized in that, The structure includes the following steps: The payment information transmission server receives a payment request message from the mobile terminal. The payment request message includes the mobile payment card number, the seller terminal ID, and the payment service provider identifier information, where the payment service provider identifier information is the identifier of the payment service provider that provides the payment method. The payment information transmission server identifies the seller terminal based on the seller terminal ID; The payment information transmission server determines the corresponding payment service provider based on the payment service provider identifier information. By reflecting the transmission process of mobile payment card numbers that vary according to the identified payment service provider, a payment information transmission server generates execution content for transmitting the mobile payment card number to a payment software program installed on the seller's terminal. This execution content is performed by the payment information transmission software installed on the seller's terminal to transmit the mobile payment card number to the payment software program, which is dedicated to the identified payment service provider and configured to receive the mobile payment card number and transmit the received mobile payment card number to a payment authentication server; and The payment information transmission server generates a payment information transmission message containing the mobile payment card number and the execution content, and transmits the payment information transmission message to the seller terminal.

2. The method for transmitting payment information using a mobile terminal according to claim 1 further includes the following steps: The payment information transmission software transmits the mobile payment card number to the payment software program by executing the execution content; and The seller's terminal transmits the mobile payment card number to the payment authentication server.

3. The method for transmitting payment information using a mobile terminal according to claim 2 further includes the following steps: When the mobile payment card number received from the seller's terminal matches the payment card number transmitted to the mobile terminal, the payment authentication server transmits the actual credit card number corresponding to the mobile payment card number to the payment approval server to approve the payment.

4. The method for transmitting payment information using a mobile terminal according to claim 1, further comprising the following steps before receiving the payment request message: The mobile terminal transmits a request message for generating a mobile payment card number, which includes the card ID selected by the user and the user authentication information, to the payment authentication server; After completing user authentication, the payment authentication server generates a mobile payment card number corresponding to the card ID and transmits the generated mobile payment card number to the mobile terminal. The mobile terminal obtains the seller terminal ID from the seller terminal ID storage unit; as well as The mobile terminal generates a payment request message containing the seller's terminal ID, mobile payment card number, and payment service provider identifier, and transmits the payment request message to the payment information transmission server.

5. The method for transmitting payment information using a mobile terminal according to claim 4, characterized in that, The seller terminal ID storage unit includes a near field communication (NFC) tag.

6. A transmission system for transmitting payment information using a mobile terminal, characterized in that, The composition includes: Seller terminal: The seller terminal ID storage unit is configured to store the seller terminal ID used to identify the seller terminal; The payment information transmission server is configured as follows: Receive a payment request message from the mobile terminal containing the mobile payment card number, the seller terminal ID, and the payment service provider identifier, where the payment service provider identifier is the identifier of the payment service provider that provides the payment method; Use the seller terminal ID to identify the seller terminal; Use payment service provider identifier information to identify the corresponding payment service provider; By reflecting the transmission process of the mobile payment card number that changes according to the identified payment service provider, execution content is generated for transmitting the mobile payment card number to the payment software program installed on the seller's terminal. This execution content is executed by payment information transmission software installed on the seller's terminal to transmit the mobile payment card number to the payment software program, wherein the payment software program is dedicated to the identified payment service provider and configured to receive the mobile payment card number and transmit the received mobile payment card number to the payment authentication server; and a payment information transmission message containing the mobile payment card number and the execution content is generated and transmitted to the seller's terminal.

7. The transmission system for transmitting payment information using a mobile terminal according to claim 6, characterized in that, The seller terminal ID storage unit includes a near field communication (NFC) tag.

Images