Information processing device, information processing method, and program

Abstract

To improve engagement with users. An acquisition unit that acquires payment information using a payment card from a store terminal at a store; An information processing device comprising: a processing unit that, in response to acquiring the payment information, instructs a user terminal device on which a payment app for an electronic payment service is installed to output a payment sound set in the electronic payment service, causing the user terminal device to output the payment sound.

Description

[Technical Field]

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

[0002] Conventionally, a provision device has been disclosed that, when payment information including user identification information, store identification information, and payment amount is received, executes payment in accordance with the payment information, and provides sound information indicating a sound that is output in response to the payment, the sound being in accordance with the location of the user using the user terminal based on the payment information (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2023-126624 Summary of the Invention [Problem to be solved by the invention]

[0004] In conventional technologies, there is a lack of consideration given to improving user engagement.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide an information processing device, an information processing method, and a program that can improve engagement with users. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing device that includes an acquisition unit that acquires payment information using a payment card from a store terminal at a store, and a processing unit that, in response to acquiring the payment information, instructs a user terminal device on which a payment app for an electronic payment service is installed to output a payment sound set in the electronic payment service, causing the user terminal device to output the payment sound. [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 engagement with users. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 10 is a diagram for explaining a comparative example. [Figure 8] FIG. 2 is a diagram for explaining the processing of the present embodiment. [Figure 9] 10A and 10B are diagrams for explaining output of a payment sound in response to online and offline use of a payment card. [Figure 10] FIG. 10 is a sequence diagram showing an example of a flow of processing executed by the electronic payment system. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, with reference to the drawings, embodiments of an information processing device, an information processing method, and a program according to the present invention will be described. Various devices, such as the "server" mentioned below, that provide services to users or perform internal analysis may be realized by a group of distributed devices, and each device may be operated by a different business. Furthermore, the owner of the device hardware (the cloud server provider) and the business that actually operates the device may also be different. An application program and a payment server work together to provide an electronic payment service. In the following description, the application program is referred to as a payment app. An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store is, for example, a physical store (real-world store) that exists in real space, but may also include a virtual store for e-commerce. A virtual store may also include a store provided by an entity different from the operator of the electronic payment service. In such a case, when paying for purchases at the virtual store, the user is controlled to transition to the interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and when a purchase is made at a store, processing such as payment is primarily conducted between the user and the affiliated store. Alternatively, processing such as payment may be conducted between the user and the store.

[0010] [Electronic payment service] FIG. 1 shows an example of the configuration of an electronic payment system in which an electronic payment service is realized. The electronic payment service is realized mainly by a payment server 100. The electronic payment system that realizes the electronic payment service includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, the payment server 100, a card server 200, and an OS (Operating System) server 300. These devices communicate, for example, via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc.

[0011] Some or all of the functional components included in the electronic payment system may be distributed across multiple devices in any form, or may be integrated into any device. For example, some or all of the functional components of the payment server 100 may be included in another device.

[0012] [User terminal device] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or 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, a voice output function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a speaker, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, the CPU executes an OS 12 to perform various processes.

[0013] In the user terminal device 10, a processor such as a CPU executes the payment app 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment app 20 is installed in the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc. A mini app 30 may also run in the user terminal device 10.

[0014] [First store terminal device] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called Point of Sale (POS) 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. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone). The first store terminal device 50 may communicate with a payment card (e.g., a credit card or debit card) to acquire information about the payment card and perform a payment using the payment card.

[0015] [Second store terminal device] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading the code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0016] [Payment server] The payment server 100 realizes electronic payment based on payment 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 an affiliated store server, in which case payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0017] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2.

[0018] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in the payment server 100 (described below). The payment application 20 sends 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 below) using the affiliated store ID and store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen displaying the affiliated store name and store name (S5). The user terminal device 10 then generates second payment information including at least the payment amount and transmits 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 transmits a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 20 displays the payment completion screen and outputs a payment sound to the user terminal device 10 (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0019] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (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, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). The payment server 100 then sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen and causes the user terminal device 10 to output a payment sound (S19).

