JP7195471B1 - Service providing device, service providing system, notification control method, and program - Google Patents

Abstract

A service providing device, a service providing system, a notification control method, and a program are provided for improving the complexity of notifications in individual applications.
In an electronic payment service in which a user terminal device, a first shop terminal device, a second shop terminal device and a payment server communicate via a network, an application program operating in the terminal device cooperates with the electronic payment service. A settlement server, which is a service providing device for providing services to users of terminal devices, includes a notification control unit. The notification control unit transmits to the terminal device a category determining unit that determines a category related to the display of the notification in the application program according to the transmission source of the notification, and information for including the category information related to the determined category in the notification and displaying it. and a notification sending unit to do.
[Selection drawing] Fig. 1

Description

The present invention relates to a service providing device, a service providing system, a notification control method, and a program.

A technology has been proposed that associates notifications of different applications based on the consistency of semantic feature values of notification messages in the applications (see Patent Document 1, for example). Such technology is convenient because the user can easily refer to highly relevant notifications even if the notifications are for different applications.

Japanese Patent No. 6783382

However, in recent years, the number of notifications handled by individual applications has increased, and even in individual applications, notifications have become complicated, making it difficult for users to confirm. On the other hand, since the conventional technology associates notifications of different applications, there are cases where the complexity of notifications in individual applications cannot be improved.

SUMMARY OF THE INVENTION The present invention has been made in consideration of such circumstances, and provides a service providing apparatus, a service providing system, a notification control method, and a program capable of improving the complexity of notifications in individual applications. is one of the purposes.

One aspect of the present invention is a service providing device that cooperates with an application program running on a terminal device to provide a service to a user of the terminal device, wherein a category related to display of notifications in the application program is the notification and a notification transmission unit configured to transmit information for displaying category information related to the determined category in the notification to the terminal device. is.

ADVANTAGE OF THE INVENTION According to one aspect of the present invention, it is possible to provide a service providing apparatus, a service providing system, a notification control method, and a program capable of reducing complexity of notifications in individual applications.

1 is a diagram showing an example of a configuration for realizing an electronic payment service; FIG. 1 is a diagram illustrating a general flow of electronic payment; FIG. 1 is a diagram illustrating a general flow of electronic payment; FIG. 2 is a configuration diagram of a settlement server 100; FIG. 4 is a diagram showing an example of contents of user information 172. FIG. 4 is a diagram showing an example of contents of member store/store information 176. FIG. 3 is a diagram illustrating an example of a functional configuration of a notification control unit 140; FIG. 4 is a diagram showing a first display example of a notification screen displayed by the payment application 20. FIG. FIG. 11 is a diagram showing a second display example of a notification screen displayed by the payment application 20; FIG. 11 is a diagram showing a third display example of a notification screen displayed by the payment application 20; FIG. 13 is a diagram showing a fourth display example of a notification screen displayed by the payment application 20; FIG. 14 is a diagram showing a fifth display example of a notification screen displayed by the payment application 20;

Hereinafter, a service providing device, a service providing system, a notification control method, and a program according to the present invention will be described with reference to the drawings. A service providing system is realized by one or more processors. The service providing system is a system that provides services such as electronic payment services. In the following description, the service providing system and the service providing device provide an electronic payment service, and the service providing system and the service providing device are referred to as an "electronic payment system" and a "payment server." The system and service providing device may provide shopping, auction, chat, microblogging, and any other services that require login. An electronic payment service is a service that supports payment related to purchase of goods and services at a store. A store is, for example, a physical store (actual store) that exists in real space. In the electronic payment service, a store is treated as belonging to, for example, a member store (brand), and processing such as settlement when a purchase is made at the store is mainly performed between the user and the member store. Alternatively, processing such as settlement may be performed between the user and the store.

[Electronic payment service]
FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. An electronic payment service is implemented centering on the payment server 100 . The settlement server 100 communicates with, for example, one or more user terminal devices 10, one or more first shop terminal devices 50, and one or more second shop terminal devices 70 via the network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), wireless base stations, provider devices, and the like.

The user terminal device 10 is, for example, a portable terminal device such as a smart phone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), and the like. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, and operates in cooperation with the payment server 100 to provide electronic payment services to the user. The payment application 20 controls a camera, a communication device, a touch panel, and the like.

