Management device, management method, and program

Abstract

To improve user convenience.SOLUTION: A management device comprises a reception unit configured to receive a digital money deposit to a user of an electronic payment service, and a processing unit configured to perform processing for remitting the received digital money to a remittance destination account based on processing information specifying the remittance destination corresponding to a service different from the electronic payment service specified in advance by the user.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] 2. Description of the Related Art Conventionally, a management device that executes a deposit process using digital money has been disclosed (see, for example, Cited Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7053924 Summary of the Invention [Problem to be solved by the invention]

[0004] Conventional techniques have not always provided sufficient convenience for users.

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

[0006] One aspect of the present invention is a management device that includes a reception unit that accepts deposits of digital money for a user of an electronic payment service, and a processing unit that executes a process of transferring the accepted digital money to a destination account based on processing information that specifies a destination of a remittance that is a service different from the electronic payment service designated in advance by the user. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide a management device, a management method, a program, and an application program that can improve user convenience. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. [Diagram 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] 1 is a configuration diagram of a payment server 100 according to a first embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 1 is a diagram for explaining an outline of a remittance process. [Figure 8] FIG. 2 is a diagram showing an example of a top screen IF1 of a payment application 20. [Figure 9] 1 shows an interface screen IF2 for determining a remittance destination of digital money. [Figure 10] FIG. 13 is a diagram showing an example of an interface screen IF3 including a set remittance destination and a remittance amount. [Figure 11] FIG. 13 is a diagram showing an example of the contents of sorting information 178. [Figure 12] 10 is a sequence diagram showing an example of a flow of processes executed by the management application 30, the payment server 100, and a cooperation destination (server device). [Figure 13] FIG. 1 is a conceptual diagram of a process for transferring digital money. [Figure 14] 10 is a sequence diagram showing an example of the flow of processes executed by the management application 30, the payment server 100, and a cooperation destination. [Figure 15]FIG. 13 is a diagram showing an example of an interface screen IF4 including completion information. [Figure 16] FIG. 13 is a diagram showing an example of an interface screen IF5 displayed on the display unit of the user terminal device 10 before remittance (for example, immediately after depositing and immediately before remittance). [Figure 17] FIG. 13 is a diagram showing an example of extracted information 172# on the amount of use for each store. [Figure 18] FIG. 13 is a diagram showing an example of voucher information 180. [Figure 19] 13 is a flowchart showing an example of the flow of processing executed by the payment server 100. [Figure 20] 13 is a diagram showing an interface screen IF6 related to recommendations that the management application 30 displays on the display unit. FIG. [Figure 21] FIG. 13 is a diagram showing an interface screen IF7 for recommending release. [Figure 22] 13 shows an interface screen IF8 provided by a management application 30. FIG. [Diagram 23] 10 is a sequence diagram showing an example of the flow of processes executed by a management application, a payment server 100, and a bank server 200. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the payment server of the present invention will be described with reference to the drawings. The application program and the payment server cooperate to provide an electronic payment service. In the following description, the application program is referred to as a payment application. The electronic payment service is a service that supports payments related to the purchase of goods and services at a store. The store is, for example, a physical store (real store) existing in real space, but may also include a virtual store of electronic commerce. The virtual store may also include a store provided by an entity other than the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, the store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at the store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be performed between the user and the store.

[0010] [overview] The payment server of this embodiment comprises a reception unit that receives deposits of digital money from users of electronic payment services, and a processing unit that executes processing to transfer the accepted digital money to a remittance destination account (including an account assigned to the remittance destination or an account for a specified service) based on processing information that specifies a remittance destination which is a service different from the electronic payment service designated in advance by the user.

[0011] Digital money is an electronic transaction object such as currency, electronic money, points, etc. that is used independently by various companies, organizations, countries, etc. Accepting a deposit means executing a process (transfer of digital money) to electronically deposit digital money from another account into a user's account or accounts.

[0012] The remittance destination is, for example, a remittance destination managed by a service different from the electronic payment service. The remittance destination includes, for example, some or all of the following (but is not limited to): a credit card company used by the user, a loan company that provides a loan service used by the user, an insurance company that provides insurance to the user, or a securities company designated by the user. The remittance destination may also include the account of another user in the electronic payment service.

[0013] For example, the reception unit receives digital money that is periodically deposited. Digital money that is periodically deposited is digital money that is provided to a user periodically or at a predetermined interval, such as salary, rental income, stock dividends, and remittances. Each time the digital money is periodically deposited, the processing unit executes a process of transferring the digital money to the remittance destination account based on the processing information.

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

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

[0016] [Payment apps, management apps] The payment app 20 includes one or more mini apps such as the management app 30. For example, when the payment app 20 is downloaded to the user terminal device 10, the mini apps included in the payment app 20 are also downloaded to the user terminal device 10. The mini apps are applications developed to be able to be launched within the payment app 20. For example, the mini apps are launched within the payment app 20 and display various screens using a web view function. When the management app 30 is launched, it cooperates with the payment server 100 to display content provided by the payment server 100 on the display unit of the user terminal device 10 in cooperation with the payment server 100 (API; Application Programming Interface provided by the payment server 100). The management app 30 may also cooperate with the bank server 200 (API provided by the bank server 200) to display content provided by the bank server 200 (bank content) on the display unit of the user terminal device 10. For example, the management application 30 accesses a uniform resource locator (URL) and uses a web view function to display HTML (Hyper Text Markup Language) content provided by the payment server 100. The management application 30 and the payment application 20 may be integrated, and the various processes executed by the management application 30 may be executed by the payment application 20.

[0017] The management app 30 is an example of an "application program that causes a computer to accept operations that instruct a server device (payment server 100) to execute the following processes: accepting a deposit of digital money for a user of an electronic payment service; and transferring the accepted digital money to a destination account based on processing information that specifies a destination that is a service different from the electronic payment service designated in advance by the user.

[0018] In this embodiment, the electronic payment service is described as including the bank server 200 and the management application 30, but instead of (or in addition to) this, it may include other service servers and mini-applications for other services.

[0019] In addition, in this embodiment, various processes are described as being executed via the bank server 200 as an example, but alternatively, the bank server 200 may be omitted and various processes may be executed in cooperation with the payment source server 300, or services may be provided to users via an intermediary other server.

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

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

[0022] [Payment server] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the payment information is sent from the first store terminal device 50.

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

[0024] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0025] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

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

