JP2020030774A - Payment service cooperation system, cooperation data collation server, payment application terminal, payment service cooperation method, and program - Google Patents

Abstract

To provide a payment service cooperation system, in which a payment application performs a payment in a manner that a non-payment application cooperates a payment without acquiring any personal information associated from the payment application when linking a payment application with a non-payment application to prevent personal information from being stolen; thereby the security function is improved.SOLUTION: Disclosed payment service cooperation system includes: a payment processing part that performs a series of payment processing relevant to a payment executed by a payment application; an information processing part that performs a series of information processing other than the payment executed by a non-payment application; and an authentication part that determines whether to perform the cooperative processing between the payment application and the non-payment application via a determination processing executed by an authentication application.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a payment service cooperation system that performs cooperation between a payment application and another application in a payment terminal, a cooperation data collation server, a payment application terminal, a payment service cooperation method, and a program.

When paying with a credit card or electronic money, payment with a credit card or electronic money is performed using a payment terminal (hereinafter, payment terminal) (for example, see Patent Document 1).
There is a demand for effective use of the payment terminal by linking the payment processing in the payment terminal with a non-payment application such as an accounting application and a POS (point of sale) application (for example, see Patent Document 2).

For example, in a small shop, in a state where space for accounting is limited, a terminal for performing non-settlement information processing is required in addition to a settlement terminal, and there are cases where it is difficult to arrange these terminals in terms of space. is there.
In this case, the user wants to install each of the above-described payment application and non-payment application on a general-purpose terminal such as a tablet computer equipped with a general OS (operating system) and use it as a multifunctional payment terminal. There are requests.

Furthermore, due to the increase in foreign tourists, it has become common to pay by credit while sitting at the table, but the clerk carries the customer's credit card to the payment terminal installed at the accounting place. , Payment processing for food and drinks and the like.
However, foreign tourists are afraid that taking credit cards to places they cannot see will be fraudulent. For this reason, it is conceivable that the payment application is installed in the order terminal at the customer's seat, and payment is made while the customer can see the credit card while sitting at the table.

JP 2004-164195 A JP 2015-194800 A

However, linking a non-payment application and a payment application that does not ensure sufficient security may adversely affect the security of the payment process itself. Therefore, it is not desirable from the viewpoint of security to install and use the non-settlement application together with the settlement application in the settlement terminal without taking any measures.
Also, for general-purpose terminals such as tablet computers equipped with a general OS, similarly to the payment terminal, it is not possible to install and use the non-payment application together with the payment application without taking any measures. Not desirable from a point of view.

That is, in the case of a terminal on which the above-described general OS is installed, each of the payment application and the non-payment application can use the functions of the OS without any limitation.
For this reason, the non-payment application can also use the function of the payment application to acquire data necessary for payment, for example, the function of reader control for reading credit card data.
As a result, personal information such as a credit card number and a password of a credit card may be stolen using a non-payment application, and the personal information may be misused.

Further, when the non-payment application cooperates, the credit card number input for the payment processing by the cooperating payment application remains on the terminal due to the processing of the non-payment application, and the credit card number may be misused. There is also.
In addition, even when the payment application and the non-payment application are linked between different terminals, there is a possibility that personal information such as a credit card number and a password of a credit card is stolen via the non-payment application in the link. is there.

  The present invention has been made in view of such circumstances, and when performing cooperation between a payment application and a non-payment application, the non-payment application cooperates without acquiring personal information associated with payment from the payment application. Provide payment service cooperation system, coordination data collation server, payment application terminal, payment service cooperation method and program for preventing payment of personal information and improving security functions in order to make payment to payment application The purpose is to do.

  The present invention has been made in order to solve the above-described problems, and a payment service cooperation system of the present invention is a payment processing unit that performs a payment process related to payment of a price executed by a payment application, and is executed by a non-payment application. An information processing unit that performs information processing other than the payment process, and an authentication unit that determines whether cooperative processing between the payment application and the non-payment application is possible by a determination process performed by an authentication application. And

  The settlement service cooperation system according to the present invention is characterized in that the settlement authentication application determines whether or not the cooperation processing is possible based on authentication information for authenticating the non-settlement application.

  In the settlement service cooperation system according to the present invention, the authentication information identifies application identification information for identifying the non-payment application, a terminal serial number of a terminal on which the non-payment application is mounted, and a user who operates the terminal. It is characterized by including any, combination, or all of the user identification information.

  The payment service cooperation system according to the present invention is characterized in that the payment authentication application determines whether or not a cooperation process between the non-payment application and another non-payment application different from the non-payment application is possible.

  The payment service cooperation system of the present invention includes a verification database indicating a correspondence between authentication information for authenticating the non-payment application and the cooperation process that can cooperate in accordance with the authentication information. And a collation data collation server that outputs the presence or absence of the collaborative processing corresponding to the authentication information as a collation result in response to the collation request.

  The settlement service cooperation system of the present invention further includes a download server that performs the cooperation processing with the settlement application and distributes the authenticated non-settlement application to a maker that created the settlement application, wherein the download server includes: In response to the inquiry from the payment application, the payment application refers to the history of non-payment applications downloaded by the payment application and notifies other non-payment applications that have not been downloaded.

In the settlement service cooperation system according to the present invention, the download server responds to an inquiry from the settlement application, refers to a history of the non-payment application downloaded by the settlement application, and notifies another non-payment application that has not been downloaded. It is characterized by doing.
The settlement service cooperation system of the present invention performs a first settlement processing unit that performs settlement processing related to payment of a price executed by a first settlement application, and a settlement processing other than the settlement processing executed by a second settlement application. A second payment processing unit for performing the processing, and an authentication unit for determining whether or not the cooperative processing between the first payment application and the second payment application is possible by a determination process performed by the authentication application.

  A cooperative authentication server according to the present invention is a payment authentication server including a payment authentication application used in a payment service cooperation system including a payment application that performs a payment process related to payment of a price and a non-payment application that performs information processing other than the payment process. Wherein the payment authentication application determines whether or not cooperative processing between the non-payment application and the payment application is possible.

  The cooperative data collation server of the present invention is a payment application that performs a payment process related to payment of a price, a non-payment application that performs information processing other than the payment process, and whether or not the coordination process between the non-payment application and the payment application is possible. A collation data collation server that collates the association between the coordination process and the authentication information of the non-settlement application in response to a collation request from a payment service collaboration system including a payment authentication application to be determined. A collation database that indicates the correspondence with the coordination process that can cooperate in response to a collation request from the payment authentication application, and determines whether the coordination process is associated with the authentication information. It is characterized in that the result of the verification is output.

  The payment application terminal according to the present invention determines a payment application for performing payment processing related to payment of a price, a non-payment application that performs information processing other than the payment processing, and determines whether or not cooperative processing between the non-payment application and the payment application is possible. A payment application terminal used in a payment service cooperation system including a payment authentication application to be executed, wherein each of the payment application and the payment authentication application is provided.

