Information processing device, information processing method, and program

Abstract

To improve usability. [Solution] An information processing device comprising: an acquisition unit that acquires an electronic payment request using the payment function of an electronic payment service via the merchant app of a merchant of the electronic payment service; and a processing unit that, upon acquiring the request, executes a process to grant the benefits of the electronic payment service to the user who made the request, based on the attributes of the user who made the request managed in the electronic payment service and the conditions for granting benefits corresponding to the merchant app.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, and a program.

Background Art

[0002] Conventionally, based on order information regarding a user's order by e-commerce for a store selling goods by e-commerce, a service is disclosed that gives a first stamp indicating that the order procedure regarding the order by the user has been completed to the user (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the conventional technology, usability may not be sufficient.

[0005] The present invention has been made in consideration of such circumstances, and one of the objectives is to provide an information processing apparatus, an information processing method, and a program that can improve usability.

Means for Solving the Problems

[0006] One aspect of the present invention is an information processing device comprising: an acquisition unit that acquires an electronic payment request using the payment function of an electronic payment service via a merchant app of a merchant of an electronic payment service; and a processing unit that, in response to acquiring the request, executes a process to grant the benefits of the electronic payment service to the user who made the request, based on the attributes of the user who made the request managed in the electronic payment service and the conditions for granting benefits corresponding to the merchant app. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an information processing device, an information processing method, and a program that can improve usability. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows an example of a configuration for implementing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payments. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payments. [Figure 4] This is a configuration diagram of the payment server 100 according to the embodiment. [Figure 5] This figure shows an example of the contents of user information 172. [Figure 6] This figure shows an example of the contents of merchant / store information 176. [Figure 7] This diagram shows an example of the contents of bonus information 178. [Figure 8] This diagram explains the contents of app information 180. [Figure 9] This is a diagram showing the interface screen IF1. [Figure 10] This is a diagram showing the interface screen IF2. [Figure 11] This is a diagram to explain how benefits are granted. [Figure 12]This sequence diagram shows an example of the processing flow performed by the merchant app 30, the payment app 20, and the payment server 100. [Figure 13] This is a diagram illustrating the generation and storage of one-time codes. [Figure 14] This flowchart shows an example of the process performed by the payment server 100 to determine whether to grant the first or second benefit. [Figure 15] This diagram shows the interface screen, including notifications. [Modes for carrying out the invention]

[0009] The information processing device, information processing method, and program embodiments of the present invention will be described below with reference to the drawings. Various devices used to provide services to users or perform internal analysis, such as the "payment server (information processing device)" described below, may be implemented by a distributed group of devices, and the operators of each device may be different. Furthermore, the owner of the hardware of the devices (the provider of the cloud server) and the operator that actually operates them may also be different. The application program and the payment server work together to provide electronic payment services. In the following description, the application program will be referred to as a payment app. The electronic payment service is a service that supports payment for the purchase of goods and services at a store. A store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for e-commerce. A virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when settling a purchase at the virtual store, the user is controlled to transition to the interface screen of the electronic payment service. In the electronic payment service, stores are treated as belonging to, for example, affiliated merchants (brands), and processing such as payment when a purchase is made at a store is mainly carried out between the user and the affiliated merchant. Alternatively, payment and other processing may be conducted between the user and the store.

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

[0011] [User Terminal Device] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), and the like. In the user terminal device 10, by executing a payment applet 20 by a processor such as a CPU, it operates to provide an electronic payment service to the user in cooperation with the payment server 100. The payment applet 20 is installed in the user terminal device 10 from, for example, an application store, and controls a camera, a communication device, a touch panel, and the like.

[0012] <~ In the user terminal device 10, by executing a franchise applet 30 by a processor such as a CPU, it operates to provide services provided by a franchise server or an electronic payment service to the user in cooperation with a franchise server (not shown) or the payment server 100. The franchise applet 30 is an application program provided by a franchise. The franchise applet 30 is, for example, an app of a ○○ convenience store or an app of a ○○ drug store. The franchise applet 30 is installed in the user terminal device 10 from, for example, an application store, and controls a camera, a communication device, a touch panel, and the like.

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

[0014] [Second store terminal device] The second store terminal device 70 is used by the operator of the franchise store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for franchise stores operates. The interface 72 for franchise stores may be an application for franchise stores or a browser. The interface 72 for franchise stores accepts settings of coupons, etc. by the operator of the franchise store and transmits them to the settlement server 100. The second store terminal device 70 which is a smartphone has a function of displaying a code image corresponding to the store code image or reading the code image displayed by the user terminal device 10 by executing an application for franchise stores.