[0020] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0021] [Payment server functional configuration] 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a content providing unit 120, a payment processing unit 130, an information management unit 140, a processing unit 150, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, 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 an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), a GPU (Graphics Processing Unit), or an SOC (System On Chip), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device having a non-transitory storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device. Information management unit 140 is an example of an "acquisition unit."

[0022] The storage unit 170 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, content information 174, affiliated store / shop information 176, etc.

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

[0024] The content providing unit 120 has, for example, a web server function, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10 or the second store terminal device 70. The content providing unit 120 reads out 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 content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100. The above content may be generated by the payment application 20. In this case, the content providing unit 120 provides the payment application 20 with information necessary for generating the content.

[0025] The payment processing unit 130 performs payment processing based on the 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.

[0026] [User information] FIG. 5 is a diagram showing 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, a user URL, account ID, telephone number, and password, as well as associated information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit card payment settings, credit card limit, credit card payment amount, available credit card payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for remittance processing between users. Registration of a telephone number and password is required when registering for an electronic payment service. The account ID is issued to the user by the payment server 100, and the user ID can be set by the user (or does not have to be set). Similarly, the email address, name, address, and date of birth can be set by the user (or do not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0027] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated bank's ATM (Automatic Teller Machine) or from a registered bank account. The credit payment setting indicates whether the settings for electronic credit payment have been completed and is set to either "Completed" or "Not Completed." The credit payment limit is the monthly credit payment limit. The credit payment amount is the amount of credit payment already used in the current month. The available credit payment amount is the amount of credit payment available in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the figure shows only one credit payment limit, in reality, there may also be daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be discussed later. The payment method setting indicates whether the user will currently make electronic payments using the charge balance or by credit payment. The bank account and credit card number are information on the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that indicates the breakdown of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.). The account ID in the user information 172 may be associated with a one-time code issued to the user (for example, the most recently issued one-time code).

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

