JP7285295B2 - Service providing system, service providing method, and program - Google Patents

Description

The present disclosure relates to a service providing system, a service providing method, and a program.

2. Description of the Related Art Conventionally, technology is known that provides a user with a predetermined service based on a predetermined application. For example, Patent Literature 1 describes a mini app that is activated when selected on a super app. For example, Non-Patent Document 1 describes a technique for displaying a code image for using a payment service and an icon indicating a notification to the user on a user terminal when a payment application is activated. For example, in Non-Patent Document 2, when a payment application is started, a code image for using a payment service and an icon of any point selected from a plurality of points are displayed on the user terminal. It describes a technique that allows

Japanese Patent Publication No. 2021-511592

"PayPay - cashless payment smartphone app", Internet, retrieved October 8, 2021, online, https://paypay.ne.jp/ “FamilyMart Official App Famipay”, Internet, Retrieved October 8, 2021, online, https://www.family.co.jp/famipay.html

However, in the technologies of Patent Document 1 and Non-Patent Document 1, the super app and the mini app are linked. It cannot be said that it is a collaboration that sufficiently enhances the quality of life. The technology of Non-Patent Literature 2 is not originally intended to link multiple applications. It is conceivable that convenience for the user will be enhanced if a process related to another application linked with this application is executed when a reading image of a certain application is read.

One of the purposes of the present disclosure is to improve convenience for users who use multiple apps.

A service providing system according to the present disclosure is a service providing system in which a first service is provided to a user based on a first application, and a second service is provided to the user based on a second application, wherein the first display control means for displaying a predetermined image for reading on the user terminal of the user when the first application is activated in a state in which the application and the second application are linked; and the image for reading of the first application. a second process executing means for executing a second process related to the second service when the is read.

According to the present disclosure, convenience for users who use multiple apps is enhanced.

It is a figure which shows an example of the whole structure of a service provision system. FIG. 10 is a diagram showing an example of a payment app screen before a student ID app is added; FIG. 10 is a diagram showing an example of the flow of adding a student ID application; FIG. 10 is a diagram showing an example of a payment application screen after a student ID application has been added; 3 is a functional block diagram showing an example of functions implemented in the first embodiment; FIG. It is a figure which shows an example of a 1st database. It is a figure which shows an example of a 2nd database. 4 is a flow chart showing an example of processing executed in the first embodiment; FIG. 4 is a flow chart showing an example of processing executed in the first embodiment; FIG. It is a figure which shows an example of the flow in which a point management application is added in 2nd Embodiment. FIG. 10 is a diagram showing an example of a payment application screen after a point management application has been added; FIG. 13 is a diagram showing an example of a payment application screen in the third embodiment; FIG. It is a figure which shows an example of the functional block of a modification. FIG. 10 is a diagram showing an example of a payment application when cooperating with a plurality of point management applications;

[1. First Embodiment]
A first embodiment, which is an example of embodiments of a service providing system according to the present disclosure, will be described.

[1-1. Overall configuration of service providing system]
FIG. 1 is a diagram showing an example of the overall configuration of a service providing system. The service providing system S includes a first server 10 , a second server 20 , a user terminal 30 , a store terminal 40 and a check-in terminal 50 . These are connectable to a network N such as the Internet. The service providing system S only needs to include at least one computer, and is not limited to the example in FIG.

The first server 10 is a server computer. Control unit 11 includes at least one processor. The storage unit 12 includes a volatile memory such as RAM and a nonvolatile memory such as a hard disk. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication. The first server 10 is managed by the provider of the first service.

In the first embodiment, a payment service will be described as an example of the first service. Therefore, the place described as settlement service can be read as the first service. The payment service is a service that provides electronic payment (cashless payment). Payment instruments available in the payment service may be of any type, such as credit cards, electronic money, points, bank accounts, debit cards, wallets, or virtual currency. An example of the first service other than the settlement service will be described in modified examples below.

The second server 20 is a server computer. The physical configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The second server 20 is managed by the provider of the second service.

In the first embodiment, a digital student ID service will be described as an example of the second service. Therefore, the description of the digital student ID service can be read as the second service. The digital student ID service is a service that provides functions related to school life by registering a user's student ID. For example, functions such as display of school attendance certificate, class attendance registration, confirmation of timetable, contact with school, or check-in to facilities such as a library are provided. An example of the second service other than the digital student ID service will be explained in a later modified example.

The user terminal 30 is a user's computer. For example, the user terminal 30 is a smartphone, tablet terminal, wearable terminal, or personal computer. The physical configurations of the control unit 31, the storage unit 32, and the communication unit 33 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The communication unit 13 may include a communication interface capable of NFC (Near Field Communication).

The operation unit 34 is an input device such as a touch panel. The display unit 35 is a liquid crystal display or an organic EL display. The imaging unit 36 includes at least one camera. The IC chip 37 may be a chip of any standard, for example, a FeliCa (registered trademark) chip or a so-called Type A or Type B chip in the contactless standard. A payment service may be used from the IC chip 37 . GPS receiver 38 includes a receiver that receives signals from satellites.

The store terminal 40 is a computer located at the store. For example, the store terminal 40 is a personal computer, tablet terminal, or smart phone. The physical configurations of the control unit 41, the storage unit 42, the communication unit 43, the operation unit 44, and the display unit 45 are the same as those of the control unit 11, the storage unit 12, the communication unit 13, the operation unit 34, and the display unit 35, respectively. be. The communication unit 43 may include a communication interface capable of NFC. The reading unit 46 includes a code reader or camera. The reading unit 46 may be connected to the outside of the store terminal 40 .

The check-in terminal 50 is a computer located at a place where the user checks in. For example, the check-in terminal 50 is a personal computer, tablet terminal, or smart phone. The physical configurations of the control unit 51, the storage unit 52, the communication unit 53, the operation unit 54, the display unit 55, and the reading unit 56 are the control unit 11, the storage unit 12, the communication unit 13, the operation unit 34, and the display unit 35, respectively. , and the reading unit 46 .

The programs stored in each of the first server 10, the second server 20, the user terminal 30, the store terminal 40, and the check-in terminal 50 may be supplied via the network N. In addition, a program stored in an information storage medium can read a computer-readable information storage medium (for example, an optical disk drive or a memory card slot), or an input/output unit for inputting/outputting data with an external device. (eg, USB port).

[1-2. Overview of the first embodiment]
The service providing system S provides users with payment services based on the payment application. A payment application is an example of a first application. Therefore, the part described as the payment application can be read as the first application. A first application is an application for providing a first service. The first application is downloaded and installed in the user terminal 30 . Note that the first application may be of a type that is executed on the first server 10 instead of being installed on the user terminal 30 . The execution result of the first application executed on the first server 10 may be displayed on the user terminal 30 using a browser or the like.

The service providing system S provides the user with a digital student ID service based on the student ID application. A student ID application is an example of a second application. Therefore, the description of the student ID application can be read as the second application. A second application is an application for providing a second service. The second application is downloaded and installed on the user terminal 30 . The second application may be of a type that is executed on the second server 20 instead of being installed on the user terminal 30 . The execution result of the second application executed on the second server 20 may be displayed on the user terminal 30 using a browser or the like.

In the first embodiment, a case where the payment application is a super application and the student ID application is a mini application that can be used from the super application will be taken as an example. A super app is an app that serves as a platform in which multiple apps are integrated. A mini appli is an app that can be used from a super app. Here, it is assumed that the user has already installed the payment application on the user terminal 30, but has not yet added the student ID application.

FIG. 2 is a diagram showing an example of the payment application screen before the student ID application is added. When the user activates the payment application, the top screen G1 of the payment application is displayed on the display unit 35 . For example, a code image C10 for executing payment processing is displayed on the top screen G1. When the code image C10 is read by the reading unit 46 of the shop terminal 40, the settlement process is executed and the settlement completion screen G2 is displayed on the display unit 35. FIG.

The top screen G1 also displays an icon I11 of the mini app in use. When the user selects the icon I11, the mini app starts. The user can add a mini app by selecting the link L12. For example, when the user selects link L12, the display unit 35 displays a selection screen for selecting a mini app. Here, the flow for the user to add the student ID application will be described.