[0015] The settlement server 100 realizes electronic settlement based on the settlement information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and a franchise store server. In that case, the settlement information is transmitted from the POS device to the settlement server 100 via the franchise store server. In the following description, this is not particularly distinguished, and it is assumed that the settlement information is transmitted from the first store terminal device 50.

[0016] FIG. 2 and FIG. 3 are sequence diagrams illustrating a rough flow of electronic settlement. There may be two patterns, pattern 1 and pattern 2, in the electronic settlement.

[0017] In the case of Pattern 1 shown in Figure 2 (hereinafter referred to as User Scan), the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 contains information about the store URL (Uniform Resource Locator). This store URL is an electronic payment service domain to which information that can identify the store has been added, and is associated with the merchant ID and store ID, etc., at the payment server 100 (described later). The payment application 20 sends the first payment information, including the store URL and account ID, to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the merchant ID and store ID corresponding to the store URL, obtains the merchant name and store name information (S3), and sends it to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen where the merchant name and store name are displayed (S5). The user terminal device 10 then generates second payment information, including at least the payment amount, and sends it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notification (information for displaying the payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). If the store code image 60 is displayed on a display placed in the store, the store code image 60 may include payment amount information as well as the store URL. In this case, the procedure for the user to enter the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Merchant name and store name information may be included and displayed on the payment completion screen.

[0018] In the case of Pattern 2 shown in Figure 3 (hereinafter referred to as Store Scan), when the payment app 20 is launched, when a payment operation is performed in the payment app 20, when it is time for an automatic update (for example, every minute), and at other times, the payment app 20 sends a request to the payment server 100 to issue a one-time code (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image such as a QR code or barcode that was generated based on the one-time code (S14). The user holds the display surface of the user terminal device 10 over the first store terminal device 50 (presents it), and the first store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including the one-time code, payment amount, merchant ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is obtained in advance by barcode scanning or manual input. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs the electronic payment (S17). The payment server 100 then sends a payment completion notification to the payment app 20 (S18), and the payment app 20 displays a payment completion screen (S19).

[0019] Furthermore, electronic payment may be performed using only one of the above patterns. Also, the "account ID" explained in Figure 2 may be other information (for example, a phone number) that can be used as identification information (user identification information) to identify the user. In addition, the issuance of a one-time code may be omitted during store scanning, and the payment app 20 may display a code image generated based on the user's account ID. In that case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0020] [Payment Server] Figure 4 is a configuration diagram of a payment server 100 according to an embodiment. The payment server 100 includes, for example, a communication unit 110, a content provision unit 120, a payment processing unit 130, an information management unit 140, a benefits processing unit 150, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit), or by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed in the storage device when the storage medium is mounted on a drive device. The Information Management Unit 140 is an example of an "acquisition unit". The Benefit Processing Unit 150, a configuration combining the Benefit Processing Unit 150 and the Payment Processing Unit 130, a configuration combining the Benefit Processing Unit 150, the Payment Processing Unit 130 and the Content Provision Unit 120, or a configuration combining these with the Information Management Unit 140 are examples of "processing units".

[0021] The storage unit 170 can be an HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may also be a NAS (Network Attached Storage) device that the payment server 100 can access via the network. The storage unit 170 stores information such as user information 172, content information 174, merchant / store information 176, benefit information 178, and application information 180.

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

[0023] The content provision unit 120, for example, has the functionality of a web server and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The content provision unit 120 reads the necessary content from the content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs from the user while the content is being played by the payment application 20 and transmits the aforementioned payment information and other data to the payment server 100.

[0024] The payment processing unit 130 performs payment processing based on payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0025] [User information] Figure 5 shows an example of the contents of User Information 172. User Information 172 is an example of user registration information. User Information 172 includes, for example, user URL, account ID, phone number, password, as well as information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit payment settings, credit payment limit, credit payment amount, available credit payment amount, payment method settings, bank account, credit card number, charge history information, payment history information, eKYC information (electronic Know Your Customer), and information about benefits. The user URL is used for money transfer processing between users. When registering for a new electronic payment service, registration of a phone number and password is mandatory. The account ID is issued to the user by the payment server 100, and the user ID is an ID that the user can set at will (or does not have to set). Similarly, the email address and name, address, and date of birth are also information that the user can set at will (or does not have to set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

[0026] The charge balance is information indicating the balance of electronic money set by the user by sending money to their account in advance. Methods of sending money include sending from an ATM (Automatic Teller Machine) of a designated provider (bank) and sending from a registered bank account. The credit payment setting indicates whether or not the user has completed the settings to enable electronic payments by credit card, and is set to either "Completed" or "Not Completed". The credit payment limit is the monthly limit for credit payments, the credit payment amount is the amount already used for credit payments in the current month, and the available credit payment amount is the amount available for credit payments in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the diagram shows only one credit payment limit, in reality there are also daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be described later. The payment method setting indicates whether the user will use electronic payment with the charge balance or payment by credit card at that time. The bank account and credit card number information, respectively, refers to the bank account or credit card number (account number, card number) to which funds can be deposited into the electronic payment service. The charge history information is a record of when the user has previously sent money to the electronic payment service to increase the charge balance. The payment history information shows the details of each payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0027] eKYC information is information obtained through identity verification performed by the user in the electronic payment service. eKYC information includes, for example, name and age. In addition to the above, eKYC information may also include some or all of the following information: region of residence (prefecture or city / ward / town / village), address, gender, family structure, date of birth, etc. Identity verification is performed using designated identification documents such as a My Number Card, driver's license, passport, or health insurance card. For example, identity verification is performed by sending an image of the identification document to the payment server 100. The payment server 100 performs identity verification by checking the information contained in the identity verification image. For example, the payment server 100 completes identity verification when the information contained in the identity verification image matches the information provided by the user to the payment server 100 (information entered on the interface screen). Information regarding benefits is benefits that can be used in the electronic payment service, such as points and coupons held by the user.