[0027] [Payment server] FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, an information processing unit 150, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transient storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

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

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

[0030] The payment content providing unit 120 has, for example, a function of a Web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content providing unit 120 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

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

[0032] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is information associated with, for example, a user URL, an account ID, a telephone number, a password, an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a post-payment setting, a post-payment limit, a post-payment usage amount, a post-payment available amount, a payment method setting, a bank account, a credit card number, charge history information, payment history information, voucher information, and a sub-account. The user URL is used for remittance processing between users and the granting of vouchers. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, the name, the address, and the date of birth are information that can be set by the user at will (does not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0033] The charge balance is information that indicates the balance of electronic money that is set by the user by transferring money to the account in advance. Methods of transfer include transfer from an ATM (Automatic Teller Machine) of a designated business (bank) and transfer from a registered bank account.

[0034] The deferred payment limit is the monthly available deferred payment limit, the deferred payment usage amount is the amount of deferred payment already used in the current month, and the available deferred payment amount is the amount of deferred payment available in the current month, calculated by subtracting the deferred payment usage amount from the deferred payment limit. Although only one deferred payment limit is shown in the figure, in reality, there may be additional daily upper limits, and the lower of these may be set as the deferred payment limit. Further details of deferred payment will be described later. The payment method setting is setting information indicating whether the user will make an electronic payment using the charge balance or a deferred payment at that time. The bank account and credit card number are information (account number, card number) of a bank account or credit card number that can be deposited into the electronic payment service. The charge history information is a history of the user transferring money to the electronic payment service in advance to increase the charge balance. The payment history information is information indicating the details of the payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each payment. The voucher information is information such as the amount of a voucher that can be used in an electronic payment service and the type of voucher (member stores, service providers, and products or services that can be used). A subaccount is an account that is subordinate to an account ID. A subaccount is an account in which digital money is saved. A user can operate the payment application 20 or the management application 30 to move the digital money saved in the subaccount to a charge balance or to another account or account (e.g., a remittance destination). In addition, the digital money saved in the subaccount can be converted into cash, and can be, for example, moved to a bank account or withdrawn from an ATM (Automatic Teller Machine).

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