FIG. 3 is a diagram showing an example of the flow of adding a student ID application. For example, the selection screen G3 displays a list of mini-apps that can be added by the user. When the user selects the student ID application from the selection screen G3, the student ID application is downloaded and installed on the user terminal 30. FIG. When the installation of the student ID application is completed, the registration screen G4 for registering the student ID is displayed on the display unit 35. Registering a student ID card means registering the information included in the student ID card in the student ID application.

In the first embodiment, the user's student ID card includes an IC chip on which various information such as the student number is recorded. The user uses the NFC function of the communication unit 33 to scan the student ID card. When the scanning of the student ID card is completed, the user's student ID card is registered in the student ID application, and the registration completion screen G5 is displayed on the display unit 35 . After that, the user can use the digital student ID service by calling the mini-app, student ID app, from the payment app, which is the super app.

FIG. 4 is a diagram showing an example of the payment application screen after the student ID application has been added. A student ID application icon I11 is added as in the top screen G1 of FIG. When the user selects the icon I11 of the student ID application, the top screen G6 of the student ID application is displayed on the display unit 35. FIG. The user can use various functions provided by the digital student ID service from the top screen G6.

For example, when the check-in function is selected from the top screen G6, a code image for checking in to a facility such as a library is displayed. It is assumed that the code image contains information that can identify the user in the digital student ID service. The user holds the code image over the reading unit 56 of the check-in terminal 50 placed at the facility. When the check-in terminal 50 reads the code image and confirms the validity of the user, the user can check-in to the facility.

In the first embodiment, when the user adds the student ID app, the user can use specific functions from the payment app. In the first embodiment, the check-in function of the digital student ID service will be described as an example of this function. This function is not limited to the check-in function as long as it can be used on the condition that the student ID application is added. For example, in addition to the check-in function, other functions such as class attendance registration may be made available from the payment application.

For example, when the user adds a student ID application, the code image C10 includes information indicating that the user is a student of a school whose student ID is registered in the student ID application. With this information, the check-in terminal 50 can identify that the user is a student of a specific school. The user can check in to a facility such as a library based on the information contained in the code image C10 displayed on the top screen G1 of the payment application without displaying the code image on the top screen G6 of the student ID application. become.

As shown in FIG. 4, a notification image I13 indicating that the student ID application has been linked is displayed on the top screen G1 of the payment application. For example, the notification image I13 shows the contents of the functions of the student ID application that can be used in the payment application code image C10. In the first embodiment, the check-in function of the student ID application can be used with the code image C10, so the notification image I13 indicates that the user can check-in at a facility such as a library.

When the user makes the code image C10 read by the reading unit 56 of the check-in terminal 50 placed in a facility such as a school library, the check-in completion screen G7 indicating that the check-in has been executed is displayed on the display unit 35. be done. When the user causes the reading unit 46 of the shop terminal 40 to read the same code image C10, the payment processing is executed and the payment completion screen G2 is displayed on the display unit 35. FIG. The user can use both the payment service and the digital student ID service with the same code image C10. That is, by linking the payment application and the student ID application, it becomes a hybrid code image C10 in which both services can be used.

As described above, in the service providing system S of the first embodiment, by linking the payment application and the student ID application, the check-in terminal 50 can check in to the facility simply by reading the code image C10. As a result, the user can check-in in the same flow as a normal check-in without presenting the student ID card each time at a facility such as a library. Furthermore, without calling the student ID application from the payment application one by one, the function of the digital student ID service can be used by using the code image C10 displayed as the first view of the payment application. Hereinafter, details of the first embodiment will be described.

[1-3. Functions realized in the first embodiment]
FIG. 5 is a functional block diagram showing an example of functions implemented in the first embodiment.

[1-3-1. Functions realized by the first server]
The data storage unit 100 is realized mainly by the storage unit 12 . First providing unit 101 is realized mainly by control unit 11 .

[Data storage part]
The data storage unit 100 stores data necessary for providing settlement services to users. For example, the data storage unit 100 stores a first database DB1.

FIG. 6 is a diagram showing an example of the first database DB1. As shown in FIG. 6, the first database DB1 is a database that stores information about users in the settlement service. This user is a user who has registered for use of the settlement service. For example, the first database DB1 stores user IDs, passwords, user information, code IDs, expiration dates, payment information, mini application information, and usage history information. The information stored in the first database DB1 may be arbitrary information about the user, and is not limited to the example of FIG.

A user ID is an example of user identification information that can identify a user in a payment service. User identification information may be any information, such as information called a user account, email address, or telephone number. For example, the user identification information is letters, numbers, other symbols, or combinations thereof. User ID and password are used to log in to the first service.

User information is information registered by a user. For example, the user information is user's personal information. For example, user information may include the user's name, gender, date of birth, address, phone number, email address, occupation, or a combination thereof. For example, user information may include the name of the organization to which the user belongs. Although a school is described as an example of an organization in the first embodiment, the organization itself may be of any type and is not limited to a school. For example, the organization may be a company, government office, local government, non-profit organization, club, or circle. An organization can also be called an institution. An organization may be multiple organizations.

The code ID is information included in the code image C10. A code ID is information that can identify a user who intends to use a payment service. Code ID is an example of user identification information. In the first embodiment, a case where the code ID is included in the code image C10 will be described, but other user identification information such as a user ID may be included in the code image C10. The term of validity is the point of time after a predetermined period of time from the issuance of the code ID. The expiration date may be of any length, for example, it may be about 1 minute to 1 hour, or it may be about several hours to several days. The code ID does not have to have an expiration date.

For example, the first server 10 issues code IDs so as not to overlap with other code IDs based on predetermined issuing rules. The code ID may not overlap with other code IDs within the valid period, and may overlap with other expired code IDs. A code ID can be issued at any timing. For example, the code ID may be issued when the payment application is activated, when the expiration date has passed, when an operation is performed to update the code ID, or when a predetermined date and time has arrived.

The payment information is information related to the user's payment method. For example, if the payment method is a credit card, the payment information includes the credit card number, expiration date, and holder. If the payment method is electronic money, the payment information includes an electronic money ID that can identify the electronic money and the balance of the electronic money. If the payment instrument is a bank account, the payment information includes the bank account branch name (branch number), account number, and name holder. Similarly, for other payment methods, the payment information may include information corresponding to the payment method. If the payment service allows registration of multiple payment methods, the payment information may include information that enables identification of the payment method set as the payment source.

The mini-app information is information related to mini-apps used by the user. For example, the mini-app information includes a mini-app ID that can identify the mini-app. When the user selects the link L12 to add a mini-app, the mini-app ID of this mini-app is added to the mini-app information. The icon I11 on the top screen G1 is displayed based on the mini app information. In the first embodiment, a case will be described in which usage status information relating to the usage status of mini-apps is stored in the second database DB2, but the usage status information of mini-apps may be stored in the first database DB1. In addition, for example, the mini-app information may include various types of information related to the student ID card registered in the student ID app. This information may be uploaded from the user terminal 30 and registered in the first database DB1 when the student ID application is registered. This information is information contained in the IC card or face of the student ID card, and may be information such as the student number, name, and year of admission, for example.

The usage history information is information related to the usage history of the settlement service. For example, the usage history information includes the date and time of use of the payment service, the place of use, and the amount of use. This user's usage history information is updated each time the user uses the settlement service.

[First provision part]
The first providing unit 101 provides a payment service to the user based on the payment application of the user terminal 30 . In the first embodiment, the first providing unit 101 provides payment services to the user based on the code image C10 displayed on the top screen G1. For example, the store terminal 40 transmits a payment request to the first server 10 when the code image C10 is read by the reading unit 46 . A payment request is a notification for requesting payment processing. For example, the payment request includes the store ID of the store, the terminal ID of the store terminal 40, the code ID acquired from the code image C10, and the amount used.

The first providing unit 101 provides a payment service to the user based on the payment request received by the first server 10 . For example, the first providing unit 101 refers to the first database DB1 and acquires the expiration date of the code ID included in the payment request. If the expiration date of the code ID has passed, the settlement process will not be executed. If the code ID is within the validity period, the first providing unit 101 executes payment processing based on the payment information associated with the code ID. A known process can be used for the settlement process itself. The first providing unit 101 updates the usage history information associated with the code ID based on the execution result of the payment processing.