[0028] Figure 6 shows an example of the contents of the merchant / store information 176. The merchant / store information 176 includes, for example, a first table 176A in which the merchant ID and store ID are associated with the store URL, a second table 176B in which the merchant name and sales amount (as described above) are associated with the merchant ID, and a third table 176C in which the store name is associated with the store ID. In addition to this information, the merchant / store information 176 may also include information such as the merchant or store category, the store's location, and payment patterns.

[0029] The Information Management Unit 140 manages user information 172 and affiliated store / store information 176 based on information obtained from the user terminal device 10 and the second store terminal device 70. The Information Management Unit 140 performs operations such as adding, editing, and deleting new records for user information 172 and affiliated store / store information 176.

[0030] The information management unit 140, for example, obtains electronic payment requests using the payment function of an electronic payment service via the merchant app 30 of a merchant participating in the electronic payment service. Details of this process will be described later.

[0031] [Electronic payment] When the payment processing unit 130 obtains payment information from the user terminal device 10 or the first store terminal device 50, it refers to the user information 172 to obtain the user's "payment method setting". For users whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance, which is managed in association with the user ID, and increasing the value of the merchant's sales proceeds item. For example, the value of the merchant's sales proceeds item is not used as electronic money itself, but rather the amount corresponding to the value of the sales proceeds item is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service.

[0032] The payment processing unit 130 performs electronic payment as follows for users whose "settings information" is set to "credit payment". Credit payment is a payment method that is carried out in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the donor and allows electronic payment that does not depend on the charge balance within the credit payment limit. In order to use the credit payment service, it may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used by credit payment is settled in a lump sum for the month on the payment date of the following month, for example, by withdrawal from a bank account. In this case, the payment processing unit 130 performs a provisional settlement by adding the settlement amount to the amount used by credit payment and subtracting the same amount from the available credit payment limit. When the closing date arrives, it processes the payment for the current month to be withdrawn on the payment date of the following month as described above, or requests the credit card company operator to perform the said process. If the settlement amount exceeds the available credit payment limit at the time of provisional settlement, an error notification is sent back to the payment application 20.

[0033] [Bonus Processing] The benefits processing unit 150, upon receiving a request from the information management unit 140, executes a process to grant the benefits of the electronic payment service to the user who made the request, based on the user's attributes (e.g., eKYC information) managed in the electronic payment service and the conditions for granting benefits corresponding to the merchant app 30. The request is an electronic payment request using the payment function of the electronic payment service via the merchant app 30 of an electronic payment service merchant. The request is, for example, an electronic payment request made by calling the payment function of the electronic payment service by operating the merchant app 30.

