KR102418755B1 - Server and method for relaying payment, payment processing system comprising server - Google Patents

Abstract

According to an embodiment of the present document, a server comprises: a communication unit for receiving recognition information including payment service identification information from a user terminal; a determination unit for determining a payment relay method set in correspondence with a payment service by using the payment service identification information; and a processing unit for relaying payment processing of the user terminal according to the determined payment relay method.

Description

Server and payment relay method thereof, payment processing system including server

Embodiments disclosed in this document relate to a server, its payment relay method, and a payment processing system including the server.

With the development of IT technology and the spread of smart phones, various simple payment services are being developed that break away from traditional payment methods such as cash payment and card payment. As such simple payment services, there are various payment services such as Kakao pay and WeChat pay using a smart phone, and various other simple payment services are explosively increasing.

However, a store that provides a simple payment service has the inconvenience of having to provide a QR code for payment for each simple payment service. In addition, since the general payment QR code includes only the store's affiliate information, the user must input the payment amount at the time of payment.

An object of the embodiments disclosed in this document is to provide a server capable of providing a simple payment service with improved user convenience and security, a payment relay method thereof, and a payment processing system including the server.

Technical problems of the embodiments disclosed in this document are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

The server according to an embodiment disclosed in this document is a communication unit that receives recognition information including payment service identification information from a user terminal, and a determination to determine a payment relay method set in response to the payment service using the payment service identification information and a processing unit that relays the payment processing of the user terminal according to the determined payment relay method.

In an embodiment, the determination unit may determine a payment relay method set in response to the payment service by comparing the payment service identification information with a database storing payment relay method information for each payment company.

In an embodiment, the recognition information may further include user information of the user terminal, affiliate store information of a store where the user intends to pay, and payment amount information.

In one embodiment, when the processing unit determines that the payment relay method is the first method, a payment page for processing the payment of the user terminal through the server and a first authentication value for authentication of the payment page to the user It can be provided to the terminal.

In an embodiment, the processing unit receives payment request information corresponding to the payment page from the user terminal, and the payment request information includes user information of the user terminal, merchant information of a store where the user wants to pay, and payment amount. information and a second authentication value.

In an embodiment, the processing unit may verify the payment request information by comparing the payment request information with the recognition information and the first authentication value.

In an embodiment, the processing unit transmits a payment approval request to a payment company server corresponding to the payment service identification information based on the result of the verification, and when receiving payment approval information from the payment company server, the user terminal and A payment approval result may be provided to a store terminal of a store where the user intends to pay.

In an embodiment, the recognition information may further include information about an affiliated store and payment amount information of a store to which the user intends to pay.

In an embodiment, when the payment relay method is determined as the second method, the processing unit may transmit driving request information for requesting to run a payment service application corresponding to the payment service identification information to the user terminal.

In an embodiment, the driving request information may include the payment amount information and subscription information of the store on the payment service.

In an embodiment, the processing unit may obtain, from a pre-stored database, subscription information of the store on the payment service corresponding to the affiliate store information of the store.

In an embodiment, the processing unit may verify whether the store is a previously registered affiliate store based on the affiliate store information included in the recognition information.

In an embodiment, the recognition information may be generated when a payment service application executed in the user terminal recognizes a payment code of the store, and the communication unit may receive the recognition information from the payment service application.

In an embodiment, the payment code may include a QR code generated including the affiliate store information and the payment amount information.

A payment relay method of a server according to an embodiment disclosed in this document includes receiving recognition information including payment service identification information from a user terminal, and a payment relay method set in response to the payment service by using the payment service identification information and relaying the payment processing of the user terminal according to the determined payment relay method.

The payment processing system according to an embodiment disclosed in this document includes a store terminal generating a payment code including affiliate store information and payment amount information, and payment service identification information by recognizing the payment code, the affiliate store information, and payment amount information and a user terminal that transmits the recognition information to the management server, and the payment service identification information to determine a payment relay method set in response to the payment service, and according to the determined payment relay method It may include a management server that relays the payment processing of the user terminal.

In an embodiment, the management server may determine a payment relay method set in response to the payment service by comparing the payment service identification information with a database storing payment relay method information for each payment company.

In an embodiment, the method may further include a payment company server for processing a payment approval request transmitted from the user terminal or the management server, wherein the payment company server may be a payment company server corresponding to the payment service identification information.

In an embodiment, the recognition information may further include user information of the user terminal.

In an embodiment, when the management server determines that the payment relay method is the first method, a payment page for processing the payment of the user terminal through the management server and a first authentication value for authentication of the payment page It can be provided to the user terminal.

In an embodiment, the management server receives payment request information corresponding to the payment page from the user terminal, and the payment request information includes user information of the user terminal, merchant information of a store where the user wants to pay, and payment. It may include amount information and a second authentication value.