Since the series of processes described above starts from the payment application, the first providing unit 101 provides payment services to the user based on the payment application. The first providing unit 101 may provide a payment service to the user by directly communicating with the user terminal 30 on which the payment application is installed. For example, when a user selects a store that uses a payment service from a payment application, the first providing unit 101 receives a payment request from the user terminal 30 and provides the payment service to the user. In this case, the user may input the usage amount.

For example, payment processing may be executed by reading a code image displayed on the store terminal 40 with the user terminal 30 . In this case, the code image may include information such as store ID, terminal ID, and usage amount. After reading the code image, the user terminal 30 transmits a payment request to the first server 10 . The flow after the first server 10 receives the payment request may be the same as the flow when the code image C10 is read by the store terminal 40 . Alternatively, for example, the payment process may be executed by reading a code image posted at the store with the user terminal 30 .

[1-3-2. Functions realized by the second server]
The data storage unit 200 is implemented mainly by the storage unit 22 . The second providing unit 201 is implemented mainly by the control unit 21 .

[Data storage part]
The data storage unit 200 stores data necessary for providing the digital student ID service to the user. For example, the data storage unit 200 stores the second database DB2.

FIG. 7 is a diagram showing an example of the second database DB2. The second database DB2 is a database that stores information about users of the digital student ID service. This user is the user who registered the student ID card in the student ID application. For example, the second database DB2 stores school IDs, student numbers, passwords, user information, and usage information. A school ID is an example of school identification information that can uniquely identify a school. The school identification information may be other information such as the school name.

A student number is an example of user identification information that can identify a user in a digital certificate service. A student number is sometimes called a student ID number. This user identification information may be any information, such as a user ID, user account, email address, or phone number. The user identification information for the digital certificate service and the user identification information for the payment service may be the same. A student number and password are used to log into the digital student ID service. A user may be identified by a combination of a school ID and a student number, since a school may have the same student number as another school.

User information means user information registered in the digital student ID service, and is different from user information stored in the first data data DB1, but the meaning of the term user information itself is as described above. The user information stored in the second database DB2 may be information included in the student ID card, or may be information not included in the student ID card. The information included in the student ID card is information stored in the IC chip of the student ID card or information formed on the surface of the student ID card. For example, the user information may include the student number, name, date of birth, department, grade, year of admission, or facial photograph included in the student ID card. The user information may include information on the user's timetable, messages exchanged with the school, and the like.

The usage status information is information about the usage status of the digital student ID service. For example, the usage status information stores information such as the status of attendance at classes, the user's timetable, the content of communication with the school, or the status of check-ins at facilities such as libraries. When the user uses the digital student ID service from the student ID app, the usage information is updated. Usage information may include any information regarding the digital student ID service. For example, the usage status information may include information such as test and report scores, credit acquisition status, or application status for seminars such as job hunting.

[Second provision part]
The second providing unit 201 provides the user with a digital student ID service based on the student ID application of the user terminal 30 . For example, when the student ID application is activated on the user terminal 30, the second providing unit 201 executes predetermined login processing. When the login process is successful, the second providing unit 201 provides the digital student ID service to the user based on the information of the user who logged in to the digital student ID service stored in the second database DB2.

For example, when the user requests display of the school attendance certificate, the second providing unit 201 causes the user terminal 30 to display the school attendance certificate screen based on the department, grade, etc. included in the user information. When the user requests attendance registration for a class, the second providing unit 201 updates the usage status information to indicate that the user has attended the requested class. When the user requests display of the timetable, the second providing unit 201 causes the user terminal 30 to display the timetable screen included in the user information.

For example, when the user requests display of a message, the second providing unit 201 causes the user terminal 30 to display the message included in the user information. When the user requests check-in to a facility such as a library, the second providing unit 201 causes the student ID application to display a code image for check-in. This code may include the user's student number, or may include a temporary ID such as the code ID of a payment app.

[1-3-3. Functions realized by the user terminal]
Data storage unit 300 is realized mainly by storage unit 32 . The display control unit 301 is realized mainly by the control unit 31 .

[Data storage part]
The data storage unit 300 stores data necessary for the user to use each of the payment service and the digital student ID service. For example, the data storage unit 300 stores payment applications and code IDs. The user terminal 30 receives the code ID issued by the first server 10 and records it in its own data storage unit 300 . When the user terminal 30 also receives the expiration date of the code ID, the user terminal 30 also records the expiration date in its own data storage unit 300 .

For example, the data storage unit 300 stores a student ID application and information on student IDs registered in the student ID application. This information may be all or part of the user information stored in the second database DB2, or may be information only indicating whether or not the student ID card has been registered in the student ID application. The data storage unit 300 stores linked information, which will be described later. The data storage unit 300 also stores mini-apps other than the student ID app and information about the mini-apps.

[Display control part]
The display control unit 301 causes the display unit 35 to display the screens described with reference to FIGS. 2 to 4 based on the payment application. For example, the display control unit 301 causes the user terminal 30 of the user to display a predetermined code image C10 when the payment application and the student ID application are linked and the payment application is activated.

A state in which the payment application and the student ID application are linked is a state in which information can be shared between the payment application and the student ID application. At least one of information sharing from the payment application to the student ID application and information sharing from the student ID application to the payment application may be possible. In the first embodiment, the payment application is a super application and the student ID application is a mini application, so adding the student ID application from the payment application corresponds to a state in which the payment application and the student ID application are linked.

For example, the student ID app can use the substantial functions of the digital student ID service only after the student ID is registered. become linked. That is, in the student ID application, which is the second application, completion of some kind of possession authentication may correspond to a state in which the payment application and the student ID application are linked.

Possession authentication verifies what proves the user's legitimacy. In the first embodiment, the item is a student ID card, but any item can be used for possession authentication. For example, an identification card such as a driver's license or personal number card, a credit card, a cash card, or a debit card may be used for possession authentication. Possession authentication itself can use various known methods. For example, a method using an image may be used in addition to the method using NFC described in the first embodiment. For example, a method called eKYC may be used.

Note that the payment application and the student ID application do not have to be in the relationship of the super application and the mini application. In this case, installing both the payment application and the student ID application as separate applications may correspond to a state in which the payment application and the student ID application are linked. Furthermore, after the payment application and the student ID application are installed, the user's operation to agree to link them may correspond to a state in which the payment application and the student ID application are linked. As described above, when these are linked, it becomes a hybrid code image C10 that can use both the payment service and the digital student ID service.

The code image C10 is an example of a read image. Therefore, the code image C10 can be read as a reading image. A read image is an image that can be optically read. The image for reading may be any image, and is not limited to the code image C10 such as a barcode or two-dimensional code. For example, the reading image may be letters, numbers, symbols, photographs, CG, or a combination thereof. For example, the read image may be an image that changes over time. For example, the image for reading may be an image embedded with an electronic watermark, and the student number may be embedded in the electronic watermark.

The display control unit 301 displays the code image C10 including the code ID on the top screen G1 based on the payment application. The code image C10 may contain arbitrary information other than the code ID. When the payment application and the student ID application are linked, the code image C10 may include information indicating that the payment application and the student ID application are linked. Linked information can also be said to be information that allows a user to be identified on the digital student ID service side. When the linked information is also shared with the payment service, the linked information becomes information that allows the user to be identified even on the payment service side.

In the first embodiment, the linked information is the school ID and student number. may be a combination of The linked information may be information that can identify the user on the digital student ID service side, apart from the school ID and student number. For example, a code ID different from the code ID for using the settlement service may be issued by the first server 10 or the second server 20, and the different code ID may be included in the code image C10 as linked information.

Although the code image C10 in FIGS. 2 to 4 includes a barcode and a two-dimensional code, the linked information may be included in at least one of the barcode and the two-dimensional code. For example, if the number of digits of the barcode cannot express both the code ID of the payment service and the linked information, the linked information may be included only in the two-dimensional code. In this case, it is assumed that the reading unit 56 of the check-in terminal 50 can read the two-dimensional code. Alternatively, for example, the code image C10 may include only either a barcode or a two-dimensional code.