[0034] The payment server 100 receives the request, which includes user identification information and merchant identification information, and if the user's age, which is associated with the user identification information and is managed in the electronic payment service, meets the age requirements specified by the merchant, it performs a process to associate a higher level of benefit than in case (1) or (2) below with the user identification information of the user who made the request. (1) refers to the fact that an electronic payment was made at the merchant using the payment app 20 of the electronic payment service without going through the merchant app 30. (2) refers to the case where an electronic payment service was used via the merchant app 30, but the user's age did not meet the specified age requirement.

[0035] The request includes, for example, user identification information that can identify the user and merchant identification information that can identify the merchant in the merchant app 30. Upon receiving the request, the reward processing unit 150 performs a process to associate the reward with the user identification information that made the request, which is managed in the electronic payment service. The reward processing unit 150 performs the above matching process and grants the reward to the user identification information in the user information 172. The above process is an example of a process for granting a reward to the user who made the request.

[0036] The benefits could be, for example, benefits usable with an electronic payment service. The benefits could be, for example, points for an electronic payment service. The benefits could also be various types of benefits, such as coupons usable with an electronic payment service, or vouchers for specific goods or services. The benefits could also be benefits usable with other services, not just electronic payment services.

[0037] Figure 7 shows an example of the contents of reward information 178. Reward information 178 is information that associates rewards corresponding to electronic payments made via the merchant app 30 with the conditions for granting those rewards. In the example in Figure 7, at the merchant with merchant ID "A", users under a certain age receive 5% of the payment amount as points. The payment server 100 manages the IDs of the merchant apps that correspond to the merchant IDs, and the merchant ID can be recognized from the ID of the merchant app.

[0038] The benefits processing unit 150 refers to the app information 180 and executes various processes described later. Figure 8 is a diagram illustrating the contents of the app information 180. The app information 180 is information that associates, for example, user identification information such as an account ID, a merchant ID, an app ID, and linkage information. The app ID is, for example, information indicating the type of app. The app ID is, for example, information that can identify each of the multiple merchant apps 30 (information that can identify the merchant of the merchant app 30). The app ID is information that can identify each of the multiple merchant apps 30 and may also be user-specific information.

[0039] Linkage information is, for example, information indicating whether the payment app 20 and the merchant app 30 are already linked. For example, if a user operates either the merchant app 30 or the payment app 20 and agrees to the linkage, the linkage between the merchant app 30 and the payment app 20 is completed. In this case, the reward processing unit 150 changes the linkage information in the app information 180 to "linked".

[0040] [Electronic payment using merchant apps] When the above-described linkage is established, electronic payment is made by calling and using the payment function of the electronic payment service via the merchant app 30, as follows. For example, the merchant app 30 uses its browser function to link with the payment server 100 and displays code information based on the one-time code sent by the payment server 100 on the display unit. Payment is made based on this code information. The reward processing unit 150 receives a request sent in response to an operation performed by the user to make an electronic payment using the payment function by operating the merchant app 30 (such as pressing a button or performing other configured operations, as described later), and grants the reward to the user.

[0041] For example, when a user launches the merchant app 30, the interface screen IF1 shown in Figure 9 is displayed on the display unit of the user terminal device 10. When the user operates a button on the interface screen IF1 (for example, a designated button or area such as the payment button B1), the merchant app 30 causes the display unit to display interface screen IF2 (see Figure 10), which includes code information based on a one-time code (such as a barcode or QR code).

[0042] For example, the function that calls the payment function of an electronic payment service via the merchant app 30 mentioned above (the function that displays code information) utilizes a so-called deep link function. A deep link is a link that allows direct navigation to specific content such as an application program. This process may utilize a technology other than deep linking.

[0043] The merchant's first store terminal device 50 acquires code information and transmits the one-time code obtained from the code information to the payment server 100. The payment server 100 executes the electronic payment using the one-time code. Once the electronic payment is complete, the payment server 100 grants the reward to the user.

[0044] The interface screen IF2 described above may be an interface screen displayed on the display unit by the merchant app 30, as described above, or it may be an interface screen displayed on the display unit by the payment app 20 in cooperation with the merchant app 30. When the payment app 20 displays the interface screen IF2 on the display unit, the payment app 20 obtains a one-time code from the payment server 100 and displays the code information on the display unit.

