KR20200017735A - Easy payment method and system for supporting payment of a plurality of payment companies using only one QR code - Google Patents

Abstract

The present invention relates to a simple payment system for supporting payment of a plurality of payment companies by using a single QR code and, more particularly, to a simple payment system for supporting mobile application payment in various ways by a plurality of payment companies without adding an affiliated store hardware infrastructure by providing a single QR code to an affiliated store without providing a plurality of QR codes for all the payment companies and minimizing modification of a user application to support payment of a plurality of payment companies only by adding a connection between a transaction brokerage server and a payment company server.

Description

Easy payment method and system for supporting payment of a multiple of payment companies using only one QR code}

The present invention relates to a QR code-based payment technology, and more particularly, to a simple payment system that supports the payment of multiple payment providers using a single QR code.

In the Republic of Korea Patent No. 10-1780707 (September 15, 2017), when a customer terminal that recognizes an NFC tag or QR code attached to a store requests a payment history information by accessing a server, the server makes a payment from a merchant POS terminal or a billing system. When the customer terminal receives the history information and transmits it to the customer terminal and requests the payment approval, the server uses the mobile payment service technology using the QR code to request the payment approval from the card company system, the bank system or the point company system. I'm proposing.

This technology allows the customer's terminal to store a large number of mobile card information, such as a loyalty card and a check card, and selects one card to pay from among a plurality of mobile cards, such as a credit card, a loyalty card and a check card, upon request for payment Ask for payment approval.

Recently, various mobile app payments using QR codes are gradually expanding. By the way, since the QR code is different for each payment provider, you must have several QR codes in the merchant, and solve the inconvenience of the user to find and pay the QR code according to the payment app.

Therefore, there is a need for a technology that has one single QR code and automatically connects payment providers according to a payment app that recognizes the QR code. At this time, the merchant owner or the user should be able to automatically connect the payment service according to the type of payment app without any additional work.

In addition, merchants who want to introduce a merchant payment infrastructure that can support various mobile app payment systems should have no difference between the card payment system and the user interface (UX) of the existing merchant payment terminal and directly between the merchant payment terminal and the user mobile terminal. There should be no connection, and transaction information must be distinguishable.

Therefore, the present inventors have studied a single QR payment technology that can solve the problem of inconvenience to both the merchant and the user by issuing a QR code separately for each payment provider in the existing QR code-based easy payment service.

Republic of Korea Patent No. 10-1780707 (2017.09.15)

The present invention can use a single QR code in common in a plurality of payment apps to pay, multiple merchants or users using a single QR code that can automatically process payments without a separate operation for each payment provider It is an object of the present invention to provide a simple payment method and system that supports the payment service provider.

Another object of the present invention is there is no difference between the existing card payment system and the user interface, no direct connection between the merchant payment terminal and the user mobile terminal, it is possible to distinguish the transaction information, various ways without changing the hardware of the existing merchant payment terminal It is to provide a simple payment method and system that can support mobile app payment.

According to an aspect of the present invention for achieving the above object, a simple payment system that supports the payment of multiple payment providers using a single QR code according to the transaction information registration request corresponding to the merchant identification information from the merchant payment terminal A transaction information registration step of storing and registering transaction information corresponding to affiliated store identification information by the transaction intermediation server; According to the transaction information inquiry request corresponding to the merchant identification information from the payment app executed by the user mobile terminal that recognizes a single QR code, the transaction brokerage server identifies the payment provider corresponding to the payment app identification information, and identifies the merchant identification information. Search transaction information corresponding to the transaction information processing step of processing the transaction information corresponding to the searched merchant identification information to the transaction information corresponding to the payment type of the identified payment provider and transmits to the payment app executed by the user mobile terminal Wow; In response to a payment request for transaction information corresponding to the payment type of the payment provider from the payment app executed by the user mobile terminal receiving the transaction information corresponding to the payment type of the payment provider, the payment provider server causes the payment provider server to settle the payment type. A payment approval processing step of processing payment approval for transaction information corresponding to the; And a payment approval result processing step of transmitting, by the payment service provider server that has processed payment approval for transaction information corresponding to the payment type of the payment service provider, to the transaction intermediation server.

According to an additional aspect of the present invention, in the payment approval result processing step, the brokerage server brokers payment approval results for transaction information corresponding to the payment type of the payment provider to the merchant payment terminal.

According to an additional aspect of the present invention, in the payment approval result processing step, the merchant payment terminal that receives the transaction information corresponding to the payment type of the payment operator outputs a payment receipt corresponding to the received payment approval result.

According to another aspect of the present invention, a simple payment system that supports the payment of multiple payment providers using a single QR code corresponding to the merchant identification information according to the transaction information registration request corresponding to the merchant identification information from the merchant payment terminal A transaction information register for storing and registering transaction information in a DB; According to the transaction information inquiry request corresponding to the merchant identification information from the payment app executed by the user mobile terminal that recognizes a single QR code including the merchant identification information, the payment service provider corresponding to the payment app identification information is identified, and the merchant Transaction information that searches for transaction information corresponding to the identification information, processes transaction information corresponding to the searched merchant identification information into transaction information corresponding to the payment type of the identified payment provider, and transmits the transaction information to a payment app executed by a user mobile terminal. A search unit; Receiving the payment approval result for the transaction information corresponding to the payment type of the payment provider from the payment provider server that processed the payment approval for the transaction information corresponding to the payment type of the payment provider, and stores the received payment approval result in the DB. Payment approval result management unit; A payment approval result retrieval unit for retrieving payment approval results for transaction information corresponding to the payment type of the payment provider from the DB and transmitting the payment approval result for the transaction information corresponding to the payment type of the searched payment provider to the merchant payment terminal; do.