[0036] The information management unit 140 manages user information 172 and affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, and deletes the user information 172 and affiliated store / store information 176.

[0037] The information processing unit 150 includes, for example, a deposit processing unit 152, a processing unit 154, and a remittance unit 156. The deposit processing unit 152 is an example of a "reception unit." One or both of the processing unit 154 and the remittance unit 156 are an example of a "processing unit."

[0038] The deposit processing unit 152, for example, accepts the deposit of digital money to a user of an electronic payment service. The processing unit 154 identifies a remittance destination based on sorting information 178 (processing information) that specifies a remittance destination that is a service different from the electronic payment service previously specified by the user, and performs various settings (for example, setting of the remittance destination) in cooperation with the management application 30. The remittance unit 156 executes a process of remitting the accepted digital money to the account of the remittance destination. Details of the processing by the information processing unit 150 will be described later.

[0039] [Electronic payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 to acquire the "payment method setting" of the user. For a user whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows. For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0040] The payment processing unit 130 performs electronic payment for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit payment" in cooperation with a credit card company that is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service acts as a creditor and allows electronic payment that is not dependent on the charge balance within the deferred payment limit. In order to receive the deferred payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used for deferred payment is settled on the payment date of the following month, for example, by debiting from a bank account, for one month. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the deferred payment amount and subtracting the same amount from the deferred payment available amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above. In addition, if the payment amount exceeds the deferred payment available amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0041] [Bank server] The bank server 200 is a device that manages the bank account of the user. Based on an instruction from the payment source server 300, the bank server 200 transfers the digital money deposited in the bank account of the user to the payment server 100. Cash may be deposited in the bank account instead of digital money. In this case, the bank server 200 may convert the money in the bank account into digital money, or the payment server 100 may convert the money transferred from the bank account into digital money.

[0042] [Payment Server] The payment source server 300 is a device managed by a business that pays salaries to users. The payment source server 300 periodically pays salaries to users. Salaries are paid, for example, in digital money.

[0043] [Remittance processing] The information processing unit 150 accepts digital money deposits from users of electronic payment services, and executes remittance processing to remit the accepted digital money to a remittance account based on sorting information 178 that specifies a remittance destination that is a service different from the electronic payment service designated in advance by the user.

[0044] FIG. 7 is a diagram for explaining an overview of remittance processing. When the payment source server 300 instructs the bank server 200 to pay a user's salary, the bank server 200 transfers the salary from the payment source's account to the user's account. The bank server 200 transfers the transferred digital money to the user's account in the payment server 100. This allows the user to receive the salary in digital money. Furthermore, the payment server 100 transfers the salary to a remittance destination preset by the user.

[0045] The remittance destination may be, for example, the credit card company of the credit card being used, the repayment destination of a loan, an electronic payment service account or account of a pre-designated person such as a wife, an insurance company that provides the insurance subscribed to, a securities company being used, a sub-account of the user, the charge balance of the user's (or a designated person's) account, a designated bank account, the seller of the voucher, etc. When the money is remitted to the seller of the voucher, the user can obtain the voucher.

[0046] [Top page] FIG. 8 is a diagram showing an example of the top screen IF1 of the payment application 20. A code image CD is displayed on the top screen IF1. The code image CD includes, for example, a barcode and a QR code. The top screen IF1 also includes a button B1 for displaying an interface screen for determining a remittance destination. The "button (switch)" is a GUI (Graphical User Interface) realized in cooperation with a touch panel. When the button B1 is operated, the management application 30 starts up and transitions to an interface screen IF2 in FIG. 9, which will be described later. The top screen IF1 also includes buttons for starting various services and buttons for starting prepared mini-applications. The various services are various services such as services provided by electronic payment services and services linked to electronic payment services.