[0045] [Regarding the provision of benefits] Figure 11 is a diagram illustrating the granting of benefits. The benefits processing unit 150 grants the first benefit to the user if the conditions for granting benefits set by the merchant are met in an electronic payment made via the merchant app 30. The benefits processing unit 150 grants the second benefit to the user if the conditions for granting benefits set by the merchant are not met in an electronic payment made via the merchant app 30. The benefits processing unit 150 grants the second benefit (or third benefit) to the user in the case of an electronic payment made not via the merchant app 30. For example, the benefits are ordered from most beneficial to the user (highest grant rate) in the order of first benefit, second benefit, and third benefit.

[0046] The above conditions are those specified by the merchant. These specified conditions include, for example, that the user's attributes meet certain criteria. These user attributes are those identified from identity verification information performed and managed within the electronic payment service. These attributes are, for example, those included in eKYC information. Examples of these attributes include age and address.

[0047] The above attributes may be those managed by the electronic payment service, in addition to (or instead of) the attributes included in the eKYC information. For example, attributes of the information included in user information 172 may be used. For example, attributes of the information obtained when applying to use the electronic payment service may be used, or attributes of the information obtained when using the electronic payment service (various payment history and information obtained through linkage with other services) may be used.

[0048] The first benefit is the one that offers a greater degree of reward than the second benefit. For example, if the benefit is the redemption of points for an electronic payment service, the redemption rate for the first benefit is higher than the redemption rate for the second benefit.

[0049] The merchant will bear some or all of the costs of the first benefit described above. For example, the merchant will bear the costs of the difference between the first and second benefits. The benefits may be set by the merchant or by the administrator of the electronic payment service.

[0050] Furthermore, the benefit will be granted if the above conditions for granting (for example, age, address, and region of residence) are met, and the benefit may not be granted if the conditions for granting are not met.

[0051] As described above, the payment server 100 can grant the first benefit to users who meet the merchant's desired conditions in electronic payments via the merchant app 30. This can improve usability. For example, a merchant can grant the first benefit to specific users. More specifically, for example, a merchant may want to promote the use of their services. In particular, they may want to turn users in a certain segment (e.g., those under a certain age) into loyal customers. For example, by having users install the merchant app 30, it is expected that usage frequency will increase and they will be elevated to loyal customers. However, merchants may not manage user information.

[0052] In this embodiment, as described above, merchants can achieve the above objectives by utilizing the electronic payment service. For example, the electronic payment service performs identity verification, and instead of the merchant using this information, the electronic payment service can determine whether or not the conditions specified by the merchant are met. Furthermore, in addition to meeting the conditions, the first benefit of the electronic payment service can be granted to users who meet the conditions and make an electronic payment via the merchant app 30, thereby promoting the use of the merchant app 30 at the merchant. This promotes the use of the merchant app 30 and the merchant by the target users.

[0053] As described above, by having the electronic payment service, the merchant app 30, and the merchant work together to perform the processes described, merchants can engage in marketing that is more suitable for them. Furthermore, users can receive the first benefit by participating in the above scheme, thus improving convenience for users. This also promotes the use of the electronic payment service. In this way, the usability for merchants, users, and the electronic payment service is improved.

[0054] [Sequence Diagram] Figure 12 is a sequence diagram showing an example of the processing flow performed by the merchant app 30, the payment app 20, and the payment server 100. First, the merchant app 30 is activated based on user operation (S100). When the user performs a payment operation (an operation to make an electronic payment using the payment app 20) (S102), the merchant app 30 sends a request (payment request) including the app ID (S104).

[0055] The request may include information to identify the user (user identification information). Information to identify the user may be sent along with the request. The app ID may also be information that identifies both the merchant and the user. In the following explanation, it will be assumed that the app ID makes it possible to identify both the merchant and the user. In addition to the above, the request may contain any other information that identifies both the user and the merchant.

[0056] Next, the payment server 100 generates and stores a one-time code in response to receiving a request (S106). Figure 13 is a diagram illustrating the generation and storage of a one-time code. When the rewards processing unit 150 obtains an app ID, it checks whether the linking information corresponding to the app ID has already been linked. If the linking information has already been linked, the rewards processing unit 150 generates a one-time code and links the generated one-time code to the app ID in the app information 180. If the linking is not yet complete, the payment app 20 or the merchant app 30 may display information on the display unit prompting the linking.