[0029] [Electronic Payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 references the user information 172 to acquire the "payment method setting" of the user. 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 managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not used as electronic money itself, for example. Instead, the amount corresponding to the item value of the sales proceeds is transferred to a bank account in accordance with a cycle agreed upon between the affiliated store and the electronic payment service. The affiliated store may receive the sales proceeds as electronic money. In this case, the payment server 100 manages the account (wallet) corresponding to the affiliated store ID, the account's electronic money balance, and the sales proceeds history for each payment method in association with each other.

[0030] The payment processing unit 130 performs electronic payments for users whose "setting information" is set to "credit payment" as follows. Credit payment is a payment method in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service, and allows electronic payments within the credit payment limit and independent of the charge balance. To receive the credit payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The payment processing unit 130 adds the payment amount to the credit payment amount in the user information 172 and subtracts the payment amount from the available credit payment amount. If the payment amount exceeds the available credit payment amount, an error notification is returned to the payment app. The amount used for credit payment is settled, for example, for one month in a lump sum on the payment date of the following month, for example, by debit from a bank account. This processing is performed by the operator of the credit card company.

[0031] The information management unit 140 acquires information provided by other server devices and terminal devices. The information management unit 140 manages user information 172 and affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, deletes, etc., the user information 172 and affiliated store / store information 176.

[0032] The processing unit 150 causes the user terminal device 10 to output a payment sound in response to a payment using a payment card, as will be described later.

[0033] [Card Server] The card server 200 acquires payment information. The payment information is, for example, authorization information regarding approval of a transaction using the payment card, which is sent in response to a user's use of the payment card at the card's affiliated store. The card server 200 acquires sales information indicating that sales for use of the payment card have been confirmed. The card server 200 provides this information or information obtained by processing this information to the payment server 100. The authorization information may include, for example, terminal identification information of the affiliated store (first store terminal device 50), the affiliated store name, store identification information, and affiliated store code. In addition to the above, the authorization information may also include information indicating whether the affiliated store is an offline affiliated store or an online affiliated store.

[0034] [OS Server] The OS server 300 cooperates with the OS 12, the payment application 20, or the payment server 100 to provide services to users. For example, the OS server 300 cooperates with the OS 12 based on instructions from the payment server 100 to send push notifications to the user terminal device 10 or output sounds.

[0035] [overview] The payment server 100 acquires payment information using a payment card from a first store terminal device 50 (store terminal of the store). In response to acquiring the payment information, the payment server 100 instructs the user terminal device 10, on which the payment app 20 of the electronic payment service is installed, to output a payment sound set in the electronic payment service, causing the user terminal device 10 to output the payment sound. The payment server 100 causes the OS 12 of the user terminal device 10 to output the payment sound from the user terminal device 10.

[0036] When electronic payment is made using the payment app 20, the payment server 100 causes the payment app 20 to output a payment sound to the user terminal device 10. The payment sound output in response to the payment information is the same as the payment sound output by the payment app 20 and is a sound indicating that the payment has been completed. The payment sound output in response to the payment information does not have to be the same as the payment sound output by the payment app 20, and may be a different sound. For example, it may be a sound that evokes an electronic payment service.

[0037] Payment information is information transmitted when a physical payment card or an electronic payment card registered in the user terminal device 10 is used. Payment information is different from information transmitted when a payment method is set to credit card payment and payment is made using the payment app 20. Registered in the user terminal device 10 means, for example, that the card is registered in a wallet app and is available for use. A wallet app is an app that can centrally manage credit cards, debit cards, etc. in the user terminal device 10. Payment information is information for authorization to confirm the validity of a payment card.

[0038] [Comparative Example] FIG. 7 is a diagram illustrating a comparative example. In the comparative example, when a payment card is used at a store, the user terminal device 10 sends a push notification. When the user performs an operation such as a tap on the display of the push notification, the payment app 20 starts up, causing the user terminal device 10 to display a payment notification screen showing details of the payment and output a payment sound. In the comparative example, the payment sound is output when the user performs an operation on the push notification.

[0039] [Present embodiment] 8 is a diagram for explaining the processing of this embodiment. When a payment card is used at a store, the user terminal device 10 sends a push notification and outputs a payment sound. When the user performs an operation such as a tap on the display of the push notification, the payment app 20 starts up and causes the user terminal device 10 to display a payment notification screen showing payment details.

[0040] In this embodiment, as described above, the payment sound is output by the user terminal device 10 without relying on user operation, which can improve engagement with the user. For example, the same payment sound as when the payment app 20 is used is output when a payment card is used, so that consistent notifications can be provided when using electronic payment services.

[0041] 9 is a diagram for explaining the output of a payment sound for online use of a payment card and offline use of a payment card. The payment server 100 may control the output of the payment sound as shown in FIG.

[0042] When the payment server 100 acquires payment information from the first store terminal device 50 (store terminal) of the physical store, the payment server 100 causes the user terminal device 10 to output a payment sound without relying on a user operation. For example, the payment server 100 causes the user terminal device 10 to output a payment sound without relying on a tap operation.

[0043] When the payment server 100 acquires payment information from a store terminal (e.g., a server device) of an online store, the payment server 100 does not cause the user terminal device 10 to output a payment sound without a user operation. For example, the payment server 100 causes the user terminal device 10 to output a payment sound by a tap operation.

[0044] In addition, even when making a payment using payment application 20, a payment sound may be output when used offline, and a payment sound may be output when used online.

[0045] As described above, the payment server 100 can improve engagement with the user by causing the user terminal device 10 to output a payment sound when a payment card is used offline. The payment server 100 does not cause the user terminal device 10 to output a payment sound when a payment card is used online. This prevents unnecessary payment sounds from being output. For example, if a user makes an online payment in a location where they do not want sound to be emitted, the payment sound is not output, improving user convenience.

[0046] [Sequence diagram] 10 is a sequence diagram showing an example of the flow of processing executed by the electronic payment system. First, when a payment is made using a payment card, the offline first store terminal device 50 sends an authorization request to the card server 200 (S100). The card server 200 performs authorization based on the authorization information included in the authorization request (S102). Authorization is a process for confirming the validity of the payment card based on the authorization information.

[0047] The card server 200 transmits the authorization result to the payment server 100 (S104), and then transmits it to the first store terminal device 50 (S106). The payment server 100 may obtain authorization information from the card server 200 instead of (or in addition to) the authorization result.

[0048] When the payment server 100 acquires the authorization result, it makes a determination regarding the payment sound (S108). The payment server 100 refers to information included in the authorization result (or authorization information) indicating whether the payment is for an online store or an offline store. If the store is an offline store, the payment server 100 sends notification information to the OS server 300 without setting the payment sound flag. If the store is an online store, the payment server 100 sends notification information with the payment sound flag set to the OS server 300 (S112).

[0049] The OS server 300 identifies the user terminal device 10 to which the notification information is to be sent (S114) and sends the notification information to the identified user terminal device 10 (S116). Next, the OS server 300 causes the user terminal device 10 to output information in an output format according to the notification information (S118). The payment app 20 and the payment server 100 share the device token of the user terminal device 10. For example, the payment server 100 associates and manages device tokens with identification information for identifying a user, such as an account ID or a credit card number. Furthermore, the OS 12 of the user terminal device 10 previously provides the device token of the user terminal device 10 to the OS server 300. The payment server 100 identifies a device token corresponding to the identification information for identifying a user, which is included in the authorization information, and sends an instruction to the OS server 300 to send a push notification to the user terminal device 10 of the identified device token. The OS server 300 can identify the user terminal device 10 to which the push notification is to be sent based on the device token of the user terminal device 10 and send the push notification to the identified user terminal device 10.

[0050] As described above, the payment server 100 can cause the user terminal device 10 to output a payment sound when a payment card is used, thereby improving engagement with the user.

[0051] When a payment card (e.g., a credit card) is used, the payment server 100 outputs a payment sound for the electronic payment service to the user terminal device 10, thereby informing the user that the service is related to the electronic payment service and promoting the use of the electronic payment service. Furthermore, by outputting the payment sound, both the user and the store can easily recognize that a payment has been made, and the electronic payment service can also be promoted to other users. This can improve brand awareness. In this way, the payment sound can be provided for electronic payments using the payment app 20 and for electronic payments using an electronic payment card, thereby improving engagement between the electronic payment service and the user.

[0052] [About status] The above embodiment is directed to authorization information. For example, when sales information is notified without authorization information (in the case of a stand-alone sale), sound output may be suppressed. Also, for example, when authorization information (a predetermined type of authorization information) requesting confirmation of a predetermined amount of credit limit is notified, the payment server 100 may output a sound, and thereafter suppress sound output for notifications of sales information within the credit limit (a stand-alone sale). The payment server 100 controls sound output based on the type of notification for the payment notified as described above (authorization information or stand-alone sale). The type of notification for the payment is determined based on information such as a flag included in the notification.

[0053] Instead of (or in addition to) the above, the above sound may be output to the user terminal device 10 along with a push notification for a cancellation of authorization, a notification of sales confirmation information that confirms sales, a refund notification, or a payment failure.

[0054] [About card types] Card types include normal cards (primer cards, secondary cards, regular cards, gold cards) as well as family cards. If a family card is not linked to the family's payment app 20 (if not registered in the payment app 20), a push notification is sent to the user terminal device 10 of the normal card user. At that time, the user terminal device 10 of the normal card user does not need to output a sound corresponding to the use.

[0055] If a family card is linked to a family member's payment app 20, a push notification (and no sound) is not sent to the user terminal device 10 of the user of the normal card, but a push notification is sent to the user terminal device 10 of the family card user. At that time, a sound corresponding to the use is output to the user terminal device 10 of the family card user. The information on whether or not the above-mentioned linkage is present is managed in the storage unit 170 in association with identification information such as the user's account ID.

[0056] [Regarding notifications after the first one] If the payment server 100 determines, based on information included in the payment information (e.g., authorization information), that the payment information is the second or subsequent payment information, it may not output a payment sound to the user terminal device 10. If order information is transmitted twice, the payment server 100 may not output a sound to the user terminal device 10 in response to the second notification. The payment server 100 may determine whether the notification is the second notification based, for example, on a payment ID included in the authorization information or information indicating the second processing, and may suppress sound output if the notification is the second notification. For example, authorization information for a 1,000 yen payment may be transmitted the first time, and the user or affiliated store may change the payment amount to 500 yen, resulting in the second notification of authorization information. In this case, the payment server 100 may output a payment sound in response to the first notification but not output a payment sound in response to the second notification. The user can recognize from the first notification that a credit card was used for the payment, thereby suppressing unnecessary second notifications. Note that sound output is also suppressed from the third notification onwards.

[0057] [User settings] If the user has set the payment server 100 not to output the payment sound, the payment server 100 will not cause the user terminal device 10 to output the payment sound even if payment information is acquired. The user can set the sound output to on or off. The payment server 100 may or may not output the sound according to the user's setting. The user can set the sound output to on or off by operating the payment app 20. The payment server 100 controls the sound output based on the above setting.

[0058] [About time settings] A time for which sound is output or a time for which sound is not output may be set. When the time at which payment information is acquired is a preset time, the payment server 100 instructs the user terminal device 10 to output a payment sound set in the electronic payment service, causing the user terminal device 10 to output the payment sound. If a payment is made with a payment card (e.g., a credit card) during a time when sound is output, the payment server 100 causes the user terminal device 10 to output a sound, and if a payment is made with a payment card during a time when sound is not output, the payment server 100 does not cause the user terminal device 10 to output a sound. For example, sound output is suppressed during times such as late at night or early in the morning. This improves user convenience.

[0059] The time for which the sound is output or the time for which the sound is not output may be specified by the user. The user can set the time by operating the payment application 20. The payment server 100 controls the sound output based on the setting. This further improves user convenience.

[0060] [About location settings] Locations where sound is to be output or locations where sound is not to be output may be set. The payment server 100 can identify the facility where the user is located based on the location information of the user terminal device 10. When the payment server 100 acquires the payment information, if the user is located in a predetermined facility or not located in a predetermined facility, the payment server 100 instructs the user terminal device 10 to output the payment sound set in the electronic payment service, causing the user terminal device 10 to output the payment sound.

[0061] The payment server 100 causes the user terminal device 10 to output sound when a payment card payment is made in a location where sound is output, and does not cause the user terminal device 10 to output sound when a credit card payment is made in a location where sound is not output. For example, sound output is suppressed in locations such as home, work, and public transportation (stations and airports). For example, sound is output in locations such as stores. This improves user convenience. The location where the user is present is identified by the payment server 100 based on location information provided by the user terminal device 10 (payment app 20). The payment server 100 identifies the type of location where the user is present (such as a store or home) based on the user's location information and map information. The home, work, etc. may be preset locations, or may be estimated based on the user's location information history. This further improves user convenience.

[0062] The user may specify the location where the sound is to be output or where the sound is not to be output. The user can set the location by operating the payment application 20. The payment server 100 controls the sound output based on the setting. This further improves user convenience.

[0063] [About the audio output] When the payment server 100 acquires the authorization information, it may cause the user terminal device 10 to output a preset sound in addition to (or instead of) the payment sound. Upon acquiring the payment information, the payment server 10 instructs the user terminal device 10 to output a setting sound set in the electronic payment service along with the payment sound, causing the user terminal device 10 to output the payment sound and the setting sound. The setting sound is the sound of a campaign for the electronic payment service or information about a benefit of the electronic payment service. The preset sound (setting sound) is, for example, information indicating that a benefit has been granted or a sound indicating that the user can participate in a lottery. For example, it is a sound such as "You have acquired a coupon" or "Scratch chance."

[0064] For example, when the payment server 100 acquires authorization information, it outputs an instruction to the OS server 300 to output a setup sound. The user terminal device 10 outputs the setup sound from the speaker in addition to the payment sound based on the instruction to output the setup sound acquired from the OS server 300. The setup sound is stored in the memory unit of the user terminal device 10. It may be provided to the OS server 300 or the payment server 100.

[0065] In the above process, the payment server 100 may determine whether to output a setup sound depending on the user's attributes and the content of the payment. For example, the payment server 100 outputs the setup sound when a predetermined condition is met. The predetermined condition may be, for example, a condition corresponding to the user's payment history (e.g., a predetermined level or more, the use of a payment card or an electronic payment service), electronic identity verification, or credit card payment. The predetermined condition may be, for example, the payment amount being a predetermined amount or more, or a predetermined number of payments being made within a predetermined period. For example, when authorization information is acquired, the payment server 100 outputs the setup sound to the user terminal device 10 if the content of the authorization information, the user's attributes, or the like meets the conditions. This can further improve user engagement with the electronic payment service.

[0066] According to the other embodiment described above, in response to obtaining payment information using a payment card from a store terminal at a store, the payment server 100 instructs a user terminal device on which a payment app for an electronic payment service is installed to output a payment sound set in the electronic payment service, thereby causing the user terminal device to output the payment sound, thereby improving engagement with the user.

[0067] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0068] 10 User terminal device 20. Payment App 100 Payment Server 120 Contents Provider 130 Payment processing unit 140 Information Management Department 150 Processing section

