JP7421272B2 - Account management device, payment management system and program - Google Patents

Description

The present invention relates to an account management device, a payment management system, and a program.

There are known payment systems that, when making a payment using a credit card, debit card, etc., send information indicating that the card was used or information on the purchased product to a third-party terminal. (For example, please refer to Patent Document 1 or 2).
[Prior art documents]
[Patent document]
[Patent Document 1] Japanese Patent Application Publication No. 2018-181381 [Patent Document 2] Japanese Patent Application Publication No. 2018-200535

In conventional payment systems, payment methods such as credit cards and debit cards are only associated with a single account. Further, the above-mentioned single account cannot be treated virtually as if it were a plurality of accounts.

In a first aspect of the present invention, an account management device is provided. The above account management device is, for example, a device for managing an account for each user to record at least one of an increase/decrease in property value and the current amount of the user. The above account management device includes, for example, a deposit information acquisition unit that acquires deposit information indicating that a first amount of property value is deposited into the first user's account. The above account management device includes, for example, a detection unit that detects that the property value deposited in the first user's account is used to pay at least a portion of the price for the product or service purchased by the first user. Equipped with. For example, when the detection unit detects that the property value deposited in the first user's account is used for the payment, the account management device described above is configured to use the first user's account management device for the payment based on the deposit information. The present invention includes an instruction output unit that outputs an instruction for generating payout information indicating that the property value deposited in the account is to be used. In the above account management device, for example, the payout information includes information indicating a client who has requested deposit of property value to be used for payment.

The above account management device may include a payout information acquisition unit that acquires payout information. In the above account management device, after the payout information acquisition unit acquires the payout information, the payout information acquisition unit includes information regarding the product or service purchased by the first user to the client who has requested the deposit of the first amount of property value. It may include a message transmitter that transmits a message. In the above account management device, the deposit information is associated with deposit amount information indicating the first amount, client identification information for identifying the client, and client address information indicating the client's communication address. It may be information that has been received. In the above account management device, the message transmitter may transmit a message to the communication address indicated by the client address information.

The above account management device may include a deposit screen generation unit that generates a deposit screen used to output deposit information based on input from a client. In the account management device described above, the deposit screen may include a deposit amount input field that accepts input of deposit amount information. In the account management device described above, the deposit screen may include a client input field for accepting input of client identification information. In the account management device described above, the deposit screen may include an address input field for accepting input of client address information.

In the above account management device, the payout information includes value identification information for specifying the property value used for payment, content information indicating at least one of the category and content of the product or service, and the consideration for the product or service. The information may be associated with consideration information indicating the amount of. In the account management device described above, the message transmitter may transmit a message including at least one of the product or service category and the content indicated by the content information.

The above account management device may include an individual management unit that individually manages at least one of an increase/decrease in property value deposited in the first user's account and the current amount based on the deposit information. In the above-mentioned account management device, the individual management unit determines whether the property value specified by the value specifying information included in the payout information includes the property value deposited in the first user's account based on the deposit information. , reduce the property value by the amount indicated by the consideration information included in the disbursement information from the current value of the property value indicated by the deposit information acquired by the deposit information acquisition unit at the time immediately before the disbursement information is acquired; With this, a new current amount can be calculated.

In the above account management device, the deposit information acquisition unit may acquire a plurality of pieces of deposit information. In the above account management device, the individual management unit may individually manage at least one of an increase/decrease in the property value deposited in the first user's account and the current amount based on each of the plurality of deposit information. In the above account management device, the deposit information acquisition unit may acquire a plurality of pieces of deposit information. The above account management device may include a classification unit that classifies at least a portion of the plurality of deposit information into one or more groups. In the above-mentioned account management device, the individual management unit is configured to determine, for each of the one or more groups, at least an increase or decrease in the property value deposited in the first user's account and the current amount based on the deposit information classified into the group. One may be managed individually for each group. The above account management device may include a central management unit that centrally manages at least one of all increases and decreases in property value managed in the first user's account and the current amount.

In a second aspect of the invention, an account management device is provided. The above account management device is, for example, a device for managing an account for each user to record at least one of an increase/decrease in property value and the current amount of the user. The above account management device includes, for example, a deposit information acquisition unit that acquires deposit information indicating that a first amount of property value is deposited into the first user's account. For example, the above account management device may use the property value deposited in the first user's account based on the deposit information to pay at least a portion of the price for the product or service purchased by the first user. The payout information acquisition unit is provided to obtain payout information indicating the payout information. For example, after the payout information acquisition unit acquires the payout information, the account management device may transmit information regarding the product or service purchased by the first user to the client who has requested the deposit of the first amount of property value. The device includes a message transmitter that transmits a message including the message.

In a third aspect of the present invention, an information processing device is provided. The above-mentioned information processing device, for example, accesses the account management device according to the above-described first form or second form and specifies the property value deposited in the first user's account based on the deposit information. A value specifying information acquisition unit is provided to obtain value specifying information for the purpose of the present invention. The above information processing device includes, for example, an account specifying information acquisition unit that acquires account specifying information for specifying the first user's account. The above-mentioned information processing device includes, for example, a specific information output unit that outputs the value specific information acquired by the value specific information acquisition unit and the account specific information acquired by the account specific information acquisition unit in association with each other to the outside.

The above information processing device may include a purchase information acquisition unit that acquires purchase information for determining the amount of consideration for the product or service purchased by the first user. In the above information processing device, the specific information output unit outputs the value specific information acquired by the value specific information acquisition unit, the account specific information acquired by the account specific information acquisition unit, and the purchase information acquired by the purchase information acquisition unit. You can associate them and output them externally.

In a fourth aspect of the invention, a payment management system is provided. The payment management system described above includes, for example, the account management device according to the first form or the second form described above. The above payment management system includes, for example, the information processing device according to the third embodiment.

In a fifth aspect of the present invention, a program is provided. A non-transitory computer readable medium may be provided that stores the above program. The above program is, for example, a program for causing a computer to function as the account management device according to the first aspect. The above program is, for example, a program for causing a computer to function as the account management device according to the third aspect.

Note that the above summary of the invention does not list all the necessary features of the invention. Furthermore, subcombinations of these features may also constitute inventions.

1 schematically shows an example of a system configuration of a payment system 100. An example of the data structure of deposit/withdrawal details data 200 is schematically shown. An example of the data structure of current high data 300 is schematically shown. An example of information processing in the payment system 100 is schematically shown. An example of the internal configuration of the sales terminal 122 is schematically shown. An example of the internal configuration of the store server 124 is schematically shown. An example of the data structure of a data table 700 is schematically shown. An example of the internal configuration of the account management server 144 is schematically shown. An example of the data structure of a data table 900 is schematically shown. An example of the internal configuration of the deposit/withdrawal management unit 816 is schematically shown. An example of the data structure of a data table 1100 is schematically shown. An example of a screen 1200 is schematically shown. An example of a screen 1300 is schematically shown. An example of a screen 1400 is schematically shown. An example of the internal configuration of the communication terminal 22 is schematically shown. An example of information processing in the deposit/withdrawal management unit 816 is schematically shown. An example of information processing in the deposit/withdrawal management unit 816 is schematically shown. An example of information processing in the deposit/withdrawal management unit 816 is schematically shown. An example of information processing in the payment system 100 is schematically shown. An example of information processing in the payment system 100 is schematically shown. An example of a system configuration of a payment system 2100 is schematically shown. An example of the internal configuration of the payment server 2164 is schematically shown. An example of information processing in the payment system 2100 is schematically shown. An example of information processing in the payment system 2100 is schematically shown. An example of information processing in the payment system 2100 is schematically shown. An example of a system configuration of a computer 3000 is schematically shown.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. Furthermore, not all combinations of features described in the embodiments are essential to the solution of the invention. In addition, in the drawings, the same or similar parts may be given the same reference numerals and redundant explanations may be omitted.

[Overview of payment system 100]
An overview of the payment system 100 will be explained using FIGS. 1, 2, 3, and 4. FIG. 1 schematically shows an example of a system configuration of a payment system 100. According to the present embodiment, the details of the payment system 100 will be explained by taking as an example a financial transaction or payment when a user 20 purchases a product 24 at a store 12. In this embodiment, money is deposited in advance into the account of the user 20 opened at the bank 14 by the depositor 40.

The depositor 40 may be the same person as the user 20. In one embodiment, user 20 deposits user's 20 money into user's 20 account. At this time, the user 20 may use the user's 20 name as the depositor 40. In another embodiment, the user 20, acting as the other person's agent, deposits money deposited by the other person, money transferred from the other person, or money advanced for the other person into the user 20 account. At this time, the user 20 may use the above-mentioned other person's name as the depositor 40.

The depositor 40 may be a different person from the user 20. In one embodiment, a person different from user 20 deposits money owned by that person into user 20 account. At this time, the above-mentioned person may use his or her name as the depositor 40. In another embodiment, a person different from the user 20, acting as an agent of another person, transfers money deposited from the other person, money transferred from the other person, or money advanced on behalf of the other person to the user 20 account. Deposit to. The above money transferred from another person may be money transferred to the user 20 under a specific name. At this time, the above-mentioned person may use the above-mentioned other person's name as the depositor 40.

In this embodiment, the store 12 is provided with a sales terminal 122 and a store server 124. In this embodiment, the bank 14 is provided with an ATM 142 and an account management server 144. In this embodiment, a communication terminal 22 is used as a user interface between the user 20 and the payment system 100. Furthermore, a communication terminal 42 is used as a user interface between the depositor 40 and the payment system 100. Each of the communication terminal 22, the communication terminal 42, the store server 124, and the account management server 144 can send and receive information to and from each other via the communication network 10.

In one embodiment, payment system 100 includes an account management server 144. In another embodiment, payment system 100 includes at least one of store server 124 and store server 124 , and account management server 144 . In yet another embodiment, payment system 100 includes communication terminal 22 and account management server 144. In yet another embodiment, the payment system 100 includes a communication terminal 22, a store server 124, at least one of the store server 124, and an account management server 144. In the various embodiments described above, the payment system 100 may further include an ATM 142. In the various embodiments described above, the payment system 100 may further include a communication terminal 42.

In the present embodiment, the payment system 100 manages, for each user, an account for recording at least one of the increase/decrease in property value and the current amount of the user. The property value may be at least one of monetary value, electronic value, and cryptocurrency. Examples of monetary value include currency and coins. Examples of electronic value include points, mileage, and electronic money. Furthermore, depending on the country or period, cryptocurrencies may be treated as monetary value or electronic value.

In one embodiment, the payment system 100 centrally manages at least one of the increase/decrease in property value and the current amount managed in the user's 20 account. In this case, for example, in response to a current balance inquiry from the user 20, the payment system 100 may display the cumulative value of the amount of property value deposited in the user's 20 account based on a deposit request, a transfer request, etc., and a payment request. , a single current amount is output by calculating the difference between the total amount of property value deposited in the user's 20 account based on a withdrawal request, remittance request, withdrawal request, etc.

In another embodiment, the payment system 100 separately manages at least one of an increase/decrease in the property value managed in the user's 20 account and the current amount. Thereby, the payment system 100 can virtually treat a single account as if it were a plurality of accounts. When the current value of the property value to be individually managed becomes 0, the payment system 100 may end the individual management of the property value.

For example, the payment system 100 treats the property value deposited in the account of the user 20 based on a single deposit request as one unit (sometimes referred to as a group), and calculates the property value for each unit. At least one of the increase/decrease and the current amount is individually managed. The property value corresponding to the deposit request specified by the user 20 may be subject to individual management, and the property value corresponding to the deposit request determined by the settings of the payment system 100 may be subject to individual management. It's okay to be. In this case, for example, in response to a current amount inquiry from the user 20, the payment system 100 calculates the current amount for each unit that is subject to individual management, and calculates the current amount for each unit that is individually managed. Output.

For example, the payment system 100 treats the property value deposited in an account based on one or more deposit requests as one unit (sometimes referred to as a group), and increases or decreases the property value for each unit. At least one of the current amount and the current amount is individually managed. One or more deposit requests may be grouped based on the user's 20 designation, or based on the settings of the payment system 100. In this case, as in the above case, for example, the payment system 100 calculates the current amount for each group in response to the current amount inquiry from the user 20, and calculates the current amount for each group, and calculates the current amount for each group. Output the current price.