In an embodiment, the management server may verify the payment request information by comparing the payment request information with the recognition information and the first authentication value.

In one embodiment, the management server transmits a payment approval request to the payment company server based on a result of the verification, and when receiving payment approval information from the payment company server, payment approval to the user terminal and the store terminal can provide results.

In an embodiment, when the payment relay method is determined as the second method, the management server may transmit driving request information for requesting to run a payment service application corresponding to the payment service identification information to the user terminal.

In an embodiment, the driving request information may include the payment amount information and subscription information of the store on the payment service.

In an embodiment, the management server may acquire, from a pre-stored database, subscription information of the store on the payment service corresponding to the affiliate store information of the store.

The server, its payment relay method, and the payment processing system including the server according to an embodiment disclosed in this document perform payment to the user through the integrated payment code without the need to generate or arrange a separate QR code for each simple payment service. can be processed

The server, its payment relay method, and the payment processing system including the server according to an embodiment disclosed in this document reduce the cost and effort caused by newly creating or disposing a payment code whenever a simple payment service is newly added. can be reduced

The server, its payment relay method, and the payment processing system including the server according to an embodiment disclosed in this document may be generated by erroneous input of a payment amount to a user terminal when a user performs a payment using a simple payment service. Payment accidents can be prevented.

A server, a payment relay method thereof, and a payment processing system including the server according to an embodiment disclosed in this document can provide a payment service with improved security.

1 shows a payment processing system according to an embodiment disclosed in this document.
2 to 5 are diagrams for explaining the operation of the payment processing system according to an embodiment disclosed in this document.
6 is a block diagram illustrating a management server according to an embodiment disclosed in this document.
7 is a diagram for explaining an operation of a management server according to an embodiment disclosed in this document.
8 is a flowchart illustrating a method of operating a management server according to an embodiment disclosed in this document.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, in describing the embodiment of the present invention, if it is determined that a detailed description of a related known configuration or function interferes with the understanding of the embodiment of the present invention, the detailed description thereof will be omitted.

In describing the components of the embodiment of the present invention, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are only for distinguishing the elements from other elements, and the essence, order, or order of the elements are not limited by the terms. In addition, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

1 shows a payment processing system according to an embodiment disclosed in this document.

Referring to FIG. 1 , the payment processing system 100 according to an embodiment disclosed in this document may include a store terminal 110 , a user terminal 120 , a management server 130 , and a payment company server 140 . can

The store terminal 110 may be an electronic device for processing payment for users who purchase or use goods or services provided by the store. For example, the store terminal 110 may process payment according to a payment method selected by the user. Here, the payment method may include a payment method such as card payment, cash payment, electronic money, and the like, and a payment method using a simple payment service. In one aspect, the simple payment service may refer to a service in which a user pays using a simple payment application installed in the user terminal 120 . Hereinafter, it is assumed that the user selects a payment method using the simple payment service.

For example, after the user purchases or uses goods or services in a store, the user proceeds with payment at the store terminal 110. When a simple payment service is selected as the payment method, the store terminal 110 provides merchant information and payment amount. You can create a payment code that includes the information. Here, the affiliate store information may refer to information that the store terminal 110 or the store subscribes to the service provided by the management server 130 as an affiliate store, and the store terminal 110 or the store provides a simple payment service. It can be distinguished from subscription information, which is information subscribed to the server 140 as an affiliated store.

The store terminal 110 may generate a payment code in real time whenever payment is made. The store terminal 110 may generate one payment code regardless of the type of the simple payment service used by the user. For example, the payment code may include a QR code. To this end, the store terminal 110 may be provided with a QR code generating module. For example, the QR code generating module may be provided inside the store terminal 110 or may be provided outside the store terminal 110 as a separate physical module electrically connected to the store terminal 110 . .

According to an embodiment, the store manager inputs a payment amount corresponding to the user's usage amount into the store terminal 110 , thereby generating a payment code including information about the affiliated store of the store and the payment amount. Accordingly, the store manager can prevent a payment accident that may occur due to an erroneous input of a payment amount to the user terminal 120 when the user performs payment using the simple payment service.

On the other hand, the QR code may be pre-generated and printed to include affiliate store information, and may be placed in a store in the form of a real thing.

As described above, the store terminal 110 does not require generating or arranging payment codes for each simple payment service, and regardless of the type of simple payment service used by the user, the store terminal 110 provides the user with one payment code as described above. payment can be processed. Accordingly, the inconvenience and hassle of the store manager can be eliminated, and the cost and trouble caused by newly generating or arranging a payment code whenever a simple payment service is newly added can also be eliminated. In this respect, the above payment code may be understood as an integrated payment code.