[0047] [Screen for deciding where to send money] FIG. 9 is an interface screen IF2 for determining the remittance destination of digital money. The interface screen IF2 includes a button B2 for setting the amount of salary to be deposited and the remittance destination from a list of remittance destinations, a button B3 for setting by the user's operation, and the like. When the button B2 is operated, a list of remittance destinations is displayed, and the user can set the remittance destination and the amount to be remitted by selecting the desired remittance destination from the list. When the button B3 is operated, an interface screen (not shown) for inputting the remittance destination is displayed, and the remittance destination can be set by inputting the information of the remittance destination (for example, a bank account number or an account of an electronic payment service) and the amount to be remitted into the interface screen. FIG. 10 is a diagram showing an example of the interface screen IF3 including the set remittance destination and the amount to be remitted.

[0048] As described above, the management application 30 accepts the remittance destination and the amount to be remitted in response to the user's operation, and the management application 30 and the information processing unit 150 cooperate to generate sorting information 178. Fig. 11 is a diagram showing an example of the contents of the sorting information 178. The sorting information 178 is information in which the remittance destination, the amount to be remitted, the execution conditions, the priority, and the cooperation destination are associated with each other. The execution conditions are conditions for executing the remittance, such as the date for executing the remittance and whether the salary has been deposited.

[0049] Priority is the priority of the remittance destination, and remittances are made preferentially to remittance destinations with higher priority. For example, if there is a shortage of digital money and the remittance amount is insufficient, remittances to remittance destinations with lower priority are not made, and the user is notified via the management app 30 that the remittance could not be made. In response to the notification, the user can operate the management app 30 to change the amount to be remitted, or can make a remittance using digital money saved in a subaccount.

[0050] The associated party is information such as a server device, a network, and a network address that are associated in processing a remittance to a remittance destination. The settlement server 100 cooperates with an associated party (server device) associated with a preset remittance destination to transfer money to the remittance destination's account of a service other than the electronic settlement service.

[0051] In the above example, a preset amount is remitted, but in addition (or instead), the user may set sorting information 178 so that the amount designated by the remittance destination is remitted to the remittance destination. For example, electricity bills, communication charges, etc. may be set so that the payment server 100 remits digital money in an amount designated by the remittance destination. In this case, remittance unit 156 remits the amount designated by the remittance destination to the remittance destination.

[0052] [Sequence diagram (part 1)] FIG. 12 is a sequence diagram showing an example of the flow of processing executed by the management application 30, the payment server 100, and the associated party (server device). First, the management application 30 accepts an operation for registering a remittance destination by a user (S100), and transmits the accepted information (registration information) to the payment server 100 (S102). Next, the payment server 100 generates sorting information 178 based on the registration information (S104). Next, the payment server 100 cooperates with the associated party of the sorting information 178 to transmit a cooperation request (S106). The cooperation request includes information such as the shared user identification information, information indicating that the user will make a payment by remittance, and the remittance date.

[0053] The cooperation destination receives the cooperation request, executes the cooperation process (S108), and transmits a completion notice indicating that the cooperation process has been completed to the payment server 100 (S110). The cooperation process is, for example, a process in which the cooperation destination registers the user's identification information and the fact that the user's payment will be made by digital money on a specified date in cooperation with the payment server 100. When the user registers a remittance destination via the management application 30, the process may be executed assuming that the user has consented to sharing the information of the user of the electronic payment service in the contacts, or the user may be separately requested to share the information and consent obtained.

[0054] Next, when the payment server 100 receives the completion notification, it finalizes the sorting information 178 (S112) and transmits the finalized information to the management application 30 (S114). Next, when the management application 30 receives the finalized information, it displays the finalized information on the display unit (S116). As a result, the sorting information 178 in Fig. 11 described above is generated, and the interface screen IF3 in Fig. 10 is displayed on the display unit.