In this embodiment, when the user 20 uses the individually managed property value, the payment system 100 sends the communication terminal 42 of the depositor 40 who has deposited the individually managed property value to the user 20. , send a message. In this embodiment, the above message includes, for example, information regarding the product or service that the user 20 purchased using the above property value. The information regarding the above product or service may include information indicating at least one of the classification and content of the product or service. Thereby, the depositor 40 can specifically know the use of the property value provided by the depositor 40 to the user 20.

[Overview of each part of the payment system 100]
In this embodiment, the communication network 10 transmits information between at least two of the communication terminal 22, the communication terminal 42, the store server 124, and the account management server 144. The communication network 10 may be a transmission path for wired communication, a transmission path for wireless communication, or a combination of a transmission path for wireless communication and a transmission path for wired communication. Communication network 10 may include a wireless communication network, the Internet, a P2P network, a leased line, a VPN, a power line communication line, and the like. The communication method in the wireless communication network may be a mobile communication method or a wireless data communication method.

Examples of mobile communication systems include communication systems such as 3G system, LTE system, 4G system, and 5G system. Wireless data communication methods include (i) Bluetooth (registered trademark), Zigbee (registered trademark), RFID such as NFC (Near Field Communication), infrared communication, visible light communication, communication using sound waves or ultrasonic waves; Examples include a short-range wireless system, (ii) a wireless LAN system such as WiFi (registered trademark), (iii) a wireless MAN system such as WiMAX (registered trademark), and (iv) a wireless WAN system.

In this embodiment, the communication terminal 22 is an information processing device used by the user 20, and its details are not particularly limited. Examples of the communication terminal 22 include a personal computer, a mobile terminal, and the like. Examples of mobile terminals include mobile phones, smart phones, PDAs, tablets, notebook computers or laptop computers, wearable computers, and the like.

In this embodiment, the communication terminal 22 sends and receives information to and from the sales terminal 122 via near field communication. The communication terminal 22 may acquire the information output by the sales terminal 122 by reading a code displayed on the display device of the sales terminal 122. The communication terminal 22 may acquire the information output by the sales terminal 122 by reading a code output by the printing device of the sales terminal 122. The code output by the printing device may be a code printed on a receipt output by sales terminal 122. The communication terminal 22 may output information to the sales terminal 122 by displaying the code on the display device of the communication terminal 22. The code may be (i) one or a combination of letters, symbols, numbers, and figures, or (ii) may be an encoded code such as a barcode or QR code (registered trademark). .

In this embodiment, the communication terminal 22 sends and receives information to and from the account management server 144 via the communication network 10. The communication terminal 22 may send and receive information to and from at least one of the communication terminal 42 and the store server 124 via the communication network 10. The communication terminal 22 may send and receive information to and from the ATM 142 in the same manner as the information is sent and received between the communication terminal 22 and the sales terminal 122.

In this embodiment, the communication terminal 42 may be an information processing device used by the depositor 40. In this embodiment, the communication terminal 42 may have the same configuration as the communication terminal 22.

In this embodiment, the sales terminal 122 acquires information (sometimes referred to as product information) for specifying a product or service that the user 20 desires to purchase. Sales terminal 122 may output product information to store server 124. For example, the sales terminal 122 acquires product information by reading a code placed on the product 24. The sales terminal 122 may acquire product information by reading identification information recorded on an RFID tag placed on the product 24.

The sales terminal 122 calculates the amount of consideration for the product or service that the user 20 desires to purchase based on one or more product information. Sales terminal 122 presents the calculated amount of consideration to user 20.

In this embodiment, the sales terminal 122 receives information from the user 20 or the communication terminal 22 for specifying an account used for payment of transactions related to the above-mentioned products or services (sometimes referred to as payment account information). ) to obtain. Sales terminal 122 may output payment account information to store server 124. Examples of the payment account information include the account number of the user's 20 account, the card number of the credit card associated with the user's 20 account, and various types of user identification information associated with the user's 20 account.

When the account management server 144 associates an application program installed on the communication terminal 22 of the user 20 with the user's 20 account, for example, the identification information (app ID) may be used as payment account information. In the account management server 144, when the communication terminal 22 of the user 20 and the account of the user 20 are associated, for example, the identification information (sometimes referred to as a terminal ID) of the communication terminal 22 is used for payment processing. It can be used as account information. Examples of the terminal ID include a MAC address, terminal name, computer name, CPU ID, and the like.

The sales terminal 122 may acquire authentication information for authenticating the user 20 from the user 20 or the communication terminal 22. Sales terminal 122 may output authentication information to store server 124. Examples of the authentication information include a password, a passphrase, biometric information, and a terminal ID associated with payment account information. The authentication information may be information about a key used for encryption processing or decryption processing between the account management server 144 and the communication terminal 22.

The sales terminal 122 receives, from the user 20 or the communication terminal 22, the property value used for payment of at least a portion of the consideration presented by the sales terminal 122, out of the property values individually managed in the account management server 144. information (sometimes referred to as a group ID) may be acquired. Sales terminal 122 may output the group ID to store server 124.

The sales terminal 122 may acquire the identification information of the payment means from the user 20 or the communication terminal 22. The sales terminal 122 may obtain the identification information of the payment means from the operator of the sales terminal 122. The sales terminal 122 may output the identification information of the payment means to the store server 124. Examples of payment methods include debit payment, credit payment, virtual currency payment, electronic money payment, and cash payment. Details of sales terminal 122 will be described later.

In this embodiment, the store server 124 acquires various information acquired by the sales terminal 122. Based on the product information acquired by the sales terminal 122, the store server 124 generates information (sometimes referred to as transaction information) used for settling transactions related to the above products or services. The store server 124 generates information (sometimes referred to as content information) indicating at least one of the category and content of the product or service purchased by the user 20 based on the product information, and uses the content information to generate information (sometimes referred to as content information). transaction information may be generated. Details of the transaction information will be described later.

In this embodiment, store server 124 may send transaction information to account management server 144. The store server 124 may transmit the payment account information and group ID to the account management server 144 in association with the transaction information. The store server 124 may transmit the payment account information, authentication information, and group ID to the account management server 144 in association with the transaction information. Details of the store server 124 will be described later.

In this embodiment, the ATM 142 is used by the depositor 40 to deposit money. The ATM 142 may be used by the user 20 to withdraw money. Note that the form of money deposit is not particularly limited. In one embodiment, the depositor 40 uses the ATM 142 to send a request to the account management server 144 to deposit money into the user's 20 account. In another embodiment, the depositor 40 uses the ATM 142 to transmit a request for transfer from the depositor's 40 account to the user's 20 account to the account management server 144 . In yet another embodiment, the depositor 40 uses the communication terminal 42 to transmit a request for transfer from the depositor's 40 account to the user's 20 account to the account management server 144 .

In this embodiment, the account management server 144 manages, for each user 20, an account for recording at least one of an increase/decrease in property value and the current amount of the user. In one embodiment, the account management server 144 centrally manages at least one of the increase/decrease in property value and the current amount managed in the user's 20 account. For example, the account management server 144 manages the history of deposits and withdrawals for each account. The account management server 144 may create and update deposit and withdrawal details for each account.

Here, details of the deposit/withdrawal details of each account will be explained using FIG. 2. FIG. 2 schematically shows an example of the data structure of the deposit/withdrawal details data 200. In this embodiment, the deposit and withdrawal details data 200 includes a deposit and withdrawal ID 212, information 214 indicating the date of deposit and withdrawal, information 216 indicating the deposit amount, information 218 indicating the withdrawal amount, and information 220 indicating the current amount. Information 222 indicating details of deposits and withdrawals and information 224 indicating settings regarding individual management are stored in association with each other.

In this embodiment, the deposit/withdrawal ID 212 is used to identify a deposit-related request (sometimes referred to as a deposit request) or process, or a withdrawal-related request (sometimes referred to as a withdrawal request) or process. This is identification information. Examples of the deposit request include a deposit request and a transfer request. Examples of payout requests include transaction information and various payment requests.

In this embodiment, the information 214 indicating the deposit or withdrawal date indicates the request date or processing date for deposit or withdrawal. The information 214 indicating the deposit/withdrawal date may be information indicating the year, month, day, or may be information indicating the year, month, day, and time.

In this embodiment, the information 216 indicating the deposit amount indicates the amount of property value deposited based on the deposit request. Information 218 indicating the withdrawal amount indicates the amount of property value paid out based on the payout request. Current amount information 220 indicates the current value of the amount of property value managed in the account.

In the present embodiment, the information 222 indicating the details of deposits and withdrawals includes, for example, information indicating the transaction form of financial transactions. Examples of financial transaction types include deposits, transfers, withdrawals, remittances, transfers, withdrawals from ATMs, withdrawals associated with credit transactions, withdrawals associated with debit transactions, and electronic money charging. The above-mentioned financial transaction may be performed within the financial institution's store or outside the financial institution's store. The information 222 indicating the contents of deposits and withdrawals indicates, for example, matters related to deposits or withdrawals. Examples of the above-mentioned related matters include information on the client and information on related financial institutions.

In the present embodiment, the information 224 indicating settings regarding individual management includes, for example, information indicating whether or not it is necessary to individually manage the property value deposited based on a deposit request. Information 224 indicating settings regarding individual management includes information indicating whether or not it is necessary to increase or decrease the value of a specific property that is individually managed based on the payout request. The information 224 indicating settings related to individual management may include identification information (for example, group ID) of a group that is a target of individual management.

In another embodiment, the account management server 144 separately manages at least one of an increase/decrease in the property value managed in the user's 20 account and the current amount. For example, the account management server 144 manages the history of deposits and withdrawals for each group. The account management server 144 may create and update deposit and withdrawal details for each group. The account management server 144 may create and update deposit/withdrawal details for each group based on the deposit/withdrawal details of each account. The account management server 144 may calculate the current balance of each group of each account based on the deposit/withdrawal details of each account.

Here, details of the current price of each group will be explained using FIG. 3. FIG. 3 schematically shows an example of the data structure of current high data 300. In this embodiment, the current value data 300 stores information indicating the current value of property values that are subject to individual management for each group. The current value data 300 may store information indicating the current value of property values that are not subject to individual management. In this embodiment, the current amount data 300 stores a group ID 312, depositor identification information 314, information 316 indicating the name of the deposit, and information 318 indicating the current amount in association with each other.

In this embodiment, the group ID 312 is assigned for the purpose of identifying each group that is subject to individual management. If each group can be identified by the depositor identification information 314 and the deposit name information 316, the group ID 312 may be omitted.

In this embodiment, the depositor identification information 314 indicates information for identifying the depositor 40 who has deposited the property value identified by the group ID 312. The depositor identification information 314 includes (i) information for identifying the depositor 40 in financial transactions with the bank 14 (sometimes referred to as a first client ID), (ii) account management server 144 Information for identifying the depositor 40 (sometimes referred to as a second client ID) is exemplified in the above message sent from the client to the communication terminal 42. Examples of the first client ID include the client's name, name, registered abbreviation, or abbreviation based on predetermined rules. Examples of the second client ID include the client's name, name, abbreviation, or nickname.

If the property value is deposited by an agent, the depositor identification information 314 may be the identification information of the actual depositor, or the identification information of the client who requested the actual depositor to make the deposit. Good too. When the above property value is subject to individual management, it is preferable that the client's identification information is used as the depositor's identification information 314. Thereby, for example, when the above-mentioned property value is subject to individual management, the user 20 can easily identify the provider of the property value. Further, the above-mentioned message is sent to the client's communication terminal.

If the deposited property value is transferred from a first person to a second person under a specific name, the depositor's identification information 314 may be the first person's identification information, and may be the second person's identification information. It may be identification information, or it may be identification information of the actual depositor. When the above-mentioned property value is subject to individual management, it is preferable that the above-mentioned first person's identification information is used as the depositor's identification information 314. Thereby, for example, when the above-mentioned property value is subject to individual management, the user 20 can easily identify the provider of the property value. Further, the above-mentioned message is sent to the communication terminal of the first person.

