JP7492942B2 - PROGRAM, INFORMATION PROCESSING METHOD, AND INFORMATION PROCESSING APPARATUS - Google Patents

Description

This disclosure relates to a program, an information processing method, an information processing device, etc.

Recently, services that allow payments (settlement) using electronic currency and the like through applications that can be executed on terminals such as smartphones are becoming more widespread. For example, Patent Literature 1 discloses a technology for settling the purchase amount of a product.

JP 2002-176671 A

According to a first aspect of the present invention, a program executed by an information processing device communicating with a first information processing device is executed by the information processing device in such a way that restrictions are set by a user of the first information processing device, and processing related to the first payment is performed by a control unit of the information processing device based on at least a portion of the first electronic currency transferred from the first information processing device and at least a portion of the second electronic currency associated with the user of the information processing device.
According to a second aspect of the present invention, an information processing method of an information processing device communicating with a first information processing device includes a restriction set by a user of the first information processing device, and processing related to a first payment being performed by a control unit of the information processing device based on at least a portion of a first electronic currency transferred from the first information processing device and at least a portion of a second electronic currency associated with the user of the information processing device.
According to a third aspect of the present invention, an information processing device communicating with a first information processing device has a control unit that performs processing related to a first payment based on at least a portion of the first electronic currency transferred from the first information processing device and at least a portion of the second electronic currency associated with the user of the information processing device, on a limit set by a user of the first information processing device.According to a fourth aspect of the present invention, an information processing device communicating with a first information processing device has a processor that reads a program stored in a memory and executes processing based on the program, and the processor executes processing related to a first payment based on at least a portion of the first electronic currency transferred from the first information processing device and at least a portion of the second electronic currency associated with the user of the information processing device, on a limit set by a user of the first information processing device.
According to a fifth aspect of the present invention, a program executed by a server communicating with a first information processing device and a second information processing device includes a control unit of the server performing a process of associating a first electronic currency transferred from the first information processing device to the second information processing device, the first electronic currency having a restriction set by the user of the first information processing device, with the user of the second information processing device, and a process of associating the second electronic currency with the user of the second information processing device, and a process related to a first payment based on at least a portion of the first electronic currency and at least a portion of the second electronic currency based on information transmitted from the second information processing device.

FIG. 1 is a diagram showing an example of a system configuration of a communication system according to an embodiment. FIG. 1 is a diagram showing an example of a system configuration of a store POS system according to an embodiment. FIG. 4 is a diagram showing an example of functions realized by a control unit of the server according to the first embodiment. FIG. 4 is a diagram showing an example of information stored in a storage unit of the server according to the first embodiment. FIG. 4 is a diagram showing an example of account registration data according to the first embodiment. FIG. 4 is a diagram showing an example of an account management database according to the first embodiment. FIG. 4 is a diagram showing an example of functions realized by a control unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of information stored in a storage unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a screen displayed on a display unit of the terminal according to the first embodiment. 5 is a flowchart showing an example of a flow of a process executed by each device according to the first embodiment. 5 is a flowchart showing an example of a flow of a process executed by each device according to the first embodiment. FIG. 11 is a diagram showing an example of an account management database according to a first modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a first modified example. FIG. 11 is a diagram showing an example of an account management database according to a first modified example. 10 is a flowchart showing an example of a flow of processes executed by each device according to the second embodiment. FIG. 11 is a diagram showing an example of information stored in a storage unit of a server according to a second modified example. FIG. 13 is a diagram showing an example of payment history management data according to a second modified example. FIG. 11 is a diagram showing an example of an account management database according to a second modified example. FIG. 11 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a second modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third embodiment. 13 is a flowchart showing an example of a flow of processes executed by each device according to the third embodiment. 13 is a flowchart showing an example of a flow of processes executed by each device according to the third embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third modified example. 13 is a flowchart showing an example of a flow of processes executed by each device according to a third modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a third modified example. 13 is a flowchart showing an example of a flow of processes executed by each device according to a third modified example. FIG. 13 is a diagram showing an example of an account management database according to the fourth embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fourth embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fourth embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fourth modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fourth modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fourth modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fourth modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifth embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifth embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifth modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a sixth embodiment. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a sixth modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a sixth modified example. FIG. 13 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a sixth modified example. FIG. 23 is a diagram showing an example of an account management database according to the seventh embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to the seventh embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to the seventh embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to the seventh embodiment. 23 is a flowchart showing an example of the flow of a process executed by each device according to the seventh embodiment. 23 is a flowchart showing an example of the flow of a process executed by each device according to the seventh embodiment. FIG. 23 is a diagram showing an example of an account management database according to a seventh modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a seventh modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a seventh modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a seventh modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a seventh modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to the eighth embodiment. 23 is a flowchart showing an example of the flow of processes executed by each device according to the eighth embodiment. 23 is a flowchart showing an example of the flow of processes executed by each device according to the eighth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eighth modified example. 13 is a flowchart showing an example of a flow of processes executed by each device according to an eighth modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eighth modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eighth modified example. 13 is a flowchart showing an example of a flow of processes executed by each device according to an eighth modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eighth modified example. FIG. 23 is a diagram showing an example of an account management database according to the ninth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a ninth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a ninth modified example. FIG. 23 is a diagram showing an example of a processing method in a used balance selection process according to a ninth modified example. FIG. 23 is a diagram showing an example of a processing method in a used balance priority order setting process according to a ninth modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a tenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a tenth modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eleventh embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eleventh embodiment. 23 is a flowchart showing an example of the flow of processes executed by each device according to the eleventh embodiment; FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to an eleventh modified example 23 is a flowchart showing an example of the flow of processes executed by each device according to an eleventh modified example. FIG. 23 is a diagram showing an example of an account management database according to the twelfth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a twelfth embodiment. 23 is a flowchart showing an example of the flow of processes executed by each device according to the twelfth embodiment; FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a twelfth modified example. FIG. 23 is a diagram showing an example of account management data according to a twelfth modified example. FIG. 23 is a diagram showing an example of account management data according to a twelfth modified example. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a thirteenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a thirteenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a thirteenth embodiment FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a thirteenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a thirteenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a thirteenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a thirteenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifteenth embodiment. FIG. 23 is a diagram showing an example of a screen displayed on a display unit of a terminal according to a fifteenth embodiment. 23 is a flowchart showing an example of the flow of processes executed by each device according to the fifteenth embodiment;

<Compliance with legal matters>
It should be noted that the disclosures described herein are subject to compliance with the laws of the country of implementation, such as communications secrecy, as necessary for the implementation of the disclosure.

<Embodiment>
In this specification, for ease of understanding, there are some places where the phrase "by way of example and not by way of limitation" is used; however, it should be noted that not only these places, but also the entirety of the embodiments described below are not limited to the contents of the description.

An embodiment for implementing the program etc. disclosed herein will be described with reference to the drawings.

A system may be, by way of example and not limitation, comprised of multiple devices.
The multiple devices may be a combination of devices of the same type, a combination of devices of different types, or a combination of devices of the same type and devices of different types.
Note that a system can be considered, by way of example and not limitation, as a plurality of devices working together to perform some kind of processing.

Furthermore, a system relating to a client (client device) and a server can be considered to be, by way of example and not limitation, at least one of the following:
(1) Terminal & Server (2) Server (3) Terminal

(1) is, by way of example and not limitation, a system that includes at least one terminal and at least one server. One example of this is a client-server system.

The server is, by way of example and not limitation, composed of the following devices, which may be a single device or a combination of multiple devices:

Specifically, the server is configured to have at least one processor (for example and without limitation, a CPU: Central Processing Unit, a GPU: Graphics Processing Unit, an APU: Accelerated Processing Unit, a DSP: Digital Signal Processor (for example and without limitation, an ASIC: Application Specific Integrated Circuit, an FPGA: Field Programmable Gate Array), etc.), a computer device (processor + memory), a control device, an arithmetic device, a processing device, etc., and may be a configuration having multiple of the same type of any one device (for example and without limitation, a CPU + CPU, a homogeneous multi-core processor, etc.), or a configuration having multiple different types of any one device (for example and without limitation, a CPU + DSP, a heterogeneous multi-core processor, etc.), or may be a combination of multiple devices (for example and without limitation, a processor + computer device, a processor + arithmetic device, a heterogeneous combination of multiple devices, etc.).
The processor may be a virtual processor.

Furthermore, when a server executes some processing, if the server is configured with a single device, the processing described in the embodiment is executed by the single device. If the server is configured with multiple devices, the server may be configured to execute some processing by one device and execute other processing by the other device. As a non-limiting example, if the server is configured with a processor and an arithmetic device, the server may be configured to execute a first processing by the processor and execute a second processing by the arithmetic device.
Furthermore, when a configuration is made up of a plurality of devices, the devices may be arranged in locations physically separated from one another.

Furthermore, the server functions may be provided in the form of PaaS, IaaS, or SaaS in cloud computing, for example and without limitation.

The control unit of the system can be at least one of the control unit of the terminal and the control unit of the server. In other words, by way of example and not limitation, the control unit of the system can be any of the following: (1A) only the control unit of the terminal, (1B) only the control unit of the server, or (1C) both the control unit of the terminal and the control unit of the server.

In addition, the control and processing (hereinafter collectively referred to as "control, etc.") performed by the control unit of the system may be (1A) performed only by the control unit of the terminal, (1B) performed only by the control unit of the server, or (1C) performed by both the control unit of the terminal and the control unit of the server.
In addition, in (1C), as an example and not a limitation, some of the controls performed by the control unit of the system may be performed by the control unit of the terminal, and the remaining controls may be performed by the control unit of the server. In this case, the allocation (allocation) of the controls may be equal or may be allocated in different proportions.

Furthermore, when referring to a communication unit of a server, if the server is configured with a single device, it may be the communication unit itself that the single device has, or if the server is configured with multiple devices, the communication unit of the server may be configured to include each communication unit that each device has.
As an example and not by way of limitation, if a server comprises a first device and a second device, the first device having a first communication unit and the second device having a second communication unit, the communication unit of the server may be conceptualized as including the first communication unit and the second communication unit.

(2) can be, by way of example and not limitation, a system made up of multiple servers (hereinafter referred to as a "server system"). In this case, the configuration of each server can be similarly applied to the configuration described above.

The control etc. performed by the server system may be performed by only one of the multiple servers (2A), by only the other servers (2B), or by both the one server and the other servers (2C).
In addition, in (2C), as an example and not a limitation, one server may perform part of the control etc. performed by the server system, and another server may perform the remaining control etc. In this case, the allocation (allocation) of the control etc. may be equal or may be allocated in different proportions.

(3) By way of example and not limitation, the system may be made up of multiple terminals.
The system may be, by way of example and not limitation, a system such as the following:
A system in which terminals have server functions (distributed system). This can be realized, for example and without limitation, by using blockchain technology.
A system in which terminals communicate wirelessly with each other. This can be realized, for example and without limitation, by communicating in a peer-to-peer (P2P) manner using short-range wireless communication technology such as Bluetooth.

The above is not limited to the control unit, but also applies to each functional unit such as the input/output unit, communication unit, memory unit, clock unit, etc., which may be components of the system.

In the following embodiment, a system including a terminal and a server (a client-server system) is illustrated as an example and not as a limitation.
Incidentally, the server system described above in (2) can also be applied as the server.

Also, instead of a system including a terminal and a server, a system not including a server, such as the above-mentioned system (3) as an example and not a limitation, may be applied.
In this case, the embodiment can be configured based on the above-mentioned blockchain technology. Specifically, by way of example and not limitation, data stored and managed in a server described in the following embodiment is stored on the blockchain. Then, the terminal generates a transaction to the blockchain, and when the transaction is approved on the blockchain, the data stored on the blockchain can be updated.

It should be noted that even when the term "terminal" is used, this is not limited to the meaning of a terminal as a client device in a client server.
That is, a terminal may include the concept of a device other than in a client-server context.

In addition, the expression "through a communication I/F" is used appropriately in this specification. This is not intended to be limiting, but may be taken as an example to indicate that a device transmits and receives various types of information and data through a communication I/F (through a communication unit) based on the control of a control unit (such as a processor).

In addition, in this specification, when the terms "related to" and "associated" are used, such as "B related to A" or "B related to A," this may mean, by way of example and not limitation, that "B" has some kind of relationship with "A." Specific examples of this will be described later.

In addition, in this specification, when a device performs processing on two or more objects, such as "transmitting A and B" or "receiving A and B," this may include performing "A" and "B" in unison (hereinafter referred to as "simultaneous"), and performing "A" and "B" with different timing (hereinafter referred to as "non-simultaneous").
As an example and not a limitation, when referring to transmitting first information and second information, this may include both concepts of transmitting the first information and the second information in a synchronized manner and transmitting the first information and the second information with a lag in timing.
In addition, taking into consideration the lag (time lag), "simultaneous" may include "almost simultaneously."

Note that, even if "A" and "B" are performed at different times, this only needs to be the processing targeting "A" and "B," and the purpose does not necessarily have to be the same.
As an example and not a limitation, when the first information and the second information are transmitted as described above, it is sufficient to transmit the first information and the second information, and this may include cases where the first information and the second information are transmitted for the same purpose as well as cases where the first information and the second information are transmitted for different purposes.

In the following embodiment, a service that enables a user to make a payment (hereinafter, referred to as a "payment service") will be exemplified. Also, an application for realizing the payment service will be referred to as a "payment application."
By way of example and not limitation, a payment application may enable a user to make payments using electronic currency.

As a payment method using electronic currency, by way of example and not limitation, either "customer-presented" code payment or "store-presented" code payment can be applied.

By way of example and not limitation, “customer-presented” code payment can be a method in which a user presents code information displayed on display unit 24 of terminal 20 to a store clerk and has the code read by the store's code reader, thereby making a payment.
By way of example and not limitation, the "store-presented" code payment can be a method in which a user makes a payment by having the code reader of their terminal 20 read code information presented by a store.

While either payment method can be used, the following example will focus on "customer-presented" code payment for simplicity. However, the same method can also be used for "store-presented" code payment.

In the following embodiment, a messaging service is illustrated as an example of a service that allows users to chat (hereinafter, referred to as a "chat service"). An application for realizing the chat service is referred to as a "chat application," and an application for realizing the messaging service is referred to as a "messaging application."
By way of example and not limitation, a chat application may enable users to chat in chat rooms.

Note that messaging services (MS) (including instant messaging services (IMS)) can also be considered as one form of social networking services (SNS). For this reason, messaging services and social networking services may or may not be distinguished. In other words, social networking services may include messaging services.

In addition, in the following embodiments, as an example of a messaging service, an instant messaging service (IMS) that transmits and receives content in the form of simple messages between multiple devices (terminals, for example and not limitation) via a server is exemplified.
By way of example and not limitation, an instant messaging application may allow users to talk in talk rooms.

A chat room (for example, but not limited to, a talk room) can be a UI (User Interface) or GUI (Graphical User Interface) that allows each user to view content sent and received between the terminals of multiple users.

In addition, chat rooms can include one-to-one user chat rooms (hereinafter referred to as "one-to-one chat rooms"), group chat rooms including multiple users (hereinafter referred to as "group chat rooms"), and chat rooms with official account users (hereinafter referred to as "OA chat rooms").

For data management purposes, a one-to-one chat room may be managed as a one-to-one user or one-to-one account chat room, or as a group chat room consisting of two users or two accounts.

An official account is an account of a business operator (an account of a user of the business operator) rather than that of a general user, and by way of example and not limitation, a user of this official account can use a terminal similar to that of a general user to send and receive content (messages) with other devices via the server.

In this specification, content may be information transmitted from a source to a destination. Also, content may be one or more pieces of content.

The content may include, by way of example and not limitation, text content in the form of text, image content in the form of images (including at least one of still images and/or moving images), audio content in the form of sounds (including voice), and the like.
In addition, the content may include operation content such as buttons and icons for user operation, and link content such as link information (including, but not limited to, a URI (Uniform Resource Identifier)).

The text may include, by way of example and not limitation, at least one of national characters, extended characters, machine-dependent characters, numbers, symbols, graphics, and signs, all of which are represented by character codes.
The text does not have to include at least one of the above characters, extended characters, machine-dependent characters, numbers, symbols, figures, and signs, and may include other text.

The image may include at least one of various types of image information, such as, for example and not limitation, icons, buttons, stamps, emojis, and banner images.

As a form for realizing the payment service (payment application), any of the following forms can be applied, by way of example and not by way of limitation.
(A) A form in which a payment service function is provided as one function of a messaging application. (B) A form in which an application having a payment service function and a messaging service function (an integrated application) is configured. (C) A form in which a messaging application is configured as an application separate from a payment application.

In embodiments (A) and (B), by way of example and not limitation, the payment service provider may be the same provider as the messaging service provider.
In this case, one method is to have the user's account in the messaging application and the user's account in the payment application be a common account.
Alternatively, the user's account in the messaging application and the user's account in the payment application may be automatically associated (linked).

In form (C), by way of example and not limitation, the payment service provider may be a different entity from the messaging service provider.
In the case of (C), a process for associating (linking) a user's account in the messaging application with a user's account in the payment application can be performed.

However, it is also possible to have the functionality of a messaging service as part of the payment application.

In this specification, "electronic currency" refers to electronic currency that is distinct from physical currency and may refer to electronic currency owned by a terminal managed in the various applications mentioned above or by a user of the terminal.
In addition, "electronic currency" may be considered as "digital currency (digital money)."

As one way of thinking, electronic currency can be considered as a concept that includes "electronic money," "virtual currency (crypto assets)," "central bank issued digital currency (CBDB)," etc.

The electronic currency may be a "legal tender" or a "corporate currency." The implementation method of the electronic currency may be "Centralized Finance (CeFi)" or "Decentralized Finance (DeFi)."

In the embodiment described below, as an example and not a limitation, electronic money as corporate currency in centralized finance is used as an example of electronic currency.

In addition, corporate currency may also include physical currency such as coupons.

First Example
The first embodiment is an example, not a limitation, in which electronic currency is transferred from a user of one terminal 20 (hereinafter referred to as the "first terminal" as appropriate) to a user of another terminal 20 (hereinafter referred to as the "second terminal" as appropriate), and a notification is sent to a specific terminal 20 (hereinafter referred to as the "third terminal" as appropriate) based on at least a portion of the electronic currency being used by the user of the second terminal.

As mentioned above, in the following, a business that provides a payment service via a payment application is referred to as a "payment service business."
The payment service provider may also be expressed as a provider that provides a payment application or a provider of the server 10.
In addition, it can also be referred to as a payment service provider, in the sense of a business that provides payment services.

In addition, stores that partner with payment service providers and offer payment services using a payment application to pay for goods and services provided at the store can be considered "affiliated stores."

Furthermore, in the following, the name of the payment application will be referred to as "Payment App" as appropriate in the illustrations and explanations.

The contents described in the first embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<System Configuration>
FIG. 1A is a diagram illustrating an example of a system configuration of a communication system 1 according to an embodiment of the present disclosure.
In the communication system 1, as an example and not a limitation, a server 10, a plurality of terminals 20 (terminal 20A, terminal 20B, terminal 20C, . . . ), and one or more store POS systems 40 are connected via a network 30.

The server 10 has a function of providing a predetermined service (such as, for example and not limitation, a payment service, a messaging service, etc.) to the terminal 20 owned by the user via the network 30. The server 10 can also be expressed as, for example and not limitation, a payment server, a settlement server, a messaging server, etc.
In this embodiment, payment service providers (operators) and messaging service providers (operators) are users of the server 10 .

The number of servers 10 and the number of terminals 20 connected to the network 30 are not limited.

The terminal 20 (terminal 20A, terminal 20B, terminal 20C, ...) may be any information processing terminal capable of implementing the functions described in each embodiment. Examples of the terminal 20 include, but are not limited to, a smartphone, a mobile phone (feature phone), a computer (such as, but not limited to, a desktop, laptop, tablet, etc.), a media computer platform (such as, but not limited to, a cable or satellite set-top box, a digital video recorder), a handheld computer device (such as, but not limited to, a PDA (personal digital assistant), an email client, etc.), a wearable device (such as, but not limited to, a glasses-type device, a watch-type device, etc.), a VR (Virtual Reality) terminal, a smart speaker (a device for voice recognition), or other types of computers or communication platforms. The terminal 20 may also be expressed as an information processing terminal.

The configurations of the terminals 20A, 20B, and 20C can be the same as one another, for example and not for limitation. In addition, if necessary, the terminal used by the user X may be expressed as the terminal 20X, and the user information in a predetermined service associated with the user X or the terminal 20X may or may not be expressed as the user information X.
The user information is information of a user associated with an account used by the user in a specific service. The user information includes, but is not limited to, information associated with a user, such as the user's name, the user's icon image, the user's age, the user's sex, the user's address, the user's hobbies and interests, and the user's identifier, which is input by the user or given by a specific service, and may be any one of these, or a combination of these, or may not be the same.

The network 30 serves to connect one or more terminals 20 and one or more servers 10. In other words, the network 30 refers to a communication network that provides a connection path so that the above-mentioned various devices can connect and then send and receive data.

One or more portions of network 30 may or may not be wired or wireless. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular network, integrated service digital networks (ISDN), wireless LAN, long term evolution (LTE), code division multiple access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof. Network 30 may include one or more networks 30.

The server 10 (not limited to, but an example of a server, information processing device, or information management device) has a function of providing a predetermined service to the terminal 20. The server 10 may be any device that is an information processing device that can realize the functions described in each embodiment. The server 10 includes, not limited to, a server device, a computer (not limited to, but an example of, a desktop, laptop, tablet, etc.), a media computer platform (not limited to, but an example of, a cable or satellite set-top box, digital video recorder, etc.), a handheld computer device (not limited to, but an example of, a PDA, email client, etc.), or other types of computers or communication platforms. The server 10 may also be expressed as an information processing device. When it is not necessary to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not be expressed as information processing devices.

[Hardware (HW) configuration of each device]
The HW configuration of each device included in the communication system 1 will be described.

(1) Terminal HW Configuration FIG. 1A shows an example of the HW configuration of the terminal 20.
The terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I/F 22 (interface), an input/output unit 23, a clock unit 29A, and a position calculation information detection unit 29B. The HW components of the terminal 20 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW configuration of the terminal 20 includes all of the components. For example and not for limitation, the terminal 20 may or may not be configured such that individual components or multiple components are removable.

The communication I/F 22 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 22 has a function of communicating with various devices such as the server 10 via the network 30. The communication I/F 22 transmits various data to various devices such as the server 10 according to instructions from the control unit 21. The communication I/F 22 also receives various data transmitted from various devices such as the server 10 and transmits it to the control unit 21. The communication I/F 22 may also be simply referred to as a communication unit. When the communication I/F 22 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20, a device for outputting the results of processing performed by the terminal 20, etc. The input/output unit 23 may be an integrated input unit and an output unit, or may be separate input unit and output unit, or it may not be the case.

The input unit is realized by any one or combination of any type of device that can accept input from a user and transmit information related to the input to the control unit 21. Examples of the input unit include, but are not limited to, a touch panel, a touch display, hardware keys such as a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input by voice).

The output unit is realized by any one or a combination of any type of device capable of outputting the results of processing by the control unit 21. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (audio output), a lens (for example, but not limited to, 3D (three dimensions) output or hologram output), a printer, etc.

By way of example only, the input/output unit 23 includes, by way of example and not limitation, a display unit 24, a sound input unit 25, a sound output unit 26, and an imaging unit 27.

The display unit 24 is realized by any one of all types of devices or a combination thereof that can display according to the display data written to the frame buffer. Examples of the display unit 24 include, but are not limited to, touch panels, touch displays, monitors (for example, but not limited to, liquid crystal displays and organic electroluminescence displays (OELDs)), head mounted displays (HDMs), projection mapping, holograms, and devices that can display images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

The sound input unit 25 is used to input sound data (including voice data; the same applies below). The sound input unit 25 includes a microphone and the like.
The sound output unit 26 is used to output sound data and includes a speaker and the like.
The imaging unit 27 is used to obtain image data (including still image data and moving image data; the same applies below). The imaging unit 27 includes a camera and the like.

If the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may be arranged facing each other and have approximately the same size and shape.

The clock unit 29A is a built-in clock of the terminal 20, and outputs time information (timekeeping information). The clock unit 29A is configured to include, for example and not limitation, a clock that uses a crystal oscillator. The clock unit 29A can also be expressed as a timekeeping unit or a time information detection unit, for example and not limitation.

The clock unit 29A may or may not have a clock that conforms to the NITZ (Network Identity and Time Zone) standard or the like.

The position calculation information detection unit 29B is a functional unit that detects (measures) information (hereinafter referred to as "position calculation information") necessary for the control unit 21 to calculate (measure) the position of its own terminal 20. The position calculation information detection unit 29B can also be expressed as a position calculation sensor unit, for example and not by way of limitation.

The position calculation information detection unit 29B includes, by way of example and not limitation, a satellite positioning sensor (satellite positioning unit) which is a sensor or unit for calculating the position of the terminal 20 using a satellite positioning system such as GPS (Global Positioning System), an inertial measurement sensor (inertial measurement unit (IMU (Inertial Measurement Unit))) which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system, a UWB positioning sensor (UWB positioning unit) which is a sensor or unit for calculating the position of the terminal 20 using UWB (Ultra Wide Band), etc.

The satellite positioning unit includes, by way of example and not limitation, an RF receiving circuit that converts RF (Radio Frequency) signals, including positioning satellite signals transmitted from positioning satellites and received by an antenna (not shown), into digital signals, and a baseband processing circuit that performs correlation calculation processing or the like on the digital signals output from the RF receiving circuit to capture the positioning satellite signals, and outputs information such as satellite orbit data and time data extracted from the positioning satellite signals as information for position calculation.

The inertial measurement unit has an inertial sensor that detects information required to calculate the position of the terminal 20 by inertial navigation calculation. Examples of inertial sensors include, but are not limited to, a three-axis acceleration sensor and a three-axis gyro sensor, and output the acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor as information for position calculation.

The UWB positioning unit includes, by way of example and not limitation, an ultra-wideband RF (Radio Frequency) receiving circuit that converts an ultra-wideband RF signal, including an ultra-wideband pulse signal for positioning transmitted from a positioning beacon and received by an antenna not shown, into a digital signal, and a relative position calculation processing circuit that calculates the relative position between the terminal 20 and the positioning beacon based on the digital signal output from the ultra-wideband RF receiving circuit.
As an example and not by way of limitation, the UWB positioning unit may or may not cause the terminal 20 to function as a positioning beacon by transmitting an ultra-wideband RF signal including an ultra-wideband pulse signal for positioning from an antenna not shown.

By way of example and not limitation, the control unit 21 calculates the position of its own terminal 20 at regular or specific timings based on the position calculation information detected by the position calculation information detection unit 29B. The terminal position is referred to as the "terminal position", and the calculated terminal position is referred to as the "calculated terminal position". The control unit 21 may, but may not, associate the calculated terminal position with the date and time when the calculated terminal position is calculated and store it in the storage unit 28 as calculated terminal position history data.

The control unit 21 has circuitry that is physically structured to execute functions realized by the code or instructions contained in the program, and is realized by, for example and not by way of limitation, a data processing device built into hardware. As such, the control unit 21 may or may not be described as a control circuit.

The control unit 21 may include, by way of example and not limitation, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an application-specific integrated circuit (ASIC), and a field programmable gate array (FPGA).

The storage unit 28 has a function of storing various programs and various data required for the operation of the terminal 20. The storage unit 28 includes, by way of example and not limitation, various storage media such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a random access memory (RAM), and a read only memory (ROM). In addition, the storage unit 28 may or may not be expressed as a memory.

The terminal 20 stores the program P in the memory unit 28, and by executing this program P, the control unit 21 executes the processing of each unit included in the control unit 21. In other words, the program P stored in the memory unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Furthermore, this program P may or may not be expressed as a program module.

(2) HW Configuration of Server FIG. 1A shows an example of the HW configuration of the server 10. As shown in FIG.
The server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I/F 14 (interface), an input/output unit 12, and a clock unit 19. The components of the HW of the server 10 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW of the server 10 includes all components as the configuration of the HW of the server 10. For example and not for limitation, the HW of the server 10 may or may not be configured such that individual components or multiple components are removable.

The control unit 11 has circuitry that is physically structured to execute the functions realized by the code or instructions contained in the program, and is realized, for example and not by way of limitation, by a data processing device built into hardware.

The control unit 11 is typically a central processing unit (CPU), but may also be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, or may not be such a unit. In this disclosure, the control unit 11 is not limited to these.

The storage unit 15 has a function of storing various programs and various data required for the operation of the server 10. The storage unit 15 is realized by various storage media such as a HDD, SSD, and flash memory. However, in this disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be expressed as a memory.

The communication I/F 14 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 14 has a function of performing communication with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. The communication I/F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. The communication I/F 14 may also be simply referred to as a communication unit. When the communication I/F 14 is composed of a physically structured circuit, it may also be referred to as a communication circuit.

The input/output unit 12 includes a device for inputting various operations to the server 10, a device for outputting the results of processing performed by the server 10, and the like. The input/output unit 12 may be an integrated input unit and an output unit, or may be separate input unit and output unit, or it may not be the case.

The input unit is realized by any one or combination of all types of devices that can accept input from a user and transmit information related to the input to the control unit 11. The input unit is typically realized by hardware keys such as a keyboard, or a pointing device such as a mouse. Note that the input unit may or may not include a touch panel, a camera (operation input via video images), or a microphone (operation input via voice), but is not limited to these.

The output unit is realized by any one or a combination of any type of device capable of outputting the results of processing by the control unit 11. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (sound output), a lens (for example, but not limited to, 3D (three dimensions) output or hologram output), a printer, etc.

By way of example only, the input/output unit 12 includes a display unit 13, by way of example and not by way of limitation.

The display unit 13 is realized by a display or the like. The display is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an organic electroluminescence display (OELD)). The display may or may not be a head mounted display (HDM) or the like. These displays may or may not be capable of displaying display data in 3D. In the present disclosure, displays are not limited to these.

The clock unit 19 is a built-in clock of the server 10, and outputs time information (timekeeping information). The clock unit 19 is configured to include, for example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, etc. The clock unit 19 can also be expressed as a timekeeping unit or a time information detection unit, for example and not limitation.

(3) System Configuration of Store POS FIG. 1-2 shows an example of the system configuration of a store POS system 40. As shown in FIG.
The store POS system 40 is a POS system that is installed and used in a store that is affiliated with the operator that operates the server 10, and includes, by way of example and not limitation, a store code reader device 50, a code register 60, and a store server 70.

The store code reader device 50 is communicatively connected to the code register 60 and store server 70 via a POS communication I/F 57 (for example, but not limited to, a wired communication I/F or wireless communication I/F within the store), and reads the code information displayed on the display unit 24 of the terminal 20 during a transaction at the code register 60. Then, based on the read code information, it sends payment request information to the server 10 via the communication I/F 54, and after the payment is made by the server 10, it receives information about the payment result from the server 10 via the communication I/F 54.

The store code reader device 50 includes, by way of example and not limitation, a control unit 51, an input/output unit 52, a display unit 53, a communication I/F 54, a memory unit 55, a sound output unit 56, a POS communication I/F 57, a code reader 58, and a clock unit 59.

The code reader 58 is a code reader for reading code information such as one-dimensional codes (one-dimensional code images), two-dimensional codes (two-dimensional code images), and, by way of example and not limitation, wallet code information, which will be described later.

The code register 60 is, by way of example and not limitation, connected to the store code reader device 50 and the store server 70 via the POS communication I/F 57, and issues a receipt on which is printed information such as the total amount of the sold items and the electronic currency balance of the user of the terminal 20, based on the payment completion notification received by the store code reader device 50 from the server 10.

Also, by way of example and not limitation, a display may be provided integrally with the code register 60 or separately from the code register 60, with the display surface facing the customer.
The code register 60 is a cash register configured to be compatible with a payment application, and can also be called a stationary terminal compatible with a payment application.

The store server 70 manages various types of information, such as, but not limited to, store information about the store itself, information about products sold at the store, information about services provided at the store, and information about sales from the sale of products and provision of services at the store. The store server 70 is configured to be able to communicate with the store code reader device 50 and the code register 60 via the POS communication I/F 57, and is also configured to be able to communicate with external devices such as the server 10 via the network 30.

The store server 70 does not necessarily need to be configured to be able to communicate directly with the store code reader device 50, but may be configured to be able to communicate with the store code reader device 50 via the code register 60. As a non-limiting example, a payment completion notification or the like received by the store code reader device 50 from the server 10 can be sent to the code register 60, and then sent from the code register 60 to the store server 70.

(3) Others The server 10 stores the program P in the storage unit 15, and by executing this program P, the control unit 11 executes the processes of each unit included in the control unit 11. In other words, the program P stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11. This program P may or may not be expressed as a program module.
The same applies to other devices.

In each embodiment of the present disclosure, the CPU of the terminal 20 and/or the server 10 is described as executing the program P to achieve this.

The control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 may or may not realize each process by a CPU having a control circuit, but may also realize each process by a logic circuit (hardware) formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or a dedicated circuit. These circuits may be realized by one or more integrated circuits, and the multiple processes shown in each embodiment may or may not be realized by a single integrated circuit. Furthermore, LSIs are sometimes called VLSIs, super LSIs, ultra LSIs, etc., depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit.

In addition, the program P (which may be, for example and not by way of limitation, a software program, computer program, or program module) of each embodiment of the present disclosure may or may not be provided in a state stored in a computer-readable storage medium. The storage medium is capable of storing the program P in a "non-transitory tangible medium." The program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the program P may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded in the storage medium.

Furthermore, when referring to a system program (a program executed by the system), the system is as described above. The above-mentioned system program is a program that can be executed by the entire system, and this program may be composed of individual programs of the devices that make up the system, for example and without limitation, and the programs stored in each device that makes up the system may be different from each other. In other words, it is not necessary for the programs to be common to the individual devices that make up the system.
As a non-limiting example, if a system is composed of a terminal and a server, and the system program is P1, the system program P1 is composed of a program P2 stored in the terminal and a program P3 stored in the server, and P2 and P3 are for executing the system program and may be different programs. As a non-limiting example, the program P2 stored in the terminal may be a program that executes a first process and transmits the result of the first process to the server, and the program P3 stored in the server may be a program that executes a second process on the received result of the first process and transmits the result of the second process to the terminal.

The storage medium may include one or more semiconductor-based or other integrated circuits (ICs) (such as, by way of example and not limitation, a field programmable gate array (FPGA) or an application specific IC (ASIC)), a hard disk drive (HDD), a hybrid hard drive (HHD), an optical disk, an optical disk drive (ODD), a magneto-optical disk, a magneto-optical drive, a floppy diskette, a floppy disk drive (FDD), a magnetic tape, a solid-state drive (SSD), a RAM drive, a secure digital card, or a drive, any other suitable storage medium, or a suitable combination of two or more of these. The storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, as appropriate. It should be noted that the storage medium is not limited to these examples and may be any device or medium capable of storing the program P. Also, the storage medium may or may not be referred to as a memory.

The server 10 and/or the terminal 20 can realize the functions of the multiple functional units shown in each embodiment by reading the program P stored in the storage medium and executing the read program P.

In addition, the program P of the present disclosure may or may not be provided to the server 10 and/or the terminal 20 via any transmission medium capable of transmitting a program (such as a communication network or broadcast waves). By way of example and not limitation, the server 10 and/or the terminal 20 executes the program P downloaded via the Internet or the like to realize the functions of the multiple functional units shown in each embodiment.

In addition, each embodiment of the present disclosure may be realized in the form of a data signal in which the program P is embodied by electronic transmission.
At least a part of the processing in the server 10 and/or the terminal 20 may or may not be realized by cloud computing consisting of one or more computers.
At least a part or all of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least a part or all of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10.
At least a part or all of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a part or all of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20.

Unless explicitly stated, the judgment configuration in the embodiments of the present disclosure is not essential, and a specified process may or may not be executed when the judgment condition is satisfied, or when the judgment condition is not satisfied.

The programs disclosed herein are implemented using, by way of example and not limitation, scripting languages such as ActionScript and JavaScript (registered trademark), compiler languages such as Objective-C and Java (registered trademark), and markup languages such as HTML Living Standard.

<Functional configuration>
(1) Functional Configuration of the Server FIG. 1-3 is a diagram showing an example of functions realized by the control unit 11 of the server 10 in this embodiment.
The control unit 11 includes, as a functional unit, an application management processing unit 111 for executing application management processing according to an application management processing program 151 stored in the storage unit 15, by way of example and not of limitation.

FIG. 1-4 is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this embodiment.
In the storage unit 15, for example and not limitation, an application management processing program 151 executed as an application management processing, account registration data 153, and an account management database 155 are stored.

The account registration data 153 is registration data relating to the account of an application (in this embodiment, a payment application), and an example of the data configuration is shown in FIG. 1-5.
In the account registration data 153, for example and not by way of limitation, a user name, an application ID, and other registration information are stored in association with each other.

The user name is the name of the account of the terminal 20 that uses this application, and by way of example and not limitation, the name registered by the user of the terminal 20 when using the application is stored.

The application ID is information used to identify an application account, or the account itself.
This application ID is preferably a value unique to each account, and as a non-limiting example, a unique value (proper value) is set and stored by the server 10 for each account.
The application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information related to the terminal or information related to the user of the terminal.

Other registration information may include, by way of example and not limitation, various types of information such as identification information for identifying the terminal 20, the telephone number (terminal telephone number) of the terminal 20, an email address (terminal email address), and authentication information such as passwords (login password, authentication password, etc.) used for various authentications in the application.

The identification information for identifying the terminal 20 may be, for example and not for limitation, a terminal ID (for example and not for limitation, an International Mobile Equipment Identity (IMEI)).
Furthermore, the identification information for identifying the user of the terminal 20 may be, for example and without limitation, an application ID for a general user or an application ID for an official user.

It should be noted that the application ID may or may not be replaced by a "user ID."
Furthermore, in the case of an application in which only one account can be registered per terminal 20, as an example and not a limitation, it is possible to use "identification information for identifying terminal 20 = identification information for identifying the user of terminal 20 = application ID".

Also, by way of example and not limitation, it may or may not be possible to assign multiple device IDs to one application ID.