The user terminal 120 may be an electronic device used by a user for payment. For example, when a user wants to make a payment at a store, the user can execute a simple payment application (eg, Kakao Pay, WeChat Pay, etc.) installed on the user terminal 120 and proceed with the payment according to the payment method using the simple payment service. have.

To this end, the user may execute the simple payment application in the user terminal 120 to subscribe to the simple payment service and register user information. For example, the user may register user information such as user identification information and payment registration information in the simple payment application. Here, the user identification information may include various information that can identify the user, such as the user's mobile phone number, the user's ID and/or password, and the user's name. The payment registration information may include card information and/or account information used for payment processing.

The user may recognize the payment code by executing the simple payment application of the user terminal 120 . When the simple payment application recognizes the payment code, recognition information including payment service identification information, affiliate store information, and payment amount information may be generated. That is, the simple payment application may be designed or defined to generate recognition information when a payment code is recognized.

Here, the payment service identification information may be information indicating the type of the simple payment application recognizing the payment code, for example, "User-Agent:Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1 .15 (KHTML, like Gecko) Mobile/15E148 XXX)". Accordingly, the management server 130 may identify which simple payment application the user is using through specific information (eg, "XXX") of the payment service identification information included in the recognition information.

Meanwhile, according to a payment relay method to be described later, the recognition information may further include user information of the user terminal 110 , that is, user information of a user who uses a simple payment application.

The user terminal 120 may transmit the generated recognition information to the management server 130 . For example, the user terminal 120 may transmit recognition information to the management server 130 according to a URL call method. According to an embodiment, the user terminal 120 may transmit authentication information together with the recognition information to the management server 130 . For example, the authentication information may be information generated according to an encryption algorithm promised in advance between the management server 130 and the simple payment application.

According to an embodiment, the user terminal 120 may include a mobile communication terminal, a personal digital assistant (PDA), an electronic organizer, a smart phone, a tablet personal computer (PC), and the like.

The management server 130 may relay the payment processing of the user terminal 120 based on the recognition information received from the user terminal 120 . Specifically, the management server 130 determines the payment relay method set in response to the payment service based on the payment service identification information received from the user terminal 120, and the user terminal 120 according to the determined payment relay method. Payment processing can be relayed. The management server 130 may store the recognition information received from the user terminal 120 in the database DB. This is to verify payment request information received from the user terminal 120 later.

For example, the management server 130 may determine the payment relay method as the first method or the second method using the payment service identification information received from the user terminal 120 . Here, the first method may include a server relay method, and the second method may include an application relay method. For example, the server relay method may be defined as a method of proceeding with payment processing of the user terminal 120 through a payment page provided by the management server 130 , and the application relay method is executed in the user terminal 120 and It can be defined as a method of proceeding with payment processing of the user terminal 120 through the simple payment application. According to an embodiment, the management server 130 may determine the payment relay method set in response to the payment service by comparing the payment service identification information with the database DB storing the payment relay method information for each payment company.

Hereinafter, a case in which the management server 130 determines the payment relay method as the first method will be described.

The management server 130 may receive recognition information including payment service identification information, affiliate store information, payment amount information, and user information from the user terminal 120 . The management server 130 may determine the payment relay method as the first method based on the payment service identification information. When it is determined that the payment relay method is the first method, the management server 130 may provide a payment page and a first authentication value for authentication of the payment page to the user terminal 120 . For example, the first authentication value may be defined as a hash value of specific information (eg, payment amount information) included in the payment page.

The user may request payment to the management server 130 by checking payment amount information and affiliate store information displayed on the payment page provided to the user terminal 120 . According to an embodiment, the user may request payment by inputting a soft button such as “request payment” on the payment page. For example, when the user inputs a payment request button, the user terminal 120 may transmit payment request information to the management server 130 . The payment request information transmitted from the user terminal 120 to the management server 130 may include user information of the user terminal 120 , affiliate store information, payment amount information, and a second authentication value.

The management server 130 may verify the payment request information by comparing the payment request information with the recognition information and the first authentication value. For example, the management server 130 verifies the payment request information by comparing the user information, the affiliated store information, and the payment amount information included in the recognition information, respectively, the user information, the affiliated store information, and the payment amount information included in the payment request information. can Also, the management server 130 may verify the payment request information by comparing the first authentication value with the second authentication value included in the payment request information. This is to enhance security in the payment process by verifying whether the payment request received by the management server 130 is a payment request received from the user terminal 120 that has transmitted recognition information.