In the first embodiment, when the payment application is activated in a state in which the payment application and the student ID application are linked, the display control unit 301 displays the code image C10, the notification image I13 regarding the student ID application linked with the payment application, is displayed on the user terminal 30 . The notification image I13 is an example of a second application image. Therefore, the part described as the notification image I13 can be read as the second application image.

The second application image is an image displayed when the first application and the second application are linked. The second application image is an image from which the second application can be identified. For example, the second application image is the name of the second application or the icon of the second application. The second application image is displayed on the same screen as the code image C10. The second application image may include a description of processing to be executed when code image C10 is read. The second application image may include characters indicating that the first application and the second application are linked.

[1-3-4. Functions realized by store terminals]
Data storage unit 400 is realized mainly by storage unit 42 . The first process execution unit 401 is realized mainly by the control unit 41 .

[Data storage part]
The data storage unit 400 stores data necessary for providing payment services. For example, the data storage unit 400 stores the store ID of the store in which the store terminal 40 is arranged and the terminal ID with which the store terminal 40 can be identified.

[First process execution unit]
The first processing execution unit 401 executes payment processing related to the payment service when the code image C10 of the payment application is read. The settlement process is an example of the first process. Therefore, the part described as payment processing can be read as the first processing. The first process is a process for providing the first service. The first process may have any content corresponding to the first service. An example of the first process in the first service other than the settlement service will be described in a later modified example.

Payment processing is processing for executing payment based on the user's payment method. In the first embodiment, the first server 10 and the store terminal 40 cooperate to execute payment processing. For example, when the code image C10 is read, the store terminal 40 extracts the code ID included in the code image C10 and transmits a payment request including the code ID to the first server 10 . It is assumed that the payment request also includes information such as the store ID, terminal ID, and usage amount. A series of these processes correspond to payment processing. That is, these series of processes correspond to the first process.

Upon receiving the payment request from the store terminal 40, the first server 10 confirms the validity of the code ID included in the payment request. After confirming that the code ID is valid, the first server 10 refers to the first database DB1 and acquires payment information associated with the code ID. The first server executes processing for paying the usage amount included in the payment request based on the acquired payment information. A series of these processes also correspond to payment processing. That is, not only the processing on the store terminal 40 side but also the series of processing performed by the first server 10 correspond to the first processing.

[1-3-5. Functions realized at the check-in terminal]
Data storage unit 500 is realized mainly by storage unit 52 . The second process execution unit 501 is realized mainly by the control unit 51 .

[Data storage part]
The data storage unit 500 stores data necessary for providing the digital student ID service. For example, the data storage unit 500 stores the facility ID of the facility in which the check-in terminal 50 is arranged and the terminal ID by which the check-in terminal 50 can be identified.

[Second process execution part]
The second processing execution unit 501 executes check-in processing related to the digital student ID service when the code image C10 of the payment application is read. The check-in process is an example of the second process. Therefore, the check-in process can be read as the second process. The second processing is processing for providing the second service. The second process may have any content corresponding to the second service. For example, as in the second embodiment, if the second service is a service related to an organization to which the user belongs, the second process is a process related to the organization.

The check-in process is a process for the user to check-in to the facility. In the first embodiment, the second server 20 and the check-in terminal 50 cooperate to execute check-in processing. For example, when the check-in terminal 50 reads the code image C10, the check-in terminal 50 extracts the linked information included in the code image C10 and transmits a check-in request including the linked information to the second server 20 . It is assumed that the check-in request also includes information such as facility ID and terminal ID. A series of these processes correspond to the check-in process. That is, these series of processes correspond to the second process.

Upon receiving the check-in request from the check-in terminal 50, the second server 20 confirms the validity of the linked information included in the check-in request. That is, it is determined whether or not the combination of the school ID and student number included in the linked information exists in the second database DB2. After confirming that the student number is valid, the second server 10 transmits the confirmation result to the check-in terminal 50 . A series of these processes also correspond to the check-in process. That is, not only the process on the check-in terminal 50 side but also the series of processes performed by the second server 20 correspond to the second process. Upon receiving the confirmation result, the check-in terminal 50 executes the processing necessary for check-in. For example, if the facility has an entrance gate, the check-in terminal 50 executes processing to open the entrance gate.

[1-4. Processing executed in the first embodiment]
8 and 9 are flow charts showing an example of processing executed in the first embodiment. This processing is executed by the control units 11, 21, 31, 41 and 51 operating according to the programs stored in the storage units 12, 22, 32, 42 and 52, respectively.

As shown in FIG. 8, when the payment application is activated and the user terminal 30 executes a predetermined login process with the first server 10 (S100), the first server 10 generates a code ID. to the user terminal 30 (S101). Upon receiving the code ID, the user terminal 30 determines whether or not the payment application and the student ID application have been linked (S102). In S<b>102 , the user terminal 30 determines whether or not cooperation completion information is stored in the storage unit 32 .

If it is not determined that the payment application and the student ID application have already been linked (S102; N), the user terminal 30 causes the top screen G1 to display a code image C10 that does not include linked information but includes the code ID (S103). . When the user selects the link L12, the user terminal 30 causes the display unit 35 to display the selection screen G3 (S104). When the user selects the student ID application from the selection screen G3, the user terminal 30 displays the registration screen G4 on the display unit 35 (S105).

The user terminal 30 scans the student ID using the NFC function of the communication unit 33 (S106), and transmits information such as the student number read from the student ID to the second server 20 (S107). When receiving the information such as the student number, the second server 20 confirms its validity (S108). When the validity of the information such as the student number is confirmed, processing for starting the use of the digital student ID service is executed, and the user terminal 30 registers the student ID with the student ID application (S109). In S<b>109 , the user terminal 30 records the linked information in the storage unit 32 .

On the other hand, when it is determined in S102 that the payment application and the student ID application have already been linked (S102; Y), the user terminal 30 displays the code image C10 including the linked information and the code ID, the notification image I13, is displayed on the top screen G1 (S110). The store terminal 40 reads the code image C10 displayed in S103 or S110 (S111). The store terminal 40 transmits a payment request to the first server 10 and executes payment processing with the first server 10 (S112).

The check-in terminal 50 reads the code image C10 displayed in S104 or S111 (S113), and determines whether or not the code image C10 includes cooperation completed information (S114). In S114, the check-in terminal 50 determines whether or not the school ID of the school where the check-in terminal 50 is arranged is included in the linked information. In addition, for example, instead of the school ID, information in a predetermined format may be included in the linked information, and it may be determined whether or not this information is included.

If it is determined that the linked information is included (S114; Y), the check-in terminal 50 transmits a check-in request to the second server 20 and executes check-in processing with the second server 20. (S115). In S115, the second server 20 determines whether or not the combination of the school ID and student number included in the linked information exists in the second database DB2. Check-in is allowed if this combination exists in the second database DB2. If it is not determined that the linked information is included (S114; N), the check-in request is not transmitted and the process ends. In this case, since the payment application and the student ID application are not linked, it is not possible to check-in to a facility such as a library with the code image C10.

Note that when the student ID application is activated on the user terminal 30 and a code image for check-in is displayed, when the code image is read by the check-in terminal 50, the check-in process similar to S115 is executed. . It is assumed that this code image contains information that can be identified as to whether it is displayed by the student ID application. If the check-in terminal 50 has this information, it identifies the code image displayed by the student ID application. It is assumed that the code image C10 also includes information that can be identified as having been displayed by the payment application.

According to the service providing system S of the first embodiment, when the payment application is started while the payment application and the student ID application are linked, the code image C10 is displayed on the user terminal 30, and the code image C10 of the payment application is displayed. If read, perform check-in processing in the digital student ID service. As a result, the function of the digital student ID service can also be used with the code image C10 of the payment application, which increases convenience for users who use multiple applications. For example, there is no need to call the student ID app from the payment app. For example, when the code image C10 is displayed in the first view of the payment application, a plurality of services can be used simply by displaying the first view of the payment application, which enhances user convenience.

Further, the service providing system S executes payment processing when the code image C10 of the payment application is read. As a result, both the payment service and the digital student ID service can be used with a single code image C10, which further enhances convenience for the user. For example, since the same operation is required when using the payment service and when using the digital student ID service, the operation burden on the user can be reduced.