In the settlement service cooperation method of the present invention, the settlement application performs a settlement process related to payment of a price, a non-settlement application performs an information processing process that performs information processing other than the settlement process, and the authentication application performs the settlement process. An authentication step of performing a process of determining whether a cooperative process between the payment application and the non-payment application is possible.
According to the settlement service cooperation method of the present invention, the first settlement application performs a settlement process related to payment of a price, and the second settlement application performs a second settlement process other than the settlement process. A processing step and an authentication step in which the authentication application performs processing for determining whether or not cooperative processing between the first payment application and the second payment application can be performed.

A program according to the present invention is a program for causing a computer to function as a payment service cooperation system, and executes the computer by a payment processing unit that performs payment processing related to payment of a price executed by a payment application, and is executed by a non-payment application. A program for functioning as information processing means for performing information processing other than the payment processing, and as authentication means for determining whether cooperation processing between the payment application and the non-payment application is possible by a determination process executed by the authentication application.
A program according to the present invention is a program for causing a computer to function as a payment service cooperation system. The computer executes the first payment processing means for performing payment processing relating to payment of a price executed by a first payment application, and the second payment. Second payment processing means for performing payment processing other than the payment processing performed by the application, and processing for determining whether or not cooperative processing between the first payment application and the second payment application is to be performed by the authentication application This is a program for functioning as an authentication means performed by the user.

A program according to the present invention is a computer as a cooperative authentication server including a payment authentication application used in a payment service cooperation system including a payment application that performs a payment process related to payment of a price and a non-payment application that performs information processing other than the payment process. And a program for causing the computer to function as means for determining whether or not cooperative processing between the non-settlement application and the settlement application is possible.

  The program of the present invention is a payment application that performs a payment process related to payment of a price, a non-payment application that performs information processing other than the payment process, and a payment that determines whether a cooperative process between the non-payment application and the payment application is possible. A program for causing a computer to function as a cooperative data verification server that outputs the payment data that can be used by the non-payment application in response to a verification request from a payment service cooperation system including an authentication application. It refers to a collation database indicating the correspondence between authentication information for authenticating the application and the payment data that can be used in correspondence with the authentication information, and responds to a collation request from the payment authentication application. A program for information and is made to function as means for outputting a verification result whether collation is associated.

  According to the present invention, when performing cooperation between the payment application and the non-payment application, the non-payment application causes the payment application to perform payment without acquiring personal information associated with payment from the payment application. It is possible to provide a payment service cooperation system, a cooperation data collation server, a payment application terminal, a payment service cooperation method, and a program that prevent personal information from being stolen and improve security functions.

It is a figure showing the example of composition of the settlement service cooperation system by one embodiment of the present invention. It is a figure showing the example of composition of the download management table written in advance and stored in management database 4_2 by this embodiment. It is a conceptual diagram explaining the cooperation of each of the payment application and the non-payment application of the payment service cooperation system in the present embodiment. 3 shows an example of the configuration of a coordination processing association table written and stored in advance in a collation database 32. It is a flow chart which shows an example of operation of each processing of settlement cooperation, device cooperation, and non-settlement cooperation in settlement service cooperation system 100 of this embodiment. It is a conceptual diagram explaining the application example of the settlement service cooperation system by this embodiment. It is a conceptual diagram explaining other application examples of the settlement service cooperation system by this embodiment. It is a figure showing the modification of the settlement service cooperation system by one embodiment of the present invention.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration example of a settlement service cooperation system according to an embodiment of the present invention. In FIG. 1, the payment service cooperation system 100 according to the present embodiment includes a payment application terminal 1-1, a payment application terminal 1-2, a payment application terminal 1-3, a cooperation data collation server 3, and a download server 4. I have.

  Each of the payment application terminal 1-1, the payment application terminal 1-2, the payment application terminal 1-3, the cooperation data collation server 3, and the download server 4 is connected by an information communication network 200 including the Internet. The payment application terminal 1-1, the payment application terminal 1-2, and the payment application terminal 1-3 are collectively referred to as the payment application terminal 1. In the present embodiment, the payment service cooperation system 100 is described as having a configuration including three payment application terminals 1, but a configuration including one or more than two payment application terminals 1 may be employed.

The payment application terminal 1 is a thin client terminal (for example, a CAFIS Arch (registered trademark) terminal or the like), for example, a terminal provided with a payment application 10 that performs payment processing for payment to a credit card company using a credit card. It is. The payment application terminal 1 includes a payment authentication application 11 and a non-payment application 20 in addition to the payment application 10 described above. Although one non-settlement application 20 is shown in FIG. 1, two or more non-settlement applications may be provided.
The payment authentication application 11 determines whether or not a cooperation request from the non-payment application 20 is possible based on the authentication information included in the information processing cooperation request from the non-payment application 20.

  The non-payment application 20 is an application that performs information processing other than processing related to payment, such as the payment application 10, and includes, for example, a POS application that performs information processing related to sales management, and a point that gives points in accordance with the payment amount. A grant application, an order (product selection) application for managing customer orders, and the like. Although the non-settlement application 20 is described as a non-settlement application in order to be distinguished from the settlement application 10, a non-settlement application 20 may be a prepaid payment or a settlement application such as a unique currency. The non-settlement application 20 includes a cooperation API (application programming interface) module 21 (described later) that outputs the authentication information for authenticating itself when the non-settlement application 20 requests the cooperation to the settlement application 10.