In this embodiment, the information 316 indicating the name of the deposit is provided for the purpose of making it easier for the user 20 to identify the group. Examples of the information 316 indicating the name of the deposit include the name given to the deposited property value, the reason for depositing the property value, and the use of the deposited property value.

In this embodiment, the information 318 indicating the current value indicates the current value of the total amount of property values classified into each group. Note that the current value of property values that are not subject to individual management is calculated from the current value of all property values managed in the account, for example, to the current value of property values managed individually in each group. Calculated by subtracting the total value of high.

In this embodiment, the account management server 144 acquires transaction information regarding products or services purchased by the user 20 from the store server 124. Further, the account management server 144 acquires payment account information and group ID regarding the transaction of the above product or service from the store server 124. The account management server 144 may obtain payment account information, authentication information, and group ID regarding the transaction of the above-mentioned products or services from the store server 124.

Based on the transaction information and the payment account information, the account management server 144 may reduce the amount of property value managed in the account identified by the payment account information. Based on the transaction information, payment account information, and group ID, the account management server 144 calculates the property value identified by the group ID among the property values managed in the account identified by the payment account information. The amount may be reduced. Before executing the above process, the account management server 144 may execute an authentication process for the user 20 using the payment account information and authentication information.

When the account management server 144 acquires the payment account information and group ID, the account management server 144 notifies a message to the depositor 40 who has deposited the property value identified by the group ID. Specifically, the account management server 144 obtains the communication address of the communication terminal 42 of the depositor 40 in advance, and stores the communication address of the communication terminal 42 and group ID in an arbitrary storage device in association with each other. ing. The communication address of the communication terminal 42 may be included in the deposit request from the depositor 40, may be registered by the user 20, or may be registered by the depositor 40. The account management server 144 generates a message containing information regarding the product or service based on the product information or content information included in the transaction information. The account management server 144 sends the above message to the communication address of the communication terminal 42.

For example, if the payment method for the above transaction is credit card payment, a situation may occur where the account management server 144 has not acquired the transaction information even though the account management server 144 has acquired the payment account information and group ID. . In such a case, the account management server 144 may access an information processing device related to payment to obtain transaction information. Details of the account management server 144 will be described later.

[Overview of payment processing using payment system 100]
FIG. 4 schematically shows an example of information processing in the payment system 100. According to this embodiment, for example, first, the depositor 40 deposits money into the account of the user 20 managed by the account management server 144 of the bank 14 as a birthday present for the user 20 . For example, the depositor 40 uses the ATM 142 to transfer money from the depositor's 40 account to the user's 20 account. The ATM 142 transmits a deposit request to the account management server 144 based on instructions from the depositor 40.

Note that in other embodiments, the depositor 40 may transfer money from the depositor's 40 account to the user's 20 account using the communication terminal 42. In this case, the communication terminal 42 transmits a deposit request to the account management server 144 based on instructions from the depositor 40.

Upon receiving the deposit request, the account management server 144 executes a deposit process and increases the current balance of the user's 20 account based on the deposit request. When the account management server 144 executes the deposit process, the account management server 144 sends a message to the communication terminal 22 of the user 20 indicating that the deposit process has been executed based on the deposit request from the depositor 40. Good too. The above message may be sent to an account management application program installed on the communication terminal 22, or may be sent to a communication address specified in advance by the user 20.

If the deposit request includes not only the first client ID but also the second client ID, the account management server 144 may store the information in association with the group ID. If the deposit request includes information indicating the communication address of the communication terminal 42 of the depositor 40, the account management server 144 may store the information in association with the group ID. If the deposit request includes information indicating the name of the deposited money, the account management server 144 may store the information in association with the group ID.

Next, the user 20 purchases the product 24 at the store 12. For example, before the user 20 executes payment processing for the product 24 at the sales terminal 122, the user 20 uses the communication terminal 22 to request the account management server 144 to inquire about the current amount of his or her account. At this time, the user 20 may request to transmit information indicating the current balance of each group that is individually managed in his/her own account, or may request to transmit information indicating the current balance of a specific group. You may. Upon receiving the above request, the account management server 144 executes the current balance inquiry process and transmits the execution result to the communication terminal 22.

Thereafter, payment processing for the product 24 is executed at the sales terminal 122. Specifically, the operator of the sales terminal 122 uses the sales terminal 122 to read the product information of the product 24 and executes an operation for finalizing the details of the transaction. As a result, the price for the product 24 is displayed on the display device of the sales terminal 122. Additionally, the sales terminal 122 outputs product information about the product 24 to the store server 124.

The user 20 (i) confirms the price of the product 24 displayed on the display device of the sales terminal 122 and the current amount for each group displayed on the display device of the communication terminal 22; Select the group you want to use to pay for. For example, the user 20 operates the communication terminal 22 to select the group to which the money deposited by the depositor 40 in the name of a birthday present for the user 20 belongs, as the group to be used for payment of the product 24.

Note that in other embodiments, the user 20 may select multiple groups as the groups used to pay for the product 24. In this case, the user 20 may specify priorities among multiple groups.

The user 20 operates the communication terminal 22 to send to the sales terminal 122 payment account information for identifying the user's 20 account, authentication information for the account, and the group ID of the group selected by the user 20. present. The sales terminal 122 outputs this information to the store server 124 in association with the product information of the product 24.

In one embodiment, communication terminal 22 transmits the above information to sales terminal 122 using near field communication. In another embodiment, communication terminal 22 outputs a code indicating the above information to a display device of communication terminal 22. The user 20 notifies the sales terminal 122 of the above information by having the sales terminal 122 read the code output to the constant device of the communication terminal 22.

The store server 124 generates transaction information regarding the transaction of the product 24 based on the product information of the product 24 . The store server 124 associates the generated transaction information, payment account information for identifying the account of the user 20, authentication information for the account, and group ID of the group selected by the user 20, and creates an account. The information is sent to the management server 144.

For example, the store server 124 issues identification information (sometimes referred to as a transaction ID) for identifying the transaction for each transaction. The store server 124 generates transaction information by associating the transaction ID related to the transaction of the product 24, the information indicating the time when the transaction was performed, and the product information of the product 24. The store server 124 may generate transaction information using part of the product information, or may process a part of the product information to generate transaction information.

Upon acquiring the transaction information, the account management server 144 executes a payout process and reduces the current amount of the user's 20 account based on the transaction information. The account management server 144 updates the deposit/withdrawal details of the user's 20 account based on the transaction information and the payment account information and group ID associated with the transaction information. The account management server 144 may update the current amount of each group managed in the user's 20 account based on the transaction information and the payment account information and group ID associated with the transaction information.

Thereby, the payment system 100 can virtually treat a single account as if it were a plurality of accounts. As a result, the user 20 can easily use his/her financial assets according to usage or purpose.

In this embodiment, the details of the payment system 100 will be explained using an example in which each account is identified by payment account information, and a group related to the property value managed in each account is identified by group ID. It was done. However, the payment system 100 is not limited to this embodiment. In other embodiments, the group ID may identify both the account and the group described above. In this case, the group ID may be used instead of payment account information.

Further, in the present embodiment, the details of the payment system 100 have been explained by taking as an example a case where payment account information, authentication information, group ID, transaction information, etc. are transmitted from the store server 124 to the account management server 144. However, the payment system 100 is not limited to this embodiment.

In other embodiments, at least one of this information is transmitted from the store server 124 to the account management server 144 via a server managed or operated by a payment service provider, such as a credit card company or payment processing company. You can. In yet other embodiments, at least one of this information may be sent from store server 124 to account management server 144 via communication terminal 22 .

[Specific configuration of each part of the payment system 100]
Each part of the payment system 100 may be realized by hardware, software, or a combination of hardware and software. When at least some of the components of the payment system 100 are realized by software, the components realized by the software can run programs that specify operations regarding the components in an information processing device with a general configuration. This may be realized by starting.

The program may be stored on a computer readable medium such as a CD-ROM, DVD-ROM, memory, hard disk, etc., or may be stored on a storage device connected to a network. The program may be installed on a computer forming at least a portion of payment system 100 from a computer readable medium or a storage device connected to a network. By executing the program, the computer may function as at least a part of each part of the payment system 100.

A program that causes a computer to function as at least a part of each part of the payment system 100 may include a module that defines the operation of each part of the payment system 100. These programs or modules act on data processing devices, input devices, output devices, storage devices, etc., to cause the computer to function as each part of the payment system 100, or to cause the computer to execute an information processing method in each part of the payment system 100. or

The information processing described in the program functions as a concrete means in which software related to the program and various hardware resources of the payment system 100 cooperate by reading the program into a computer. Then, the above-mentioned specific means realizes calculation or processing of information according to the purpose of use of the computer in this embodiment, thereby constructing the payment system 100 according to the purpose of use.

The above program may be a program for causing a computer to function as at least a part of the payment system 100. The above program may be a program for causing a computer to execute an information processing method in at least a portion of the payment system 100.

The above program may be a program for causing a computer to function as the account management server 144 or a program for causing the computer to execute an information processing method in the account management server 144.

The above information processing method may be an account management method. The above account management method is, for example, a method for managing an account for recording, for each user, at least one of an increase/decrease in property value and the current amount of the user. The account management method described above includes, for example, a deposit information acquisition step of acquiring deposit information indicating that a first amount of property value is deposited in the first user's account. The above account management method includes, for example, a detection step of detecting that the property value deposited in the first user's account is used to pay at least a portion of the price for the goods or services purchased by the first user. has. For example, in the above account management method, when the detection unit detects that the property value deposited in the first user's account is used for payment, the detection unit uses the first user's deposit information for the payment. The method includes an instruction output step for outputting instructions for generating payout information indicating that the property value deposited in the account is to be utilized. In the above account management method, for example, the payout information includes information indicating a client who has requested deposit of property value to be used for payment.

The above information processing method may be an account management method. The above account management method is, for example, a method for managing an account for recording, for each user, at least one of an increase/decrease in property value and the current amount of the user. The account management method described above includes, for example, a deposit information acquisition step of acquiring deposit information indicating that a first amount of property value is deposited in the first user's account. In the above account management method, for example, the property value deposited in the first user's account based on the deposit information is used to pay at least part of the price of the product or service purchased by the first user. The method includes a payout information acquisition stage for obtaining payout information indicating the payout information. In the above account management method, for example, after the payout information is acquired in the payout information acquisition stage, information regarding the goods or services purchased by the first user is sent to the client who has requested the deposit of the first amount of property value. and a message sending step of sending a message containing the message.

The above program is a program for causing a computer to function as a communication terminal 22, a sales terminal 122, or a store server 124, or a program for causing a computer to execute an information processing method in a communication terminal 22, a sales terminal 122, or a store server 124. It may be a program of The above information processing method includes, for example, accessing the account management server 144 to obtain value specifying information for specifying the property value deposited in the first user's account based on deposit information. It has stages. The above information processing method includes, for example, an account specifying information acquisition step of obtaining account specifying information for specifying the first user's account. The above information processing method includes, for example, a specific information output step in which the value specific information acquired in the value specific information acquisition step and the account specific information acquired in the account specific information acquisition step are correlated and output to the outside. have

User 20 may be an example of a first user. The communication terminal 22 may be an example of an information processing device. The depositor 40 may be an example of a client. The payment system 100 may be an example of an account management device, a payment management system, and an information processing device. Sales terminal 122 may be an example of an information processing device. The store server 124 may be an example of an information processing device. The account management server 144 may be an example of an account management device. The deposit request may be an example of deposit information. Transaction information may be an example of content information, consideration information, and payout information. Product information may be an example of content information and purchase information. Payment account information may be an example of account specific information. The group ID may be an example of value identification information.

FIG. 5 schematically shows an example of the internal configuration of the sales terminal 122. In this embodiment, the sales terminal 122 includes a short-range communication section 512, a code reader 514, a card reader 516, and an operation input section 518. In this embodiment, the sales terminal 122 includes a display section 522 and a receipt output section 524. In this embodiment, the sales terminal 122 includes an input/output control section 532 and a communication control section 534.