Further, when the payment application is activated in a state in which the payment application and the student ID application are linked, the service providing system S sends the code image C10 and the notification image I13 regarding the student ID application linked with the payment application to the user terminal 30. to display. As a result, by checking the notification image I13, the user can understand that the payment application and the student ID application are linked, which further enhances the user's convenience.

In the service providing system S, the first service is a payment service, the second service is a digital student ID service related to schools, and the second process is a process related to schools. As a result, payment services and digital student ID services can be effectively linked. For example, if the user's school recommends the use of a student ID application, even if the user does not use the payment application, it can be conveniently used by installing the payment application on the user terminal 30. The user can be motivated to install the payment application on the terminal 30 . Therefore, it is possible to promote the use of settlement services.

In the service providing system S, the payment application is a super application, and the student ID application is a mini application that can be used from the super application. As a result, the super app and the mini app can be effectively linked. Compared to the case where the payment application and the student ID application are separate applications, it is easier to link the applications. Since the user can manage mini-apps such as a student ID app from the payment app, which is a super app, it becomes easier to manage the apps on the user terminal 30 .

[2. Second Embodiment]
In the first embodiment, the first service is the settlement service and the second service is the digital student ID service, but each of the first service and the second service may be any service. In the second embodiment, a case will be described where the first service is a payment service and the second service is a point management service. The second server 20 is a server computer for providing point management services. In the second embodiment, the check-in terminal 50 can be omitted. In the second embodiment, descriptions of the same points as in the first embodiment are omitted.

The point management service is a service for managing points owned by users. The point management service manages the points in the store used by the user or in the group of stores. For example, when a user becomes a member of a point management service, by presenting a point card at a store, points corresponding to the amount spent at the store can be earned. The user can use his/her own points for payment at the store. By using the point management application, which is the second application, the user can use the point management service without presenting the point card. In the second embodiment, a case where the point management application is a mini application will be described.

FIG. 10 is a diagram showing an example of the flow of adding a point management application in the second embodiment. As shown in FIG. 10, when the user selects the link L12 on the top screen G1 in a state in which no point management application has been added, the display unit 35 displays a selection screen G3 from which a point management application can be selected. When the user selects the point management application, the display unit 35 displays a registration screen G8 for registering the point card owned by the user.

When the user inputs the point card number written on the point card from the registration screen G8 to register the point card, the completion screen G9 is displayed on the display unit 35. FIG. The second server 20 or another server computer stores a database that stores information such as point card numbers and point balances. If the point card number entered by the user exists in this database, the point card Registration is complete. This database may be the second database DB2. Registration of a point card may require input of information such as a name. Like the student ID card of the first embodiment, the point card may be registered using NFC.

FIG. 11 is a diagram showing an example of the payment application screen after the point management application is added. As in the top screen G1 of FIG. 11, an icon I11 of the point management application is added. When the user selects the icon I<b>11 of the point management application, the top screen G<b>10 of the point management application is displayed on the display unit 35 . The user can use various functions provided by the point management service from the top screen G10.

For example, when the point card display function is selected from the top screen G10, a code image including a point card number is displayed. The user holds the code image over the reading unit 46 of the shop terminal 40 of the shop that accepts points. When the store terminal 40 reads the code image and confirms the legitimacy of the point card number, the user can use points at the store and accumulate points according to the amount used at the store. For these processes themselves, processes of known point management applications can be applied.

In the second embodiment, when the user adds the point management application, the user can use specific functions from the payment application. In the second embodiment, a point use function will be described as an example of this function. This function may be any function as long as it is a function that can be used on the condition that the point management application is added. For example, when the user adds a point management application, the code image C10 includes linked information indicating that the payment application and the point management application are linked. For example, the linked information may be a point card number or a code ID issued by the point management service.

The store terminal 40 can identify the user as a member of the point management service based on the linked information. The user can use the points at the store based on the information included in the code image C10, or accumulate points according to the amount spent at the store, without displaying the code image from the top screen G10 of the point management application. be able to As shown in FIG. 11, a notification image I14 indicating the type of point card and the point card number is displayed on the top screen G1 of the payment application. When the user causes the reading unit 46 of the store terminal 40 to read the code image C10, the display unit 35 displays a settlement completion screen G2 indicating that points have been obtained.

In the second embodiment, the second process execution unit 501 is realized mainly by the control unit 41 of the store terminal 40. FIG. The second processing is processing related to points. This process is a process of acquiring points or a process of consuming points. Hereinafter, this processing will be referred to as point processing. Known processing can be applied to the point processing itself. For example, the second process execution unit 501 communicates with the second server 20 to execute a process of increasing the user's point balance or execute a process of consuming the user's point balance.

For example, when the store terminal 40 reads the code image C10, the store terminal 40 transmits a payment request to the first server 10 and a point use request to the second server 20 . The point use request is a request to execute point processing. For example, the point use request includes the store ID, the terminal ID, and the amount of points. The amount of points is the amount of points spent on payment or the amount of points that can be earned on payment. The point usage request may include a payment amount instead of the amount of points. In this case, the earned amount of points corresponding to the payment amount may be calculated on the second server 20 side.

According to the service providing system S of the second embodiment, when a point card is registered in the point management application, both payment processing and point processing can be executed at once simply by reading the code image C10 with the store terminal 40. . As a result, points can be processed in the same flow as the normal payment process without the need for the user to present the point card each time at the store or select the icon I11 of the point management application from the top screen G1 of the payment application. can also be executed, which enhances the user's convenience.

[3. Third Embodiment]
In the second embodiment, the case where the payment application and the point management application cooperate with each other has been described, but the user terminal 30 does not have to have the point management application. In the third embodiment, a case will be described in which a plurality of user's point cards are registered in a payment application. The second server 20 may exist for each point management service provider. Therefore, a plurality of second servers 20 may exist. In the third embodiment, descriptions of the same points as in the first and second embodiments are omitted.

In the third embodiment, the payment application is an example of the predetermined application, and the payment service is an example of the predetermined service. Therefore, the part described as a payment application can be read as a predetermined application. The place described as settlement service can be read as a predetermined service. In the third embodiment, a case where the payment application is not the super application will be described, but the payment application of the third embodiment may also be the super application.

FIG. 12 is a diagram showing an example of a payment application screen according to the third embodiment. A plurality of buttons B15 for registering a point card in the payment application are displayed on the top screen G1 of the payment application. When the user selects the button B15, an input screen G11 for inputting a point card number is displayed on the display section 35. FIG. When the user inputs the point card number from the input screen G11, the second server 20 confirms the validity of the point card number. Once the legitimacy of the point card number is confirmed, the point card is registered in the payment application. The flow of this validity confirmation may be the same as in the second embodiment.

When a point card is registered in the payment application, an icon I16 is displayed on the top screen G1. The icon I16 is similar to the notification image I13 described in the second embodiment, but since there is no point management application in the third embodiment, the icon I16 indicates the type of point card registered in the payment application. The point balance and point card number may be displayed on the top screen G1. When the code image C10 is read by the reading unit 46 of the shop terminal 40, payment processing and point processing are executed. This process itself may be the same as in the second embodiment.

As shown in FIG. 12, when the user registers multiple point cards in the payment application, multiple icons I16 are displayed on the top screen G1. Of the plurality of point cards registered in the settlement application, point processing is executed for the point card that can be used at the store visited by the user. As shown in FIG. 13, in a store where a plurality of point cards can be used at the same time, point processing for each of the plurality of point cards is executed. A plurality of point cards can be used, but if the store allows only one of them, an arbitrary point card is selected and point processing is executed.

The display control unit 301 of the third embodiment displays the code image C10 on the user terminal 30 of the user when the payment application is activated. When the code image C10 of the payment application is read, the second processing execution unit 501 executes point processing corresponding to the location where the code image C10 is read, among the plurality of points held by the user. The display of the code image C10 and the point processing are different from the second embodiment in that they are not performed when the payment application and the point management application cooperate, but other points are the same as in the second embodiment. be. The details of the point processing corresponding to the location where the code image C10 is read will be described in modification 1 below.