Based on the authentication information supplied from the payment application terminal 1 and the cooperation information indicating the content of the cooperation process, the cooperation data collation server 3 provides the payment application terminal 1 specified by the authentication information with the cooperation information. The collation is performed to determine whether or not the content of the coordination process is associated, and a collation result is notified.
Further, the payment authentication application 11 determines whether or not it is possible to respond to the cooperation request from the non-payment application 20 based on the verification result from the cooperation data verification server 3.

The download server 4 is a server that manages processing related to the download of the non-settlement application 20, and is provided in, for example, a download center 400 that supplies the non-settlement application 20 to the settlement application 10.
The download server 4 includes an application database 4_1 and a management database 4_2.

In the application database 4_1, each of the non-payment applications 20 created by a third party and allowed to cooperate with the payment application 10 provided in the payment application terminal 1 is stored.
In the management database 4_2, each payment application terminal 1 and the non-payment application 20 downloaded by each payment application terminal 1 are stored in association with each other.

  In the present embodiment, the payment application terminal 1 is configured by a computer, and the payment application 10, the payment authentication application 11, and the non-payment application 20, which are programs, are activated and activated by the OS installed in each of the computers. Then, information processing is performed using hardware resources (hardware devices such as a CPU (central processing unit), a memory, a display device, a printer, and a card reader) of the computer.

FIG. 2 is a diagram showing a configuration example of a download management table previously written and stored in the management database 4_2 according to the present embodiment.
In the download management table of FIG. 2, columns for terminal serial number, user identification information, download application information, and usable application information are provided for each record.

  The terminal serial number is a number corresponding to a manufacturing number uniquely assigned to each terminal at the time of manufacturing, and can uniquely identify each payment application terminal 1. The user identification information is identification information given to each of the users who operate the non-payment application 20, and can uniquely identify each user. The download application information describes information on a non-payment application that the payment application terminal 1 indicated by the terminal serial number has already downloaded. The usable application information describes information on a non-settlement application that can be used by the user indicated by the user identification information.

Further, when the payment application terminal 1 is notified of the download inquiry, the download server 4 reads the terminal serial number added to the inquiry. Then, the download server 4 reads the available application information corresponding to the terminal serial number, selects a non-payment application not described in the download application information, and uses the selected non-payment application for the payment application terminal 1. Notify as a possible non-payment application.
In addition, the download server 4 newly writes the non-settlement application newly authenticated by the maker in the column of usable application information corresponding to the user identification information that enables the non-settlement application, and stores the application.

In the above-described download processing, when a usable non-payment application is notified, the payment application terminal 1 presents the usable non-payment application to the user. The download server 4 is notified of information indicating the non-settlement application selected by the user.
Thereby, the download server 4 transmits the data of the non-payment application notified from the payment application terminal 1 to the payment application terminal 1.
Then, the payment application terminal 1 installs the downloaded non-payment application, and activates the installed non-payment application.

FIG. 3 is a conceptual diagram illustrating a cooperative relationship between the payment application and the non-payment application of the payment service cooperation system (FIG. 1) in the present embodiment.
3, the payment authentication application 11 includes a payment application cooperation interface module 111, a device cooperation interface module 112, a non-payment application cooperation interface module 113, an authentication module 114, a payment application cooperation module 115, and a non-payment application cooperation module 116. Have. In the following description, the payment application terminal 1 includes each of the non-payment application 20_1 and the non-payment application 20_2. When the non-settlement application 20_1 and the non-settlement application 20_2 are collectively referred to, they are referred to as the non-settlement application 20. In the present embodiment, the payment application terminal 1 includes two non-payment applications 20_1 and 20_2, but one or more non-payment applications 20_2 may be provided.

  The non-settlement application 20 is configured to include a cooperation API module 21. The cooperation API module 21 is a program module generated by a maker that has created the payment application 10, and is distributed to each of third parties that cooperate with the payment application 10. Each of the third parties needs to incorporate the cooperative API module 21 into the non-payment application 20 that cooperates with the payment application 10.

  The maker (the maker that distributes the payment application 10) operates normally without causing the non-payment application 20 provided by the third party to adversely affect the payment service cooperation system (including the payment application system 10). Is confirmed, and if there is no problem, the non-settlement application 20 is permitted. Thereby, the third party, the maker, or the administrator of the download center 400 stores the non-settlement application 20 permitted by the maker in the application database 4_1 (FIG. 1) of the download center 400 and stores the non-settlement application 20 in the management database 4_2 (FIG. 1). The non-settlement application 20 is registered as a usable application (usable application information). Then, the download server 4 supplies the non-settlement application 20 stored in the application database 4_1 in response to a download request from the settlement application terminal 1.