The management server 130 may transmit a payment approval request to the payment company server 140 based on the verification result of the payment request information. For example, when the verification result for the payment request information is verification success, the management server 130 may transmit the payment approval request to the payment company server 140 . The management server 130 may receive a payment approval result from the payment company server 140 in response to the payment approval request. When receiving the payment approval result from the payment company server 140 , the management server 130 may transmit the payment approval result to the store terminal 110 and the user terminal 120 . Also, the payment company server 140 may transmit the payment approval result to the user terminal 120 or a simple payment application running in the user terminal 120 .

Hereinafter, a case in which the management server 130 determines the payment relay method as the second method will be described.

The management server 130 may receive recognition information including payment service identification information, affiliate store information, and payment amount information from the user terminal 120 . The management server 130 may determine the payment relay method as the second method based on the payment service identification information. When the payment relay method is determined as the second method, the management server 130 may verify whether affiliate store information included in the recognition information matches affiliate store information previously registered in the database DB. When it is determined that the payment relay method is the second method, the management server 130 may transmit driving request information for requesting the operation of the simple payment application corresponding to the payment service identification information to the user terminal 120 .

For example, the driving request information may include payment amount information and subscription information of a store or store terminal 110 on a payment service. That is, the driving request information may include subscription information signed by the store or the store terminal 110 as an affiliate store of the simple payment service provided by the payment company server 140 . To this end, the management server 130 may acquire subscription information corresponding to affiliate store information of a store or store terminal 110 using a pre-stored database DB.

The user terminal 120 may provide a payment page of the simple payment application to the user in response to the driving request information. Specifically, the user terminal 120 may call or execute the payment page of the simple payment application in response to the driving request information. The user may check payment amount information and affiliate store information displayed on the payment page of the simple payment application displayed on the user terminal 120 , and request payment from the payment company server 140 .

According to an embodiment, the user may perform user authentication required by the simple payment application or payment company server 140 and request payment from the payment company server 140 . According to an embodiment, the user may request payment by inputting a soft button such as “request payment” on the payment page. For example, when the user inputs a payment request button, the user terminal 120 may transmit a payment approval request to the payment company server 140 . For example, the payment approval request may include payment amount information, subscription information, user information, and the like.

The payment company server 140 may process a payment approval request. For example, the payment company server 140 may process a payment using the information included in the payment approval request, and transmit the payment approval result to the user terminal 120 and the management server 130 . The management server 130 may transmit the payment approval result to the store terminal 110 .

As described above, the management server 130 of the payment processing system 100 according to an embodiment disclosed in this document uses the payment service identification information received from the user terminal 120 to determine a corresponding payment relay method and , the payment processing of the user terminal 120 may be relayed according to the first method or the second method negotiated in advance with the payment company that provides the simple payment service, and the payment service identification information is the payment service identification information of the user terminal 120 . It may be generated by recognizing the integrated payment code (ie, integrated QR code) displayed on the store terminal 110 or placed in the store through the payment application.

Therefore, the store does not need to generate or arrange a separate QR code for each simple payment service, the store terminal 110 does not need to generate or arrange a payment code for each simple payment service, and the type of simple payment service used by the user Regardless, payment for users can be processed through the integrated payment code. Accordingly, the inconvenience and hassle of the store manager can be eliminated, and the cost and trouble caused by newly generating or arranging a payment code whenever a simple payment service is newly added can also be eliminated.

2 to 5 are diagrams for explaining the operation of the payment processing system according to an embodiment disclosed in this document.

Referring to FIG. 2 , when the store terminal 110 generates a payment code and the management server 130 determines the payment relay method as the first method, the store terminal 110, the user terminal 120, and the management server ( 130) and the operation of the payment company server 140 are shown.

For convenience of description, it is assumed that the user of the user terminal 120 proceeds with payment using the simple payment service in the store where the store terminal 110 is installed.

First, the store terminal 110 may generate a payment code including affiliate store information and payment amount information (S11). For example, the store terminal 110 may generate one payment code regardless of the type of the simple payment service used by the user. For example, the payment code may include a QR code. To this end, the store terminal 110 may be provided with a QR code generating module. For example, by inputting a payment amount corresponding to the user's usage amount to the store terminal 110 , the store manager may generate a payment code including affiliate store information and the payment amount of the store.

The user may recognize the payment code by executing the simple payment application of the user terminal 120 (S12). When the simple payment application recognizes the payment code, recognition information including user information, payment service identification information, affiliate store information, and payment amount information may be generated.

The user terminal 120 may transmit the generated recognition information to the management server 130 (S13). For example, the user terminal 120 may transmit recognition information to the management server 130 according to a URL call method.

The management server 130 may determine the payment relay method set in response to the payment service as the first method based on the payment service identification information included in the recognition information received from the user terminal 120 (S14).

The management server 130 may generate a first authentication value for authentication of the payment page (S15). For example, the first authentication value may be defined as a hash value of specific information (eg, payment amount information) included in the payment page.