According to the service providing system S of the third embodiment, when the code image C10 displayed on the user terminal 30 is read, the point corresponding to the location where the code image C10 was read out of the plurality of points held by the user Execute the processing for the points to be done. This eliminates the need for the user to carry multiple point cards and the need to install multiple point management applications in the user terminal 30, thereby enhancing user convenience. In addition, the user can accumulate points that can be accumulated at the shop by scanning the code image C10 at the shop without being conscious of which points are accumulated at which shop, or can use the points that can be used at the shop. can be used.

[4. Modification]
The present disclosure is not limited to the embodiments described above. Modifications can be made as appropriate without departing from the gist of the present disclosure.

FIG. 13 is a diagram illustrating an example of functional blocks of a modification. Selection unit 302 , match determination unit 303 , notification unit 304 , information provision unit 305 , and restriction unit 306 are each realized mainly by control unit 31 . In the modified example described below, the case where the payment application and the point management application are linked as in the second embodiment will be taken as an example. good. In addition, for example, a plurality of applications may not cooperate as in Modification 9 described later, or applications of other services may cooperate with each other as in other Modifications described later.

[4-1. Modification 1]
For example, multiple point management services corresponding to multiple point management applications may be provided. That is, the payment application may cooperate with a plurality of point management applications. In Modification 1, three point management applications are taken as an example, but the number of point management applications may be two, or four or more. The payment application can cooperate with any number of point management applications. In modification 1, as in the second embodiment, the case where three point management applications are mini applications will be described.

For example, an e-commerce service point card, a convenience store point card, and a drug store point card are registered in three point management applications. These point cards may be usable only at a single store or group, but in Modification 1, they are assumed to be usable at various member stores of the point cards. Therefore, when the user does shopping at a certain store, there are cases where multiple point cards can be used at this store. In this case, some stores require the user to select one of a plurality of point cards, while other stores allow points to be accumulated on multiple point cards at the same time. Various well-known mechanisms can be applied to the mechanism itself of these points.

FIG. 14 is a diagram showing an example of a payment application when linked with a plurality of point management applications. As shown in FIG. 14, when the cooperation between the payment application and the three point management applications is completed, the display control unit 301 displays the code image C10 and a plurality of icons corresponding to the plurality of point management applications associated with the payment application. I17A to I17C are displayed on the user terminal 30. Hereinafter, when the icons I17A to I17C are not distinguished, they will simply be referred to as icon I17. In Modification 1, the icon I17 corresponds to the second application image. Therefore, the portion described as icon I17 can be read as the second application image.

The icon I17 is an image that can identify the point management application and the point management service. That is, the icon I17 is an image from which the point type can be identified. For example, icon I17A is the logo of an e-commerce service that offers the first point. Icon I17B is the logo of a convenience store that offers the second point. Icon I17C is the drugstore logo that provides the third point.

The flow of adding individual point management applications is the same as in the second embodiment. For example, when the user selects a point management application to be added from the payment application selection screen G3 and registers a point card, addition of the point management application is completed. When the point management application is added, an icon I11 for starting the point management application and an icon I17 indicating points that can be accumulated when the code image C10 is read are displayed.

The second process executing unit 501 executes the second process of the point management service corresponding to the location where the code image C10 is read, among the plurality of point management services. The location is a location where payment services are available, and may be, for example, a store, event venue, shopping mall, public facility, or location with vending machines. In Modified Example 1, a store will be described as an example of this place. A store terminal 40 is arranged in each store. It is assumed that the store terminal 40 stores information for identifying point management services available at the store.

In Modified Example 1, a convenience store and a drug store will be described as examples of stores. E-commerce service points shall be available at both convenience stores and drug stores. Convenience store points cannot be used at drug stores, but can be used at convenience stores. Drugstore points cannot be used at convenience stores, but can be used at drugstores.

Furthermore, at the convenience store, it is assumed that both electronic commerce service points and convenience store points can be accumulated at the same time for one purchase. In a drugstore, it is not possible to accumulate both electronic commerce service points and convenience store points in a single purchase. In other words, at the drugstore, it is necessary to select either points for electronic commerce services or points for convenience stores.

For example, code image C10 includes a code ID and three point card numbers. The code image C10 also includes information capable of identifying the types of points indicated by the three point card numbers.

For example, when the code image C10 is read by the store terminal 40 of the convenience store, the store terminal 40 of the convenience store converts the e-commerce service points and the convenience store points based on the information extracted from the code image C10. Identify what the user has. Since drug store points cannot be used at the convenience store, the store terminal 40 of the convenience store ignores the drug store point card number included in the code image C10. The store terminal 40 of the convenience store executes the point processing for accumulating both points while executing the payment processing based on the code ID included in the code image C10.

For example, when the code image C10 is read by the store terminal 40 of the drug store, the store terminal 40 of the drug store converts the e-commerce service points and the drug store points based on the information extracted from the code image C10. Identify what the user has. Since convenience store points cannot be used at the drug store, the drug store store terminal 40 ignores the convenience store point card number included in the code image C10. The store terminal 40 of the drugstore executes the point processing for accumulating any of these points while executing the settlement processing based on the code ID included in the code image C10.

In the drugstore, the user may verbally inform the clerk which of the electronic commerce service points and the drugstore points is to be used. In this case, an image for selecting either the electronic commerce service points or the drugstore points is displayed on the display unit 45 of the store terminal 40 of the drugstore, and the clerk or the user selects one of them. You can choose. When the payment processing is executed, the point processing of the selected one of the electronic commerce service points and the drug store points is executed.

As described above, the display control unit 301 of Modification 1 causes the user terminal 30 to display a plurality of icons I17 regardless of where the code image C10 is read. That is, the display control unit 301 causes the user terminal 30 to display not only the icon I17 indicating points that can be used at the location where the code image C10 is read, but also the icon I17 that indicates points that cannot be used at this location.

According to Modification 1, the code image C10 and the plurality of icons I17 corresponding to the plurality of point management applications linked with the payment application are displayed on the user terminal 30 . This eliminates the need for the user to carry around a plurality of point cards, thereby enhancing the user's convenience. In addition, the user can accumulate points that can be accumulated at the shop by scanning the code image C10 at the shop without being conscious of which points are accumulated at which shop, or can use the points that can be used at the shop. can be used. Since the user does not have to call each point management application one by one, the user's convenience is improved in this respect as well.

Further, among the plurality of point management services, the plurality of icons I17 are displayed on the user terminal 30 regardless of the location where the code image C10 is read. As a result, the user can understand the point management application linked to the payment application by looking at the icon I17, thereby enhancing user convenience.

[4-2. Modification 2]
For example, the display control unit 301 determines the display order of the plurality of icons I17 based on the usage status of each of the plurality of point management services, and displays the plurality of icons I17 on the user terminal 30 based on the determined display order. may be displayed in This usage status is the usage status indicated by the usage status information stored in the second database DB2. In the case of the point management service, the usage information includes the date and time of use, the place of use, and the amount of points. The usage information may include content corresponding to the second service. For example, if the second service is a digital student ID service, the usage status information is as described in the first embodiment.

The date and time of use is the date and time when the user used the point management service. For example, the date and time when the user accumulated points or the date and time when the user consumed points corresponds to the usage date and time. The place of use is the place where the user used the point management service. For example, a store where the user has accumulated points through shopping or a store where the user has consumed points while shopping corresponds to the place of use. The amount of points is the increase/decrease amount of points when using the point management service. For example, the amount of points acquired by the user through shopping or the amount of points consumed by the user through shopping corresponds to the amount of points. The amount of points may refer to the balance of points.

For example, the display control unit 301 may determine the display order of the icons I17 so as to be in descending order or ascending order of the number of times of use or frequency of use. For example, the display control unit 301 may determine the display order of the icons I17 so as to be in descending or ascending order of the length of continuous use. For example, the display control unit 301 may determine the display order of the icons I17 so as to be in descending order or ascending order of the total amount of points. The number of times of use, the frequency of use, and the total amount of points may be aggregated over the entire past period, or may be aggregated over a recent partial period (for example, about the last half year). It should be noted that the user terminal 30 is assumed to be able to acquire usage status information of individual points from the second server 20 as appropriate.

According to Modification 2, the plurality of icons I17 are displayed on the user terminal 30 based on the display order determined based on the usage status of each of the plurality of point management services. This makes it easier for the user to grasp the usage status from the display order of the icons I17. For example, by preferentially displaying the icon I17 of the point frequently used by the user, the visibility of the icon I17 is also enhanced.