[0055] As described above, users can easily set the remittance destination, which improves user convenience.

[0056] Then, the settlement server 100 remits the deposited digital money to the remittance destination as shown in Fig. 13 based on a predetermined timing such as a payday and on the sorting information 178. Fig. 13 is a conceptual diagram of the process of remittance of digital money.

[0057] [Sequence diagram (part 2)] FIG. 14 is a sequence diagram showing an example of the flow of processing executed by the management application 30, the payment server 100, and the associated destination. First, the payment server 100 judges whether or not the salary has been deposited (S200). If the salary has been deposited, the payment server 100 executes a remittance process by referring to the sorting information 178 (S202), and transfers the salary to the associated destination (S204). For example, the payment is deposited into a subaccount of the user information 172, and then transferred to each associated destination. Alternatively, the payment may be transferred to each associated destination without going through a subaccount.

[0058] Next, the cooperating party performs a process of receiving the remittance (S206) and transmits a receipt notification to the settlement server 100 (S208). For example, the cooperating party identifies the user corresponding to the remittance, confirms that the payment of the identified user has been made, and transmits a receipt notification to the settlement server 100 after the confirmation is completed.

[0059] Next, upon receiving the receipt notification, the payment server 100 modifies the user information 172 (S210). For example, the payment server 100 modifies the amount deposited into the subaccount of the user information 172, or modifies the charge balance. Next, the payment server 100 transmits a remittance completion notification to the management application 30 (S212). Next, the management application 30 displays completion information indicating that the remittance has been completed on the display unit (S214).

[0060] 15 is a diagram showing an example of an interface screen IF4 including completion information. The interface screen IF4 includes information such as the date on which the salary was deposited, the salary amount, the remittance destination, the amount remitted to the remittance destination, and the processing date on which the remittance was completed. The completion information may be displayed each time one remittance process is completed, or may be displayed after all remittances to all predetermined remittance destinations are completed. For example, when a user performs a predetermined operation on the management application 30, a screen showing a list of information (e.g., amount, deposit source, remittance destination, deposit date, remittance date, etc.) showing deposits and expenditures during a period specified by the user is displayed.

[0061] As described above, the payment server 100 executes the process of sending digital money to a previously designated remittance destination, thereby improving the convenience for the user. For example, the user can determine each remittance destination by operating the management application 30. This allows the user to easily select a remittance destination without performing complicated processes. As a result, the convenience for the user is improved.