According to an additional aspect of the present invention, a simple payment system that supports the payment of multiple payment providers using a single QR code according to the payment request for the transaction information corresponding to the payment type of the payment provider from the user mobile terminal, The apparatus further includes a payment provider server that processes payment approval for transaction information corresponding to the payment type of the payment provider and transmits the payment approval result to the corresponding user mobile terminal and the transaction brokerage server.

According to an additional aspect of the present invention, if transaction information is registered by the transaction brokerage, the transaction status information changes the payment status information to change the transaction status information corresponding to the merchant identification information matched with the transaction information to the transaction registration status. Includes more wealth.

According to an additional aspect of the present invention, when the transaction information corresponding to the payment type of the payment provider is transmitted to the user mobile terminal, the payment status information changing unit may receive payment status information corresponding to the transaction information corresponding to the payment type of the payment provider. Change to the payment waiting state, and change the payment status information corresponding to the merchant identification information to the transaction waiting state to enable the registration of another transaction information.

According to an additional aspect of the present invention, if the payment approval result for the transaction information corresponding to the payment type of the payment provider is transmitted to the merchant payment terminal corresponding to the merchant identification information, The payment status information corresponding to the corresponding transaction information is changed to the payment completion status.

According to an additional aspect of the present invention, if there is no transaction information search request corresponding to the affiliated store identification information from the user mobile terminal for a specific time in the transaction registration state transaction information search unit corresponding to the affiliated store identification information, merchants Cancel registration of transaction information registered matching the identification information.

According to an additional aspect of the present invention, after the payment approval result management unit receives the payment approval result for the transaction information corresponding to the payment type of the payment provider from the payment provider server, when the specific error condition is satisfied, the payment of the payment provider is satisfied. Cancel the payment approval for the transaction information corresponding to the type.

According to an additional aspect of the present invention, the transaction brokerage server further comprises a payment provider information management unit for managing the payment provider information for processing the transaction information corresponding to the payment type of the payment provider for each payment app identification information.

According to an additional aspect of the present invention, a simple payment system that supports the payment of multiple payment providers using a single QR code transmits the transaction information registration request information including the merchant identification information and the transaction information to the transaction brokerage server transaction information The merchant further includes a merchant payment terminal for requesting registration and receiving payment approval results for transaction information corresponding to the payment type of the payment provider from the transaction brokerage server.

According to an additional aspect of the present invention, the merchant payment terminal outputs a payment receipt for the payment approval result corresponding to the transaction information corresponding to the payment type of the payment operator received from the transaction brokerage server.

According to an additional aspect of the present invention, a simple payment system that supports the payment of a plurality of payment providers using a single QR code requests the transaction brokerage server to query transaction information corresponding to the merchant identification information, and from the transaction brokerage server The mobile terminal may further include a user mobile terminal configured to receive transaction information corresponding to a payment type.

According to an additional aspect of the present invention, a user mobile terminal makes a payment request for transaction information corresponding to a payment type of a payment provider received by a payment provider server.

The present invention does not have a large number of QR codes for each payment provider in the merchant, only one single QR code, and minimize the modification of the user app to make payment of multiple payment providers by adding the connection between the transaction brokerage server and the payment provider server By supporting this, it is possible to support various types of mobile app payments by multiple payment providers without adding merchant hardware infrastructure.

In addition, the present invention has no user interface difference with the existing card payment system, does not require a direct connection between the merchant payment terminal and the user mobile terminal, can distinguish transaction information, merchant payment infrastructure that can support a variety of mobile app payments It can be easily built at low cost.

1 is a schematic diagram of a simple payment system supporting multiple payment service providers using a single QR code according to the present invention.
2 is a flowchart illustrating an embodiment of a simple payment method for supporting a plurality of payment service providers using a single QR code according to the present invention.
Figure 3 is a block diagram showing the configuration of an embodiment of a transaction intermediation server of a simple payment system that supports the payment of multiple payment providers using a single QR code according to the present invention.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily understand and reproduce. Although specific embodiments are illustrated in the drawings and related detailed description is described, it is not intended to limit the various embodiments of the present invention to a specific form.

In the following description of the present invention, when it is determined that detailed descriptions of related known functions or configurations may unnecessarily obscure the gist of the embodiments of the present invention, the detailed description thereof will be omitted.

When a component is said to be "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in the middle. Should be.

On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

1 is a schematic diagram of a simple payment system supporting multiple payment service providers using a single QR code according to the present invention. As shown in FIG. 1, a simple payment system that supports a plurality of payment provider payments using a single QR code according to this embodiment includes a transaction brokerage server 100, a payment provider server 200, and a merchant payment terminal. 300, and a user mobile terminal 400.

The transaction brokerage server 100 registers transaction information by matching the merchant identification information according to the transaction information registration request from the merchant payment terminal 300, and recognizes a single QR code including the merchant identification information. In response to the transaction information inquiry request corresponding to the affiliated store identification information from 400, a payment service provider corresponding to the payment app identification information is identified, the transaction information corresponding to the affiliated store identification information is searched, and the transaction corresponding to the retrieved merchant identification information. The information is processed into transaction information corresponding to the payment type of the identified payment provider and transmitted to the payment app executed by the user mobile terminal 400.