[0057] Next, the payment server 100 sends the generated one-time code to the merchant app 30 (S108). In this way, the rewards processing unit 150 sends a one-time passcode to the merchant app 30 for use by the merchant app 30, provided that it has received the request. The rewards processing unit 150 stores the app ID, the one-time passcode, and the account ID that can be identified from the app ID in a storage unit, associating them with each other.

[0058] Next, the merchant app 30 generates code information based on the transmitted one-time code and displays the generated code information on the display unit (S110). The payment server 100 obtains payment information (including payment amount, information to identify the merchant, and information to identify the user) from the first store terminal device 50 (S112) and executes electronic payment based on the payment information (S114). Next, the payment server 100 grants benefits to the user according to the electronic payment (S116).

[0059] As described above, the payment server 100 grants the benefit to the user and sends a payment completion notification to the merchant app 30 (S118). Next, the merchant app 30 displays the payment completion screen on its display unit (S120). Some of the above processes may be executed by the payment app 20. For example, the processes in S108 and S110, or the processes in S118 and S120, may be executed by the payment app 20.

[0060] As described above, when a user makes an electronic payment using the payment function of the electronic payment service via the merchant app 30, the payment server 100 can grant the user a reward. This improves usability.

[0061] [flowchart] Figure 14 is a flowchart showing an example of the process by which the payment server 100 determines whether to grant the first or second benefit. This process details the process (S112, S114, S116 in Figure 12) when the payment server 100 acquires payment information and makes a payment based on the acquired payment information.

[0062] First, the payment server 100 determines whether the electronic payment related to the payment information was made via the merchant app 30 (S200). If the electronic payment related to the payment information was not made via the merchant app 30, the process proceeds to S204.

[0063] If the electronic payment related to the payment information is an electronic payment made via the merchant app 30, the payment server 100 determines whether the user of the electronic payment meets the conditions set by the merchant (S202). If the user of the electronic payment does not meet the conditions set by the merchant, the payment server 100 grants the second benefit to the user (S204).

[0064] If a user of electronic payment meets the conditions set by the merchant, the payment server 100 grants the first benefit (S206). This completes the processing of one routine in this flowchart.

[0065] As described above, the payment server 100 can improve usability by determining whether the transaction is made via the merchant app 30 and whether the user meets the conditions, and by providing the user with benefits according to the result of the determination.

[0066] [Notification to users] The payment server 100 sends a notification to the user's electronic payment service payment app 20 indicating that the user's attributes match the conditions specified by the merchant, and that the user will be granted a benefit by making an electronic payment using the merchant app 30. The notification may also be sent by other methods such as email or SMS (Short Message Service) instead of the payment app 20. For example, the notification may be a notification that the first benefit will be granted, that a benefit will be granted when making an electronic payment via the merchant app 30, or that the degree of benefit granted will be greater when making an electronic payment at the target merchant via the merchant app 30 than when making an electronic payment at the target merchant without using the merchant app 30.

[0067] The payment server 100, for example, refers to user information 172 to extract users who meet the conditions. The payment server 100 then sends push notifications to the payment apps 20 of the extracted users, or displays notifications on the interface screen shown in Figure 15.

[0068] Figure 15 shows an interface screen including notifications. The interface screen is the home screen of the payment app 20, and an area AR is provided at the bottom of the home screen. The area AR includes notifications. When a user opens the home screen, they can recognize that they will receive a reward if they use the merchant app 30 to make an electronic payment at a target merchant. The home screen may include, for example, a button to install the merchant app 30, or a button to install the merchant app 30 may be included on the screen after tapping the area AR.

[0069] As described above, the payment server 100 can notify users who meet the conditions that more benefits will be awarded to them. Furthermore, merchants can increase their chances of acquiring new loyal customers through these notifications.

[0070] Furthermore, the recipients of the notification may be users who meet the conditions but whose merchant app 30 and payment app 20 are not yet linked, or users who meet the conditions and whose merchant app 30 and payment app 20 are already linked. The recipients of the notification may also be users who meet the conditions.

[0071] Furthermore, notifications may be made on the payment completion screen displayed after an electronic payment using the electronic payment service has been made at a merchant using the merchant app 30. On this screen, information such as recommendations for installing and using the merchant app 30, and information indicating that the first benefit will be granted, may be displayed.