The cooperation API module 21 includes, as a program library, a payment application cooperation call module 211, a device cooperation call module 212, and a non-payment application cooperation call module 213, which are read functions.
The payment application cooperation calling module 211 determines whether the cooperation process at the time of cooperation is a payment cooperation process using payment data that is data processed by the payment application 10. Then, when the coordination process that cooperates with the payment application 10 is the payment coordination process, the payment application coordination call module 211 outputs coordination information indicating that the coordination process is the payment coordination process (that the coordination is a cooperable payment process and that the And the authentication information used to determine whether or not the cooperation with the non-settlement application 20 is possible is output to the settlement authentication application 11 as cooperation request information.

  Here, the authentication information is application identification information for identifying the non-payment application 20, for example, if the OS of the payment application terminal 1 is Android (registered trademark), the package information is a package name, and the OS is Windows (registered trademark). Is a URI (uniform resource identifier), and when the OS is an iOS (registered trademark), a URI (uniform resource identifier) Scheme (scheme) is included.

The authentication information includes not only the application identification information for identifying the non-payment application 20 but also a terminal serial number (for example, a terminal-specific number assigned at the time of factory shipment) for identifying the payment application terminal 1, and a payment application terminal 1. The user identification information of the operating user or an authentication (permission) code issued by the manufacturer may be used.
The authentication information may use any one of, or a combination of, the application identification information, the terminal serial number, the user identification information, and the authentication (permission) code.
Further, as the authentication information, a hash value obtained by obtaining any, a combination, or all of the application identification information, the terminal serial number, the user identification information, and the authentication code using a predetermined hash function may be used.
In the present embodiment, as an example, a case where the authentication information uses all of the application identification information, the terminal serial number, the user identification information, and the authentication code will be described.

  The device cooperation calling module 212 determines whether or not the cooperation process at the time of cooperation is a device cooperation process in which the device provided in the payment application terminal 1 is used. When the cooperation process is a device cooperation process, the device cooperation calling module 212 sets the cooperation information indicating that the cooperation process is the device cooperation process and the authentication information used to determine whether or not the cooperation with the non-settlement application 20 is possible, in settlement. It outputs to the authentication application 11 as cooperation request information. Here, the device is a device installed in the payment application terminal 1 and used by the payment application 10 in response to a payment process. For example, the device is a card number magnetic device that reads a credit card number of a credit card. Examples include a card reader, an IC card reader, and a barcode reader.

  The non-settlement application cooperation calling module 213 determines whether or not the cooperation process at the time of cooperation is a non-settlement cooperation process using non-settlement data which is data processed by another non-settlement application provided in the settlement application terminal 1. Perform When the cooperation process is the non-settlement cooperative process, the non-settlement application cooperative calling module 213 outputs the coordination information indicating that the cooperative process is the non-settlement cooperative process, and the authentication information used to determine whether the coordination with the non-settlement application 20 is possible. And the cooperation destination information indicating the non-settlement application to be linked are output to the settlement application 11 as cooperation request information.

  The payment application cooperation interface module 111 determines whether the cooperation request information input from the non-payment application 20 is a payment cooperation process. If the cooperation request information is a payment cooperation process, the payment application cooperation interface module 111 extracts authentication information from the cooperation request information, outputs the extracted authentication information to the authentication module 114, and performs authentication of the authentication information. At the same time, a request is made for authentication (determination) as to whether or not execution of the settlement cooperation process is possible.

  The device cooperation interface module 112 determines whether the cooperation request information input from the non-settlement application 20 is a device cooperation process. If the cooperation request information is device cooperation processing, the device cooperation interface module 112 extracts authentication information from the cooperation request information, outputs the extracted authentication information to the authentication module 114, and authenticates (determines) the authentication information. Is performed, and authentication (determination) of whether or not the execution of the device cooperation process is possible is requested.

  The non-settlement application cooperation interface module 113 determines whether the cooperation request information input from the non-settlement application 20 is a non-settlement cooperation process. If the cooperation request information is a non-settlement cooperation process, the non-settlement application cooperation interface module 113 extracts authentication information from the cooperation request information, outputs the extracted authentication information to the authentication module 114, and authenticates the authentication information. Is performed, and authentication (determination) of whether or not the execution of the non-settlement cooperation process is possible is requested.

  The authentication module 114 performs a matching process based on the authentication information in response to a matching request supplied from each of the payment application cooperation interface module 111, the device cooperation interface module 112, and the non-settlement application cooperation interface module 113.

In other words, the authentication module 114 responds to the request for authentication of the payment cooperation process from the payment application cooperation interface module 111 and responds to the cooperation data collation server 3 as a service in which the payment cooperation process corresponding to the authentication information is available. It outputs a request for collation as to whether it is attached and whether it is associated with the designated business in the settlement cooperative processing.
Then, the authentication module 114 associates the result of the collation as to whether or not the payment cooperation process corresponding to the authentication information is associated with the available service, and whether the designated business in the payment cooperation process is associated with the available business. Input from the data collation server 3.

At this time, if the authentication module 114 obtains a collation result indicating that the payment coordination processing is available as an available service corresponding to the authentication information and that the designated business in the payment coordination processing is associated, the authentication module 114 The module 115 is made to perform the cooperative processing for the payment application 10.
On the other hand, if the authentication module 114 obtains a collation result indicating that one or both of the payment coordination processing and the designated business in the payment coordination processing are not associated with the authentication information as an available service, The settlement application 20 is notified of information indicating that cooperation is impossible.

That is, the authentication module 114 is associated with the cooperation data collation server 3 as an available device for the device cooperation process corresponding to the authentication information in response to the request for authentication of the device cooperation process from the device cooperation interface module 112. And output a request for collation.
Then, the authentication module 114 inputs a collation result as to whether or not the device cooperation process corresponding to the authentication information is associated as an available service from the cooperation data collation server 3.

At this time, if the authentication module 114 obtains the collation result indicating that the device cooperation process is associated with the authentication information as an available service, the authentication module 114 performs the device cooperation process on the corresponding device.
On the other hand, the authentication module 114 notifies the non-settlement application 20 of information indicating that coordination is impossible when the collation result that the settlement processing is not associated with the authentication information as an available service is obtained. Perform processing.

In other words, the authentication module 114 responds to the request for authentication of the non-settlement cooperative process from the non-settlement application coordination interface module 113 to the cooperative data collation server 3 to use the non-settlement cooperative process corresponding to the authentication information. A request for collation as to whether or not they are associated is output.
Then, the authentication module 114 inputs a collation result as to whether or not the non-settlement coordination process corresponding to the authentication information is associated as an available service from the coordination data collation server 3.

At this time, if the authentication module 114 obtains a collation result indicating that the non-settlement cooperative processing is associated with the authentication information as a usable service, the authentication module 114 determines that the other non-settlement application 20 (for example, In the case of the payment application 20_1, the non-payment application 20_2) is caused to perform a non-payment cooperation process as another non-payment application via the non-payment application cooperation module 116.
On the other hand, if the authentication module 114 obtains a collation result indicating that the non-settlement cooperative processing is not associated with the authentication information as an available service, the authentication module 114 notifies the non-settlement application 20 (20_1) that coordination is not possible. The notification processing of the indicated information is performed.

The payment application cooperation module 115 responds to the request for the payment cooperation processing from the authentication module 114, and performs the payment processing and the business cooperation processing in the payment processing in response to the cooperation information from the non-payment application 20 to the payment application 10. Let it do.
The non-settlement application cooperation module 116 responds to the request for the non-settlement cooperation process from the authentication module 114, performs the non-settlement process in response to the cooperation information from the non-settlement application 20_1, and executes the non-settlement application 20 of the other non-settlement application 20_2. To do. The non-settlement application 20_2 responds to the non-settlement application 20_1 via the non-settlement application cooperation module 116.

The cooperation data collation server 3 includes a cooperation possibility collation unit 31 and a collation database 32.
When a request for collation is supplied from the authentication module 114, the coordination permission / inhibition collation unit 31 performs coordination processing (settlement coordination processing, device coordination processing, and non-payment coordination processing) in the coordination information supplied together with the authentication information. ) Are collated with reference to the collation database 32.