For example, the merchant payment terminal 300 may be a POS terminal provided in the affiliated store, a CAT terminal, a kiosk terminal for unattended payment, a software form mounted on a smartphone owned by the affiliate store, and the like.

When a customer orders a product at a merchant store, transaction information such as merchant identification information, transaction amount, and installment months are input through the merchant payment terminal 300. When the transaction information is input, the merchant payment terminal 300 transmits transaction information registration request information including transaction information such as merchant identification information, transaction amount, and installment months to the transaction intermediation server 100 to request transaction information registration. do.

Then, the transaction brokerage server 100 receiving the transaction information registration request from the merchant payment terminal 300 matches with the merchant identification information and stores the transaction information in the DB and registers it. The affiliated store identification information is information that can uniquely identify the affiliated store. For example, the affiliated store identification information may be an affiliated store ID used for the actual affiliated store settlement or may be information matched with an affiliated store ID used for the actual affiliated store settlement.

In the merchant store is provided with a single QR code that can be commonly used in the payment app of multiple payment providers. For example, a single QR code may be attached to the merchant payment terminal 300, or may be displayed through the merchant payment terminal 300 screen or a separate display.

The user who registered the transaction information recognizes a single QR code by executing a payment app through the user mobile terminal 400 owned by the user. In this case, the single QR code may include a transaction brokerage server access URL and the affiliated store identification information. In addition, it may further include version information of a single QR code.

When a single QR code is recognized through the payment app executed by the user mobile terminal 400, the payment app extracts the transaction brokerage server access URL and the affiliated store identification information from the single QR code, and then indicates that the transaction brokerage server access URL is indicated. Access the transaction brokerage server 100, and transmits the transaction information query request information including the merchant identification information and payment app identification information to the transaction brokerage server 100 to request an inquiry about the transaction information.

At this time, the payment app identification information may be unique information used for checking the payment app version of each payment provider that can be identified by the transaction brokerage server 100 without the user's separate selection or modification of the payment app, but is not limited thereto. Does not. In addition, the payment operator may pass additional information as a parameter when the transaction brokerage server 100 is connected to implement additional functions such as security.

The transaction brokerage server 100 receiving the transaction information inquiry request information including the merchant identification information and the payment app identification information identifies the payment service provider corresponding to the payment app identification information, and obtains the transaction information corresponding to the merchant identification information from the DB. By searching, the transaction information corresponding to the retrieved merchant identification information is processed into transaction information corresponding to the payment type of the identified payment operator and transmitted to the payment app executed by the user mobile terminal 400.

For example, the transaction information corresponding to the payment type of the payment operator may be URL or URL redirection information or an HTML page or a JavaScript Object Notation (JSON). To this end, the transaction brokerage server 100 stores and manages payment provider information for processing transaction information corresponding to the payment type of each payment provider in a DB for each payment app identification information in advance.

The payment service provider server 200 requests transaction information corresponding to the merchant identification information and receives transaction information corresponding to the payment type of the payment service provider from the user mobile terminal 400. In response to the payment request for the payment process, payment approval for transaction information corresponding to the payment type of the payment provider is processed, and the payment approval result is transmitted to the corresponding user mobile terminal 400 and the transaction intermediation server 100. For example, the payment provider server 200 may be a card issuer server such as a card company, a prepaid service provider, a bank, or the like.

The payment app executed by the user mobile terminal 400 that receives the transaction information corresponding to the payment type of the payment provider from the transaction brokerage server 100 is the payment information corresponding to the payment type of the payment provider to the payment provider server 200. Make a payment request by sending payment request information for.

The payment service provider server 200 receiving the payment request for the transaction information corresponding to the payment type of the payment service provider processes payment approval for the transaction information corresponding to the payment type of the payment service provider and moves the payment approval result to the corresponding user. It transmits to the terminal 400 and the transaction brokerage server 100.

Merchant payment terminal 300 receives transaction information such as merchant identification information, transaction amount, installment months, and the like, and transmits transaction information registration request information including merchant identification information and transaction information to transaction brokerage server 100. Request registration.

In addition, the merchant payment terminal 300 receives the payment approval result for the transaction information corresponding to the payment type of the payment provider from the transaction intermediation server 100, and outputs a payment receipt for the received payment approval result.

When a customer orders a product at a merchant store, transaction information such as merchant identification information, transaction amount, and installment months are input through the merchant payment terminal 300. When the transaction information is input, the merchant payment terminal 300 transmits transaction information registration request information including transaction information such as merchant identification information, merchant identification information, transaction amount, installment months, etc. to the transaction intermediation server 100. Request to register transaction information.

Then, the transaction brokerage server 100 receiving the transaction information registration request from the merchant payment terminal 300 matches the merchant identification information and registers the transaction information and stores it in the DB. When the transaction information is registered, the customer runs a payment app through the user mobile terminal 400 to recognize a single QR code.

When a single QR code including a transaction brokerage server access URL and merchant identification information is recognized, the payment app of the user mobile terminal 400 accesses the transaction brokerage server 100 indicated by the transaction brokerage server access URL, and the merchant identification information. The transaction information inquiry request information including payment app identification information is transmitted to the transaction brokerage server 100 to request an inquiry about transaction information.