Also, instead of various IDs such as application IDs, it is possible to apply a method of managing accounts using information such as terminal telephone numbers.
In this case, instead of storing ID information such as an application ID in the account registration data 153 , information such as a terminal telephone number can be stored in the account registration data 153 .

In the following various embodiments, for the sake of simplicity, it is assumed that one account is registered for one terminal 20.
Furthermore, in this case, as described above, "identification information for identifying terminal 20 = identification information for identifying the user of terminal 20 = application ID," so the term "user of the account" used in the following explanation may be considered to be essentially synonymous with "terminal of the account."

The account management database 155 is a database for managing information related to the accounts registered in the account registration data 153. FIG. 1-6 shows an example of the data structure of an account management database 155A.
Account management database 155A stores account management data as management data for each account.

Each account management data stores, by way of example and not limitation, an application ID, a regular electronic money balance, and electronic money management data with notifications.

The regular electronic money balance is the balance of regular (ordinary) electronic money associated with the account of this application ID.

The notification-attached electronic money management data is data for managing information related to notification-attached electronic money associated with the account of this application ID, and by way of example and not limitation, the notification recipient ID, the notifier's name, and the notification-attached electronic money balance are stored in association with each other.

In the embodiment described below, the terminal 20 or server 10 of the remittance source account (or remittance source user) is configured to be able to set a notification to the notification destination account (or notification destination user) as a setting related to remittance of electronic money to the remittance destination account (or remittance destination user). Furthermore, remittance based on this setting is referred to as "remittance with notification", and electronic money remitted based on this setting is referred to as "electronic money with notification".
The notification may include, by way of example and not limitation, a notification based on the use of the electronic money with notification by the destination account (or its user), which is referred to as a "electronic money with notification use notification."

The notification destination ID is information for identifying the account to which the notification of electronic money usage with notification is sent (hereinafter referred to as the "notification destination account"); as a non-limiting example, the application ID of the account set as the notification destination account is stored.

The notifier name is the user name that corresponds to this notification destination ID. In the account registration data 153, the user name associated with the application ID that corresponds to this notification destination ID is stored.

The notification electronic money balance is the balance of notification electronic money associated with this notification destination ID.

As a non-limiting example, each time a sending account sends electronic money with notification to a receiving account, the sending account ID, the notifier name, and the electronic money with notification balance can be associated with each other and added to and stored as a new record in the electronic money with notification management data.
When the notification-attached electronic money balance is reduced by a payment or the like, a notification of usage of the notification-attached electronic money can be sent to the terminal 20 of the user of the account of the notification destination ID.

In this embodiment, information about who sent the notification-attached electronic money to the user of the recipient account is not required. For this reason, the notification-attached electronic money management data does not store information such as the sender ID, but instead stores the notification-attached electronic money balance in association with the recipient ID.

Furthermore, as an example and not a limitation, in the first to third embodiments, the "notification destination account = remittance source account" is assumed, and the notification of electronic money usage with notification is sent to the account (or its user) that made the remittance with notification.

(2) Functional Configuration of the Terminal FIG. 1-7 is a diagram showing an example of functions realized by the control unit 21 of the terminal 20 in this embodiment.
The control unit 21 includes, as a functional unit, an application processing unit 211 for executing application processing according to an application processing program 281 stored in the storage unit 28, for example and not for limitation.

FIG. 1-8 is a diagram showing an example of data stored in the storage unit 28 of the terminal 20 in this embodiment.
In the storage unit 28, for example and not for limitation, an application processing program 281 executed as application processing and an application ID 283 corresponding to this terminal 20 or the account of the user of the terminal 20 are stored.

<Display screen>
In the following, as an example and not a limitation, a case will be described in which the terminal 20 is a smartphone equipped with a display unit 24 having a portrait display.

For example, but not by way of limitation, a smartphone has a touch panel that functions as an input unit and is disposed opposite the display, thereby forming a touch screen. When an element such as an icon, button, item, or input area is displayed on the display, and a part of the touch panel that faces the area in which the element is displayed is operated by a user, a program associated with that element or a subroutine of that program is executed.

In the following, the operation by the user will be described as a tap (tap operation) as an example and not as a limitation.
A tap (tap operation) is, by way of example and not limitation, an action in which a user lightly touches the display unit 24 (touch screen) that is integrally configured with a touch panel with a finger or the tip of a pen, and then releases the touch.

Note that the display screen transitions described below are merely examples of display screen transitions for implementing the method of the present disclosure. In the display screen transitions illustrated below, the display of some display screens may be omitted, or other display screens may be added.

FIG. 1-9 is a diagram showing an example of the transition of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
A case will be illustrated in which the following are used: remittance source account = account of user B.B (user of the first terminal) remittance destination account = account of user A.A (user of the second terminal) notification destination account = remittance source account = account of user B.B (user of the first terminal)

The left side of Figure 1-9 shows, by way of example and not limitation, the main menu screen of the payment application displayed on the display unit 24 of user B.B's terminal 20B.

The name of the payment application, "Payment App," is displayed in the center of the top of the menu screen. In addition, the icon image and user name of the payment application of the user of terminal 20B (user B.B. in this example) are displayed in the top right of the screen.

Below this is a page name display area showing the name of the page in the payment application. In this example, the words "Wallet Main Menu" are displayed in the page name display area to indicate that the page name is the main menu of the payment application.

The area below the page name display area is a balance display area BR1 that displays information about the electronic money balance of this account. By way of example and not limitation, the balance display area BR1 displays the word "Balance," the latest electronic money balance of this account, and a charge button CBT for charging electronic money to the regular electronic money balance.

When a "Transfer" icon IC1, which includes the word "Transfer" and an illustration and is displayed at the bottom of the main menu screen, is tapped, the screen shown in the center of FIG. 1-9 is displayed, by way of example and not by way of limitation.
This screen is for setting a destination account, and by way of example and not limitation, the information for specifying the destination account includes the text "Please specify destination," along with a search box for searching for the destination account by phone number.

Below that, a list of information about accounts that have previously made notification-attached remittances is displayed. Specifically, in this example, an icon image and user name (A.A) corresponding to user A.A, and an icon image and user name (C.C) corresponding to user C.C are displayed. Also, a check box is provided to the left of each, and tapping a check box places a check mark in the check box, making it possible to specify that user's account as a remittance destination account. In this example, the check box corresponding to user A.A is shown checked.

In this state, when the "OK" button BT1 at the bottom of the screen is tapped, the screen on the right side of FIG. 1-9 is displayed, by way of example and not limitation.
This screen is for specifying the remittance amount and setting notifications, and by way of example and not limitation, the top of the screen displays information regarding specifying the remittance amount, including the text "Please specify the amount," along with information for specifying the remittance amount by directly entering the remittance amount or using a button.

In addition, information for setting up notifications is displayed below that. Specifically, by way of example and not limitation, the word "Remittance Destination" is displayed along with an icon image of User A.A., the user of the remittance destination account set on the screen in the center of Figure 1-9, and the user name (A.A.).

Also, below that, a slide button is displayed for setting whether or not to receive information indicating that electronic money has been used by user A.A. (hereinafter referred to as "electronic money usage information with notification"). In this example, a tap or slide operation on the slide button is performed, which indicates that the notification setting has been set to "ON."

As a non-limiting example, the notification-attached electronic money usage information is received by the terminal 20 of the user of the notification destination account and displayed or output as sound, etc., to notify the user that the notification-attached electronic money has been used by the remittance destination account. This notification is referred to as a "notification of electronic money usage with notification."

In this state, when the "Remit" button BT2 at the bottom of the screen is tapped, the screen shown on the left side of FIG. 1-10 is displayed on the display unit 24 of the terminal 20A of the user A.A., by way of example and not limitation.
This screen is a diagram showing an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A.
Below the page name display area is a notification area in which the contents of the notification are displayed, and on the left side of the notification area, notification-attached electronic money remittance result information NR1, which is information regarding the result of the remittance of electronic money with notification, is displayed.
For user A.A, this information indicates that the electronic money with notification has been received, so it can also be considered as electronic money receipt result information with notification.

The notification-attached electronic money remittance result information NR1 includes, by way of example and not limitation, the amount remitted (amount received), the remittance date and time which is the date and time when the notification-attached electronic money remittance process was performed by server 10, a "Receive" icon indicating that the recipient is the remittance destination, illustrated information of the remitter and remittance destination, and a ">Check details" button for checking the details.

In this example, the remittance amount is displayed as "1,000 yen," and next to it is a "Receive" icon indicating that the remittance has been received. In addition, the remittance date and time is displayed as "April 5, 2021, 10:23 AM," and the icon image and user name (B.B) of user B.B are displayed as the remittance source account, and the icon image and user name (A.A) of user A.A are displayed as the remittance destination account.

When user A taps the "Return to Menu" button BT3 at the bottom of the screen, for example and not limitation, the main menu screen in the center of FIG. 1-10 is displayed. As with the main menu screen of terminal 20B on the left side of FIG. 1-9, a balance display area BR2 is configured on the main menu screen of terminal 20A.

Here, the balance displayed in the balance display area BR2 may be, for example and without limitation, the total value of the normal electronic money balance and the notification-attached electronic money balance.
As a non-limiting example, the account with application ID "U001" in FIG. 1-6 is the account of user A.A in this example, and the normal electronic money balance is "500 yen." Also, in this example, user B.B remits "1,000 yen" to user A.A as a remittance with notification, and user A.A receives this. Therefore, the sum of the normal electronic money balance and the electronic money balance with notification is "1,500 yen." Therefore, "1,500 yen" is displayed as the electronic money balance in the balance display area BR2.

After that, assume that user A. A is about to make a purchase at a store, by way of example and not limitation. In this case, when the "Code Payment" icon IC2 containing the words "Code Payment" is tapped on the main menu screen in the center of FIG. 1-10, by way of example and not limitation, the screen on the right side of FIG. 1-10 is displayed.

This screen is a code payment screen for making a code payment, and the words "Code Payment" are displayed in the page name display area.
In addition, in the area below that, a wallet code information display area WCR1 in which wallet code information is displayed is configured.

In this example, the wallet code information display area WCR1 displays, as an example and not a limitation, the word "Balance" indicating the electronic money balance of user A.A and the amount (in this example, "1,500 yen"), a one-dimensional wallet code image represented by a one-dimensional code image (a barcode, as an example and not a limitation), and a two-dimensional wallet code image represented by a two-dimensional code image (a QR code, as an example and not a limitation), as wallet code information.

In addition, in this example, below the one-dimensional code image, a wallet token represented by a predetermined number of digits (in this example, "12 digits") (in this example, "123456789000") is displayed as wallet code information.
The wallet token may be encoded into a two-dimensional wallet code image, for example and not limitation.

It is not necessary to display both the one-dimensional wallet code image and the two-dimensional wallet code image, and only one of them may be displayed.
Also, the wallet token may not be displayed.
Also, as shown in this figure, information regarding the expiration date of the wallet code information (as an example and not a limitation, the time remaining until the expiration date is displayed below the two-dimensional wallet code image) may or may not be displayed.

In addition, since wallet code information is code information used to make payments (settlements), it may also be referred to as payment code information or settlement code information, etc.

In this embodiment, by way of example and not limitation, when the normal electronic money balance is less than the notification electronic money balance, the server 10 may perform payment (payment processing) based on the following:
(a) Payment amount ≦ normal electronic money balance: payment is made from the normal electronic money balance. (b) Normal electronic money balance < payment amount ≦ electronic money balance with notification: consumption is made from the electronic money balance with notification. (c) Electronic money balance with notification < payment amount: payment not possible (payment NG)
That is, in this embodiment, a payment using both the normal electronic money balance and the notification-attached electronic money balance (combined payment) is not made.

in particular,
In this example, (a) means that when making a payment of 500 yen or less, the payment is usually made from the electronic money balance.
(b) means that in this example, when making a payment of more than 500 yen and less than 1000 yen, the payment is made from the notification-attached electronic money balance.
(c) in this example means that if a payment is made over 1000 yen, the payment is not possible.

In this embodiment, as in (c) above, if the payment amount exceeds the maximum value of the electronic money balance with notification, the payment is not allowed. Therefore, it is also possible to use the balance displayed in the wallet code information display area as the electronic money balance with notification.

When making a payment in (a) above, the payment may be made from the notification-attached electronic money balance, as in (b) above. In other words, the notification-attached electronic money balance may be used in preference to the normal electronic money balance to make the payment.

By way of example and not limitation, if the regular electronic money balance is greater than or equal to the notified electronic money balance, the server 10 may perform a payment (payment process) based on the following:
(d) Payment amount ≦ notification electronic money balance: payment is made from notification electronic money balance. (e) notification electronic money balance < payment amount ≦ normal electronic money balance: consumption is made from normal electronic money balance. (f) normal electronic money balance < payment amount: payment not possible (payment NG)

When making a payment in (d) above, the payment may be made from the regular electronic money balance, as in (e) above. In other words, the regular electronic money balance may be used in preference to the notification electronic money balance to make the payment.

In the code payment screen on the right side of FIG. 1-10, by way of example and not limitation, when a one-dimensional wallet code image or a two-dimensional wallet code image is read by the code reader 58 of the store code reader device 50, the payment is made by the server 10.
In this example, it is assumed that user A.A. purchases a book for "1,000 yen" at "XX Bookstore." As a result, by way of example and not limitation, the screen on the left side of FIG. 1-11 is displayed.

In this example, in addition to an image of a robot and text indicating that the payment has been completed, the payment amount (in this example, "1,000 yen"), the date and time of the payment (in this example, "14:50 on April 5, 2021"), and the payment destination (in this example, "XX Bookstore") are displayed, by way of example and not limitation.

When the "Confirm" button BT4 at the bottom of the screen is tapped, the screen in the center of Figure 1-11 is displayed, by way of example and not limitation. This screen is the main menu screen mentioned above, and the balance displayed in the balance display area BR2 has been reduced from "1,500 yen" to "500 yen" due to the payment.

The right side of Figure 1-11 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B of user B, who is the user of the notification destination account in this case.
This notification screen displays electronic money remittance result information NR2 with notification corresponding to electronic money remittance result information NR1 with notification displayed on the notification screen of terminal 20A shown on the left side of FIG. 1-10.

The notification-attached electronic money remittance result information NR2 includes, by way of example and not limitation, the remittance amount, the remittance date and time, a "remittance" icon indicating that the notification-attached electronic money is the sender, illustrated information of the sender and recipient, and a ">Check details" button.

Also displayed below that is notification-attached electronic money usage information NU2, which indicates that the notification-attached electronic money remitted to user A.A. has been used by user A.A.
This notification-attached electronic money usage information NU2 includes, by way of example and not limitation, the date and time when the amount remitted in the notification-attached transfer was used (in this example, "14:50 on April 5, 2021"), text indicating that it was used (in this example, "The electronic money remitted to A.A. has been used"), and a ">Check details" button.
This notification-attached electronic money usage information NU2 allows user B.B, who has remitted money to user A.A, to know that the remitted amount has been used by user A.A.

<Processing>
1-12 and 1-13 are flow charts showing an example of the flow of processes executed by each device in this embodiment.
This figure shows, from the left, an example of processing performed by the control unit 21 of terminal 20A, processing performed by the control unit 21 of terminal 20B, processing performed by the control unit 11 of server 10, and processing performed by the store POS system 40.

Note that the processes described below are merely examples of processes for implementing the method of the present disclosure, and the present disclosure is not limited to these.
Other steps may be added to the process described below, or some steps may be omitted (deleted) from the process described below.

Here, as with the display screen,
The following illustrates an example of processing in which remittance source account = account of user B.B (user of the first terminal), remittance destination account = account of user A.A (user of the second terminal), and notification destination account = remittance source account = account of user B.B (user of the first terminal).

First, the control unit 21 of the terminal 20B performs a setting process for electronic money remittance with notification (B110) based on user input to the input/output unit 23, as a setting process for remittance of electronic money with notification. Specifically, by way of example and not limitation, the amount to be remitted, the remittance destination account (user A.A's account in this example), whether or not to perform electronic money notification with notification (ON/OFF), the notification destination account (user B.B's account in this example), etc. are set.

Next, the control unit 21 of the terminal 20B sends notification-attached electronic money remittance request information, which includes, by way of example and not limitation, the application ID of the remittance source account and the setting information set in B110, to the server 10 via the communication I/F 22 (B120).

When the notification-attached electronic money remittance request information is received from the terminal 20B via the communication I/F 14, the control unit 11 of the server 10 performs notification-attached electronic money remittance processing (S110).
Specifically, based on the setting information, the remittance amount is subtracted from the normal electronic money balance in the account management data of user B.B. Also, a record associating the notification destination ID ("U0002" in this example), the notifier name ("user B.B" in this example), and the notification electronic money balance (the remittance amount) is added to the notification-attached electronic money management data in the account management data of user A.A.

Thereafter, the control unit 11 of the server 10 transmits electronic money remittance result information with notification, which is information relating to the result of electronic money remittance with notification, to each of the terminals 20A and 20B via the communication I/F 14 (S120).
The control unit 21 of the terminal 20A and the control unit 21 of the terminal 20B cause the electronic money remittance result information received from the server 10 to be displayed on the respective display units 24 (A110, B130).

After A110, the control unit 21 of the terminal 20A transmits wallet payment request information to the server 10 via the communication I/F 22 based on the user input to the input/output unit 23 (A120).
When wallet payment request information is received from terminal 20A via communication I/F 14, the control unit 11 of the server 10 generates the wallet code information described above, for example but not limited to, and sends it to terminal 20A via communication I/F 14 (S130).
The electronic money balance information may be included in the wallet code information.

When the wallet code information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20A displays the received wallet code information on the display unit 24 (A130). The wallet code information displayed on the display unit 24 is read by the store code reader device 50 (code reader 58) of the store POS system 40 (P110).

The store code reader device 50 transmits payment request information, which includes, by way of example and not limitation, store information (store ID, etc.), the requested payment amount, and the wallet token contained in the read wallet code information, to the server 10 via the communication I/F 44 (P120).

When the communication I/F 14 receives payment request information from the store POS system 40, the control unit 11 of the server 10 performs payment processing (S140). In this case, the control unit 11 performs payment based on the above-mentioned methods (a) to (f), which are not limiting examples.

Then, the control unit 11 of the server 10 transmits payment result information, which is information regarding the result of the payment, to the terminal 20A and the store POS system 40 via the communication I/F 14 (S150).

The control unit 21 of the terminal 20A causes the display unit 24 to display the payment result information received from the server 10 (A140). Then, the control unit 21 of the terminal 20A ends the process.

Similarly, the control unit 51 of the store code reader device 50 causes the display unit 53 to display the payment result information received from the server 10 (P130). Then, the control unit 51 of the store code reader device 50 ends the process.

After S150, the control unit 11 of the server 10 determines whether or not the notification-attached electronic money balance has been used for the payment in the payment process of S140 (S160).
If it is determined that the information has not been used (S160: NO), the control unit 11 of the server 10 ends the process.
On the other hand, if it is determined that the electronic money has been used (S160: YES), the control unit 11 of the server 10 transmits the electronic money use information with notification to the terminal 20B via the communication I/F 14 (S170). Then, the control unit 11 of the server 10 ends the process.

After B130, the control unit 21 of the terminal 20B determines whether or not the notification-attached electronic money usage information has been received from the server 10 via the communication I/F 22 (B140).
If it is determined that the message has not been received (B140: NO), the control unit 21 of the terminal 20B ends the process.
On the other hand, if it is determined that the electronic money usage information with notification has been received (B140: YES), the control unit 21 of the terminal 20B causes the display unit 24 to display the received electronic money usage information with notification (B150). Then, the control unit 21 of the terminal 20B ends the process.

Effects of the First Embodiment
In this embodiment, the server 10 receives remittance request information (not limiting, an example of information regarding remittance of the first electronic currency) for notification-enabled electronic money (not limiting, an example of the first electronic currency), which is electronic money for which notification settings have been made by a user (not limiting, an example of the user of the first terminal) of the terminal 20 (not limiting, an example of the first terminal) of the user of the remittance source account.
In addition, based on receiving remittance request information, the server 10 performs control through the control unit 11 to store the notification-attached electronic money to be remitted to the user of the destination account in the notification-attached electronic money balance (this is not limited to the above, but is an example of control to associate the first electronic currency to be remitted to the user of the second terminal with the user of the second terminal).
In addition, based on receiving the remittance request information, the server 10 transmits electronic money remittance result information with notification (not limited to this, an example of second information indicating that remittance has been made from the first terminal to the user of the second terminal) to the terminal 20 of the user of the destination account via the communication I/F 14.
The server 10 is configured to transmit notification-attached electronic money usage information (not limiting, an example of a notification) to the terminal 20 (not limiting, an example of a third terminal) of the user of the destination account based on the use of at least a portion of the notification-attached electronic money by the user of the destination account.
As an example of the effect of the embodiment obtained by such a configuration, based on receiving from the first terminal first information which is information regarding sending the first electronic currency for which notification settings have been made by the user of the first terminal to the user of the second terminal, the first electronic currency to be sent to the user of the second terminal can be stored in association with the user of the second terminal, and the user of the second terminal can be notified of the fact that the first electronic currency has been sent from the first terminal. Also, the user of the third terminal can be notified of the fact that at least a portion of the first electronic currency has been used by the user of the second terminal.

In this case, the notification-attached electronic money usage information may include information indicating that at least a portion of the notification-attached electronic money has been used by the user of the remittance destination account.
As an example of an effect of an embodiment obtained by such a configuration, it is possible to inform a user of a third terminal that at least a part of the first electronic currency has been used by a user of a second terminal.

In addition, this embodiment illustrates a configuration in which the terminal 20 (not limited to, an example of a third terminal) of the user of the notification destination account is the terminal 20 (not limited to, an example of a first terminal) of the user of the remittance source account.
As an example of the effect of an embodiment obtained by such a configuration, it is possible to notify a user of a first terminal that has set up notifications that at least a portion of a first electronic currency has been used by a user of a second terminal.

As one example, a parent (mother, father) may transfer electronic money to their child to allow the child to do shopping or the like.
In this case, by way of example and not limitation, the mother's account is the sender account, and the mother's terminal 20 is the first terminal.
Also, by way of example and not limitation, the child's account may be the destination account, in which case the child's terminal 20 is the second terminal.
Also, as a non-limiting example, the mother's account is set as the notification destination account, in which case the mother's terminal 20 becomes the third terminal (=first terminal).
When the child uses the electronic money with notification transferred from the mother through his/her own account to make a purchase or the like, a notification can be sent to the mother's account.

In addition, this embodiment shows a configuration in which the control unit 11 controls the server 10 to distinguish and store electronic money with notification (not limited to, but an example of a first electronic currency with a notification set) and normal electronic money (not limited to, but an example of a second electronic currency associated with a user of a second terminal).
As an example of the effect of an embodiment obtained by such a configuration, it is possible to manage separately a first electronic currency for which a notification has been set and a second electronic currency for which a notification has not been set and which is associated with a user of a second terminal, thereby improving user convenience.

<First Modification (1)>
In the above embodiment, the user of the remittance source account may be able to set the contents of the notification to be sent to the notification destination account.

FIG. 1-14 is a diagram showing an example of an account management database 155B which is an example of the account management database 155 in this modification.
The information stored in each account management data included in the account management database 155B is similar to that in the account management database 155A, but the information stored in the notification-attached electronic money management data is partially different.

Specifically, the notification-attached electronic money management data stores the notification contents in addition to the notification destination ID, the notifier's name, and the notification-attached electronic money balance.
The notification content is more detailed than the content notified to the notified account, and may include, by way of example and without limitation, information such as the "amount" in which the electronic money with the notification was used and the "store" in which the electronic money with the notification was used.

In addition, the notification content may or may not include information about the product or service purchased at the payment destination store. In this case, the store POS system 40 may, by way of example and not limitation, include information about the product or service the user is trying to purchase in the payment request information and send it to the server 10.

Furthermore, at least one of the various pieces of information described above may be stored. In other words, one piece of information may be stored, or two or more pieces of information may be stored.

Each time a sender account sends electronic money with notification to a recipient account, the recipient ID, the name of the sender, the balance of electronic money with notification, and the notification content are associated with each other and added to and stored as a new record in the electronic money with notification management data.

The control unit 11 of the server 10 receives information capable of identifying the notification content sent from the store POS system 40 in step P120 of FIG. 1-13, and performs the payment process in S140 of FIG. 1-13. Then, in step S170 of FIG. 1-13, the control unit 11 of the server 10 includes the notification content in electronic money usage information with notification and sends it to the terminal 20 of the user of the notification destination account. Then, the terminal 20 of the user of the notification destination account displays the electronic money usage information with notification including the notification content on the display unit 24.

FIG. 1-15 is a diagram showing an example of a transition of a display screen of the terminal 20 in this modified example.
The left side of Figure 1-15 is an example of a remittance screen of a payment application displayed on terminal 20B of user B, who is the user of the remittance source account, and corresponds to the right side of Figure 1-9.

In this example, an area for setting whether or not to receive a notification of electronic money use with notification is provided with an area for setting the content of the notification.
Specifically, as a non-limiting example, three items of "amount,""payee," and "contents" are displayed as the notification contents along with the words "notification contents," and a check box is displayed associated with each item. When a check box is tapped, the check box is checked, and the item can be included in the notification contents. In this example, the check box corresponding to the "amount" item and the check box corresponding to the "payee" item are both checked, and the "Transfer" button BT2 is shown as having been tapped.

The center of Figure 1-15 shows an example of a screen displayed on the display unit 24 of user A.A's terminal 20A, which is a code payment completion screen similar to the screen on the left side of Figure 1-11.

The right side of Fig. 1-15 is a diagram showing an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B of user B, who is the notification destination in this case, and corresponds to the right side of Fig. 1-11.
On this notification screen, notification-attached electronic money usage information NU3 is displayed in place of the notification-attached electronic money usage information NU2 on the screen on the right side of FIG. 1-11.

In addition to the information contained in the notification-attached electronic money usage information NU2 on the screen on the right side of Figure 1-11, this notification-attached electronic money usage information NU3 also displays, by way of example and not limitation, the amount of notification-attached electronic money used for the payment (in this example, "1,000 yen") and the payee (in this example, "XX Bookstore").

In this modified example, in step S170 of FIG. 1-13, the server 10 can incorporate the notification content into notification-attached electronic money usage information and transmit it to the terminal 20 of the user of the notification destination account.

In this variation, the notification-included electronic money usage information includes at least one of the following: the amount paid by the user of the destination account (not limiting, but an example of the amount used of the first electronic currency), the payment destination (not limiting, but an example of the location used by the user of the second terminal), and the goods or services purchased.
As an example of an effect of an embodiment obtained by such a configuration, it is possible to inform a user of a third terminal of at least one of the amount of the first electronic currency used by the user of the second terminal, the location where it was used by the user of the second terminal, the product purchased by the user of the second terminal, and the service purchased by the user of the second terminal.

<First Modification (2)>
It is also possible for the server 10 to manage the notification-attached electronic money balance without distinguishing between the normal electronic money balance and the notification-attached electronic money balance.

FIG. 1-16 is a diagram showing an example of a data configuration of an account management database 155C, which is an example of the account management database 155 in this modified example.
In each account management data, for example but not limited to, an application ID, an electronic money balance, and electronic money usage notification destination management data are stored.

The electronic money balance is a common balance that does not distinguish between the normal electronic money balance and the notification electronic money balance described above.

The electronic money usage notification destination management data is data for managing the notification destination when electronic money with notification is used, and as a non-limiting example, the notification destination ID and the name of the notifier are stored in association with each other.

In this modified example, in step S110 of FIG. 1-12, the server 10 subtracts the remittance amount from the electronic money balance in the account management data of user B.B based on the setting information. The server 10 also adds a record associating the notification destination ID ("U0002" in the above example) and the notifier name ("user B.B" in the above example) to the electronic money usage notification destination management data in the account management data of user A.A, and adds the remittance amount to the electronic money balance.

In addition, if the server 10 determines that electronic money has been used and the electronic money balance has become "0", it clears the electronic money usage notification destination management data.

This modified example shows a configuration in which the control unit 11 controls the server 10 to store electronic money with notification (not limited to, but an example of a first electronic currency with a notification set) and normal electronic money (not limited to, but an example of a second electronic currency associated with a user of a second terminal) without distinguishing between them.
As an example of the effect of an embodiment obtained by such a configuration, it is possible to manage a first electronic currency for which notification has been set and a second electronic currency for which notification has not been set and which is associated with a user of a second terminal without distinguishing between them.

<First Modification (3)>
In the first embodiment, when making a payment, there may be cases where the payment is not possible (payment NG) due to insufficient electronic money balance, etc. Examples of this are the above-mentioned cases (c) and (f).
In such a case, if the server 10 determines that payment is not possible during the payment process, it may issue a notification of insufficient balance or payment impossibility, for example by sending insufficient balance information or payment impossibility information to at least one of the terminal 20 of the user of the destination account and the terminal 20 of the user of the notification destination account.

Second Example
The second embodiment is an embodiment in which notification of use of notification-attached electronic money is given according to the balance of the notification-attached electronic money.

The contents described in the second embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

In this embodiment, when the balance of the notification-attached electronic money is equal to or less than a set amount (set value), the notification-attached electronic money use notification is not sent. This is because, by way of example and not by way of limitation, if the balance of the notification-attached electronic money is relatively small, it is difficult to make a large payment or the like from the notification-attached electronic money. By way of example and not by way of limitation, the set amount can be set by the user of the remittance source account (the user of the first terminal, and not by way of limitation).
However, this is not limited to this, and may be set by the server 10 (a user of the server 10), or by a user of the notification destination account (not limited to this, but an example of a user of a third terminal).

<Processing>
FIG. 2-1 is a flowchart showing an example of the flow of processes executed by each device in this embodiment, and shows the portion corresponding to FIG. 1-13.
As a non-limiting example, in step B110 of FIG. 1-12, the control unit 21 of the terminal 20B may set the notification content based on a user input to the input/output unit 23.

If it is determined in S160 that the notification-attached electronic money balance has been used (S160: YES), the control unit 21 of the terminal 20B determines whether the notification-attached electronic money balance is equal to or less than a set amount (S210).
If it is determined that the notification-attached electronic money balance is equal to or less than the set amount (S210: YES), the control unit 21 of the terminal 20B ends the process.
On the other hand, if it is determined that the notification-attached electronic money balance exceeds the set amount (S210: NO), the control unit 21 of the terminal 20B advances the process to S170.

In addition, in S210, the control unit 21 of the terminal 20B may determine whether the notification-attached electronic money balance is less than the set amount.

<Effects of the Second Example>
This embodiment illustrates a configuration in which the notification of electronic money usage with notification is not sent by the server 10 to the terminal 20 (not limited to, but an example of a third terminal) of the user of the notification account if the balance of the electronic money with notification is less than or equal to a set amount.
As an example of the effect of the embodiment obtained by such a configuration, when the notification-attached electronic money balance is relatively small, it is possible to prevent the server from sending the notification to the third terminal.

<Second Modification Example (1)>
The conditions for issuing or not issuing a notification of electronic money use with notification are not limited to those described in the above embodiment.
For example and not by way of limitation, if the amount of the notification-attached electronic money used per transaction is equal to or less than a set amount, the notification of use of the notification-attached electronic money may not be transmitted by the server 10. This is because if the amount used per transaction is small, it is likely that the use of the notification-attached electronic money is not a high-risk one.

Also, as a non-limiting example, the notification may be made at a set timing, rather than every time the notification-enabled electronic money is used. In this case, the conditions for making the notification may be, for example, the following, but are not limited to these:
- At set times (once a month, once a week, etc.)
・When all electronic money with notification has been used. ・When the amount used of electronic money with notification is equal to or greater than the set amount. ・When the percentage of the amount used of electronic money with notification is equal to or greater than the set percentage. ・When the number of times or frequency of use of electronic money with notification is equal to or greater than the set value (e.g., when it is used five or more times within 24 hours) or is greater than the set value. ・A combination of two or more of the above.

The various conditions above may be set, by way of example and not by way of limitation, by a user of the sending account (and not by way of limitation, a user of the first terminal).
However, this is not limited to this, and may be set by the server 10 (a user of the server 10), or by a user of the notification destination account (not limited to this, but an example of a user of a third terminal).

This modified example illustrates a configuration in which the notification of electronic money usage with notification is not sent by server 10 if the amount of electronic money with notification (an example of the first electronic currency, not limited to this) used by the user of the destination account (an example of the user of the second terminal, not limited to this) is less than the set amount or less than the set amount.
As an example of the effect of the modified example obtained by such a configuration, when the amount of the first electronic currency used by the user of the second terminal is relatively small, the server can be prevented from sending a notification to the third terminal, thereby reducing the effort of the user of the third terminal in checking the notification.

Furthermore, this modified example shows a configuration in which the notification-attached electronic money usage notification is sent by the server 10 at a timing set by the user of the remittance source account (not limited to this, but an example of the user of the first terminal).
As an example of the effect of this modified example obtained by such a configuration, a notification can be transmitted from the server to the third terminal at a timing arbitrarily set by the user of the first terminal.

<Second Modification Example (2)>
The user of the notification destination account may be allowed to check the usage history of the notification-attached electronic money by, for example, displaying information regarding the usage history of the notification-attached electronic money on the terminal 20 of the user of the notification destination account.

FIG. 2B is a diagram showing an example of information stored in the storage unit 15 of the server 10 in this modified example.
In addition to the above-mentioned programs and data, the memory unit 15 stores, by way of example and not limitation, payment history management data 157.

FIG. 2C is a diagram showing an example of the data configuration of the payment history management data 157.
The payment history management data is data for managing payment history made from normal electronic money balance without notification and payment history made from electronic money balance with notification, and by way of example and not limitation, the payment ID, application ID, name of the store used, date and time of payment, and payment amount are stored in association with each other.

The payment ID is identification information for uniquely identifying a payment, and by way of example and not limitation, a unique ID is set by the server 10 each time a payment is made using electronic money.

In the application ID field, the server 10 stores the application ID of the terminal 20 (or the user of the terminal 20) that performed the payment (payment-related processing).
The name of the store that requested the payment with that payment ID is stored by the server 10 as the store name used.
As the payment date and time, the date and time when the payment process for that payment ID was performed by the server 10 is stored by the server 10.
The payment amount for that payment ID is stored by the server 10 in the payment amount field.

In addition, instead of the name of the store used, the store ID of the store that requested the payment with that payment ID may be stored.

FIG. 2D is a diagram showing an example of the account management database 155D, which is an example of the account management database 155 in this embodiment.
Each account management data included in the account management database 155D stores, in addition to an application ID, a normal electronic money balance, and notification-attached electronic money management data, notification-attached electronic money usage history data, for example and not by way of limitation.

In this data, the notification-attached electronic money management data stores, by way of example and not limitation, a remittance management ID, a notification destination ID, the name of the notifier, and the notification-attached electronic money balance in association with each other.

Unlike the notification-attached electronic money management data described above, in this embodiment, the notification destination ID, notifier name, and notification-attached electronic money balance are associated with the remittance management ID.

The remittance management ID is an ID for uniquely identifying a remittance of electronic money with notification, and by way of example and not limitation, a different ID is set and stored by server 10 each time a remittance of electronic money with notification is executed by server 10.
As a non-limiting example, even when electronic money with notification is transferred from the same account of user B.B to the same account of user A.A, different IDs are set for each.

The notification-attached electronic money usage history data is data related to the usage history of notification-attached electronic money, and by way of example and not limitation, the payment ID, remittance management ID, name of the store used, date and time of use, and amount used are stored in association with each other.

The payment ID stores a payment ID corresponding to a payment made using notification-attached electronic money, among the payment IDs stored in the payment history management data 157.
By storing this payment ID, the server 10 can determine the required amount even when returning a product or service.

The remittance management ID stores the remittance management ID stored in the notification-attached electronic money management data that corresponds to the notification-attached electronic money balance used in the payment for this payment ID.

The store name of the store used is the name of the store used that corresponds to this payment ID from among the store names stored in the payment history management data 157.

The date and time of use is the payment date and time stored in the payment history management data 157 that corresponds to this payment ID.

The amount used is the amount of notification-attached electronic money used in the payment for this payment ID, out of the payment amounts stored in the payment history management data 157.

In this embodiment, the server 10 performs the settlement by the above-mentioned methods (a) to (f).
Of these, in the above-mentioned cases (b) and (d), the payment is made from the notification-attached electronic money balance, so that amount can be stored as the amount used.

Although details will be described later, it is also possible to use both the normal electronic money balance without notification and the electronic money balance with notification for payment. In this case, the total amount of these amounts is stored as the payment amount in the payment history management data 157 (FIG. 2-3).
In this case, the amount of the notification-attached electronic money used in the payment out of the payment amount can be stored as the usage amount in the notification-attached electronic money usage history data (FIG. 2-4).

As a non-limiting example, the account management data shown in the foreground of FIG. 2-4 is the account management data of the remittance destination user A.A., and the remittance management ID "T01003" in the electronic money management data with notification indicates that "2,000 yen" was remitted by the electronic money remittance with notification from the remitter user B.B., and the electronic money balance with notification was "2,000 yen."
Thereafter, payments were made using the notification-attached electronic money for the payment IDs "P21053,""P29903," and "P32306" in the notification-attached electronic money usage history data, and the total amount used was "1,000 yen + 400 yen + 200 yen = 1,600 yen," so the notification-attached electronic money balance was "2,000 yen - 1,600 yen = 400 yen."

The left side of Figure 2-5 shows an example of a notification screen for the payment application displayed on the display unit 24 of user B's terminal 20B, who is the user of the remittance source account and the user of the notification destination account in this modified example.

This notification screen displays notification-attached electronic money usage information NU21.
This electronic money usage information NU21 with notification includes, by way of example and not limitation, a "Check Usage History" button BT21 containing the words "View Usage History" for allowing the user to check the usage history of the remittance with notification.

When this "Check Usage History" button BT21 is tapped, the screen shown in the center of FIG. 2-5 is displayed, by way of example and not limitation.
This screen is an example of an electronic money usage history screen with notification in a payment application, and at the top, an icon image of user A.A and his/her user name (A.A.) are displayed, along with the total amount of remittance with notification (in this example, "2,000 yen") and the unused amount of that (in this example, "400 yen").

Below that is provided selection information that the user can select, for example but not limited to "1 week," "1 month," and "6 months," to enable viewing of notification-included electronic money usage history over a specified period of time in the past. This selection information is similar to a tab, and for convenience is referred to as a "selection tab."