In this embodiment, the short-range communication unit 512 transmits and receives information to and from the communication terminal 22 of the user 20 by short-range wireless communication. The short-range communication unit 512 may acquire information stored in an electronic tag attached to the product 24. The electronic tag may be an RFID tag.

In this embodiment, code reader 514 reads the code. For example, the code reader 514 optically reads a code displayed on the display device of the communication terminal 22. The code reader 514 may optically read the code attached to the product 24.

In this embodiment, the card reader 516 reads information stored or recorded on a physical card such as a bank card, credit card, point card, or the like. The information read by the card reader 516 may be a contact method or a non-contact method.

In this embodiment, the operation input unit 518 receives input from the operator of the sales terminal 122. Examples of the operation input unit 518 include various input devices such as a keyboard, pointing device, touch panel, microphone, camera, voice input system, and gesture input system.

In this embodiment, the display unit 522 presents various information to the user 20 or the communication terminal 22. Examples of the display unit 522 include a display, a projector, a Braille output device, and the like. The display unit 522 may include a display device for the operator of the sales terminal 122 and a display device for the customers of the store 12. In this embodiment, the receipt output unit 524 outputs a receipt related to a commercial transaction.

In this embodiment, the input/output control unit 532 controls input/output of the sales terminal 122. In one embodiment, the input/output control unit 532 outputs information acquired by at least one of the short-range communication unit 512, the code reader 514, the card reader 516, and the operation input unit 518 to the store server 124. In another embodiment, the input/output control unit 532 controls the output of information in at least one of the short-range communication unit 512, the display unit 522, and the receipt output unit 524. For example, the input/output control unit 532 acquires information from the store server 124, controls at least one of the short-range communication unit 512, the display unit 522, and the receipt output unit 524, and transmits the information to the user 20 or the communication terminal. Presented on 22nd.

In this embodiment, the communication control unit 534 controls communication between the sales terminal 122 and equipment external to the sales terminal 122. Examples of external devices include the communication terminal 22 and the store server 124. The communication control unit 534 may be a communication interface. The communication control unit 534 may support one or more communication methods.

FIG. 6 schematically shows an example of the internal configuration of the store server 124. In this embodiment, the store server 124 includes a transaction content acquisition section 612, a transaction ID issuing section 614, and a transaction information generation section 616. In this embodiment, the store server 124 includes a storage section 622, a terminal control section 624, and a communication section 626.

In this embodiment, the transaction details acquisition unit 612 acquires information indicating the details of the transaction of goods or services from the sales terminal 122. Transaction details acquisition section 612 outputs information acquired from sales terminal 122 to transaction information generation section 616.

Examples of the information indicating the content of the transaction include product information of the traded product or service, information indicating the quantity of the product or service, and information regarding the settlement of the transaction. Examples of information related to payment include information indicating a payment method, information for specifying the account of the user 20 used for payment, information for specifying a group used for payment, and the like.

In this embodiment, the transaction ID issuing unit 614 issues a transaction ID every time a transaction of a product or service occurs. Transaction ID issuing section 614 outputs the transaction ID of each transaction to transaction information generating section 616.

In this embodiment, the transaction information generation unit 616 acquires information indicating the details of the transaction from the transaction details acquisition unit 612. The transaction information generation unit 616 acquires the transaction ID of the transaction from the transaction ID issuing unit 614. The transaction information generation unit 616 generates transaction information based on information indicating the details of the transaction and the transaction ID. Note that details of the transaction information will be described later.

In one embodiment, the transaction information generation unit 616 generates transaction information including information regarding the settlement of the transaction, and transmits the transaction information to the account management server 144. In another embodiment, the transaction information generation unit 616 generates transaction information that does not include information regarding the settlement of the above-described transaction, associates the transaction information with information regarding the settlement of the above-described transaction, and sends the transaction information to the account management server. 144. The above transaction information and the above transaction settlement information include, for example, the same transaction ID, and are associated via the transaction ID. With these, (i) settlement account information indicating the account of user 20, (ii) group ID of the group used for settlement of this transaction among the groups managed by user 20's account, and (iii) Information indicating the amount of consideration for the current transaction is transmitted to the account management server 144.

The transaction details acquisition unit 612 may be an example of a purchase information acquisition unit. The transaction information generation section 616 may be an example of a purchase information acquisition section and a specific information output section. Information indicating the details of the transaction may be an example of purchase information.

In this embodiment, the storage unit 622 stores various types of information regarding transactions of products or services. Identification information of a product or service and information indicating details of the product or service are stored in association with each other. Examples of details of the product or service include classification, name, unit price, and the like.

In this embodiment, the terminal control unit 624 controls the operation of the sales terminal 122. In this embodiment, the communication unit 626 transmits and receives information between the store server 124 and devices external to the store server 124. Examples of external devices include the sales terminal 122 and the account management server 144.

FIG. 7 schematically shows an example of the data structure of the data table 700. Each row (sometimes referred to as a record) of data table 700 may be an example of transaction information. In this embodiment, the data table 700 stores a store ID 712, a transaction ID 714, information 716 indicating the date and time of the transaction, and information 718 indicating the content of the transaction in association with each other.

The store ID 712 may be information for identifying the store 12 where the sales terminal 122 is installed. Transaction ID 714 may be identification information given to each transaction by transaction ID issuing unit 614. The information 716 indicating the transaction date and time may be information indicating the transaction time of each transaction. The information 716 indicating the transaction date and time may be information indicating the transaction date. The information 718 indicating the transaction details may be various types of information acquired by the transaction details acquisition unit 612 in relation to each transaction.

FIG. 8 schematically shows an example of the internal configuration of the account management server 144. In this embodiment, the account management server 144 includes a deposit information acquisition section 812, a transaction information acquisition section 814, a deposit/withdrawal management section 816, a communication section 818, and a storage section 820. In this embodiment, the storage section 820 includes a setting information storage section 822 and a history information storage section 824.

In this embodiment, the deposit information acquisition unit 812 acquires deposit information indicating that a first amount of property value is deposited into the user's 20 account. For example, the deposit information acquisition unit 812 acquires a deposit request from the depositor 40. The deposit information acquisition unit 812 may output the deposit information to the deposit/withdrawal management unit 816.

In this embodiment, the transaction information acquisition unit 814 acquires transaction information regarding the product or service purchased by the user 20. For example, the transaction information acquisition unit 814 acquires transaction information regarding the product 24 purchased by the user 20 from the store server 124. As described above, the above transaction information indicates that the property value managed by group in the account of the user 20 is used to pay at least a portion of the consideration for the product 24 purchased by the user 20. The transaction information acquisition unit 814 may output transaction information to the deposit/withdrawal management unit 816.

In this embodiment, the deposit/withdrawal management unit 816 manages deposits/withdrawals for each account. The deposit and withdrawal management unit 816 may manage deposits and withdrawals for each group that is individually managed in each account. The deposit/withdrawal management unit 816 may manage messages sent to the depositor 40 in connection with the user's 20 transaction. Details of the deposit/withdrawal management section 816 will be described later.

In this embodiment, the communication unit 818 transmits and receives information between the account management server 144 and devices external to the account management server 144. Examples of external devices include the communication terminal 22, the communication terminal 42, the store server 124, and the ATM 142. For example, the communication unit 818 transmits a message output by the deposit/withdrawal management unit 816 to the communication terminal 22 based on an instruction from the deposit/withdrawal management unit 816 .

In this embodiment, the storage unit 820 stores various types of information used for account management processing in the account management server 144. The storage unit 820 stores various types of information generated during account management processing in the account management server 144.

In this embodiment, the setting information storage unit 822 stores information indicating various settings related to account management processing in the deposit/withdrawal management unit 816 for each account. Examples of various settings include settings related to individual management, settings related to message notification timing, and settings related to message format or format.

In this embodiment, the history information storage unit 824 stores information indicating the history of deposits and withdrawals for each account. Examples of information indicating the history of deposits and withdrawals include deposit and withdrawal details data 200, current amount data 300, and the like.

The deposit information acquisition unit 812 may be an example of a deposit information acquisition unit. The transaction information acquisition unit 814 may be an example of a payout information acquisition unit. The deposit/withdrawal management unit 816 may be an example of an account management device. The communication unit 818 may be an example of a message transmission unit. The deposit information may be an example of deposit information. Transaction information may be an example of payout information.

FIG. 9 schematically shows an example of the data structure of a data table 900. The data table 900 may be an example of a data structure of a deposit request. In this embodiment, the data table 900 stores a request ID 912, depositor identification information 914, information 916 indicating the deposited amount, and information 918 indicating settings regarding individual management in association with each other.

In this embodiment, the request ID 912 may be information for identifying a deposit request. In this embodiment, the depositor identification information 914 may be information for identifying the requester. The depositor identification information 914 may include a first client ID and a second client ID. In this embodiment, the information 916 indicating the deposit amount indicates the amount of money deposited in response to the deposit request. In this embodiment, the information 918 indicating settings related to individual management includes, for example, information indicating whether individual management is necessary, information indicating the name of money to be deposited, information indicating the communication address of the client, and the like. Examples of the communication address include (i) an email address, (ii) identification information or account of an application program for account management, and (iii) an SNS account.

The data table 900 may be an example of deposit information. The depositor identification information 914 may be an example of client identification information. Information 916 indicating the deposit amount may be an example of deposit amount information. Information 918 indicating settings related to individual management may be an example of client address information.

FIG. 10 schematically shows an example of the internal configuration of the deposit/withdrawal management section 816. In this embodiment, the deposit/withdrawal management section 816 includes a deposit processing section 1012, a payout processing section 1014, and an inquiry processing section 1016. In this embodiment, the deposit/withdrawal management section 816 includes a group setting section 1022 and a message management section 1024. In this embodiment, the deposit/withdrawal management section 816 includes a screen information generation section 1026.

In this embodiment, the deposit processing unit 1012 executes processing for depositing property value into an account (sometimes referred to as deposit processing). For example, the deposit processing unit 1012 acquires a deposit request related to the user's 20 account, and executes a deposit process to deposit the amount of money indicated by the deposit request into the user's 20 account. Thereby, the deposit processing unit 1012 can manage at least one of the increase/decrease in property value and the current amount managed in each account.

In one embodiment, the deposit processing unit 1012 centrally manages at least one of the increase/decrease in property value and the current amount managed in each account. In another embodiment, the deposit processing unit 1012 individually manages at least one of an increase/decrease in the property value and the current amount deposited in each account based on a deposit request. For example, the deposit processing unit 1012 individually manages at least one of the increase/decrease in property value and the current amount managed in each account for each group.

For example, the deposit processing unit 1012 individually manages at least one of an increase/decrease in the property value and the current amount deposited in the user's 20 account based on each of a plurality of deposit requests. For each of one or more groups managed in the user's 20 account, the deposit processing unit 1012 calculates the increase/decrease in the property value deposited in the user's 20 account and the current balance based on requests classified into the group. At least one of these may be managed individually for each group.

For example, when the deposit processing unit 1012 acquires a deposit request shown in the data table 900, the information 918 indicating settings regarding individual management indicates that the money deposited into the account by the deposit request requires individual management. When the information is included, the deposit processing unit 1012 transfers the deposit request to the group setting unit 1022 and acquires the group ID corresponding to the deposit request from the group setting unit 1022. The deposit processing unit 1012 updates the deposit/withdrawal details data 200 using the information indicated by the deposit request and the group ID output by the group setting unit 1022.

In this embodiment, the payout processing unit 1014 executes processing for paying out property value from an account (sometimes referred to as payout processing). For example, the payout processing unit 1014 acquires transaction information related to the user's 20 account, and executes a payout process to pay out the amount of money indicated by the transaction information from the user's 20 account. Thereby, the payout processing unit 1014 can manage at least one of the increase/decrease in property value and the current amount managed in each account.

In one embodiment, the payout processing unit 1014 centrally manages at least one of the increase/decrease in property value and the current amount managed in each account. In another embodiment, the payout processing unit 1014 individually manages at least one of an increase/decrease in the property value deposited in each account based on a deposit request and the current amount. For example, the payout processing unit 1014 individually manages at least one of the increase/decrease in property value and the current amount managed in each account for each group.