The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the POS device may realize the product price acquisition function and the optical reading function. The store code image 60 is placed in a store and is a code image such as a QR code (registered trademark) printed on a medium such as paper or plastic. Note that the store code image 60 may be displayed on a display placed in the store (a display of a terminal device such as a smart phone may be used).

The second store terminal device 70 is used by the member store operator. The second store terminal device 70 is a smart phone, a tablet terminal, a personal computer, or the like. A member store interface 72 operates on the second store terminal device 70 . The merchant interface 72 may be a merchant application or a browser. The member store interface 72 accepts coupon settings and the like from the member store operator and transmits them to the settlement server 100 . The second store terminal device 70, which is a smartphone, has a function of displaying a code image corresponding to the store code image and reading a code image displayed by the user terminal device 10 by executing an application for member stores. have.

The payment server 100 cooperates with the payment application 20 running on the user terminal device 10 to provide the user of the user terminal device 10 with an electronic payment service. The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first shop terminal device 50 . The first store terminal device 50 may include a POS device and a member store server. In this case, payment information is transmitted from the POS device to the payment server 100 via the member store server. In the following explanation, it is assumed that the payment information is transmitted from the first store terminal device 50 without distinguishing between them. The payment server 100 performs electronic payment by, for example, decreasing the charge balance managed in association with the user ID and increasing the item value of the sales proceeds of the affiliated store. For example, the item value of the sales proceeds of the member store is not used as electronic money per se, but the amount corresponding to the item value of the sales proceeds is calculated in a cycle according to the agreement between the member store and the electronic payment service. transferred to a bank account. Electronic payment may include those that enable purchase of a larger amount than the charge balance at the time of purchase by methods such as revolving payment and credit payment.

FIG. 2 is a diagram illustrating a general flow of electronic payment. FIG. 3 is a diagram illustrating a general flow of electronic payment. 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two types of electronic payment: pattern 1 and pattern 2.