In this example, when the selection tab corresponding to "1 week" is tapped, that selection tab is highlighted, and below it is displayed a list of electronic money usage history with notification for the past week period. Specifically, in this example, a payment of "1,000 yen" at "XX Bookstore," a payment of "400 yen" at "Convenience Store YY," and a payment of "200 yen" at "ZZ Supermarket" are displayed. In other words, of the total amount of remittance with notification (the above "2,000 yen"), "1,600 yen" has been used.

Below that, a "Check Usage" button BT22 containing the words "View Usage" is provided for the user to check the specific usage of the notification-enabled electronic money. When this "Check Usage" button is tapped, the screen on the right side of FIG. 2-5 is displayed, by way of example and not limitation.
As a non-limiting example, a trend graph of the notification-attached electronic money balance corresponding to the period displayed when the "Check Usage" button BT22 is tapped is displayed. In this example, a trend graph of the notification-attached electronic money balance for the past "one week" period (in this example, the period from April 5, 2021 to April 11, 2021) is displayed on the screen on the right side of FIG. 2-5, corresponding to the notification-attached electronic money usage history for the past "one week" period displayed on the screen in the center of FIG. 2-5 when the "Check Usage" button BT22 is tapped.

In addition, below the trend graph, there is a "View Usage History List" button BT23 containing the words "View Usage History List." When this "View Usage History List" button BT23 is tapped, the screen returns to the center screen of Figure 2-5.

In this modification, by way of example and not limitation, various devices may be configured to execute the processes according to FIGS. 1-12 to 2-1.
As a non-limiting example, the electronic money remittance result information with notification may include a remittance management ID set by the electronic money remittance with notification process.

In this process, the control unit 21 of the terminal 20 of the user of the notification destination account stores the notification-attached electronic money usage information in the memory unit 28, for example and not for limitation. Then, based on user input, the control unit 21 of the terminal 20 of the user of the notification destination account can cause the display unit 24 to display the notification-attached electronic money usage history based on the notification-attached electronic money usage information stored in the memory unit 28.

Alternatively, the control unit 21 of the terminal 20 of the user of the notification destination account may transmit notification-attached electronic money usage history data request information to the server 10, and the control unit 11 of the server 10 may transmit notification-attached electronic money usage history data to the terminal 20 of the user of the notification destination account.

In this case, by way of example and not limitation, the control unit 21 of the terminal 20 of the user of the notified account can generate a trend graph based on the notification-attached electronic money usage information stored in the memory unit 28.
Alternatively, the control unit 11 of the server 10 may generate a trend graph based on the notification-attached electronic money usage history data (FIG. 2-4) and transmit it to the terminal 20 of the user of the notification destination account.

This modified example shows a configuration in which the server 10 transmits information regarding the usage history of notification-attached electronic money (not limited to, but an example of a first electronic currency) by a user of a destination account (not limited to, but an example of a user of a second terminal) to a terminal 20 (not limited to, but an example of a third terminal) of the user of the destination account.
As an example of the effect of this modified example obtained by such a configuration, based on the use of at least a portion of the first electronic currency by the user of the second terminal, information regarding its usage history can be provided to the user of the third terminal.

<Second Modification Example (3)>
As described above, by storing the payment ID in the payment history management data 157, the server 10 can determine the required amount even when returning a product or service.
In this case, when refunding at least a portion of the notification-attached electronic money used by the user of the remittance destination account, the control unit 11 of the server 10 identifies the payment ID sent from the store POS system 40 from the payment history management data 157. This is to confirm whether or not a payment has been made and to identify the payment amount.

Next, the control unit 11 of the server 10 refers to the notification-attached electronic money usage history data contained in the account management data of the user of the remittance destination account in the account management database 155D, and identifies the remittance management ID that corresponds to the identified payment ID.

If there is no remittance management ID corresponding to the identified payment ID, the notification-attached electronic money was not used for the payment. Therefore, the refund amount is added to the regular electronic money balance. If the payment was made using only regular electronic money, the payment amount corresponding to the identified payment ID in the payment history management data 157 becomes the refund amount to the regular electronic money balance.

On the other hand, if a remittance management ID exists that corresponds to the identified payment ID, it means that the notification-attached electronic money was used for the payment. Therefore, the amount used that corresponds to the identified payment ID is identified from the notification-attached electronic money usage history data, and this amount used is added to the notification-attached electronic money balance of the corresponding remittance management ID in the notification-attached electronic money management data.

In this modified example, when the server 10 refunds at least a portion of the notification-attached electronic money used by the user of the destination account, the control unit 11 controls the refund to the user of the destination account with a notification set on at least a portion of the notification-attached electronic money.
As an example of the effect of the modified example obtained by such a configuration, when it is necessary to refund at least a portion of the first electronic currency used by the user of the second terminal, the refund can be made to the user of the second terminal with a notification set on at least a portion of the first electronic currency.

<Third Example>
The third embodiment is an embodiment that enables the user of the remittance destination account to confirm the remittance of electronic money with notification and the association of the electronic money with notification with the account of the remittance destination user.

The contents described in the third embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Display screen>
The left side of Figure 3-1 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A of User A, who is the user of the remittance destination account.
On the left side of the notification area of this notification screen, notification-attached electronic money receipt confirmation information NC31 for confirming receipt of notification-attached electronic money from user B.B. is displayed.

In this notification-attached electronic money receipt confirmation information NC31, by way of example and not limitation, the amount to be remitted (in this example, "1,000 yen"), a "Receive" icon indicating that the user is the recipient, an illustration indicating that user B.B. will be notified when the remitted notification-attached electronic money is received and used, the date and time of transmission of the notification-attached electronic money receipt confirmation information NC31 by server 10, the text "Electronic money with notification has arrived (usage status will be notified to B.B.)," an illustration indicating that the remittance is from user B.B. to user A.A, and a ">Check details" button are displayed. In addition, a "Reject" button BT31 for refusing to receive the notification-attached electronic money and a "Receive" button BT32 for permitting the receipt of the notification-attached electronic money are displayed.

Note that since user A.A has not yet received the electronic money with notification, the electronic money with notification receipt confirmation information NC31 uses the expression "Electronic money with notification has arrived" as an example and not a limitation.

When the "Decline" button BT31 is tapped, the notification-attached electronic money is not remitted from user B.B to user A.A. Also, a screen such as that shown on the right side of FIG. 3-1 is displayed on the display unit 24 of the terminal 20B of user B.B, who is the user of the remittance source account, by way of example and not limitation.
This screen is a diagram showing an example of a notification screen of a payment application displayed on the display unit 24 of terminal 20B, and on the left side of the notification area, notification-attached electronic money receipt refusal information ND31 is displayed, indicating that receipt of the notification-attached electronic money has been refused.

Specifically, by way of example and not limitation, the date and time when the notification-attached electronic money refusal information ND31 was sent by the server 10, the text "Failed to transfer notification-attached electronic money to A.A," the amount attempted to be transferred (in this example, "1,000 yen"), and a ">Check details" button labeled ">Check details" are displayed.

On the other hand, when the "Receive" button BT32 is tapped on the screen on the left side of FIG. 3-1, a transfer of electronic money with notification is made from user B.B to user A.A.

<Processing>
3B and 3C are flow charts showing an example of the flow of processes executed by each device in this embodiment.
When the control unit 11 of the server 10 receives the notification-attached electronic money remittance request information from the terminal 20B, the control unit 11 transmits notification-attached electronic money receipt confirmation information to the terminal 20A via the communication I/F 14 (S310).
In this case, the notification-attached electronic money receipt confirmation information may include, by way of example and not limitation, information indicating that notification has been set for the electronic money to be transferred to the user of terminal 20A.

In response to this, the control unit 21 of the terminal 20A causes the display unit 24 to display the received electronic money receipt confirmation information with notification (A310).

Then, the control unit 21 of the terminal 20A judges whether or not to accept the notification-attached electronic money based on, for example, a user input to the input/output unit 23 indicating acceptance of the receipt (A320). If it is judged not to accept the notification-attached electronic money (A320: NO), the control unit 21 of the terminal 20A ends the process.

On the other hand, if it is determined that the electronic money should be received (A320: YES), the control unit 21 of the terminal 20A transmits electronic money receipt acceptance information with notification to the server 10 via the communication I/F 22 (A330).

After S310, the control unit 11 of the server 10 determines whether or not electronic money receipt acceptance information with notification has been received from the terminal 20A (S320), and if it is determined that it has been received (S320: YES), the process proceeds to S110.

On the other hand, if it is determined that the electronic money has not been received (S320: NO), the control unit 11 of the server 10 sends electronic money refusal information with notification to the terminal 20B via the communication I/F 14 (S330).

After B120, the control unit 21 of the terminal 20B determines whether or not electronic money receipt refusal information with notification has been received from the server 10 (B310), and if it determines that it has not been received (B310: NO), it executes step B130.

On the other hand, if it is determined that the notification has been received (B310: YES), the control unit 21 of the terminal 20B causes the display unit 24 to display the received electronic money receipt refusal information with notification (B320). Then, the control unit 21 of the terminal 20B ends the process.

In the above process, the control unit 11 of the server 10 may transmit, in step S120, information indicating that a notification has been set for the electronic money to be remitted to the user of the terminal 20A, in addition to transmitting electronic money receipt confirmation information with notification to the terminal 20A in step S310, and may transmit the information to the terminal 20A in step S120.

In addition, in the above process, the control unit 21 of the terminal 20A may not execute step A320, but execute step A330 after step A310.

<Effects of the Third Embodiment>
This embodiment shows a configuration in which the server 10 transmits electronic money receipt confirmation information with notification (not limited to, but an example of notification setting information indicating that notification settings have been made for the first electronic currency remitted to the user of the second terminal) to the terminal 20 of the user of the destination account via the communication I/F 22.
As an example of the effect of an embodiment obtained by such a configuration, it is possible to inform the user of the second terminal that a notification setting has been made for the first electronic currency transferred to the user of the second terminal.

In this case, the server 10 receives, based on the transmission of the electronic money receipt confirmation information with notification, electronic money receipt acceptance information with notification (not limited to this, an example of permission information regarding permission to remit to the user of the second terminal) transmitted from the terminal 20 of the user of the remittance destination account via the communication I/F 14. Then, based on the reception of this electronic money receipt acceptance information with notification, the electronic money with notification is stored in association with the user of the remittance destination account.
As an example of an effect of an embodiment obtained by such a configuration, it is possible to prevent the first electronic currency from being stored in association with the user of the second terminal without the permission of the user of the second terminal.

<Third Modification (1)>
For example and not by way of limitation, a malicious user of a sender account may intentionally send electronic money with notification in an attempt to learn information, such as the location, of a user of a destination account.
Also, by way of example and not limitation, in the parent-child example described above, the child who receives the electronic money with notification may end up sending the electronic money with notification to a complete stranger through a tipping function, which is a type of gifting function.

Therefore, it is also possible to inform the destination account before at least a portion of the notification-attached electronic money is used by the user of the destination account that a notification will be sent to the terminal 20 of the user of the destination account when the notification-attached electronic money is used.

FIG. 3D is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of Figure 3-4 shows a code payment screen displayed on the display unit 24 of the terminal 20A of User A, who is the user of the destination account.
When the wallet code information displayed in the wallet code information display area WCR1 is read by the store code reader device 50, as an example and not a limitation, as shown in the center of Figure 3-4, notification-attached electronic money usage confirmation information NE31 is displayed, superimposed on the wallet code information display area WCR1 of the code payment screen, to inform the user of the destination account (in this example, user A.A's account) that at least a portion of the notification-attached electronic money has been used by the destination account, and a notification of the use of the notification-attached electronic money has been sent to the destination account (in this example, user B.B's account).

Specifically, in this example, the text "This payment will be notified to B.B. Are you sure?" is displayed along with a "Pay" button BT33 for accepting the use of the notification-attached electronic money and making the payment, and a "Cancel" button T34 for rejecting the use of the notification-attached electronic money and stopping the payment.

When the "Pay" button BT33 is tapped, the payment process is performed by the server 10. Then, the user of the remittance source account and the user of the notification destination account, User B. On the display unit 24 of User B's terminal 20B, the screen shown on the right side of FIG. 3-4 is displayed, by way of example and not of limitation.
This screen is a notification screen of the payment application, and on the left side of the notification area, electronic money remittance result information NR2 with notification indicating that remittance of electronic money with notification from user B.B to user A.A has been completed is displayed below electronic money use information NU3 with notification indicating that electronic money with notification has been used by user A.A.

FIG. 3-5 is a flowchart showing an example of the flow of processes executed by each device in this modified example.
After S120, when the control unit 11 of the server 10 receives wallet payment request information from the terminal 20A, it transmits notification-attached electronic money use confirmation information to the terminal 20A via the communication I/F 14 (S340). This notification-attached electronic money use confirmation information can include, by way of example and not limitation, information informing (notifying) the user A.A that a notification of electronic money use with notification is to be sent to the notification destination account (user B.B's account in this example) when at least a portion of the notification-attached electronic money is used by the remittance destination account (user A.A's account in this example).

After A120, when the control unit 21 of the terminal 20A receives notification-attached electronic money use confirmation information from the server 10, it determines whether or not to use the notification-attached electronic money (A340), for example by determining whether or not an input permitting the use of the notification-attached electronic money has been made to the input/output unit 23. If it is determined not to use the notification-attached electronic money (A340: NO), the control unit 21 of the terminal 20A ends the process.

On the other hand, if it is determined that the notification-attached electronic money is to be used (A340: YES), the control unit 21 of the terminal 20A transmits notification-attached electronic money use consent information to the server 10 via the communication I/F 22 (A350).

After S340, the control unit 11 of the server 10 determines whether or not notification-attached electronic money use consent information has been received from the terminal 20A via the communication I/F 14 (S350). If it is determined that notification-attached electronic money use consent information has not been received (S350: NO), the control unit 11 of the server 10 ends the process.

On the other hand, if it is determined that notification-attached electronic money use consent information has been received (S350: YES), the control unit 11 of the server 10 proceeds to S130.

In addition, if the setting is such that the notification-attached electronic money balance is used preferentially for making payments, as described above, the control unit 11 of the server 10 can execute step S340 after step S120.
However, when the setting is such that the regular electronic money balance is given priority for making a payment, unless the control unit 11 of the server 10 knows the payment amount, it cannot determine whether or not to make the payment using the notification-attached electronic money balance instead of the regular electronic money balance, and therefore cannot determine whether or not it is necessary to send notification-attached electronic money usage confirmation information to the terminal 20A.

As a non-limiting example, the control unit 11 of the server 10 may transmit notification-attached electronic money use confirmation information to the terminal 20A along with the wallet code information in step S130. Then, before executing step S140 in FIG. 1-13, the control unit 11 may confirm with the terminal 20A whether or not the payment using the notification-attached electronic money balance is permitted.

Also, as a non-limiting example, before the control unit 11 of the server 10 executes step S140 in FIG. 1-13, it determines whether or not the notification-attached electronic money balance will be used for the payment, based on the payment amount included in the payment request information received from the store POS system 40. Then, if it determines that the notification-attached electronic money balance will be used for the payment, it may send notification-attached electronic money use confirmation information to the terminal 20A to confirm with the terminal 20A whether or not the payment using the notification-attached electronic money balance is permitted.

This modified example shows a configuration in which the server 10 transmits notification-attached electronic money usage confirmation information (not limited to, but an example of third information regarding a notification to be sent to a third terminal before at least a portion of the first electronic currency is used by a user of a second terminal) to the terminal 20 of the user of the destination account before at least a portion of the notification-attached electronic money is used by the user of the destination account.
As an example of the effect of this modified configuration, the user of the second terminal can be informed that a notification will be sent to the third terminal before at least a portion of the first electronic currency is used by the user of the second terminal.

<Third Modification (2)>
For example and not by way of limitation, a user of a destination account may not want notifications to be sent to the user of the destination account.
Therefore, if the user of the remittance destination account has set up not to receive electronic money with notification, electronic money with notification may not be associated with the remittance destination account. In this case, the user of the remittance source account may be notified that remittance with notification is not possible.

Here, the following are examples of settings for not accepting remittance of electronic money with notification (settings for refusing to accept electronic money with notification).
(S1) Bulk rejection (S2) Block (S3) Blacklist (S4) Whitelist

(S1) Bulk rejection can be, for example and not by way of limitation, set to not accept electronic money transfers with notification from all accounts (or all users).

(S2) The block may be configured, by way of example and not limitation, to not accept electronic money transfers with notifications from a particular account (or a particular user).

(S3) As a non-limiting example, the blacklist may be set by default to allow receipt of electronic money transfers with notifications from all accounts, but it may be possible to set the blacklist so that electronic money transfers with notifications from specific accounts are not accepted.

(S4) As a non-limiting example, the whitelist may be set by default to not accept electronic money transfers with notifications from all accounts, but it may be possible to set the whitelist to accept electronic money transfers with notifications from specific accounts.

In addition, the (S3) blacklist and (S4) whitelist can also be considered as a method of implementing the (S2) block.
Specifically, by way of example and not limitation, (S2) blocking can be achieved by adding a particular account to a blacklist.
Conversely, by way of example and not limitation, blocking (S2) can also be achieved by deleting a particular account from the whitelist.

Also, (S1) blanket rejection can be considered a type of (S2) blocking, meaning blocking all accounts.

FIG. 3-6 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of FIG. 3-6 is a diagram showing an example of a wallet setting screen of the payment application displayed on the display unit 24 of the terminal 20A, and displays, as examples, but not limited to, settings related to electronic money, such as an item "Automatically charge" for automatically charging electronic money and an item "Refuse to receive electronic money with notification" for refusing to receive electronic money with notification from all accounts. A slide button is associated with the right side of each item, and the item can be set to "ON" by tapping or sliding the slide button. In this example, the state in which the item "Refuse to receive electronic money with notification" is set to "ON" is shown. This is an example of a screen diagram of the above-mentioned (S1) blanket refusal.

In this example, the above item "Reject receipt of electronic money with notification" may be replaced with a refusal to receive electronic money with notification from the account of user B. In this case, the above-mentioned (S2) block is executed.
Also, a screen image may be configured that allows the account of user B.B. to be added to a blacklist or deleted from a whitelist. In this case, it becomes the above-mentioned (S3) blacklist and (S4) whitelist.

In this state, when the “Settings” button BT35 at the bottom of the screen is tapped, the screen shown in the center of FIG. 3-6 is displayed, by way of example and not limitation.
This screen is a diagram showing an example of a remittance screen displayed on the display unit 24 of the terminal 20B of user B, who is the user of the remittance source account, and is the same as the screen on the right side of Figure 1-9. When the "Remit" button BT2 is tapped on this screen, the notification screen of the payment application displayed on the display unit 24 of the terminal 20B will display, by way of example and not limitation, the display shown on the right side of Figure 3-6.

Specifically, on the left side of the notification area, notification-attached electronic money receipt refusal information NF31 is displayed, which indicates that receipt of the notification-attached electronic money has been refused by user A.A based on the (S1) blanket refusal setting in the screen diagram on the left side of FIG. 3-1.
This electronic money receipt refusal information with notification NF31 displays, by way of example and not limitation, the date and time when this electronic money receipt refusal information with notification was sent by server 10, the text "Failed to transfer electronic money with notification to A.A.", the text "(A.A.'s wallet settings have refused to accept electronic money with notification)," the amount attempted to be transferred (in this example, "1,000 yen"), and a ">Check details" button.

In order to distinguish it from the above-mentioned electronic money receipt refusal information with notification, in this modification, for the sake of convenience, it is called "electronic money rejection information with notification".
On the other hand, a consistent terminology may be easier for users of the payment application to understand, so the example display screen uses the term "rejected."

FIG. 3-7 is a flowchart showing an example of the flow of processes executed by each device in this modified example.
First, the control unit 21 of the terminal 20A transmits notification-attached electronic money reception refusal setting information to the server 10 via the communication I/F 22 based on a user input to the input/output unit 23 to refuse reception of notification-attached electronic money (A360).

In response to this, the control unit 11 of the server 10 performs a notification-attached electronic money receipt refusal setting process (S360). In this case, the control unit 11 can, by way of example and not limitation, set the sender account (in this example, the account of user B.B.) to be blocked. The server 10 can prevent the blocked sender account from transferring notification-attached electronic money to the destination account.

Thereafter, the control unit 11 of the server 10 judges whether or not the remittance destination account has been set to refuse receipt of the notification-attached electronic money (S370), and if it is determined that the setting has been set (S370: YES), it transmits notification-attached electronic money refusal information to the terminal 20B via the communication I/F 14 (S380).Then, the control unit 11 of the server 10 proceeds to the process of S130.
On the other hand, if it is determined that the setting has not been completed (S370: NO), the control unit 11 of the server 10 advances the process to S110.

After B120, the control unit 21 of the terminal 20B determines whether or not electronic money receipt refusal information with notification has been received from the server 10 via the communication I/F 22 (B310), and if it is determined that the electronic money receipt refusal information with notification has been received (B310: YES), causes the display unit 24 to display the electronic money receipt refusal information with notification (B320).Then, the control unit 21 of the terminal 20B moves the process to B140 in FIG.
On the other hand, if it is determined that the signal has not been received (B310; NO), the control unit 21 of the terminal 20B advances the process to B130.

After A360, the control unit 21 of the terminal 20A determines whether or not electronic money remittance result information with notification has been received from the server 10 via the communication I/F 22 (A370), and if it is determined that it has been received (A370: YES), the process proceeds to A110.
On the other hand, if it is determined that the signal has not been received (A370: NO), the control unit 21 of the terminal 20A advances the process to A120.

This modified example shows a configuration in which, when the server 10 performs electronic money receipt refusal setting processing with notification based on receiving electronic money receipt refusal setting information with notification from the terminal 20 of the user of the destination account (not limiting, an example of a case where the user of the second terminal has set up not to receive remittances for which a notification is set), the server 10 does not perform electronic money receipt remittance processing with notification (not limiting, an example of associating the first electronic currency with the user of the second terminal), but instead sends electronic money receipt refusal information with notification (not limiting, an example of remittance impossible information indicating that remittance to the user of the second terminal is not possible) to the terminal 20 of the user of the remittance account (not limiting, an example of the first terminal).
As an example of the effect of the modified example obtained by such a configuration, if the user of the second terminal has set up the device not to receive remittances for which notifications are set up, the first electronic currency can be made not to be associated with the user of the second terminal, and the user of the first terminal can be informed that remittances cannot be made.

In this case, the setting for the user of the destination account not to receive a remittance for which notification has been set may include a setting for blocking the user of the source account.
As an example of the effect of the modified example obtained by such a configuration, if the user of the second terminal does not want to receive a remittance for which a notification has been set, the user of the first terminal can be blocked, thereby avoiding the receipt of a remittance for which a notification has been set from the user of the first terminal.

In this case, the setting for the user of the remittance destination account not to receive remittances for which notifications are set may include a setting to block users of all accounts.
As an example of the effect of this modified configuration, if a user of the second terminal does not want to receive a remittance for which a notification has been set, all users can be blocked so that they will not receive a remittance for which a notification has been set from a user of the first terminal.

<Fourth Example>
The fourth embodiment is an embodiment that distinguishes between electronic money with notification and electronic money associated with the user of the remittance destination account for which notification is not set.

The contents described in the fourth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Data structure>
FIG. 4A is a diagram showing an example of the data configuration of the account management database 155E, which is an example of the account management database 155 in this embodiment.
In each account management data of this account management database 155E, the notification-attached electronic money management data is stored in association with, by way of example and not limitation, a remittance management ID, a remitter ID, a notification destination ID, the notifier name, and a notification-attached electronic money balance.

Unlike the account management data described above, the remitter ID is additionally stored. This allows the server 10 to distinguish and manage the remitter account and the notification destination account.

<Display screen>
4B and 4C are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of Fig. 4-2 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A, which displays electronic money remittance result information NR41 with notification indicating that electronic money with notification remitted from user B.B to user A.A has been received.

This notification-attached electronic money remittance result information NR41 displays, by way of example and not limitation, the amount remitted (amount received), a "Receive" icon, an illustration indicating that user B.B. will be notified when the received notification-attached electronic money is used, the date and time this information was sent by server 10, the text "Electronic money with notification has been received (usage status will be notified to B.B.)," an illustration indicating that the remittance is from user B.B. to user A.A, and a ">Check details" button.

Note that since user A.A has already received the electronic money with notification, unlike the electronic money with notification receipt confirmation information NC31 shown on the left side of Figure 3-1, the electronic money with notification remittance result information NR41 uses the expression "electronic money with notification has been received" as an example and not a limitation.

The center of Fig. 4-2 shows the state in which the main menu screen of the payment application is subsequently displayed. The word "Balance" is displayed in the balance display area BR2 at the top of the screen, and below that, the balance corresponding to the notification-attached electronic money of "1,000 yen" transferred from user B.B to user A.A is displayed as the notification-attached electronic money balance, together with the word "notification-attached" and an illustration indicating that a notification will be sent to user B.B.
Below that, the regular electronic money balance is displayed along with the words "No notification" and a charge button CBT.

When the "Code Payment" icon IC2 is tapped on this screen, a code payment screen of the payment application is displayed, as shown on the right side of FIG. 4-2, by way of example and not by way of limitation.
On this code payment screen, the area in which information regarding the balance in the wallet code information display area WCR1 is displayed displays information for selecting whether to make a payment from the notification-attached electronic money balance or the regular electronic money balance.

Specifically, the word "with notification" for making a payment from the "electronic money balance with notification," the electronic money balance with notification (in this example, "1,000 yen"), and an illustration indicating that a notification will be sent to user B.B when a payment is made from the balance are displayed.
Also displayed below that are the words "No notification" to allow payment to be made from the "normal electronic money balance," the normal electronic money balance (in this example, "500 yen"), and a charge button CBT for charging electronic money to the normal electronic money balance.

To the left of the words "with notification" and "without notification" are radio buttons, and the user can select whether to make a payment from the electronic money balance with notification or the normal electronic money balance by tapping the corresponding radio button. In this example, electronic money with notification is shown as being selected. When a payment is made in this state, payment result information is displayed as shown on the left side of Figure 4-3, by way of example and not limitation.

In this case, the notification screen of the payment application on the display unit 24 of the terminal 20B will display, by way of example and not limitation, something like that shown on the right side of FIG. 4-3.
Specifically, as an example and not by way of limitation, electronic money usage information with notification NU3 is displayed below electronic money remittance result information with notification NR42, which includes the remitted amount (in this example, "1,000 yen"), a "remittance" icon, an illustration indicating that the remitted electronic money with notification is used and a notification is given to user B.B, the date and time of transmission by server 10 of electronic money remittance result information with notification, the text "Electronic money with notification has been remitted (usage status will be notified)," an illustration indicating that the remittance is from user B.B to user A.A, and a ">Check details" button.

<Processing>
In the processing of this embodiment, in the example of the screen diagram above, but not limited thereto, by way of example and not limitation, in step S120 of FIG. 1-12, the control unit 11 of the server 10 can transmit the remittance management ID of the notification-attached electronic money management data contained in the account management data of the account of user A.A in the account management database 155E to the terminal 20A together with the remittance result information. By doing so, it becomes possible to specify the remittance management ID on the terminal 20A, and as an example and not limiting, the user can select the notification-attached electronic money balance with the account of user B.B as the remitter ID and the account of user B.B as the notification destination ID, as shown in the screen on the right side of FIG. 4-2.

In addition, after the electronic money balance to be used for payment is selected by the user, in step A120 of FIG. 1-12 or before or after that, the control unit 21 of the terminal 20A can transmit a remittance management ID corresponding to the selected electronic money balance with notification to the server 10. In this way, the server 10 can identify the electronic money balance with notification selected by the user.

<Effects of the Fourth Embodiment>
This embodiment shows a configuration in which the control unit 11 controls the server 10 to distinguish and store electronic money with notification (not limited to, but an example of a first electronic currency with a notification set) and normal electronic money (not limited to, but an example of a second electronic currency associated with a user of a second terminal).
As an example of the effect of an embodiment obtained by such a configuration, it is possible to manage separately a first electronic currency for which a notification has been set and a second electronic currency for which a notification has not been set and which is associated with a user of a second terminal, thereby improving user convenience.

<Fourth Modification (1)>
As described above, the account management data in FIG. 2-4 enables the server 10 to distinguish and manage the remittance source account and the notification destination account.
This allows the user of the remittance source account to set an account other than his/her own account as the notification destination account, for example and not by way of limitation. In this case, if one user can only have one account, the user of the notification destination account will be a user other than the user of the remittance source account. As a result, it is possible to set up so that the notification of electronic money usage with notification is sent to a terminal 20 (= the terminal 20 of the user of the notification destination account) other than the terminal 20 of the user of the remittance source account.

In the non-limiting parent-child example described above, the mother's account is the sender account, and the mother's terminal 20 is the first terminal.
Also, by way of example and not limitation, the child's account may be the destination account, in which case the child's terminal 20 is the second terminal.
Also, as a non-limiting example, the father's account is set as the notification destination account, in which case the father's terminal 20 becomes the third terminal.
In this case, when the child uses the electronic money with notification transferred from the mother through his/her own account to make a purchase or the like, a notification can be sent to the father's account.

4-4 and 4-5 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of Fig. 4-4 is a remittance screen of the payment application displayed on the display unit 24 of terminal 20B, and in the area at the bottom of the screen for setting the user of the remittance destination account, there are provided a slide button marked "Receive usage notification" for setting so that an electronic money usage notification with notification is sent to oneself, and a slide button marked "Send usage notification to other users" for setting so that an electronic money usage notification with notification is sent to other users. In this example, the slide button marked "Send usage notification to other users" is shown in the "ON" state.

Below that is a "Set notification destination" button BT36 for setting a notification destination account. Also, because a notification destination account has not yet been set, the "Transfer" button BT2 at the bottom of the screen is displayed in a grayed-out state, and tapping it will not transfer money.

When the “Set notification destination” button BT36 is tapped in this state, the display shown in the center of FIG. 4-4 is displayed, for example and not for limitation.
This screen is a remittance screen, just like the one on the left side of Figure 4-4, but at the top of the screen, the words "Please set the notification destination" are displayed, and below that there is a search box for searching for the notification destination account (that user) by phone number.
Below that, destination accounts (users) that have been set as notification destinations in the past are displayed as history, and in this example, an icon image of user C.C. and his/her user name are displayed. Next to that is associated a check box, which is configured to allow this user to be set as a notification destination by checking it "ON." In this example, the state in which the check box for user C.C. is "ON" is shown.

In this state, when the "Settings" button BT37 at the bottom of the screen is tapped, the display shown on the right side of FIG. 4-4 is displayed, by way of example and not limitation.
This screen corresponds to the screen on the left side of Figure 4-4, but because the notification account was set on the screen in the center of Figure 4-4, the icon image of user C.C., who was set as the notification destination on the screen in the center of Figure 4-4, and his/her user name are displayed together with the word "Notification destination."

In addition, with the notification account being set, the grayed-out state of the "Transfer" button BT2 is released. When the "Transfer" button BT2 is tapped in this state, the server 10 executes the notification-attached electronic money transfer process, and the notification-attached electronic money is transferred from user B.B to user A.A.

The left side of Figure 4-5 shows an example of a screen displayed on the display unit 24 of the terminal 20A of User A, who is the user of the destination account in this case.
This screen is a notification screen of the payment application, and electronic money remittance result information with notification NR43 is displayed on the left side of the notification area.

This notification-attached electronic money remittance result information NR43 displays, by way of example and not limitation, the remitted amount (received amount), a "Receive" icon, an illustration indicating that user C.C. will be notified when the received notification-attached electronic money is used, the date and time this information was sent by server 10, the text "Notification-attached electronic money has been received (usage status will be notified to C.C.)," an illustration indicating that the remittance is from user B.B. to user A.A., and a ">Check details" button.

After that, when the notification-enabled electronic money is used by user A.A, a payment result screen of the payment application, as shown in the center of FIG. 4-5, is displayed on the display unit 24 of terminal 20A, by way of example and not limitation.

In this case, the notification-attached electronic money usage information is sent to the terminal 20C of the user C.C., who has been set as the notification destination. As a result, the display unit 24 of the terminal 20C displays, by way of example and not limitation, the display shown on the right side of FIG.
This screen is a notification screen of the payment application, and on the left side of the notification area, notification-attached electronic money usage information NU43 is displayed. Specifically, information is displayed indicating that notification-attached electronic money transferred from user B.B to user A.A has been used by user A.A.

In this modified example, the notification-attached electronic money notification setting shows a configuration including a setting related to sending a notification to a terminal 20 different from the terminal 20 of the user of the remittance source account.
As an example of the effect of this modified example obtained by such a configuration, it is possible to notify a user of a third terminal different from the first terminal that at least a portion of the first electronic currency has been used by a user of a second terminal.

<Fourth Modification (2)>
In the fourth embodiment, as shown in the screen on the right side of Figure 4-2, an example was shown in which a payment is made by selecting either electronic money with notification transferred from a single user or regular electronic money, but the present invention is not limited to this.
The user may be allowed to select either electronic money with notification sent from two or more users or ordinary electronic money.

4-6 and 4-7 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of FIG. 4-6 is a notification screen of the payment application displayed on the display unit 24 of the terminal 20A, and on the left side of the notification area, two pieces of electronic money remittance result information with notifications are displayed.

The electronic money remittance result information with notification NR45 with the older time is electronic money remittance result information with notification of "1,000 yen" remitted from user B.B to user A.A, and user B.B, the user of the remitter's account, is set as the notification destination.
The electronic money remittance result information with notification NR46 with the newer time is electronic money remittance result information with notification of "2,000 yen" remitted from user C.C to user A.A, and user C.C, who is the user of the remitter's account, is set as the notification destination.

The right side of Figure 4-6 shows the state in which the main menu screen of the payment application is then displayed. The word "Balance" is displayed in the balance display area BR2 at the top of the screen, and two notification-attached electronic money balances are displayed below that.
Specifically, the balance corresponding to the notification-attached electronic money of "1,000 yen" transferred from user B.B to user A.A is displayed together with the characters "with notification" and an illustration indicating that a notification will be sent to user B.B. Similarly, the balance corresponding to the notification-attached electronic money of "2,000 yen" transferred from user C.C to user A.A is displayed together with the characters "with notification" and an illustration indicating that a notification will be sent to user C.C.
Below that, the normal electronic money balance (in this example, "500 yen") and a charge button CBT are displayed.

When the "Pay Code" icon IC2 is tapped on this screen, a pay code screen of the payment application is displayed, as shown on the left side of FIG. 4-7, by way of example and not limitation.
On this code payment screen, in the area in which information on the balance is displayed in the wallet code information display area WCR1, information for selecting from which balance to make a payment: the balance of the notification-attached electronic money remitted from user B.B, the balance of the notification-attached electronic money remitted from user C.C, or the normal electronic money balance is displayed.

Specifically, the text "with notification" is displayed to indicate that payment will be made from the balance of the notification-attached electronic money remitted from user B.B, the balance of the notification-attached electronic money (in this example, "1,000 yen"), and an illustration is displayed indicating that user B.B will be notified when payment is made from the balance.
Similarly, the word "with notification" for making a payment from the balance of the electronic money with notification remitted from user C.C, the balance of the electronic money with notification ("2,000 yen" in this example), and an illustration indicating that a notification will be sent to user C.C when a payment is made from the balance are displayed.
Also displayed below that are the words "No notification" to allow payment to be made from the "normal electronic money balance," the normal electronic money balance (in this example, "500 yen"), and a charge button CBT for charging electronic money to the normal electronic money balance.

A radio button is provided next to each of them, and the corresponding balance can be selected based on the operation of the corresponding radio button. In this example, the balance of the electronic money with notification transferred from user C.C. is shown to be selected. When a payment is made in this state, the payment result information shown in the center of Figure 4-7 is displayed, as an example and not a limitation.

The right side of FIG. 4-7 shows an example of a notification screen displayed on the display unit 24 of the terminal 20C of user C.C., who is the user of the notification destination account in this case.
On the left side of the notification area, electronic money remittance result information with notification NR48 is displayed. This electronic money remittance result information with notification NR48 includes, by way of example and not limitation, the remittance amount (in this example, "2,000 yen"), the remittance date and time, a "Remit" icon indicating that the electronic money with notification is the remitter, illustrated information of the remitter and the remitter destination, and a ">Check details" button.

In addition, based on the fact that the electronic money with notification sent to user A.A has been used, electronic money with notification usage information NU48 is displayed below electronic money with notification remittance result information NR48.

<Fourth Modification (3)>
In the above embodiment, two or more accounts may be set as notification destination accounts.
In the non-limiting parent-child example described above, the mother's account is the sender account, and the mother's terminal 20 is the first terminal.
Also, by way of example and not limitation, the child's account may be the destination account, in which case the child's terminal 20 is the second terminal.
Also, as a non-limiting example, two accounts, a mother's account and a father's account, are set as notification destination accounts. In this case, the two terminals 20, the mother's terminal 20 and the father's terminal 20, become the third terminal.
In this case, when the child uses the electronic money with notification transferred from the mother through his/her own account to make a purchase or the like, a notification can be sent to both the mother's account and the father's account.

<Fourth Modification (4)>
In the fourth embodiment, when a payment is about to be made by code payment or the like, information indicating that the notification-attached electronic money is about to be used (hereinafter referred to as "notification-attached electronic money use intention information") may be sent to the terminal 20 of the user of the notification destination account, thereby notifying the notification destination account that the notification-attached electronic money is about to be used.

Specifically, by way of example and not limitation, when the radio button associated with the notification-attached electronic money balance displayed in the wallet code information display area WCR1 on the code payment screen on the right side of FIG. 4-2 is turned "ON," the control unit 21 of terminal 20A sends information indicating that the notification-attached electronic money balance has been selected to the server 10 via the communication I/F 22. In response, the control unit 11 of the server 10 sends notification-attached electronic money usage intention information to the terminal 20 of the user of the notification destination account via the communication I/F 14.

<Fourth Modification (5)>
In the various embodiments described above, the notification-accompanying electronic money remittance setting process is performed by the remitter account, but this is not limiting.
As explained in the fourth embodiment, it is possible for the remittance source account and the notification destination account to be different.

As a non-limiting example, if one user can have multiple accounts, the first account of this user is the sender account and the second account of this user is the notification destination account. Then, the electronic money remittance with notification setting may or may not be performed by the second account of this user (notification destination account). In this case, the electronic money remittance with notification setting process can be performed on the terminal 20 of this user.