[4-3. Modification 3]
For example, the display control unit 301 determines the display mode of the plurality of icons I17 based on the usage status of each of the plurality of point management services, and displays the plurality of icons I17 on the user terminal based on the determined display mode. 30 may be displayed. The meaning of this usage status is as described in Modification 2. The display mode is the appearance of the icon I17. In Modified Example 3, the case where the size of the icon I17 corresponds to the display mode will be described, but the display mode may be any other element. For example, the shape, brightness, color, or effect of the icon I17 may correspond to the display mode.

For example, the display control unit 301 may make the icon I17 larger as the number of uses or the frequency of use increases. The display control unit 301 may make the icon I17 larger as the continuous use period is longer. The display control unit 301 may make the icon I17 larger as the total amount of points increases. Similarly, for other display modes, it is sufficient that the relationship between the usage status and the display mode of the icon I17 is determined in advance. The display control unit 301 may determine the display mode of the icon I17 corresponding to the point management service so that the display mode corresponds to the usage status of each point management service.

According to Modification 3, a plurality of icons I17 are displayed on the user terminal 30 based on the display mode determined based on the usage status of each of the plurality of point management services. This makes it easier for the user to grasp the usage status from the display order of the icons I17. For example, by prominently displaying the icon I17 of points frequently used by the user, the visibility of the icon I17 is also enhanced.

[4-4. Modification 4]
For example, the service providing system S may further include a selection unit 302 that selects at least one of a plurality of point management applications based on the situation when the payment application is activated. This situation is a situation that the user terminal 30 can detect. For example, the location of the user when the payment application is activated or the time when the payment application is activated correspond to the situation when the payment application is activated.

In Modified Example 4, it is assumed that situations in which the point management application can be used are limited. For example, as described in Modification 1, the point management application for electronic payment services can be used at both convenience stores and drug stores, but the point management application for convenience stores can only be used at convenience stores. Drugstore point management apps can only be used at drugstores.

In addition, for example, there may be a point management application that can be used only at a certain specific time. For example, there may be a point management application that can be used only for shopping during the day and a point management application that can be used only for shopping at night. In addition, for example, there may be a point management application that can be used only for shopping on weekdays and a point management application that can be used only for shopping on weekends. Which point management application corresponds to which situation should be determined in advance.

For example, the selection unit 302 selects at least one point management application based on user location information regarding the user's location when the payment application is activated. The user position information may be information that can be acquired by the user terminal 30 . In Modified Example 4, a case will be described in which user position information is acquired based on the signal received by the GPS receiver 38, but various known positioning methods can be used as the user position information acquisition method itself. For example, user location information may be acquired using wireless LAN access point information or mobile base station information.

The selection unit 302 estimates which store the user is at based on the user location information. The location of the store may be recorded in the user terminal 30 in advance, or may be recorded in the first server 10 or the second server 20 . The selection unit 302 may inquire of the first server 10 or the second server 20 which store the user is at. A selection unit 302 selects a point management application that can be used at the estimated store. Which point management application can be used at which store may be recorded in the user terminal 30 in advance, or may be recorded in the first server 10 or the second server 20 . The selection unit 302 may inquire of the first server 10 or the second server 20 which point management applications are available.

The display control unit 301 causes the user terminal 30 to display at least one point management application icon I17 selected by the selection unit 302 . For example, the display control unit 301 may prevent the user terminal 30 from displaying the icon I17 of the point management application that was not selected by the selection unit 302 . In addition, for example, the display control unit 301 gives priority to the icon I17 of at least one point management application selected by the selection unit 302 over the icon I17 of the point management application not selected by the selection unit 302. It may be displayed on the terminal 30 . Preferential means that the display order is first, or that the display mode is conspicuous. The conspicuous display mode means that the size is large, the color is chromatic, the brightness is bright, and the effect such as blinking and expansion/contraction is provided.

According to Modification 4, the user terminal 30 displays at least one point management application icon I17 selected based on the situation when the payment application is activated. For example, when a large number of icons I17 are displayed, the visibility deteriorates, but since it is possible to hide the icon I17 of the point management application that cannot be used in the current situation, the visibility of the icon I17 is improved.

Also, at least one point management application is selected based on user location information regarding the location of the user when the payment application is activated. As a result, it is possible to display the icon I17 according to the location where the user is, so that the visibility of the icon I17 is enhanced. The user can easily understand the points that can be used at the current location, so the user's convenience is enhanced.

[4-5. Modification 5]
For example, as described somewhat in Modification 1, the second processing execution unit 501 may execute point processing for each of a plurality of point management services when the code image C10 of the payment application is read. As in the convenience store described in Modification 1, when both electronic commerce service points and convenience store points can be accumulated and consumed at the same time, the second processing execution unit 501 When the code image C10 is read, the electronic commerce service point processing and the convenience store point processing are executed. For example, the second processing execution unit 501 communicates with the second server 20 that manages the points of the electronic commerce service to execute point processing of the electronic commerce service, and communicates with the second server 20 that manages the points of the convenience store. Execute convenience store point processing.

According to Modification 5, when the code image C10 of the payment application is read, the point processing for each of the plurality of point management services is executed. As a result, by reading the code image C10, it is possible to accumulate a plurality of points at the same time or consume a plurality of points at the same time, so that the user's convenience is enhanced.

[4-6. Modification 6]
For example, when using a certain service, the user may not notice that old user information has been registered. In this regard, since the payment application and the point management application are linked, if the user information registered with each other does not match, the user may be prompted to change it. The meaning of the user information is as explained in the first embodiment. The service providing system S of Modification 6 includes a match determination unit 303 and a notification unit 304 .

The match determination unit 303 determines whether or not the first user information of the user registered in the payment service matches the second user information of the user registered in the point management service. The first user information is user information registered in the first database DB1. The second user information is user information registered in the second database DB2. The match determination unit 303 may determine complete match or partial match. The matching determination unit 303 may determine whether all items included in the user information that can be compared match, or may determine whether only some items such as an address or telephone number match.

When the first user information and the second user information do not match, the notification unit 304 notifies the user to change at least one of the first user information and the second user information. Any medium may be used for this notification, and may be, for example, a notification within a payment application, a notification within a point management application, e-mail, or SMS. This notification includes a message prompting the user to change the information. Information may be included in the notification that identifies which items of user information do not match.

According to Modified Example 6, when the first user information of a user registered in the payment service and the second user information of a user registered in the point management service do not match, the first user information and the first 2. Send a notification prompting the user to change at least one of the user information. Thereby, the latest user information can be registered in the payment service and the point management service.

[4-7. Modification 7]
For example, the service providing system S may further include an information providing unit 305 that provides predetermined information on the point management application based on information on the user associated with the payment service. The information about the user may be user information stored in the first database DB1, or may be usage history information. Alternatively, for example, other information associated with the user ID in the settlement service may be used. Other information may be hotel reservation information in a travel reservation service linked with a payment service or ticket reservation information in a ticket reservation service. Modification 7 describes a case where the information about the user is hotel reservation information in a travel reservation service that cooperates with a payment service. It is assumed that the first server 10 can acquire reservation information from a travel reservation service server. In this case, it is assumed that the user ID is shared between the payment service and the travel reservation service so that it is possible to specify which user's reservation information belongs to.

The predetermined information provided by the information providing unit 305 may be arbitrary information, for example, the reservation information itself, or information that the user is likely to be interested in based on the reservation information. . For example, the relationship between reservation information and information to be provided to the user is stored in the data storage unit 100, and the information providing unit 305 provides information according to the reservation information to the user. For example, the information providing unit 305 provides the user with recommended information about shops near the location indicated by the reservation information on the point management application. The information providing unit 305 provides the user with coupon information available on the date and time indicated by the reservation information on the point management application. In addition, for example, the information providing unit 305 provides the user with information on products presumed to be required at the facility indicated by the reservation information on the point management application. Arbitrary media such as banner advertisements can be used to provide information.

According to Modification 7, predetermined information is provided on the point management application based on the information about the user associated with the payment service. As a result, it is possible to provide information that interests the user, thereby enhancing the user's convenience. By providing information that promotes the use of point management applications or payment applications, the use of these applications can be promoted.