The management server 130 may provide the payment page and the first authentication value to the user terminal 120 (S16).

The user may request payment to the management server 130 by checking payment amount information and affiliate store information displayed on the payment page provided to the user terminal 120 (S17). For example, when the user inputs a payment request button, the user terminal 120 may transmit payment request information to the management server 130 . The payment request information transmitted from the user terminal 120 to the management server 130 may include user information of the user terminal 120 , affiliate store information, payment amount information, and a second authentication value.

The management server 130 may verify the payment request information by comparing the payment request information with the recognition information and the first authentication value (S18). For example, the management server 130 verifies the payment request information by comparing the user information, the affiliated store information, and the payment amount information included in the recognition information, respectively, the user information, the affiliated store information, and the payment amount information included in the payment request information. can Also, the management server 130 may verify the payment request information by comparing the first authentication value with the second authentication value included in the payment request information.

The management server 130 may transmit a payment approval request to the payment company server 140 based on the verification result of the payment request information (S19).

The payment company server 140 may transmit a payment approval result corresponding to the payment approval request to the management server 130 and the user terminal 120 (S20).

When receiving the payment approval result from the payment company server 140 , the management server 130 may transmit the payment approval result to the store terminal 110 and the user terminal 120 ( S21 ).

Referring to FIG. 3 , when the store terminal 110 generates a payment code and the management server 130 determines the payment relay method as the second method, the store terminal 110, the user terminal 120, and the management server ( 130) and the operation of the payment company server 140 are shown.

First, the store terminal 110 may generate a payment code including affiliate store information and payment amount information (S31). For example, the store terminal 110 may generate one payment code regardless of the type of the simple payment service used by the user. For example, the payment code may include a QR code. To this end, the store terminal 110 may be provided with a QR code generating module. For example, by inputting a payment amount corresponding to the user's usage amount to the store terminal 110 , the store manager may generate a payment code including affiliate store information and the payment amount of the store.

The user may recognize the payment code by executing the simple payment application of the user terminal 120 (S32). When the simple payment application recognizes the payment code, recognition information including payment service identification information, affiliate store information, and payment amount information may be generated.

The user terminal 120 may transmit the generated recognition information to the management server 130 (S33). For example, the user terminal 120 may transmit recognition information to the management server 130 according to a URL call method.

The management server 130 may determine the payment relay method set in response to the payment service as the second method based on the payment service identification information included in the recognition information received from the user terminal 120 ( S34 ). When the payment relay method is determined as the second method, the management server 130 may verify whether affiliate store information included in the recognition information matches affiliate store information previously registered in the database DB.

The management server 130 may transmit driving request information for requesting driving of the simple payment application corresponding to the payment service identification information to the user terminal 120 (S35). For example, the driving request information may include payment amount information and subscription information of a store or store terminal 110 on a payment service. The user terminal 120 may provide a payment page of the simple payment application to the user in response to the driving request information.

The user may check payment amount information and affiliate store information displayed on the payment page of the simple payment application displayed on the user terminal 120, and request payment approval from the payment company server 140 (S36). For example, the payment approval request may include payment amount information, subscription information, user information, and the like.

The payment company server 140 may process the payment approval request and transmit the payment approval result to the user terminal 120 and the management server 130 (S37).

The management server 130 may transmit the payment approval result to the store terminal 110 (S38).

Referring to FIG. 4 , there is shown an embodiment in which the store terminal 110 does not generate a payment code, and the payment code is pre-generated to include affiliate store information and placed in a store in a printed physical form. In addition, when the management server 130 determines the payment relay method as the first method, operations of the store terminal 110 , the user terminal 120 , the management server 130 , and the payment company server 140 are illustrated.

The user may recognize the pre-printed payment code placed in the store by executing the simple payment application of the user terminal 120 (S41). When the simple payment application recognizes the payment code, recognition information including user information, payment service identification information, and affiliate store information may be generated.

The user terminal 120 may transmit the generated recognition information to the management server 130 (S42). For example, the user terminal 120 may transmit recognition information to the management server 130 according to a URL call method.

The management server 130 may determine the payment relay method set in response to the payment service as the first method based on the payment service identification information included in the recognition information received from the user terminal 120 ( S43 ).

The management server 130 may generate a first authentication value for authentication of the payment page (S44). For example, the first authentication value may be defined as a hash value of specific information (eg, affiliate store information) included in the payment page.

The management server 130 may provide the payment page and the first authentication value to the user terminal 120 (S45).

The user may input a payment amount to be paid in the payment page provided to the user terminal 120 (S46).