Also, as a non-limiting example, if one user can only own one account, the user of the notification destination account can be a different user from the user of the remitter account. In this case, too, the notification-attached electronic money remittance setting may or may not be performed by the account of the different user (notification destination account). In this case, the notification-attached electronic money remittance setting process can be performed on the terminal 20 of this different user.

Fifth Example
The fifth embodiment relates to a case where at least a part of the notification-attached electronic money is withdrawn to a bank account, etc. The notification-attached electronic money withdrawn to a bank account, etc. can be withdrawn as cash.

The contents described in the fifth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Display screen>
5-1 and 5-2 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of Fig. 5-1 is a diagram showing an example of a main menu screen of a payment application displayed on the display unit 24 of the terminal 20A, and in the balance display area BR2, the notification-attached electronic money balance, the normal electronic money balance, and the charge button CBT are displayed, in which user B.B is the user of the notification destination account.

In this example, the "Withdrawal" icon IC3, one of the multiple function icons displayed below it, is shown as having been tapped. Then, by way of example and not limitation, the screen in the center of Figure 5-1 is displayed.

This screen is a withdrawal screen for the payment application, and displays the message "Please specify the withdrawal destination" along with the bank account registered by user A. A (in this example, "LL Bank, Regular Account, XXXXXX"). Next to the bank account is a radio button, and by turning the radio button "ON," the user can specify that bank account as the withdrawal destination. In this example, the radio button for "LL Bank, Regular Account, XXXXXX" is shown turned "ON."

Below that, along with the words "Please specify the withdrawal source balance", information regarding the notification-attached electronic money balance and information regarding the regular electronic money balance are displayed. By turning "ON" the radio button displayed next to "With notification", the user can specify the notification-attached electronic money balance as the withdrawal source balance, and by turning "ON" the radio button displayed next to "No notification", the user can specify the regular electronic money balance as the withdrawal source balance. In this example, the radio button for the notification-attached electronic money balance of "1,000 yen", which is set to be notified to user B.B, is shown to be in the "ON" state.

In this state, when the "Confirm" button BT51 at the bottom of the screen is tapped, the withdrawal destination and withdrawal source balance are confirmed. Then, as an example and not a limitation, the screen on the right side of Figure 5-1 is displayed.

This screen is the remittance screen of the payment application, and in this example, it shows the state in which "1,000 yen" has been entered, which is the entire amount of the electronic money balance with notification determined as described above. In this state, when the "Withdraw" button BT52 at the bottom of the screen is tapped, the server 10 performs the withdrawal process. As a result, the display unit 24 of the terminal 20A displays the image shown on the left side of Figure 5-2, which is an example and not a limitation.

This screen is the notification screen of the payment application, and withdrawal result information WR51 indicating the withdrawal result is displayed below electronic money remittance result information with notification NR41 on the left side of the notification area. Specifically, the withdrawal amount (in this example, "1,000 yen") is displayed along with the word "Amount," and next to it is a "Withdrawal" icon indicating that it is a withdrawal. Also displayed below that are the withdrawal date and time, the withdrawal destination, and a ">Check details" button.

The right side of Fig. 5-2 shows an example of a notification screen displayed on the display unit 24 of the terminal 20B of user B, who is the user of the notification destination account in this case.
On the left side of the notification area, under electronic money remittance result information with notification NR51, electronic money withdrawal information with notification NW51 indicating that electronic money with notification has been withdrawn by user A.A. is displayed. Specifically, along with the withdrawal date and time, the text "The electronic money remitted to A.A. has been withdrawn" is displayed, and below that, the withdrawal amount (in this example, "1,000 yen") and a ">Check details" button are displayed.

<Processing>
1-12, 1-13, and other various flowcharts, the control unit 21 of the terminal 20A, by way of example and not limitation, after step A140, determines whether or not a user input requesting a withdrawal has been made to the input/output unit 23. Then, if it is determined that a withdrawal has been made, the control unit 21 transmits withdrawal request information including, by way of example and not limitation, an application ID, a withdrawal destination, a withdrawal source balance, and a withdrawal request amount to the server 10 via the communication I/F 22.

