Information processing apparatus, information processing method, program, and information processing system
By linking user identification information across message and electronic payment services, the information processing device automates the acquisition of rewards within the electronic payment app, enhancing usability by eliminating the need for separate operations.
Patent Information
- Application Number
- JP2024038984
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-03-13
- Publication Date
- 2025-09-29
AI Technical Summary
Existing electronic payment services require users to perform separate operations on multiple applications to obtain benefits, such as coupons, leading to reduced usability.
An information processing device that links user identification information from a message delivery service with an electronic payment service, allowing benefits to be granted upon operation of a message delivery app, thereby automating the acquisition of rewards within the electronic payment app.
Improves usability by enabling users to receive rewards through the electronic payment app without additional operations, leveraging the message delivery app as a conduit for linking and granting benefits.
Smart Images

Figure 2025139900000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to an information processing device, an information processing method, a program, and an information processing system. [Background technology]
[0002] Cashless payments, which do not require the use of currency when paying for goods or services, are becoming increasingly common. In particular, electronic payments using payment applications (hereinafter referred to as electronic payment apps) that can be installed on terminal devices such as smartphones are attracting attention due to their high convenience.
[0003] Patent Document 1 discloses a method for automatically following up on the affiliated store that provided the coupon in an electronic payment service after the coupon is provided. Patent Document 2 discloses a method for automatically applying coupons that can be used at the store where the payment is processed when making an electronic payment using a terminal device. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent Publication No. 2022-058000 [Patent Document 2] Japanese Patent Publication No. 2020-004122 Summary of the Invention [Problem to be solved by the invention]
[0005] However, the above-mentioned conventional techniques have room for improvement in terms of improving the usability of electronic payment services.
[0006] The present disclosure aims to improve usability. [Means for solving the problem]
[0007] An information processing device according to one embodiment of the present disclosure is an information processing device that provides an electronic payment service, and is characterized by comprising: a receiving unit that receives a request to acquire a benefit that can be used in the electronic payment service from an external device that provides a message delivery service; and an granting unit that grants the benefit to the user who made the request to acquire the benefit in the message delivery service, on the condition that first identification information that identifies the user who receives the message delivery service is linked to second identification information that identifies the user who receives the electronic payment service. [Effects of the Invention]
[0008] According to the present disclosure, usability can be improved. [Brief explanation of the drawings]
[0009] [Figure 1] FIG. 10 is a diagram illustrating an example of information processing. [Figure 2] FIG. 1 illustrates an example of a system configuration. [Figure 3] FIG. 2 is a block diagram illustrating an example of a hardware configuration of an information processing device. [Figure 4] FIG. 2 illustrates an example of a software configuration of a message delivery server. [Figure 5] FIG. 2 is a diagram showing an example of MS user information stored in an MS user information database. [Figure 6] FIG. 2 is a diagram illustrating an example of OA user information stored in an OA user information database. [Figure 7] FIG. 10 is a diagram illustrating an example of linking of store IDs. [Figure 8] FIG. 10 is a diagram showing an example of friend registration information stored in a registration information database. [Figure 9] FIG. 2 is a diagram illustrating an example of the software configuration of an electronic payment server. [Figure 10] FIG. 2 is a diagram showing an example of PS user information stored in a PS user information database. [Figure 11] FIG. 2 is a diagram showing an example of affiliated store information stored in an affiliated store information database. [Figure 12] FIG. 10 is a diagram showing an example of coupon information stored in a coupon information database. [Figure 13] FIG. 10 is a diagram illustrating an example of linked information managed by the electronic payment server. [Figure 14] FIG. 10 is a diagram showing the coupon acquisition status of PS users. [Figure 15] FIG. 10 is a sequence diagram illustrating an example of a flow of information processing. [Figure 16] FIG. 10 is a diagram illustrating an example of a screen displayed on a terminal device. [Figure 17] 10 is a flowchart illustrating an example of a process executed by an electronic payment server. [Figure 18] FIG. 10 is a diagram illustrating an example of information processing when an OA user of a coupon distribution source store is registered as a friend. DETAILED DESCRIPTION OF THE INVENTION
[0010] Preferred embodiments of an information processing device, an information processing method, a program, and an information processing system according to the present disclosure will be described in detail below with reference to the drawings. Note that the information processing device, the information processing method, the program, and the information processing system according to the present disclosure are not limited to these embodiments. Furthermore, the same components in the following embodiments will be assigned the same reference numerals, and duplicated descriptions will be omitted.
[0011] [1. An example of a possible case] Applications that can be installed on terminal devices such as smartphones include electronic payment applications, message delivery applications, etc. In the following, applications may be simply referred to as apps.
[0012] Electronic payment apps are operated and managed by service providers that provide electronic payment services. Electronic payment services are an example of a first service. A store or service provider that has a contract with a service provider that provides electronic payment services is called an affiliated store. An example of an affiliated store is an organization that operates multiple physical stores or online shops. Users can make payments using the electronic payment app at affiliated stores. The store manager of an affiliated store (hereinafter referred to as the store manager) can use a dedicated interface to distribute information on coupons and other benefits that can be used at the store. Generally, in order to receive such benefits, users must operate the electronic payment app and actively perform operations to receive the benefits on the electronic payment app.
[0013] Message delivery apps are operated and managed by service providers that provide message delivery services (hereinafter referred to as message delivery services) as one of the user communication tools. Message delivery services are an example of the second service. Users can use message apps to send messages to other users. In addition to general users (MS users, described below), users who have acquired official accounts (OA users, described below) can also send messages to general users for marketing purposes. One example is the delivery of messages announcing campaign information at stores. General users can view such messages by operating the message delivery app. Message delivery apps are often used for everyday messaging between general users, so messages sent by OA users tend to be widely viewed by general users.
[0014] As such, each service provided has a corresponding application. Users typically operate the corresponding application to obtain information about each service. The more services provided, the greater the operational burden on users. For example, the aforementioned electronic payment app store and the official account for the message delivery service may be operated by the same entity. In such cases, users must perform separate operations to obtain the same information, leaving room for improvement in terms of usability. Specifically, it is anticipated that general users will be notified of the availability of rewards available through the electronic payment app by sending messages through the message delivery app. As mentioned above, messages sent through message delivery apps are likely to be viewed by general users. However, as mentioned above, to obtain rewards through the electronic payment app, users must operate the electronic payment app and perform operations to obtain the rewards within the electronic payment app. Therefore, general users who recognize the availability of rewards through the message delivery app must separately launch the electronic payment app and perform operations (possibly multiple operations) to open a page or screen within the electronic payment app to obtain the desired rewards. After that, the reward will only be granted within the electronic payment app once the user performs the operation to acquire the reward on the desired page or screen. There is room for improvement in terms of usability in this type of user operation. Below, we will explain how to improve usability.
[0015] [2-1. Information processing devices] Fig. 1 is a diagram showing an example of information processing executed by an information processing device according to this embodiment. First, the information processing device according to this embodiment will be described with reference to Fig. 1. Note that the message delivery server 101, terminal device 102, and electronic payment server 103 in Fig. 1 are all types of information processing devices. Below, the information processing executed by the electronic payment server 103 will be described together with the processing executed by the message delivery server 101 and terminal device 102.
[0016] (About Message Delivery Server 101) The message delivery server 101 is an information processing device that provides a message delivery service. The message delivery server 101 is an example of an external device. A user can receive the message delivery service by installing a message delivery application for using the message delivery service on a terminal device 102 (described later). The message delivery service can also be used by accessing a page provided by the message delivery server 101 using a general web browser.
[0017] Using the message delivery app, a user can send messages, view messages sent by other users, reply to messages, and register friends. In this specification, a user who receives the message delivery service is referred to as an MS user. An MS user is, for example, a user who has obtained an account within the message delivery app. The obtained account is managed by the message delivery server 101. "Friend registration" means that a user registers another user's account as a "friend." Registering a friend is sometimes expressed as registering another user as a friend. Friend registration can be performed by the user operating the message delivery app. By registering a friend, the user can exchange messages with the friend user.
[0018] Furthermore, users can obtain a second account (for example, an official account) that is different from a general account (first account). An official account is an account that allows a company, store, etc. to deliver information directly to general users. A user with a second account (hereinafter referred to as an OA user) is granted different privileges than an MS user with a first account. For example, an OA user can send segmented messages to MS users who have registered the OA user as a friend. Segmented messages are sent to specific MS users using segment information, which will be described later.
[0019] A store manager may acquire an official account of a message distribution service and distribute messages as an OA user. In this case, the message distribution server 101 can distribute a predetermined message from the official account of the store manager's store on the message distribution service.
[0020] A service provider that provides electronic payment services may acquire an official account for a message delivery service and deliver messages as an OA user. In this case, the message delivery server 101 can deliver a predetermined message from the official account of the service provider on the message delivery service.
[0021] (Regarding terminal device 102) The terminal device 102 is an information processing device used by a user who receives the above-mentioned message delivery service and the below-described electronic payment service. In this embodiment, the terminal device 102 is described as a smartphone, but is not limited to this. The terminal device 102 may be, for example, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, or a PDA (Personal Digital Assistant).
[0022] The terminal device 102 can display information distributed by the message distribution server 101, which provides a message distribution service, and other information using a web browser or an application, etc. The terminal device 102 can display information distributed by the electronic payment server 103, which will be described later, and other information using a web browser or an application, etc.
[0023] The terminal device 102 may have a GPS (Global Positioning System) function, a camera function, etc. The terminal device 102 can provide location information acquired by the GPS function to other devices. The terminal device 102 can provide code information (information such as one-dimensional codes and two-dimensional codes) acquired by the camera function to other devices.
[0024] (About electronic payment server 103) The electronic payment server 103 is an information processing device that provides an electronic payment service, such as processing electronic payments and distributing information related to electronic payments. A user can receive the electronic payment service by installing an electronic payment app on the terminal device 102. The electronic payment service can also be used by accessing a page provided by the electronic payment server 103 using a general web browser.
[0025] Using the electronic payment app, users can pay for goods or services at stores, view and acquire bonus information distributed by stores or affiliated stores, and view recommendation information. In this specification, users who receive electronic payment services are referred to as PS users. A PS user is, for example, a user who has acquired an account within the electronic payment app. The acquired account is managed by the electronic payment server 103.
[0026] For example, the electronic payment server 103 manages the electronic accounts of affiliated stores and the electronic accounts of PS users, and realizes various payments by transferring electronic money between the electronic accounts.
[0027] "Recommendation information" refers to information about a store. Examples of recommendation information include introduction information about affiliated stores, special offer information such as coupons, information about products or services handled by the store, and point redemption information when making a payment at the store.
[0028] A "store" is any place that actually provides goods or services to users, such as a shop, restaurant, department store, movie theater, or gym.
[0029] "Products" include tangible items such as goods that users actually acquire at stores, and intangible items such as image data, video data, music data, and game programs. "Services" are services that users actually receive at stores, etc.
[0030] [2-2. An example of information processing] (About information processing) An overview of information processing according to this embodiment will be described. In this embodiment, an example will be described in which an OA user delivers a message to an MS user regarding benefits such as coupons that can be used in an electronic payment service. That is, an example will be described in which information regarding benefits that can be used in a first service is delivered as a message using a message delivery service in a second service.
[0031] The message distribution server 101 distributes a message regarding coupons that can be used at stores on the electronic payment service (S1). This message is distributed from the message distribution server 101 based on a distribution instruction from an OA user. When the message is distributed in S1, the user can view the message regarding the coupon from screen G1 of the message distribution app displayed on the terminal device 102, as shown in FIG. 1. Screen G1 displays the text "Register as a friend to receive a coupon." If the user wishes to receive a coupon, the user performs an operation on the message. Note that the message distributed in S1 may be sent to MS users who have registered the OA user who issued the message distribution instruction as a friend, or to MS users who have not registered the OA user as a friend.
[0032] When the user operates the message delivered in S1, the terminal device 102 transmits to the message delivery server 101 an instruction to acquire a coupon for the electronic payment service (hereinafter referred to as a coupon acquisition instruction) (S2). That is, because the message delivery app of the terminal device 102 is not directly linked to the electronic payment app, the user cannot acquire a coupon for the electronic payment service directly on the electronic payment app from the message delivery app. For this reason, the terminal device 102 transmits to the message delivery server 101 a coupon acquisition instruction to acquire a coupon for the electronic payment service through the user's operation using the message delivery app.
[0033] When the instruction to acquire a coupon is received in S2, the message delivery server 101 determines whether the identification information of the MS user who issued the instruction is linked (linked) with the identification information of the PS user. Specifically, the message delivery server 101 determines whether there is linkage using a linkage flag, which will be described later. If the message delivery server 101 determines that there is no linkage, it transmits an authorization screen to the terminal device 102 requesting permission to link (S3). Details of the authorization screen will be described later.
[0034] If the user operates the permission screen received in S3 to permit collaboration, the terminal device 102 transmits an instruction to perform collaboration processing (hereinafter referred to as a collaboration instruction) to the message delivery server 101 (S4). If the user operates the permission screen received in S3 to not permit collaboration, the terminal device 102 transmits an instruction not to perform collaboration processing to the message delivery server 101. Alternatively, the terminal device 102 may not transmit a collaboration instruction to the message delivery server 101.
[0035] When the link instruction is received in S4, the message distribution server 101 performs a process of registering the official account of the store that distributed the coupon as a friend for the MS user who issued the coupon acquisition instruction (S5). In this example, as described above, this is because the process is to "register as a friend and acquire a coupon." Note that the friend registration process in S5 may be performed after S6 or S9, which will be described later. Also, friend registration does not have to be performed. In other words, S5 may be an optional process.
[0036] Upon receiving the link instruction in S4, the message delivery server 101 transmits link information and a request for acquiring a coupon to the electronic payment server 103 (S6). Hereinafter, the request for acquiring a coupon will be referred to as a coupon acquisition request. When an intermediate device, which will be described later, is used, the message delivery server 101 transmits link information and the like to the intermediate device. The link information includes a link flag, an MS user ID, which will be described later, and the like. The link flag is a flag that indicates whether a linking process, which will be described later, has been performed for an MS user managed by the message delivery server 101. The coupon acquisition request includes a coupon ID, which will be described later, and an MS user ID, and the like, for identifying the coupon to be granted.
[0037] Upon receiving the link information in S6, the electronic payment server 103 determines the value indicated by the link flag included in the link information. Specifically, if the link flag indicates "Yes," the electronic payment server 103 determines that linking processing has already been performed and does not perform the linking processing. If the link flag indicates "No," the electronic payment server 103 determines that linking has not yet been performed and performs the linking processing (S7). Specifically, the electronic payment server 103 performs processing to link the MS user ID included in the link information received in S6 with the PS user ID that it manages.
[0038] (About collaboration processing) Existing linking technology can be used for the linking process. As an example of a method for performing the linking process, information for the linking process can be exchanged between the message delivery server 101 and the electronic payment server 103 via an intermediate device (not shown) that stores an intermediate ID.
[0039] (Regarding intermediate devices) The intermediate device stores an MS user ID and a PS user ID that are linked to an intermediate ID. Linking of intermediate IDs can be performed by a user operation. For example, a PS user operates the terminal device 102 to launch an electronic payment app and register (input) an MS user ID on the app screen. The electronic payment server 103 then transmits the PS user ID it manages and the registered MS user ID to the intermediate device. The intermediate device generates an intermediate ID and stores the generated intermediate ID in association with the received PS user ID and MS user ID.
[0040] The following methods can be used to prompt the user to register an MS user ID in the electronic payment app. For example, in S3, the message delivery server 101 sends a message to the permission screen, such as "Please launch the electronic payment app and perform the registration operation before obtaining the coupon," to prompt the user to perform the registration operation. That is, if the message delivery server 101 determines in S2 that the link is not established, it sends to the terminal device 102 a permission screen displaying a message prompting the user to perform the registration operation. In this way, the delivery of the message by the message delivery server 101 triggers the user to register the user identification information required for the intermediate ID linking process, thereby realizing the above-mentioned linking process.
[0041] Note that the message delivery server 101 does not transmit a coupon acquisition request or the like to the intermediate device until the intermediate ID linking process described above is completed. In other words, even if the message delivery server 101 receives a coupon acquisition instruction from the terminal device 102, if it does not receive a notification from the intermediate device indicating that the intermediate ID linking process has been completed, it does not transmit a coupon acquisition request or the like to the intermediate device. The notification indicating that the intermediate ID linking process has been completed includes an MS user ID for identifying the user for whom intermediate ID linking has been completed.
[0042] As an alternative to the method of linking the intermediate ID described above, the PS user can input information linked to the MS user ID from the screen of the electronic payment app. Examples of information linked to the MS user ID include the login ID and password for the message delivery app. The electronic payment server 103 then transmits the input information to the message delivery server 101. The message delivery server 101 identifies the MS user ID based on the received information and transmits the identified MS user ID to the electronic payment server 103. After this, the intermediate device associates the intermediate ID with the received PS user ID and MS user ID and stores them, following the flow described above.
[0043] (Regarding processing by intermediate devices) In S6, when the intermediate device receives the link information from the message delivery server 101, it identifies the PS user ID from the MS user ID included in the link information. The intermediate device then includes the identified PS user ID in the link information and transmits it to the electronic payment server 103. The electronic payment server 103 can perform the link processing using the received link information.
[0044] If the linking process is performed or has already been performed, the electronic payment server 103 performs a coupon granting process in response to the received coupon acquisition request (S8). Specifically, the electronic payment server 103 identifies the coupon to grant from the coupon ID included in the coupon acquisition request. The electronic payment server 103 then associates the coupon ID with the PS user ID.
[0045] After performing the granting process in S8, the electronic payment server 103 transmits to the message delivery server 101 a coupon acquisition notification instruction to display a notification that the coupon has been granted on the message delivery app that made the request (S9). Furthermore, if the electronic payment server 103 performed the linking process in S7, it transmits to the message delivery server 101 linking process information indicating that the linking process has been performed, in addition to the coupon acquisition notification instruction. The linking process information includes an MS user ID for identifying the user for whom the linking process was performed, etc.
[0046] If an intermediate device is used, in S8, the electronic payment server 103 may include the PS user ID of the user who performed the linking process in place of the MS user ID in the linking process information and transmit the linking process information to the intermediate device. In this case, the intermediate device includes the MS user ID linked to the received PS user ID in the linking process information and transmits the linking process information to the message delivery server 101.
[0047] When the message delivery server 101 receives the coupon acquisition notification instruction in S9, it sends a message to the MS user who issued the instruction notifying the user that the coupon has been acquired in response to the coupon acquisition instruction (S10). Details of the notification that the coupon has been acquired will be explained later. Furthermore, when the message delivery server 101 receives the linking process information in S9, it rewrites the value of the linking flag of the linked MS user to "Yes."
[0048] The user can view a notification on the message delivery app that the coupon has been acquired. The terminal device 102 determines whether the notification that the coupon has been acquired has been operated by the user. If the terminal device 102 determines that the notification has been operated, it launches the electronic payment app and sends a request to the electronic payment server 103 to transition to the page of the affiliated store that distributed the granted coupon (S11).
[0049] Upon receiving the request in S11, the electronic payment server 103 transmits the requested page to the terminal device 102 (S12). After this, the terminal device 102 displays page G2 shown in Fig. 1 on the electronic payment app. The displayed page G2 indicates that a coupon has been acquired.
[0050] In this way, the electronic payment server 103 grants a coupon on the condition that the user identification information managed by the message delivery server 101 is linked to the user identification information managed by the electronic payment server 103. That is, information about benefits available in the first service is delivered as a message using the message delivery service of the second service. Then, when the user operates the message in the first service, the benefit in the second service is granted.
[0051] [3. An example of an information processing system] Fig. 2 is a diagram showing an example of the configuration of an information processing system 200. The configuration of the information processing system according to this embodiment will be described with reference to Fig. 2. The information processing system 200 has a message distribution server 101, a terminal device 102, and an electronic payment server 103. These devices are connected to each other via a network N, either wired or wirelessly, so as to be able to communicate with each other. The network N is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network) such as the Internet.
[0052] 2, for the sake of simplicity, one terminal device 102 is shown, but this is merely an example and is not limiting. That is, there may be two or more terminal devices 102 in the information processing system 200. The terminal device 102 can connect to the network N via a wireless communication network such as LTE (Long Term Evolution), a 4G (4th Generation) mobile communication system, and a 5G mobile communication system, and communicate with other devices. The terminal device 102 can connect to the network N via short-range wireless communication such as Bluetooth (registered trademark) and wireless LAN, and communicate with other devices.
[0053] Information transmitted and received between the message delivery server 101, the terminal device 102, the electronic payment server 103, and other devices may be written in a script language such as JavaScript (registered trademark). The transmitted and received information may be written in a style sheet language such as CSS (Cascading Style Sheets) or a programming language such as Java (registered trademark). The transmitted and received information may be written in a markup language such as XML (Extensible Markup Language) or HTML (HyperText Markup Language). Alternatively, the information may be converted into a data description language such as JSON (JavaScript Object Notation) and then transmitted and received.
[0054] [4. An example of the hardware configuration of an information processing device] The message delivery server 101, terminal device 102, and electronic payment server 103 described above are realized, for example, by an information processing device 300 ("an example of a computer") configured as shown in FIG. 3. FIG. 3 is a block diagram showing an example of the hardware configuration of the information processing device 300. The information processing device 300 has a CPU 301, a ROM 302, a RAM 303, a storage device 304, an input / output I / F 305, and a network I / F 306. The components are connected to each other via a system bus.
[0055] (About CPU301) The CPU 301 reads a program stored in the ROM 302 into the RAM 303 and executes the read program to realize various controls. The CPU 301 may be an MPU (Micro Processing Unit) or an ASIC (Application Specific Integrated Circuit). The CPU 301 may also be an FPGA (Field Programmable Gate Array) or the like.
[0056] (About ROM302) The ROM 302 stores control programs such as a startup program for the information processing device 300.
[0057] (About RAM303) The RAM 303 temporarily stores control programs, data, etc. when the CPU 301 executes various controls. The RAM 303 is used as a work memory.
[0058] (Regarding storage device 304) The storage device 304 is a memory for storing applications, software, various data, and the like. Examples of the storage device 304 include a hard disk drive (HDD), a solid state drive (SDD), flash memory, and storage. If the storage device 304 is the message distribution server 101, it stores an MS user information database (hereinafter, the database will be referred to as DB), a store information DB, a registration information DB, and linkage flags, which will be described later. If the storage device 304 is the electronic payment server 103, it stores a PS user information DB, affiliated store information DB, and coupon information DB, which will be described later.
[0059] (About input / output I / F305) The input / output I / F 305 is an interface for transmitting output information to an output device such as a display unit 310. Examples of the display unit 310 include a display and a projector. The display unit 310 may be provided outside the information processing device 300 as shown in FIG. 3, or may be provided within the information processing device 300.
[0060] The input / output I / F 305 is an interface for receiving input information from an input device such as the input unit 311. Examples of the input unit 311 include a mouse, a keyboard, a button, and a touch panel. The input unit 311 may be provided outside the information processing device 300 as shown in FIG. 3, or may be provided within the information processing device 300.
[0061] Furthermore, the input / output I / F 305 may be connected wirelessly or by wire to the display unit 310 and the input unit 311. The input / output I / F 305 may be configured as being divided into an input I / F and an output I / F.
[0062] (About Network I / F306) The network I / F 306 is an interface for receiving data etc. from other devices via the network N, and for transmitting data generated or stored in the information processing device 300 etc. to other devices via the network N.
[0063] The information processing device 300 is not limited to the configuration shown in Fig. 3. For example, the terminal device 102 may be provided with a camera unit for realizing a camera function, a positioning unit for realizing a GPS function, and a microphone unit and a speaker unit for realizing a call function.
[0064] Information processing device 300 may also include a media I / F (not shown). The media I / F reads programs and data stored in a storage device (not shown) connected by wire or wirelessly, and provides them to CPU 301 via RAM 303. CPU 301 can read the provided programs from the storage device onto RAM 303 via the media I / F and execute the read programs. The storage device may be, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase Change Rewritable Disk), or a magneto-optical recording medium such as an MO (Magneto-Optical disk). The storage device may also be a tape medium, a magnetic recording medium, a semiconductor memory, or the like.
[0065] For example, when the information processing device 300 functions as the terminal device 102 , the CPU 301 of the information processing device 300 executes a program read onto the RAM 303 to realize various functions of the information processing device 300 .
[0066] The CPU 301 of the information processing device 300 reads and executes these programs from a storage device, but as another example, these programs may be acquired from another device via a predetermined communication network. Furthermore, it goes without saying that the information processing device 300 is provided with a configuration necessary to realize the information processing in this embodiment.
[0067] [5. An example of software configuration for a message delivery server] FIG. 4 is a diagram showing an example of the software configuration of the message delivery server 101. The configuration of the message delivery server 101 will be described with reference to FIG. 4. The message delivery server 101 has a communication unit 400, a control unit 410, and a storage unit 420. The control unit 410 includes a delivery unit 411, a receiving unit 412, a determination unit 413, a registration unit 414, and a request unit 415. The control unit 410 controls the entire message delivery server 101. The storage unit 420 includes an MS user information DB 421, an OA user information DB 422, a registration information DB 423, and a linkage flag 424.
[0068] (Regarding the communication unit 400) The communication unit 400 communicates with the terminal device 102, the electronic payment server 103, and other devices via the network N. The communication unit 400 functions as a transmission unit that transmits requests, information, and the like to the terminal device 102, the electronic payment server 103, and the like via the network N. The communication unit 400 receives instructions, information, and the like from the terminal device 102, the electronic payment server 103, and the like via the network N.
[0069] (About Distribution Section 411) The distribution unit 411 transmits a message to an MS user. For example, when the communication unit 400 receives information such as a character string, an image, and a video transmitted from the terminal device 102 of a first MS user, the distribution unit 411 transmits the information as a message to a second MS user who is the destination. The distribution unit 411 can also distribute a message to an MS user identified based on the distribution conditions set by the OA user and segment information indicating the attributes of the MS user (hereinafter referred to as segment distribution).
[0070] The message delivery unit 411 may deliver the message to MS users who have registered the OA user who is the message delivery source as a friend. For example, if a first MS user has registered the OA user as a friend, the message delivered from the OA user may be sent to the first MS user, and may not be sent to a second MS user who has not registered the OA user as a friend.
[0071] (Regarding the receiving unit 412) The receiving unit 412 receives a coupon acquisition instruction and the like from the terminal device 102 via the communication unit 400, and also receives an instruction to notify that a coupon has been acquired and linked processing information and the like from the electronic payment server 103. The coupon acquisition instruction includes the MS user ID of the MS user who is logged in to the message delivery app on the terminal device 102.
[0072] (Regarding the determination unit 413) The determination unit 413 determines the content of the request, instruction, information, etc. received by the reception unit 412. The distribution unit 411, and the registration unit 414 and request unit 415 (described later) each perform corresponding processing according to the determination result of the determination unit 413.
[0073] (Regarding the registration unit 414) The registration unit 414 performs a friend registration process. For example, the registration unit 414 performs the friend registration process in response to a linking instruction from the terminal device 102. Furthermore, when the reception unit 412 receives linking process information from the electronic payment server 103, the registration unit 414 performs a process of rewriting the linking flag to "Yes."
[0074] (Regarding the request unit 415) The request unit 415 makes a request to a device such as the electronic payment server 103. For example, when the receiving unit 412 receives an instruction to acquire a coupon, the request unit 415 transmits a coupon acquisition request to the electronic payment server 103 via the communication unit 400. The request unit 415 transmits link information together with the coupon acquisition request. Note that the link information may be transmitted together with the coupon acquisition request.
[0075] (About MS User Information DB421) The MS user information DB 421 stores information about MS users. Figure 5 is a diagram showing an example of MS user information stored in the MS user information DB 421. The message distribution server 101 manages MS users using the MS user information. The MS user information includes an MS user ID 501, user information 1 (502), user information 2 (503), and segment information 504.
[0076] The MS user ID 501 is an identifier for uniquely identifying an MS user. The MS user ID 501 is an example of first identification information. User information 1 (502) and user information 2 (503) are information indicating the contact information of the MS user, such as an email address and a phone number. Segment information 504 is information indicating the attributes of the MS user. The segment information 504 is used to identify target users for segment delivery. The segment information 504 includes the MS user's gender, age, address, hobbies, etc. The symbols "AR10" to "AR12" shown in the address column each indicate the address of the MS user. The address may indicate the MS user's residence, expressed as a prefecture and city / town / village, or may indicate the area where the MS user lives, such as Kanto or Kansai. When an OA user performs segment delivery, the delivery unit 411 delivers a message to MS users whose segment information 504 matches the target user conditions for segment delivery set by the user.
[0077] (About OA User Information DB422) Information about OA users is stored in the OA user information DB 422. Fig. 6 is a diagram showing an example of OA user information stored in the OA user information DB 422. The OA user information includes an OA user ID 601, a user name 602, URL information 603, address information 604, and contact information 605.
[0078] The OA user ID 601 is an identifier for uniquely identifying an OA user. An OA user can be a service provider that operates an electronic payment service, a member store or shop that has a contract with the service provider, or other shops that do not have a contract with the service provider. The user name 602 indicates the name of the OA user, which can be set arbitrarily. The URL (Uniform Resource Locator) information 603 indicates the URL information of the website established by the OA user. The address information 604 indicates the address or store location of the OA user. The contact information 605 indicates the contact information for the OA user. Examples of contact information include an email address or a telephone number.
[0079] Here, it is assumed that the OA user is a store of an affiliated store that has a contract with a service provider that operates an electronic payment service. In this case, as shown in FIG. 7, the message delivery server 101 can manage an OA user ID 601 by linking it with a store ID 701 (described later). FIG. 7 is a diagram showing an example of the link between the OA user ID 601 and the store ID 701. The link information between the OA user ID 601 and the store ID 701 shown in FIG. 7 is stored in the OA user information DB 422, for example, along with the above-mentioned OA user information. The store ID 701 is an identifier that can be shared by the message delivery server 101 and the electronic payment server 103. In other words, the store ID 701 is used to uniquely identify the store between the message delivery server 101 and the electronic payment server 103. For example, when a service provider that operates an electronic payment service enters into a contract with an affiliated store, the store ID 701 is an identifier shared between the message delivery server 101 and the electronic payment server 103 as information identifying the store of the affiliated store that has the contract.
[0080] (Regarding registration information DB423) The registration information DB 423 stores information linking an MS user with an OA user who has been registered as a friend by the user. FIG. 8 is a diagram showing an example of friend registration information stored in the registration information DB 423. The friend registration information includes an MS user ID 501 and an OA user ID 601. As shown in FIG. 8, one MS user ID 501 may be linked to multiple OA user IDs 601. The message distribution server 101 uses the registration information DB 423 to manage friend registrations of MS users. The registration information DB 423 may also store registration information (not shown) of an MS user and other MS users who have been registered as friends by the user.
[0081] As an example of friend registration, when the receiving unit 412 receives a link instruction, the determination unit 413 uses the friend registration information to determine whether the MS user who issued the coupon acquisition instruction has registered the OA user of the store that distributes the coupon as a friend. If the determination unit 413 determines that the MS user has not registered the OA user as a friend, the registration unit 414 associates the MS user ID 501 and the OA user ID 601 with the friend registration information and stores them in the registration information DB 423. As described above, this is because the present embodiment is configured to allow coupon acquisition in the electronic payment service in addition to friend registration in the message distribution service. Note that, in a configuration in which friend registration is not required to acquire a coupon in the electronic payment service, the determination unit 413 does not need to make a determination in response to the reception of the link instruction. Furthermore, in a case in which a friend registration has already been made in the message distribution service, the registration unit 414 does not perform re-registration.
[0082] (Regarding collaboration flag 424) The linkage flag 424 is a flag that indicates whether linkage processing executed by the electronic payment server 103 is in progress. When linkage processing is in progress, the linkage flag indicates "Yes," indicating that linkage processing has been performed. On the other hand, when linkage processing is not in progress, the linkage flag indicates "No," indicating that linkage processing has not been performed. Note that, although the linkage flag 424 has been described as being stored in the storage unit 420 separately from other databases, this is not a limitation. For example, the linkage flag 424 may be managed in association with the MS user ID 501 of the MS user information DB 421.
[0083] [6. An example of software configuration for an electronic payment server] FIG. 9 is a diagram showing an example of the software configuration of the electronic payment server 103. The configuration of the electronic payment server 103 will be described with reference to FIG. 9. The electronic payment server 103 has a communication unit 900, a control unit 910, and a storage unit 920. The control unit 910 includes a distribution unit 911, a reception unit 912, a determination unit 913, a linking unit 914, an granting unit 915, and a payment processing unit 916. The control unit 910 controls the entire electronic payment server 103. The storage unit 920 includes a PS user information DB 921, an affiliated store information DB 922, and a coupon information DB 923.
[0084] (About PS User Information DB921) Information about PS users is stored in the PS user information DB 921. Fig. 10 is a diagram showing an example of PS user information stored in the PS user information DB 921. The PS user information includes a PS user ID 1001, an age 1002, a gender 1003, an address 1004, contact information 1005, an account balance 1006, and a point balance 1007.
[0085] The PS user ID 1001 is an identifier for uniquely identifying a PS user. The PS user ID 1001 is an example of second identification information. The age 1002 indicates the user's age. The gender 1003 indicates the user's gender. The symbols "AR10" to "AR12" shown in the address 1004 indicate the PS user's address, respectively. The address may indicate the PS user's residence expressed by prefecture and city / town / village, or may indicate the area where the PS user lives, such as Kanto or Kansai. The address may indicate location information received from the terminal device 102. The age 1002, gender 1003, and address 1004 are information indicating the attributes of the PS user. Other information identifying the PS user may also be included in the PS user information. The contact information 1005 indicates the user's contact information. Examples of contact information include an email address or a phone number.
[0086] The account balance 1006 indicates the balance of digitized currency (hereinafter referred to as electronic money) in the user's electronic account. The electronic money may be, for example, points or currency used independently by various companies, or electronically tradable currencies provided by a country, such as Japanese yen or dollars. The user can pay for goods or services within the balance of the electronic account. The point balance 1007 indicates the balance of applicable points at the time of payment processing. Points are managed separately from electronic money and can be used as a substitute for electronic money. Points may be awarded by a service provider that operates an electronic payment service when certain conditions are met. Points are used in place of electronic money at a predetermined rate (for example, by converting "1 point" to "1 yen").
[0087] (About the affiliated store information DB922) The affiliated store information DB 922 stores information about affiliated stores that have contracts with service providers that operate electronic payment services. Figure 11 shows an example of affiliated store information stored in the affiliated store information DB 922. The affiliated store information includes an affiliated store ID 1101, a store ID 701, a store name 1102, URL information 1103, address information 1104, and contact information 1105.
[0088] The affiliated store ID 1101 is an identifier for uniquely identifying an affiliated store. As shown in FIG. 11, multiple stores can be linked to one affiliated store. The electronic payment server 103 manages affiliated stores using the affiliated store ID 1101. If an affiliated store has one store, the affiliated store and the store may be linked and managed in a one-to-one relationship in the electronic payment server 103. The store name 1102 indicates the name of the store, which can be set arbitrarily. The URL information 1103 indicates the URL of the store's dedicated website. The address information 1104 indicates the location of the store. The contact information 1105 indicates the store's contact information. Examples of contact information include an email address or a telephone number.
[0089] (Coupon information DB923) Coupon information DB 923 stores coupon information distributed in electronic payment services. Fig. 12 is a diagram showing an example of the distributed coupon information. The distributed coupon information includes a coupon ID 1201, coupon information 1202, a store ID 701, and an affiliated store ID 1101.
[0090] Coupon ID 1201 is an identifier for uniquely identifying a distributed coupon. As shown in FIG. 12, coupon ID 1201 is linked to the store ID of the store that distributed the coupon and the affiliated store ID of that store. Coupon information 1202 is information indicating the content of the coupon. Coupon information 1202 includes, for example, the expiration date of the coupon, the products or services to which the coupon can be applied, the coupon discount rate, the conditions for recipients of the coupon, and the conditions for applying the coupon.
[0091] The coupon expiration date is the date and time when the coupon can be used. For example, the coupon expiration date is expressed as "year / month / day / day". The goods or services to which the coupon can be applied are expressed as, for example, daily necessities, furniture, and home appliances, or dining at store X, or using △△ at store X. The coupon discount rate is the discount rate relative to the amount paid when the coupon is applied. For example, the coupon discount rate is expressed as 100 yen off, 10% off, or 1000 yen return.
[0092] The conditions for recipients of a coupon are, for example, the conditions for target users set by a store manager when distributing a coupon. For example, the conditions for recipients of a coupon may include users aged 20 or over, women only, and users who live in a certain area. The conditions for coupon application are the conditions under which the coupon can be used. For example, the conditions for coupon application may include products worth 1,000 yen or more, food and drink worth 2,000 yen or more, or first-time use at a certain store. The conditions for recipients of a coupon may also be set by the service provider providing the electronic payment service.
[0093] (Regarding the communication unit 900) The communication unit 900 communicates with the message delivery server 101, the terminal device 102, and other devices via the network N. The communication unit 900 has the same functions as the communication unit 400, and therefore a description thereof will be omitted.
[0094] (About the 911 distribution department) The distribution unit 911 distributes coupons and messages such as recommendation information in response to operations by the store manager. The distributed coupons can be acquired by PS users operating the electronic payment app. PS users can use the acquired coupons by fulfilling the coupon application conditions.
[0095] (Regarding the receiving unit 912) The receiving unit 912 receives a coupon acquisition request, linkage information, and the like from the message distribution server 101 via the communication unit 900, and also receives a page request and the like from the terminal device 102. Note that the receiving unit 912 can also receive a request to acquire a coupon from the terminal device 102.
[0096] (Regarding the determination unit 913) The determination unit 913 determines the content of the request, information, etc. received by the reception unit 912. The distribution unit 911, as well as the linking unit 914 and the attachment unit 915 (described later), each perform corresponding processing according to the determination result of the determination unit 913.
[0097] (About the Collaboration Unit 914) The linking unit 914 performs a process of linking the MS user's identification information with the PS user's identification information based on the determination made by the determination unit 913. For example, if the linking flag included in the linking information indicates "No," the linking unit 914 performs the linking process. If an intermediate device is used, as described above, the linking of the intermediate ID is performed in accordance with the user's registration operation in the electronic payment app, and the linking unit 914 can perform the linking process by receiving the MS user ID and the PS user ID from the intermediate device.
[0098] FIG. 13 is a diagram showing an example of linked information managed by the electronic payment server 103. When the linking process is performed by the linking unit 914, the electronic payment server 103 links the PS user ID 1001 with the MS user ID 501 and manages the linked information as linked information, as shown in FIG. 13. The linked information is stored in the PS user information DB 921, for example, along with the PS user information described above. Note that the linking unit 914 may also link the store ID 701 and affiliated store ID 1101 to the PS user ID 1001 and manage them as linked information, in addition to the MS user ID 501. If the linking flag included in the linking information indicates "Yes," the linking unit 914 does not perform the linking process.
[0099] (Regarding the granting unit 915) The granting unit 915 grants coupons to PS users. Examples of coupon granting methods include a first granting method in which a coupon is granted in response to an operation of an electronic payment app by a PS user, and a second granting method in which a coupon is granted in response to a coupon acquisition request from the message delivery server 101.
[0100] In the first granting method, the granting unit 915 grants a coupon in response to a PS user's operation on the electronic payment app screen. For example, a PS user can acquire a desired coupon by selecting the coupon from a coupon acquisition screen (not shown) of the electronic payment app. In this case, the terminal device 102 sends a request to the electronic payment server 103 to acquire the coupon, including the PS user ID of the PS user who is logged in to the electronic payment app. In response to the request, the electronic payment server 103 then grants the coupon to the requesting PS user.
[0101] In the second granting method, the granting unit 915 grants a coupon in response to a coupon acquisition request from the message delivery server 101. As described above, in response to an MS user's operation on a screen displayed by the message delivery app of the terminal device 102, the message delivery server 101 transmits a coupon acquisition request including an MS user ID to the electronic payment server 103. If the linking process has been performed or has already been performed by the linking unit 914, the granting unit 915 grants a coupon in response to the coupon acquisition request from the message delivery server 101. Specifically, the granting unit 915 grants a coupon identified by coupon ID 1201 to a PS user indicated by PS user ID 1001 linked to MS user ID 501 included in the linking information. Note that, if the linking flag indicates that linking has been performed, the granting unit 915 can transmit the MS user ID 501 to an intermediate device (not shown) and acquire the linked PS user ID 1001.
[0102] FIG. 14 shows the status of coupon acquisition by PS users. When the electronic payment server 103 grants a coupon to a PS user, it manages the coupon by linking the PS user ID 1001 with the coupon ID 1201, as shown in FIG. 14. The linking information between the PS user ID 1001 and the coupon ID 1201 shown in FIG. 14 is stored in the coupon information DB 923, for example, along with the distributed coupon information described above. FIG. 14 shows that one PS user has acquired multiple coupons. For convenience, FIG. 14 shows the linking information for one PS user, but it goes without saying that the linking information for all PS users is stored in the coupon information DB 923.
[0103] As shown in FIGS. 12 and 14, the electronic payment server 103 may issue coupons (C0002 and C0003) having similar coupon information 2 ("an example of the same benefit information") multiple times to the same user. For example, suppose a PS user is issued a coupon with a 10% discount (an example of coupon information 2) that can be used at a certain store. Thereafter, at any time, the PS user may be issued another coupon with a 10% discount that can be used at the same store.
[0104] The electronic payment server 103 may also simultaneously grant multiple coupons (C0001 and C0002) indicating coupon information 1 and coupon information 2 ("examples of mutually different benefit information") to the same user. For example, the same PS user may simultaneously be granted a coupon (C0001) with a 10% discount that can be used at a certain store and a coupon (C0002) with a 3% discount.
[0105] During electronic payment processing (at the time of payment), the electronic payment server 103 may automatically apply coupons from the coupon IDs 1201 shown in Fig. 14. For example, the electronic payment server 103 may preferentially apply coupons that are close to their expiration date or coupons with high discount rates.
[0106] (Regarding the payment processing unit 916) The payment processing unit 916 performs electronic payment processing when a user makes a payment at a store, etc. There are two types of electronic payment methods: a first electronic payment method in which a store clerk scans a code presented by the user and makes payment based on the scanned information, and a second electronic payment method in which a user reads a code placed in the store and makes payment based on the read information.
[0107] The first electronic payment method will be described. When a user launches an electronic payment app on the terminal device 102, the terminal device 102 sends a payment code generation request to the electronic payment server 103. Upon receiving the generation request, the electronic payment server 103 generates a payment code and sends the generated payment code to the terminal device 102. Here, the payment code is a code used in electronic payment processing and has an expiration date (for example, a few minutes). The payment code is sometimes referred to as a one-time code. The electronic payment server 103 does not perform electronic payment processing using a payment code that has expired. The terminal device 102 discards the expired payment code and sends a new generation request. In this way, the terminal device 102 can automatically update the payment code while the electronic payment app is running.
[0108] When the terminal device 102 receives the payment code, it analyzes the code, converts it into a code that can be read by the store, and displays the converted code. The store's reading device scans the displayed code, decodes it again, and obtains user identification information for the electronic payment app. The store's reading device then transmits the decoded user identification information and POS (Point of Sale) information to the electronic payment server 103. Here, POS is a system for collecting and managing information such as the products or services available at the store and the time the products or services were sold or provided. POS information includes store information and information such as the payment amount. In this type (store scan) in which the store's reading device scans the code for the electronic payment app, the store's reading device associates the user identification information with the POS information (payment information).
[0109] The electronic payment server 103 performs electronic payment processing based on the received code, POS information, etc. Specifically, the electronic payment server 103 transfers electronic money in the amount indicated by the payment amount from the PS user's account indicated by the user identification information to the store's account. The electronic payment server 103 then sends a notification that the payment has been completed to the store's reading device or terminal device 102. The store's reading device or terminal device 102 notifies the user that the payment has been made using electronic money by displaying a screen indicating that the payment has been completed or by outputting a specified audio message.
[0110] Next, a second electronic payment method will be described. When a user purchases or pays for a payment object such as various products or services at a store, the user reads a code displayed at the store using the camera function of terminal device 102. Examples of codes displayed at the store include one-dimensional codes such as barcodes, and two-dimensional codes such as QR (quick response) codes (registered trademark).
[0111] The terminal device 102 transmits the read code as store information to the electronic payment server 103 together with user identification information (PS user ID). The electronic payment server 103 transmits a screen for inputting the payment amount to the terminal device 102, which is the sender. The user inputs the amount required for payment using the terminal device 102. Alternatively, a store clerk inputs the amount required for payment using the terminal device 102. The terminal device 102 then transmits information about the input amount to the electronic payment server 103.
[0112] The process of transmitting the information about the entered amount to the electronic payment server 103 may be performed together with the transmission of the store information and user identification information described above. In this case, the terminal device 102 acquires the store information and then displays a screen for inputting the payment amount. Then, when the terminal device 102 determines that the amount required for payment has been entered, it transmits information about the entered amount, the store information, and the user identification information to the electronic payment server 103.
[0113] The electronic payment server 103 transfers the received amount of electronic money from the electronic account of the user who sent the message to the electronic account of the store linked to the received store information. The electronic payment server 103 sends a notification that the payment has been completed to the terminal device 102. The terminal device 102 notifies the user that the payment has been made using electronic money by displaying a screen indicating that the payment has been completed or by outputting a specified sound.
[0114] In addition, the service provider that operates the electronic payment service performs a transfer process to transfer the transferred electronic money from its own account to the store's account. The transfer process can be performed periodically (for example, about once a month).
[0115] Payment using the terminal device 102 may involve not only transferring electronic money from an electronic account to which the user has previously charged electronic money to the store's electronic account, but also, for example, payment using a credit card that the user has previously registered. In such a case, for example, the electronic payment server 103 may transfer the payment amount of electronic money to the store's electronic account and bill the user's credit card company for the payment amount.
[0116] Payments using the terminal device 102 may involve not only transferring electronic money from a user's electronic account to a store's electronic account, but also transferring electronic money from the user's electronic account to the electronic account of a provider (business) that provides a specific transaction object. In such cases, the user uses the camera of the terminal device 102 to read a barcode included in a payment slip (e.g., a transfer slip used in convenience store collection agency services) sent to the user by the business. The terminal device 102 then displays on its screen the payee and payment amount indicated by the read barcode. When the terminal device 102 receives an operation from the user approving the remittance to the payee, it transmits payment information indicating the user identification information, the payment amount, and information identifying the payee to the electronic payment server 103. In such cases, the electronic payment server 103 transfers electronic money in the amount indicated by the payment amount from the user's electronic account to the payee's electronic account.
[0117] [7-1. An example of the flow of information processing in the system] Fig. 15 is a sequence diagram showing an example of the flow of information processing among the message delivery server 101, the terminal device 102, and the electronic payment server 103. Fig. 16 is a diagram showing an example of a screen displayed on the terminal device 102. The flow of information processing according to this embodiment will be described with reference to Figs. 15 and 16.
[0118] In S1501 of FIG. 15, the message delivery server 101 delivers a message to the terminal device 102. For example, assume that a service provider operating an electronic payment service acquires an official account for the message delivery service and delivers messages as an OA user. In this case, a message related to a coupon is delivered from the official account of the message delivery app owned by the service provider. A service provider operating an electronic payment service may deliver a message related to a coupon from the official account of the message delivery app for the purpose of business expansion. For example, a message may be delivered that collectively delivers coupons currently available for electronic payment services, such as coupons from major chains. In this case, the delivered message is basically the same for all MS users, but the coupons to be delivered may be selected according to segment. When delivering such a message, the message delivery server 101 can obtain the coupon ID 1201, the store ID 701, and the like from the electronic payment server 103. An API (Application Programming Interface) can be used to obtain this information. In the above example, a service provider that operates an electronic payment service uses terminal device 102 to send an instruction to message delivery server 101 to deliver a message related to a coupon from its official account. When delivering the message related to the coupon, message delivery server 101 sends a request to an API provided by electronic payment server 103. Then, upon receiving the request, the API accesses the coupon management system of electronic payment server 103, obtains information such as coupon ID 1201 and store ID 701, and transmits that information as a response to message delivery server 101. Message delivery server 101 can include the obtained coupon ID 1201, store ID 701, etc. in a message related to the coupon and deliver it.
[0119] The above-mentioned message regarding the coupon distributed on the message distribution app is shown on display screen 1610 in FIG. 16. Display screen 1610 displays message 1611 regarding the distributed coupon and get coupon button 1612. Get coupon button 1612 is an example of an element for obtaining a benefit. Message 1611 displays, for example, the name of the affiliated store or shop along with a message encouraging the user to obtain the coupon. When the user wishes to obtain the coupon, he or she operates get coupon button 1612.
[0120] In S1502, the terminal device 102 transmits a coupon acquisition instruction to the message delivery server 101 in response to a user's operation on the coupon acquisition button 1612. The coupon acquisition instruction includes the MS user ID and the like. Upon receiving the coupon acquisition instruction, the message delivery server 101 determines whether the MS user who issued the instruction is linked. Here, it is assumed that the message delivery server 101 determines that the MS user is not linked.
[0121] In S1503, the message delivery server 101 transmits a permission screen 1620 requesting permission for the collaboration to the terminal device 102. Then, the permission screen 1620 is displayed on the terminal device 102, as shown in Fig. 16. The permission screen 1620 displays a message 1621 for confirming permission for the collaboration and a permission button 1622 for permitting the collaboration. If the user permits the collaboration, he or she operates the permission button 1622.
[0122] On the other hand, in S1502, if the message delivery server 101 determines that they are linked, it does not send the permission screen 1620 to the terminal device 102. In other words, once the linking process has been performed, the message delivery server 101 does not send the permission screen 1620 to the terminal device 102, but instead sends a coupon acquisition request or the like to the electronic payment server 103 in S1506, which will be described later.
[0123] In S1504, the terminal device 102 transmits a link instruction to the message delivery server 101 in response to the user's operation on the permission button 1622.
[0124] In S1505, the message distribution server 101 performs a friend registration process in response to receiving the link instruction. The message distribution server 101 identifies the OA user ID 601 from the acquired store ID 701, and performs a process of automatically registering the OA user linked to the OA user ID 601 as a friend of the MS user who issued the coupon acquisition instruction. Here, the OA user who becomes friends with the MS user is the affiliated store that distributed the coupon in the electronic payment service.
[0125] In S1506, the message delivery server 101 sends a coupon acquisition request and linkage information to the electronic payment server 103. The coupon acquisition request includes the acquired coupon ID 1201 and the MS user ID 501 of the requestor. Upon receiving the linkage information, the electronic payment server 103 determines the value indicated by the linkage flag included in the linkage information. Here, it is assumed that the electronic payment server 103 determines that the linkage flag indicates that linkage processing has not been performed.
[0126] In S1507, the electronic payment server 103 performs the linking process. Specifically, the electronic payment server 103 performs a process of linking the MS user ID 501 included in the received linking information with the PS user ID 1001 that it manages. When an intermediate device is used, the electronic payment server 103 performs the linking process using the received MS user ID 501 and PS user ID 1001.
[0127] In S1508, the electronic payment server 103 performs a coupon granting process. Specifically, the electronic payment server 103 associates the identified PS user ID 1001 with the ID 1201 of the received coupon and stores them in the coupon information DB 923.
[0128] In S1509, the electronic payment server 103 transmits a coupon acquisition notification instruction and linkage processing information to the message distribution server 101. The linkage processing information includes information indicating that linkage processing has been performed. Note that if linkage processing is not performed in S1507 in the series of processes, i.e., if linkage has already been performed, the linkage processing information does not need to be transmitted.
[0129] In S1510, when the message delivery server 101 receives the link processing information, it rewrites the value of the link flag associated with the user identification information to "Yes." In response to the coupon acquisition notification instruction, the message delivery server 101 transmits a coupon acquisition notification to the terminal device 102 of the MS user who issued the coupon acquisition instruction. In other words, the notification that a coupon has been acquired in the electronic payment service can be sent through a message delivery in the message delivery service. The coupon acquisition notification can be sent as a message from the official account of the service provider that operates the electronic payment service.
[0130] The terminal device 102 displays a coupon acquisition notification display screen 1630, as shown in Fig. 16. The display screen 1630 displays a message 1631 indicating that the coupon has been acquired, and a confirmation button 1632 for confirming that the coupon has been acquired. If the user wishes to confirm the acquired coupon, the user operates the confirmation button 1632. The confirmation button 1632 is an example of an element for confirming that the benefit has been granted.
[0131] In S1511, the terminal device 102 starts the electronic payment application in response to the user's operation on the confirmation button 1632, and transmits to the electronic payment server 103 a request to transition to a screen for confirming the acquired coupon.
[0132] In S1512, the electronic payment server 103 sends a confirmation screen to the terminal device 102 to confirm that the coupon has been acquired, as a response to the request from the terminal device 102. Then, upon receiving the response, the terminal device 102 displays a confirmation screen 1640 as shown in Fig. 16. The confirmation screen 1640 displays an affiliated store 1641 of the store that distributed the coupon, and a display 1642 indicating that the coupon has been acquired.
[0133] [7-2. Information processing of other systems] In Figure 15, we have explained a case where a service provider that operates an electronic payment service acquires an official account and distributes coupon-related messages as an OA user. In addition to this case, a store manager may also acquire an official account and distribute coupon-related messages as an OA user. Below, we will use Figure 15 to explain the processing that differs from the previously explained case for a case where an affiliated store distributes coupon-related messages as an OA user.
[0134] In S1501, the message delivery server 101 delivers a message to the terminal device 102. In this case, the delivery of this message is performed in conjunction with the delivery of a coupon by the electronic payment server 103. In this case, when a coupon delivery event occurs, the electronic payment server 103 sends a coupon delivery notification to the message delivery server 101. Upon receiving the notification, the message delivery server 101 performs processing to deliver a message from the official account of the store that delivered the coupon. Note that delivery of a message related to a coupon can be performed from the official account at any time. The coupon delivery notification may include the store ID 701 and coupon ID 1201 linked to the delivered coupon.
[0135] In S1505, the message distribution server 101 can automatically register the official account of the service provider that operates the electronic payment service as a friend of the MS user who issued the coupon acquisition instruction. The above is the difference in the case where an affiliated store distributes a message about a coupon as an OA user.
[0136] As explained in the two possible cases, a process will be performed to automatically add the official account of the service provider or the official account of the affiliated store, which is different from the account that sent the coupon message, as a friend.
[0137] In cases where messages are delivered on the condition that the PS user has registered the OA user who sent the message as a friend, friend registration provides the PS user with more opportunities to receive benefits such as coupons, thereby improving user satisfaction. Furthermore, obtaining the coupon for the electronic payment service included in the message from the OA user in the message delivery service requires only one tap. In other words, if a coupon has been successfully obtained once using this scheme, the linking process is complete. In this case, the permission screen 1620 shown in FIG. 16 does not need to be displayed. In other words, a user who has viewed the OA user's message in the highly readable message delivery service can obtain a coupon for the electronic payment service, a completely different service, with a simple operation on the message delivery app.
[0138] [8. An example of the information processing flow of an electronic payment server] 17 is a flowchart showing an example of processing executed by the electronic payment server 103. The processing performed by the electronic payment server 103 to grant a coupon in response to a coupon acquisition request will be described with reference to FIG.
[0139] In S1700, the receiving unit 912 receives the coupon acquisition request and the link information via the communication unit 900. At this time, the receiving unit 912 acquires the link flag included in the link information.
[0140] In S1701, the determination unit 913 determines whether the acquired cooperation flag indicates “Yes” or “No.” If the determination unit 913 determines that the cooperation flag indicates “Yes” (Yes), the process proceeds to S1703, and if the determination unit 913 determines that the cooperation flag indicates “No” (No), the process proceeds to S1702.
[0141] In S1702, the linking unit 914 performs the above-described linking process. In S1703, the granting unit 915 performs a process of granting the coupon indicated in the received coupon acquisition request to the user who made the request.
[0142] In S1704, when the granting process is completed by the granting unit 915 in S1703, the communication unit 900 transmits a coupon acquisition notification instruction and linkage process information to the message distribution server 101, and the process shown in FIG. 17 ends.
[0143] [9. Effects] When there are multiple services to be provided, i.e., when there are multiple apps for receiving the services, the burden on the user to operate the terminal device increases. According to this embodiment, by linking the user identification information managed by the servers that provide different services, the user can obtain benefits delivered by the electronic payment service without operating the electronic payment app. In other words, the operational burden on the user can be reduced, thereby improving usability.
[0144] Furthermore, one service can be used to provide another service. For example, a coupon service provided by an electronic payment server can be effectively provided by utilizing the functions of a message delivery service, which has a high advertising effect.
[0145] [10. Information processing when friend registration has been completed] FIG. 18 is a diagram showing information processing when an OA user who is the store that distributes the coupon is registered as a friend. The case where the MS user who requested to acquire the coupon has not registered the OA user as a friend was explained with reference to FIG. 1, but information processing when the OA user has registered as a friend will be explained with reference to FIG. 18. The basic configurations of the message distribution server 101, terminal device 102, and electronic payment server 103 are the same as those shown in FIG. 1. Furthermore, S1, S3, and S6-S12 in FIG. 1 and S1801, S1803, and S1805-S1811 in FIG. 18 are similar processes, so their explanations will be omitted.
[0146] 18, the terminal device 102 transmits a coupon acquisition instruction to the message distribution server 101. Then, upon receiving the coupon acquisition instruction, the message distribution server 101 determines whether the MS user who issued the instruction has registered the OA user, who is the store that distributed the coupon, as a friend. Here, the message distribution server 101 determines that the OA user is registered as a friend.
[0147] 18, the terminal device 102 transmits a link instruction to the message delivery server 101. Then, upon receiving the link instruction, the message delivery server 101 transmits a coupon acquisition request or the like to the electronic payment server 103. In this case, the processing of S5 described in FIG. 1 is not performed.
[0148] In this way, if an MS user has registered an OA user who is a member store of the affiliated store that distributed the coupon as a friend, the message distribution server 101 sends a coupon acquisition request and linkage information to the electronic payment server 103 without performing the friend registration process.
[0149] [11.Other] In the above description, an example has been given in which the electronic payment server 103, when performing the linking process, transmits linking process information to the message delivery server 101. If the electronic payment server 103 does not perform the linking process, that is, if it determines that the linking process has already been performed, it does not need to transmit the linking process information to the message delivery server 101. In this case, the electronic payment server 103 may transmit the coupon acquisition notification instruction together with the MS user ID 501.
[0150] In the above description, the linking process is performed when a coupon acquisition request is received. However, the linking process may be performed even if a coupon acquisition request is not received. That is, the linking process may be performed before a coupon acquisition request is received. In this case, the electronic payment server 103 may perform the linking process in response to a linking instruction from the message delivery server 101 or the terminal device 102, for example.
[0151] Furthermore, the configuration of the terminal device 102 described above can be flexibly changed, for example, by calling an external platform or the like using an API or network computing, depending on the function.
[0152] Furthermore, the above-described embodiments can be combined as appropriate within the scope of not causing any contradiction in the processing content. [Explanation of symbols]
[0153] 101 Message Delivery Server 102 Terminal Equipment 103 Electronic Payment Server 424 Collaboration Flag 900 Communications Department 911 Broadcasting Department 912 Receiving unit 914 Collaboration Department 915 Granting Department 916 Payment Processing Unit 921 PS User Information DB 922 Member store information DB 923 Coupon Information DB
Claims
1. An information processing device that provides an electronic payment service, a receiving unit that receives a request to acquire a benefit that can be used in the electronic payment service from an external device that provides a message delivery service; an awarding unit that awards the benefit to the user who has made the request to receive the benefit in the message delivery service, on the condition that first identification information that identifies the user who receives the message delivery service and is associated with second identification information that identifies the user who receives the electronic payment service; An information processing device comprising:
2. 2. The information processing device according to claim 1, wherein the electronic payment service is an electronic payment service using code information.
3. The information processing device according to claim 1, further comprising a transmitting unit that, when the granting unit grants the privilege, transmits an instruction to the external device to cause the external device to send a message indicating that the privilege has been granted to the user's terminal device.
4. The message indicating that the reward has been granted includes an element for confirming the reward; The information processing device described in claim 3, characterized in that when the receiving unit receives a request for a confirmation screen of the benefit from the user's terminal device in response to the element being operated by the user, the transmitting unit transmits the confirmation screen to the terminal device.
5. The information processing device according to claim 1 , wherein the granting unit grants, as the benefit, a coupon that can be used to pay for goods or services in the electronic payment service to the user who has made the acquisition request.
6. The information processing device according to claim 1, characterized in that the external device distributes a message from the official account of the store on the message distribution service indicating that the benefit, which can be used at a store that has a contract with a service provider that operates the electronic payment service, can be obtained.
7. The information processing device according to claim 1, characterized in that the external device distributes a message from the official account of the service provider on the message distribution service indicating that the benefit, which can be used at stores that have a contract with the service provider that operates the electronic payment service, can be obtained.
8. The message indicating that the reward can be obtained includes an element for obtaining the reward, 8. The information processing apparatus according to claim 6, wherein the acquisition request is made from the external device in response to a user operating the element.
9. the message indicating that the benefit can be obtained includes an element for registering the store as a friend in the message delivery service and obtaining the benefit; 8. The information processing device according to claim 7, wherein the acquisition request is made from the external device in response to the element being operated by the user, and a process of registering the store as a friend is performed by the external device.
10. The information processing device according to claim 6 or 7, wherein the message indicating that the benefit can be obtained is delivered from the official account at any timing.
11. 2. The information processing device according to claim 1, wherein the benefit is a coupon that is automatically applied at the time of payment in the electronic payment service.
12. 2. The information processing device according to claim 1, further comprising a linking unit that performs processing to link the first identification information and the second identification information when the first identification information and the second identification information are not linked.
13. 13. The information processing device according to claim 12, wherein the linking unit performs the processing using the first identification information and the second identification information received from an intermediate device that stores the first identification information and the second identification information in association with each other.
14. 13. The information processing apparatus according to claim 12, wherein the processing performed by the coordinating unit can be performed regardless of whether the receiving unit has received the acquisition request.
15. 8. The information processing device according to claim 6, wherein the granting unit is capable of granting the same benefit indicating the same benefit information at the same store to the user who has made the acquisition request multiple times.
16. 8. The information processing device according to claim 6, wherein the granting unit is capable of simultaneously granting a plurality of benefits indicating mutually different benefit information for the same store to the user who has made the acquisition request.
17. An information processing method of an information processing device that provides an electronic payment service, a receiving step of receiving a request to acquire a benefit that can be used in the electronic payment service from an external device that provides a message delivery service; a granting step of granting the benefit to the user who has made the request to receive the benefit in the message delivery service, on the condition that first identification information identifying the user who receives the message delivery service is linked to second identification information identifying the user who receives the electronic payment service; 2. An information processing method for an information processing device, comprising:
18. A program for an information processing device that provides electronic payment services, On the computer, a receiving step of receiving a request to acquire a benefit that can be used in the electronic payment service from an external device that provides a message delivery service; a granting step of granting the benefit to the user who has made the request to acquire the benefit in the message delivery service, on the condition that first identification information identifying the user who receives the message delivery service and is associated with second identification information identifying the user who receives the electronic payment service; A program for an information processing device, characterized by causing the information processing device to execute the above.
19. An information processing system including an information processing device that provides an electronic payment service and an external device that provides a message delivery service, the information processing device receives, from the external device, a request to acquire a benefit that can be used in the electronic payment service; The information processing device grants the benefit to the user who has made the request to acquire the benefit in the message delivery service, on the condition that first identification information identifying the user who receives the message delivery service and is provided with the message delivery service is linked to second identification information identifying the user who receives the electronic payment service. An information processing system comprising:
Citation Information
Patent Citations
Information processor, information processing method, and information processing program
JP2020004122A
Information processor, information processing method and information processing program
JP2022058000A