In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the shop code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. The store URL is a domain of the electronic payment service to which information that can identify the store is added, and is associated with the member store ID, the store ID, and the like in the settlement server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 retrieves store information (described later) from the member store ID and store ID corresponding to the store URL, acquires the member store name and store name information (S3), and transmits them to the settlement application 20 (S4). . The user inputs the settlement amount into the user terminal device 10 on the screen displaying the member store name and store name (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits the second payment information to the payment server 100 (S6). The payment server 100 completes electronic payment as described above based on the received second payment information (S7). The payment server 100 then transmits a payment completion notification (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). When the store code image 60 is displayed on a display placed in a store, the store code image 60 may include not only the store URL but also the payment amount information. In this case, the procedure for the user to input the settlement amount is omitted, and the information of the settlement amount is included in the first settlement information and transmitted to the settlement server 100 . The merchant name and store name information may be included and displayed on the payment completion screen.

In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment application 20 sends a one-time code issue request to the settlement server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or barcode generated based on the one-time code (S14). The user holds up (presents) the display surface of the user terminal device 10 to the first shop terminal device 50, and the first shop terminal device 50 decodes the code image by the optical reading function and acquires the one-time code ( S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, member store ID, store ID, etc., and transmits the payment information to the payment server 100 (S16). Information on the payment amount is obtained in advance by reading a bar code, manually entering the information, or the like. The payment server 100 identifies the user corresponding to the one-time code based on the received information, and completes the electronic payment as described above (S17). The payment server 100 then transmits a payment completion notification to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

It should be noted that electronic payment may be performed using only one of the above patterns. Also, the "account ID" described in FIG. 2 may be other information (such as a telephone number) that can be used as user identification information. Alternatively, the issuance of the one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In that case, the settlement server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[Settlement server]
FIG. 4 is a configuration diagram of the settlement server 100. As shown in FIG. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 122, a payment processing unit 124, an information management unit 130, a notification control unit 140, and a storage unit 170. Components other than communication unit 110 and storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components are hardware (circuit part; circuitry) or by cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as a HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium) and installed in the storage device by loading the storage medium into the drive device.

The storage unit 170 is an HDD, flash memory, RAM (Random Access Memory), or the like. The storage unit 170 may be a NAS (Network Attached Storage) device that can be accessed by the settlement server 100 via a network. The storage unit 170 stores information such as user information 172, payment content information 174, member store/store information 176, and the like.

The communication unit 110 is a communication interface for connecting to the network NW. The communication unit 110 is, for example, a network interface card.

The payment content providing unit 122 has, for example, a function of a web server, and provides the user terminal device 10 with information (contents) for displaying various screens of the electronic payment service. The payment content providing unit 122 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10 . The user terminal device 10 accepts various inputs from the user while the content is being reproduced by the payment application 20 , and transmits the above-described payment information and the like to the payment server 100 .

The payment processing unit 124 performs payment processing based on the payment information transmitted from the user terminal device 10 or the first shop terminal device 50 . The payment processing unit 124 performs payment processing while referring to the user information 172 .

The information management unit 130 creates a new record of the user information 172 based on information acquired from the user terminal device 10, the first store terminal device 50, the second store terminal device 70, etc. Update each data item in the record.

The notification control unit 140 controls notification to users of the electronic payment service. More specifically, the notification control unit 140 controls the transmission of notifications and the display of notifications on the user terminal device 10 . Notifications from the payment server 100 can be displayed by the payment application 20 on the user terminal device 10 .

FIG. 5 is a diagram showing an example of the contents of the user information 172. As shown in FIG. FIG. 5 is a diagram showing an example of the contents of the user information 172. As shown in FIG. The user information 172 is an example of user registration information. User information 172 includes, for example, user URL, account ID, phone number, password, email address, user ID, name/address/date of birth, registration date, charge balance, bank account, credit card number, Information such as other service cooperation information, radio wave authentication setting, carrier payment setting, chat friend list, charge history information, payment history information, chat history information, notification history information, notification setting information, etc. are associated with each other. When registering for the electronic payment service, it is mandatory to register a phone number and password. The account ID is issued to the user by the settlement server 100, and the user ID is an ID that can be set arbitrarily by the user (does not need to be set). In addition, information other than the user URL, account ID, telephone number, password, registration date, charge balance, charge history information, and settlement history information can be arbitrarily set by the user. Hereinafter, a user instance (electronic settlement account) associated with these pieces of information will be referred to as an account. The user URL is used for remittance processing between users. The registration date is the date when the user registers for the electronic payment service (the date when the account is created).

The charge balance is information indicating the balance of electronic money set by the user transferring money to the account in advance. Methods of remittance include remittance from an ATM (Automatic Teller Machine) of a designated trader (bank), remittance from a registered bank account, and the like. Each of the bank account and credit card number is information (account number, card number) of a bank account or credit card number that can deposit money into the electronic payment service. Other service cooperation information is a login ID or the like of another service that cooperates with the electronic payment service (for example, is operated by an operator belonging to the same business group). Radio wave authentication setting is setting information when performing authentication by communication with a specific communication carrier. The carrier payment setting is setting information for transferring at least part of the payment using the electronic payment service to payment to the communication carrier. The chat friend list is a list of other users who are chat partners in the chat function provided by the electronic payment service. The charge history information is a history of the user's advance remittance to the electronic payment service to increase the charge balance. The payment history information is information indicating details of payments made by the user (date and time, shop ID of the shop where the purchase was made, payment amount, etc.) for each payment. The chat history information is a history of the contents of chats conducted by users.

The notification history information is information indicating the history of notifications made by the settlement server 100 to the user. The notification history information includes information such as the content of the notified message, the date and time of the notification, and the read status of the notification. The notification setting information is setting information regarding notification display on the user terminal device 10 .

FIG. 6 is a diagram showing an example of the contents of the member store/store information 176. As shown in FIG. The store information 176 includes, for example, a first table 176A in which member store IDs and store IDs are associated with store URLs, and a second table 176A in which member store names and sales proceeds (described above) are associated with member store IDs. It includes a table 176B and a third table 176C in which store IDs are associated with store IDs. The member store/store information 176 may include, in addition to this information, information such as the category of the member store or store, the location of the store, and the payment pattern.

FIG. 7 is a diagram showing an example of the functional configuration of the notification control unit 140. As shown in FIG. The notification control unit 140 includes, for example, a category determination unit 142, a notification transmission unit 144, a priority determination unit 146, and an unread counting unit 148. The category determination unit 142 determines a category related to notification display by the payment application 20 according to the transmission source of the notification. More specifically, the category determining unit 142 sets the category of the notification to be transmitted to the user terminal device 10 to the first category, which is the category of the notification from the provider of the electronic payment service to the user of the electronic payment service. and a second category, which is a category of notification from the member store of the electronic payment service to the user of the member store. Note that the category may have subcategories hierarchically.

The notification transmission unit 144 transmits a notification containing category information about the category determined by the category determination unit 142 to the user terminal device 10 . Here, the notification may be meta information, or may be the content of the notification itself (for example, text or image). Also, the notification may be information for displaying category information included in the notification content, or may be information including category information so that the category can be recognized separately from the notification content. Note that if a category hierarchically has subcategories, the notification transmitting unit 144 may change the notification transmission frequency based on the attributes of the subcategories and the content of notifications belonging to the subcategories.

By transmitting the notification including the category information in this way, the payment application 20 in the user terminal device 10 recognizes the category of the notification received from the payment server 100 and sends the notification in association with the category. can be displayed. In addition, when a category hierarchically has subcategories, the payment application 20 can display information about the received notification attached to a corresponding subcategory of the subcategories of the notification category.

The priority determination unit 146 determines display priorities for a plurality of categories based on the user's usage history of the electronic payment service or the user's action history, and notifies the payment application 20 of them. By being notified of such priorities, the payment application 20 in the user terminal device 10 can change the display mode of the plurality of categories according to the priorities.

The unread tallying unit 148 tallies unread notifications by recognizing whether or not unread notifications are to be tallied based on setting information registered in advance for each subcategory in a category hierarchically having subcategories. The settlement application 20 is notified of the tallied result. With regard to the unread notices, by notifying such a tally result, the payment application 20 in the user terminal device 10 displays the number of unread notices excluding the unread notices not subject to tallying in association with the category or subcategory. be able to. Regarding the setting of this unread tally, the payment application 20 receives a setting operation for each subcategory as to whether or not unread notifications are to be tallied, and transmits the setting information to the payment server 100 .

[Notification control]
Specific examples of notification control performed by the payment server 100 and the payment application 20 will be described below with reference to display examples of the notification screens shown in FIGS.

FIG. 8 is a diagram showing a first display example of the notification screen displayed by the payment application 20. As shown in FIG. The notification screen G100A shown in FIG. 8 displays notifications classified into categories and subcategories. For example, the notification screen G100A includes an application tab G110, a member store tab G120, and a mini app tab G130 for classifying and displaying notifications into a plurality of categories. In the example of FIG. 8, the application tab G110 is an example of the first category described above, and mainly displays notifications from the electronic payment service provider to the user. On the other hand, the affiliated store tab G120 is an example of the above-described second category, and mainly displays notifications directed to the user from affiliated stores of the electronic payment service. Note that the indicator G140 indicates the tab being selected, and is displayed in association with the selected tab according to the tab selection operation.

Also, the mini app tab G130 is an example of a third category different from the above first and second categories. Specifically, in the third category, when the payment application 20 has a second function of providing a second service in cooperation with an electronic payment function (first function) of an electronic payment service (first service), This is a category of notifications sent from the provider of the second service to the user. A payment application 20 having such a function is generally called a "super application", and a second function that cooperates with the electronic payment function of the payment application 20 is called a "mini application". Hereinafter, this second function or the second service provided by the second function may be referred to as a mini app. As an example of a mini-app in the present embodiment, for example, a member store may provide a service that enables a user to purchase its own product (or service) in cooperation with an electronic payment function. Another example of a mini-application is, for example, an electronic payment service provider that implements other service functions using the electronic payment function.

Note that the first display example does not limit the number of notification categories to three (first category, second category, and third category). Also, in the first display example, the categories shall have at least a first category and a second category. Regarding the first display example, the category determination unit 142 selects a category from a category group including at least a first category and a second category for notifications transmitted to the payment application 20 . In the first display example, the category group may include the third category described above.

Also, in the first display example, notifications classified into each category are classified into subcategories under each category and displayed. For example, the notification screen G100A in FIG. 8 displays notifications classified into five subcategories G111 to G115 including "system", "campaign", and "new arrival information". In the display of each subcategory, the notification screen G100A may display an icon to improve the visibility of the subcategory, or may display the title of the subcategory, various information related to the most recent notification, the number of unread notifications, and the like. . For example, the subcategory G111 in FIG. 8 displays an icon C1, a title T1, information N11 and N12 regarding the most recent notifications, and the number of unread notifications U1. For example, the information N11 represents part of the content of the most recent unread notification, and the information N12 represents the reception time of the most recent unread notification.

FIG. 9 is a diagram showing a second display example of the notification screen displayed by the payment application 20. As shown in FIG. A notification screen G100B shown in FIG. 9 shows a display example of the member store tab G120 described with reference to FIG. The notification screen G100B in the example of FIG. 9 is a display in which notifications classified into the category of "affiliated store" are classified into subcategories G121 to G125 for each subordinate affiliated store. In the subcategory display, the notification screen G100B displays an icon for enhancing the visibility of the subcategory, the title of the subcategory, various information related to the most recent notification, the number of unread notifications, etc., in the same manner as in the first display example. can be anything.

FIG. 10 is a diagram showing a third display example of the notification screen displayed by the payment application 20. As shown in FIG. A notification screen G100C shown in FIG. 10 shows a display example of a notification in a subcategory selected from a category. The notification screen G100C in the example of FIG. 10 displays notifications N21 and N22 classified into the subcategory "campaign" selected from the category "application". The notification screen G100C also includes an input interface IF23 that receives an operation for displaying various setting interfaces for the subcategory being displayed (here, "campaign").

FIG. 11 is a diagram showing a fourth display example of the notification screen displayed by the payment application 20. As shown in FIG. A notification screen G100D shown in FIG. 11 shows a display example of a notification in a subcategory selected from a category, as in the third display example. Notification screen G100D in the example of FIG. 11 displays notifications N31 and N32 classified into the subcategory of "asset management" selected from the "mini app" category.

As shown in FIGS. 10 and 11, in the notification screens G100C and G100D that display subcategory notifications, each notification has a icon, the content of the notification (which may include text and images), the time the notification was received, and the like may be displayed. In addition to these displays, each notification may also display its read status.

FIG. 12 is a diagram showing a fifth display example of the notification screen displayed by the payment application 20. As shown in FIG. The notification screen G100E shown in FIG. 12 is a display example of a user interface (hereinafter referred to as "setting interface") for the user to set notification suppression for a subcategory selected from a category. The suppression of notifications referred to here includes a first notification suppression that suppresses notifications for notifying that the payment application 20 has received a new notification, and a second notification suppression that suppresses the transmission of notifications to the payment application 20 itself. and The notification screen G100E in the example of FIG. 12 is a setting interface that includes an information display area IF41 for prompting confirmation of notification suppression targets, and an input interface IF42 that receives an operation for executing notification suppression settings for the displayed targets. IF40 is displayed. The setting interface IF40 is displayed by, for example, a selection operation of the input interface IF23.

For example, when the first notification suppression is set for the target subcategory, the unread counting unit 148 counts unread notifications in the category or subcategory including the subcategory (hereinafter referred to as "parent category"). In the target subcategory, Aggregate by excluding unread notifications. By notifying the settlement application 20 of such a tally result, the settlement application 20 displays the number of unread notifications excluding the unread notifications of the target subcategory as the unread number of the parent category. In this way, by excluding subcategories specified by the user from unread tabulation, the priority of confirmation for notifications of the subcategories can be lowered, thereby reducing complexity of notifications.

In the example of FIG. 12, the setting interface IF40 for suppressing notification of the target subcategory is illustrated, but if the input interface IF23 is operated when notification suppression is already set for the target subcategory, settlement The application 20 displays a setting interface for canceling notification suppression for the target subcategory.

In addition, in the example of FIG. 12, the setting interface is used to set whether or not to set notification suppression for the target subcategory. Whether or not may be controlled based on the display priority for each subcategory. For example, the payment application 20 is configured not to accept a setting operation (for example, not to display a setting interface) for determining whether or not to count unread notifications for a subcategory whose priority is higher than a threshold. good too. Such control of the settings interface can prevent users from not being notified about important categories or subcategories.

According to the electronic payment system 1 of the embodiment described above, the payment server 100 provides an electronic payment service to the user of the user terminal device 10 in cooperation with the payment application 20 operating on the user terminal device 10. , a category determination unit 142 that determines a category related to the display of the notification in the payment application 20 according to the transmission source of the notification; and the notification transmission unit 144 that transmits the notification to the payment application 20 .

For example, applications such as e-mail and chat generally notify information in chronological order regardless of whether the sender is an individual or a corporation. For this reason, especially in the case of e-mail, users set filtering conditions to organize information. On the other hand, as notification information becomes more diverse, information with high or low importance, information with the nature of immediate notification (immediacy), information with high user interest, etc. The sorting of information itself becomes complicated. According to the electronic payment system 1 of the embodiment, it is possible to improve the complexity of sorting such notification information.

<Modification>
The payment application 20 may be configured to change the display mode of the tabs according to the priority of the tabs. For example, the payment application 20 may change the order of tabs according to priority. Further, for example, the payment application 20 may automatically select the tab with the highest priority when any tab needs to be displayed in the selected state, such as when the application is started. In this case, for example, the priority determining unit 146 determines the importance of each category or subcategory for the user based on the user's operation history (an example of payment history or action history) on the payment application 20. A high priority may be determined according to the level of importance. By changing the display mode of tabs based on such priority, the electronic payment system 1 can personalize the display mode of a plurality of tabs according to the characteristics of the user. Also, if the user terminal device 10 has a function of acquiring location information, location information may be used as an example of the action history. Moreover, the payment application 20 may change the display mode of each notification according to the degree of importance. For example, the payment application 20 changes the display mode (background, background color, presence/absence of tagging, etc.) of a particular member store for a user who has used a particular member store many times or has a high frequency of use. The degree of importance of member stores can be suggested to users.

Moreover, the payment application 20 may change the display mode of the subcategories on the tabs for each category according to the priority of the subcategories. Moreover, the payment application 20 may change the display mode of the notification in the subcategory according to the priority of the subcategory. In this case, for example, the payment application 20 may be required to notify the user (for example, notifications related to authentication or notifications related to various deadlines (payment deadline, remittance request deadline, etc.)) and optional ones (campaign information, etc.). coupons, etc.), and then the display order may be changed in the optional notification.