Then, the transaction brokerage server 100 identifies the payment operator corresponding to the payment app identification information, retrieves the transaction information corresponding to the merchant identification information from the DB, and the payment provider identified the transaction information corresponding to the retrieved merchant identification information. Process the transaction information corresponding to the payment type of the mobile terminal 400 to be transmitted to the payment app executed by.

Then, the user mobile terminal 400 receiving the transaction information corresponding to the payment type of the payment provider requests the payment provider server 200 for payment of the transaction information corresponding to the payment type of the payment provider.

The payment service provider server 200 receiving the payment request for the transaction information corresponding to the payment type of the payment service provider processes the payment approval for the transaction information corresponding to the payment service type of the payment service provider, and deals with the user mobile terminal 400. The payment approval result is transmitted to the mediation server 100.

On the other hand, the merchant payment terminal 300 receives a payment approval result for the transaction information corresponding to the payment type of the payment provider from the transaction brokerage server 100. When the payment approval result for the transaction information corresponding to the payment type of the payment provider is received from the transaction brokerage server 100, the merchant payment terminal 300 receives the payment receipt for the payment approval result received from the transaction brokerage server 100. Output

The user mobile terminal 400 is equipped with a payment app is executed, and recognizes a single QR code including a transaction brokerage server access URL, and merchant identification information, to the transaction brokerage server 100 indicated by the transaction brokerage server access URL Access the transaction information inquiry request information including the merchant identification information and the payment app identification information to the transaction brokerage server 100 to request an inquiry about the transaction information.

Then, the transaction brokerage server 100 identifies the payment operator corresponding to the payment app identification information, retrieves the transaction information corresponding to the merchant identification information from the DB, and the payment provider identified the transaction information corresponding to the retrieved merchant identification information. Process the transaction information corresponding to the payment type of the mobile terminal 400 to be transmitted to the payment app executed by.

On the other hand, when the mobile terminal 400 receives the transaction information corresponding to the payment type of the payment provider from the transaction brokerage server 100, the payment provider server 200 to pay for the transaction information corresponding to the payment type of the payment provider Ask. At this time, the payment provider server 200 may be a card issuer server such as a card company, a prepaid service provider, a bank.

The payment service provider server 200 receiving the payment request for the transaction information corresponding to the payment type of the payment service provider processes the payment approval for the transaction information corresponding to the payment service type of the payment service provider, and deals with the user mobile terminal 400. The payment approval result is transmitted to the mediation server 100.

By implementing in this way the present invention does not have a large number of QR codes for each payment provider in the merchant, only one single QR code, and minimize the modification of the user app by adding a connection between the transaction brokerage server and the payment provider server multiple By supporting payment by payment providers, it is possible to support various types of mobile app payments by multiple payment providers without adding merchant hardware infrastructure.

In addition, the present invention has no user interface difference with the existing card payment system, does not require a direct connection between the merchant payment terminal and the user mobile terminal, can distinguish transaction information, merchant payment infrastructure that can support a variety of mobile app payments Can be easily deployed at low cost.

2 is a flowchart illustrating an embodiment of a simple payment method for supporting a plurality of payment service providers using a single QR code according to the present invention. As shown in FIG. 2, a simple payment method for supporting a plurality of payment service providers using a single QR code according to the present embodiment includes a transaction information registration step 510, a transaction information inquiry step 520, and a payment method. An approval processing step 530 and a payment approval result processing step 540 are included.

In the transaction information registration step 510, the transaction brokerage server 100 stores and registers transaction information corresponding to the affiliated store identification information according to the transaction information registration request corresponding to the affiliated store identification information from the affiliated store payment terminal 300.

When the transaction information is input, the merchant payment terminal 300 communicates with the transaction brokerage server 100, and then transmits the input transaction information to the transaction brokerage server 100 to request transaction information registration.

Then, the transaction brokerage server 100 receives the registration information by matching the merchant identification information and storing the transaction information in a DB, and transmits a response to the transaction information registration to the merchant payment terminal 300.

Then, the merchant payment terminal 300 receiving the response to the transaction information registration releases the communication connection with the transaction brokerage server 100, enters the standby mode and periodically checks the payment completion information for the registered transaction information Inquire. In this case, since the payment approval completion process for the registered transaction information does not need to be processed sequentially, the next transaction information may be registered to allow the next payment to occur.

In the transaction information inquiry step 520, according to the transaction information inquiry request corresponding to the merchant identification information from the payment app executed by the user mobile terminal 400 that recognizes a single QR code, the transaction brokerage server 100 is a payment app Identify a payment operator corresponding to the identification information, search for transaction information corresponding to the merchant identification information, process the transaction information corresponding to the searched merchant identification information into transaction information corresponding to the payment type of the identified payment operator, and move the user. Send to the payment app executed by the terminal 400.

When the transaction information corresponding to the merchant identification information is registered through the merchant payment terminal 300, the user executes a payment app through the user mobile terminal 400, and includes a single QR code including a transaction brokerage server access URL and merchant identification information. Recognize the transaction, and accesses the transaction brokerage server 100 indicated by the transaction brokerage server access URL, and transmits transaction information inquiry request information including merchant identification information and payment app identification information and requests transaction information inquiry.