The user may check the affiliate store information displayed on the payment page of the user terminal 120 and request payment to the management server 130 (S47). For example, when the user inputs a payment request button, the user terminal 120 may transmit payment request information to the management server 130 . The payment request information transmitted from the user terminal 120 to the management server 130 may include user information of the user terminal 120 , affiliate store information, payment amount information, and a second authentication value.

The management server 130 may verify the payment request information by comparing the payment request information with the recognition information and the first authentication value (S48). For example, the management server 130 may verify the payment request information by comparing the user information and the affiliated store information included in the recognition information and the user information and the affiliated store information included in the payment request information, respectively. Also, the management server 130 may verify the payment request information by comparing the first authentication value with the second authentication value included in the payment request information.

The management server 130 may transmit a payment approval request to the payment company server 140 based on the verification result for the payment request information (S49).

The payment company server 140 may transmit a payment approval result corresponding to the payment approval request to the management server 130 and the user terminal 120 (S50).

When receiving the payment approval result from the payment company server 140 , the management server 130 may transmit the payment approval result to the store terminal 110 and the user terminal 120 ( S51 ).

Referring to FIG. 5 , an embodiment in which the store terminal 110 does not generate a payment code, but is arranged in a store in the form of a pre-generated and printed payment code including affiliate store information is illustrated. In addition, when the management server 130 determines the payment relay method as the second method, operations of the store terminal 110 , the user terminal 120 , the management server 130 , and the payment company server 140 are illustrated.

The user may recognize the pre-printed payment code placed in the store by executing the simple payment application of the user terminal 120 (S61). When the simple payment application recognizes the payment code, recognition information including user information, payment service identification information, and affiliate store information may be generated.

The user terminal 120 may transmit the generated recognition information to the management server 130 (S62). For example, the user terminal 120 may transmit recognition information to the management server 130 according to a URL call method.

The management server 130 may determine the payment relay method set in response to the payment service as the second method based on the payment service identification information included in the recognition information received from the user terminal 120 ( S63 ).

The management server 130 may transmit driving request information for requesting to run the simple payment application corresponding to the payment service identification information to the user terminal 120 (S64). For example, the driving request information may include subscription information of a store on a payment service or the store terminal 110 . The user terminal 120 may provide a payment page of the simple payment application to the user in response to the driving request information.

The user may input a payment amount to be paid in the payment page provided to the user terminal 120 (S65).

The user may check payment amount information and affiliate store information displayed on the payment page of the simple payment application displayed on the user terminal 120, and request payment approval from the payment company server 140 (S66). For example, the payment approval request may include payment amount information, subscription information, user information, and the like.

The payment company server 140 may process the payment approval request and transmit the payment approval result to the user terminal 120 and the management server 130 (S67).

The management server 130 may transmit the payment approval result to the store terminal 110 (S68).

6 is a block diagram illustrating a management server according to an embodiment disclosed in this document. 7 is a diagram for explaining an operation of a management server according to an embodiment disclosed in this document.

First, referring to FIG. 6 , the management server 130 according to an embodiment disclosed in this document may include a communication unit 131 , a determination unit 132 , and a processing unit 133 .

The communication unit 131 may receive recognition information from the user terminal 120 . The communication unit 131 may transmit a payment page and a first authentication value for authentication of the payment page to the user terminal 120 . The communication unit 131 may transmit driving request information for requesting to run the simple payment application corresponding to the payment service identification information to the user terminal 120 . The communication unit 131 may receive payment request information from the user terminal 120 . The communication unit 131 may transmit a payment approval request to the payment company server 140 and receive a payment approval result from the payment company server 140 . The communication unit 131 may transmit the payment approval result to the store terminal 110 and the user terminal 120 .

The determination unit 132 may determine a payment relay method set in response to the payment service based on the payment service identification information received from the user terminal 120 .

Referring to FIG. 7 , the determination unit 132 may determine the payment relay method set in response to the payment service by comparing the payment service identification information with the database DB storing the payment relay method information for each payment company. For example, the determination unit 132 may determine the payment relay method as the first method or the second method using the payment service identification information received from the user terminal 120 .

The processing unit 133 may relay the payment processing of the user terminal 130 according to the determined payment relay method.

According to an embodiment, the processing unit 133 may receive recognition information including payment service identification information, affiliate store information, payment amount information and user information from the user terminal 120 when the payment relay method is determined as the first method. have. When the payment relay method is determined as the first method, the processing unit 133 may provide a payment page and a first authentication value for authentication of the payment page to the user terminal 120 . For example, the first authentication value may be defined as a hash value of specific information (eg, payment amount information) included in the payment page.

The processing unit 133 may verify the payment request information by comparing the payment request information with the recognition information and the first authentication value. Here, the payment request information is information received from the user terminal 120 as the user inputs a payment request on the payment page, and includes user information of the user terminal 120, affiliate store information, payment amount information, and a second authentication value. can do.