Further, when the electronic payment system 1 provides a service related to asset management as illustrated in FIG. may be configured. For example, in this case, the notification transmission unit 144 recognizes the importance of notifications based on the frequency of confirmation of notifications related to asset management, and increases the frequency of sending notifications with high importance or increases the frequency of sending notifications with low importance. can be lowered. In addition, for example, the notification transmission unit 144 increases the frequency of notification transmission for investment products whose investment status is likely to change rapidly, such as stock investment in individual stocks (see notification N32 in FIG. 11, for example). For example, a real-time report may be used), and the frequency of sending notifications may be reduced for investment products whose investment status is unlikely to change rapidly, such as investment trusts (see notification N31 in FIG. 11) (for example, weekly reports). as a report, etc.).

In addition, the notification transmission unit 144 may be configured to transmit notifications filtered according to user preferences. For example, in principle, the notification transmission unit 144 may be configured to transmit only notifications related to member stores that the user is following. Furthermore, for example, the notification transmitting unit 144 may notify information about affiliated stores that are likely to match the user's preferences even if the affiliated stores are not followed by the user. The user's preferences may be grasped based on, for example, the user's action history or payment history, or may be based on the types and characteristics of member stores that the user follows, or their similarities, etc. It may be something that can be grasped based on. For example, the notification transmission unit 144 may transmit, to users who have similar behavioral tendencies, a notification that recommends a member store that they have never been to before. By transmitting such notifications, the electronic payment system 1 can suppress transmission of unnecessary notifications while providing more appropriate notifications to users.