Then, the transaction brokerage server 100 identifies the payment provider corresponding to the payment app identification information, retrieves the transaction information corresponding to the merchant identification information, and checks the payment information of the payment provider identified the transaction information corresponding to the searched merchant identification information. It processes the transaction information corresponding to the type and transmits the transaction information to the user mobile terminal 400 to respond to the transaction information inquiry request.

In the payment approval processing step 530, the payment request for the transaction information corresponding to the payment type of the payment provider from the payment app executed by the user mobile terminal 400 that receives the transaction information corresponding to the payment type of the payment provider. Accordingly, the payment service provider server 200 processes payment approval for transaction information corresponding to the payment type of the payment service provider.

When a payment request for transaction information corresponding to the payment type of the payment provider is transmitted from the user mobile terminal 400 that receives the transaction information corresponding to the payment type of the payment provider, the payment provider server 200 sets the payment type of the payment provider. Process the payment approval for the transaction information corresponding to the, and transmits the payment approval result to the user mobile terminal 400 to respond to the payment request. At this time, it may be implemented to process the payment approval for the transaction information corresponding to the payment type of the payment provider only when the user is authenticated through user authentication.

In the payment approval result processing step 540, the payment service provider server 200 that has processed payment approval for transaction information corresponding to the payment type of the payment service provider transmits the payment approval result to the transaction brokerage server 100.

Meanwhile, in the payment approval result processing step 540, the transaction brokerage server 100 mediates the payment approval result for the transaction information corresponding to the payment type of the payment provider to the merchant payment terminal 300, The merchant payment terminal 300 receiving the corresponding transaction information outputs a payment receipt corresponding to the received payment approval result.

When the payment approval result for the transaction information corresponding to the payment type of the payment provider is transmitted from the payment provider server 200 that has processed payment approval for the transaction information corresponding to the payment type of the payment provider, the transaction intermediation server 100 The payment approval result for the transaction information corresponding to the payment type of the payment operator is transmitted to the merchant payment terminal 300, and the merchant payment terminal 300 receiving the payment approval for the transaction information corresponding to the payment type of the payment provider is approved. Print the payment receipt corresponding to the result. The printed payment receipt is delivered to the user.

Payment completion processing for the transaction information registered in the present invention may proceed regardless of the transaction information registration order. Therefore, the next payment can be made without waiting for the transaction to be completed, and the existing credit card can be used as the next payment type.

By implementing in this way the present invention does not have a large number of QR codes for each payment provider in the merchant, only one single QR code, and minimize the modification of the user app by adding a connection between the transaction brokerage server and the payment provider server multiple By supporting payment by payment providers, it is possible to support various types of mobile app payments by multiple payment providers without adding merchant hardware infrastructure.

In addition, the present invention has no user interface difference with the existing card payment system, does not require a direct connection between the merchant payment terminal and the user mobile terminal, can distinguish transaction information, merchant payment infrastructure that can support a variety of mobile app payments Can be easily deployed at low cost.

Figure 3 is a block diagram showing the configuration of an embodiment of a transaction intermediation server of a simple payment system that supports the payment of multiple payment providers using a single QR code according to the present invention. As shown in FIG. 3, the transaction brokerage server 100 according to the present embodiment may include a transaction information register 110, a transaction information search unit 120, a settlement approval result management unit 130, and a settlement approval result search. The unit 140 is included.

The transaction information registration unit 110 stores and registers transaction information corresponding to the affiliated store identification information in a DB according to the transaction information registration request corresponding to the affiliated store identification information from the affiliated store payment terminal 300. For example, the merchant payment terminal 300 may be a POS terminal provided in the affiliated store, a CAT terminal, a kiosk terminal for unattended payment, a software form mounted on a smartphone owned by the affiliate store, and the like.

When a customer orders a product at a merchant store, transaction information such as merchant identification information, transaction amount, and installment months are input through the merchant payment terminal 300. When the transaction information is input, the merchant payment terminal 300 transmits transaction information registration request information including transaction information such as merchant identification information, merchant identification information, transaction amount, installment months, etc. to the transaction intermediation server 100. Request to register transaction information.

Then, the transaction brokerage server 100 receiving the transaction information registration request from the merchant payment terminal 300 matches with the merchant identification information through the transaction information registration unit 110 to store and register the transaction information in the DB. The affiliated store identification information is information that can uniquely identify the affiliated store. For example, the affiliated store identification information may be an affiliated store ID used for the actual affiliated store settlement or may be information matched with an affiliated store ID used for the actual affiliated store settlement.

When the transaction information requested by the merchant payment terminal 300 is registered in the transaction brokerage server 100 by matching with the merchant identification information, the merchant payment terminal 300 receiving the response to the transaction information registration is the transaction broker server 100. After the communication connection with the service is released, the user enters the standby mode and periodically checks the payment completion information on the registered transaction information. In this case, since the payment approval completion process for the registered transaction information does not need to be processed sequentially, the next transaction information may be registered to allow the next payment to occur.

The transaction information search unit 120 identifies the payment app according to the transaction information inquiry request corresponding to the merchant identification information from the payment app executed by the user mobile terminal 400 that recognizes a single QR code including the affiliate store identification information. Identify a payment operator corresponding to the information, search for transaction information corresponding to the merchant identification information, process the transaction information corresponding to the searched merchant identification information into transaction information corresponding to the payment type of the identified payment operator, and the user mobile terminal. Send to the payment app executed by 400.

The merchant store has a single QR code including a transaction brokerage server access URL, and merchant identification information, and the user executes a payment app through the user mobile terminal 400 to recognize a single QR code.