For example, the payout processing unit 1014 acquires transaction information and a group ID associated with the transaction information. The payout processing unit 1014 updates the deposit/withdrawal details data 200 using the information indicated by the above transaction information and the above group ID. When the payout processing unit 1014 acquires the transaction information and group ID, the payout processing unit 1014 calculates the value of the product 24 indicated by the transaction information from the current amount of the group indicated by the group ID at the time immediately before the payout processing unit 1014 acquires the transaction information. A new current amount may be calculated by decreasing the amount of consideration.

In the present embodiment, the store server 124 associates transaction information with a group ID and transmits them to the account management server 144. Thereby, the payout processing unit 1014 can acquire the above transaction information and group ID. In another embodiment, the store server 124 transmits transaction information including a specific transaction ID to the account management server 144, and the communication terminal 22 transmits a group ID associated with the transaction ID to the account management server 144. You may. Thereby, the payout processing unit 1014 can acquire the above transaction information and group ID.

In this embodiment, the inquiry processing unit 1016 obtains a request regarding current balance inquiry from a device external to the account management server 144. The inquiry processing unit 1016 outputs information indicating the current balance of the account indicated by the above request as a response to the above request.

In one embodiment, the inquiry processing unit 1016 centrally manages the current amount of all amounts of property value managed in each account. In another embodiment, the inquiry processing unit 1016 separately manages the current amount of property value deposited in each account based on the deposit request. For example, the deposit processing unit 1012 individually manages the current amount of property value managed in each account for each group.

In this embodiment, the group setting unit 1022 manages settings regarding groups in each account. Thereby, the deposit/withdrawal management unit 816 can individually manage the property values deposited in the user's 20 account based on one or more deposit requests as one group.

In one embodiment, the group setting unit 1022 classifies each of the plurality of deposit requests acquired by the deposit information acquisition unit 812 into different groups. In another embodiment, the group setting unit 1022 classifies at least some of the plurality of deposit requests acquired by the deposit information acquisition unit 812 into one or more groups.

The group setting unit 1022 may classify deposit requests based on a prior setting by the user 20, or may classify money requests based on default settings. The above settings may be information indicating conditions for deposit requests classified into each group. The above condition may be a condition that deposit requests from the same client are classified into the same group, or a condition that deposit requests with the same client and name are classified into the same group. You can.

When the deposit information acquisition unit 812 or the deposit processing unit 1012 acquires a deposit request, it may request the group setting unit 1022 for a group ID corresponding to the deposit request. The group setting unit 1022 may analyze the above deposit request, determine the group to which the deposit request belongs, and output the group ID of the group to the deposit information acquisition unit 812 or the deposit processing unit 1012. The group setting unit 1022 may analyze the above deposit request, issue a new group ID, and output the group ID to the deposit information acquisition unit 812 or the deposit processing unit 1012.

In this embodiment, the message management unit 1024 manages messages that are notified to the depositor 40 when the user 20 purchases a product or service. The message management unit 1024 may manage setting information regarding messages. Details of the above setting information will be described later.

For example, the message management unit 1024 manages at least one of message creation, storage, and transmission. The message management unit 1024 may send a reminder regarding message creation to the communication terminal 22 of the user 20. The message management unit 1024 may manage message transmission timing.

For example, after the transaction information acquisition unit 814 acquires transaction information regarding the purchase of the product 24 by the user 20, the message management unit 1024 transmits a message including information regarding the product 24 to the depositor 40. The message management unit 1024 may send a message to the communication address of the depositor 40 included in the deposit request. The message management unit 1024 may send a message that includes at least one of the category and content of the product or service indicated by the transaction information. The above message may be a message registered by the user 20. The message management unit 1024 may use a template selected in advance by the user 20 to generate a message that includes at least one of the category and content of the product or service indicated by the transaction information.

In this embodiment, the screen information generation unit 1026 generates various screens. For example, the screen information generation unit 1026 generates a deposit screen. The screen information generation unit 1026 may generate a screen showing the result of the current amount inquiry. The screen information generation unit 1026 may generate a screen for the user 20 to select a group to be used for payment. Details of these screens will be described later.

The deposit processing unit 1012 may be an example of a deposit information acquisition unit, a unified management unit, and an individual management unit. The payout processing unit 1014 may be an example of an account management device, a detection unit, an instruction output unit, a payout information acquisition unit, a unified management unit, and an individual management unit. The inquiry processing unit 1016 may be an example of a unified management unit and an individual management unit. The group setting section 1022 may be an example of a classification section. The message management unit 1024 may be an example of a message transmission unit. The screen information generation section 1026 may be an example of a deposit screen generation section.

FIG. 11 schematically shows an example of the data structure of the data table 1100. The data table 1100 may be an example of setting information regarding messages. In this embodiment, the data table 1100 stores a group ID 1112, information 1114 indicating the name of the group, and information 1116 indicating settings related to messages in association with each other.

Information 1114 indicating the name of the group is provided for the user 20 to identify the group. The information 1114 indicating the name of the group may include information indicating the name of the person making the deposit request. The information 1114 indicating the name of the group may include information indicating the name of the deposit. Examples of the information 1116 indicating settings related to the message include the communication address of the client, the URI of the message, and information indicating conditions regarding the timing of sending the message.

FIG. 12 schematically shows an example of a screen 1200. Screen 1200 may be an example of a deposit screen used to output a deposit request based on input from a client.

In this embodiment, the screen 1200 includes an input field 1222 that accepts input of the account information of the deposit destination, an input field 1232 that accepts the input of the first client ID, and an input field 1234 that accepts the input of the second client ID. , an input field 1242 that accepts an input of a deposit amount, and an input field 1252 that accepts an input of a deposit name. The screen 1200 includes an input field 1262 that accepts input of information indicating whether or not individual management is desired, an input field 1264 that accepts input of information indicating whether or not message notification is desired, and a message destination. It may also include an input field 1266 that accepts input.

Screen 1200 may be an example of a deposit screen. The input field 1232 may be an example of a client input field. The input field 1234 may be an example of a client input field. The input field 1242 may be an example of a deposit amount input field. Input field 1266 may be an example of an address input field.

FIG. 13 schematically shows an example of a screen 1300. Screen 1300 may be an example of a screen showing current balance inquiry results. In this embodiment, the screen 1300 includes a table 1320 and a table 1330. Screen 1300 may include button 1342 and button 1344.

Table 1320 shows the current amount of money that is subject to individual management, the current amount of money that is not subject to individual management, and the total of both. Table 1330 shows the current amount of each group that is individually managed. The button 1342 may be a button for the user 20 to select that money that is not individually managed will be used in the current transaction. The button 1344 may be a button for the user 20 to select that individually managed money will be used in the current transaction.

When the user 20 clicks the button 1344, for example, the information processing terminal used as the user interface of the user 20 and the payment system 100 sends individually managed money, etc. to pay at least a portion of the price for the product or service. Detects that it is being used. Further, the above-mentioned information processing terminal may, for example, notify the payout processing unit 1014 of the account management server 144 that individually managed money, etc. will be used to pay at least a portion of the consideration for the product or service. The information shown is transmitted.

When the payout processing unit 1014 detects that individually managed money, etc. will be used, the payout processing unit 1014, for example, instructs the screen information generation unit 1026 about the group to be used for settlement in this transaction. Outputs instructions for generating a screen for selection. The screen information generation unit 1026 generates a screen for selecting a group to be used for payment. Further, the screen information generation unit 1026 transmits data used for presenting the above screen to the user 20 to the user 20 and the information processing terminal used as a user interface of the payment system 100. As a result, for example, a screen for selecting a group to be used for settlement in the current transaction is displayed on the display device of the information processing terminal.

As described above, according to the payment system 100 according to the present embodiment, a plurality of virtual accounts can be provided within a single account. According to one embodiment, a single account includes multiple virtual accounts categorized by purpose. According to another embodiment, a single account includes a plurality of virtual accounts classified by deposit requester, remittance requester, or remittance requester.

In addition, according to the payment system 100 according to the present embodiment, for example, when the user 20 purchases a product or service using money managed in the user's 20 account, the user 20 uses the communication terminal 22, proceed with the payment procedure while looking at the screen 1300 output. As described above, the screen 1300 displays information indicating the amount of money, etc. managed in the user's 20 account, as well as information indicating the transfer requester who transferred the money to the user's 20 account.

Therefore, according to the present embodiment, the payment system 100 can make the user 20 aware of the person making the transfer request, for example, when the user 20 pays out money or the like. The payment system 100 can prompt the user 20 to refer to information such as deposit history and transfer history. Note that even if communication between the user 20 and the communication terminal 22 is realized, for example, via a voice recognition system installed in the communication terminal 22, the user 20 It is possible to make the user 20 aware of the person making the transfer, and to prompt the user 20 to refer to information such as deposit history and transfer history.

The information processing terminal used as a user interface for the user 20 and the payment system 100 may be an example of an account management device, a detection unit, and an instruction output unit. The account management server 144 may be an example of an account management device, a detection unit, and an instruction output unit. The payout processing unit 1014 may be an example of an account management device, a detection unit, and an instruction output unit. The communication terminal 22, the sales terminal 122, and the store server 124 may be examples of at least one of an account management device, a detection unit, and an instruction output unit.

FIG. 14 schematically shows an example of a screen 1400. Screen 1400 may be an example of a screen for user 20 to select a group to be used for the current payment. In this embodiment, the screen 1400 includes a table 1420 and an input field 1440 for message-related settings.

In this embodiment, the table 1420 includes, for each group, information 1422 indicating the name of the person making the deposit request, information 1424 indicating the name of the deposit, information 1426 indicating the current amount, and whether or not it can be used in the current transaction. Information 1432 indicating the usage priority and information 1434 indicating the priority order of use are stored in association with each other. In this embodiment, the input field 1440 includes a message input field 1442, a button 1444 embedded with a command to call a file attachment process, and a button 1446 embedded with a command to call a setting process related to a fixed phrase. , a button 1448 embedded with an instruction for executing a process to omit creating a message when purchasing a product or service, and a button 1450 for selecting to make a phone call instead of being notified of a message. That's fine. Note that if a process for omitting message creation is executed at the time of purchasing a product or service, a process for prompting the user 20 to create a message is executed at an appropriate time after the product or service is purchased. It's okay to be.

When the user 20 performs an operation to send the information input on the screen 1400 to the account management server 144, the information processing terminal used as a user interface for the user 20 and the payment system 100 transmits the information input on the screen 1400. The information is sent to the account management server 144. As described above, the information input on the screen 1400 includes information indicating that money, etc. that is classified into a specific group and individually managed will be used to pay at least a portion of the price for the product or service. is included.

According to the present embodiment, for example, the account management server 144 acquires information input on the screen 1400, so that the payout processing unit 1014 of the account management server 144 can pay at least a portion of the price for the product or service. Detects the use of money that is classified into specific groups and managed individually. Further, the payout processing unit 1014 uses the receipt of the information inputted on the screen 1400 as a trigger to pay at least a portion of the consideration for the product or service using money that is classified into a specific group and managed individually. Generate information indicating that etc. will be used.

The payout processing unit 1014 also sends information to the message management unit 1024 indicating that money, etc. that are classified into a specific group and individually managed will be used to pay at least a portion of the consideration for the product or service. Output. As a result, the message management unit 1024 notifies the depositor who deposited the money used to pay at least a portion of the price for the product or service into the account of the user 20 of the message from the user 20. Can be done. The depositor may be an example of a client who requests deposit of money or the like into the account.

According to the present embodiment, the user 20 desires to allocate a portion of the money, etc. that is virtually individually managed for each group in the user's 20 account to at least a portion of the purchase price of a product or service. In this case, the user 20, while looking at the screen displayed on the screen 1400, determines which group the money or the like is to be used. As described above, the screen 1400 displays information indicating the amount of money, etc. classified into each group, and information indicating the transfer requester, etc. who transferred the money, etc. Thereby, the payment system 100 can make the user 20 aware of the transfer requestor, for example, when the user 20 pays out money. Further, the payment system 100 can prompt the user 20 to refer to information such as deposit history and transfer history.