In addition, the notification transmission unit 144 may be configured to classify users who follow each affiliated store according to their common points, and to perform notification according to each class of users for each class. For example, the notification sending unit 144 may classify users according to usage timing or frequency (for example, Saturdays and Sundays, once a month, every day, etc.), or may classify users according to their attributes (student, elderly, gender, age, whether they live in a rural area, etc.). Alternatively, they may be classified according to whether they live in Tokyo, whether they are light users, whether they are heavy users, etc.).

Also, the priority determining unit 146 may determine the priority of notification for each category or for each subcategory. More specifically, the priority determining unit 146 may determine priority according to the importance of notification. For example, the priority determining unit 146 may determine the highest priority for notifications regarding user consent to revisions of terms due to legal revisions or the like. In this case, the payment application 20 may be configured to display the notifications in order of priority so that the notification is displayed fixedly at the top of the category or subcategory until the user confirms it.

As described above, the mode for carrying out the present invention has been described using the embodiments, but the present invention is not limited to such embodiments at all, and various modifications and replacements can be made without departing from the scope of the present invention. can be added.

DESCRIPTION OF SYMBOLS 1... Electronic payment system 10... User terminal device 20... Payment application 50... First shop terminal device 60... Shop code image 70... Second shop terminal device 72... Interface for member stores 100... Payment Server 110 Communication unit 122 Payment content providing unit 124 Payment processing unit 130 Information management unit 140 Notification control unit 142 Category determination unit 144 Notification transmission unit 146 Priority determination unit , 148... Unread counting unit 170... Storage unit 172... User information 174... Settlement content information 176... Store information 176A... First table 176B... Second table 176C... Third table