[0072] The above example describes a case where a store scan is performed, but the processing of this embodiment may also be performed in the case of a user scan. In this case, the user terminal device 10 (payment app 20 or merchant app 30) sends a request for electronic payment using the payment function of the electronic payment service via the merchant app 30 of the merchant of the electronic payment service, and the payment server 100 may grant the benefit to the user when it receives this request. For example, if the camera of the user terminal device 10 is activated via (operated by) the merchant app 30 and the user captures the merchant's QR code or the like to obtain the merchant's identification information, the user terminal device 10 (payment app 20 or merchant app 30) sends to the payment server 100 (or together with the second payment information) information indicating that the merchant's identification information has been obtained via the merchant app 30, including this information in the second payment information (such as the payment amount). In this case, the payment server 100 grants the user the benefit related to the merchant.

[0073] As described above, the payment server 100 can improve usability by, upon receiving an electronic payment request using the payment function of the electronic payment service via the merchant app of a merchant of the electronic payment service, executing a process to grant the electronic payment service benefits to the user who made the request, based on the attributes of the user who made the request managed in the electronic payment service and the conditions for granting benefits corresponding to the merchant app 30.

[0074] Although embodiments for carrying out the present invention have been described above using examples, the present invention is not limited in any way to these embodiments, and various modifications and substitutions can be made without departing from the spirit of the present invention. [Explanation of Symbols]

[0075] 10. User terminal device 20 Payment Apps 30 Merchant Apps 100 Payment Servers 120 Content Provision Department 130 Payment Processing Unit 140 Information Management Department 150 Special Offer Processing 178 Bonus Information 180 App Information

Claims

1. An acquisition unit that acquires requests for electronic payments using the payment function of the electronic payment service via the merchant app of a merchant that is a member of the electronic payment service, Upon receiving the aforementioned request, a processing unit executes a process to grant the benefits of the electronic payment service to the user who made the request, based on the attributes of the user who made the request, which are managed in the electronic payment service, and the conditions for granting benefits corresponding to the merchant app. An information processing device equipped with the following features.

2. The acquisition unit acquires the request which includes user identification information that can identify the user and merchant identification information that can identify the merchant of the merchant app. Upon receiving the request, the processing unit performs a process to associate the benefit with identification information for identifying the user who made the request, which is managed in the electronic payment service. The information processing apparatus according to claim 1.

3. The aforementioned benefit is the points of the aforementioned electronic payment service. The information processing apparatus according to claim 1.

4. The aforementioned benefits are benefits set by the aforementioned merchant, or benefits for which the aforementioned merchant bears the cost. The information processing apparatus according to any one of claims 1 to 3.

5. The aforementioned conditions are those specified by the aforementioned member store. The information processing apparatus according to any one of claims 1 to 3.

6. The aforementioned condition is that the age is as specified by the affiliated store. The information processing apparatus according to any one of claims 1 to 3.

7. The user's attributes are those identified from the identity verification information performed and managed within the electronic payment service. The information processing apparatus according to any one of claims 1 to 3.

8. The aforementioned attribute is age. The information processing apparatus according to claim 7.

9. The processing unit notifies the user's electronic payment service payment app that the user's attributes match the conditions and that the user will be granted the benefit by making an electronic payment using the merchant app of the electronic payment service. The information processing apparatus according to any one of claims 1 to 3.

10. The acquisition unit acquires the request which includes user identification information that can identify the user and merchant identification information that can identify the merchant of the merchant app. If the user's age, which is associated with the user identification information in the identity verification information managed in the aforementioned electronic payment service, meets the age requirements specified by the merchant in the merchant identification information, the process of associating a higher degree of benefit than in case (1) or (2) below with the user identification information of the user who made the request is executed. (1) The merchant made an electronic payment using the payment app of the electronic payment service without going through the merchant app mentioned above. (2) The user used the electronic payment service via the merchant app, but the user's age did not meet the specified age requirement. The information processing apparatus according to claim 1.

11. Computers The merchant app of the electronic payment service obtains an electronic payment request using the payment function of the said electronic payment service. Upon receiving the aforementioned request, the electronic payment service executes a process to grant the electronic payment service's benefits to the user who made the request, based on the user's attributes managed in the electronic payment service and the conditions for granting benefits corresponding to the merchant app. Information processing methods.

12. On the computer, The merchant app of the electronic payment service obtains an electronic payment request using the payment function of the said electronic payment service. Upon receiving the aforementioned request, the electronic payment service executes a process to grant the electronic payment service's benefits to the user who made the request, based on the user's attributes managed within the electronic payment service and the conditions for granting benefits corresponding to the merchant app. program.

Images