Claims

1. an acquisition unit that acquires payment information using a payment card from a store terminal of the store; a processing unit that, in response to acquiring the payment information, instructs a user terminal device on which a payment app for an electronic payment service is installed to output a payment sound set in the electronic payment service, causing the user terminal device to output the payment sound; When electronic payment is made using the payment app, the payment app outputs the payment sound to the user terminal device, The payment sound output in accordance with the payment information is the same as the payment sound output by the payment app, and is a sound indicating completion of payment. Information processing device.

2. the processing unit causes an operation system of the user terminal device to output the payment sound from the user terminal device. The information processing device according to claim 1 .

3. The payment information is information transmitted by using a physical payment card or an electronic payment card registered in a user terminal device.

3. The information processing device according to claim 1.

4. When the acquisition unit acquires the payment information from a store terminal of a physical store, the processing unit causes the user terminal device to output the payment sound without relying on an operation by a user, When the acquisition unit acquires the payment information from a store terminal of an online store, the processing unit does not cause the user terminal device to output the payment sound without an operation by the user.

3. The information processing device according to claim 1.

5. The payment information is information for authorization to confirm the validity of the payment card.

3. The information processing device according to claim 1.

6. When the processing unit determines based on information included in the payment information that the payment information is payment information for a second or subsequent time, the processing unit does not cause the user terminal device to output the payment sound.