FIG. 15 schematically shows an example of the internal configuration of the communication terminal 22. As shown in FIG. In this embodiment, the communication terminal 22 includes an input section 1512, an output section 1514, a communication section 1516, an account management section 1522, a transaction management section 1524, and a screen generation section 1526.

In this embodiment, the input unit 1512 receives input from the user 20. Examples of the input unit 1512 include various input devices such as a keyboard, pointing device, touch panel, microphone, camera, voice input system, and gesture input system.

In this embodiment, the output unit 1514 outputs information to the outside. Examples of the external device include the user 20 and the sales terminal 122. Examples of the output unit 1514 include various output devices such as a display device, a projection device, an audio output device, and a vibration device. In this embodiment, the communication unit 1516 transmits and receives information between the communication terminal 22 and external equipment. Examples of external devices include the sales terminal 122 and the account management server 144.

In this embodiment, the account management unit 1522 sends and receives information to and from the account management server 144, and executes various processes for managing the account of the user 20. In one embodiment, account management unit 1522 performs processing to determine payment account information between communication terminal 22 and account management server 144.

For example, when an application program for account management installed on the communication terminal 22 is used for the first time, the account management unit 1522 accesses the account management server 144 and performs processing to make the application program usable. (sometimes referred to as activation), processing for completing the initial settings of the application program, processing for registering the communication terminal 22, etc. are executed. The account management server 144 may issue information for the account management server 144 to identify or authenticate the application program installed on the communication terminal 22. The account management server 144 may execute processing for associating the terminal ID of the communication terminal 22 with the user's 20 account. This allows the terminal ID of the communication terminal 22 to be used as payment account information for the user's 20 account.

The account management unit 1522 may store the information issued by the account management server 144 in an appropriate storage device (not shown) as payment account information. Account management section 1522 may output payment account information to transaction management section 1524.

In other embodiments, the account management unit 1522 performs processing to inquire about current balances. For example, when the user 20 inputs into the input unit 1512 an instruction for the account management unit 1522 to execute the current balance inquiry process, the account management unit 1522 accesses the account management server 144 and performs the current balance inquiry process. request execution. The request from the account management unit 1522 to the account management server 144 includes, for example, the payment account information of the user 20, information indicating whether to inquire about the current balance of the entire account, and information for each group managed in the account. and at least one of information indicating whether or not to inquire about the current amount.

The account management server 144 calculates the current balance of the user's 20 account based on a request from the account management unit 1522, and as a response to the request, for example, stores the data necessary for generating the screen 1300 in the account. It is sent to the management section 1522. Note that the account management server 144 may generate the screen 1300 and transmit the data on the screen to the account management section 1522. At this time, the account management server 144 may transmit the above data for generating the screen 1300 or the data of the screen 1300 as well as the group ID of each group to the account management unit 1522. Thereby, the account management unit 1522 can acquire the group ID of one or more groups managed in the user's 20 account at the time of current balance inquiry.

The account management unit 1522 may output data regarding the screen 1300 acquired from the account management server 144 to the screen generation unit 1526. The account management unit 1522 may output a request to the screen generation unit 1526 to cause the output unit 1514 to output the screen 1300. The account management unit 1522 may output the group ID acquired from the account management server 144 to the transaction management unit 1524. The account management unit 1522 may store the information acquired from the account management server 144 in an appropriate storage device (not shown).

In this embodiment, the transaction management unit 1524 sends and receives information to and from the sales terminal 122 or the store server 124, and executes various processes for managing transactions of products or services. For example, the transaction management unit 1524 executes processing for presenting payment account information regarding the user's 20 account to the sales terminal 122. The transaction management unit 1524 may execute processing for presenting the sales terminal 122 with the group ID of the group used for settlement in the current transaction. As a result, information necessary for payment is transmitted to the account management server 144 via the store server 124.

For example, when the user 20 inputs an instruction to select the button 1342 on the screen 1300 into the input section 1512, the transaction management section 1524 presents the payment account information of the user's 20 account to the sales terminal 122. Furthermore, when the user 20 inputs an instruction to select the button 1344 on the screen 1300 into the input section 1512, the transaction management section 1524 causes the screen generation section 1526 to output the screen 1400 on the output section 1514. Outputs the request. When the user 20 inputs an instruction to select a group to be used for payment into the input unit 1512, the transaction management unit 1524 inputs (i) the payment account information of the user 20's account, and (ii) the user 20's The group ID of the selected group is presented to the sales terminal 122.

Note that, as described above, the transaction management section 1524 can acquire the payment account information of the user's 20 account from the account management section 1522, for example. Further, the transaction management unit 1524 can obtain the group ID of each group from the account management server 144 or the group ID via the account management unit 1522, for example.

When the user 20 inputs information indicating the priority order of the group into the input unit 1512, the transaction management unit 1524 may present the information indicating the priority order of the group to the sales terminal 122. Further, the transaction management unit 1524 may present the authentication information of the user's 20 account to the sales terminal 122.

In one embodiment, the transaction management unit 1524 presents the various types of information described above to the sales terminal 122 by short-range wireless communication via the communication unit 1516. In another embodiment, the transaction management unit 1524 generates a code representing the various types of information described above and causes the output unit 1514 to display the code. Thereby, the sales terminal 122 can obtain this information using the code reader 514.

The screen generation unit 1526 generates various screens to be presented to the user 20. The screen generation unit 1526 may display the generated screen on the display device of the output unit 1514. For example, the screen generation unit 1526 generates at least one of the screen 1300 and the screen 1400, and causes the output unit 1514 to display the generated screen. The screen generation unit 1526 may generate the screen 1300 based on a request from the account management unit 1522. The screen generation unit 1526 may generate the screen 1400 based on a request from the transaction management unit 1524. The screen generation unit 1526 may access the account management server 144, obtain information presented to the user 20 by the screen 1300, and generate the screen 1300. The screen generation unit 1526 may access the account management server 144, obtain information presented to the user 20 by the screen 1400, and generate the screen 1400.

The account management unit 1522 may be an example of a value specific information acquisition unit and an account specific information acquisition unit. The transaction management unit 1524 may be an example of a value specific information acquisition unit, an account specific information acquisition unit, and a specific information output unit.

In this embodiment, the details of the payment system 100 will be explained using an example in which the communication terminal 22 is used as a user interface between the user 20 and at least one of the store server 124 and the account management server 144. Ta. However, the payment system 100 is not limited to this embodiment. In other embodiments, sales terminal 122 is utilized in place of communication terminal 22 as a user interface with store server 124 and/or account management server 144. In this case, the terminal control unit 624 of the store server 124 may function as the account management unit 1522, transaction management unit 1524, and screen generation unit 1526, or a portion thereof. Further, the operation input section 518 of the sales terminal 122 may function as the input section 1512, and the display section 522 of the sales terminal 122 may function as the output section 1514.

Further, in the present embodiment, the details of the payment system 100 have been explained using an example in which payment account information, authentication information, group ID, transaction information, etc. are transmitted from the store server 124 to the account management server 144. However, the payment system 100 is not limited to this embodiment. As mentioned above, at least one of these pieces of information may be transmitted from store server 124 to account management server 144 via communication terminal 22 .

In this case, for example, the transaction management unit 1524 associates the transaction ID and the group ID and transmits them to the account management server 144. In another example, the transaction management unit 1524 acquires transaction information generated by the store server 124, associates payment account information, authentication information, group ID, and transaction information, and transmits the transaction information to the account management server 144.

[Overview of information processing in payment system 100]
An example of information processing in the deposit/withdrawal management unit 816 will be explained using FIGS. 16, 17, and 18. FIG. 16 schematically shows an example of deposit processing in the deposit processing unit 1012. According to this embodiment, first, in step 1610 (step may be abbreviated as S), the deposit processing unit 1012 obtains a request for depositing money into the user's 20 account.

Next, in S1620, the deposit processing unit 1012 analyzes the deposit request and determines whether it is necessary to individually manage the money deposited according to the deposit request. If it is determined that individual management is not necessary (No in S1620), the process in S1630 is executed. On the other hand, if it is determined that individual management is necessary (Yes in S1620), the deposit processing unit 1012 outputs the deposit request to the group setting unit 1022 in S1622, and the group setting unit 1022 sends the deposit request to the group setting unit 1022. Receive the group ID corresponding to the group ID. After that, the process of S1630 is executed.

Next, in S1630, the deposit processing unit 1012 updates the deposit/withdrawal details data 200 based on the deposit request. This completes the deposit processing based on the deposit request.

FIG. 17 schematically shows an example of payout processing in the payout processing unit 1014. According to this embodiment, in S1710, the payout processing unit 1014 acquires transaction information regarding the purchase of a product or service by the user 20 from the account management server 144, for example. Further, the payout processing unit 1014 acquires payment account information indicating the account of the user 20 and information regarding the group used for payment from the account management server 144 or the communication terminal 22. Examples of information regarding groups include group IDs, information indicating priorities, and the like.

Next, in S1712, the payout processing unit 1014 settles the price for the product or service purchased by the user 20 based on the transaction information. For example, the payout processing unit 1014 executes processing for transferring money to an account specified by transaction information. Thereafter, in S1720, the payout processing unit 1014 updates the deposit/withdrawal details data 200 based on the transaction information. If the payout processing unit 1014 has received information about the group used for settlement in association with transaction information, the payout processing unit 1014 receives information about the group used for settlement based on the transaction information and the information about the group used for settlement. , the deposit/withdrawal details data 200 may be updated.

Next, in S1730, the payout processing unit 1014 determines whether the current transaction is subject to individual management. For example, if the payout processing unit 1014 has acquired information regarding the group used for payment, the payout processing unit 1014 determines that the current transaction is subject to individual management.

If the current transaction is not subject to individual management (No in S1730), the payout processing unit 1014 ends the payout process. On the other hand, if the current transaction is subject to individual management (Yes in S1730), in S1722, the payout processing unit 1014 requests the message management unit 1024 to manage messages related to the current transaction. For example, the payout processing unit 1014 transmits transaction information and information regarding the group used for payment to the message management unit 1024 along with the above request. Note that transaction information and information regarding groups used for payment may be stored in the storage unit 820.

The message management unit 1024 manages messages based on, for example, the items input by the user 20 into the message-related setting input field 1440 on the screen 1400 presented on the communication terminal 22 or the sales terminal 122. For example, the message management unit 1024 creates a message from the user 20 to the depositor 40 based on the items input in the input field 1440. The message management unit 1024 transmits the created message to the communication terminal 42 of the depositor 40 at an appropriate timing based on the items input in the input field 1440. This completes the payout process.

FIG. 18 schematically shows an example of inquiry processing in the inquiry processing unit 1016. According to the present embodiment, in S1810, the inquiry processing unit 1016 obtains a request regarding a current amount inquiry from the communication terminal 22 of the user 20, for example.

Next, in S1820, the inquiry processing unit 1016 determines whether there is a group that is subject to individual management in the user's 20 account. If there is no group that is subject to individual management in the account of the user 20 (in the case of No in S1820), the inquiry processing unit 1016 uses the latest current amount managed in the deposit/withdrawal details data 200 as the current Obtain as current price. After that, S1830 is executed.

On the other hand, if there is a group that is subject to individual management in the account of the user 20 (in the case of Yes in S1820), in S1822, the inquiry processing unit 1016 aggregates the information for each group based on the deposit/withdrawal details data 200. Execute the process to calculate the current value of each group. After that, S1830 is executed.

In S1830, the inquiry processing unit 1016 transmits information regarding the current balance of the user's 20 account to the communication terminal 22 as a response to the above request. If there is a group that is subject to individual management in the user's 20 account, the inquiry processing unit 1016 may include the group ID of the group in the response to the above request. This completes the current amount inquiry process.

An example of information processing in the payment system 100 will be explained using FIG. 19 and FIG. 20. In this embodiment, an example of a series of information processing in a payment process using the payment system 100 will be described, taking as an example a case where the communication terminal 22 is used as a user interface between the user 20 and the payment system 100. is explained. However, information processing in the payment system 100 is not limited to this embodiment. Note that, as mentioned above, in other embodiments, instead of communication terminal 22, sales terminal 122, for example, may be utilized as a user interface between user 20 and payment system 100.