For example, the processing unit 133 may verify the payment request information by comparing the user information, the affiliated store information, and the payment amount information included in the recognition information, respectively, the user information, the affiliated store information, and the payment amount information included in the payment request information. have. Also, the processing unit 133 may verify the payment request information by comparing the first authentication value with the second authentication value included in the payment request information.

The processing unit 133 may transmit a payment approval request to the payment company server 140 through the communication unit 131 based on the verification result of the payment request information. When receiving the payment approval result from the payment company server 140 in response to the payment approval request, the processing unit 133 may transmit the payment approval result to the store terminal 110 and the user terminal 120 through the communication unit 131 . have.

According to an embodiment, when the payment relay method is determined as the second method, the processing unit 133 may receive recognition information including payment service identification information, affiliate store information, and payment amount information from the user terminal 120 . When the payment relay method is determined as the second method, the processing unit 133 may verify whether affiliate store information included in the recognition information matches affiliate store information previously registered in the database DB.

When the payment relay method is determined as the second method, the processing unit 133 may transmit driving request information for requesting the operation of the simple payment application corresponding to the payment service identification information to the user terminal 120 through the communication unit 131 . . Meanwhile, for example, the driving request information may include payment amount information and subscription information of a store or store terminal 110 on a payment service. That is, the driving request information may include subscription information signed by the store or the store terminal 110 as an affiliate store of the simple payment service provided by the payment company server 140 . To this end, the processing unit 133 may acquire subscription information corresponding to affiliate store information of a store or store terminal 110 using a pre-stored database DB.

The user terminal 120 receiving the driving request information may provide a payment page of the simple payment application to the user. The user may check payment amount information and affiliate store information displayed on the payment page of the simple payment application displayed on the user terminal 120 , and request payment from the payment company server 140 .

When the payment request is approved by the payment company server 140 , the processing unit 133 may receive a payment approval result from the payment company server 140 . The processing unit 133 may transmit the payment approval result to the store terminal 110 through the communication unit 131 .

As described above, the management server 130 according to an embodiment disclosed in this document determines a corresponding payment relay method using the payment service identification information received from the user terminal 120, and provides a simple payment service. The payment processing of the user terminal 120 may be relayed according to the first method or the second method negotiated with the payment company in advance, and the payment service identification information is provided by the user through the simple payment application of the user terminal 120 to the store terminal ( 110) or may be generated by recognizing the integrated payment code (ie, integrated QR code) displayed in the store.

Therefore, the store does not need to generate or arrange a separate QR code for each simple payment service, the store terminal 110 does not need to generate or arrange a payment code for each simple payment service, and the type of simple payment service used by the user Regardless, payment for users can be processed through the integrated payment code. Accordingly, the inconvenience and inconvenience of the store manager can be eliminated, and the cost and trouble caused by newly generating or disposing a payment code whenever a simple payment service is newly added can also be eliminated.

8 is a flowchart illustrating a method of operating a management server according to an embodiment disclosed in this document.

Referring to FIG. 8 , in the method of operating a management server according to an embodiment disclosed in this document, receiving recognition information including payment service identification information from a user terminal ( S110 ), payment service using payment service identification information Determining a payment relay method set in response to (S120), and relaying the payment processing of the user terminal according to the determined payment relay method (S130) may include.

Hereinafter, steps S110 to S130 will be described in detail with reference to FIG. 6 .

In step S110, the communication unit 131 may receive recognition information including payment service identification information from the user terminal (S110).

In step S120 , the determination unit 132 may determine a payment relay method set in response to the payment service based on the payment service identification information received from the user terminal 120 . For example, the determination unit 132 may determine the payment relay method set in response to the payment service by comparing the payment service identification information with the database DB storing the payment relay method information for each payment company.

In step S130 , the processing unit 133 may relay the payment processing of the user terminal 120 according to the determined payment relay method. According to an embodiment, the processing unit 133 may relay the payment processing of the user terminal 120 according to the first method or the second method. The payment processing operation of the user terminal 120 according to the first method or the second method is the payment processing operation of the management server 130 described with reference to FIGS. 1 to 5 and the payment of the processing unit 133 described with reference to FIG. 6 . Since it may be substantially the same as the processing operation, a detailed description is omitted to avoid repetition.

The above description is merely illustrative of the technical spirit of the present disclosure, and various modifications and variations will be possible without departing from the essential characteristics of the present disclosure by those of ordinary skill in the art to which the present disclosure pertains.

Accordingly, the embodiments disclosed in the present disclosure are for explanation rather than limiting the technical spirit of the present disclosure, and the scope of the technical spirit of the present disclosure is not limited by these embodiments. The protection scope of the present disclosure should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present disclosure.