FIG. 4 shows an example of the configuration of a coordination processing correspondence table that is written and stored in the collation database 32 in advance.
In the coordination processing correspondence table of FIG. 4, columns of application identification information, terminal serial number, user identification information, available service type, available business type, and available device type are provided for each record.
The application identification information is identification information for identifying a non-settlement application. The terminal serial number is a number corresponding to a manufacturing number uniquely assigned to each terminal at the time of manufacturing, and can uniquely identify each payment application terminal 1. The user identification information is identification information given to each of the users who operate the non-payment application 20, and can uniquely identify each user.

Authentication information is a combination of each of the above-described application identification information, terminal serial number, and user identification information, or a combination of information paid in advance.
The available service type is, for example, a type of credit settlement, electronic money settlement, barcode settlement, account transfer, and the like in the case of the settlement cooperation process, and information indicating that the settlement application cannot be linked when no association is made. Is described. In the available device type, in the case of the device cooperation processing, a device name that can be cooperated (available) is described, and when no association is made, information indicating that device cooperation is impossible is described. In the case of the payment coordination process, the available business type is, for example, credit sales, and in the case of the non-payment coordination process, for example, points are given, an instruction corresponding to an order, business management, and the like. If not, information indicating that non-settlement application cooperation is impossible is described.

  For example, non-settlement applications that do not link with other applications include, for example, a time management application that manages the employee's attendance, a date and time sales management application that manages sales on any day and at any time, and business communication to employees. And a surveillance camera video management application that manages imaging of a surveillance camera. Also, when installing a non-payment application that does not cooperate with other applications, it is necessary to download and install from among the non-payment applications that have been authenticated by the manufacturer from the download server 4 described above.

  Further, in the above-described embodiment, an example has been described in which the cooperation data collation server 3 is arranged in a different place, for example, a management center that manages cooperation, but the authentication module 114 has the function of the cooperation possibility collation unit 31. Alternatively, only the collation database 32 may be arranged in the management center. In the case of this configuration, the authentication module 114 directly refers to the collation database 32 when performing authentication of whether or not the cooperative processing of the non-payment application 20 in each of the payment cooperative processing, the device cooperative document processing, and the non-payment cooperative processing, It is checked whether each process is associated with the non-settlement application 20 or not.

  Further, in the above-described embodiment, the payment authentication application 11 is provided for the payment application terminal 1. However, a payment authentication server having the function of the payment authentication application 11 is provided, and upon receiving a cooperation request from the non-payment application 20, The authentication processing may be performed with the cooperation data collation server 3 so that the payment application 10 of the payment application terminal 1 is operated.

FIG. 5 is a flowchart illustrating an operation example of each processing of payment cooperation, device cooperation, and non-payment cooperation in the payment service cooperation system 100 of the present embodiment.
Step S101:
The non-settlement application 20 (for example, the non-settlement application 20_1) outputs a command corresponding to the cooperative processing to the cooperative API module 21 by an internal processing process or external control by an input unit (for example, a touch pad). I do.

Step S102:
In the cooperation API module 21, each of the payment application cooperation call module 211, the device cooperation call module 212, and the non-payment application cooperation call module 213 determines whether or not the command cooperation processing corresponds to itself.
At this time, if the cooperative processing is the payment cooperative processing (case A), the payment application cooperative calling module 211 advances the processing to step S103A.
If the cooperation process is a device cooperation process (case B), the device cooperation calling module 212 advances the process to step S103B.
If the cooperation processing is a device cooperation processing (case B), the non-settlement application cooperation calling module 213 advances the processing to step S103B.

Step 103A:
The payment application cooperation calling module 211 converts, for example, a command supplied from the non-payment application 20 into a payment command in the payment application 10 in preparation for the payment cooperation.

Step 104A:
The payment application cooperation calling module 211 acquires authentication information (for example, application identification information, terminal serial number, user identification information, and the like) from each of the non-payment application 20 and the payment application terminal 1.

Step 105A:
The payment application cooperation calling module 211 uses the payment information indicating that the cooperation process is a payment cooperation process (here, the payment cooperation process includes a settlement command) and the acquired authentication information as cooperation request information as a payment application terminal. 1 to the payment authentication application 11 (payment cooperation request).

Step 106A:
The payment application cooperation interface module 111 in the payment authentication application 11 extracts each of the payment cooperation processing and the authentication information.
Then, the payment application cooperation interface module 111 outputs each of the extracted payment cooperation processing and authentication information to the authentication module 114, and requests authentication for whether or not the payment cooperation processing can be cooperated.

Step 107A:
The authentication module 114 responds to the authentication request from the payment application cooperation interface module 111, and requests the cooperation data verification server 3 to verify whether the requested payment cooperation processing is associated with the authentication information. I do.
Thereby, in the cooperation data collation server 3, the cooperation possibility collation unit 31 refers to the coordination processing association table in the collation database 32, and performs collation as to whether the requested settlement coordination process is associated with the authentication information. Then, the collation result is transmitted to the authentication module 114.

Step 108A:
The authentication module 114 determines whether or not the requested settlement cooperation process can be executed based on the comparison result from the cooperation data comparison server 3.
At this time, when the authentication module 114 indicates that the collation result is associated with the settlement cooperation process, the authentication module 114 advances the process to step S109A, and on the other hand, indicates that the collation result is not associated with the settlement cooperation process The process proceeds to Step S110.

Step 109A:
The authentication module 114 requests the payment application cooperation module 115 to execute the payment cooperation process based on the collation result indicating that the payment cooperation process is associated with the authentication information.
Thereby, the payment application cooperation module 115 causes the payment application 10 to execute the cooperation processing requested by the non-cooperation application 20.

Step 103B:
The device cooperation call module 212 converts, for example, a command supplied from the non-payment application 20 into a device command when the payment application 10 controls a device of the payment application terminal 1 as a preparation for payment cooperation.