When the payment app of the user mobile terminal 400 recognizes a single QR code including a transaction brokerage server access URL and affiliated store identification information, accesses the transaction brokerage server 100 indicated by the transaction brokerage server access URL to identify a merchant. Request transaction information inquiry by transmitting transaction information inquiry request information including information and payment app identification information.

In this case, the payment app identification information may be unique information used for checking the payment app version of each payment provider that can be identified by the transaction brokerage server 100 without a user's separate selection, but is not limited thereto.

Then, the transaction brokerage server 100 identifies the payment operator corresponding to the payment app identification information through the transaction information search unit 120, retrieves the transaction information corresponding to the merchant identification information from the DB, and retrieves the searched merchant identification information. The corresponding transaction information is processed into transaction information corresponding to the payment type of the identified payment provider and transmitted to the payment app executed by the user mobile terminal 400, and the user mobile terminal 400 receiving the received transaction information includes a payment provider server ( 200) request payment for transaction information corresponding to the payment type of the payment operator.

For example, the transaction information corresponding to the payment type of the payment operator may be URL or URL redirection information, an HTML page, or a JavaScript Object Notation (JSON). To this end, the transaction brokerage server 100 previously stores payment provider information for processing transaction information corresponding to the payment type of each payment provider in the DB for each payment app identification information.

The payment approval result management unit 130 receives the payment approval result for the transaction information corresponding to the payment type of the payment provider from the payment provider server 200 that has processed payment approval for the transaction information corresponding to the payment type of the payment provider. The received payment approval result is stored in the DB.

The user mobile terminal 400 that receives the transaction information corresponding to the payment type of the payment provider by requesting the transaction information inquiry corresponding to the merchant identification information from the transaction brokerage server 100, the payment provider payments to the payment provider server 200. When requesting payment for transaction information corresponding to a type, the payment provider server 200 processes payment approval for transaction information corresponding to the payment type of the payment provider, and for the transaction information corresponding to the payment type of the payment provider. The payment approval result is transmitted to the user mobile terminal 400 and the transaction brokerage server 100.

The transaction intermediation server 100 receiving the payment approval result for the transaction information corresponding to the payment type of the payment provider from the payment provider server 200, the transaction corresponding to the payment type of the payment provider through the payment approval result management unit 130. The payment approval result for the information is stored in the DB.

The payment approval result search unit 140 retrieves the payment approval result for the transaction information corresponding to the payment type of the payment provider from the DB, and checks the payment approval result for the transaction information corresponding to the payment type of the searched payment provider. Send to 300.

When the payment approval result for the transaction information corresponding to the payment type of the payment provider is stored in the DB through the payment approval result management unit 130 of the transaction intermediation server 100, the payment approval result search unit 140 is the payment provider from the DB. Search for the payment approval result for the transaction information corresponding to the payment type of, and broker the payment approval result for the transaction information corresponding to the payment type of the searched payment provider to the merchant payment terminal 300.

At this time, transaction information registration and single QR code recognition should be performed sequentially, but since payment for sequentially registered transaction information may be performed regardless of the order of transaction information registration, transaction information corresponding to the payment type of the payment provider is applied. Mediation of the settlement approval result may also be made regardless of the transaction information registration order.

The merchant payment terminal 300 receiving the payment approval result for the transaction information corresponding to the payment type of the payment provider from the transaction intermediation server 100 pays for the payment approval result for the transaction information corresponding to the payment type of the payment provider. Print a receipt. The printed payment receipt is delivered to the user.

By implementing in this way the present invention does not have a large number of QR codes for each payment provider in the merchant, only one single QR code, and minimize the modification of the user app by adding a connection between the transaction brokerage server and the payment provider server multiple By supporting payment by payment providers, it is possible to support various types of mobile app payments by multiple payment providers without adding merchant hardware infrastructure.

In addition, the present invention does not have a user interface difference with the existing card payment system, does not need a direct connection between the merchant payment terminal and the user mobile terminal, it is possible to distinguish transaction information, merchant payment infrastructure that can support a variety of mobile app payments Can be easily deployed at low cost.

On the other hand, according to an additional aspect of the invention, the transaction brokerage server 100 may further include a payment status information changing unit 150. When the transaction information is registered by the transaction information registration unit 110, the payment state information changing unit 150 changes the payment state information corresponding to the merchant identification information matched with the transaction information to the transaction registration state. Payment status information corresponding to the merchant identification information may be stored and managed in the DB.

When the payment status information corresponding to the affiliated store identification information matched with the transaction information registered by the payment status information changing unit 150 becomes a transaction registration state, the transaction intermediation server 100 recognizes a single QR code for a user mobile terminal ( Wait for the inquiry request for the registered transaction information from the payment app executed by 400).

On the other hand, according to an additional aspect of the invention, if the transaction information corresponding to the payment type of the payment provider 150 is transmitted to the user mobile terminal 400, the transaction corresponding to the payment type of the payment provider The payment status information corresponding to the information is changed to the payment standby state, and the payment status information corresponding to the affiliated store identification information is changed to the transaction waiting state so that another transaction information registration is possible.

In order to allow the payment approval completion process for the transaction information to proceed regardless of the transaction information registration order, the present invention provides a payment state information corresponding to the merchant identification information, and a payment state corresponding to the transaction information corresponding to the payment type of the payment provider. The information is dualized and managed separately.