FIG. 19 shows an example of information processing in the payment system 100, taking as an example a case where the group ID of the group used for payment is transmitted from the communication terminal 22 to the account management server 144 via the store server 124. is shown. FIG. 20 shows an example of information processing in the payment system 100, taking as an example a case where the group ID of the group used for payment is transmitted from the communication terminal 22 to the account management server 144.

According to the embodiment shown in FIG. 19, first, in S1912, the user 20 indicates an intention to purchase the product 24 to the operator of the sales terminal 122 at the store 12. The operator of the sales terminal 122 operates the sales terminal 122 to execute processing for calculating and determining the amount to be billed to the user 20. Thereby, the sales terminal 122 can acquire the product information of the product 24. Further, the information acquired by the sales terminal 122 is transmitted to the store server 124.

When the amount charged to the user 20 is determined, the amount is displayed on the display section 522 of the sales terminal 122. Thereby, the user 20 can grasp the billing amount for the current transaction.

Next, in S1922, the user 20 uses the communication terminal 22 to present the payment account information of the account used for the transaction to the sales terminal 122. If the user 20 wishes to use money that is individually managed in the user's 20 account for a transaction, in S1924 the user 20 uses the communication terminal 22 to request the sales terminal 122 for the transaction. Present the group ID of the group to be used. The method of presenting information from communication terminal 22 to sales terminal 122 is not particularly limited. Thereby, the sales terminal 122 can acquire payment account information and group ID. Further, the information acquired by the sales terminal 122 is transmitted to the store server 124.

Next, in S1932, the store server 124 generates transaction information based on the product information of the product 24 acquired by the sales terminal 122. Store server 124 transmits transaction information to account management server 144. Further, in S1934, the store server 124 transmits the payment account information presented by the user 20 to the account management server 144. Similarly, the store server 124 transmits the group ID presented by the user 20 to the account management server 144.

On the other hand, in S1936, the user 20 uses the communication terminal 22, for example, to create a message to inform the depositor 40 that the product 24 has been purchased. Communication terminal 22 transmits the message created by user 20 to account management server 144 .

Next, in S1942, the account management server 144 executes a payout process regarding the user's 20 account. Further, in S1944, the account management server 144 transmits a message from the user 20 to the depositor 40 to the communication terminal 42 of the depositor 40. Details of the processing in S1942 and S1944 may be as described in relation to FIG. 17. This completes the process.

In the embodiment shown in FIG. 20, S1912, S1922, and S1932 are performed in the same manner as in the embodiment shown in FIG. Note that in S1932, the store server 124 may transmit the transaction information generated in S1932 to the communication terminal 22 via the sales terminal 122.

Next, according to the present embodiment, in S1934, the store server 124 transmits the payment account information presented by the user 20 to the account management server 144. Further, in S2036, the store server 124 presents the transaction ID issued by the transaction ID issuing unit 614 to the user 20 for the current transaction. For example, the store server 124 controls the sales terminal 122 to transmit the transaction ID to the communication terminal 22.

Next, in S2038, the communication terminal 22 associates the transaction ID and group ID and transmits them to the account management server 144. Thereafter, S1936, S1942, and S194 are performed similarly to the embodiment shown in FIG. This completes the process.

[Overview of payment system 2100]
An overview of the payment system 2100 will be explained using FIGS. 21 and 22. FIG. 21 schematically shows an example of a system configuration of a payment system 2100. The payment system 2100 receives at least one of payment account information, group ID, and transaction information from the store server 124 via a payment server 2164 managed or operated by a payment service provider 16 such as a credit card company or payment agency. It differs from the payment system 100 in that it is sent to the account management server 144. Payment system 2100 may have the same configuration as payment system 100 with respect to features other than the above-mentioned differences.

FIG. 22 schematically shows an example of the internal configuration of the payment server 2164. In this embodiment, the payment server 2164 includes a credit processing section 2212, a transaction information acquisition section 2214, a payment processing section 2216, and a transaction information transmission section 2218. The payment server 2164 may be an example of an account management device, a detection unit, and an instruction output unit. The payment processing unit 2216 may be an example of an account management device, a detection unit, and an instruction output unit.

In this embodiment, the credit processing unit 2212 executes credit processing for the user 20. In this embodiment, the transaction information acquisition unit 2214 acquires transaction information from the store server 124. Transaction information acquisition unit 2214 acquires payment account information from store server 124. The transaction information acquisition unit 2214 may acquire the group ID from the store server 124.

In this embodiment, the payment processing unit 2216 executes payment processing based on transaction information. In this embodiment, the transaction information transmitter 2218 transmits transaction information to the account management server 144. Transaction information transmitter 2218 transmits transaction information, and at least one of payment account information and group ID to account management server 144 .

Payment system 2100 may be an example of an account management device, a payment management system, and an information processing device. The store server 124 may be an example of an information processing device. The transaction information acquisition section 2214 may be a purchase information acquisition section and a transaction information transmission section that may be an example of a purchase information acquisition section and a specific information output section.

[Overview of information processing in payment system 2100]
An example of information processing in the payment system 2100 will be explained using FIGS. 23, 24, and 25. In this embodiment, an example of information processing in the payment system 2100 will be described using a case where the user 20 uses credit card payment provided by the payment service provider 16 as an example.

In this embodiment, an example of a series of information processing in a payment process using the payment system 2100 will be described, taking as an example a case where the communication terminal 22 is used as a user interface between the user 20 and the payment system 2100. is explained. However, information processing in payment system 2100 is not limited to this embodiment. Note that, as discussed above, in other embodiments, instead of communication terminal 22, sales terminal 122, for example, may be utilized as the user interface between user 20 and payment system 2100.

The embodiment described with respect to FIG. 23 corresponds to the embodiment described with respect to FIG. The embodiment described with respect to FIG. 24 corresponds to the embodiment described with respect to FIG. In FIG. 25, the information processing in the payment system 2100 is taken as an example where at least one of the account management server 144 and the communication terminal 22 accesses the payment server 2164 and acquires transaction information managed by the payment server 2164. An example is shown.

In the embodiment described with respect to FIG. 23 and the embodiment described with respect to FIG. 24, the user 20 may or may not use a physical card when making a credit card payment. . On the other hand, in the embodiment described with reference to FIG. 25, it is assumed that the user 20 mainly uses a physical card when making credit card payments.

In the embodiment shown in FIG. 23, S1912, S1922, and S1924 are performed in the same manner as in the embodiment shown in FIG. Note that, according to the present embodiment, card information of a credit card used by the user 20 is used as the payment account information of the user 20 in S1922. Examples of card information include identification information of a credit card company, a credit card number, an expiration date of a credit card, and a security code written on a physical credit card.

Next, in S2332, store server 124 generates transaction information and transmits the transaction information to payment server 2164. The payment server 2164 executes payment processing between the payment service provider 16 and the store 12 based on the transaction information. The payment server 2164 also sends transaction information to the account management server 144.

Similarly, in S2334, the store server 124 transmits the payment account information and group ID to the payment server 2164. As described above, the payment server 2164 obtains the card information of the credit card used by the user 20 as the payment account information. Using the credit card number as a key, the payment server 2164 refers to a database in which credit card numbers and bank account numbers are associated, and determines the account of the user 20 associated with the credit card. Extract the account number.

The payment server 2164 transmits the extracted account number of the user's 20 account to the account management server 144 as payment account information. Payment server 2164 may send the group ID to account management server 144. The payment server 2164 may associate transaction information with at least one of an account number and a group ID, and transmit the association to the account management server 144.

Thereafter, S1936, S1942, and S194 are performed similarly to the embodiment shown in FIG. This completes the process.

In the embodiment shown in FIG. 24, S1912 and S1922 are performed in the same manner as in the embodiment shown in FIG. Note that, according to the present embodiment, card information of a credit card used by the user 20 is used as the payment account information of the user 20 in S1922.

Next, S2332 and S2334 are performed in a manner similar to the embodiment described in connection with FIG. 23. Note that, according to the present embodiment, in S2334, the store server 124 does not need to send the group ID to the payment server 2164, and the payment server 2164 does not need to send the group ID to the account management server 144. .

Thereafter, S2036, S2038, S1936, S1942, and S194 are performed in the same manner as in the embodiment shown in FIG. This completes the process.

In the embodiment shown in FIG. 25, S1912, S1922, and S1924 are performed in the same manner as in the embodiment shown in FIG. Note that, according to the present embodiment, card information of a credit card used by the user 20 is used as the payment account information of the user 20 in S1922.

Next, in S2532, store server 124 generates transaction information and transmits the transaction information to payment server 2164. The payment server 2164 executes payment processing between the payment service provider 16 and the store 12 based on the transaction information.

Next, in S2534, the payment server 2164 transmits information indicating that the user 20 used credit card payment to the account management server 144. Payment server 2164 may send information to account management server 144 to identify transactions related to goods or services. Information for identifying a transaction regarding a product or service includes (i) identification information given by the payment server 2164 to the credit card payment corresponding to the transaction, (ii) a transaction ID included in the transaction information of the transaction, Examples include (iii) a credit card number, and (iv) an account number of the user's 20 account.

Generally, in credit card payments, detailed information indicating the details of one or more transactions during a certain period of time is transmitted from the payment server 2164 to the account management server 144 after the period has elapsed. Then, the account management server 144 performs payment between the payment service provider 16 and the user 20 based on the detailed information.

Therefore, the account management server 144 cannot accurately grasp the status of deposits and withdrawals in the user's 20 account until it acquires the above detailed information from the payment server 2164. Therefore, in this embodiment, the payment server 2164 sends information indicating that the user 20 has used credit card payment to the account management server 144 before the above detailed information is notified to the account management server 144. Send to. When the account management server 144 acquires information indicating that the user 20 used credit card payment, it executes the process of S2540.

At S2540, account management server 144 accesses payment server 2164 to obtain transaction information regarding user 20. The account management server 144 may acquire the above transaction information using the information sent from the payment server 2164 for specifying the transaction related to the product or service as a key. At this time, the account management server 144 may acquire at least one of the payment account information and group ID stored in association with each of the one or more pieces of transaction information in the payment server 2164.

As a result, information regarding transactions of the user 20 is shared between the payment server 2164 and the account management server 144. Information regarding user's 20 transactions may be shared between payment server 2164, account management server 144, and communication terminal 22. For example, the account management server 144 transmits at least part of the information acquired from the payment server 2164 to the communication terminal 22.

Thereafter, in S2552, the user 20 uses the communication terminal 22, for example, to create a message to inform the depositor 40 that the product 24 has been purchased. Communication terminal 22 transmits the message created by user 20 to account management server 144 . Further, in S2554, the account management server 144 transmits a message from the user 20 to the depositor 40 to the communication terminal 42 of the depositor 40. Note that the timing at which the message is sent is not limited to this embodiment. In other embodiments, S2554 may be performed after S2654 is performed.

According to this embodiment, in S2562, the payment server 2164 transmits a request regarding payment between the payment service provider 16 and the user 20 to the account management server 144. Then, in S2564, the account management server 144 executes a payout process regarding the user's 20 account based on the above payment request. This completes the process.

In this embodiment, an example of information processing in the payment system 2100 will be described using a case where the payment server 2164 transmits information indicating that the user 20 has used a credit card payment to the account management server 144. It was done. However, information processing in payment system 2100 is not limited to this embodiment. In other embodiments, store server 124 may send information to account management server 144 indicating that user 20 used credit card payment.

Further, in this embodiment, the details of the embodiment shown in FIG. 25 have been explained based on the embodiment shown in FIG. 23. However, information processing in payment system 2100 is not limited to this embodiment. In other embodiments, the processes after S2038 in the embodiment shown in FIG. 24 may be replaced with the processes after S2540 in the embodiment shown in FIG. 25.

FIG. 26 illustrates an example computer 3000 in which aspects of the invention may be implemented, in whole or in part. For example, payment system 100 and a portion thereof are implemented by computer 3000. For example, payment system 2100 and a portion thereof are implemented by computer 3000.

The program installed on the computer 3000 causes the computer 3000 to function as an operation associated with a device according to an embodiment of the present invention or as one or more “parts” of the device, or to perform the operation or the one or more “parts” of the device. and/or the computer 3000 may be caused to perform a process or a step of a process according to an embodiment of the present invention. Such programs may be executed by CPU 3012 to cause computer 3000 to perform certain operations associated with some or all of the blocks in the flowcharts and block diagrams described herein.