Step 104B:
The device cooperation calling module 212 acquires authentication information (for example, application identification information, terminal serial number, user identification information, and the like) from each of the non-payment application 20 and the payment application terminal 1.

Step 105B:
The device cooperation calling module 212 uses the cooperation information indicating that the cooperation process is the device cooperation process (here, the device cooperation process includes a device command) and the acquired authentication information as cooperation request information as the payment application terminal 1 Is output to the payment authentication application 11 in (1) (device cooperation request).

Step 106B:
The device cooperation interface module 112 in the payment authentication application 11 extracts each of the device cooperation processing and the authentication information.
Then, the device cooperation interface module 112 outputs each of the extracted device cooperation processing and authentication information to the authentication module 114, and requests authentication for whether or not the device cooperation processing can be performed.

Step 107B:
The authentication module 114 responds to an authentication request from the device cooperation interface module 112 and requests the cooperation data verification server 3 to verify whether the requested device cooperation processing is associated with the authentication information. .
Thereby, in the cooperation data collation server 3, the cooperation possibility collation unit 31 refers to the coordination processing correspondence table in the collation database 32, and performs collation as to whether the requested device cooperation process is associated with the authentication information. Then, the collation result is transmitted to the authentication module 114.

Step 108B:
The authentication module 114 determines whether or not the requested device cooperation process can be executed based on the verification result from the cooperation data verification server 3.
At this time, when the authentication module 114 indicates that the collation result is associated with the device cooperation process, the authentication module 114 proceeds the process to step S109B, while on the other hand, indicates that the collation result is not associated with the device cooperation process The process proceeds to Step S110.

Step 109B:
The authentication module 114 outputs a device command to a device indicated by the cooperation process based on the collation result indicating that the device cooperation process is associated with the authentication information, and performs a device operation requested by the non-settlement application 20. Is executed.

Step 103C:
The non-settlement application cooperation calling module 213 converts, for example, a command supplied from the non-settlement application 20 (20_1) into a non-settlement command in another cooperating non-settlement application (20_2) in preparation for the settlement cooperation.

Step 104C:
The non-settlement application cooperation calling module 213 acquires authentication information (for example, application identification information, terminal serial number, user identification information, etc.) from each of the non-settlement application 20 and the settlement application terminal 1.

Step 105C:
The non-settlement application cooperation calling module 213 links cooperation information indicating that the cooperation process is a non-settlement cooperation process (here, the non-settlement cooperation process includes a non-settlement command, etc.) and the acquired authentication information with the cooperation request information. Is output to the payment authentication application 11 in the payment application terminal 1 (non-payment cooperation request).

Step 106C:
The non-payment application cooperation interface module 113 in the payment authentication application 11 extracts each of the non-payment cooperation processing and the authentication information.
Then, the non-settlement application cooperation interface module 113 outputs each of the extracted non-settlement cooperation process and authentication information to the authentication module 114, and requests authentication for whether or not the non-settlement cooperation process can cooperate.

Step 107C:
The authentication module 114 responds to an authentication request from the non-settlement application cooperation interface module 113, and checks with the cooperation data verification server 3 whether the requested non-settlement cooperation process is associated with the authentication information. Ask for.
Thereby, in the cooperation data collation server 3, the cooperation possibility collation unit 31 refers to the coordination processing association table in the collation database 32, and collates whether the requested non-settlement cooperation process is associated with the authentication information. And sends the collation result to the authentication module 114.

Step 108C:
The authentication module 114 determines whether or not the requested non-settlement cooperative processing can be executed based on the collation result from the cooperative data collation server 3.
At this time, when the authentication module 114 indicates that the collation result is associated with the non-settlement cooperation process, the authentication module 114 proceeds the process to step S109C, and on the other hand, indicates that the collation result is not associated with the settlement cooperation process. In this case, the process proceeds to step S110.

Step 109C:
The authentication module 114 requests the non-settlement application cooperation module 116 to execute the non-settlement cooperation process based on the collation result indicating that the non-settlement cooperation process is associated with the authentication information.
Thereby, the non-settlement application cooperation module 116 causes another non-settlement application (for example, the non-settlement application 20_2 in FIG. 3) to execute the cooperation process requested by the non-settlement application 20_1.

Step 110:
If the settlement cooperation process is not associated with the authentication information, the device cooperation process is not associated with the authentication information, or the non-settlement cooperation process is not associated with the authentication information, A notification is output to the application 20_1 indicating that the requested cooperative processing is not cooperable.

・ Application example # 1
FIG. 6 is a conceptual diagram illustrating an application example of the settlement service cooperation system according to the present embodiment.
As described above, for example, the POS application 51, which is the non-settlement application 20, and the sales management application 52, which is an individual business, are activated. Accordingly, the non-settlement application 20 outputs a request for the settlement cooperation process to the cooperation API module 21, and the cooperation API module 21 is activated.

At this time, the cooperation API module 21 determines which payment service (available service) the customer will use when preparing for the payment cooperation process, by selecting the type of the payment service input from the menu screen 53 of the payment application terminal 1. Determined by The menu screen 53 displays all types of payment services available at the store (the user identified by the user identification information).
Then, on the menu screen 53, if the customer selects a credit card, the credit card is set as the payment method, and if the customer selects electronic money, the electronic money is set as the payment method.

Then, the cooperation API module 21 outputs, to the payment application terminal 1, each of the cooperation request information and the authentication information indicating the payment cooperation processing using the selected payment service.
Thereby, the payment authentication application 11 authenticates that the payment cooperation process is associated with the authentication information and that the payment service can be executed. The payment authentication application 11 performs the payment processing by the payment application 10 corresponding to the payment service 54 via the payment application cooperation module 115.
After detecting the completion of the payment processing by the notification from the payment application 10, the payment authentication application 11 returns the processing to the POS application 51 or the sales management application 52 that is the non-payment application 20.