The payment status information corresponding to the merchant identification information may be one of a transaction registration status or a transaction waiting status, and the payment status information corresponding to transaction information corresponding to a payment type of a payment provider is one of a payment waiting status or a payment completion status. Can be.

If the payment status information corresponding to the transaction information corresponding to the payment type of the payment provider is changed to the payment waiting status by the payment status information changing unit 150 and the payment status information corresponding to the merchant identification information is changed to the transaction waiting status, Another transaction information can be registered regardless of payment approval for transaction information corresponding to the payment type of the payment provider, so payment approval processing for registered transaction information and new transaction information registration processing are performed separately regardless of the order. Will be.

On the other hand, according to an additional aspect of the invention, if the payment status information change unit 150 is the payment approval result for the transaction information corresponding to the payment type of the payment provider is transmitted to the merchant payment terminal 300 corresponding to the merchant identification information. The payment status information corresponding to the transaction information corresponding to the payment type of the payment provider is changed to the payment completion state, and the payment operation for the transaction information corresponding to the payment type of the payment provider is completed.

On the other hand, according to an additional aspect of the invention, the transaction information search unit 120 transactions corresponding to the merchant identification information from the user mobile terminal 400 for a specific time in the transaction registration state of the payment status information corresponding to the merchant identification information If there is no information inquiry request, it may be implemented to cancel the registration for the registered transaction information matching the merchant identification information.

That is, in this embodiment, if there is no inquiry request for transaction information corresponding to the registered affiliated store identification information for a specific time while the transaction information corresponding to the affiliated store identification information is registered, the transaction registered by matching with the affiliated store identification information The embodiment is to cancel the registration of the registered transaction information by determining that there is no intention to pay for the information.

On the other hand, according to an additional aspect of the invention, if the payment approval result management unit 130 receives the payment approval result for the transaction information corresponding to the payment type of the payment provider from the payment provider server, and satisfies a specific error condition The payment approval for transaction information corresponding to the payment type of the payment provider may be implemented.

That is, this embodiment may solve the payment error problem by automatically canceling the payment approval when a certain error condition such as a communication error is received after the payment approval result for the transaction information corresponding to the payment type of the payment operator is received. It would be.

On the other hand, according to an additional aspect of the invention, the transaction brokerage server 100 may further include a payment provider information management unit 160. The payment provider information manager 160 manages payment provider information for processing transaction information corresponding to the payment type of the payment provider for each payment app identification information.

For example, the transaction information corresponding to the payment type of the payment operator may be URL or URL redirection information, an HTML page, or a JavaScript Object Notation (JSON).

The payment provider information management unit 160 may receive payment provider information for processing transaction information corresponding to the payment type of each payment provider from each payment provider server 200 and store and manage the information in a DB.

Payment provider information for processing transaction information corresponding to the payment type of each payment provider stored in the DB payment app identification information according to the transaction information query request, including merchant identification information and payment app identification information from the user mobile terminal 400 It may be referred to when identifying the payment operator corresponding to the.

As described above, the present invention does not have a large number of QR codes for each payment provider in the merchant, only one single QR code, and minimize the modification of the user app by adding a connection between the transaction brokerage server and the payment provider server By supporting payment providers' payments, it is possible to support various types of mobile app payments by multiple payment providers without adding merchant hardware infrastructure.

In addition, the present invention has no user interface difference with the existing card payment system, does not require a direct connection between the merchant payment terminal and the user mobile terminal, can distinguish transaction information, merchant payment infrastructure that can support a variety of mobile app payments Can be easily deployed at low cost.

The various embodiments disclosed in the specification and drawings are merely presented as specific examples for clarity and are not intended to limit the scope of the various embodiments of the present invention.

Accordingly, the scope of various embodiments of the present invention includes all changes or modifications derived based on the technical spirit of the various embodiments of the present invention in addition to the embodiments described herein are included in the scope of the various embodiments of the present invention. Should be interpreted as

The present invention can be used industrially in the QR code-based payment technology field and its application field.

100: trading brokerage server
110: transaction information register
120: transaction information search unit
130: payment approval result management unit
140: payment approval result search unit
150: change of payment status information
160: payment provider information management unit
200: payment provider server
300: merchant payment terminal
400: user mobile terminal

Claims (15)