[4-8. Modification 8]
For example, the service providing system S may further include a restriction unit 306 that restricts functions available from the point management application based on user location information regarding the user's location obtained using the payment application. The user position information is as described in Modification 4. The user location information may be acquired when the payment application is activated. It is assumed that the relationship between the user's position and the functions available from the point management application are stored in advance in the data storage unit 100 . As described in Modification 4, this relationship may be information such as the location and time of a store where points can be used. The function to be restricted may be any function of the point management application, for example, the code image display function. In this case, the restriction unit 306 may restrict the display of code information by the point management application only when the user is near a store where points can be used.

In addition, for example, if the second service is the digital student ID service as in the first embodiment, the restriction unit 306 may use the attendance registration function of the digital student ID service only when the user is near the school. may be restricted so that it cannot be used. That is, when the user is away from the school, even if the user tries to register for attendance by sending a screen shot of the code image used for attendance to a friend, such attendance registration will not be possible. may be restricted so that In this case, the restriction unit 306 may restrict display of the code image.

According to Modification 8, the functions available from the point management application are restricted based on the user location information regarding the user's location obtained using the payment application. As a result, convenience for the user can be enhanced, and unauthorized use of a specific function can be prevented.

[4-9. Modification 9]
For example, modification 1-6 may be applied to the third embodiment. It should be noted that Modified Example 7-8 presupposes a point management application, and thus is not applied to a mode that can be completed only with a payment application as in the third embodiment. For example, modification 1 may be applied to the third embodiment to display icons I16 for each of a plurality of point cards registered in the payment application. Modification 2 may be applied to the third embodiment, and the display order of icons I16 may be determined based on the usage status of each of a plurality of point cards. Modification 3 may be applied to the third embodiment, and the display mode of the icon I16 may be determined based on the usage status of each of a plurality of point cards.

By applying modification 4 to the third embodiment, one of the plurality of point cards may be selected based on the situation when the payment application is activated, and the icon I16 of the selected point card may be displayed. . The fifth modification may be applied to the third embodiment, and the point processing for each of the plurality of points may be executed when the code image C10 is read. By applying modification 6 to the third embodiment, it is determined whether or not the user information of each of a plurality of point cards match, and if it is determined that they do not match, a request is made to change the user information. may be

[4-10. Other Modifications]
For example, the modified examples described above may be combined.

For example, each of the first service and the second service may be any service. For example, each of the first service and the second service may be electronic commerce service, administrative service, financial service, communication service, insurance service, video distribution service, point management service, or SNS (Social Networking Service). The first service and the second service may be services of different types, or may be services of the same type. Alternatively, for example, the first service may be a service for collectively managing a plurality of second applications. In this case, the first application is an application for managing multiple mini-apps. For example, the code image displayed by the first application may enable use of at least one function of a plurality of second applications that cooperate with the first application.

For example, the first server 10 and the second server 20 may not be separated, and each function may be realized by one computer. For example, the functions described as being realized by each of the first server 10, the second server 20, the user terminal 30, the store terminal 40, and the check-in terminal 50 may be shared by a plurality of computers. Each function may be realized by at least one computer.

S service providing system, N network, 10 first server, 20 second server, 30 user terminal, 40 store terminal, 50 check-in terminal, 11, 21, 31, 41, 51 control section, 12, 22, 32, 42 , 52 storage unit, 13, 23, 33, 43, 53 communication unit, 34, 44 operation unit, 35, 45 display unit, 36 photographing unit, 37 IC chip, 38 GPS receiving unit, 46, 56 reading unit, G1 top Screen, G2 payment completion screen, G3 selection screen, G4 registration screen, G5 registration completion screen, G6 top screen, G7 check-in completion screen, G8 registration screen, G9 completion screen, 100 data storage unit, 200 data storage unit, 300 data storage unit 301 display control unit 302 selection unit 303 match determination unit 304 notification unit 305 information provision unit 306 restriction unit 400 data storage unit 401 first process execution unit 500 data storage unit 501 second Process execution part, B15 button, C10 code image, G10 top screen, G11 input screen, I11, I17, I17A, I17B, I17C icon, I13 notification image, I14 notification image, L12 link.

Claims (18)

A service providing system in which a first service is provided to a user based on a first application and a second service is provided to the user based on a second application,
When the first application is activated in a state in which the first application and the second application are linked, the user terminal of the user receives first identification information capable of identifying the user with the first service; display control means for displaying a reading image including second identification information capable of identifying the user in the second service ;
a second process executing means for executing a second process related to the second service based on the second identification information when the reading image of the first application is read;
service delivery system, including The service providing system further includes first processing executing means for executing a first processing related to the first service based on the first identification information when the reading image of the first application is read. ,
The service providing system according to claim 1. The display control means controls, when the first application is activated in a state in which the first application and the second application are linked, a second display related to the reading image and the second application linked with the first application. displaying an application image on the user terminal;
The service providing system according to claim 1 or 2. providing a plurality of the second services corresponding to the plurality of the second applications;
The display control means causes the user terminal to display the reading image and the plurality of second application images corresponding to the plurality of second applications linked with the first application.
The service providing system according to claim 3. The second process executing means executes the second process of the second service according to the location where the image for reading is read, among the plurality of second services,
The display control means causes the user terminal to display the plurality of second application images regardless of the location.
The service providing system according to claim 4. The display control means determines a display order of the plurality of second application images based on the usage status of each of the plurality of second services, and determines the display order of the plurality of second application images based on the determined display order. displaying an application image on the user terminal;
The service providing system according to claim 4 or 5. The display control means determines a display mode of the plurality of second application images based on the usage status of each of the plurality of second services, and controls the plurality of second application images based on the determined display mode. displaying an application image on the user terminal;
A service providing system according to any one of claims 4 to 6. The service providing system further includes selection means for selecting at least one of the plurality of second applications based on the time when the first application is started,
The display control means causes the user terminal to display the second application image of at least one second application selected by the selection means.
The service providing system according to any one of claims 4-7. The service providing system further includes selection means for selecting at least one of the plurality of second applications based on user location information regarding the location of the user when the first application is activated,
The display control means causes the user terminal to display the second application image of at least one second application selected by the selection means.
The service providing system according to any one of claims 4-7 . providing a plurality of the second services corresponding to the plurality of the second applications;
The second process executing means executes the second process of each of the plurality of second services when the reading image of the first application is read.
The service providing system according to claims 1-9. The service providing system is
match determination means for determining whether the first user information of the user registered in the first service and the second user information of the user registered in the second service match;
a notifying means for notifying to prompt a change of at least one of the first user information and the second user information when the first user information and the second user information do not match;
11. The service providing system according to any one of claims 1 to 10, further comprising: The service providing system further includes information providing means for providing predetermined information on the second application based on the information about the user associated with the first service,
A service providing system according to any one of claims 1 to 11. The service providing system further includes restriction means for restricting functions available from the second application based on user location information regarding the location of the user obtained using the first application.
A service providing system according to any one of claims 1 to 12. the first service is a payment service;
the second service is a service related to an organization to which the user belongs;
The second process is a process related to the tissue,
A service providing system according to any one of claims 1 to 13. the first service is a payment service;
The second service is a service for managing points owned by the user,
The second process is a process related to the point,
A service providing system according to any one of claims 1 to 14. the first app is a super app;
the second app is a mini app that can be used from the super app;
A service providing system according to any one of claims 1 to 15. A service providing method in which a first service is provided to a user based on a first application and a second service is provided to the user based on a second application, the computer comprising:
When the first application is activated in a state in which the first application and the second application are linked, the user terminal of the user receives first identification information capable of identifying the user with the first service; a display control step of displaying a reading image including second identification information capable of identifying the user in the second service ;
a second process executing step of executing a second process related to the second service based on the second identification information when the image for reading of the first application is read;
Service delivery method to perform . a computer when a first service is provided to a user based on a first app and a second service is provided to the user based on a second app;
When the first application is activated in a state in which the first application and the second application are linked, the user terminal of the user receives first identification information capable of identifying the user with the first service; 2 display control means for displaying a reading image including second identification information that can identify the user in the service ;
function as
When the reading image of the first application is read, a second process relating to the second service is executed based on the second identification information .
program.

Images