・ Application example # 2
FIG. 7 is a conceptual diagram illustrating another application example of the settlement service cooperation system according to the present embodiment.
As in FIG. 6, for example, the product selection application, which is the non-settlement application 20, is activated, or in a state where the product selection application is activated, the type of the product ordered by the customer, the number of each product type, and the price of the product are input. Accordingly, the product selection application 55 displays the type of the product, the number of each type, and the amount of money on the display screen 55S of the payment application terminal 1, and then outputs a request for the cooperative processing to the cooperative API module 21, and The API module 21 is activated.
Then, a cooperation process capable of cooperation with the cooperation API module 21 is displayed as a menu screen 56.

At this time, the cooperation API module 21 displays all types of payment services available in the store and types of other non-payment applications available. In FIG. 7, another non-settlement application is a POS application.
Then, the cooperation API module 21 outputs to the payment application terminal 1 each of the cooperation request information and the authentication information indicating the non-payment cooperation processing using the selected POS application.

Thereby, the payment authentication application 11 authenticates that the non-payment cooperation process is associated with the authentication information, and that the POS application can be executed as a non-payment service. The payment authentication application 11 activates the POS application 57 via the non-payment application cooperation module 116.
Next, the POS application 57 manages the sales of each of the type of the product, the number of each product, and the amount of the product, and then outputs a request for the payment cooperation process to the cooperation API module 21, and the cooperation API module 21 Is activated.

At this time, the cooperation API module 21 determines which payment service is used by the customer when preparing for the payment cooperation process according to the type of the payment service input from the menu screen (not shown) of the payment application terminal 1. decide. On the menu screen of the payment application terminal 1, all types of payment services available in the store are displayed.
If the customer selects a credit card on the menu screen of the payment application terminal 1, the credit card is used as the payment method, and if the customer selects electronic money, the electronic money is used as the payment method.

Then, the cooperation API module 21 outputs, to the payment application terminal 1, each of the cooperation request information and the authentication information indicating the payment cooperation processing using the selected payment service.
Thereby, the payment authentication application 11 authenticates that the payment cooperation process is associated with the authentication information and that the payment service can be executed. The payment authentication application 11 performs payment processing by the payment application 10 corresponding to the payment service 58 via the payment application cooperation module 115.
After detecting the completion of the payment processing by the notification from the payment application 10, the payment authentication application 11 returns the processing to the POS application 57 which is the non-payment application 20.

  As described above, according to the present embodiment, when performing the cooperation between the payment application 10 and the non-payment application 20, when the non-payment application 20 activates the payment application 10 for the cooperation, the customer who performs the payment Without acquiring the personal information of the payment application, and outputting only the payment amount to the payment application 10 so that the payment application 10 performs the payment. It is possible to prevent personal information for payment from being input, prevent personal information from being stolen, and improve the security function.

  That is, it is necessary that the third party that creates this application incorporates the cooperative API module 21 specified by the manufacturer that created the payment application 10 into the non-payment application 20 that cooperates with the payment application 10. The cooperation API module 21 outputs cooperation request information for the non-settlement application 20 to activate the settlement application 10 to the settlement authentication application 11. The authentication information is the authentication information for authenticating the non-settlement application 20 and the type of the cooperative processing. The authentication information does not include the customer's personal information, and no extra customer's personal information is input to the non-settlement application 20. The security function can be improved without personal information being given to the non-settlement application.

  Further, in the present embodiment, a non-payment application 20 that is installed in the payment application terminal 1 (or in the non-payment application terminal 2 as described later) and performs cooperative processing with the payment application 10 or the same as the payment application 10 Since the non-payment application 20 installed on the terminal is limited to an application that has been approved by the maker that creates the payment application, the operation is not an unknown application. Can be improved.

  In the above-described embodiment, the payment application terminal 1 includes the payment application 10 and the non-payment application 20. However, as illustrated in FIG. 8, the payment application 10 is installed in the payment application terminal 1. Alternatively, the non-payment application 20 may be installed and used in another non-payment application terminal. FIG. 8 is a diagram showing a modification of the settlement service cooperation system according to one embodiment of the present invention.

In FIG. 8, the payment service cooperation system 100 according to the present embodiment includes a payment application terminal 1, a non-payment application terminal 2_1, a non-payment application terminal 2_2, a cooperation data collation server 3, and a download server 4.
Each of the payment application terminal 1, the non-payment application terminal 2_1, the non-payment application terminal 2_2, the cooperation data collation server 3, and the download server 4 are connected by an information communication network 200 including the Internet. When the non-settlement application terminal 2_1 and the non-settlement application terminal 2_2 are collectively referred to, they are referred to as the non-settlement application terminal 2. Further, in the modification of FIG. 8, a description is given as a configuration in which the payment service cooperation system 100 includes two non-payment application terminals 2, but a configuration including one or a plurality of non-payment application terminals 2 may be used.

  In this configuration, the payment authentication application 11 determines whether or not a cooperation request from the non-payment application 20 is possible based on the authentication information included in the information processing cooperation request from the non-payment application terminal 2. In the modification of FIG. 8, the terminal serial number as the authentication information is a number corresponding to a serial number uniquely assigned to each of the non-settlement application terminals 2 at the time of manufacture. It is a number that can be uniquely identified.

The non-settlement application terminal 2 includes a non-settlement application 20 that performs information processing other than the settlement-related processing such as the settlement application 10 described in FIG.
When the non-settlement application 20 is installed in the non-settlement application terminal 2 in the configuration illustrated in FIG. 8, the non-settlement application having a function of not performing a cooperative process with the settlement application 10 or another non-settlement application 20 is installed. You may use it.

  Further, in the present embodiment, the cooperative processing between the payment application and the non-payment application is described. However, the payment application (first payment application) is not limited to the non-payment application but may be another payment application (second payment application). It is also possible to adopt a configuration in which coordination processing is performed with. For example, in the case where the second payment application performs the payment processing of the payment method using the line pay and the first payment application performs the payment processing of the payment method using the electronic money, when the payment using the line payment is performed by the second payment application, If the balance is smaller than the price, a cooperative process for coordinating the payment process such as inquiring the balance of the electronic money by the first payment application may be performed. Here, when the second payment application performs the cooperative processing with the first payment application, it is determined whether or not the second payment application can cooperate, as in the case of the non-payment application in the present embodiment described above.

  Further, a program for realizing the functions of the payment authentication application 11, the non-payment application 20, and the cooperation data collation server 3 in the payment service cooperation system 100 shown in FIGS. 2 and 8 is recorded on a computer-readable recording medium, By causing the computer system to read and execute the program recorded on the recording medium, the cooperative processing between the payment application and the non-payment application may be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices.