As a non-limiting example, after step S170, the control unit 11 of the server 10 determines whether or not withdrawal request information has been received from the terminal 20A via the communication I/F 14. If it is determined that the withdrawal request information has been received, the control unit 11 performs the withdrawal process. Specifically, the control unit 11 subtracts the withdrawal request amount from the withdrawal source balance in the account management data for the application ID included in the received withdrawal request information. Then, an electronic money transfer is performed to send the withdrawal request amount to the server of the financial institution to which the withdrawal is to be made (the financial institution's server).

Thereafter, the control unit 11 of the server 10 transmits withdrawal completion information to the terminal 20A via the communication I/F 14.
Furthermore, when the withdrawal source balance is an electronic money balance with notification, the control unit 11 of the server 10 transmits electronic money withdrawal information with notification to the terminal 20B via the communication I/F 14.

<Effects of the Fifth Example>
This embodiment shows a configuration in which, when at least a portion of the notification-attached electronic money is withdrawn by the user of the destination account, the server 10 transmits notification-attached electronic money withdrawal information to the terminal 20 of the user of the destination account via the communication I/F 14.
As an example of the effect of an embodiment obtained by such a configuration, when the user of the second terminal withdraws at least a portion of the first electronic currency, the user of the third terminal can be notified of the details thereof.

If it is possible to withdraw electronic money with notifications, it can be thought of as disabling the notification setting, and as a result, it can be thought of as not sending notifications to the notification destination account even if the money is withdrawn. As a result, it can be thought of as allowing the user of the remittance destination account to use it freely.
However, in this embodiment, when notification-attached electronic money is withdrawn, a notification is sent to the notification destination account, thereby making it possible to prevent the above-mentioned situation.

<Fifth Modification (1)>
In view of the above problem, as a method different from that of the fifth embodiment, it is possible to make it impossible to withdraw electronic money with notification.

FIG. 5C is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this modified example.
The screens on the left side and center of FIG. 5-3 are similar to the screens on the left side and center of FIG. 5-1, respectively.
In this modified example, when the "OK" button BT51 is tapped on the screen in the center of FIG. 5-3, the display on the right side of FIG. 5-3 is shown, by way of example and not limitation.

This screen is the remittance screen of the payment application, but it is displayed differently from the right side of Figure 5-1. Specifically, as electronic money withdrawal unavailability information with notification, the text "This balance cannot be withdrawn" is displayed along with information about the withdrawal source balance specified by User A.A on the screen in the center of Figure 5-3.

In the process of this modified example, in the process of the various flowcharts described above in FIG. 1-12, FIG. 1-13, etc., the control unit 21 of the terminal 20A determines, by way of example and not limitation, after step A140, whether or not a user input has been made to the input/output unit 23 to request a withdrawal. Then, if it is determined that a withdrawal has been made, by way of example and not limitation, the control unit 21 transmits withdrawal request information including, by way of example and not limitation, the application ID, the withdrawal destination, the withdrawal source balance, and the withdrawal request amount to the server 10 via the communication I/F 22.

As an example, but not by way of limitation, after step S170, the control unit 11 of the server 10 determines whether or not withdrawal request information has been received from the terminal 20A via the communication I/F 14. If it is determined that the withdrawal request information has been received, it determines whether or not the withdrawal source balance included in the received withdrawal request information is an electronic money balance with notification. If it is determined that the withdrawal source balance is an electronic money balance with notification, it transmits electronic money withdrawal failure information with notification to the terminal 20A via the communication I/F 14.

The control unit 11 of the server 10 may be configured to send the notification-attached electronic money withdrawal impossibility information to the terminal 20B of the user of the remittance source account in addition to the terminal 20A.

In addition, when the control unit 11 of the server 10 receives the withdrawal request information of the electronic money balance with notification, the control unit 11 may transmit inquiry information to the terminal 20B of the user of the remittance source account as to whether or not to approve the withdrawal. In this case, as an example and not a limitation, when the user of the remittance source account approves the withdrawal based on the input (user operation, etc.) to the input/output unit 23 of the terminal 20B, the withdrawal process of the electronic money balance with notification is executed.

This modified example shows a configuration in which, when the server 10 receives withdrawal request information for withdrawing at least a portion of the electronic money with notification from the terminal 20 of the user of the destination account, it transmits electronic money withdrawal failure information with notification (not limited to this, but an example of withdrawal failure information) to the terminal 20 of the user of the destination account.
As an example of an effect of an embodiment obtained by such a configuration, when information regarding the withdrawal of at least a portion of the first electronic currency by the second terminal is received by the communication unit, the user of the second terminal can be informed that withdrawal is not possible.

<Fifth Modification (2)>
In the above embodiment, a notification is sent to the notification destination account when a withdrawal is made to a bank account, etc., but this is not limited to this. As a non-limiting example, if the payment application is equipped with a cash withdrawal function from an automated teller machine (ATM) or the like, when the electronic money balance with notification is withdrawn using an ATM, a notification may be sent to the terminal 20B of the user of the notification destination account.

As in the fifth modified example (1), when the terminal 20A of the remittance destination account attempts to withdraw funds using an ATM, the control unit 11 of the server 10 may transmit electronic money withdrawal failure information with notification to the terminal 20A.

Sixth Example
A sixth embodiment is one that utilizes a messaging application instead of or in addition to a payment application.

The contents described in the sixth embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

By way of example and not limitation, the messaging application can be configured to allow one-on-one chat between accounts registered as friends on the server 10. Also, by way of example and not limitation, a group can be formed containing two or more accounts, and group chat can be performed between the accounts included in the group.

<Display screen>
FIG. 6A is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of Fig. 6-1 is a screen of a talk room (not limited to, but an example of a chat room) of a messaging application (not limited to, but an example of a chat application), and in the center of the top of the screen, the characters "Messaging App" are displayed as the name of the messaging application. Also, in the top right of the screen, an icon image and a user name (user A.A in this example) in the messaging application of the user of this terminal 20A are displayed.

Below that is a talk room name display area showing the name of the talk room in the messaging application; in this example, the talk room name is "<B.B," which includes the letters "B.B," indicating that the talk room is a one-to-one talk room with user B.B, and a "<" button for returning to the previous screen.

Below that is a talk area. In the talk area, as a non-limiting example, the content sent by you is displayed on the right side of the screen, and the content sent by the other party is displayed on the left side of the screen, with the contents displayed chronologically from oldest to newest downwards. Also, as a non-limiting example, the content sent by you is displayed in a speech bubble at the right edge of the talk area, and the content sent by the other party is displayed in a speech bubble at the left edge of the talk area in association with that user's icon image and username.

In this example, on the left side of the talk area, text content TC61, which is sent from user B.B, encouraging the purchase of a reference book, and electronic money remittance result content NRC61, which is sent from a payment application, are displayed.

The notification-attached electronic money remittance result content NRC61 is, by way of example and not limitation, a content indicating that notification-attached electronic money of "1,000 yen" remitted from user B.B has been received, and indicates that user B.B. is set as the notification destination account.
Also, on the right side of the talk area, text content TC62 is displayed, which expresses gratitude to user A.A.

In this state, a function for making a code payment using a payment application is called based on user input (not shown), and the payment process is executed using the electronic money with notification transferred from user B.B through the code payment described above. As a result, the screen in the center of FIG. 6-1 is displayed, not as a limitation, but as an example. In this example screen, a payment result information display area PWR that displays payment result information is displayed rising from the bottom of the talk room screen so as to overlap part of the talk area on the talk room screen on the left side of FIG. 6-1.

The right side of FIG. 6-1 shows an example of a talk room screen of a messaging application displayed on the display unit 24 of the terminal 20B in this case.
This talk room screen is a one-to-one talk room screen with the talk partner being user A.A., and on the left side of the talk area, electronic money remittance result content with notification NRC62, the source of which is a payment application, is displayed, and below that, text content TC62, the aforementioned thank-you text content, the source of which is user A.A., is displayed.
Also, below that, a notification-attached electronic money usage content NUC62, which indicates that notification-attached electronic money has been used by user A.A, is displayed as a content whose transmission source is a payment application.

<Processing>
The processing in this embodiment can be realized, by way of example and not limitation, by giving the server 10 the functionality to provide a messaging service using a messaging application, and by combining the processing described in the first to fifth embodiments with the processing of the messaging service.

<Effects of the Sixth Embodiment>
This embodiment shows a configuration in which the control unit 11 controls the server 10 to send notification-attached electronic money usage information to a chat room including the user of the notification destination account (not limited to this, an example of the first chat room).
As an example of an effect of an embodiment obtained by such a configuration, the user of the third terminal can be informed in an easy-to-understand manner by displaying in a first chat room including a user of the third terminal information regarding the use of at least a portion of the first electronic currency by the user of the second terminal.

<Sixth Modification (1)>
It is also possible to configure a group containing three or more accounts in the messaging application so that users of the other accounts are notified based on the use of notification-enabled electronic money by a user of the destination account.

Figure 6-2 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example. Here, taking the above-mentioned parent-child example, an example of a display screen will be described in which a group "family" is made up of a mother's account, a father's account, and a child's account. The description will be given assuming that user A.A is the "child," user B.B is the "mother," and user C.C is the "father."

The left side of FIG. 6-2 shows an example of a group talk room screen for the group "Family" displayed on the display unit 24 of the child's terminal 20A. On this group talk room screen, on the left side of the talk area, there are displayed text content TC61 sent from user B.B's account, encouraging the child to purchase the reference book mentioned above, electronic money remittance result content NRC63 with notification sent from a payment application, text content TC62 sent from user A.A, and text content TC64 sent from user C.C, warning the child not to buy snacks.

The electronic money remittance result content NRC63 with notification is, by way of example and not limitation, content indicating that electronic money with notification for the amount of "1,000 yen" remitted from user B.B has been received, and indicates that the group "Family" has been set as the notification destination account.

Since the group "Family" is set as the notification destination account, when the electronic money with notification is used by user A.A, the electronic money use content with notification is sent to the terminals 20 (terminal 20A, terminal 20B, terminal 20C) of all users included in the group "Family".

It may be considered undesirable to send a notification to user A.A. Therefore, unlike the above, electronic money usage content with notification may be sent to the terminal 20 of the user of an account other than the remittance destination account among the accounts included in the group.

In the above state, a function for making a code payment by a payment application is called based on user input (not shown), and the above-mentioned code payment is used to execute a payment process using the electronic money with notification transferred from user B.B. As a result, the screen in the center of FIG. 6-2 is displayed, by way of example and not limitation. This screen is similar to the screen in the center of FIG. 6-1.

The right side of FIG. 6-2 shows an example of a group talk room screen of a messaging application displayed on the display unit 24 of the terminal 20C in this case.
On this group talk room screen, electronic money remittance result content with notification NRC64, whose source is the payment application, is displayed on the left side of the talk area, and below that, text content TC62, whose source is user A.A, and text content TC64, whose source is user C.C, are displayed.

Below that, notification-attached electronic money usage content NUC64 is displayed, which indicates that notification-attached electronic money was used by user A.A. as content sent from a payment application.

The processing in this modified example can be similarly realized by making the processing in the sixth embodiment a processing targeting a group of messaging applications.
In this case, the control unit 11 of the server 10 can transmit the notification-attached electronic money usage content to the terminal 20 of each user included in the group, as an example and not a limitation, as described above.
Alternatively, the control unit 11 of the server 10 may be configured not to transmit the notification-attached electronic money use content to the terminal 20 of the user of the remittance destination account.

<Sixth Modification (2)>
It may be possible to transmit the content by quoting information contained in the content of the messaging application.

6C and 6D are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of FIG. 6C is a talk room screen of a messaging application displayed on the display unit 24 of the terminal 20B, which is an example of an OA talk room screen in which the talk partner is an official account of a payment application.

On this OA chat room screen, on the left side of the chat area, the aforementioned electronic money remittance result content with notification NRC62 and electronic money usage content with notification NUC62 are displayed in chronological order as content sent from a payment application.

In this state, by way of example and not limitation, when the notification-enabled electronic money usage content NUC62 is tapped, a function selection area FSR is displayed above it as a display area in which the user can select a function to be executed based on this content. In this example, the function selection field includes, by way of example and not limitation, multiple functions such as a "copy" function for copying the tapped content, a "transfer" function for transferring the tapped content, a "reply" function for replying to the tapped content, and an "announce" function for displaying the content in the chat room fixedly in a specified position (such as the top of the screen).

As a non-limiting example, when the "Reply" function is tapped, the screen shown in the center of FIG. 6-3 is displayed. This screen is a one-to-one talk room screen with user A.A as the talk partner, and text content TC61 originating from user B.B and text content TC62 originating from user A.A are displayed in the talk area.
Also, a keyboard area and a reply area are displayed so as to be superimposed on a part of the talk area.

The reply area includes, by way of example and not limitation, a citation information display area QIR in which first citation information is displayed that quotes information related to the source content, which is the notification-enabled content NUC62 that uses electronic money, shown in the screen on the left side of Figure 6-3, or at least a portion of the information contained in the notification-enabled content NUC62, and a content input area CIR for the user to input content to be sent together with second citation information that quotes information related to the notification-enabled content NUC62 that is also the source content, or at least a portion of the information contained in the notification-enabled content NUC62 that uses electronic money.
In this example, a citation information display area QIR is displayed as an area different from the content input area CIR, in which the user cannot input content.

In this example, the citation information display area QIR displays the text "The electronic money sent to A.A has been used" as part of the information contained in the notification-included electronic money usage content NUC62.

The first citation information displayed in the citation information display area QIR may or may not include information about the source (sender) of the citation source content.
Information about the source (sender) of the content may include, by way of example and not limitation, the name of the source (account name, user name), an icon image, and the like.

In the example screen in the center of Figure 6-3, the citation information display area QIR displays the icon image and name (Payment App) of the payment application that sent the notification-included electronic money usage content NUC62, associated with the text "The electronic money sent to A.A. has been used."

A content input area CIR below includes a content input field for the user to input content, and a send button for sending the input content together with citation information.
In this example, a state is shown in which user B.B. has entered the text "You haven't bought the manga, have you?" into the content input field using the keyboard and tapped the send button.

Then, by way of example and not limitation, the screen on the right side of FIG. 6-3 will be displayed.
Specifically, below the text content TC62 sent from user A.A, as the content sent from user B.B, a second citation information including the icon image of the payment application displayed as the citation information on the screen in the center of FIG. 6-3 and its name (Payment App), and a citation response content (reply content) QC61 including "You didn't buy the manga, did you?" input by user B.B on the screen in the center of FIG. 6-3 are displayed. Also, below that, a text content TC66 including the text "I did buy the textbook" sent from user A.A is displayed.

In this example, the content entered by user B.B. is displayed in the area below the second citation.
Alternatively, different from this example, the content input by user B.B may be displayed in the area above the second citation information.

In this example, by way of example and not limitation, the content NUC62 using electronic money with notification, which is the content of the quote source, includes a ">Check details" button, but the quote response content QC61 sent to the user with whom the message is sent does not include a ">Check details" button. This is because, as one way of thinking, it is appropriate to limit the ability to check "detailed information" such as the usage history of electronic money with notification to the user of the notification destination account.
However, the present invention is not limited to this, and the quote response content QC61 may include a “>Check details” button.

In the above example, the first citation information displayed in the citation information display area QIR may be all of the information included in the quoting content, or may be only a part of the information.
The second citation information to be transmitted together with the content input by the user may be all of the information contained in the quoting content, or may be only a part of the information.
The first citation information and the second citation information may be completely the same information, or may be information that is partially different.

Also, unlike the above example, the content input area CIR and the citation information display area QIR may be integrated into one area, that is, the first citation information may be displayed in the content input area CIR.
Also, unlike the above example, information regarding the source (sender) of the content may not be displayed in the quoted information display area QIR.

FIG. 6D is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20B in this modified example.
The left side of FIG. 6-4 is a diagram showing an example of a group chat room screen with the group "Family" as the chat partner, and on the left side of the chat area, electronic money remittance result content with notification NRC64 with a payment application as the sender, text content TC67 including the text "Thank you for the pocket money!" with user A.A as the sender, and electronic money use content with notification NUC64 based on the use of the electronic money with notification remitted to user A.A are displayed in chronological order.

In this state, by way of example and not limitation, when the notification-attached electronic money-using content NUC64 is tapped, a function selection area FSR is displayed below it as a display area in which the user can select a function to be executed based on this notification-attached electronic money-using content NUC64. In this example, in addition to the functions described above, the function selection area FSR includes, by way of example and not limitation, a "Regular remittance settings" function for setting up regular remittances. When this "Regular remittance settings" function is tapped, by way of example and not limitation, the screen in the center of Figure 6-4 is displayed.

This screen is an example of a regular remittance setting screen in a payment application, and by way of example and not limitation, it includes a remittance date setting field for setting the remittance date, a remittance destination account setting field for setting the remittance destination account, a notification destination account setting field for setting the notification destination account, and a remittance amount setting field for setting the remittance amount.

The remittance date setting field displays the remittance date that has been set. In this example, the setting is shown to "remit on the 1st of every month." In addition, the remittance date for electronic money with notifications can be changed by tapping the "Change" button on the right.

In the destination account setting field, information about the destination account that has been set is displayed. In this example, an icon image of user A.A and their user name (A.A.) are displayed.

In the notification account settings field, information about the configured notification account is displayed. In this example, the "Family" group in the messaging application is shown as the notification account. The notification account can also be changed by tapping the "Change" button on the right.

The remittance amount setting field displays the remittance amount of the electronic money with notification that has been set. In this example, "3,000 yen" is shown as the setting. The remittance amount can also be changed by tapping the "Change" button on the right.

In this state, when the "Settings" button BT61 at the bottom of the screen is tapped, the screen on the right side of FIG. 6-4 is displayed, by way of example and not limitation.
This screen corresponds to the talk room screen on the left side of Fig. 6-4, and below the notification-included electronic money usage content NUC64 on the talk room screen on the left side of Fig. 6-4, regular remittance setting content NSC61, which indicates that regular remittance settings have been made (or that regular remittance settings have been changed), is displayed as content whose sender is a payment application. The regular remittance setting content NSC61 indicates that the remittance amount for the regular remittance has been reduced from "5,000 yen" to "3,000" yen.

Also displayed below that are text content TC68 sent from user B.B, which includes the text "You're buying games, so starting next month, I'll cut your allowance," and text content TC69 sent from user A.A, which includes the text "Huh, why?".

<Processing>
In this embodiment, the control unit 21 of the terminal 20 (as an example, and not a limitation, the terminal 20 of the user of the remittance source account) displays a function selection area corresponding to a certain content (as an example, and not a limitation, electronic money usage content with notification) based on an input to the content in the talk room of the messaging application displayed on the display unit 24 of the terminal 20.

As a non-limiting example, when the "reply" function is selected, the control unit 21 displays a citation information display area including the first citation information and a content input area. Also, based on detection of an operation on the content input area, it displays a keyboard. Then, input content input by the user via the keyboard is displayed in the content input area, and when a send button is operated, it displays quote response content including the second citation information and the input content in the talk room of the user's terminal 20. Also, it transmits the second citation information and the input content to the server 10 via the communication I/F 22.
In response to this, the control unit 11 of the server 10 generates quote response content based on the received information, and transmits it to the talk partner terminal 20 via the communication I/F 14 .
Then, the control unit 21 of the talk partner's terminal 20 displays the received quote response content in the talk room on the display unit 24 of the talk partner's terminal 20 .

Furthermore, as a non-limiting example, when the "regular remittance setting" function is selected, the control unit 21 executes the payment application and causes the display unit 24 to display a regular remittance setting screen. Then, setting information related to the regular remittance set based on user input is transmitted to the server 10 via the communication I/F 22.
In response to this, the control unit 11 of the server 10 generates regular remittance setting content based on the received setting information, and transmits it to the talk partner's terminal 20 via the communication I/F 14 .
Then, the control unit 21 of the other party's terminal 20 displays the received regular remittance setting content in the talk room on the display unit 24 of the other party's terminal 20 .

In this embodiment, the terminal 20 of the user of the destination account is the terminal 20 of the user of the remittance source account (not limiting, an example of the third terminal being the first terminal), and the talk room includes the user of the remittance source account (not limiting, an example of the user of the first terminal) and the user of the destination account (not limiting, an example of the user of the second terminal). When input is made to electronic money-using content with notification displayed in the talk room, the server 10 transmits information for setting regular remittance (not limiting, an example of information for inputting the amount of electronic money to be remitted to the user of the second terminal for each set period) via the communication I/F 14 to the terminal 20 of the user of the remittance source account.
As an example of the effect of an embodiment obtained by such a configuration, it is possible to enable a user of a first terminal to input the amount of electronic currency for which a notification has been set to be transferred to a user of a second terminal for each set period, based on the input made by the user of a first terminal to a notification displayed in a chat room including a user of a first terminal and a user of a second terminal.

Seventh Example
The seventh embodiment is an embodiment that allows restrictions to be imposed on the use of the notification-attached electronic money balance.

The contents described in the seventh embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

FIG. 7A is a diagram showing an example of the account management database 155F, which is an example of the account management database 155 in this embodiment.
Each account management data included in the account management database 155F stores, in addition to an application ID and a normal electronic money balance, by way of example and not limitation, restricted electronic money management data, restricted electronic money usage history data, and electronic money usage restriction management data.

The restricted electronic money management data is data for managing information related to restricted electronic money associated with the account of this application ID. In this data, the restricted electronic money management data stores, by way of example and not limitation, a remittance management ID, a remitter ID, a notification destination ID, a notifier name, and a restricted electronic money balance in association with each other.

The remittance management ID is an ID for uniquely identifying a remittance of restricted electronic money, and by way of example and not limitation, a different ID is set and stored by server 10 each time a remittance of restricted electronic money is executed by server 10.
As a non-limiting example, even if restricted electronic money is transferred from the same account of user B.B to the same account of user A.A, different IDs are set for each.

The remitter ID is identification information for identifying the account that remitted the restricted electronic money to the account of this application ID, and as a non-limiting example, the application ID of the account that remitted the restricted electronic money (the remitter account) is stored.

The notification destination ID is information for identifying the notification destination account when the corresponding restricted electronic money balance is used, and as a non-limiting example, the application ID of the account set as the notification destination account is stored.

The notifier name is the user name that corresponds to this notification destination ID. By way of example and not limitation, the user name associated with the application ID that corresponds to this notification destination ID is stored in the account registration data 153.

The restricted electronic money balance is the balance of restricted electronic money associated with this remittance management ID.

The restricted electronic money usage history data is data regarding the usage history of restricted electronic money, and by way of example, and not limitation, a payment ID, a remittance management ID, the name of the store used, the date and time of use, and the amount used are stored in association with each other.
The payment ID, remittance management ID, name of the store used, date and time of use, and amount used can be configured in the same manner as the notification-attached electronic money use history data described above, but are not limited thereto.

The electronic money usage restriction management data is data for managing (prescribing) usage restrictions on restricted electronic money, and by way of example and not limitation, a remittance management ID, a usability flag, and the end date and time of the usable state are stored in association with each other.

The remittance management ID is information for identifying restricted electronic money for which a usage limit is imposed on the restricted electronic money balance in the electronic money usage limit management data, and as a non-limiting example, among the remittance management IDs stored in the restricted electronic money management data, a remittance management ID for which a usage limit has been set by the remitter is stored.

The usability flag is flag information that indicates whether or not the use of this restricted electronic money balance (payment using this restricted electronic money balance) is possible; by way of example and not limitation, if it is possible to use it, a "possible" flag is stored, and if it is not possible to use it, a "not possible" flag is stored.

For example and not by way of limitation, the end date and time of the available state is stored as the date and time when this limited electronic money balance changes from available to unavailable if it is available.

In this data, as a restriction on the use of the notified electronic money balance, whether or not use (payment) is possible within a certain period is given as an example, but is not limited to this. Examples of electronic money use restriction management data for various restrictions will be described later.

<Display screen>
7-2, 7-3, and 7-4 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of Fig. 7-2 shows an example of a remittance screen of the payment application displayed on the display unit 24 of the terminal 20B. On this remittance screen, from the center to the bottom of the screen, there is provided information indicating the user of the remittance destination account as described above, as well as a slide button for selecting whether or not to receive the notification-attached electronic money usage notification as described above. Further below that, there is provided a slide button for selecting whether or not to place a restriction on the usage of the notification-attached electronic money balance.

Below that, a "Set Usage Restriction" button BT71 is provided for setting restrictions on the use of restricted electronic money.
In this example, it is assumed that a "time limit" has already been set as a restriction on the use of restricted electronic money.

Here, both slide buttons are shown to be "ON" and the "Remittance" button BT2 is tapped.
The center of FIG. 7-2 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A in this case.
On this notice screen, on the left side of the notice area, limited electronic money remittance result information RR71 indicating that limited electronic money has been remitted is displayed.

In this example, the restricted electronic money remittance result information RR71 indicates that when the restricted electronic money is used, a notification of electronic money use with notification is sent to user B.B., and that permission of user B.B. is required to use the restricted electronic money.
Further, to the right of the illustration indicating that a notification of use of electronic money with notification is sent to user B.B when the restricted electronic money is used, a mark RMK (hereinafter referred to as a "restriction mark") is displayed, which is similar to a caution mark/construction mark and indicates that the use of the electronic money with notification is restricted.

The right side of FIG. 7-2 shows an example of a code payment screen displayed on the display unit 24 of the terminal 20A.
On this code payment screen, the area at the top of the wallet code information display area WCR1 where the balance is displayed displays information regarding the limited electronic money balance and information regarding the unlimited electronic money balance (i.e., the normal electronic money balance).
The balance marked "Limited" is the restricted electronic money balance, but as described above, permission from user B.B is required to use the restricted electronic money, and user A.A has not yet received permission from user B.B. For this reason, the display portion of the information regarding the restricted electronic money balance is grayed out, and even if user A.A taps the radio button to the left of the word "Limited," he or she cannot turn it "ON."

The left side of Figure 7-3 shows an example of a notification screen of a payment application displayed on the display unit 24 of terminal 20B, and on the left side of the notification area, restricted electronic money remittance result information RR72 is displayed, indicating that restricted electronic money has been remitted. The restricted electronic money remittance result information RR72 has a restricted electronic money usage permission button BT72 for permitting the use of the remitted notification-attached electronic money for a set period of time only (in this example, "60 minutes").

The right side of FIG. 7C shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A in this case.
Under the restricted electronic money remittance result information RR71 in the notification area, restricted electronic money use permission information RP71 is displayed, which indicates that the use of restricted electronic money has been permitted by user B.B.
In this example, the period during which the restricted electronic money can be used can be, by way of example and not limitation, the period from when the server 10 receives information permitting/approving the use of the restricted electronic money sent from terminal 20B (restricted electronic money use approval information, described later) until a set time (in this example, "60 minutes") has elapsed.

FIG. 7-4 is a diagram showing an example of a code payment screen displayed on the display unit 24 of the terminal 20B.
As a result of user B.B being permitted to use the restricted electronic money, the grayed-out portion of the display of information regarding the balance of the restricted electronic money displayed in the wallet code information display area WCR1 on the code payment screen on the right side of FIG. 7-2 is released, and user A.A can tap the radio button to the left of the word "restricted" to set it to "ON." Here, the state in which the radio button is set to "ON" is shown. By making a code payment in this state, payment result information is displayed as shown on the right side of FIG. 7-4.

<Processing>
7-5 and 7-6 are flowcharts showing an example of the flow of processes executed by each device in this embodiment.
First, the control unit 21 of the terminal 20B performs a restricted electronic money remittance setting process as a setting process related to the remittance of restricted electronic money based on a user input to the input/output unit 23 or the like (B410).

Then, the control unit 21 of the terminal 20B transmits notification-attached electronic money remittance request information, which includes, by way of example and not limitation, setting information including settings regarding usage restrictions and a notification destination account, to the server 10 via the communication I/F 22 (B420).

When the communication I/F 14 receives the restricted electronic money remittance request information from the terminal 20B, the control unit 11 of the server 10 performs a restricted electronic money remittance process (S410).
Specifically, the control unit 11 of the server 10 updates the account management data included in the account management database 155F, which corresponds to the account of user A.A (or terminal 20A), who is the user of the remittance destination account, based on the setting information included in the notification-attached electronic money remittance request information received from terminal 20B.
Furthermore, the control unit 11 of the server 10 sets the usage permission flag of the electronic money usage restriction management data to a "disabled" flag as an initial value, for example and not as a limitation.

Thereafter, the control unit 11 of the server 10 transmits restricted electronic money remittance result information, which is information on the restricted electronic money remittance result, to each of the terminals 20A and 20B via the communication I/F 14 (S420). Note that the restricted electronic money remittance result information may include the remittance management ID generated in the restricted electronic money remittance process.
When the control unit 21 of the terminal 20A and the control unit 21 of the terminal 20B receive the restricted electronic money remittance result information from the server 10, they each cause the display unit 24 to display it (A410, B430).

Next, the control unit 21 of the terminal 20B causes the display unit 24 to display a selection display for whether or not to approve the use of the remitted restricted electronic money balance (B440). If approval of use is selected based on a user input to the input/output unit 23 or the like (B440: YES), the control unit 21 of the terminal 20B transmits restricted electronic money use approval information to the server 10 via the communication I/F 22 (B450). Note that the restricted electronic money use approval information may include a remittance management ID of the restricted electronic money balance to be approved for use.
If the use approval is not selected (B440: NO), the control unit 21 of the terminal 20B skips step B450.

When the restricted electronic money use approval information is received from the terminal 20B via the communication I/F 14 (S430: YES), the control unit 11 of the server 10 executes the restricted electronic money use approval process (S440).
Specifically, the control unit 11 of the server 10 changes the usability flag of the remittance management ID specified in the restricted electronic money use approval information from "unavailable" to "available" in the electronic money use restriction management data in the account management data included in the account management database 155F, and also stores a predetermined date and time (as an example and not a limitation, 60 minutes after the restricted electronic money use approval information is received) as the usable state end date and time.

If restricted electronic money use approval information is not received from terminal 20B via communication I/F 14 (S430: NO), control unit 11 of server 10 skips step S440.

The control unit 21 of terminal 20A causes the display unit 24 to display the received wallet code information (A130), and based on user input to the input/output unit 23, etc., transmits payment balance selection information including, by way of example and not limitation, a remittance management ID for specifying the balance to be paid to the server 10 via the communication I/F 22 (A420). Note that when payment is selected to be made from the normal electronic money balance, the payment balance selection information may include information for selecting to make payment from the normal electronic money balance. Furthermore, when the balance to be paid is not specified, the control unit 21 of terminal 20A does not need to transmit the payment balance selection information to the server 10.

The control unit 21 of the terminal 20A may execute step A420 simultaneously with, or before or after, step A120. In this case, the control unit 11 of the server 10 may not transmit wallet code information to the terminal 20A if the use availability flag of the restricted electronic money balance specified as the balance to be paid is "unavailable."

When payment request information is received from the store POS system 40 via the communication I/F 14 and payment balance selection information is received from the terminal 20A, the control unit 11 of the server 10 executes a restricted payment process (S450).

In the limited payment process, the control unit 11 of the server 10, by way of example and not limitation, determines whether or not payment can be made using the specified limited electronic money balance based on the payment balance selection information if the use availability flag of the limited electronic money balance specified as the balance to be paid is "available" and the usable state end date and time has not passed. If the payment is successful, the control unit 11 of the server 10 subtracts the payment amount from the specified limited electronic money balance.
If the use availability flag of the limited electronic money balance specified as the balance to be paid is "unavailable" or if the end date and time of the available state has passed, the control unit 11 of the server 10 determines that the payment using the specified limited electronic money balance has failed. Note that if the end date and time of the available state has passed, the control unit 11 of the server 10 may change the use availability flag of the specified limited electronic money balance from "available" to "unavailable" and erase the end date and time of the available state.
In addition, if a payment using the restricted electronic money balance fails due to insufficient balance, usage restrictions, etc., the control unit 11 of the server 10 may switch to the normal electronic money balance and execute the payment.
When the regular electronic money balance is specified as the balance for payment, the control unit 11 of the server 10 executes the settlement using the regular electronic money balance.

If payment balance selection information is not received from terminal 20A, the control unit 11 of server 10 may replace the notification-attached electronic money balance with a restricted electronic money balance based on the methods (a) to (f) described in the first embodiment, select the balance to be paid, and perform the restricted payment process.

After S150, the control unit 11 of the server 10 determines whether or not the limited electronic money balance has been used for the payment in the limited payment process of S450 (S460).
If it is determined that the information has not been used (S460: NO), the control unit 11 of the server 10 ends the process.
On the other hand, if it is determined that the electronic money has been used (S460: YES), the control unit 11 of the server 10 transmits the restricted electronic money usage information to the terminal 20B via the communication I/F 14 (S470). Then, the control unit 11 of the server 10 ends the process.

The control unit 21 of the terminal 20B determines whether or not restricted electronic money usage information has been received from the server 10 via the communication I/F 22 (B460).
If it is determined that the message has not been received (B460: NO), the control unit 21 of the terminal 20B ends the process.
On the other hand, if it is determined that the information has been received (B460: YES), the control unit 21 of the terminal 20B causes the display unit 24 to display the received restricted electronic money usage information (B470).Then, the control unit 21 of the terminal 20B ends the process.

<Seventh Modification (1)>
In the above embodiment, when the limited electronic money balance is used, the notification destination account is notified, but the present invention is not limited to this. For example and not for limitation, when the limited electronic money balance is used, a third party such as a remitter may not be notified.

In this case, for example and not limitation, no data is stored in the notification destination ID and notifier name of the restricted electronic money management data (for example and not limitation, NULL is stored). And even if the restricted electronic money balance is used in the restricted payment process, the control unit 11 of the server 10 does not transmit the restricted electronic money usage information.

<Seventh Modification (2)>
In the above embodiment, there are cases where the use of the limited electronic money balance is not possible in the limited payment process, but this is not limiting. By way of example and not of limitation, the use of the limited electronic money balance may always be permitted in the limited payment process.
In this case, for example and not by way of limitation, a remittance management ID may be prevented from being stored in the electronic money use restriction management data for a specific remittance management ID. Alternatively, for a specific remittance management ID, the usability flag in the electronic money use restriction management data may be permanently set to "enabled" and the usable state end date and time may be set sufficiently far into the future (for example and not by way of limitation, 5 billion years in the future). In this case, this is equivalent to there being no restriction on the use of the restricted electronic money balance in the restricted payment process.

In addition, if the use of the restricted electronic money balance is not restricted in the restricted payment process, and the use of the restricted electronic money balance is notified to the notification account, the restricted electronic money balance may be called a notified electronic money balance.

<Seventh Modification (3)>
In the above embodiment, a distinction is made between a normal electronic money balance and a restricted electronic money balance, but this is not limiting. As a non-limiting example, the normal electronic money balance may be a restricted electronic money balance with no notification destination ID or notifier name in the restricted electronic money management data, and with no usage restrictions in the restricted payment processing in the electronic money usage restriction management data. In this case, as a non-limiting example, in the restricted electronic money management data, the remittance management ID may be an ID generated when the electronic money is charged, and the remitter ID may be the same as the application ID.

In other words, the broad definition of "limited electronic money balance" can include the following concepts:
(1) "Notification restricted electronic money balance" which has restrictions on its use and notifies a third party, such as the remitter, when it is used.
(2) "Electronic money balance with non-notification restrictions," which has restrictions on its use but is not notified to third parties when it is used.
(3) "Electronic money balance without restriction with notification (electronic money balance with notification)" which has no restriction on use and is notified to a third party when used (there is a restriction that notification is given when used).
(4) "Electronic money balance without notification and without restriction (normal electronic money balance)" which has no restriction on use and is not notified to third parties even if it is used (no restriction exists).

<Seventh Modification (4)>
In the above embodiment, the limit on the use of the balance in the restricted payment process requires the prior approval of the remitter, but the present invention is not limited to this.
As a non-limiting example of a restriction on the use of the balance in a restricted payment process, the balance may not be used to make payments at stores or services in a specific business type or format.

FIG. 7-7 is a diagram showing an example of an account management database 155G which is an example of the account management database 155 in this modified example.
In the account management database 155G, the electronic money use restriction management data includes, by way of example and not of limitation, a remittance management ID and a prohibited store type in association with each other.

The prohibited store types are items for storing the types and formats of businesses in which the use of the restricted electronic money balance is prohibited, and are set and stored based on an input by the remitter, for example and not for limitation.
In FIG. 7-7, by way of example and not limitation, it is stored that the restricted electronic money balance managed by the remittance management ID “T01003” cannot be used in stores and services classified into the industries of “apparel,” “furniture and home appliances,” and “taverns and pubs.”

7-8 to 7-9 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this modified example.
7 and 8 are diagrams showing examples of display screens relating to other examples of usage restrictions on restricted electronic money.
The left side of FIG. 7-8 is a diagram showing an example of a remittance screen of the payment application displayed on the display unit 24 of the terminal 20B, and corresponds to the screen shown on the left side of FIG. 7-2.
In this example, the restrictions on the use of restricted electronic money have not yet been set, so the "Transfer" button at the bottom of the screen is displayed as grayed out.
When the above-mentioned "Set Usage Restriction" button BT71 is tapped, a display such as that shown in the center of FIG. 7-8 is displayed.

This screen is configured so that, as a non-limiting example of restrictions on the use of restricted electronic money, it is possible to set the type of business of a store in which the use of restricted electronic money is prohibited.
In this example, several store types, such as "convenience stores,""supermarkets/home improvement centers,""apparel,""furniture/homeappliances,""izakayas/pubs," and "coffee shops," are listed in boxes containing an illustration and the name of the type of store.

When you tap a box for which you want to prohibit the use of restricted electronic money, a check mark is placed in association with that box, for example and not by way of limitation. Then, by tapping the "Set" button BT73 at the bottom of the screen, you can set the business type with the check mark as the business type for which the use of restricted electronic money is restricted.

In this example, user B.B. has tapped and checked three business types, "Apparel," "Furniture/Home Appliances," and "Izakaya/Pubs," as business types for which he wants to prohibit the use of restricted electronic money. By tapping the "Settings" button BT73 in this state, the screen on the right side of FIG. 7-8 is displayed, as an example and not a limitation.

This screen is the remittance screen of the payment application, and corresponds to the screen on the left side of Figure 7-8. In this example, icons corresponding to the industries set on the screen in the center of Figure 7-8 are displayed above the "Set usage restrictions" button BT71 on the remittance screen on the left side of Figure 7-8. Specifically, icons corresponding to the three industries, "Apparel," "Furniture/Home Appliances," and "Izakaya/Pubs," are displayed. In addition, by setting the industries in which the use of restricted electronic money is prohibited, the "Remit" button on the screen on the left side of Figure 7-8 is no longer grayed out. Here, the "Remit" button BT2 is shown in a tapped state.

The left side of FIG. 7-9 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A in this case.
On the left side of the notification area, restricted electronic money remittance result information RR73 is displayed. This restricted electronic money remittance result information includes illustrations corresponding to the types of businesses for which the use of the restricted electronic money set by user B.B is prohibited. Specifically, icons corresponding to three types of businesses, "apparel,""furniture and home appliances," and "taverns and pubs," are displayed along with a prohibition mark and the text "cannot be used at the following stores."

Then, the code payment screen in the center of Figure 7-9 shows the state in which the radio button for the restricted electronic money balance in the wallet code information display area WCR1 is set to "ON." In this state, as an example and not a limitation, let us say that user A. A attempts to make a payment at an electronics store (in this example, "XX Electric") and has the wallet code information read by the store's code reader. However, since the electronics store is included in the "furniture and home appliances" industry, which prohibits the use of restricted electronic money, the use of restricted electronic money is prohibited. As a result, as an example and not a limitation, the screen on the right side of Figure 7-9 is displayed.

On this screen, information indicating that the balance is insufficient and a payment cannot be made is displayed so as to be superimposed on the wallet code information display area WCR1.
Specifically, the payment amount is "1,000 yen" and the limited electronic money balance is "1,000 yen", so the amount is actually sufficient. However, because the use of the limited electronic money balance is prohibited, the limited electronic money balance "1,000 yen" cannot be used for payment. Therefore, there is a shortage of "1,000 yen" for the payment amount of "1,000 yen", resulting in an insufficient balance.
In this example, only the restricted electronic money balance is used for payments, and the normal electronic money balance is not used for payments.

In this modified example, first, in step B410 of FIG. 7-5, the control unit 21 of the terminal 20B sets, by way of example and not limitation, the industry and business type in which the use of the restricted electronic money balance is prohibited, based on user input to the input/output unit 23, etc.
In step S410 of Figure 7-5, the control unit 11 of the server 10 updates the prohibited store types in the electronic money use restriction management data based on, by way of example and not limitation, the setting information included in the notification-attached electronic money remittance request information received from terminal 20B.

In addition, the control unit 21 of the terminal 20B skips steps B430 to B450 in FIG. 7-5, and the control unit 11 of the server 10 skips steps S430 to S440 in FIG. 7-5.

7-5, when the prohibited store business type of the restricted electronic money balance specified as the balance to be paid does not match the business type/category determined from the payment request information, the control unit 11 of the server 10 uses the specified restricted electronic money balance to determine whether or not the payment can be made. If the payment is successful, the control unit 11 of the server 10 subtracts the payment amount from the specified restricted electronic money balance.
If the type of store in which the restricted electronic money balance specified as the balance to be paid is prohibited matches the type and business form determined from the payment request information, the control unit 11 of the server 10 determines that the payment using the specified restricted electronic money balance has failed.

The following restrictions are examples of restrictions on the use of restricted electronic money balance, but are not limited thereto:
- Approval for use in the sending account, notification account, etc.
- Notification regarding the use of restricted electronic money balance.
- The dates, times and periods when the restricted electronic money balance can be used (for example and not limitation, it can be used on school trip days, on weekends, and between 11:00 and 13:00).
- Dates, times and hours when the restricted electronic money balance cannot be used (for example, but not limited to, it cannot be used on weekdays or during the late night hours from 22:00 to 6:00).
- Usage restrictions based on the type and business format of the store or service provider making the payment (as an example, and not a limitation, setting usability based on the type and business format of the store or service based on the identification information of the payment store included in the payment request information)
- Usage restrictions on the items of goods and services for which payment is made (for example and not limitation, setting usable goods and services based on the JAN code or EAN code included in the product image captured by the terminal or the payment request information. More specifically, for example and not limitation, it may be possible to use it to purchase plastic models but not to purchase video games.)
- Usage restrictions regarding payment amounts (for example, it can be used if the payment amount is 1,000 yen or less, etc.)
- Restrictions on use based on device location (for example, use within a 5km radius of home)
Restrictions on withdrawals (for example, but not limited to, not being able to withdraw cash from a restricted electronic money balance via ATM or to a bank account)
- The expiration date from the first time the restricted electronic money balance is used.
The number of times a limited electronic money balance can be used (for example and not by way of limitation, it can be used "10 times").
- Any combination of the above restrictions.

Furthermore, the restricted electronic money balance is not limited to being generated by money transfer. By way of example and not limitation, when a parent charges a child's account, the parent's device or the child's device may or may not be able to set usage limits.

This modified example shows a configuration in which the restrictions set on the restricted electronic money include at least one of the following: restrictions on notification when the user of the terminal 20 making the payment uses the restricted electronic money, restrictions on stores where the restricted electronic money can be used, restrictions on goods or services for which the restricted electronic money can be used, restrictions on categories of goods or services for which the restricted electronic money can be used, restrictions on goods for which the restricted electronic money cannot be used, restrictions on time periods when the restricted electronic money cannot be used, dates on which the restricted electronic money cannot be used, and restrictions on dates and times when the restricted electronic money cannot be used.
As an example of the effect of the modified example obtained by such a configuration, it is possible for the user of the first information processing device to set various restrictions on the first electronic currency by the user of the first information processing device, such as restrictions on notifying the user of the first information processing device when the user of the information processing device uses the first electronic currency, restrictions on stores where the first electronic currency can be used, restrictions on goods or services for which the first electronic currency can be used, restrictions on categories of goods or services for which the first electronic currency can be used, restrictions on goods for which the first electronic currency cannot be used, restrictions on time periods during which the first electronic currency cannot be used, and restrictions on dates or times when the first electronic currency cannot be used, thereby improving convenience for the user of the first information processing device.

<Seventh Modification (5)>
In the above embodiment, the limited electronic money balance is used at the time of payment, but the present invention is not limited to this.
By way of example and not limitation, after regular electronic money is used in a payment, the restricted electronic money balance may be converted to a regular electronic money balance based on, by way of example and not limitation, authorization for use from the sender account, the notified account, etc. That is, even if the restricted electronic money is not available at the time of payment, a payment may be made in advance using regular electronic money so that the restricted electronic money balance can be used after the payment.

7-10 to 7-11 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of Figure 7-10 is a code payment screen similar to the screen in the center of Figure 7-9.
In this example, the charge button CBT is tapped and the electronic money is charged by user A.A by 500 yen, and the normal electronic money balance is increased from 500 yen to 1,000 yen. When a code payment of 1,000 yen is made in this state, the payment result information in the center of FIG. 7-10 is displayed, by way of example and not limitation.
In this example, it is shown that ordinary electronic money was used for the payment, and the payment from "No limit" is "1,000 yen."

The right side of Figure 7-10 shows the main menu screen of the payment application that is displayed afterwards, with the balance displayed in the balance display area remaining at "1,000 yen" for "Limited" and changing to "0 yen" for "No limit."

The left side of FIG. 7-11 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B.
In this notification screen, restricted electronic money use confirmation information RV74 for confirming whether or not to permit use of the restricted electronic money is displayed below restricted electronic money remittance result information RR74. When the "Allow" button included in this information is tapped and user B.B selects to permit use of the restricted electronic money remitted to user A.A, a notice to that effect (text "Allow") is displayed in the notification area, as shown in the center of FIG. 7-11. However, this permission to use the restricted electronic money is permission to convert the balance from the restricted electronic money balance to a normal electronic money balance in this example.

Based on the above permission, the server 10 converts the balance of user A.A's account from the limited electronic money balance to the normal electronic money balance. Then, the server 10 transmits limited electronic money usage information RU71 to the terminal 20B. As a result, as shown in the center of Figure 7-11, the limited electronic money usage information RU71 is displayed in the notification area.

Meanwhile, the wallet main menu screen of the payment application of terminal 20A displays the screen shown on the right side of FIG. 7-11. Specifically, as a result of the server 10 converting the balance of user A.A's account from a limited electronic money balance to a normal electronic money balance, the display of information relating to the limited electronic money balance that was displayed in the balance display area BR2 on the screen on the right side of FIG. 7-10 is erased, and the screen on the right side of FIG. 7-11 displays a balance of "1000 yen" (normal electronic money balance) and a charge button CBT.

<Seventh Modification (6)>
When a refund occurs upon return of a product or service, etc., and the limited electronic money balance has been used at the time of payment, the amount of the refund may be added to the limited electronic money balance used at the time of payment. In this case, the processing may be executed in the same manner as in the second modified example, by way of example and not of limitation.

Eighth Example
In the above-described embodiment, the server 10 executes the payment process (limited payment process) using either normal electronic money or limited electronic money.
The eighth embodiment is an embodiment in which settlement is carried out using normal electronic money and one piece of restricted electronic money.

The contents described in the eighth embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Display screen>
8A is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of FIG. 8-1 shows the main menu screen of the payment application displayed on the display unit 24 of the terminal 20A with the "Code Payment" icon tapped.
Then, by way of example and not limitation, a code payment screen like that shown in the center of Figure 8-1 is displayed.

On this screen, the notification account is user B. The limited notification money balance is displayed as "1,000 yen" for B's account, and the regular electronic money balance is displayed as "500 yen." When the "Code Payment" icon IC2 is tapped, the code payment screen in the center of Figure 8-1 is displayed.

On this code payment screen, the combined balance of the limited electronic money balance and the normal electronic money balance (in this example, "1,500 yen") is displayed in the wallet code information display area WCR1. As described above, information about the limited electronic money balance (limited) and information about the normal electronic money balance (unlimited) are also displayed. However, here, there are no radio buttons next to these displays, and the limited electronic money balance and the normal electronic money balance are automatically used for payment.

Here, we will take an example of purchasing a product that costs 1,200 yen. The sum of the limited notification money balance and the regular electronic money balance is 1,500 yen, which exceeds the payment amount of 1,200 yen. In this case, by way of example and not limitation, the limited electronic money can be used preferentially, and the shortfall can be made up by using regular electronic money. The payment process is carried out based on this, and the payment result information on the right side of Figure 8-1 is displayed.

Specifically, information is displayed indicating that a payment of "1,200 yen" has been completed, with the breakdown showing that "1,000 yen" was paid from restricted electronic money and the remaining "200 yen" was paid from regular electronic money.

<Processing>
8B and 8C are flow charts showing an example of the flow of processes executed by each device in this embodiment.

When the communication I/F 14 receives payment request information from the store POS system 40, the control unit 11 of the server 10 executes a usage balance calculation process (S500). In the usage balance calculation process, the control unit 11 of the server 10 calculates, from the payment amount of the payment request information, a first payment amount to be paid from the limited electronic money balance and a second payment amount to be paid from the normal electronic money balance.

Here, the first payment amount and the second payment amount are any amounts that satisfy the condition "first payment amount" + "second payment amount" = "payment amount in the payment request information", and can be determined as follows, by way of example and not limitation:
- Priority use of restricted electronic money balance.
"First payment amount" = "Limited electronic money balance"("Second payment amount" = "Payment amount in payment request information" - "First payment amount")
・Normal electronic money balance is used first.
"Second payment amount" = "Normal electronic money balance"("First payment amount" = "Payment amount in payment request information" - "Second payment amount")
・Use according to the ratio of each balance.
"First payment amount": "Second payment amount" = "Limited electronic money balance": "Normal electronic money balance"
Hereinafter, the priority order of the balance used for payment is referred to as the "usage balance priority order."

By way of example and not limitation, FIG. 8-1 shows an example of automatically prioritizing the use of a limited electronic money balance. The method of calculating the first payment amount and the second payment amount shown above is, by way of example and not limitation, preset and programmed by a user of the server 10.

When the first payment amount and the second payment amount are calculated, the control unit 11 of the server 10 performs a payment process with a consecutive limit (S510). In the payment process with a consecutive limit, the control unit 11 of the server 10 sequentially executes, by way of example and not limitation, a limited payment process using a limited electronic money balance for the first payment amount, and a payment process using a normal electronic money balance for the second payment amount.

If the payment process with restriction and the payment process are successful, the payment process with consecutive restriction is successful.
If at least one of the limited payment process and the payment process fails, the continuous limited payment process will fail (payment is not possible). If the continuous limited payment process fails, by way of example and not limitation, for the limited payment process or the payment process that was successful, the process will be cancelled and the balance will be returned.

Note that if the first payment amount = "0", the restricted payment process may not be executed. Also, if the second payment amount = "0", the payment process may not be executed. In these cases, the restricted payment process (payment process) that is not executed is treated as successful.

When a restricted payment process is executed, by way of example and not limitation, the control unit 11 of the server 10 can generate a payment ID for each restricted payment process in the payment history management data 157 and add it to the payment history management data 157. In this case, the payment amount in the payment request information is stored as the payment amount in the payment history management data 157, and the first payment amount is stored as the usage amount in the restricted electronic money usage history data.

The control unit 11 of the server 10 may generate separate payment IDs for restricted payment processing and payment processing in the payment history management data 157 and add them to the payment history management data 157. In this case, the payment history management data 157 records that two payments were made for one processing of payment request information. Therefore, in the case of a refund due to a return to a store, etc., it is necessary to specify two payment IDs.

In this flowchart, for the sake of simplicity, the notification sending process for the restricted electronic money balance with notification and the unrestricted electronic money balance with notification is omitted. In the continuous restricted payment process, when the restricted electronic money balance with notification or the unrestricted electronic money balance with notification is used to send a notification, the control unit 11 of the server 10 may, by way of example and not by way of limitation, send restricted electronic money usage information to the terminal 20B, which is the terminal of the notification destination account, as in FIG. 7-6. When the control unit 21 of the terminal 20B receives the restricted electronic money usage information, by way of example and not by way of limitation, the control unit 21 may display the received restricted electronic money usage information on the display unit 24.

Also, prior to this flowchart, by way of example and not limitation, the control unit 21 of terminal 20A may transmit charge request information for charging the normal electronic money balance to the server 10 via the communication I/F 22 based on user input to the input/output unit 23, etc. In this case, when the charge request information is received from terminal 20A via the communication I/F 14, the control unit 11 of the server 10 may execute a charge process for increasing the normal electronic money balance based on the received charge request information.

<Effects of the Eighth Example>
The present embodiment shows a configuration executed by the information processing device, in which a program is executed by a terminal 20A (not limited to, an example of an information processing device) communicating with a terminal 20B (not limited to, an example of a first information processing device), and a usage restriction (not limited to, an example of a restriction) including a notification is set by a user B.B (not limited to, an example of a user of the first information processing device), and a wallet code information display process (not limited to, an example of a process related to the first payment) for performing a payment process with a consecutive restriction is performed by a control unit of the information processing device based on a first payment amount (not limited to, an example of at least a part of the first electronic currency) of a limited electronic money balance (not limited to, an example of the first electronic currency) transferred from the first information processing device and a second payment amount (not limited to, an example of at least a part of the second electronic currency) of a normal electronic money balance (not limited to, an example of the second electronic currency) associated with a user A.A (not limited to, an example of a user of the information processing device).
As an example of an effect of an embodiment obtained by such a configuration, a limit is set by a user of a first information processing device, and processing related to a first payment is performed based on at least a portion of a first electronic currency transferred from the first information processing device and at least a portion of a second electronic currency associated with the user of the information processing device, thereby realizing, by way of example and not limitation, a payment using at least two electronic currencies including at least the first electronic currency for which a limit is set.

In this example, the information processing device is the terminal 20 (terminal 20A, as an example and not a limitation) of the user of the destination account of the restricted electronic money, and the first information processing device is the terminal 20 (terminal 20B, as an example and not a limitation) of the source account of the restricted electronic money.
However, without being limited to this, as an example, the information processing device can be the terminal 20 of the user of the destination account of the restricted electronic money, and the first information processing device can be the server 10.
It should be noted that combinations other than these are also possible.

In addition, this embodiment illustrates a configuration in which the first electronic currency and the second electronic currency are selected based on pre-set (pre-programmed) conditions (not limited to, but an example of set conditions).
As an example of an effect of an embodiment obtained by such a configuration, and by way of example and not limitation, it is possible to appropriately select the first electronic currency and the second electronic currency to be used for payment based on set conditions.

Furthermore, this embodiment shows a configuration in which the set conditions include a condition regarding use from a limited electronic money balance (not a limitation, but an example of electronic currency with a set limit).
As an example of an effect of an embodiment obtained by such a configuration, and by way of example and not limitation, a restriction can be set by the user of the first information processing device, and the first electronic currency transferred from the first information processing device can be used preferentially for payment.

In addition, this embodiment shows a configuration in which the restrictions set on the restricted electronic money include at least one of the following: restrictions regarding notification when the user of the terminal 20 making the payment uses the restricted electronic money, restrictions regarding the stores where the restricted electronic money can be used, restrictions regarding the products or services for which the restricted electronic money can be used, restrictions regarding the categories of products or services for which the restricted electronic money can be used, restrictions regarding products for which the restricted electronic money cannot be used, restrictions regarding the time periods during which the restricted electronic money cannot be used, dates on which the restricted electronic money cannot be used, and restrictions on the dates and times on which the restricted electronic money cannot be used.
As an example of the effect of the modified example obtained by such a configuration, it is possible for the user of the first information processing device to set various restrictions on the first electronic currency by the user of the first information processing device, such as restrictions on notifying the user of the first information processing device when the user of the information processing device uses the first electronic currency, restrictions on stores where the first electronic currency can be used, restrictions on goods or services for which the first electronic currency can be used, restrictions on categories of goods or services for which the first electronic currency can be used, restrictions on goods for which the first electronic currency cannot be used, restrictions on time periods during which the first electronic currency cannot be used, and restrictions on dates or times when the first electronic currency cannot be used, thereby improving convenience for the user of the first information processing device.

In addition, this embodiment shows a configuration in which the server performs a limited electronic money remittance process (not limited to, a program executed by a server communicating with terminal 20B (not limited to, an example of a first information processing device) and terminal 20A (not limited to, an example of a second information processing device), which is an example of a process of associating a limited electronic money balance (not limited to, an example of a first electronic currency) transferred from the first information processing device to the second information processing device, in which a limit has been set by the user of the first information processing device, with the user of the second information processing device) and a charge process (not limited to, an example of a process of associating a normal electronic money balance (not limited to, an example of a second electronic currency) with the user of the second information processing device), and a process related to a continuous limited payment process (not limited to, an example of a first payment) based on at least a portion of the first electronic currency and at least a portion of the second electronic currency based on wallet payment request information (not limited to, an example of information transmitted from the second information processing device).
As an example of the effect of an embodiment obtained by such a configuration, a first electronic currency transferred from a first information processing device to a second information processing device, for which a restriction has been set by a user of the first information processing device, can be associated with the user of the second information processing device, and the second electronic currency can be associated with the user of the second information processing device, and a first payment can be realized based on at least a portion of the first electronic currency and at least a portion of the second electronic currency based on information transmitted from the second information processing device.

In addition, this embodiment shows a configuration in which the restriction includes a notification to the notification destination account (not limited to, but an example of a restriction in which, when at least a portion of the first electronic currency is used by a user of the second information processing device, a notification indicating that the user of the second information processing device has used it is sent to the first information processing device by the communication unit of the server).
As an example of an effect of an embodiment obtained by such a configuration, when at least a part of the first electronic currency is used by a user of the second information processing device, the user of the first information processing device can be notified of the contents related to the use.

<Eighth Modification (1)>
In the above embodiment, an example was shown in which both the limited electronic money balance and the normal electronic money balance were automatically used, but the present invention is not limited to this.
As an example and not by way of limitation, the amount of electronic money (balance) to be used may be determined based on input by a user of the terminal 20 making the payment.

FIG. 8D is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of Fig. 8-4 is a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, and is the same as the left side of Fig. 8-1. When the "Code Payment" icon IC2 is tapped, the code payment screen in the center of Fig. 8-4 is displayed.

As mentioned above, the information displayed in the wallet code information display area WCR1 on this code payment screen is the combined balance of the restricted electronic money balance and the normal electronic money balance (in this example, "1,500 yen"). Also, below this is a slide button for selecting whether or not to use the restricted electronic money for payment. By turning the slide button "ON," it is possible to set the restricted electronic money to be used for payment. Also, by turning the slide button "OFF," it is possible to set the restricted electronic money not to be used for payment.

In this example, the slide button is shown in the "ON" state. In this case, as in Figure 8-1, the restricted electronic money is used preferentially, and any shortfall can be made up with normal electronic money. The payment process is carried out based on this, and the payment result information on the right side of Figure 8-4 is displayed.

In addition, unlike this example, regular electronic money may be used preferentially by turning the slide button "ON." In this case, it is possible to set it so that restricted electronic money cannot be used for payment by turning the slide button "OFF."

FIG. 8-5 is a flowchart showing an example of the flow of processes executed by each device in this modified example.
As an example and not a limitation, when the control unit 21 of the terminal 20A displays the wallet code information (A130), based on user input to the input/output unit 23, the control unit 21 transmits limited electronic money usage selection information including a setting as to whether or not to use the limited electronic money balance and the normal electronic money balance via the communication I/F 22 to the server 10 (A510).

When the communication I/F 14 receives the restricted electronic money use selection information from the terminal 20A, the control unit 11 of the server 10 executes a usage balance calculation process based on the restricted electronic money use selection information (S500). Then, based on the calculated first payment amount and second payment amount, it executes a consecutive restricted payment process (S510).

In the balance usage calculation process, by way of example and not limitation, if only the restricted electronic money balance is used, the "second payment amount" can be set to "0", and if only the normal electronic money balance is used, the "first payment amount" can be set to "0".

When the control unit 11 of the server 10 does not receive restricted electronic money usage selection information from the terminal 20A, the control unit 11 of the server 10 may, by way of example and not limitation, execute a usage balance calculation process based on the usage balance priority (usage ratio) preset by the user of the server 10, and may or may not execute a continuous restricted payment process.

In addition, if the continuous limited payment process fails because the limited electronic money use selection information selects not to use the limited electronic money balance or the normal electronic money balance, the control unit 11 of the server 10 may be configured to transmit limited electronic money use confirmation information to the terminal 20A via the communication I/F 14 to confirm whether or not to re-execute the payment using both balances. When the control unit 21 of the terminal 20A receives the limited electronic money use confirmation information from the server 10, the control unit 21 may transmit the limited electronic money use selection information to the server 10 again if it is selected to re-execute the payment using the limited electronic money balance and the normal electronic money balance based on user input to the input/output unit 23, etc. Thereafter, the control unit 11 of the server 10 may re-execute the usage balance calculation process and the continuous limited payment process based on the re-sent limited electronic money use selection information.

The selection of the balance to be used for payment is not limited to each time a payment is made. As a non-limiting example, prior to a payment, the control unit 21 of the terminal 20A accepts a default setting regarding which balance, the restricted electronic money balance or the normal electronic money balance, is to be used for the payment, based on user input to the input/output unit 23, etc. Then, as a non-limiting example, in a payment after accepting the default setting, when the control unit 21 of the terminal 20A displays wallet code information (A130), the control unit 21 of the terminal 20A may transmit the default setting to the server 10 as restricted electronic money use selection information.

This modified example shows a configuration in which the limited electronic money balance (not limiting, an example of a first electronic currency) and the normal electronic money balance (not limiting, an example of a second electronic currency) are selected based on input by a user of terminal 20A (not limiting, an example of an information processing device).
As an example of an effect of an embodiment obtained by such a configuration, it becomes possible for a user of an information processing device to select the first electronic currency and the second electronic currency to be used for payment, thereby improving convenience for the user of the information processing device.

<Eighth Modification (2)>
In the above embodiment, the first payment amount and the second payment amount are determined according to the usage balance priority order set in advance by the user of the server 10, by way of example and not limitation, but are not limited thereto.
By way of example and not limitation, the usage balance priority may be determined based on input by a user of the payment terminal 20 .

FIG. 8-6 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of Fig. 8-6 shows the main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, in which the "Code Payment" icon IC2 has been tapped. Then, the code payment screen in the center of Fig. 8-6 is displayed.
On this code payment screen, the information displayed in the wallet code information display area WCR1 is the limited electronic money balance ("Limited") and the normal electronic money balance (Unlimited), with the limited electronic money balance ("Limited") displayed at the top and the normal electronic money balance (Unlimited) displayed below.

As a non-limiting example, when user A. A touches the display location of the regular electronic money balance and slides it toward the display location of the restricted electronic money balance (upward in this example), the display locations of the regular electronic money balance and the restricted electronic money balance are swapped, as shown on the right side of Figure 8-6, with the regular electronic money balance displayed on top and the restricted electronic money balance displayed below it. This swaps the priority order of balance usage, and the regular electronic money balance is now used preferentially.

In addition, instead of this example, a check box or the like may be used to allow the user to select the electronic money balance that they would prefer to use.

8-5, the control unit 21 of the terminal 20A displays wallet code information (A130), and then transmits limited electronic money use selection information including a setting regarding the usage balance priority order between the limited electronic money balance and the normal electronic money balance based on a user input to the input/output unit 23 via the communication I/F 22 to the server 10 (A510). Note that the limited electronic money use selection information may include information regarding the usage ratio of each balance.
When the control unit 11 of the server 10 receives the restricted electronic money use selection information from the terminal 20A via the communication I/F 14, the control unit 11 of the server 10 executes the usage balance calculation process (S500) based on the usage balance priority (usage ratio) of the restricted electronic money use selection information, and executes the continuous restricted payment process (S510). Note that, when the control unit 11 of the server 10 does not receive the restricted electronic money use selection information from the terminal 20A, it may, but need not, execute the usage balance calculation process and execute the continuous restricted payment process based on the usage balance priority (usage ratio) preset by the user of the server 10, for example and not by way of limitation.

If the consecutive limited payment process fails, the control unit 11 of the server 10 may transmit limited electronic money use confirmation information to the terminal 20A via the communication I/F 14 to confirm whether or not to re-execute the payment with different first and second payment amounts. When the control unit 21 of the terminal 20A receives the limited electronic money use confirmation information from the server 10, the control unit 21 may transmit limited electronic money use selection information to the server 10 again if it is selected to set different first and second payment amounts and re-execute the payment based on user input to the input/output unit 23, etc. Thereafter, the control unit 11 of the server 10 may re-execute the usage balance calculation process and the consecutive limited payment process based on the re-sent limited electronic money use selection information.

Furthermore, the balance usage priority is not limited to being selected each time a payment is made. As a non-limiting example, prior to a payment, the control unit 21 of the terminal 20A accepts a default setting regarding the balance usage priority between the restricted electronic money balance and the normal electronic money balance based on user input to the input/output unit 23, etc. Then, in a payment after accepting the default setting, as a non-limiting example, when the control unit 21 of the terminal 20A displays wallet code information (A130), the control unit 21 of the terminal 20A may transmit the default setting to the server 10 as restricted electronic money usage selection information.

In this modified example, the set conditions are conditions set by the user of the terminal 20 making the payment.
As an example of the effect of this modified example obtained by such a configuration, the first electronic currency and the second electronic currency to be used for settlement can be selected based on conditions reflecting the intentions of the user of the information processing device.

In addition, this modified example shows a configuration in which the conditions set by the user of the terminal 20 making the payment include a condition regarding the use from a limited electronic money balance (not a limitation, but an example of electronic currency with a set limit).
As an example of the effect of the embodiment obtained by such a configuration, since electronic currency with a set limit is used for settlement, settlement according to the intention of the user of the information processing device can be realized.

In addition, this modified example shows a configuration in which the conditions set by the user of the terminal 20 making the payment include a condition regarding use in the order set by the user of the terminal 20 making the payment (not limited to this, but an example of an information processing device).
As an example of an effect of an embodiment obtained by such a configuration, since electronic currency is used for payment in the order set by the user of the information processing device, payment can be realized in accordance with the intentions of the user of the information processing device.

In addition, this modified example shows a configuration in which the condition regarding use in the order set by the user of the terminal 20 making the payment includes a condition regarding use in order starting from the limited electronic money balance (not a limitation, but an example of electronic currency with a set limit).
As an example of the effect of the embodiment obtained by such a configuration, electronic currency for which a limit is set can be preferentially used for settlement.

<Eighth Modification (3)>
In the above embodiment, after executing the consecutive limited payment process, the server 10 transmits payment result information including the used limited electronic money balance and the normal electronic money balance to the terminal 20A, but this is not limited to this.
As an example and not a limitation, in a payment process with consecutive restrictions, the control unit 11 of the server 10 may be configured to transmit the first payment amount and the second payment amount to the terminal 20A once the first payment amount and the second payment amount are determined.

FIG. 8-7 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
On the code payment screen on the left side of Figure 8-7, when the wallet code information displayed in the wallet code information display area WCR1 is read by the store's code reader, the display shown in the center of Figure 8-7 is displayed.

In this example, the restricted electronic money usage confirmation information transmitted from the server 10 is displayed so as to be superimposed on a part of the wallet code information display area WCR1.
In this example, by way of example and not limitation, restricted electronic money use confirmation information including the first payment amount in addition to the payee and payment amount is transmitted to terminal 20A. As a result, by way of example and not limitation, restricted electronic money use confirmation information including the payee ("XX Bookstore" in this example), the payment amount ("1,200 yen" in this example), and the first payment amount ("1,000 yen" of restricted electronic money in this example) is displayed.

In addition, in this example, the restricted electronic money usage confirmation information includes a "Pay" button BT81 for agreeing to use the first payment amount, and a "Cancel" button BT82 for refusing to use the first payment amount.

As a non-limiting example, when the "Pay" button BT81 is tapped, the server 10 executes a consecutive restricted payment process, and the payment result information on the right side of FIG. 8-7 is displayed. Specifically, it shows that the restricted electronic money is used preferentially, and the first payment amount (in this example, "1,000 yen") is paid from the restricted electronic money, and the second payment amount (in this example, "200 yen") is paid from the normal electronic money.

In this example, only the first payment amount among the payment amounts is displayed on the screen in the center of FIG. 8-7, but this is not limiting.
Specifically, by way of example and not limitation, both the first payment amount and the second payment amount may be displayed. In this case, the server 10 may transmit restricted electronic money usage confirmation information including the first payment amount and the second payment amount to the terminal 20A.

FIG. 8-8 is a flowchart showing an example of the flow of processes executed by each device in this modified example.
When the server 10 receives the payment request information from the store POS system 40 via the communication I/F 14, the control unit 11 of the server 10 calculates the first payment amount and the second payment amount (S500). Then, the control unit 11 of the server 10 transmits the limited electronic money usage confirmation information including at least the calculated first payment amount to the terminal 20A via the communication I/F 14.

When the communication I/F 22 receives the restricted electronic money use confirmation information from the server 10, the control unit 21 of the terminal 20A causes the display unit 24 to display a confirmation screen for asking whether or not to agree to the use of the first payment amount (A520). By way of example and not of limitation, if consent to spending the first payment amount from the restricted electronic money balance is selected based on the input (user operation) to the input/output unit 23 of the terminal 20A (A520: YES), the control unit 21 of the terminal 20A transmits the restricted electronic money use permission information to the server 10 via the communication I/F 22 (A530).

When the communication I/F 14 receives the limited electronic money use permission information from the terminal 20A (S530: YES), the control unit 11 of the server 10 executes the payment process with the consecutive limit (S510). When the communication I/F 14 does not receive the limited electronic money use permission information (S530: NO), the control unit 11 of the server 10 skips the payment process with the consecutive limit.

If consent to spending the first payment amount from the limited electronic money balance is not selected (A520: NO), the control unit 21 of terminal 20A skips step A530.

When consent to spending the first payment amount from the limited electronic money balance is not selected (A520: NO), the control unit 21 of the terminal 20A accepts the first payment amount and the second payment amount based on user input to the input/output unit 23, for example and not by way of limitation, and transmits the first payment amount and the second payment amount to the server 10 via the communication I/F 22. When the control unit 11 of the server 10 receives the first payment amount and the second payment amount from the terminal 20A, it may execute a consecutive limited payment process based on the received first payment amount and second payment amount.

<Eighth Modification (4)>
This modification relates to the contents of the notification to the notification destination account.
8 and 9 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of Fig. 8-9 shows the state where the payment result information is displayed on the display unit 24 of the terminal 20A. In this example, the first payment amount from the limited electronic money balance is "700 yen", the second payment amount from the normal electronic money balance is "500 yen", and it is shown that a total payment of "1,200 yen" has been made.

The right side of FIG. 8-9 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B in this case.
In this example, restricted electronic money usage information RU81 is displayed below restricted electronic money remittance result information RR81. This electronic money usage information displays information including the amount used for payment (i.e., the first payment amount) from the restricted electronic money balance remitted by user B.B to user A.A.
Specifically, information including the amount used from the limited electronic money balance (in this example, "700 yen"), the payee (in this example, "XX Bookstore"), and a button to confirm details is displayed.

Alternatively, the payment amount (the sum of the first payment amount and the second payment amount) may be displayed in the electronic money usage information.

Ninth Example
In the above-described embodiment, in the consecutive limit payment process, the payment is made using the normal electronic money balance and the limited electronic money balance.
The ninth embodiment is an embodiment in which any two or more of two or more restricted electronic money balances are used to make a settlement.

The contents described in the ninth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

FIG. 9A is a diagram showing an example of the account management database 155H, which is an example of the account management database 155 in this embodiment.
In addition to the application ID and normal electronic money balance, each account management data included in the account management database 155H stores, by way of example and not limitation, restricted electronic money management data, restricted electronic money usage history data, and electronic money usage restriction management data.
The information stored in each account management data included in the account management database 155H is similar to that in the account management database 155F, but the information stored in the electronic money usage restriction management data is partially different.

Specifically, the electronic money usage restriction management data stores, by way of example and not limitation, a remittance management ID and the type of store in which the electronic money can be used in association with each other.

The usable store type is an item for storing the type and format of business in which the limited electronic money balance can be used, and is set and stored based on an input by the remitter, for example and not by way of limitation.
In Fig. 9-1, by way of example and not limitation, it is stored that the restricted electronic money balance managed by the remittance management ID "T02108" can be used at stores and services classified into the industries of "convenience stores,""supermarkets and home improvement centers," and "books and stationery." Also, it is stored that the restricted electronic money balance managed by the remittance management ID "T02571" can be used at stores and services classified into the industries of "books and stationery" and "furniture and home appliances."

<Display screen>
9-2 and 9-3 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of Fig. 9-2 shows the main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, where the balance area shows the electronic money balance of "6,500 yen." The breakdown of this is also shown to be the normal electronic money balance of "2,500 yen" and the restricted electronic money balance of "4,000 yen."

In addition, a button for displaying the breakdown of the restricted electronic money balance is displayed to the left of the balance, and when this button is tapped, the display shown in the center of FIG. 9-2 is displayed.
Specifically, the breakdown of the restricted electronic money balance is displayed below the display portion of the restricted electronic money balance. In this example, the breakdown of the restricted electronic money balance "4,000 yen" is shown to be "1,000 yen" for the user of the notification destination account named user B.B, and "3,000 yen" for the user of the notification destination account named user C.C.

As shown in the center screen of FIG. 9-2, when the restriction mark RMK displayed in association with the balance of "3,000 yen" for the user of the notification account named user C.C. is tapped, information about the restriction is displayed in a speech bubble, by way of example and not limitation. In this example, the types of stores in which the restricted electronic money can be used are displayed as icons. Specifically, an icon for "books and stationery" and an icon for "furniture and home appliances" are displayed in the speech bubble, indicating that the restricted electronic money for the user of the notification account named user C.C. can be used in these two types of stores.

On the other hand, as shown in the screen on the right side of FIG. 9-2, when the restriction mark RMK displayed in association with the balance of "1,000 yen" for the user of the notification account named User B.B is tapped, information about the restriction is displayed in a speech bubble, not as a limitation, but as an example. In this example, the types of stores in which the restricted electronic money can be used are displayed as icons. Specifically, an icon for "convenience store," an icon for "supermarket/home improvement center," and an icon for "books/stationery" are displayed in the speech bubble, indicating that the restricted electronic money for the user of the notification account named User B.B can be used in these three types of stores.

The left side of Fig. 9-3 corresponds to the left side of Fig. 9-2 and shows the state where the "Pay with Code" icon IC2 is tapped. Then, by way of example and not limitation, the pay with code screen in the middle of Fig. 9-3 is displayed.
In this code payment screen, the wallet code information display area WCR1 displays the balance, which is the same as the balance display area BR2 on the screen on the left side of Fig. 9-2. When the wallet code information is read by a code reader at the store, the server 10 executes a payment process with a consecutive limit, and the payment result information on the right side of Fig. 9-3 is displayed.

Specifically, it shows that "1,000 yen" was used for payment from the restricted electronic money account of user B.B, and "200 yen" was used for payment from the restricted electronic money account of user C.C.

In this example, both the restricted electronic money whose notification account is the account of user B.B and the restricted electronic money whose notification account is the account of user C.C are used for the payment. Therefore, the server 10 transmits the restricted electronic money usage information to each of the terminals 20B and 20C.

<Processing>
As a non-limiting example of the process, in the used balance calculation process (S500) in Figures 8-2 to 8-3, the control unit 11 of the server 10 calculates a third payment amount to be paid from the first limited electronic money balance and a fourth payment amount to be paid from the second limited electronic money balance out of the payment amount in the payment request information.
As an example and not by way of limitation, in FIG. 9-1, the balance of remittance management ID "T02108" can be applied to the first limited electronic money balance, and the balance of remittance management ID "T02571" can be applied to the second limited electronic money balance.

Here, the third payment amount and the fourth payment amount are any amounts that satisfy the condition "third payment amount" + "fourth payment amount" = "payment amount in payment request information". However, as a non-limiting example, the server 10 determines the usage limit of each limited electronic money balance based on the payment request information received, and if each limited electronic money balance cannot be used, the payment amount is set to "0". In other words, if the usage limit of the first limited electronic money balance is met and the balance cannot be used, the "third payment amount" = "0", and if the usage limit of the second limited electronic money balance is met and the balance cannot be used, the "fourth payment amount" = "0".

If the first limited electronic money balance and the second limited electronic money balance are available, the third payment amount and the fourth payment amount may be determined according to the following usage balance priority order, by way of example and not by way of limitation:
- Priority is given to using restricted electronic money balances with larger balances.
- Prioritize the use of restricted electronic money balances with small balances.
- Priority will be given to the use of restricted electronic money balances that were received the oldest.
・Used in order of strictest limit on available electronic money balance.
- Any combination of the above.

As a non-limiting example, the following is an example of a case where the limit on the first limited electronic money balance is stricter than the limit on the second limited electronic money balance.
The number of recipients of the first limited electronic money balance usage notification is greater than the number of recipients of the second limited electronic money balance usage notification (the number of recipients is greater).
The number of stores and service providers where the first restricted electronic money balance can be used is less than the number of stores and service providers where the second restricted electronic money balance can be used (few stores and service providers where it can be used).
The number of types of stores and industries in which the first limited electronic money balance can be used is less than the number of types of stores and industries in which the second limited electronic money balance can be used (narrow range of types of stores and industries in which the electronic money can be used).
The number of products and services that can be used with the first limited electronic money balance is less than the number of products and services that can be used with the second limited electronic money balance (few products and services can be purchased).
The expiration date for the first restricted electronic money balance is less than the expiration date for the second restricted electronic money balance (the expiration date for the balance becoming unusable is approaching).
The location area in which the first limited electronic money balance can be used is smaller than the location area in which the second limited electronic money balance can be used (the usable map range is narrow).
The time during which the first limited electronic money balance can be used within a specified time period (for example, one week, but not limited to this) is less than the time during which the second limited electronic money balance can be used within a specified time period (there are fewer time periods during which it can be used).
- The number of days during which the first limited electronic money balance can be used within a specified period (for example, but not limited to, one month) is less than the number of days during which the second limited electronic money balance can be used within a specified period (fewer days and times when it can be used).
- Any combination of the above.

When the third payment amount and the fourth payment amount are calculated, the control unit 11 of the server 10 performs a consecutive limited payment process (S510). In the consecutive limited payment process, the control unit 11 of the server 10 sequentially executes, as an example and not a limitation, a limited payment process using the first limited electronic money balance for the third payment amount, and a limited payment process using the second limited electronic money balance for the fourth payment amount.

If both restricted payment transactions are successful, the consecutive restricted payment transaction is successful.
If at least one of the restricted payment processes fails, the consecutive restricted payment processes will fail (cannot be paid). If the consecutive restricted payment processes fail, by way of example and not by way of limitation, any of the restricted payment processes that have succeeded in the payment will be cancelled and the balance will be returned.
If the third payment amount is "0", the limited payment process using the first limited electronic money balance may not be executed. If the fourth payment amount is "0", the limited payment process using the second limited electronic money balance may not be executed. In these cases, the limited payment process that is not executed is treated as successful.

In addition, in the consecutive limited payment process, the normal electronic money balance may be used in addition to the first limited electronic money balance and the second limited electronic money balance. As a non-limiting example, let us assume that "third payment amount" + "fourth payment amount" < "payment amount in payment request information". In the case where the limited electronic money balance is used in priority over the normal electronic money balance as a usage balance priority order, the second payment amount paid from the normal electronic money balance in the usage balance calculation process can be calculated as "second payment amount" = "payment amount in payment request information" - "third payment amount" - "fourth payment amount". In addition, the normal electronic money balance may be used in priority over the limited electronic money balance.

In addition, in this embodiment, for the sake of simplicity, a case has been described in which there are two remittance management IDs stored in the restricted electronic money management data, but this is not limiting. As a non-limiting example, a case in which there are three or more remittance management IDs stored in the restricted electronic money management data can also be handled by setting the usage balance priority of the restricted electronic money balance in the same manner as in this embodiment.

<Effects of the ninth embodiment>
This embodiment illustrates a configuration in which a first limited electronic money balance (not limiting, but an example of a first electronic currency) and a second limited electronic money balance (not limiting, but an example of a second electronic currency) are selected based on preferential use of the limited electronic money balance with the smaller balance (not limiting, but an example of a set condition).
As an example of the effect of the embodiment obtained by such a configuration, the first electronic currency and the second electronic currency to be used for settlement can be appropriately selected based on the set conditions.

Furthermore, this embodiment shows a configuration in which the set conditions include a condition regarding use from a first restricted electronic money balance (not a limitation, but an example of electronic money with a set limit).
As an example of the effect of the embodiment obtained by such a configuration, electronic currency for which a limit is set can be preferentially used for settlement.

In addition, this embodiment shows a configuration in which the condition regarding the use of electronic currency with restrictions set thereon includes the use of electronic currency with stricter restrictions first.
As an example of the effect of the embodiment obtained by such a configuration, electronic currency with stricter restrictions can be preferentially used for settlement.

In addition, this embodiment shows a configuration in which the use of electronic currency with stricter restrictions first includes at least a case in which the balance of electronic currency is small or the usable category is narrow.
As an example of the effect of the embodiment obtained by such a configuration, electronic currency with a small balance or electronic currency with a narrow range of usable categories can be preferentially used for settlement.

<Ninth Modification (1)>
In the above embodiment, when the used balance calculation process is executed, the consecutive limited payment process is executed, but the present invention is not limited to this.
As a non-limiting example, when the remaining balance calculation process is executed, the control unit 11 of the server 10 may transmit the third payment amount and the fourth payment amount to the terminal 20A.

FIG. 9D is a diagram showing another example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of FIG. 9-4 is a code payment screen of the payment application displayed on the display unit 24 of the terminal 20A, which corresponds to the screen in the center of FIG. 9-3.
When the wallet code information is read by a code reader at the store, a display like that shown in the center of Figure 9-4 is displayed.

Specifically, the restricted electronic money usage confirmation information transmitted from the server 10 is displayed so as to be superimposed on a part of the wallet code information display area WCR1.
In this example, by way of example and not limitation, the payment destination (in this example, "YY Camera"), the payment amount (in this example, "3,800 yen"), as well as information regarding the restricted electronic money to be used for the payment are displayed.

In this example, there is restricted electronic money with a notification account belonging to user B.B, and restricted electronic money with a notification account belonging to user C.C, but the payment destination is "YY Camera" and the store's type of business is "furniture and home appliances." Therefore, the restricted electronic money permitted for use in the "furniture and home appliances" type of business is selected as the restricted electronic money to make the payment. As a result, the restricted electronic money with a notification account belonging to user C.C is selected, and information is displayed to confirm to user A.A that the payment will be made using this restricted electronic money.

As a non-limiting example, when the "Pay" button BT81 is tapped, the server 10 executes a continuous restricted payment process, and the payment result information on the right side of FIG. 9-4 is displayed. Specifically, it shows that "13,000 yen" was used for payment from the restricted electronic money, which is the account of user C.C., and the shortfall of "800 yen" was used for payment from the regular electronic money.

In this example, in the screen in the center of FIG. 9-4, only the amount (in this example, "3,000 yen") used for payment from the restricted electronic money whose notification account is the account of user C.C. is displayed in the restricted electronic money usage confirmation information, but the present invention is not limited to this.
In addition, in the above example, the amount "800 yen" used for payment from regular electronic money may also be displayed.
Furthermore, in the above example, the payment amount "0 yen" of the restricted electronic money that is not used for payment, that is, the payment amount "0 yen" of the restricted electronic money whose notification destination account is the account of user B.B. may also be displayed.

8-8, the control unit 11 of the server 10 transmits limited electronic money use confirmation information including the calculated third payment amount and/or fourth payment amount to the terminal 20A via the communication I/F 14. Then, as a non-limiting example, when consent to spending the third payment amount and/or the fourth payment amount from the limited electronic money balance is selected based on an input (user operation) to the input/output unit 23 of the terminal 20A, the control unit 21 of the terminal 20A transmits limited electronic money use permission information to the server 10 via the communication I/F 22.
The limited electronic money usage confirmation information may include the second payment amount, which is the amount of the normal electronic money balance used.

<Ninth Modification (2)>
In the above embodiment, each payment amount is automatically calculated in the remaining balance calculation process, but the present invention is not limited to this.
By way of example and not limitation, the amount of each payment may be calculated based on input by a user of the terminal 20 making the payment.

8-5, the process in this modified example, by way of example and not limitation, transmits limited electronic money use selection information including settings regarding the usage balance priority order for each limited electronic money balance and normal electronic money balance to the server 10 via the communication I/F 22 based on a user input to the input/output unit 23. Then, the control unit 11 of the server 10 executes a usage balance calculation process based on the balance usage priority order.
The restricted electronic money use selection information may include information specifying the restricted electronic money balance (normal electronic money balance) to be used for payment.

The priority order of the usage balance in the restricted electronic money usage selection information is not limited to the following examples.
Specify the balance usage order for each remittance management ID (as an example and not a limitation, based on a user operation on the balance display field, specify the balance usage order as follows: balance of remittance management ID "T02571"> balance of remittance management ID "T02108">"regular electronic money balance").
-Specify that the balance will be used in order of lowest (highest).
-Specify that the restricted electronic money balance is used in the order of receipt, starting with the oldest.
Directly specify each payment amount (as an example, not a limitation, if the payment amount in the payment request information is "1500 yen", specify the third payment amount = "1000 yen" and the fourth payment amount = "500 yen".)
・Specify to use according to the ratio of each balance.

In this modified example, the set conditions include a condition regarding use in an order set by the user of the terminal 20 making the payment.
As an example of an effect of an embodiment obtained by such a configuration, since electronic currency is used for payment in the order set by the user of the information processing device, payment can be realized in accordance with the intentions of the user of the information processing device.

In addition, this modified example shows a configuration in which the condition regarding use in the order set by the user of the terminal 20 making the payment includes a condition regarding use in the order starting with electronic currency for which restrictions are set.
As an example of the effect of an embodiment obtained by such a configuration, electronic currency with restrictions set can be used preferentially for payment, thereby realizing payment in line with the wishes of the user of the information processing device.

<Ninth Modification (3)>
In the above embodiment, the usage balance calculation process is executed in the server 10, but this is not limited to this. As a non-limiting example, a part or all of the processing of the usage balance calculation process may be executed in the terminal 20.

By way of example and not limitation, the remaining balance calculation process can be broadly divided into a remaining balance selection process and a payment amount calculation process.
The usage balance calculation process is a process for selecting a balance to be used for payment from one or more restricted electronic money balances and a normal electronic money balance, and the payment amount calculation process is a process for setting a usage balance priority order for the selected balances and calculating the amount to be paid from each balance.

Figure 9-5 shows an example of a processing method for the used balance selection process.

In the selection pattern "select balance each time," the control unit 21 of the terminal 20 selects the balance the user will use for the payment each time a payment is made, based on, for example but not limited to, the selection of a check box corresponding to each balance displayed on the display unit 24.

In the selection pattern "Default Balance Selection (1)", the control unit 21 of the terminal 20 sets the default settings for balance selection to be used by the user for payment (hereinafter referred to as "balance selection default settings") based on, for example and not by way of limitation, the selection of check boxes corresponding to each balance displayed on the display unit 24 before making a payment. Then, when making a payment, the control unit 21 of the terminal 20 selects the balance to be used by the user for payment based on the balance selection default settings.

In selection pattern "Specified Balance Selection (2)", the control unit 21 of the terminal 20 sets the balance selection specification settings in the same way as in Specified Balance Selection (1), and then transmits the balance selection specification settings to the server 10 via the communication I/F 22. Then, when making a payment, the control unit 11 of the server 10 selects the balance to be used by the user for the payment based on the received balance selection specification settings.

The "all selection" selection pattern is a pattern in which the system selects to use the entire balance. In this case, the balance usage selection process may not be executed.

Figure 9-6 shows an example of a processing method for setting the balance usage priority order.

In the processing pattern "fully automatic processing (1)", the control unit 11 of the server 10 sets the priority order of the used balance in accordance with the defined system settings, and calculates the amount to be paid from each balance.
In the processing pattern "fully automatic processing (2)", the control unit 21 of the terminal 20 sets the priority order of the used balance in accordance with the defined system settings, and calculates the amount to be paid from each balance.
Fully automatic processing is processing that does not involve the will of the user of the terminal 20 making the payment.

In the processing pattern "Suggestion Processing (1)", the control unit 11 of the server 10 sets the priority order of the used balance according to the specified system settings, calculates the amount to be paid from each balance, and when the user of the terminal 20 approves each calculated payment amount, the consecutive limit set payment processing is executed.
In the processing pattern "Suggestion Processing (2)", the control unit 21 of the terminal 20 sets the priority order of the used balance according to the specified system settings, calculates the amount to be paid from each balance, and when the user of the terminal 20 approves each calculated payment amount, the consecutive limit payment processing is executed.
The suggestion process is a process in which the user of the terminal 20 approves each payment amount determined by the system.

In the processing pattern "default setting process (1)", by way of example and not limitation, default balance usage priority levels are set prior to payment based on user operations on the terminal 20. Then, the control unit 11 of the server 10 calculates the amount to be paid from each balance based on the default balance usage priority levels.
In the processing pattern "default setting process (2)", by way of example and not limitation, default balance usage priority levels are set prior to payment based on user operations on the terminal 20. The control unit 21 of the terminal 20 then calculates the amount to be paid from each balance based on the default balance usage priority levels.
The default setting process is a process in which each payment amount is calculated based on the default balance usage priority order set by the user of the terminal 20 before payment.

In the processing pattern "prescribed confirmation processing (1)", the user of the terminal 20 approves each payment amount calculated in the "prescribed setting processing (1)" before the execution of the consecutive limit-attached settlement processing.
In the processing pattern "prescribed confirmation processing (2)", the user of the terminal 20 approves each payment amount calculated in the "prescribed setting processing (2)" before the execution of the consecutive limit-applied settlement processing.

In the processing pattern "each-time setting processing (1)", the priority order of the used balance is set each time a payment is made based on the user's operation on the terminal 20. Then, the control unit 11 of the server 10 calculates the amount to be paid from each balance based on the set priority order of the used balance.
In the processing pattern "each-time setting processing (2)", the priority order of the used balance is set each time a payment is made based on the user's operation on the terminal 20. Then, the control unit 21 of the terminal 20 calculates the amount to be paid from each balance based on the set priority order of the used balance.
The each-time setting process is a process in which the user of the terminal 20 sets the used balance priority order and calculates each payment amount each time a payment is made.

In this modified example, the set conditions are conditions set by the user of the terminal 20 making the payment.
As an example of the effect of this modified example obtained by such a configuration, the first electronic currency and the second electronic currency to be used for settlement can be selected based on conditions reflecting the intentions of the user of the information processing device.

In addition, this modified example shows a configuration in which the conditions set by the user of the terminal 20 making the payment include a condition regarding the use from a limited electronic money balance (not a limitation, but an example of electronic currency with a set limit).
As an example of the effect of this modified example obtained by such a configuration, since electronic currency with a set limit is used for payment, payment can be realized in accordance with the intention of the user of the information processing device.

In addition, this modified example shows a configuration in which the condition regarding the use of electronic currency with restrictions set thereon includes the use of electronic currency with stricter restrictions first.
As an example of the effect of this modified example obtained by such a configuration, electronic currency with stricter restrictions can be preferentially used for settlement.

In addition, this modified example shows a configuration in which the use of electronic currency with stricter restrictions first includes at least a case in which the balance of electronic currency is small or the usable category is narrow.
As an example of the effect of this modified example obtained by such a configuration, electronic currency with a small balance or electronic currency with a narrow range of usable categories can be preferentially used for settlement.

In addition, this modified example shows a configuration in which the conditions set by the user of the terminal 20 making the payment include a condition regarding use in the order set by the user of the terminal 20 making the payment (not limited to this, but an example of an information processing device).
As an example of an effect of an embodiment obtained by such a configuration, since electronic currency is used for payment in the order set by the user of the information processing device, payment can be realized in accordance with the intentions of the user of the information processing device.

In addition, this modified example shows a configuration in which the condition regarding use in the order set by the user of the terminal 20 making the payment includes a condition regarding use in order starting from the limited electronic money balance (not a limitation, but an example of electronic currency with a set limit).
As an example of the effect of the modified example obtained by such a configuration, electronic currency for which a restriction is set can be preferentially used for settlement.

<Ninth Modification (4)>
In the above embodiment, when multiple notification-attached restricted electronic money balances (notification-attached electronic money balances) are used, notification is sent to all notification destination accounts, but this is not limited to this. As a non-limiting example, when a restricted electronic money balance whose notification destination account is user B.B and a restricted electronic money balance whose notification destination account is user C.C are used, the control unit 11 of the server 10 may send a notification to only one of the terminal 20B of user B.B or the terminal 20C of user C.C.

In addition, a priority order may be set for the notification destination accounts, and the control unit 11 of the server 10 may be configured to send notifications only to the terminal 20 of the notification destination account with the highest priority order. The control unit 11 of the server 10 may be configured to send notifications to the terminals 20 of the notification destination accounts with the highest priority order up to "N" (where "N" is any natural number).

In addition, if two or more notification-enabled restricted electronic money balances (notification-enabled electronic money balances) are used in a payment and the notification destination accounts span multiple accounts, the control unit 11 of the server 10 may choose not to send a notification.

<Ninth Modification (5)>
When a refund occurs, such as when returning a product or service, the amount to be refunded may be added to each of the multiple restricted electronic money balances and/or normal electronic money balances used at the time of payment, based on the amount used at the time of payment.

In this case, when refunding at least a portion of the restricted electronic money (normal electronic money) used by the user of the remittance destination account, the control unit 11 of the server 10 identifies the payment ID sent from the store POS system 40 from the payment history management data 157. This is to confirm whether or not a payment has been made and to identify the payment amount (refund amount).

Next, the control unit 11 of the server 10 refers to the restricted electronic money usage history data contained in the account management data of the user of the remittance destination account in the account management database 155H, and identifies the remittance management ID corresponding to the identified payment ID. If multiple restricted electronic money are used at the time of payment, this remittance management ID will include multiple IDs.

If there is a remittance management ID that corresponds to the identified payment ID, it means that at least a portion of the restricted electronic money has been used for the payment. Therefore, the amount used that corresponds to the identified payment ID is identified from the restricted electronic money usage history data, and this amount used is added to the restricted electronic money balance of the corresponding remittance management ID in the restricted electronic money management data. If there are multiple remittance management IDs that correspond to the identified payment ID, the above process is repeated for each remittance management ID.

The control unit 11 of the server 10 then calculates the sum of the amounts used for each remittance management ID corresponding to the identified payment ID. This sum is referred to as the "limited electronic money payment amount."
The control unit 11 of the server 10 determines whether the limited electronic money payment amount is equal to the payment amount corresponding to the payment ID. If the limited electronic money payment amount is equal to the payment amount, the normal electronic money has not been used for the payment. Therefore, the control unit 11 of the server 10 ends the process.
If the limited electronic money payment amount is not equal to the payment amount, normal electronic money has also been used for the payment, so the control unit 11 of the server 10 adds the amount calculated by subtracting the limited electronic money payment amount from the normal electronic money balance.

On the other hand, if there is no remittance management ID corresponding to the identified payment ID, it means that the restricted electronic money was not used for the payment. Therefore, the refund amount is added to the normal electronic money balance. If the payment was made using only normal electronic money, the payment amount corresponding to the identified payment ID in the payment history management data 157 becomes the refund amount to the normal electronic money balance.

Tenth Example
The tenth embodiment is an embodiment in which, before making a payment by a settlement process with consecutive limits, the user of the terminal 20 can confirm the total balance available for the payment, taking into account the limit on the limited electronic money balance.

The contents described in the tenth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Display screen>
10-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment. Here, the limited electronic money balance is the same as that shown in FIG. 9-2.
The left side of FIG. 10-1 shows a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, and is an example of the screen displayed when the terminal 20A is located at the store "XX Bookstore."
Based on the method described below, store introduction information regarding the store "XX Bookstore" is sent from the server 10 to the terminal 20A, and as a result, the store introduction information including the words "Welcome to XX Bookstore! Spring reference book fair now on!" is displayed at the bottom of the screen.
The balance display area also displays the combined usable balance, which is the sum of the limited electronic money balance and the normal electronic money balance that the user A.A can use at the store "XX Bookstore."

Here, the breakdown of the electronic money balance and the contents of the restrictions in this example are the same as those shown in FIG. 9-2 of the ninth embodiment.
Specifically, the normal electronic money balance is "2,500 yen" and the limited electronic money balance is "4,000 yen."
In addition, the balance of the restricted electronic money with the notification destination account being the account of user C.C. is "3,000 yen", and the types of stores where the electronic money can be used are set to "books and stationery" and "furniture and home appliances".
In addition, among the limited electronic money balances, the balance of the limited electronic money with the notification account set to the account of user B.B is "1,000 yen", and the types of stores where the electronic money can be used are set to "convenience store", "supermarket/home center", and "book/stationery".

The example screen on the left side of Figure 10-1 shows a case where terminal 20A is located at the store "XX Bookstore." Since both of the restricted electronic money mentioned above can be used at stores in the "Bookstore/Stationery" industry, the full amount can be used.
Therefore, the balance display area displays the combined usable balance as "2,500 yen + 4,000 yen = 6,500 yen", which is the sum of the normal electronic money balance and the full amount of the limited electronic money balance.

On the other hand, the screen in the center of FIG. 10-1 is a diagram showing an example of a main menu screen when the terminal 20A is located at the store "MM Supermarket."
Of the two types of restricted electronic money described above, the only restricted electronic money that can be used at a store in the "super home improvement" business type is the restricted electronic money with the notification account being the account of user B.B.
Therefore, in the balance display area, the sum of the normal electronic money balance and the balance of the restricted electronic money whose notification account is the account of user B.B., "2,500 yen + 1,000 yen = 3,500 yen", is displayed as the combined usable balance.

On the other hand, the screen on the right side of FIG. 10-1 is a diagram showing an example of a main menu screen when the terminal 20A is located at the store "YY Camera."
Of the two types of restricted electronic money, the only type of restricted electronic money that can be used at a store in the "furniture and home appliances" industry is the restricted electronic money whose notification account is the account of user C.C.
Therefore, in the balance display area, the sum of the normal electronic money balance and the balance of the restricted electronic money whose notification account is the account of user C.C., i.e., "2,500 yen + 3,000 yen = 5,500 yen", is displayed as the usable combined balance.

<Processing>
8-2, when the control unit 21 of the terminal 20A causes the display unit 24 to display the restricted electronic money remittance result information (A410), the control unit 21 transmits usable combined balance request information to the server 10 via the communication I/F 22. Here, the usable combined balance request information may include, by way of example and not limitation, a beacon signal received from a beacon device (not shown) installed in the store, or by way of example and not limitation, location information of the terminal 20A indicated by latitude, longitude and altitude based on location calculation information acquired by the location calculation information detection unit 29B.

When the control unit 11 of the server 10 receives the usable combined balance request information from the terminal 20A via the communication I/F 14, the control unit 11 of the server 10 executes a usable combined balance calculation process.
In the usable combined balance calculation process, as a non-limiting example, first, the control unit 11 of the server 10 determines the store where the terminal 20A is located based on the received usable combined balance request information. The control unit 11 of the server 10 then references the electronic money usage restriction management data in the account management database 155H and determines whether each limited electronic money balance stored in the limited electronic money management data is usable or not. Then, the control unit 11 of the server 10 transmits usable combined balance information including the usable combined balance, which is the sum of the usable limited electronic money balance and the normal electronic money balance, to the terminal 20A via the communication I/F 14.
The usable combined balance information may include individual restricted electronic money balances that have been determined to be usable.

When the available combined balance information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20A displays the received available combined balance information on the display unit 24.

In addition, if the date, time, and expiration date when the limited electronic money balance can be used are set as the electronic money usage restriction management data, in the process of calculating the combined usable balance, the control unit 11 of the server 10 may obtain the current date and time using the clock unit 19 and determine whether each limited electronic money balance can be used.

In addition, when the electronic money usage restriction management data specifies products for which the limited electronic money balance can be used, the control unit 21 of the terminal 20A may include the brand logo or product image of the store or service captured by the imaging unit 27 in the usable combined balance request information. In this case, the control unit 11 of the server 10 may identify the product or service to be purchased based on the product image, etc., included in the usable combined balance request information, and determine whether or not each limited electronic money balance can be used.

The usable combined balance calculation process is not limited to being executed by the server 10. As a non-limiting example, when the control unit 21 of the terminal 20A acquires its own terminal account management data from the account management database 155H from the server 10, the control unit 21 may execute the usable combined balance calculation process based on the location information and current date and time of the terminal 20A to calculate the usable combined balance.

<Effects of the Tenth Example>
This embodiment shows a configuration executed by an information processing device in which a control unit performs control to display on the information processing device a usable combined balance (not limiting, an example of the total amount of electronic currency) that can be used for a continuous limited payment process (not limiting, an example of a second payment) among multiple electronic currency available to a user of terminal 20A (not limiting, an example of an information processing device), which includes a first limited electronic money balance (not limiting, an example of a first electronic currency) and a second limited electronic money balance (not limiting, an example of a second electronic currency).
As an example of the effect of an embodiment obtained by such a configuration, it becomes possible to inform a user of an information processing device of the total amount of electronic currency available for the first payment among multiple electronic currency available to the user of the information processing device, including the first electronic currency and the second electronic currency, thereby improving convenience.

<Tenth Modification (1)>
In the above embodiment, the usable combined balance is calculated based on the state (location, date and time, etc.) of the terminal 20A, but this is not limiting.
As a non-limiting example, the available combined balance for each available store type may be calculated and displayed as a list on the display unit 24 of the terminal 20A.

FIG. 10B is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of FIG. 10-2 is a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, and corresponds to the left side of FIG. 10-1.
When the word "Balance" or the display portion of the balance value (in this example, "6,500 yen") in the balance display area is tapped, a display such as that shown on the right side of FIG. 10-2 is displayed, by way of example and not limitation.

In this example, an available balance display area UR2 containing the available combined balance by store type is displayed in a speech bubble below the balance value in the balance display area BR2. In this example, a restriction mark RMK and the words "Available balance by store" are displayed in the available balance display area UR2, and below that, the available combined balance by store type is displayed in association with an icon of the type of store.
Specifically, for the industries "Convenience Stores" and "Supermarkets/Home Centers", the combined usable balance is displayed as "3,500 yen", for the industry "Books/Stationery", the combined usable balance is displayed as "6,500 yen", and for the industry "Furniture/Home Appliances", the combined usable balance is displayed as "5,500 yen".

Note that the targets for which the usable combined balance is calculated as a list are not limited to each store type. As a non-limiting example, when a date on which the limited electronic money balance can be used is specified, the usable combined balance may be displayed corresponding to the date on a calendar. Also, when a time period during which the limited electronic money balance can be used is specified, as a non-limiting example, the usable combined balance for each time period may be displayed inside an analog clock-like display. When a product or service for which the limited electronic money balance can be used is specified, as a non-limiting example, the usable combined balance for each product or service may be displayed, such as "games: 500 yen," "books: 3000 yen," etc. When a store for which the limited electronic money balance can be used is specified, as a non-limiting example, the usable combined balance for each area may be displayed within an area on a map.

This modified example shows a configuration in which the control unit performs control to display on the information processing device a usable combined balance (not a limitation, but an example of a usable amount) for each store type (not a limitation, but an example of a payment category) of multiple electronic currencies usable by a user of the information processing device, including a first electronic currency and a second electronic currency.
As an example of an effect of an embodiment obtained by such a configuration, it becomes possible to inform a user of an information processing device of the amount available for each payment category among multiple electronic currencies available to the user of the information processing device, including the first electronic currency and the second electronic currency, thereby improving convenience.

<Eleventh Example>
The eleventh embodiment is an embodiment that makes it possible to transfer (which may be considered as a refund, return, or return) the remaining balance of a restricted electronic money balance transferred from a user of a remittance source account to a user of a remittance destination account, based on specified conditions, to the user of the remittance source account, etc.

The contents described in the eleventh embodiment are applicable to any of the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Display screen>
11-1 and 11-2 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this embodiment. Here, the limited electronic money balance is the same as that shown in FIG. 9-2.
The left side of Fig. 11-1 is a code payment screen of the payment application displayed on the display unit 24 of the terminal 20A, and when a payment is made based on the wallet code information displayed in the wallet code information display area WCR1, the payment result information shown on the right side of Fig. 11-1 is displayed. In this example, the payment amount is "3,800 yen", and the breakdown shows that "1,000 yen" was paid from the restricted electronic money whose notification account is the account of users B and B, and "2,800 yen" was paid from the restricted electronic money whose notification account is the account of user C.

As a result, the limited electronic money whose notification account is the account of user C.C. is reduced to "3,000 yen - 2,800 yen = 200 yen." Here, a case will be illustrated in which the remaining amount of this limited electronic money, "200 yen," is remitted to the remitter's account based on the fact that this remaining amount, "200 yen," is equal to or less than a predetermined value.
In this example, the remittance source account is the account of user C.C., which is the same as the notification destination account. Therefore, "200 yen" is remitted from user A.A's account to user C.C.'s account via server 10.

The left side of FIG. 11-2 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A in this case.
On the left side of the notice area, payment result information PR1 indicating that a payment has been made is displayed, and below that, restricted electronic money refund information RF1 indicating that restricted electronic money of "200 yen" has been sent to user C.C for the purpose of refund is displayed.

The center of FIG. 11-2 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20C in this case.
On the left side of the notification area, restricted electronic money remittance result information RR91 is displayed, which indicates that restricted electronic money has been remitted to user A.A, and below that, restricted electronic money refund information RF2 is displayed, which indicates that restricted electronic money "200 yen" has been remitted from user A.A for the purpose of refund and that this has been received.

The right side of FIG. 11-2 shows an example of a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A in this case.
As a result of the above payment and refund, the limited electronic money balance of the user A.A's account becomes "0", and only the normal electronic money balance remains. As a result, the balance display area BR2 displays the word "Balance" along with a balance of "2,500 yen" (normal electronic money balance) and the charge button CBT.

<Processing>
FIG. 11-3 is a flow chart showing an example of the flow of processing executed by each device in this embodiment. FIG. 11-3 is executed following FIG. 8-2 by way of example and not by way of limitation.

As a non-limiting example, a consecutive limited payment process is executed (S510), and payment result information is transmitted (S150). The control unit 11 of the server 10 then determines whether or not there is a limited electronic money balance that is equal to or less than a predetermined value among the limited electronic money balances after the consecutive limited payment process (S610).

Here, the predetermined value is, for example and not limitation, a balance determined by the user of the server 10 or the user of the terminal 20 (for example and not limitation, "200 yen"). The control unit 11 of the server 10 may be configured to determine whether or not there is a limited electronic money balance that is less than the predetermined value. Also, it may or may not be configured to determine (S610) whether or not there is a limited electronic money balance that is equal to or less than the predetermined value among the limited electronic money balances after the limited payment process.

If there is a limited electronic money balance that is below the predetermined value (S610: YES), the control unit 11 of the server 10 executes the limited electronic money return process (S620). In the limited electronic money return process, the control unit 11 of the server 10 references the limited electronic money management data in the account management database 155H and searches for a remittance management ID whose limited electronic money balance is below the predetermined value. Then, it remits (refunds/returns) the remaining amount of the limited electronic money balance as a normal electronic money balance to the remitter ID linked to the remittance management ID. Then, it deletes the record of the remittance management ID that made the remittance from the limited electronic money management data.

When the restricted electronic money return process is executed, the control unit 11 of the server 10 transmits restricted electronic money return result information to the terminal 20A and to the terminal 20B of the account of the remitter ID that returned the restricted electronic money balance (S630).

If there is no restricted electronic money balance that is equal to or less than the predetermined value (S610: NO), the control unit 11 of the server 10 ends the process.

When the communication I/F 22 receives restricted electronic money return result information from the server 10 (A610: YES), the control unit 21 of the terminal 20A displays the received restricted electronic money return result information (A620). When the communication I/F 22 does not receive restricted electronic money return result information from the server 10 (A610: NO), the control unit 21 of the terminal 20A ends the process. The same applies to the terminal 20B.

<Effects of the Eleventh Example>
This embodiment shows a configuration in which, based on the balance of a limited electronic money balance (an example of a first electronic currency, not limiting) held by a user of terminal 20A (an example of an information processing device, not limiting), falling below a predetermined value (an example of a condition for use, not limiting), the balance of the first electronic currency is transferred to a user of terminal 20B (an example of a first information processing device, not limiting), and limited electronic money return result information (an example of first information, not limiting) indicating that the transfer has been made is received by a communication unit of the information processing device.
As an example of the effect of the embodiment obtained by such a configuration, the balance of the first electronic currency can be transferred to the user of the first information processing device based on the conditions regarding the use of the first electronic currency by the user of the information processing device. Note that this may be considered as the balance of the first electronic currency being refunded, returned, or returned to the user of the first information processing device.

<Eleventh Modification (1)>
In the above embodiment, when the limited electronic money balance becomes equal to or less than a predetermined value after the execution of the consecutive limited payment process, the limited electronic money balance is transferred to the user of the remittance source ID, but this is not limited to this. For example, but not limited to this, the user of the remittance source ID may transfer the money to any other user (account) designated by the user.

<Eleventh Modification (2)>
In the above embodiment, when the balance of the restricted electronic money falls below a predetermined value, the restricted electronic money return process is executed, but the present invention is not limited to this. As a non-limiting example, approval to execute the restricted electronic money return process may be obtained from the terminal 20A that executed the payment.

FIG. 11D is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this modified example.
The left side of FIG. 11-4 shows an example of a code payment screen displayed on the display unit 24 of the terminal 20A.
When a payment is made based on the wallet code information displayed in the wallet code information display area WCR1, payment result information is displayed as shown in the center of Fig. 11-4. After that, as shown on the right side of Fig. 11-4, by way of example and not limitation, restricted electronic money return approval confirmation information RA1 for confirming whether or not to return the remaining restricted electronic money is displayed so as to be superimposed on part of the payment result information.

This restricted electronic money return approval confirmation information RA1 includes, by way of example and not by way of limitation, the words "Do you want to return the restricted electronic money?" along with the amount to be transferred for the purpose of the return (in this example, "200 yen"), an illustration indicating that the return will result in a notification of the use of restricted electronic money being sent to the user of the notification destination account (in this example, "User C.C."), and an illustration indicating that the money will be transferred to the user of the sender account (in this example, "User C.C.").

Below that are displayed a "Refund" button BT91 for approving the refund and a "Cancel" button BT92 for rejecting the refund. When the "Refund" button BT91 is tapped, the remaining amount of the restricted electronic money is refunded to the user C.C.

Figure 11-5 is a flowchart showing an example of the process flow executed by each device in this modified example.

If there is a restricted electronic money balance that is equal to or less than a predetermined value (S610: YES), the control unit 11 of the server 10 transmits restricted electronic money return approval confirmation information to the terminal 20A via the communication I/F 14 (S640). If the restricted electronic money return approval confirmation information is received from the server 10 via the communication I/F 22 (A630: YES), the control unit 21 of the terminal 20A displays the restricted electronic money return approval confirmation information on the display unit 24 (A640). As a non-limiting example, if a return (remittance) of the restricted electronic money balance is selected based on an input (user operation) to the input/output unit 23 of the terminal 20A (A640: YES), the control unit 21 of the terminal 20A transmits restricted electronic money return approval information to the server 10 via the communication I/F 22 (A650).
If restricted electronic money return approval confirmation information is not received from the server 10 (A630: NO), the control unit 21 of the terminal 20A ends the process.
If the return (remittance) of the restricted electronic money balance is not selected (A640: NO), the control unit 21 of the terminal 20A ends the process.

When the communication I/F 14 receives restricted electronic money return approval information from the terminal 20A (S650: YES), the control unit 11 of the server 10 executes the restricted electronic money return process (S620). When the communication I/F 14 does not receive restricted electronic money return approval information from the terminal 20A (S650: NO), the control unit 11 of the server 10 ends the process.

Note that approval to execute the restricted electronic money return process may or may not be obtained at the terminal 20B of the remittance source ID. Also, if approval is obtained at both the payer's terminal 20A and the terminal 20B of the remittance source ID, the restricted electronic money return process may or may not be executed.

In this modification, the information processing device displays second information for transferring the balance of the first electronic currency to a user of the first information processing device on a display unit of the information processing device based on conditions for use of the first electronic currency, and the balance of the first electronic currency is transferred to the user of the first information processing device based on an input of the user of the information processing device for the second information.The information processing device then receives the first information.
As an example of the effect of an embodiment obtained by such a configuration, the user of the information processing device can be notified by displaying the second information on the display unit of the information processing device that the balance of the first electronic currency will be refunded to the user of the first information processing device based on the conditions regarding the use of the first electronic currency. Also, the balance of the first electronic currency can be transferred to the user of the first information processing device based on an input by the user of the information processing device to the second information displayed on the display unit. As a result, by way of example and not limitation, the user of the information processing device can be notified that the transfer has been made by displaying the first information on the display unit of the information processing device.

<Eleventh Modification (3)>
In the above embodiment, the condition for executing the limited electronic money return process is that the limited electronic money balance becomes equal to or less than a predetermined value after the consecutive limited payment process is executed, but the condition is not limited to this. The following are examples of the condition for executing the limited electronic money return process, but are not limited thereto.
- If the restricted electronic money balance becomes or falls below a specified percentage (for example, but not limited to, "5%) of the balance at the time of transfer.
As a non-limiting example, if a limited electronic money balance of "10,000 yen" is received, if the limited electronic money balance becomes "10,000 yen" x "5%" = "500 yen" or less after executing the continuous limited payment process, the limited electronic money return process will be executed.
When the time remaining until the expiration date of the restricted electronic money balance is less than a certain amount of time (for example, but not limited to, 24 hours).
As a non-limiting example, if the expiration date is set to "7 days later" (by July 23, 2021) due to the first use of a restricted electronic money balance, then "when it becomes midnight on July 23, 2021, the restricted electronic money return process will be executed. In this case, the due date may be determined after the continuous restricted payment process is executed, or the due date may be determined even if the continuous restricted payment process has not been executed.
- When a limited electronic money balance is used a certain number of times (for example, but not limited to, "10" times).
By way of example and not limitation, if a limited electronic money balance has been used in ten consecutive limited payment transactions (limited payment transactions), a limited electronic money refund transaction may be performed.

In this modified example, the conditions regarding the use of the first electronic currency include conditions regarding the balance of the restricted electronic money or the ratio of the balance to the amount of the restricted electronic money transferred to the terminal 20 .
As an example of an effect of an embodiment obtained by such a configuration, the balance of the first electronic currency can be appropriately transferred to a user of the first information processing device based on conditions related to the balance of the first electronic currency or the ratio of the balance to the amount of the first electronic currency transferred to the information processing device.

Furthermore, in this modified example, the conditions regarding the use of the first electronic currency include conditions regarding the period during which the terminal 20 can make payments using restricted electronic money.
As an example of an effect of an embodiment obtained by such a configuration, the balance of the first electronic currency can be appropriately transferred to the user of the first information processing device based on conditions regarding the period during which the information processing device can make payments using the first electronic currency.

In addition, in this modified example, the conditions regarding the use of the first electronic currency include a condition regarding the number of times that a payment has been made using limited electronic money.
As an example of the effect of an embodiment obtained by such a configuration, the balance of the first electronic currency can be appropriately transferred to the user of the first information processing device based on conditions related to the number of times a payment has been made using the first electronic currency.

<Eleventh Modification (3)>
In the above embodiment, when the limited electronic money return process is executed, the balance is transferred to the account of the remitter ID, but this is not limited to this. As a non-limiting example, the balance may be transferred to the normal electronic money balance of the account of the terminal 20A that made the payment. In this case, if the balance of the limited electronic money balance is equal to or less than a predetermined value after the consecutive limited payment process is executed, the fractional balance is incorporated into the normal electronic money balance.

If the balance of the limited electronic money balance falls below a predetermined value after executing the consecutive limited payment process, the remaining limited electronic money balance may be transferred to the normal electronic money balance if the sender (account of the sender ID) gives consent. Also, if the sender (account of the sender ID) gives consent, the limited electronic money balance may be transferred to the normal electronic money balance at any timing.

<Twelfth Example>
In the above embodiment, the restricted electronic money balance is managed by dividing the balance for each remittance.
The twelfth embodiment is an embodiment in which two restricted electronic money balances with the same usage limit are merged together and managed and used as a single restricted electronic money balance.

The contents described in the twelfth embodiment are applicable to any of the other embodiments and other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Data structure>
FIG. 12A is a diagram showing an example of the data configuration of the account management database 155J, which is an example of the account management database 155 in this embodiment.
Each account management data in this account management database 155J stores, by way of example and not limitation, an application ID, a normal electronic money balance, limited electronic money management data, merged limited electronic money management data, limited electronic money usage history data, and electronic money usage limit management data.

The merged restricted electronic money management data is data for managing information relating to two or more restricted electronic money (hereinafter referred to as "merged restricted electronic money") that have been merged in the restricted electronic money merging process described below, and by way of example and not limitation, a merger management ID, a pre-merger remittance management ID, and a merged restricted electronic money balance are stored in association with each other.

The merger management ID is an ID for uniquely identifying merged restricted electronic money, and by way of example and not limitation, a different ID is set and stored by server 10 each time the restricted electronic money merging process is executed by server 10.

The pre-merger remittance management ID is data for managing information about the restricted electronic money to be merged, and as a non-limiting example, when the restricted electronic money merging process is executed by the server 10, the remittance management ID of the restricted electronic money to be merged is added and stored.

The merged restricted electronic money balance is the balance of restricted electronic money associated with this merge management ID.

When the restricted electronic money merging process is executed, the restricted electronic money balance stored in the pre-merger remittance management ID becomes unusable. In the account management database 155J, the restricted electronic money balance that can no longer be used is shown in parentheses, not as a limitation, but as an example. In the account management database 155J, not as a limitation, but as an example, the restricted electronic money balance is shown as "(1000 yen)" in the restricted electronic money management data in the account management database 155J, since the restricted electronic money of the remittance management ID "T02109" has been merged with the restricted electronic money of the merger management ID. The amount in parentheses is the restricted electronic money balance at the time the restricted electronic money merging process was executed, not as a limitation, but as an example. Therefore, it can be seen that the restricted electronic money of the remittance management ID "T02109" cannot be used (it has already been merged).

When merged restricted electronic money is used for payment, a record is added to the restricted electronic money usage history data with the merge management ID as the remittance management ID.

In addition, information regarding the notification account, such as the notification ID, may be stored in the merged restricted electronic money management data in association with the merged management ID.

<Display screen>
The first restricted electronic money and the second restricted electronic money described below are described as having no restrictions set on notifications, but only restrictions set on the stores at which they can be used.

FIG. 12B is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
12-2 shows a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, in which the balance display area BR2 shows the restricted electronic money balance (in this example, "1,000 yen") and the restriction mark RMK. Here, the state in which the restriction mark RMK has been tapped by the user is shown.

In this case, by way of example and not limitation, a speech bubble displays usable store information including information on the type of business of stores where the restricted electronic money can be used. In this example, "books and stationery" is displayed as the type of business of stores where the restricted electronic money can be used. The balance of this restricted electronic money is the balance based on the first restricted electronic money whose sender account is user B.B's account, and corresponds to the first restricted electronic money remittance result information RR101 shown on the screen in the center of FIG. 12-2.

The center of FIG. 12-2 shows an example of a notice screen displayed on the display unit 24 of the terminal 20A.
On the left side of the notification area, first limited electronic money remittance result information RR101 corresponding to the first limited electronic money whose remittance source account is the account of user B.B. is displayed.

After that, as a non-limiting example, assume that "2,000 yen" is transferred as second restricted electronic money from user C.C's account to user A.A's account. As a result, second restricted electronic money transfer result information RR102 is displayed below first restricted electronic money transfer result information RR101.

The first restricted electronic money and the second restricted electronic money can both be used at the same store type, "books and stationery." In this case, based on the fact that the store types at which the electronic money can be used are the same, by way of example and not of limitation, when the second restricted electronic money is received, the server 10 merges these two restricted electronic moneys.

The right side of FIG. 12-2 shows an example of a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A in this case.
Based on the fact that the restricted electronic money has been merged, the balance display area BR2 displays the balance of the merged restricted electronic money as "1,000 yen + 2,000 yen = 3,000 yen." Also, in this example, the restriction mark RMK is shown in a state where it has been tapped by the user.

In this case, as an example and not a limitation, similar to the screen on the left side of FIG. 12-2, available store information including information on the type of business of stores that can use the merged restricted electronic money is displayed in a speech bubble. In this example, "Books and stationery" is displayed as the type of business of stores that can use the merged restricted electronic money.

<Processing>
FIG. 12C is a flowchart showing an example of the flow of processes executed by each device in this embodiment, and shows the part corresponding to FIG.

The control unit 21 of the terminal 20B executes the first-limited electronic money remittance setting process (B710) in the same manner as B410 to B420 in FIG. 7-5, for example and not for limitation, and transmits the first-limited electronic money remittance request information to the server 10 (B720). The condition (restriction) set in the first-limited electronic money remittance setting process is referred to as the "first restriction." The control unit 11 of the server 10 executes the first-limited electronic money remittance process (S710) in the same manner as S410 to S420 in FIG. 7-5, for example and not for limitation, and transmits the first-limited electronic money remittance result information (S720). When the control unit 21 of the terminal 20A and the control unit 21 of the terminal 20B receive the first-limited electronic money remittance result information, they display it on the display unit 24 (A710, B730).

Next, the control unit 21 of the terminal 20B executes the electronic money remittance setting process with the second limit (B715) in the same manner as B410 to B420 in FIG. 7-5, by way of example and not limitation, and transmits the electronic money remittance request information with the second limit to the server 10 (B725). The condition (limit) set in the electronic money remittance setting process with the second limit is referred to as the "second limit." The control unit 11 of the server 10 executes the electronic money remittance process with the second limit (S715) in the same manner as S410 in FIG. 7-5, by way of example and not limitation.
It should be noted that steps B715 to B725 may be executed in a terminal 20 other than terminal 20B.

Then, the control unit 11 of the server 10, by way of example and not limitation, reads the account management data from the account management database 155J and determines whether or not there is restricted electronic money with the same usage restrictions (in this example, the usable store type and notification destination ID) by referring to the restricted electronic money management data and the electronic money usage restriction management data (S730).

If it is determined that the limits are the same (S730: YES), the control unit 11 of the server 10 executes a restricted electronic money merging process (S740). In the restricted electronic money merging process, the control unit 11 of the server 10 combines the balances of two or more restricted electronic money (for example, but not limited to, the first restricted electronic money and the second restricted electronic money) that are determined to have the same limits (for example, but not limited to, the first limit and the second limit are equal), and stores the combined restricted electronic money balance in the combined restricted electronic money management data in association with the generated merger management ID. The control unit 11 of the server 10 also adds the remittance management IDs of the two or more restricted electronic money that are determined to have the same limits to the remittance management ID before merging. The control unit 11 of the server 10 makes the two or more restricted electronic money balances that are determined to have the same limits in the restricted electronic money management data unusable ("store in parentheses").

Then, the control unit 11 of the server 10 transmits the generated merger management ID and the limited electronic money merger result information including at least the merged limited electronic money balance to the terminal 20A via the communication I/F 14 (S750). Note that the limited electronic money merger result information may include the remittance management ID stored in the pre-merger remittance management ID.

When the communication I/F 22 receives restricted electronic money merging result information from the server 10 (A720: YES), the control unit 21 of the terminal 20A displays the received restricted electronic money merging result information on the display unit 24 (A730). When the communication I/F 22 does not receive restricted electronic money merging result information from the server 10 (A720: NO), the control unit 21 of the terminal 20A skips step A730.

The control unit 11 of the server 10 may or may not transmit the restricted electronic money merging result information to the terminal 20B of the account of the sender ID of the merged restricted electronic money. When receiving the restricted electronic money merging result information from the server 10, the control unit 21 of the terminal 20B causes the display unit 24 to display the received restricted electronic money merging result information.

If it is not determined that the restrictions are the same (S730: NO), the control unit 11 of the server 10 skips steps S740 to S750.
Then, the control unit 11 of the server 10 transmits the second restricted electronic money remittance result information in the same manner as S420 in Fig. 7-5, for example and not for limitation (S725). Note that, when the second restricted electronic money has been merged by the restricted electronic money merging process, the control unit 11 of the server 10 may be configured not to transmit the second restricted electronic money remittance result information to the terminal 20A that transmitted the restricted electronic money merging result information.

When the control unit 21 of terminal 20A and the control unit 21 of terminal 20B receive the second restricted electronic money remittance result information, they cause it to be displayed on the display unit 24 (A715, B735).

After the user selects the electronic money balance to be used for payment, at or before or after step A120, the control unit 21 of terminal 20A can transmit to server 10 a remittance management ID or merger management ID corresponding to the selected restricted electronic money balance.
Furthermore, when the first restricted electronic money and the second restricted electronic money have been merged by the restricted electronic money merging process, the control unit 21 of the terminal 20A can prevent the merged restricted electronic money from being displayed in the payment selection display. Note that, when the first restricted electronic money and the second restricted electronic money have been merged, the control unit 11 of the server 10 may not transmit information on the first restricted electronic money and the second restricted electronic money to the terminal 20A as if they do not exist. In this way, the terminal 20A and the server 10 can prevent the use of the restricted electronic money that was the source of the merger.

When a merged management ID is specified as the electronic money to be used for payment, in the restricted payment process, the availability of use is determined according to the usage restrictions associated with the specified merged management ID, which are stored in the remittance management ID of the electronic money usage restriction management data, and the payment process is executed by consuming the merged restricted electronic money balance.

<Effects of the twelfth embodiment>
This embodiment shows a configuration in which a program is executed by server 10 (not limited to this, an example of a server that associates and stores electronic currency with a user of terminal 20A (not limited to this, an example of a first terminal)), in which a control unit of the server performs a process of associating first limited electronic money (not limited to this, an example of the first electronic currency) transferred from a second terminal to the first terminal, on which a first limit has been set by a user of terminal 20B (not limited to this, an example of a second terminal), with the user of the first terminal, and a process of associating second limited electronic money (not limited to this, an example of the second electronic currency) transferred from a third terminal to the first terminal, on which a second limit has been set by a user of terminal 20C (not limited to this, an example of a third terminal), with the user of the first terminal, and a process of performing a limited electronic money merging process (not limited to this, an example of a process of associating a third electronic currency based on the first electronic currency and the second electronic currency with a user of the first terminal) based on the first limit and the second limit by the control unit.
As an example of the effect of the embodiment obtained by such a configuration, a third electronic currency based on the first electronic currency and the second electronic currency can be associated with a user of a first terminal based on the first and second restrictions. That is, electronic currencies with restrictions can be, so to speak, merged with each other based on those restrictions.

In addition, this embodiment illustrates a configuration in which the first restriction includes at least one of restrictions on purchasable products, restrictions on stores where the products can be purchased, and restrictions on notifications, and the second restriction includes at least one of restrictions on purchasable products, restrictions on stores where the products can be purchased, and restrictions on notifications.
As an example of an effect of an embodiment obtained by such a configuration, a third electronic currency based on the first electronic currency and the second electronic currency can be associated with a user of a first terminal based on a first restriction including at least one of restrictions on purchasable products, restrictions on stores where the products can be purchased, and restrictions on notifications, and a second restriction including at least one of restrictions on purchasable products, restrictions on stores where the products can be purchased, and restrictions on notifications.

Furthermore, this embodiment illustrates a configuration in which the merged restricted electronic money (as an example of the third electronic currency, but not limited to it) is an electronic currency formed by combining the first electronic currency and the second electronic currency.
As an example of an effect of an embodiment obtained by such a configuration, a third electronic currency obtained by adding up the first electronic currency and the second electronic currency can be associated with the user of the first terminal.

<Twelfth Modification (1)>
In the above embodiment, if there is restricted electronic money with the same limit, the money is automatically merged, but this is not limited to this. As a non-limiting example, if it is determined that the limits are the same, a restricted electronic money merging process may be executed based on an approval operation of the user of the terminal 20A.

FIG. 12D is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of FIG. 12-4 is a diagram showing an example of a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, and corresponds to the screen on the left side of FIG. 12-2.

The center of FIG. 12-4 shows an example of a display screen when "2,000 yen" is transferred as second restricted electronic money from user C.C's account to user A.A's account and received by user A.A. In the balance display area BR2, the balance of the first restricted electronic money, "1,000 yen," the balance of the second restricted electronic money, "2,000 yen," and the normal electronic money balance, "500 yen," are individually displayed.

In addition, the restricted electronic money merger confirmation information MCR1 sent from the server 10 to the terminal 20A based on the fact that the first restricted electronic money and the second restricted electronic money can be used in the same type of store is displayed superimposed on the main menu screen.

Specifically, the restricted electronic money merging confirmation information MCR1 displays the message "Do you want to combine restricted electronic money?" along with the balance of the first restricted electronic money (in this example, "1,000 yen") and the restriction mark RMK, which are the restricted electronic money to be merged, and the balance of the second restricted electronic money (in this example, "2,000 yen") and the restriction mark RMK. Below that, it is shown that the type of business of the store where both the first restricted electronic money and the second restricted electronic money can be used is "Books and stationery."

Below that are displayed a "Merge" button BT101 to approve the merging of the first restricted electronic money and the second restricted electronic money, and a "Cancel" button BT102 to reject the merging.

When the "Merge" button BT101 is tapped, the server 10 merges these two restricted electronic money. As a result, as shown on the right side of Figure 12-4, the main menu screen of the payment application displays the same as the right side of Figure 12-2.

In the above screen diagram, the first restricted electronic money and the second restricted electronic money are exemplified, but if user A.A owns three or more restricted electronic money that can be merged, information on whether or not to combine the three or more restricted electronic money into one may be displayed as restricted electronic money merge confirmation information.

As an example and not a limitation, in the process of this modified example, when it is determined in S730 of FIG. 12-3 that the restrictions are the same (S730: YES), the control unit 11 of the server 10 transmits restricted electronic money merging confirmation information to the terminal 20A via the communication I/F 14. The control unit 21 of the terminal 20A displays the received restricted electronic money merging confirmation information on the display unit 24. As an example and not a limitation, when merging of restricted electronic money is selected based on an input (user operation) to the input/output unit 23 of the terminal 20A, the control unit 21 of the terminal 20A transmits restricted electronic money merging approval information to the server 10 via the communication I/F 22.
When receiving restricted electronic money merging approval information from the terminal 20A, the control unit 11 of the server 10 executes restricted electronic money merging processing.

If it is determined that the restrictions are the same, the restricted electronic money merging process may be executed based on the approval operation of the user of the sender ID of the first restricted electronic money and the second restricted electronic money to be merged. In this case, the restricted electronic money merging process may be executed when approval is obtained from both the user of the sender ID of the first restricted electronic money and the user of the sender ID of the second restricted electronic money, or when approval is obtained from either one of them.

In addition, if the sender IDs of the restricted electronic money before merging are three or more (three or more restricted electronic money are to be merged), approval of all users of each sender ID may be required in order for the restricted electronic money merging process to be executed, or approval of a predetermined number (for example, a majority, not a limitation) may be required.

<Twelfth Modification (2)>
In the above embodiment, when the limits are the same, the restricted electronic money is merged, but this is not limited to this. As a non-limiting example, even when the first limit and the second limit are close to each other, the restricted electronic money merging process of the first restricted electronic money and the second restricted electronic money may be executed.

Here, examples of the first limit and the second limit being close to each other include, but are not limited to, the following.
- The first restriction includes the second restriction.
- The second restriction includes the first restriction.
- The first and second restrictions are similar.

Examples of cases in which the second restriction includes the first restriction (or the first restriction includes the second restriction) include, by way of example and not limitation, the following:
Inclusion relationship of notification destinations As an example, and not a limitation, if the first restriction = notification destinations are user A.A and user B.B, and the second restriction = notification destination is user A.A (or user B.B), the first restriction includes the second restriction.
Inclusion relationship of usable store industries/service industries As an example and not a limitation, if a first restriction = usable at "convenience stores" and "books and stationery" and a second restriction = usable at "convenience stores" (or "books and stationery"), then the first restriction includes the second restriction.
Inclusion of purchasable goods/services As an example and not a limitation, if the first restriction means that the product can be used for "entertainment" and the second restriction means that the product can be used for "game software" (or "music purchase", etc.), the first restriction includes the second restriction.
Inclusion relationship regarding usable date, time, and time period As an example, and not a limitation, if the first limit is usable from 9:00 to 21:00 and the second limit is usable from 12:00 to 13:00, the first limit includes the second limit. Also, if the first limit is usable during June, which is the month of remittance, and the second limit is usable on June 15, which is the day of the field trip, the first limit includes the second limit.

Examples of cases where the first and second restrictions are similar include, by way of example and not limitation, the following:
- Similarity of the recipients of notice As an example and not a limitation, if the first restriction = notification to the father of the payer and the second restriction = notification to the mother of the payer, they are similar because the recipients of notice are both first degree kinship.
Similarity of purchasable goods and services As an example, but not limited to, if the first restriction is that X.X's home appliances are purchasable, and the second restriction is that Y.Y's home appliances are purchasable, then they are similar because the same product type is purchasable. Also, if the first restriction is that X.X's home appliances are purchasable, and the second restriction is that X.X's food and beverages are purchasable, then they are similar because the same manufacturer's products are purchasable.
Inclusion relationship regarding usable dates, times, and time periods As an example and not a limitation, if the first limit = usable from "11:00 to 13:00" and the second limit = usable from "12:00 to 14:00", this is similar because the time during which use is permitted in the usable time period (in this example, both the first limit and the second limit are 2 hours) overlaps by more than a certain percentage (by way of example and not a limitation, more than 50%).

This modified example shows a configuration in which the server performs a process of associating a third electronic currency based on the first electronic currency and the second electronic currency with a user of the first terminal using a control unit in at least one of the cases where the first restriction includes the second restriction, where the second restriction includes the first restriction, and where the first restriction and the second restriction are the same restriction.
As an example of an effect of an embodiment obtained by such a configuration, in at least one of the cases where the first restriction includes the second restriction, where the second restriction includes the first restriction, and where the first restriction and the second restriction are the same restriction, a third electronic currency based on the first electronic currency and the second electronic currency can be associated with a user of the first terminal based on the first restriction and the second restriction.

<Twelfth Modification (3)>
In the above embodiment, in the restricted electronic money merging process, the sum of the first restricted electronic money balance and the second restricted electronic money balance to be merged is set as the merged restricted electronic money balance, but the present invention is not limited to this. As a non-limiting example, the merged restricted electronic money balance may be calculated using the following formula:
"Merged restricted electronic money balance" = "First restricted electronic money balance" + "Second restricted electronic money balance" + "Merged bonus"
Here, the merger bonus is the bonus balance obtained by merging restricted electronic money, and by way of example and not limitation, it can be set to 10% of the combined value of the first restricted electronic money balance and the second restricted electronic money balance.

The merged limited electronic money balance may be calculated using the following formula:
"Merged restricted electronic money balance" = "First restricted electronic money balance" + "Second restricted electronic money balance" - "Merged onus"
Here, the merger onus is the balance that the user of terminal 20 bears by merging restricted electronic money, and as a non-limiting example, it can be set to 5% of the combined value of the first restricted electronic money balance and the second restricted electronic money balance.

<Twelfth Modification (4)>
In the above embodiment, an example was shown in which the association between the records indicated by the respective remittance management IDs is preserved in the restricted electronic money management data even after the first restricted electronic money balance and the second restricted electronic money balance are merged, but this is not limited to this.

FIG. 12-5 is an example of the account management data included in the account management database 155H before the limited electronic money merging process is executed in this case.
The restricted electronic money with the remittance management ID "T02109" and the restricted electronic money with the remittance management ID "T02572" are in the same usable store type in the electronic money usage restriction management data, so the restricted electronic money merging process is executed.

FIG. 12-6 is an example of the account management data included in the account management database 155H after the limited electronic money merging process has been executed.
In this diagram, a new remittance management ID "T90001" is issued (generated) based on the execution of the restricted electronic money merging process. Then, as the remitter ID of the restricted electronic money with remittance management ID "T90001", the remitter ID "U0002" of the restricted electronic money with remittance management ID "T02109" and the remitter ID "U0003" of the restricted electronic money with remittance management ID "T02572" are stored. In addition, the restricted electronic money balance of "T90001" is stored as "3,000 yen", which is the sum of the restricted electronic money balance of "1,000 yen" with remittance management ID "T02109" and the restricted electronic money balance of "2,000 yen" with remittance management ID "T02572".

The control unit 11 of the server 10 may choose not to issue a new remittance management ID during the restricted electronic money merging process. In this case, "T02109" or "T02572" will continue to be used as the remittance management ID.

<Twelfth Modification (5)>
In the above embodiment, the data after the restricted electronic money merging process is managed using merged restricted electronic money management data obtained by merging the first restricted electronic money and the second restricted electronic money, but this is not limited to this. As a non-limiting example, the data shown in FIG. 12-5 may be used as the data after the restricted electronic money merging process. However, merged flag information indicating that the restricted electronic money has been merged is added to the restricted electronic money with the remittance management ID "T02109" and the restricted electronic money with the remittance management ID "T02572". In this case, when the control unit 21 of the terminal 20A transmits electronic money balance request information requesting a list of electronic money balances to the server 10, the control unit 11 of the server 10 transmits the normal electronic money balance and the restricted electronic money management data to the control unit 21 of the terminal 20A. Then, the control unit 21 of the terminal 20A adds the restricted electronic money balance to which the merged flag information has been added based on the received restricted electronic money management data, and displays the result on the display unit 24. At this time, the control unit 21 of the terminal 20A may not cause the display unit 24 to display each of the restricted electronic money balances to which the merged flag information has been added.

This modified example shows a configuration in which a program is executed by terminal 20A (an example of an information processing device, not limiting), and the program displays on the information processing device information on first limited electronic money (an example of a first electronic currency, not limiting) transferred from a first information processing device to the information processing device, for which a first limit has been set by a user of terminal 20B (an example of a first information processing device, not limiting), and information on second limited electronic money (an example of a second electronic currency, not limiting) transferred from a second information processing device to the first information processing device, for which a second limit has been set by a user of terminal 20C (an example of a second information processing device, not limiting), and the control unit of the information processing device controls the display unit to display a merged limited electronic money balance (an example of a third electronic currency, not limiting), based on the first electronic currency and the second electronic currency, based on the first limit and the second limit.
As an example of the effect of an embodiment obtained by such a configuration, information on a first electronic currency transferred from a first information processing device to an information processing device, for which a first limit has been set by a user of the first information processing device, and information on a second electronic currency transferred from the second information processing device to the first information processing device, for which a second limit has been set by a user of the second information processing device, can be displayed to make the user of the information processing device aware. Also, based on the first limit and the second limit, third electronic currency based on the first electronic currency and the second electronic currency can be displayed to make the user of the information processing device aware.

<Twelfth Modification (6)>
In the above embodiment, after the first restricted electronic money remittance process and the second restricted electronic money remittance process are executed, the restricted electronic money merging process is executed for merging the first restricted electronic money and the second restricted electronic money, but this is not limited to this. As a non-limiting example, when the control unit 11 of the server 10 receives second restricted electronic money remittance request information from the terminal 20 after executing the first restricted electronic money remittance process, the control unit 11 determines whether or not the second limit and the first limit that has been remitted are the same limit based on the second restricted electronic money remittance request information. If they are the same limit, the control unit 11 of the server 10 may execute the restricted electronic money merging process for merging the first restricted electronic money and the second restricted electronic money. If they are not the same limit, the control unit 11 of the server 10 executes the second restricted electronic money remittance process.

In this case, the data configuration may be, for example and not for limitation, the data configuration shown in FIG. 12-6. Also, for example and not for limitation, in the data configuration shown in FIG. 12-1, in the restricted electronic money merging process, changes may be made to the restricted electronic money management data based on the second restricted electronic money remittance request information, and changes may be made to the merged restricted electronic money management data.

<Twelfth Modification (7)>
In the above embodiment, the merged restricted electronic money identified by the merger management ID is generated by executing the restricted electronic money merging process for merging the first restricted electronic money and the second restricted electronic money, but the present invention is not limited to this. As a non-limiting example, the merger of the generated merged restricted electronic money may be released to split (restore) the first restricted electronic money and the second restricted electronic money.

In this case, the first limited electronic money balance and the second limited electronic money balance after the division (restoration) can be calculated by distributing the merged limited electronic money balance at the time of division according to the balance ratio in "( )" stored for each limited electronic money balance, as an example and not a limitation.

In addition, in order to cancel the merging of the generated merged restricted electronic money, approval may be required at the terminal 20A of the remittance destination account. In addition, in order to cancel the merging of the generated merged restricted electronic money, approval may be required at the terminal 20B of the remittance source account.

<Twelfth Modification (8)>
In the above embodiment, an example is given of executing a restricted electronic money merging process for merging the first restricted electronic money and the second restricted electronic money, but the present invention is not limited to this. As a non-limiting example, when the first merged restricted electronic money obtained by merging the first restricted electronic money and the second restricted electronic money and the third restricted electronic money have the same first merged limit and third limit, a restricted electronic money merging process may be executed for merging the first merged restricted electronic money and the third restricted electronic money.

In this case, in the restricted electronic money merging process, the control unit 11 of the server 10 adds the sender ID of the third restricted electronic money to the pre-merger remittance management ID in the merged restricted electronic money management data, in association with the merger management ID of the first merged restricted electronic money, and stores the result. Also, the first merged restricted electronic money balance and the third restricted electronic money balance are added to the merged restricted electronic money balance, and the third restricted electronic money balance is stored. Then, the third restricted electronic money balance in the restricted electronic money management data is made unusable.

In the restricted electronic money merging process, the control unit 11 of the server 10 generates a new merge management ID in the merged restricted electronic money management data, and stores the sender ID of the first merged restricted electronic money and the sender ID of the third restricted electronic money in association with the pre-merger remittance management ID. The first merged restricted electronic money balance and the third restricted electronic money balance may then be added together and stored in association with the newly generated merge management ID. In this case, the control unit 11 of the server 10 makes the first merged restricted electronic money balance unusable (shown in "( )" as an example and not a limitation).

Note that, if the first merged limit and the second merged limit are the same, a restricted electronic money merging process may be executed in which the first merged restricted electronic money and the second merged restricted electronic money are to be merged. In this case, as a non-limiting example of a processing method for the restricted electronic money merging process, the sender ID of the second merged restricted electronic money is added in association with the merger management ID of the first merged restricted electronic money, and the sum of the first merged restricted electronic money balance and the second merged restricted electronic money balance is stored as the merged restricted electronic money balance.

Alternatively, a new merger management ID is issued, and the sender ID of the first merged limited electronic money and the sender ID of the second merged limited electronic money are associated with the issued merger management ID and stored in the pre-merger remittance management ID, and the sum of the first merged limited electronic money balance and the second merged limited electronic money balance is stored in the merged limited electronic money balance. The control unit 11 of the server 10 then makes the first merged limited electronic money balance and the second merged limited electronic money balance unusable.

<Twelfth Modification (9)>
When a refund occurs, such as when returning a product or service, and the merged limited electronic money balance was used at the time of payment, the amount of the refund may be added to the merged limited electronic money balance used at the time of payment.

In this case, when refunding at least a portion of the merged restricted electronic money used by the user of the remittance destination account, the control unit 11 of the server 10 identifies the payment ID sent from the store POS system 40 from the payment history management data 157. This is to confirm whether or not a payment has been made and to identify the payment amount (refund amount).

The control unit 11 of the server 10 then references the restricted electronic money usage history data contained in the account management data of the user of the remittance destination account in the account management database 155J, and identifies the remittance management ID that corresponds to the identified payment ID. If merged restricted electronic money was used at the time of payment, this remittance management ID will include the merged management ID.

If a merger management ID exists in the remittance management ID corresponding to the identified payment ID, at least a portion of the merged restricted electronic money has been used for payment. Therefore, the amount used corresponding to the identified payment ID is identified from the restricted electronic money usage history data, and this amount used is added to the merged restricted electronic money balance of the corresponding merger management ID in the merged restricted electronic money management data.

On the other hand, if there is no merger management ID in the remittance management ID corresponding to the identified payment ID, the merged restricted electronic money was not used for the payment. Therefore, as an example and not a limitation, the processing can be performed in the same manner as in the seventh variant.

<Thirteenth Example>
In the above embodiment, when the restrictions including the notification destination are the same, the restricted electronic money merging process is executed.
The thirteenth embodiment is an embodiment in which restricted electronic money that has different notification destinations but has the same usage restrictions managed by the electronic money usage restriction management data is merged.

The contents described in the thirteenth embodiment are applicable to the other embodiments and the other modified examples.
In addition, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Data structure>
As for the data structure, the account management database 155J shown in FIG. 12A can be used as an example and not a limitation.

<Display screen>
In the following example, it is assumed that the first restricted electronic money and the second restricted electronic money are both set with a restriction on notification and a restriction different from the restriction on notification. In addition, it is assumed that the first restricted electronic money and the second restricted electronic money are set with different notification accounts, but the restriction different from the restriction on notification is the same.

13A and 13B are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this embodiment.
13A is a diagram showing an example of a main menu screen displayed on the display unit 24 of the terminal 20A. In this example, the first restricted electronic money is an account whose user is a notification destination account user B.

On the left side of FIG. 13-1, the balance display area BR2 shows that the notification account is user B.B and that the notification account has a first limited electronic money balance of "1,000 yen" and a normal electronic money balance of "500 yen."

The screen in the center of FIG. 13-1 is a portion of the display screen on terminal 20A when a second restricted electronic money balance of "2,000 yen" is received with the notification account being user C.C. In this screen, in the balance display area BR2, in addition to the first restricted electronic money balance of "1,000 yen" and the normal electronic money balance of "500 yen", the second restricted electronic money balance of "2,000 yen" with the notification account being user C.C. is displayed. Also, restricted electronic money merging confirmation information MCR2 transmitted from server 10 to terminal 20A is displayed based on the fact that the first restricted electronic money and the second restricted electronic money have the same restrictions (as an example, not a limitation, the stores where the money can be used) that are different from the restrictions on notifications.

Specifically, the restricted electronic money merging confirmation information MCR2 displays the message "Do you want to merge restricted electronic money?" along with the first restricted electronic money balance (in this example, "1,000 yen"), an illustration and a restriction mark RMK indicating that the account to be notified is user B.B's account, and the second restricted electronic money balance (in this example, "2,000 yen"), an illustration and a restriction mark RMK indicating that the account to be notified is user C.C's account.

Below that, the aforementioned "Combine" button BT101 and "Cancel" button BT102 are displayed. When the "Combine" button BT101 is tapped, the server 10 merges these two restricted electronic money. As a result, as shown on the right side of FIG. 13-1, the balance display area BR2 displays "3,000 yen" as the merged electronic money balance.

In this example, two restricted electronic money items, whose notification accounts are user B.B. and user C.C., respectively, have been merged, so both user B.B. and user C.C. are set as notification accounts for the merged restricted electronic money.

When the "code payment icon" IC2 is tapped, a code payment screen like that shown on the left side of Figure 13-2 is displayed. In this example, the wallet code information display area WCR1 displays the merged limited electronic money balance (limited) and the normal electronic money balance (unlimited), with the radio buttons described above corresponding to each. Here, the radio button corresponding to the merged limited electronic money balance is shown as being "ON." When a code payment is made in this state, the settlement is made using the merged limited electronic money, and as a result, the settlement result information like that shown on the right side of Figure 13-2 is displayed.

In this example, it is shown that a product costing "1,800 yen" was purchased at "XX Bookstore" and that "1,800 yen" was used for payment (settlement) from the merged restricted electronic money. It is also shown that this results in a notification of the use of restricted electronic money being sent to both user B.B and user C.C.

The left side of FIG. 13C shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A.
On the left side of the notification area, payment result information PR121 is displayed, which indicates that a payment has been made using merged limited electronic money.

The center of FIG. 13-3 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B.
On the left side of the notification area, restricted electronic money remittance result information RR121 (in this example, "1,000 yen") is displayed, which indicates that restricted electronic money has been remitted to the account of user A.A., and below that, restricted electronic money usage information RU121 is displayed, which indicates that restricted electronic money has been used by user A.A.

The right side of FIG. 13C shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20C.
On the left side of the notification area, restricted electronic money remittance result information RR122 (in this example, "2,000 yen") is displayed, which indicates that restricted electronic money has been remitted to the account of user A.A., and below that, restricted electronic money usage information RU122 is displayed, which indicates that restricted electronic money has been used by user A.A.

<Other examples of notifications>
Another example of the notification of restricted electronic money usage will be described below. In this example, the amount notified to each notification destination account is referred to as the "notification amount."

FIG. 13D is a diagram showing another example of the screen shown in FIG. 13C, which is displayed on the display unit 24 of the terminal 20 in this embodiment.
In this example, the amount paid by user A.A is distributed in the balance ratio between the first limited electronic money balance and the second limited electronic money balance before the merger (hereinafter referred to as the "distributed amount"), and the amount is notified to each notification destination account as the notification amount.

In this example, the amount of restricted electronic money (first restricted electronic money) transferred by user B.B to user A.A is "1,000 yen," and the amount of restricted electronic money (second restricted electronic money) transferred by user C.C to user A.A is "2,000 yen." As a result, the balance display area BR2 of the main menu screen shown in the center of FIG. 13-1 displays that the balance of the first restricted electronic money is "1,000 yen," and the balance of the second restricted electronic money is "2,000 yen."

Also, in this example, the amount paid by user A.A is "1,800 yen."
In this case, the distribution amount corresponding to user B.B is calculated as "1,800 yen x (1,000 yen ÷ 3,000 yen) = 600 yen", and the distribution amount corresponding to user C.C is calculated as "1,800 yen x (2,000 yen ÷ 3,000 yen) = 1,200 yen".

The left side of Figure 13-4 is an example of a notification screen for a payment application displayed on the display unit 24 of the terminal 20, and is similar to the left side of Figure 13-3.

The center of FIG. 13-4 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B.
This notification screen is almost the same as the screen in the center of Fig. 13-3, but some of the information contained in the restricted electronic money usage information RU 123 is different. In addition to the payee (in this example, "XX Bookstore"), this restricted electronic money usage information RU 123 displays the distribution amount corresponding to user B.B. (as above, "600 yen") as the amount notified to user B.B.

The right side of FIG. 13-4 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20C.
This notification screen is almost the same as the screen on the right side of Fig. 13-3, but some of the information contained in the restricted electronic money usage information RU 124 is different. In addition to the payee (in this example, "XX Bookstore"), this restricted electronic money usage information RU 124 displays the distribution amount corresponding to user C.C. (as above, "1,200 yen") as the amount notified to user C.C.

FIG. 13-5 is a diagram showing another example of the screen shown in FIG. 13-3, which is displayed on the display unit 24 of the terminal 20 in this embodiment.
In this example, the amount paid by user A.A is notified to each of the notification accounts.

The left side of Figure 13-5 is an example of a notification screen for a payment application displayed on the display unit 24 of the terminal 20, and is similar to the left side of Figure 13-3.

The center of FIG. 13-5 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B.
This notification screen is almost the same as the screen in the center of Fig. 13-4, but the notification amount included in the restricted electronic money usage information RU125 is different. Specifically, the amount paid by user A.A (in this example, "1,800 yen") is displayed as the notification amount to user B.B.

The right side of FIG. 13-5 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20C.
This notification screen is almost the same as the screen on the right side of Fig. 13-4, but the notification amount included in the restricted electronic money usage information RU126 is different. Specifically, the amount paid by user A.A (in this example, "1,800 yen") is displayed as the notification amount to user C.C.

FIG. 13-6 is a diagram showing another example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
In this example, the first restricted electronic money before the merger and the second restricted electronic money before the merger are prioritized, and when the merged restricted electronic money is used, the amount is consumed from the balance of the one with the higher priority.

In this case, by way of example and not limitation, the one with the smaller balance can be given higher priority. That is, for each payment, the merged restricted electronic money balance in the merged restricted electronic money management data is updated, and the restricted electronic money balance enclosed in "()" in the restricted electronic money management data is updated. At this time, the amount is consumed from the balance of the restricted electronic money with the smaller balance. Then, the balance is updated for each payment, and when the restricted electronic money balance enclosed in "()" in the restricted electronic money management data becomes "0", the merger of the merged electronic money with notification is released. Then, by way of example and not limitation, a notification is not sent to the notification destination account corresponding to the restricted electronic money whose balance has become "0".

In this example, the amount of restricted electronic money (first restricted electronic money) remitted by user B.B to user A.A is "1,000 yen," and the amount of restricted electronic money (second restricted electronic money) remitted by user C.C to user A.A is "2,000 yen." As a result, the balance display area BR2 of the main menu screen shown in the center of FIG. 13-1 displays that the balance of the first restricted electronic money is "1,000 yen," and the balance of the second restricted electronic money is "2,000 yen."
In this case, since the first limited electronic money balance is less than the second limited electronic money balance, an amount is consumed from the first limited electronic money balance.

In this example, the payment amount is 1,800 yen. In this case, the entire amount of 1,000 yen is consumed from the first limited electronic money balance of the merged limited electronic money, and the remaining 800 yen is consumed from the second limited electronic money balance.

The left side of Figure 13-6 is an example of a notification screen for a payment application displayed on the display unit 24 of the terminal 20, and is similar to the left side of Figure 13-3.

The center of FIG. 13-6 is a diagram showing an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20B.
This notification screen is almost the same as the screen in the center of Fig. 13-3, but the notification amount included in the restricted electronic money usage information RU127 is different. Specifically, the "1,000 yen" calculated as described above is displayed as the notification amount to user C.C.

The right side of FIG. 13-6 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20C.
This notification screen is almost the same as the screen in the center of Fig. 13-3, but the notification amount included in the restricted electronic money usage information RU128 is different. Specifically, the "800 yen" calculated as described above is displayed as the notification amount to user C.C.

FIG. 13-7 is a diagram showing another example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of Fig. 13-7 is a main menu screen of the payment application displayed on the display unit 24 of the terminal 20A, and the balance display area BR2 shows the balance (in this example, "3,000 yen") of the merged restricted electronic money obtained by merging the first restricted electronic money whose notification account is the account of user B.B and the second restricted electronic money whose notification account is the account of user C.C.

After that, assume that user A.A newly receives third restricted electronic money with user B.B's account as the notification account. In this case, as shown in the center of FIG. 13-7, the balance display area BR2 displays the balance of the merged electronic money (in this example, "3,000 yen") as well as the balance of the third restricted electronic money (in this example, "1,500 yen"). Also assume that the usage restrictions other than notifications on the merged restricted electronic money are the same as the usage restrictions other than notifications on the third restricted electronic money.

The restricted electronic money merge confirmation information MCR3 displays the message "Merge restricted electronic money?" along with the balance of the third restricted electronic money (in this example, "1,500 yen"), an illustration and a restriction mark RMK indicating that the account to be notified is user B.B's account, and the balance of the merged restricted electronic money (in this example, "3,000 yen"), an illustration and a restriction mark RMK indicating that the account to be notified is user B.B's account and user C.C's account.

Below that, the aforementioned "Combine" button BT101 and "Cancel" button BT102 are displayed. When the "Combine" button BT101 is tapped, the server 10 merges the third limited electronic money with the combined limited electronic money. As a result, as shown on the right side of FIG. 13-7, "4,500 yen" is displayed in the balance display area BR2 as the new combined limited electronic money balance.

Unlike the above, restricted electronic money for which notification is set may be made unable to be merged.
While this may not pose much of a problem in the example of the family mentioned above, there is a possibility that restricted electronic money accounts for which unknown users are the notification accounts may be merged, resulting in the unknown user being notified that the merged restricted electronic money has been used.

As an example and not a limitation, suppose that user X.X and user Y.Y are complete strangers, and that each has set their own account as the notification destination account and transferred restricted electronic money to user A.A, which has then been merged. In this case, by user A.A using the merged restricted electronic money, there is a possibility that user X.X or user Y.Y may receive an unexpected notification (as an example and not a limitation, a notification including an amount different from the expected amount used, etc.).

In addition, when restricted electronic money with notification settings are merged, the notification settings may be canceled. In this case, all usage restrictions other than the notification settings are carried over to the merged restricted electronic money.

<Processing>
As a non-limiting example of the process, in S730 of FIG. 12C, the control unit 11 of the server 10 determines whether or not restrictions other than the notification destination ID are the same.

It should be noted that, by taking into consideration the above-described embodiment, the following processing can be executed in the restricted electronic money with notification (merged restricted electronic money with notification) by way of example and not limitation.
At the terminal 20A of the account of the destination ID, before the notification-attached limited electronic money is used, a message is displayed indicating that a notification will be sent to the account of the destination ID (third modified example).
- If the terminal 20A of the account of the destination ID is set to refuse receipt of electronic money with notification and restriction, information indicating that the remittance of electronic money with notification and restriction has been refused is displayed on the terminal 20B of the account of the sender ID (third variant).
In terminal 20A of the account of the destination ID, receipt of notification-and-restricted electronic money from the account of terminal 20B is blocked (third modified example).
When a process for withdrawing the notification- and limited electronic money is executed at the terminal 20A, the control unit 11 of the server 10 transmits information indicating that the notification- and limited electronic money cannot be withdrawn to the terminal 20A (Fifth embodiment).

The same can be done by restricting the restricted electronic money to electronic money with notification. In this case, two or more electronic money with notification can be merged unconditionally. The notification pattern in this case is as described above.

<Effects of the Thirteenth Example>
In this embodiment, the first limited electronic money has a restriction set by the user of the second terminal as electronic money with notification (not a restriction, but an example of a restriction on a notification indicating that the user of the first terminal has used electronic money) as a restriction different from the first restriction. Also, the second limited electronic money has a restriction set by the user of the third terminal as electronic money with notification (not a restriction, but an example of a restriction on a notification indicating that the user of the first terminal has used electronic money) as a restriction different from the second restriction.
As an example of the effect of an embodiment obtained by such a configuration, a third electronic currency based on a first electronic currency in which a restriction regarding notifications indicating that the user of the first terminal has used the electronic currency, which restriction is different from the first restriction and is set by a user of a second terminal, and a second electronic currency in which a restriction regarding notifications indicating that the user of the first terminal has used the electronic currency, which restriction is different from the second restriction and is set by a user of a third terminal, can be associated with a user of a first terminal.

In this case, when at least a portion of the merged restricted electronic money (not limited to, but an example of a third electronic currency) is used by the user of the first terminal, the server 10 can transmit restricted electronic money usage information via the communication I/F 14 to the terminal 20 (not limited to, but an example of a fourth terminal) of the user of the notification destination account set by the user of the second terminal based on the restriction for notification, and can transmit restricted electronic money usage information via the communication I/F 14 to the terminal 20 (not limited to, but an example of a fifth terminal) of the user of the notification destination account set by the user of the third terminal based on the restriction for notification.
As an example of an effect of an embodiment obtained by such a configuration, when at least a portion of the third electronic currency is used by a user of the first terminal, a notification can be sent to a fourth terminal set by a user of the second terminal and a fifth terminal set by a user of the third terminal.

In this case, the server 10 can control the control unit 11 to not send restricted electronic money usage information when at least a portion of the merged restricted electronic money based on the first restricted electronic money (not limited to, but an example of the first electronic currency) and the second restricted electronic money (not limited to, but an example of the second electronic currency) is used by the user of the first terminal.
As an example of the effect of an embodiment obtained by such a configuration, even if at least a part of the third electronic currency is used by the user of the first terminal, no notification can be given.

In this case, the server 10 performs a process of associating the merged restricted electronic money (not limited, but an example of a third electronic currency) in which a restriction for issuing a notification is set with the user of the first terminal, and also associates the restricted electronic money (not limited, but an example of a fourth electronic currency) in which a restriction for issuing a notification is set with the user of the first terminal. In this case, the merged restricted electronic money in which a restriction for issuing a notification is set and the restricted electronic money in which a restriction for issuing a notification are set cannot be merged.
As an example of the effect of an embodiment obtained by such a configuration, if a notification restriction is set on a third electronic currency associated with a user of a first terminal based on the first restriction and the second restriction, and a notification restriction is also set on a fourth electronic currency, it is possible to prevent these electronic currencies from being made into a fifth electronic currency based on these electronic currencies, or in other words, from being merged.

In this case, the server 10 can be configured to send information to the first terminal via the communication I/F 14 confirming that notification will be given to the second terminal before at least a portion of the first restricted electronic money is used by the user of the first terminal.
As an example of an effect of an embodiment obtained by such a configuration, the user of the first terminal can be informed that a notification will be sent to the second terminal before at least a portion of the first electronic currency is used by the user of the first terminal.

In this case, if the user of the first terminal has set up the server 10 to not receive remittances for which notifications are set up, the server 10 can transmit information to the second terminal via the communication I/F 14 indicating that the first restricted electronic money cannot be associated with the user of the first terminal and cannot be remitted to the user of the first terminal.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to prevent the first electronic currency from being associated with the user of the first terminal against the will of the user of the first terminal, and it is also possible to inform the user of the second terminal that remittance to the user of the first terminal is not possible.

In this case, the setting for the user of the first terminal not to receive a remittance for which notification is set may include a setting for blocking the user of the second terminal.
As an example of the effect of an embodiment obtained by such a configuration, it is possible to block the user of the second terminal so that the user will not receive a remittance for which a notification is set.

In addition, this embodiment shows a configuration in which, when the server 10 receives withdrawal request information for withdrawing at least a portion of the merged restricted electronic money by a user of the first terminal, it sends withdrawal prohibition information for the merged restricted electronic money to the first terminal.
As an example of an effect of an embodiment obtained by such a configuration, when information regarding a user of the first terminal withdrawing at least a portion of the third electronic currency is received via the communication unit, the user of the first terminal can be informed that withdrawal is not possible.

<Thirteenth Modification (1)>
In the above embodiment, the notification destination is not involved in the determination of whether or not to execute the restricted electronic money merging process, but the present invention is not limited to this. As a non-limiting example, when the notification destinations are similar and the restrictions other than the notification destination ID are the same, the restricted electronic money merging process may be executed. In this case, as a non-limiting example, a condition for determining that the notification destinations are similar is when the relationship between the notification destination user and the remittance destination user is within the second degree of kinship. In this way, restricted electronic money with notification that notifies close users such as family members is merged, but it is possible to avoid erroneously merging restricted electronic money with notification that notifies complete strangers.

<Fourteenth Example>
In the above embodiment, restricted electronic money is merged when the restrictions are the same.
The fourteenth embodiment is an embodiment in which special restricted electronic money is not merged regardless of the conditions of restrictions, etc.

The contents described in the fourteenth embodiment are applicable to any of the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

In this embodiment, as an example and not a limitation, electronic money for running an errand is sent from a parent to a child. However, it is preferable that the electronic money for running an errand is returned (sent) from the child to the parent after the payment for the errand is completed. Restricted electronic money that is temporarily handed over for a certain purpose in this way is called "restricted electronic money for pooling." Restricted electronic money for pooling may be electronic money with notification, or restricted electronic money with usage restrictions imposed by electronic money usage restriction management data. It may also be restricted electronic money with notification.

Limited pool electronic money is electronic money that is automatically transferred (returned) to the account of the sender ID at a certain specified time (for example, but not limited to, the night after an errand is finished) according to, for example, but not limited to, the 11th embodiment. Therefore, it can also be treated as a normal electronic money balance that is limited to being transferred (returned) at a certain time.

<Data structure>
As for the data structure, the account management database 155J shown in FIG. 12A can be used as an example and not a limitation.
The restricted electronic money management data stores, by way of example and not by way of limitation, an electronic money remittance date and time in association with a remittance management ID. The electronic money remittance date and time stores the date and time when the remaining balance of the restricted electronic money is remitted (returned) to the remitter ID. The electronic money remittance date and time is, by way of example and not by way of limitation, a date and time set in the first restricted electronic money remittance setting process or the second restricted electronic money remittance setting process, or both, in the terminal 20B of the remitter account.

<Processing>
As a non-limiting example of the processing, in step S730 of FIG. 12-3, the control unit 11 of the server 10 refers to the restricted electronic money management data, and if the electronic money remittance date and time is set for the first restricted electronic money or the second restricted electronic money, the control unit 11 does not execute the restricted electronic money merging processing.

In addition, if the electronic money transfer date and time of the first restricted electronic money and the electronic money transfer date and time of the second restricted electronic money are the same, the control unit 11 of the server 10 may or may not execute a restricted electronic money merging process in which the first restricted electronic money and the second restricted electronic money are to be merged.

When the control unit 11 of the server 10 executes step S470 in Fig. 7-6, for example and not limitation, the control unit 11 acquires the current date and time using the clock unit 19 and determines whether the electronic money remittance date and time has passed. If the electronic money remittance date and time has passed, the control unit 11 of the server 10 executes steps from S620 in Fig. 11-3, for example and not limitation, with the restricted electronic money that has passed the electronic money remittance date and time as the object for return.
The control unit 11 of the server 10 may, but need not, determine whether the electronic money remittance date and time has passed at predetermined intervals (for example, but not limited to, at 0 minutes past the hour).

<Fifteenth Example>
In the above embodiment, an example has been shown in which merged restricted electronic money is generated when the restricted electronic money merging process for merging first restricted electronic money and second restricted electronic money is executed.
The fifteenth embodiment is an embodiment in which, when a limited electronic money merging process is executed for merging limited electronic money and normal electronic money, the limited electronic money is merged into normal electronic money.

The contents described in the fifteenth embodiment are applicable to any of the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

<Data structure>
Regarding the data structure, the account management database 155J shown in Fig. 12-1 can be used as an example and not as a limitation. If the merging of limited electronic money is not taken into consideration, the account management database 155F shown in Fig. 7-1 or the account management database 155G shown in Fig. 7-7 can be used as an example and not as a limitation.

<Display screen>
14-1 and 14-2 are diagrams showing examples of screens displayed on the display unit 24 of the terminal 20 in this embodiment.
14-1 shows a code payment screen of the payment application displayed on the display unit 24 of the terminal 20A, in which the balance of the restricted electronic money (in this example, "3,000 yen") and the restriction mark RMK are displayed in the wallet code information display area WR2. Also, "500 yen" is displayed as the normal electronic money balance. In this example, the restriction mark RMK is tapped, and the state in which the store where the restricted electronic money can be used (in this example, "Books and Stationery") is displayed is shown.

After that, when a payment of 2,800 yen is made at "XX Bookstore" using restricted electronic money, the payment result information shown in the center of Figure 14-1 is displayed.

The right side of Figure 14-1 shows the state in which the main menu screen of the payment application is then displayed on the display unit 24 of terminal 20A. In this example, based on the fact that 200 yen of restricted electronic money remains, restricted electronic money merge confirmation information MCR4 is displayed to confirm whether or not to merge this remaining amount of restricted electronic money into normal electronic money. When the aforementioned "Combine" button BT101 is tapped in the restricted electronic money merge confirmation information MCR4, the display shown on the left side of Figure 14-2 is displayed, by way of example and not limitation.

The server 10 executes the restricted electronic money merging process, and the restricted electronic money is merged with the normal electronic money, so that the balance display area BR2 shows the normal electronic money balance as "500 yen + 200 yen = 700 yen."

In this state, for example and not limitation, assume that the "Withdraw" icon IC3 is tapped. In this case, for example and not limitation, the screen in the center of FIG. 14-2 is displayed.
This screen is the withdrawal screen of the payment application mentioned above, and shows the state in which an input has been made to withdraw "500 yen" out of the normal electronic money balance of "700 yen", and the "Withdrawal" button BT52 has been tapped.

The right side of FIG. 14-2 shows an example of a notification screen of the payment application displayed on the display unit 24 of the terminal 20A in this case.
On the left side of the notification area, payment result information PR131 corresponding to the screen in the center of FIG. 14-1 is displayed, and below that, withdrawal result information WR131 indicating that "500 yen" has been withdrawn is displayed.

<Processing>
Fig. 14-3 is a flow chart showing an example of the flow of the process executed by each device in this embodiment, and shows the part corresponding to Fig. 7-6. Prior to Fig. 14-3, the user of terminal 20A may transmit normal electronic money charge request information for charging normal electronic money to server 10 via communication I/F 22, and control unit 11 of server 10 may execute normal electronic money charge processing for charging the balance of normal electronic money to the account of terminal 20A based on the received normal electronic money charge request information.

The control unit 21 of the terminal 20A transmits, as payment balance selection information, by way of example and not limitation, a restriction set in an arbitrary terminal, payment balance selection information including a remittance management ID of the sixth restricted electronic money remitted to the user of the terminal 20A to the server 10 via the communication I/F 22 (A420). Note that the control unit 21 of the terminal 20A may transmit, to the server 10, payment balance selection information including a merger management ID of the merged restricted electronic money to be merged with the first restricted electronic money and the second restricted electronic money.

The control unit 11 of the server 10 executes the limited payment process based on the received payment balance selection information (S450), and when it transmits the payment result information (S150), it determines whether the balance of the limited electronic money balance used for the payment (merged limited electronic money balance) is equal to or less than a specified balance (S760). Note that in S760, the control unit 11 of the server 10 may determine whether the balance of the limited electronic money balance used for the payment (merged limited electronic money balance) is less than a specified balance.

The specified balance here is the amount at which the restricted electronic money balance becomes small enough that it becomes difficult to use the balance alone. As a non-limiting example, the specified balance is 200 yen, which is an amount set by the user of server 10. Note that the specified balance may be an amount determined by the user of terminal 20A, or may be an amount specified by terminal 20 of the sender's account of the restricted electronic money balance (merged restricted electronic money balance). In the case of restricted electronic money with notification, the specified balance may be able to be specified by terminal 20 of the notified account.

The specified balance is not limited to a certain set amount. As a non-limiting example, it may be "specified balance" = "remaining balance ratio" x "limited electronic money balance at time of remittance (merged limited electronic money balance at time of merging)". As a non-limiting example, the remaining balance ratio is a ratio set by the user of the server 10, such as "5%". The remaining balance ratio may be a ratio determined by the user of the terminal 20A, or may be a ratio specified by the terminal 20 of the sender's account of the limited electronic money balance (merged limited electronic money balance). In the case of limited electronic money with notification, the remaining balance ratio may be able to be specified by the terminal 20 of the notified account.

If it is determined that the balance of the limited electronic money used for the payment (merged limited electronic money balance) is equal to or less than the specified balance (S760: YES), the control unit 11 of the server 10 executes a normal electronic money merging process (S770).
In the normal electronic money merging process, the control unit 11 of the server 10 adds the limited electronic money balance of the remittance management ID that is determined to be equal to or less than the predetermined balance to the normal electronic money balance, and then deletes the record designated by the remittance management ID from the limited electronic money management data.
If it is determined that the merged limited electronic money balance is equal to or less than the predetermined balance, the control unit 11 of the server 10 adds the merged limited electronic money balance of the merger management ID to the normal electronic money balance. Then, the control unit 11 of the server 10 deletes the record designated by the merger management ID from the merged limited electronic money management data. In addition, the control unit 11 of the server 10 may delete the record of the remittance management ID stored as the pre-merger remittance management ID from the limited electronic money management data.

Normal electronic money can also be considered as restricted electronic money, that is, electronic money without notification or restrictions. Therefore, the normal electronic money merging process can also be considered as a type of restricted electronic money merging process.

Also, the normal electronic money merging process may be executed without any conditions.

When the normal electronic money merging process is executed, the control unit 11 of the server 10 transmits normal electronic money merging process result information to the terminal 20A via the communication I/F 14. The control unit 11 of the server 10 may transmit the normal electronic money merging process result information to the terminal 20 of the sender account of the restricted electronic money merged in the normal electronic money merging process or the terminal 20 of the notification destination account.

If it is determined that the balance of the limited electronic money balance used for the payment (the merged limited electronic money balance) is greater than the specified remaining balance (S760: NO), the control unit 11 of the server 10 skips steps S770 and S780.

If it is determined that normal electronic money merging process result information is received from the server 10 via the communication I/F 22 (S740: YES), the control unit 21 of the terminal 20A causes the display unit 24 to display the received normal electronic money merging process result information (A750).
When it is determined that normal electronic money merging process result information has not been received from the server 10 (S740: NO), the control unit 21 of the terminal 20A skips step A750.

Then, the control unit 21 of terminal 20A, by way of example and not limitation, transmits normal electronic money withdrawal request information regarding the withdrawal of the normal electronic money balance to the server 10 via the communication I/F 22 based on an input (user operation) to the input/output unit 23 of terminal 20A. When the normal electronic money withdrawal request information is received from terminal 20A via the communication I/F 14, the control unit 11 of the server 10 executes the normal electronic money withdrawal process. The control unit 11 of the server 10 transmits normal electronic money withdrawal process result information, which is the processing result of the normal electronic money withdrawal process, to terminal 20A via the communication I/F 14, and the control unit 21 of terminal 20A may display the received normal electronic money withdrawal process result information on the display unit 24.

As an example and not a limitation, restricted electronic money withdrawal request information regarding a withdrawal from the restricted electronic money balance (merged restricted electronic money balance) is sent to the server 10 via the communication I/F 22 based on an input (user operation) to the input/output unit 23 of the terminal 20A. When the restricted electronic money withdrawal request information is received from the terminal 20A via the communication I/F 14, the control unit 11 of the server 10 sends restricted electronic money withdrawal disabled information indicating that the withdrawal is not possible to the terminal 20A via the communication I/F 14. When the restricted electronic money withdrawal disabled information is received from the server 10 via the communication I/F 22, the control unit 21 of the terminal 20A causes the display unit 24 to display the received restricted electronic money withdrawal disabled information.

<Effects of the 15th embodiment>
In this embodiment, a restricted electronic money remittance process for associating sixth restricted electronic money (as an example, not limiting, of a sixth electronic currency remitted from the fourth terminal to the first terminal, for which a third restriction is set by the user of the fourth terminal) with a user of terminal 20A (as an example, not limiting, of a first terminal) and a normal electronic money charge process for associating normal electronic money (as an example, not limiting, of a seventh electronic currency, for which no restriction is set) with a user of the first terminal, are performed by a control unit of a server; and a normal electronic money withdrawal process for associating normal electronic money (as an example, not limiting, of a seventh electronic currency, for which no restriction is set) with a user of the first terminal is performed by a control unit of a server. The server is configured to execute the following operations: when it receives restricted electronic money withdrawal request information (an example of information regarding withdrawing at least a portion of the eighth electronic currency based on the sixth electronic currency and the seventh electronic currency as cash), it sends restricted electronic money withdrawal impossible information (an example of withdrawal impossible information, not by way of limitation), indicating that withdrawal in cash is not possible, to the first terminal; and when it receives normal electronic money withdrawal request information (an example of information regarding withdrawing at least a portion of the eighth electronic currency based on the sixth electronic currency and the seventh electronic currency as cash, not by way of limitation), it performs normal electronic money withdrawal processing via the control unit, regarding withdrawing at least a portion of the normal electronic money (an example of the eighth electronic currency, not by way of limitation), as cash.
As an example of an effect of an embodiment obtained by such a configuration, when information is received regarding the withdrawal of at least a portion of the sixth electronic currency by the user of the first terminal, it is possible to inform the user of the first terminal that the withdrawal is not possible. On the other hand, when information is received regarding the withdrawal of at least a portion of an eighth electronic currency based on the sixth electronic currency and the seventh electronic currency, it is possible to make it possible to withdraw at least a portion of the eighth electronic currency.

In addition, this embodiment shows a configuration in which restricted electronic money (not limiting, but an example of the sixth electronic currency) can be combined with normal electronic money (not limiting, but an example of the seventh electronic currency) based on the condition that the balance of the restricted electronic money is below a specified balance (not limiting, but an example of a set combination condition), and the eighth electronic currency is an electronic currency formed by combining the sixth electronic currency and the seventh electronic currency.
As an example of the effect of the embodiment obtained by such a configuration, the sixth electronic currency can be added to the seventh electronic currency to obtain an eighth electronic currency based on the set addition condition.

In addition, this embodiment shows a configuration in which the combination condition includes a condition regarding a specified balance (not limited to, but an example of the balance of the sixth electronic currency) or a condition regarding the balance ratio (not limited to, but an example of the ratio of the balance to the amount of the sixth electronic currency transferred to the first terminal).
As an example of an effect of an embodiment obtained by such a configuration, the sixth electronic currency can be appropriately added to the seventh electronic currency based on conditions regarding the balance of the sixth electronic currency or conditions regarding the ratio of the balance to the amount of the sixth electronic currency transferred to the first terminal.

<16th Example>
In the above embodiment, an example has been shown in which the restricted payment process is performed using merged restricted electronic money in which the first restricted electronic money and the second restricted electronic money are to be merged.
The sixteenth embodiment is an embodiment in which a payment process with a continuous limit is executed using merged electronic money with a limit.

The contents described in the sixteenth embodiment are applicable to the other embodiments and the other modified examples.
Furthermore, the same components as those already mentioned are given the same reference numerals and will not be described again.

As an example and not a limitation, in a restricted electronic money merging process in which the first restricted electronic money and the second restricted electronic money are to be merged, they are merged into the first merged restricted electronic money. Also, as an example and not a limitation, in a restricted electronic money merging process in which the third restricted electronic money and the fourth restricted electronic money are to be merged, they are merged into the second merged restricted electronic money.

In this case, by way of example and not limitation, referring to the 12th embodiment and executing the limited electronic money merging process according to the flow of Figure 12-3, and then by way of example and not limitation, referring to the 9th embodiment and executing the payment process with consecutive restrictions according to the flow of Figure 8-3, the payment process can be executed in the following combinations.
・Normal electronic money and the first merged restricted electronic money・Normal electronic money and the second merged restricted electronic money・First merged restricted electronic money and the second merged restricted electronic money・Normal electronic money, the first merged restricted electronic money and the second merged restricted electronic money・The fifth restricted electronic money and the first merged restricted electronic money・The fifth restricted electronic money and the second merged restricted electronic money・The fifth restricted electronic money and the first merged restricted electronic money and the second merged restricted electronic money・Normal electronic money, the fifth restricted electronic money and the first merged restricted electronic money・The fifth restricted electronic money and the sixth restricted electronic money and the first merged restricted electronic money・Normal electronic money, the fifth restricted electronic money, the sixth restricted electronic money, the first merged restricted electronic money and the second merged restricted electronic money

In other words, payments can be made using any combination of regular electronic money, restricted electronic money, and merged restricted electronic money.

<Other Examples>
In the above embodiment, the "customer-presented" code payment has been described as a payment method using electronic currency, but the present invention is not limited to this. As a non-limiting example, the process may be performed using a "store-presented" code payment.
In this case, the store POS system 40 is not necessary. In the process of the "store-presented" code payment, first, the control unit 21 of the terminal 20A transmits wallet payment request information, and the server 10 transmits account identification information to the terminal 20. As a non-limiting example, the control unit 21 of the terminal 20A reads store information (store identification code information) presented by the store where the payment is made, by the imaging unit 27. The control unit 21 of the terminal 20A may capture an image of the product/service to be purchased by the imaging unit 27, and identify the product/service to be purchased based on the captured image. Unlike the "customer-presented" code payment, the control unit 21 of the terminal 20A can determine the available balance of each restricted electronic money before inputting the payment amount. Therefore, in the "store-presented" code payment, the payment amount can be input by referring to the available combined balance. The control unit 21 of the terminal 20A may transmit the store information and the captured image to the server 10, and calculate the available combined balance based on the store information and the captured image received by the server 10.
When the payment amount is entered based on input (user operation) to the input/output unit 23 of terminal 20A, the control unit 21 of terminal 20A sends payment request information including at least account identification information, store information, and the payment amount to the server 10, and the server 10 executes payment processing (payment processing with restrictions/payment processing with consecutive restrictions) based on the received payment request information.

Note that the payment method using electronic currency may be a payment method using short-range wireless communication such as NFC (NFC payment) instead of code payment. In this case, when wallet code information is received from server 10, control unit 21 of terminal 20A transmits the wallet code information to store POS system 40 via communication I/F 22. When wallet code information is received from terminal 20A via communication I/F 54, payment request information is transmitted to server 10 based on the received wallet code information.

＜Other＞
In the above embodiment, an example of making a payment using a terminal is illustrated, but the present invention is not limited to this. As a non-limiting example, in a plurality of servers 10 (server 10A, server 10B, ...), account management data is linked to a user's account on server 10A. Also, account management data is linked to a user's account on server 10B. Then, the process executed on terminal 20A may be executed by server 10A, and the process executed on terminal 20B may be executed by server 10B.
The information processing device of the remittance source account may or may not be the server 10B and the information processing device of the remittance destination account may or may not be the terminal 20A. Also, the information processing device of the remittance source account may or may not be the terminal 20B and the information processing device of the remittance destination account may or may not be the server 10A.

Reference Signs List 1 Communication system 10 Server 20 Terminal 30 Network 40 Store POS system

Claims (22)

A program executed by an information processing device that communicates with a first information processing device of a first user who can use a first electronic currency,
The information processing device executes a process related to a first payment by a control unit of the information processing device based on at least a portion of the first electronic currency of the first amount, for which a limit has been set by the first user and which can be used by the first user and which is borne by the first user through remittance , and at least a portion of the first electronic currency of the first amount, for which a limit has been set by the first user , which has been remitted from the first information processing device to the information processing device, and at least a portion of the second electronic currency associated with the user of the information processing device. The program according to claim 1,
The first electronic currency of the first amount for which a limit is set by the first user and the second electronic currency are selected based on an input by a user of the information processing device. The program according to claim 1,
The first electronic currency of the first amount for which a limit is set by the first user and the second electronic currency are selected based on a set condition. The program according to claim 3,
The set conditions are conditions set by a user of the information processing device. The program according to claim 4,
The set conditions include conditions regarding use of the electronic currency for which the restriction is set. The program according to claim 5,
The condition regarding the use of electronic currency having the restriction set therein includes the use of electronic currency having the strictest restriction. The program according to claim 6,
The use of electronic currency with stricter restrictions includes at least a small balance of electronic currency or a narrow category of usable currency. The program according to any one of claims 4 to 7,
The conditions set by the user of the information processing device include a condition regarding use in an order set by the user of the information processing device. The program according to claim 8,
The conditions set by the user of the information processing device include a condition regarding use of the electronic currency for which the restriction is set. The program according to any one of claims 1 to 9,
The information processing device executes control such that the control unit performs control to display on the information processing device the total amount of electronic currency available for the first payment , among multiple electronic currency available to the user of the information processing device, including the first electronic currency of the first amount for which a limit has been set by the first user, and the second electronic currency. The program according to any one of claims 1 to 10,
The information processing device executes control such that the control unit performs control to display on the information processing device the amount available for each payment category based on the restriction, of multiple electronic currencies available to the user of the information processing device , including the first electronic currency of the first amount for which a restriction is set by the first user, and the second electronic currency. The program according to claim 1,
The information processing device executes the following: based on conditions regarding the use of the first electronic currency of the first amount, for which a limit has been set by the first user, the balance of the first electronic currency of the first amount , for which a limit has been set by the first user, is transferred to the first user, and first information based on the transfer is received by a communication unit of the information processing device. The program according to claim 12,
The conditions regarding use include conditions regarding the balance of the first electronic currency in the first amount for which a limit has been set by the first user , or the ratio of the balance to the first amount, which is the amount of the first electronic currency in the first amount for which a limit has been set by the first user that has been transferred to the information processing device. The program according to claim 12 or 13,
The conditions regarding use include conditions regarding a period during which the information processing device can make payments using the first electronic currency of the first amount, the limit of which is set by the first user . The program according to any one of claims 12 to 14,
The conditions regarding the use include a condition regarding the number of times a payment is made using the first electronic currency of the first amount for which a limit is set by the first user . The program according to any one of claims 12 to 15,
The information processing device executes a process of displaying, on a display unit of the information processing device, second information for transferring the balance of the first electronic currency of the first amount, the limit of which is set by the first user, to the first user based on the conditions of use;
The balance of the first electronic currency of the first amount, for which a limit has been set by the first user , is transferred to the first user based on input by the user of the information processing device regarding the second information , and the first information is received. The program according to any one of claims 1 to 16,
The restrictions include at least one of the following: restrictions regarding notifying the first user when a user of the information processing device uses the first electronic currency of the first amount for which a restriction has been set by the first user; restrictions regarding stores where the first electronic currency of the first amount can be used for which a restriction has been set by the first user ; restrictions regarding goods or services for which the first electronic currency of the first amount can be used for which a restriction has been set by the first user; restrictions regarding categories of goods or services for which the first electronic currency of the first amount can be used for which a restriction has been set by the first user; restrictions regarding goods for which the first electronic currency of the first amount cannot be used for which a restriction has been set by the first user; restrictions regarding time periods during which the first electronic currency of the first amount cannot be used for which a restriction has been set by the first user; and restrictions regarding days or dates and times during which the first electronic currency of the first amount cannot be used for which a restriction has been set by the first user . 1. An information processing method of an information processing device that communicates with a first information processing device of a first user who can use a first electronic currency, comprising:
The method includes performing processing related to a first payment by a control unit of the information processing device based on at least a portion of the first electronic currency of the first amount, for which a limit has been set by the first user and which can be used by the first user and which is remitted from the first information processing device to the information processing device , and at least a portion of a second electronic currency associated with a user of the information processing device, the first electronic currency having no limit set by the first user and which can be used by the first user, wherein a limit has been set by the first user on the first electronic currency of the first amount to be borne by the first user through remittance. An information processing device that communicates with a first information processing device of a first user who can use a first electronic currency,
The system includes a control unit that performs processing related to a first payment based on at least a portion of the first electronic currency of the first amount for which a limit has been set by the first user and which can be used by the first user, the first electronic currency having no limit set by the first user and being borne by the first user through remittance , and at least a portion of the second electronic currency associated with the user of the information processing device, which is remitted from the first information processing device to the information processing device. A program executed by a server that communicates with a first information processing device of a first user who can use a first electronic currency and a second information processing device of a second user ,
a control unit of the server performs a process of associating the first electronic currency of a first amount, for which no limit has been set by the first user and which can be used by the first user, where a limit has been set by the first user on the first electronic currency of a first amount borne by the first user through remittance, with the second user of the second information processing device, and a process of associating the second electronic currency with the second user of the second information processing device;
The server executes, based on the information transmitted from the second information processing device, a process related to a first payment based on at least a portion of the first electronic currency of the first amount for which a limit has been set by the first user and at least a portion of the second electronic currency using the control unit. The program according to claim 20 ,
The restriction includes a restriction that, when the second user of the second information processing device uses at least a portion of the first electronic currency of the first amount for which a restriction has been set by the first user , a notification indicating that the second user of the second information processing device has used it is sent to the first information processing device by a communication unit of the server. The program according to claim 21 ,
When the restriction is set on the second electronic currency, the server controls the control unit so as not to transmit the notification to the first information processing device.

Images