1000: payment processing system
110: shop terminal
120: user terminal
130: management server
131: communication department
132: judgment unit
133: processing unit
140: payment company server

Claims (26)

a communication unit for receiving recognition information including payment service identification information from a user terminal;
a determination unit configured to determine a payment relay method set in response to the payment service by using the payment service identification information; and
a processing unit for relaying the payment processing of the user terminal according to the determined payment relay method;
The payment relay method includes a first method that is a server relay method and a second method that is an application relay method,
When the payment relay method is determined as the first method, the processing unit provides a payment page for processing the payment of the user terminal through the server and a first authentication value for authentication of the payment page to the user terminal,
The first authentication value is defined as a hash value of information included in the payment page,
The processing unit receives payment request information corresponding to the payment page from the user terminal,
The payment request information includes user information of the user terminal, affiliate store information of a store where the user wants to pay, payment amount information, and a second authentication value,
Verifies the payment request information by comparing the payment request information with the recognition information and a first authentication value,
The recognition information is generated by recognizing a payment code of a store generated by a payment service application running in the user terminal regardless of the type of payment service application,
The payment service identification information is information indicating the type of payment service application that recognizes the payment code server. The method of claim 1,
The determination unit compares the payment service identification information with a database storing payment relay method information for each payment company to determine a payment relay method set in response to the payment service. delete delete delete delete The method of claim 1,
The processing unit transmits a payment approval request to a payment company server corresponding to the payment service identification information based on a result of the verification, and when receiving a payment approval result from the payment company server, the user terminal and the user want to pay Server, characterized in that for providing the payment approval result to the store terminal of the store. The method of claim 1,
The recognition information server, characterized in that it further comprises information about the merchant and payment amount information of the store to which the user wants to pay. 9. The method of claim 8,
When the payment relay method is determined as the second method, the processing unit transmits driving request information for requesting to run a payment service application corresponding to the payment service identification information to the user terminal. 10. The method of claim 9,
The driving request information server, characterized in that it includes the payment amount information and the subscription information of the store on the payment service. 11. The method of claim 10,
The server, characterized in that the processing unit acquires the store subscription information on the payment service corresponding to the affiliate store information of the store from a pre-stored database. 9. The method of claim 8,
The server, characterized in that the processing unit verifies whether the store is a previously registered affiliate store based on the affiliate store information included in the recognition information. delete The method of claim 1,
The payment code is a server, characterized in that it includes a QR code generated including the merchant information and payment amount information of the store. delete a store terminal generating a payment code including affiliate store information and payment amount information;
a user terminal for recognizing the payment code to generate recognition information including payment service identification information, the affiliated store information and payment amount information, and transmitting the recognition information to a management server; and
and a management server that determines a payment relay method set in response to the payment service by using the payment service identification information, and relays the payment processing of the user terminal according to the determined payment relay method,
The payment relay method includes a first method that is a server relay method and a second method that is an application relay method,
When the management server determines that the payment relay method is the first method, a payment page for processing the payment of the user terminal through the management server and a first authentication value for authentication of the payment page are provided to the user terminal do,
The first authentication value is defined as a hash value of information included in the payment page,
The management server receives payment request information corresponding to the payment page from the user terminal, compares the payment request information with the recognition information and a first authentication value to verify the payment request information,
The payment request information includes user information of the user terminal, affiliate store information of a store where the user wants to pay, payment amount information, and a second authentication value,
The recognition information is generated by recognizing a payment code of a store by a payment service application running on the user terminal,
The store terminal generates one payment code regardless of the type of payment service application,
The payment service identification information is information indicating a type of a payment service application that recognizes a payment code, the payment processing system. 17. The method of claim 16,
The management server compares the payment service identification information with a database storing payment relay method information for each payment company to determine a payment relay method set in response to the payment service. 17. The method of claim 16,
The payment processing system according to claim 1, further comprising a payment company server for processing a payment approval request transmitted from the user terminal or the management server, wherein the payment company server is a payment company server corresponding to the payment service identification information. delete delete delete delete 17. The method of claim 16,
The management server transmits a payment approval request to the payment company server based on the verification result, and provides the payment approval result to the user terminal and the store terminal when receiving a payment approval result from the payment company server Characterized by the payment processing system. 19. The method of claim 18,
The management server, when the payment relay method is determined as the second method, the payment processing system, characterized in that the transfer request information for requesting to drive the payment service application corresponding to the payment service identification information to the user terminal. 25. The method of claim 24,
The driving request information comprises the payment amount information and the subscription information of the store on the payment service. 26. The method of claim 25,
The payment processing system, wherein the management server acquires, from a pre-stored database, subscription information of the store on the payment service corresponding to the affiliate store information of the store.

Images