A computer 3000 according to this embodiment includes a CPU 3012, a RAM 3014, a graphics controller 3016, and a display device 3018, which are interconnected by a host controller 3010. The computer 3000 also includes input/output units such as a communication interface 3022 , a hard disk drive 3024 , a DVD-ROM drive 3026 , and an IC card drive, which are connected to the host controller 3010 via an input/output controller 3020 . The computer also includes legacy input/output units, such as ROM 3030 and keyboard 3042, which are connected to input/output controller 3020 via input/output chip 3040.

The CPU 3012 operates according to programs stored in the ROM 3030 and RAM 3014, thereby controlling each unit. Graphics controller 3016 obtains image data generated by CPU 3012, such as in a frame buffer provided in RAM 3014 or itself, and causes the image data to be displayed on display device 3018.

Communication interface 3022 communicates with other electronic devices via a network. Hard disk drive 3024 stores programs and data used by CPU 3012 within computer 3000. The DVD-ROM drive 3026 reads programs or data from the DVD-ROM 3001 and provides the programs or data to the hard disk drive 3024 via the RAM 3014. The IC card drive reads programs and data from and/or writes programs and data to the IC card.

ROM 3030 stores therein programs such as a boot program executed by computer 3000 upon activation and/or programs dependent on the computer 3000 hardware. I/O chip 3040 may also connect various I/O units to I/O controller 3020 via parallel ports, serial ports, keyboard ports, mouse ports, etc.

A program is provided by a computer readable storage medium such as a DVD-ROM 3001 or an IC card. The program is read from a computer-readable storage medium, installed on hard disk drive 3024, RAM 3014, or ROM 3030, which are also examples of computer-readable storage medium, and executed by CPU 3012. The information processing described in these programs is read by the computer 3000 and provides coordination between the programs and the various types of hardware resources described above. An apparatus or method may be configured to implement the operation or processing of information according to the use of computer 3000.

For example, when communication is performed between the computer 3000 and an external device, the CPU 3012 executes a communication program loaded into the RAM 3014 and sends communication processing to the communication interface 3022 based on the processing written in the communication program. You can give orders. The communication interface 3022 reads transmission data stored in a transmission buffer area provided in a recording medium such as a RAM 3014, a hard disk drive 3024, a DVD-ROM 3001, or an IC card under the control of the CPU 3012, and transmits the read transmission data. Data is transmitted to the network, or received data received from the network is written to a reception buffer area provided on the recording medium.

Further, the CPU 3012 causes the RAM 3014 to read all or a necessary part of the files or databases stored in external recording media such as the hard disk drive 3024, DVD-ROM drive 3026 (DVD-ROM 3001), and IC card. Various types of processing may be performed on data on RAM 3014. CPU 3012 may then write the processed data back to an external storage medium.

Various types of information, such as various types of programs, data, tables, and databases, may be stored on a recording medium and subjected to information processing. The CPU 3012 performs various types of operations, information processing, conditional determination, conditional branching, unconditional branching, and information retrieval on the data read from the RAM 3014 as described elsewhere in this disclosure and specified by the instruction sequence of the program. Various types of processing may be performed, including /replacement, etc., and the results are written back to RAM 3014. Further, the CPU 3012 may search for information in a file in a recording medium, a database, or the like. For example, when a plurality of entries are stored in a recording medium, each having an attribute value of a first attribute associated with an attribute value of a second attribute, the CPU 3012 selects the first entry from among the plurality of entries. Search for an entry whose attribute value of the attribute matches the specified condition, read the attribute value of the second attribute stored in the entry, and thereby set the attribute value to the first attribute that satisfies the predetermined condition. An attribute value of the associated second attribute may be obtained.

The programs or software modules described above may be stored in a computer-readable storage medium on or near computer 3000. Also, a storage medium such as a hard disk or RAM provided in a server system connected to a dedicated communication network or the Internet can be used as a computer-readable storage medium, thereby allowing the above-mentioned program to be transmitted over the network. Provided to computer 3000.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the range described in the above embodiments. It will be apparent to those skilled in the art that various changes or improvements can be made to the embodiments described above. It is clear from the claims that such modifications or improvements may be included within the technical scope of the present invention.

The order of execution of each process, such as the operation, procedure, step, and stage in the apparatus, system, program, and method shown in the claims, specification, and drawings, is specifically defined as "before" or "before". It should be noted that they can be implemented in any order unless the output of the previous process is used in the subsequent process. Even if the claims, specifications, and operational flows in the drawings are explained using "first," "next," etc. for convenience, it means that it is essential to carry out the operations in this order. It's not a thing.

10 communication network, 12 store, 14 bank, 16 payment service provider, 20 user, 22 communication terminal, 24 product, 40 depositor, 42 communication terminal, 100 payment system, 122 sales terminal, 124 store server, 142 ATM, 144 account management server, 200 deposit/withdrawal details data, 212 deposit/withdrawal ID, 214 information, 216 information, 218 information, 220 information, 222 information, 224 information, 300 current high data, 312 group ID, 314 identification information, 316 information, 318 information, 512 short-range communication section, 514 code reader, 516 card reader, 518 operation input section, 522 display section, 524 receipt output section, 532 input/output control section, 534 communication control section, 612 transaction details acquisition section, 614 transaction ID issuing unit, 616 transaction information generation unit, 622 storage unit, 624 terminal control unit, 626 communication unit, 700 data table, 712 store ID, 714 transaction ID, 716 information, 718 information, 812 deposit information acquisition unit, 814 transaction information acquisition unit, 816 deposit/withdrawal management unit, 818 communication unit, 820 storage unit, 822 setting information storage unit, 824 history information storage unit, 900 data table, 912 request ID, 914 identification information, 916 information, 918 information, 1012 deposit Processing unit, 1014 Payout processing unit, 1016 Inquiry processing unit, 1022 Group setting unit, 1024 Message management unit, 1026 Screen information generation unit, 1100 Data table, 1112 Group ID, 1114 Information, 1116 Information, 1200 Screen, 1222 Input field, 1232 input field, 1234 input field, 1242 input field, 1252 input field, 1262 input field, 1264 input field, 1266 input field, 1300 screen, 1320 table, 1330 table, 1342 button, 1344 button, 1400 screen, 1420 table, 1422 information, 1424 information, 1426 information, 1432 information, 1434 information, 1440 input field, 1442 message input field, 1444 button, 1446 button, 1448 button, 1450 button, 1512 input section, 1514 output section, 1516 communication section, 1522 account management Department, 1524 Transaction Management Department, 1526 Screen Generation Department, 2100 Payment System, 2164 Payment Server, 2212 Credit Processing Department, 2214 Transaction Information Acquisition Department, 2216 Payment Processing Department, 2218 Transaction Information Transmission Department, 3000 Computer, 3001 DVD-ROM, 3010 host controller, 3012 CPU, 3014 RAM, 3016 graphic controller, 3018 display device, 3020 input/output controller, 3022 communication interface, 3024 hard disk drive, 3026 DVD-ROM drive, 3030 ROM, 3040 input/output chip, 3042 keyboard

Claims (12)

An account management device that manages at least one of an increase or decrease in property value deposited in a user's account and the current amount,
executing at least one of a deposit process for depositing a property value into the first user's account and a payout process for paying out the property value from the first user's account, and the property value of the first user's account; a management department that manages at least one of the increase/decrease and the current amount;
Information output by a device that has received a deposit request from a client different from the first user, which is a request for depositing money into the first user's account, wherein a first amount of property is deposited in the first user's account. a deposit information acquisition unit that acquires deposit information indicating that the value of the asset is to be deposited, and outputs the deposit information to the management unit;
Information output by a device used for trading goods or services, which is used to pay at least a portion of the consideration for goods or services purchased by the first user in the first user's account based on the deposit request. a payout information acquisition unit that acquires payout information indicating that the property value of the first amount deposited in is to be used, and outputs the payout information to the management unit;
Equipped with
The management unit executes the deposit process based on the deposit information and/or executes the payout process based on the payout information,
The management department is
An individual managing the property value deposited in the first user's account based on one or more of the deposit requests, at least one of the increase/decrease in the property value and the current amount for each deposit request or for each client. management department and
Prior to the processing of disbursing the consideration for the product or service purchased by the first user, an inquiry screen is generated that shows an inquiry result of the current balance for each deposit request or for each client in the account of the first user. an inquiry screen generation unit to
After the payout information acquisition unit acquires the payout information, the first user requests the client who has requested the deposit of the first amount of property value to deposit the first amount of the property value from the client. a message transmitting unit that transmits a message containing information regarding the product or service purchased using property value;
has
The inquiry screen is configured to allow the first user to select that the property value managed for each deposit request or for each client is used for the payment,
The deposit information is
deposit amount information indicating the first amount;
request identification information for identifying the deposit request or the client;
Client address information indicating the communication address of the client;
is the associated information,
The payout information is
request identification information for identifying the deposit request or the client who requested the deposit of the property value to be used for the payment;
content information indicating at least one of the classification and content of the product or the service;
Consideration information indicating the amount of consideration for the product or the service;
is the associated information,
The request specific information is generated based on input from the first user who viewed the inquiry screen,
The individual management department is
When the deposit information acquisition unit acquires the deposit information, the property for each deposit request or for each client identified by the request identification information included in the deposit information at the time the deposit information is acquired. Calculate the total value of the amount of value,
When the payout information acquisition unit acquires the payout information, the property for each deposit request or for each client specified by the request specifying information included in the payout information at the time the payout information is acquired. calculating a new current amount for each deposit request or each client by reducing the property value of the amount indicated by the consideration information included in the payout information from the current amount of the asset value;
Account management device. The message transmitter includes:
With reference to a database that stores the request specifying information and the deposit request specified by the request specifying information or the request identification information of the client in association with each other, the request associated with the request specifying information is determined. Obtain identification information,
In the deposit information, the message is sent via a communication network to the communication address indicated by the client address information that is associated with the request identification information obtained by referring to the database. ,
The account management device according to claim 1. the message transmitting unit transmits the message including at least one of the category and content of the product or the service indicated by the content information;
The account management device according to claim 1. further comprising a deposit screen generation unit that generates a deposit screen used to output the deposit information based on input from the client,
The deposit screen is
a deposit amount input field for accepting input of the deposit amount information;
a request input field for accepting input of the request identification information;
an address input field for accepting input of the client address information;
including,
The account management device according to claim 1. Prior to the payment processing of the consideration for the product or the service, the first user generates a selection screen for selecting the deposit request or the client corresponding to the property value to be used for the payment. further comprising a selection screen generation unit;
The account management device according to claim 1. The selection screen is configured to allow the first user to create the message.
The account management device according to claim 5. further comprising a central management unit that manages at least one of the increase and decrease of all amounts of property value deposited in the account of the first user and the current amount;
The account management device according to claim 1. An information processing device configured to be able to access the account management device according to claim 1,
a storage device that stores account identification information for identifying the first user's account;
an account specific information acquisition unit that acquires the account specific information from the storage device;
a request specific information acquisition unit that acquires the request specific information that the first user inputs into the first user's communication terminal from the first user's communication terminal or the device that outputs the payout information;
a specific information output unit that outputs the request specific information acquired by the request specific information acquisition unit and the account specific information acquired by the account specific information acquisition unit to the account management device;
An information processing device comprising: further comprising a purchase information acquisition unit that acquires the payout information including purchase information for determining the amount of consideration for the product or the service purchased by the first user from the device that outputs the payout information;
The specific information output unit outputs the request specific information acquired by the request specific information acquisition unit, the account specific information acquired by the account specific information acquisition unit, and the purchase information acquired by the purchase information acquisition unit. outputting the associated information to the account management device;
The information processing device according to claim 8. The account management device according to any one of claims 1 to 7;
The information processing device according to claim 8 or 9;
A payment management system equipped with A program for causing a computer to function as the account management device according to any one of claims 1 to 7. A program for causing a computer to function as the information processing device according to claim 8 or 9.