A transaction information registration step of storing and registering transaction information corresponding to the affiliated store identification information by the transaction brokerage server according to the transaction information registration request corresponding to the affiliated store identification information from the affiliated store payment terminal;
According to the transaction information inquiry request corresponding to the merchant identification information from the payment app executed by the user mobile terminal that recognizes a single QR code, the transaction brokerage server identifies the payment provider corresponding to the payment app identification information, and identifies the merchant identification information. Search transaction information corresponding to the transaction information processing step of processing the transaction information corresponding to the searched merchant identification information to the transaction information corresponding to the payment type of the identified payment provider and transmits to the payment app executed by the user mobile terminal Wow;
In response to a payment request for the transaction information corresponding to the payment type of the payment provider from the payment app executed by the user mobile terminal receiving the transaction information corresponding to the payment type of the payment provider, the payment provider server causes the payment provider server to settle the payment type. A payment approval processing step of processing payment approval for transaction information corresponding to the;
A payment approval result processing step of transmitting, by the payment service provider server that has processed payment approval for transaction information corresponding to the payment type of the payment service provider, to the transaction intermediation server;
Easy payment method that supports the payment of multiple payment providers using a single QR code to include. The method of claim 1,
During the payment authorization process:
Simple payment method that supports the payment of multiple payment providers using a single QR code to broker the payment results for the transaction information corresponding to the payment type of the payment provider to the merchant payment terminal. The method of claim 2,
During the payment authorization process:
Simple payment method that supports the payment of multiple payment providers using a single QR code that outputs a payment receipt corresponding to the payment approval result received by the merchant payment terminal receiving the transaction information corresponding to the payment type of the payment provider. A transaction information registration unit for storing and registering transaction information corresponding to the affiliated store identification information in a DB according to a transaction information registration request corresponding to the affiliated store identification information from the affiliated store payment terminal;
According to the transaction information inquiry request corresponding to the merchant identification information from the payment app executed by the user mobile terminal that recognizes a single QR code including the merchant identification information, the payment service provider corresponding to the payment app identification information is identified, and the merchant Transaction information corresponding to the identification information is searched, transaction information corresponding to the searched merchant identification information is processed into transaction information corresponding to the payment type of the identified payment provider, and transaction information transmitted to the payment app executed by the user mobile terminal. A search unit;
Receiving the payment approval result for the transaction information corresponding to the payment type of the payment provider from the payment provider server that processed the payment approval for the transaction information corresponding to the payment type of the payment provider, and stores the received payment approval result in the DB. Payment approval result management unit;
A payment approval result retrieval unit for retrieving payment approval results for transaction information corresponding to the payment type of the payment provider from the DB, and transmitting the payment approval result for the transaction information corresponding to the payment type of the searched payment provider to the merchant payment terminal;
Simple payment system that supports the payment of multiple payment providers using a single QR code that includes a transaction brokering server. The method of claim 4, wherein
A simple payment system that supports multiple payment providers using a single QR code:
In accordance with the payment request for the transaction information corresponding to the payment type of the payment provider from the user mobile terminal, the payment approval for the transaction information corresponding to the payment type of the payment provider is processed, and the payment approval result is displayed. A payment provider server for transmitting to the transaction brokerage server;
Simple payment system that supports the payment of multiple payment providers using a single QR code that includes more. The method of claim 4, wherein
Trading broker server:
If the transaction information is registered by the transaction information registration unit, the payment status information changing unit for changing the payment status information corresponding to the merchant identification information matched with the transaction information to the transaction registration state;
Simple payment system that supports the payment of multiple payment providers using a single QR code that includes more. The method of claim 6,
Change payment status information:
When the transaction information corresponding to the payment type of the payment provider is transmitted to the user mobile terminal, the payment status information corresponding to the transaction information corresponding to the payment type of the payment provider is changed to the payment standby state and the payment corresponding to the merchant identification information. Simple payment system that supports the payment of multiple payment providers using a single QR code to change the status information to the transaction waiting state to enable registration of another transaction information. The method of claim 7, wherein
Change payment status information:
When the payment approval result of the transaction information corresponding to the payment type of the payment provider is transmitted to the merchant payment terminal corresponding to the merchant identification information, the payment status information corresponding to the transaction information corresponding to the payment type of the payment provider is completed. Easy payment system that supports the payment of multiple payment providers using a single QR code to change to. The method of claim 6,
Transaction Information Search Department:
If the payment status information corresponding to the merchant identification information does not have a transaction information inquiry request corresponding to the merchant identification information from the user mobile terminal for a specific time in the transaction registration state, registration of the registered transaction information is matched with the merchant identification information. Easy payment system that supports multiple payment providers payment using a single QR code to cancel. The method of claim 4, wherein
Payment approval result management department:
After receiving the payment approval result for the transaction information corresponding to the payment type of the payment provider from the payment provider server, if a specific error condition is satisfied, the single payment is canceled for the transaction information corresponding to the payment type of the payment provider. Easy payment system that supports the payment of multiple payment providers using a QR code. The method of claim 4, wherein
Trading broker server:
A payment provider information manager configured to manage payment provider information for processing transaction information corresponding to the payment type of the payment provider for each payment app identification information;
Simple payment system that supports the payment of multiple payment providers using a single QR code that includes more. The method according to any one of claims 4 to 11,
A simple payment system that supports multiple payment providers using a single QR code:
Sending transaction information registration request information including merchant identification information and transaction information to the transaction brokerage server to request transaction information registration, and receiving payment approval results for transaction information corresponding to the payment type of the payment provider from the transaction brokerage server. Merchant payment terminal;
Simple payment system that supports the payment of multiple payment providers using a single QR code that includes more. The method of claim 12,
Merchant payment terminal:
Simple payment system that supports the payment of multiple payment providers using a single QR code to output the payment receipt for the payment approval result corresponding to the transaction information corresponding to the payment type of the payment provider received from the transaction brokerage server. The method according to any one of claims 4 to 11,
A simple payment system that supports multiple payment providers using a single QR code:
A user mobile terminal for requesting transaction information inquiry request corresponding to the merchant identification information to the transaction brokerage server and receiving transaction information corresponding to the payment type of the payment operator from the transaction brokerage server;
Simple payment system that supports the payment of multiple payment providers using a single QR code that includes more. The method of claim 14,
User mobile terminal:
Simple payment system that supports the payment of multiple payment providers using a single QR code to request payment for transaction information corresponding to the payment type of the payment provider received by the payment provider server.

Images