Claims (5)

A service providing device that cooperates with an application program running on a terminal device to provide an electronic payment service to a user of the terminal device,
Categories related to the display of notifications in the application program are classified into a first category, which is a category of notifications from the provider of the electronic payment service to the users of the electronic payment service, and the electronic a category determination unit that selects and determines from a category group including a second category, which is a category of notifications directed to the user from a member store that sells to the user using a payment service ;
a notification transmission unit configured to transmit information including the content of the notification and category information about the determined category to the terminal device;
with
The category information is information that specifies on which display screen the content of the notification is to be displayed, among the display screens for each of the categories that are displayed by the terminal device and are selected by tabs.
Service provider. The application program provides a second function of providing a second service in cooperation with a first function of providing the electronic payment service as the first service,
The category determination unit selects a category of notification to be transmitted to the terminal device from the category group further including a third category, which is a category of notification directed to the user from the provider of the second service. do,
The service providing device according to claim 1 . A service providing system comprising: a service providing device for providing an electronic payment service to a user of the terminal device in cooperation with an application program running on the terminal device; and the application program,
The service providing device
Categories related to the display of notifications in the application program are classified into a first category, which is a category of notifications from the provider of the electronic payment service to the users of the electronic payment service, and the electronic a category determination unit that selects and determines from a category group including a second category, which is a category of notifications directed to the user from a member store that sells to the user using a payment service ;
a notification transmission unit configured to transmit information including the content of the notification and category information related to the determined category to the terminal device;
with
Based on the information received from the service providing device, the application program displays the content of the notification on the display screen corresponding to the category indicated by the category information, among the display screens for each of the categories selected by tabs. , to display on the terminal device ,
Service delivery system. A service providing device that provides an electronic payment service to a user of the terminal device in cooperation with an application program running on the terminal device,
Categories related to the display of notifications in the application program are classified into a first category, which is a category of notifications from the provider of the electronic payment service to the users of the electronic payment service, and the electronic Selecting and determining from a category group including a second category, which is a category of notification directed to the user from a member store that sells to the user using a payment service ;
transmitting information including the content of the notification and category information about the determined category to the terminal device;
including
The category information is information that specifies on which display screen the content of the notification is to be displayed, among the display screens for each of the categories that are displayed by the terminal device and are selected by tabs.
Notification control method. An application program that cooperates with a service providing device to provide an electronic payment service to a user,
on the terminal device of the user,
a first category, which is a category of notifications directed to the user of the electronic payment service from the provider of the electronic payment service, according to the transmission source of the notification, as a category related to the display of the notification to the user; The service providing device that selects and determines from a category group including a second category, which is a category of notification directed to the user from a member store that conducts sales activities to the user using the electronic payment service. receive information including the content of the notification and category information about the determined category from
displaying the contents of the notification on a display screen corresponding to the category indicated by the category information, out of the display screens for each of the categories selected by tabs, based on the received information about the notification;
program.

Images