[0062] In addition, the user can collectively manage expenditures at linked destinations by using the management application 30 as described above. For example, if loan or insurance payments, remittances (P2P remittances such as remittances to one's wife), subaccount balances, charge balances, payments for purchasing gift vouchers, and the like are made via different applications or different systems, the user may not accurately grasp the cash flows and assets such as the above expenditures and balances. In addition, in order to grasp such information, it is necessary to obtain information from each system or application, and it may be difficult to grasp such information. In contrast, the management application 30 can collectively manage the cash flows and assets such as the above expenditures and balances. This allows the user to easily control how to spend his / her salary, for example, by using a function that allows the salary to be managed collectively or in a continuous manner.

[0063] In the above process or the process of each modification, the information processing unit 150 may execute a process for converting a predetermined ratio or more of the deposited amount of digital money into cash. The process for converting into cash is a process for depositing into a designated bank account, or a process for depositing as cash into a predetermined account of an electronic payment service. The predetermined account is, for example, a subaccount. The digital money deposited into this subaccount can be converted into cash, transferred to a bank account, or withdrawn from an ATM by the user's operation. In this way, the payment server 100 can improve the usability of the user's salary and improve the user's convenience by maintaining a part of the salary in a state that can be converted into cash.

[0064] In the above process or the process of each modification, the information processing unit 150 may allow digital money of less than a predetermined percentage of the deposited amount to be remitted. In other words, the information processing unit 150 may not allow digital money of more than a predetermined percentage of the deposited amount to be remitted. In this way, the payment server 100 can suppress the remittance of digital money for maintaining life, etc., by not remitting part of salary.

[0065] <Variation 1> In the above example, it has been described that remittance to the remittance destination is automatically performed, but instead (or in addition), remittance may be performed after obtaining the user's consent. The information processing unit 150 inquires whether or not to consent to remittance to the remittance destination based on the timing of deposit of digital money and sorting information 178 that specifies a remittance destination that is a service different from the electronic payment service specified by the user. When the information processing unit 150 obtains information indicating consent from the management application 30, it executes processing to remit money to the remittance destination account.

[0066] 16 is a diagram showing an example of an interface screen IF5 displayed on the display unit of the user terminal device 10 before remittance (for example, immediately after depositing money and immediately before remittance). Interface screen IF5 includes, for example, a remittance destination, an amount to be remitted, a button for instructing execution of remittance, and a button for accepting an operation to change the amount. After a salary is deposited, a user may refer to interface screen IF5 to check the remittance destination and amount to be remitted, and instruct remittance.

[0067] The user may also set it so that remittances to pre-specified remittance destinations are executed automatically, and remittances to other remittance destinations are executed after confirmation. For example, it may be set so that payments that need to be paid on a specific date, such as rent or credit card payments, are executed automatically, and remittances to specified people and voucher purchases are executed after confirmation. That is, the information processing unit 150 may determine whether or not an inquiry is required for the automatic remittance process based on information on whether or not an inquiry is required that is pre-set by the user, and if an inquiry is required, make an inquiry to the user, and if the inquiry is not required, automatically execute the remittance to the remittance destination without making an inquiry.

[0068] As described above, the user can determine the mode of processing for sending money to the remittance destination according to his / her preference and the nature of the remittance to the remittance destination, thereby improving convenience for the user.

[0069] <Variation 2> In the above example, the remittance destination includes an account for purchasing a voucher usable at a store designated by the user, and the information processing unit 150 transfers money to the account for purchasing the voucher, and acquires and manages the voucher. The management application 30 may suggest purchasing a voucher. For example, the information processing unit 150 may recommend the purchase of a voucher usable at a store based on the store where the electronic payment service was used and the degree of use of the store, and when the user performs an operation to accept the recommendation, transfer money to an account for purchasing the voucher according to the deposit of digital money, and acquire and manage the voucher. The voucher is, for example, a voucher for receiving a product or service worth a larger amount than the amount required for purchase.

[0070] The payment server 100, for example, refers to the user information 172 to extract the usage amount for each store of the electronic payment service used by the user for a predetermined period. The payment server 100 may take into account usage amounts other than those for the electronic payment service, or may refer to other information instead of (in addition to) the user information 172. The other information may be, for example, a usage history of a cooperable household accounting app, other devices, or a credit card provided by the user, or a purchasing history. FIG. 17 is a diagram showing an example of the extracted information 172# of the usage amount for each store.

[0071] The payment server 100 extracts a voucher to be recommended by referring to the information on the amount of use 172# and the voucher information 180 stored in the storage unit 170. FIG. 18 is a diagram showing an example of the voucher information 180. The voucher information 180 is information in which a store (affiliated store), a user to whom a voucher is recommended, and the contents of the voucher to be recommended to the target user are associated with each other. For example, the voucher information 180 specifies that a voucher from a supermarket XX that can be purchased for 10,000 yen and can be used for 12,000 yen is recommended to a user who has spent 10,000 yen or more (or a user who satisfies any condition, such as a user who has spent 9,000 yen or more).

[0072] [flowchart] 19 is a flowchart showing an example of the flow of the process executed by the payment server 100. First, the payment server 100 judges whether or not a predetermined timing has arrived (S300). The predetermined timing is, for example, the timing to execute a remittance process.

[0073] When a predetermined timing arrives, the payment server 100 calculates the amount used for each store and generates the amount information 172# (S302). Next, the payment server 100 refers to the amount information 172# and the voucher information 180 to identify a voucher to be recommended (S304). Next, the payment server 100 determines whether or not the voucher to be recommended has been identified (S306). If the voucher to be recommended has not been identified, the processing of one routine of the flowchart of this processing ends.

[0074] When the recommended voucher is identified, the payment server 100 recommends the user to purchase the recommended voucher (S308). The recommendation may be made, for example, when a salary is deposited or before a remittance process is executed. FIG. 20 is a diagram showing an interface screen IF6 related to the recommendation displayed on the display unit by the management application 30. The interface screen IF6 includes, for example, the merits for the user to purchase the voucher, the amount used at the store that the voucher is applicable to last month, the contents of the voucher, and a button for setting the purchase of the voucher (for example, monthly purchase). The user can set the purchase of the voucher by operating the setting button B11 of the interface screen IF6. As a result, the payment server 100 automatically performs the remittance for purchasing the voucher.

[0075] In the above example, the purchase of a voucher may be recommended based on the monthly usage amount. For example, if the usage is such that it is more advantageous to purchase a voucher over a two-month or three-month period (if a certain amount or more is used each month), the purchase of a voucher may be recommended. Also, instead of a recommendation, the purchase may be automatically performed.

[0076] For example, in the case where a user has set a voucher purchase every month, if the user has not used up all the vouchers, the user may be recommended to cancel the voucher purchase setting. Fig. 21 is a diagram showing an interface screen IF7 for recommending cancellation. For example, if the amount of purchases at a store has not reached an amount where purchasing a voucher would be beneficial, the payment server 100 may display an interface screen IF7 on the display unit that includes a recommendation to the user to cancel the monthly purchase and a cancellation button.

[0077] As described above, the payment server 100 proposes the purchase of a voucher that is beneficial to the user. If the user accepts the proposal, the payment server 100 automatically purchases the voucher. In this way, the proposal and remittance process that are beneficial to the user are provided, improving the user's convenience.

[0078] <Variation 3> The user may operate the management app 30 to set up debits from a bank account of a partner. The user can operate the management app 30 to set the items to be debited from the bank account and the information on the source of the deduction. For example, the user can set up the bank account to be debited for rent from XX Management Service, or to be debited for electricity from XX Electricity.

[0079] 22 is a diagram showing an interface screen IF8 provided by the management application 30. For example, when the user sets the withdrawal as described above, the interface screen IF8 sets that the payment is withdrawn from the bank account of the affiliated bank. In this case, for example, the remaining amount of the salary after the withdrawal is transferred to the payment server 100 in digital money.

[0080] Fig. 23 is a sequence diagram showing an example of the flow of processing executed by the management application, the payment server 100, and the bank server 200. The sequence diagram in Fig. 23 is an embodiment in which the link destination in the sequence diagram in Fig. 12 is replaced with the bank server 200, and the flow of processing is the same as that in Fig. 12, and therefore description of each process will be omitted.

[0081] As described above, the user can operate the management application 30 to set up bank withdrawals, remittances, and the like in cooperation with the payment server 100, thereby improving user convenience.

[0082] According to the embodiment described above, the payment server 100 accepts deposits of digital money from users of electronic payment services, and executes a process of transferring the accepted digital money to a destination account based on processing information that specifies a destination that is a service different from the electronic payment service previously designated by the user, thereby improving user convenience.

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

[0084] 10 User terminal device 20. Payment App 30 Management App 100 Payment Server 120 Payment Contents Provider 130 Payment processing unit 140 Information Management Department 150 Information Processing Section 152 Deposit Processing Unit 154 Processing section 156 Remittance Department 178 Sorting Information

Claims

1. A reception desk that accepts digital money deposits from users of electronic payment services, A processing unit that executes a process to transfer the received digital money to the accounts of the multiple recipients based on processing information that specifies multiple recipients corresponding to each of multiple services of different or similar types as the electronic payment service specified in advance by the user, A control device equipped with the following features.

2. The processing unit is The interface screen for setting the recipient of the aforementioned digital money is displayed on the display unit. In response to user operations on the interface screen, the processing information sets multiple different types of recipients as recipients for the digital money. Based on the processing information, the process of sending the received digital money to the accounts of the multiple different recipients is executed. The control device according to claim 1.

3. The processing unit is The interface screen, which includes the deposit history of the digital money and the transfer history of the digital money being sent to the multiple recipients, is displayed on the display unit. The control device according to claim 1 or 2.

4. The aforementioned reception department accepts deposits of digital money that are deposited on a regular basis. The processing unit executes a process to transfer the digital money to the recipient account based on the processing information each time the regularly deposited digital money is received. The control device according to claim 1 or 2.

5. The processing information is information that associates the recipient with the amount to be sent to that recipient. The processing unit transfers the amount associated with the recipient to the recipient's account. The control device according to claim 1 or 2.

6. The processing unit transfers the specified amount sent from the recipient's server device to the recipient's account. The control device according to claim 1 or 2.

7. The processing unit, in cooperation with a server device associated with a pre-configured recipient, sends funds to the recipient's account that is not managed by the electronic payment service. The control device according to claim 1 or 2.

8. The aforementioned recipient of the remittance includes some or all of the following: the credit card company used by the user, the loan company providing the loan service used by the user, the insurance company providing the insurance the user has purchased, or the securities company designated by the user. The control device according to claim 1 or 2.

9. The aforementioned recipient of the remittance includes an account for purchasing vouchers that can be used at stores designated by the user. The processing unit transfers funds to an account for purchasing the voucher, obtains the voucher, and manages it. The control device according to claim 1 or 2.

10. The processing unit recommends the purchase of a voucher usable at the store based on the store that used the electronic payment service and the degree of store usage. When the user performs an action that allows the aforementioned recommendation, In response to the deposit of the aforementioned digital money, the funds are transferred to an account for purchasing the aforementioned vouchers, and the vouchers are obtained and managed. The control device according to claim 9.

11. The aforementioned voucher is a voucher that allows the recipient to receive goods or services worth more than the amount spent on the purchase. The control device according to claim 10.

12. The recipient of the remittance includes an account of a user of the electronic payment service who is different from the user mentioned above. The processing unit executes the process of transferring funds to the accounts of the different users. The control device according to claim 1 or 2.

13. The aforementioned processing unit, Based on the timing of the deposit of the digital money and the processing information specifying a recipient service that is different from the electronic payment service designated by the user, the user is asked whether or not to consent to the transfer to the recipient service. If information indicating acceptance is obtained, the process of transferring funds to the aforementioned recipient account will be executed. The control device according to claim 1 or 2.

14. The aforementioned processing unit, Based on the information regarding the necessity of inquiries set in advance by the user, the system determines whether an inquiry is necessary for the process of automatically transferring funds. If the aforementioned inquiry is necessary, the user will be contacted. If the aforementioned inquiry is denied, the system will automatically execute the transfer to the recipient without making the aforementioned inquiry. The control device according to claim 13.

15. The aforementioned processing unit, Refer to the information indicating the priority of the pre-configured recipients. The process of sending funds to the aforementioned high-priority recipient is executed with priority. The control device according to claim 1 or 2.

16. The processing unit performs a process to convert a predetermined percentage or more of the deposited amount of digital money into cash. The control device according to claim 1 or 2.

17. The process for converting to cash is to deposit the funds into a designated bank account or into a specified account of the electronic payment service. The control device according to claim 16.

18. Computers The process of accepting digital money deposits from users of electronic payment services, A process that executes the process of sending the received digital money to the accounts of the multiple recipients based on processing information that specifies multiple recipients corresponding to each of multiple services of different or similar types, which have been designated in advance by the user, A management method for executing this.

19. On the computer, The process of accepting digital money deposits from users of electronic payment services, A process that executes the process of sending the received digital money to the accounts of the multiple recipients based on processing information that specifies multiple recipients corresponding to each of multiple services of different or similar types, which have been designated in advance by the user, A program that executes the command.

Images