The “computer system” also includes a homepage providing environment (or a display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, and a CD-ROM, and a storage device such as a hard disk built in a computer system. Further, a "computer-readable recording medium" refers to a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line, and dynamically holds the program for a short time. In this case, it is also assumed that a program holding a program for a certain period of time, such as a volatile memory in a computer system serving as a server or a client in that case, is included. Further, the above-mentioned program may be for realizing a part of the above-mentioned functions, or may be for realizing the above-mentioned functions in combination with a program already recorded in a computer system.

  The embodiments of the present invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to the embodiments, and includes a design and the like within a range not departing from the gist of the present invention.

1,1-1,1-2,1-3 ... Payment application terminal 2,2_1,2_2 ... Non-payment application terminal 3 ... Cooperation data collation server 4 ... Download server 4_1 ... Application database 4_2 ... Management database 10 ... Payment application 11 ... Payment authentication application 20 ... Non-payment application 21 ... Cooperation API module 31 ... Cooperation availability check unit 32 ... Collation database 100 ... Payment service cooperation system 111 ... Payment application cooperation interface module 112 ... Device cooperation interface module 113 ... Non-payment application cooperation interface Module 114: Authentication module 115: Payment application cooperation module 116: Non-payment application cooperation module Lumpur 211 ... settlement application cooperation calling module 212 ... device cooperation calling module 213 ... non-settlement applications cooperation calling module 400 ... Download Center

Claims (14)

A payment processing unit that performs payment processing related to payment of the price executed by the payment application;
An information processing unit that performs information processing other than the payment processing executed by the non-payment application,
A payment service cooperation system, comprising: an authentication unit that determines whether or not cooperation processing between the payment application and the non-payment application is possible by a determination process performed by an authentication application. The settlement service cooperation system according to claim 1, wherein the authentication application determines whether or not the cooperation processing is possible based on authentication information for authenticating the non-settlement application. The authentication information is one of application identification information for identifying the non-payment application, a terminal serial number of a terminal on which the non-payment application is mounted, and user identification information for identifying a user operating the terminal, or The settlement service cooperation system according to claim 2, wherein the system includes a combination or all of them. 4. The authentication application according to claim 1, wherein the authentication application determines whether cooperative processing between the non-payment application and another non-payment application different from the non-payment application is permitted. 5. Payment service linkage system. A collation database indicating a correspondence between authentication information for authenticating the non-settlement application and the coordination process capable of coordinating in accordance with the authentication information, wherein the authentication information corresponds to a collation request from the authentication application; A collaborative data collation server that outputs the presence or absence of the collaborative processing corresponding to
The settlement service cooperation system according to any one of claims 1 to 4, further comprising: Performing cooperative processing with the payment application further includes a download server that distributes the authenticated non-payment application to a maker that created the payment application,
The download server responds to an inquiry from the payment application, refers to a history of non-payment applications downloaded by the payment application, and notifies other non-payment applications that have not been downloaded. The settlement service cooperation system according to any one of claims 1 to 5. A first payment processing unit that performs payment processing related to payment of the price executed by the first payment application;
A second payment processing unit that performs payment processing other than the payment processing performed by the second payment application;
A payment service cooperation system, comprising: an authentication unit that determines whether or not a cooperation process between the first payment application and the second payment application can be performed by a determination process performed by the authentication application. A payment application that performs a payment process related to payment of a price, a non-payment application that performs information processing other than the payment process, and a payment authentication application that determines whether a cooperative process between the non-payment application and the payment application is possible. A cooperation data collation server that collates the association between the cooperation processing and the authentication information of the non-settlement application by a collation request from a service cooperation system,
A collation database that indicates the correspondence between the authentication information and the coordination process that can cooperate in accordance with the authentication information, and corresponds to a collation request from the payment authentication application, and the coordination process corresponds to the authentication information. A collaborative data collation server that outputs a collation result of collation as to whether or not it is attached. A payment application that performs a payment process related to payment of a price, a non-payment application that performs information processing other than the payment process, and a payment authentication application that determines whether a cooperative process between the non-payment application and the payment application is possible. A payment application terminal used in the service cooperation system,
A payment application terminal, wherein each of the payment application and the payment authentication application is provided. A payment processing step in which the payment application performs payment processing relating to payment of the payment;
An information processing step in which the non-payment application performs information processing other than the payment processing;
An authentication step for performing a process of determining whether or not a cooperative process between the payment application and the non-payment application can be performed by the authentication application. A first payment processing step in which the first payment application performs payment processing relating to payment of the price;
A second payment processing step in which the second payment application performs a payment process other than the payment process;
An authentication application, wherein the authentication application performs a process of determining whether or not cooperative processing between the first payment application and the second payment application is possible. It is a program for making a computer function as a payment service cooperation system,
Said computer,
Payment processing means for performing payment processing relating to payment of the price executed by the payment application,
Information processing means for performing information processing other than the payment processing executed by the non-payment application,
A program for functioning as an authentication unit for determining whether or not the cooperative processing between the payment application and the non-payment application is possible by a determination process performed by the authentication application. It is a program for making a computer function as a payment service cooperation system,
Said computer,
First payment processing means for performing payment processing related to payment of the price executed by the first payment application,
A second payment processing means for performing a payment process other than the payment process executed by the second payment application;
A program for causing the first payment application and the second payment application to function as an authentication unit for determining whether or not a cooperative process is performed by a determination process performed by the authentication application. A payment application that performs a payment process related to payment of a price, a non-payment application that performs information processing other than the payment process, and a payment authentication application that determines whether a cooperative process between the non-payment application and the payment application is possible. A program for causing a computer to function as a cooperation data verification server that outputs payment data that can be used by the non-payment application by a verification request from a service cooperation system,
Said computer,
Refers to a collation database indicating the correspondence between the authentication information for authenticating the non-payment application and the payment data that can be used in correspondence with the authentication information, and responds to a collation request from the payment authentication application, A program for functioning as a means for outputting a collation result of collation as to whether or not the authentication information is associated with the authentication information.

Images