3. The information processing device according to claim 1.

7. When the user has set the payment sound not to be output, the processing unit does not cause the user terminal device to output the payment sound even when the payment information is acquired.

3. The information processing device according to claim 1.

8. When the time when the payment information is acquired is a preset time, the processing unit instructs the user terminal device to output a payment sound set in the electronic payment service, causing the user terminal device to output the payment sound.

3. The information processing device according to claim 1.

9. The processing unit The facility where the user is located can be identified based on the location information of the user terminal device, when the payment information is acquired, if the user is present at a predetermined facility or if the user is not present at a predetermined facility, an instruction is given to the user terminal device to output a payment sound set in the electronic payment service, causing the user terminal device to output the payment sound; 3. The information processing device according to claim 1.

10. the processing unit, in response to acquiring the payment information, instructs the user terminal device to output a setting sound set in the electronic payment service together with the payment sound, causing the user terminal device to output the setting sound; The setting sound is a campaign sound for the electronic payment service or information about a benefit of the electronic payment service.

3. The information processing device according to claim 1.

11. The computer Obtain payment information using a payment card from the store's terminal, In response to acquiring the payment information, instruct a user terminal device on which a payment app for an electronic payment service is installed to output a payment sound set in the electronic payment service, causing the user terminal device to output the payment sound; When electronic payment is made using the payment app, the payment app outputs the payment sound to the user terminal device, The payment sound output in accordance with the payment information is the same as the payment sound output by the payment app, and is a sound indicating completion of payment. Information processing methods.

12. On the computer, A process of acquiring payment information using a payment card from a store terminal at a store; a process of instructing a user terminal device on which a payment app of an electronic payment service is installed to output a payment sound set in the electronic payment service in response to acquiring the payment information, causing the user terminal device to output the payment sound; When electronic payment is made using the payment app, the payment app outputs the payment sound to the user terminal device, The payment sound output in accordance with the payment information is the same as the payment sound output by the payment app, and is a sound indicating completion of payment. program.

Images