JP2024132329A - Information processing device, information processing method, and information processing program - Google Patents

Abstract

[Problem] To flexibly accommodate a user's payment method. [Solution] The information processing device according to the present application has a reception unit, a provision unit, and a determination unit. The provision unit provides a history of payments made by the payer via a payment application that provides a predetermined payment service via a terminal device. The reception unit receives a history selected by the payer from the payment history and a designation of an additional payer. The determination unit determines a remittance amount to be remitted from the designated additional payer to the payer, based on the history selected by the payer. The provision unit provides the additional payer with remittance information to have the payer remit the remittance. [Selected Figure] Figure 1

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

Conventionally, there are known technologies that provide services to assist users in making payments and transferring money. One example of such a technology is a technology that, when a user pays a bill on an even split basis, identifies a customer table that is the subject of payment processing from among customer tables scattered around a store, and determines the payment amount for that customer table and the individual payment amounts for each user seated at that customer table.

JP 2019-133712 A

However, the above conventional technology may not be able to flexibly accommodate users' payment methods.

For example, when multiple customers split the bill at a restaurant or the like, one customer may pay for everyone at the time of payment and collect the fees from the other customers at a later date, i.e., the customer pays in advance. The above-mentioned conventional technology cannot handle this type of payment in advance.

The present application has been made in consideration of the above, and aims to provide an information processing device, an information processing method, and an information processing program that can flexibly accommodate the user's payment method.

The information processing device according to the present application is characterized by having a history providing unit that provides a history of payments made by a payer via a payment application that provides a predetermined payment service via a terminal device, a reception unit that receives a history selected by the payer from the payment history and a designation of an additional payer, a determination unit that determines a remittance amount to be remitted from the designated additional payer to the payer based on the history selected by the payer, and a remittance information providing unit that provides the additional payer with remittance information for allowing the additional payer to remit to the payer.

According to one aspect of the embodiment, it has the effect of being able to flexibly accommodate the user's payment method.

FIG. 1 is a diagram illustrating an example of a bill collection process according to an embodiment. FIG. 2 is a diagram illustrating an example of a screen of a terminal device according to the embodiment. FIG. 3 is a diagram illustrating an example of a screen of a terminal device according to the embodiment. FIG. 4 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. FIG. 5 is a diagram illustrating an example of an account database according to the embodiment. FIG. 6 is a diagram illustrating an example of a user information database according to the embodiment. FIG. 7 is a flowchart illustrating an example of a procedure of a bill collection process according to the embodiment. FIG. 8 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server.

Below, the information processing device, information processing method, and information processing program according to the present application will be described in detail with reference to the drawings. Note that the information processing device, information processing method, and information processing program according to the present application are not limited to these embodiments. In addition, the same components in the following embodiments will be denoted by the same reference numerals, and duplicated descriptions will be omitted.

1. Embodiment
A bill collection process implemented by an information processing device of the present embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the bill collection process according to the embodiment. In Fig. 1, the bill collection process according to the embodiment is implemented by a payment server 10, which is an example of the information processing device according to the present embodiment.

As shown in FIG. 1, the information processing system 1 according to the embodiment includes a payment server 10 and a terminal device 20. The payment server 10 and the terminal device 20 are connected to each other via a network N (e.g., see FIG. 4) so as to be able to communicate with each other by wire or wirelessly. The network N is, for example, a wide area network (WAN) such as the Internet. Note that the information processing system 1 shown in FIG. 1 may include multiple payment servers 10 and multiple terminal devices 20.

The payment server 10 shown in FIG. 1 is an information processing device that executes the collection process according to the embodiment, and is realized by a server device, a cloud system, or the like. For example, the payment server 10 provides an electronic payment service related to electronic payments using a terminal device 20. For example, the payment server 10 manages the accounts of providers of transaction objects and users to whom transaction objects are provided, and realizes various types of payments by transferring electronic money between accounts in accordance with a payment request from a user. Note that electronic money may be, for example, points or currency used independently by various companies, or may be electronically tradable currency provided by a country, such as Japanese yen or dollars.

The terminal device 20 shown in FIG. 1 is an information processing device used by a user. The terminal device 20 is realized, for example, by a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), etc. In addition, the terminal device 20 displays information distributed by the payment server 10 using a web browser or an application.

In the example shown in FIG. 1, the terminal device 20 is a smartphone. In the example shown in FIG. 1, the terminal device 20 is described as terminal device 20-1 to 20-N (N is any natural number) depending on the user who uses the terminal device 20. For example, terminal device 20-1 is the terminal device 20 used by a user (user U1) identified by a user ID "U1". In the following, when there is no particular distinction between the terminal devices 20-1 to 20-N, they will be referred to as terminal device 20.

When the terminal device 20 receives control information for implementing a specified information processing from the payment server 10, the terminal device 20 implements the information processing in accordance with the control information. Here, the control information is described in, for example, a script language such as JavaScript (registered trademark) or a style sheet language such as CSS (Cascading Style Sheets). Note that the specified application itself delivered from the payment server 10 may be regarded as the control information.

1-1. Payment using terminal device 20
Here, an example of payment (electronic payment) using the terminal device 20 will be described prior to the collection process executed by the payment server 10. In the following description, it is assumed that an application for electronic payment using the terminal device 20 (hereinafter, simply referred to as a "payment app"), which is an application distributed from the payment server 10, is installed in the terminal device 20. In addition, in the following description, an example will be described in which a user U1 makes a payment using the terminal device 20-1 using a two-dimensional code (QR code (registered trademark)) arranged in a store and indicating store identification information that identifies the store, but the embodiment is not limited to this. The example of payment described below can also be applied when an arbitrary user makes a payment at an arbitrary store using an arbitrary terminal device 20. In addition, the store identification information may be not only a QR code but also a barcode, a predetermined mark, a number, or the like.

For example, when user U1 makes a payment for the use or purchase of a payment object (transaction object) such as various products or services at a store, user U1 launches a payment app pre-installed on terminal device 20-1. User U1 then photographs the store identification information set up in the store via the payment app. In such a case, terminal device 20-1 displays a screen for inputting the price of the payment object and accepts input of the payment amount from user U1 or a store clerk. Terminal device 20-1 then transmits to payment server 10 the user identification information that identifies user U1, the store identification information (or information indicated by the store identification information, i.e., information indicating the store (e.g., store ID)), and payment information indicating the payment amount.

In such a case, the payment server 10 transfers electronic money in the amount indicated by the payment amount from the account of user U1 indicated by the user identification information to the account of the store indicated by the store identification information. The payment server 10 then sends a notification that the payment has been completed to the terminal device 20-1. In such a case, the terminal device 20-1 notifies that the payment has been made with electronic money by outputting a screen or a specified sound indicating that the payment has been completed.

Note that the payment using the terminal device 20 is not limited to the above-mentioned process. For example, the payment using the terminal device 20 may be made using a store terminal installed in a store. As a specific example, the terminal device 20-1 displays user identification information for identifying the user U1 on a screen. In such a case, the store terminal installed in the store reads the user identification information displayed on the terminal device 20-1 and transmits payment information indicating the user identification information (or information indicated by the user identification information, i.e., information indicating user U1 (e.g., user ID)), the payment amount, and information identifying the store to the payment server 10. In such a case, the payment server 10 transfers electronic money in an amount indicated by the payment amount from the account of user U1 indicated by the user identification information to the store's account, and may notify the store terminal of the store or the terminal device 20-1 that the payment has been completed by outputting a screen or a predetermined sound indicating that the payment has been completed.

Furthermore, payment using the terminal device 20 may not only be a process of transferring electronic money from an account to which user U1 has previously charged electronic money to the store's account, but may also be, for example, a payment using a credit card that user U1 has previously registered. In such a case, for example, the terminal device 20 may transfer electronic money of the payment amount to the store's account and bill the management company of user U1's credit card for the payment amount.

Payment using the terminal device 20-1 may not only be a process of transferring electronic money from the account of user U1 to the account of a store, but may also be, for example, a payment of transferring electronic money from the account of user U1 to the account of another user (i.e., a transfer between users). For example, the terminal device 20-1 used by the sender user U1 reads user identification information identifying the recipient user (for example, user identification information displayed on the terminal device used by the recipient user), accepts input of the amount to be transferred from user U1, and transmits information indicating the read identification information, the amount to be transferred, and the user identification information identifying user U1 to the payment server 10. In such a case, the payment server 10 may transfer electronic money in an amount indicated by the amount to be transferred from the account of user U1 to the account of the recipient user, and notify the user that the transfer has been completed by outputting a screen or a predetermined sound indicating that the transfer has been completed on the terminal device 20-1 or the terminal device used by the recipient user.

Note that remittance using the terminal device 20 is not limited to the above-mentioned process. For example, remittance using the terminal device 20 may be performed by inputting the telephone number of the remittance destination user or information indicating the remittance destination user (e.g., a user ID) into the terminal device 20. As a specific example, the terminal device 20-1 accepts input of the remittance destination user's telephone number or user ID and the remittance amount from user U1, and transmits the input telephone number or user ID, the remittance amount, and user identification information identifying user U1 to the payment server 10. The payment server 10 then transfers electronic money in the amount indicated by the remittance amount from the account of user U1 to the account of the user linked to the transmitted telephone number or user ID.

The telephone number or user ID of the remittance destination user may be linked to information about that user and registered in advance in the payment app. In this case, terminal device 20-1 accepts from user U1 the designation of the user (remittance destination) registered in the payment app and the input of the amount to be remitted to that user, and transmits to payment server 10 the telephone number or user ID linked to the designated user, the remittance amount, and user identification information that identifies user U1.

For example, a remittance using the terminal device 20 may be performed by providing the remittance destination user with link information for receiving the remittance amount. As a specific example, the terminal device 20-1 accepts input of the remittance amount from user U1, generates link information for receiving the remittance amount, and provides the link information to the terminal device used by the remittance destination user by sending an email containing the link information or posting information containing the link information on a social networking service (SNS). Then, when the remittance destination user selects the link information and performs a receiving operation, the settlement server 10 transfers electronic money in the amount indicated by the remittance amount from the account of user U1 to the account of the remittance destination user.

1-2. Overview of the embodiment
The following describes the collection process executed by the payment server 10. The collection process is a process for allowing other users to remit the amount of the fee paid by one user when the fee is paid by multiple users at once. In other words, the collection process is a process for dividing the amount paid by one user among multiple users.

A user who pays the fee in one lump sum is called the payer. In addition, among multiple users who are to pay the fee, one or more users other than the payer are called additional payers.

The payer pays the fee using a payment app. In this case, the payment server 10 transfers electronic money in an amount equivalent to the fee from an account linked to the payer to an account of the store that accepted the payment.

The settlement server 10 executes a collection process to prompt the additional payer to transfer the money to the payer. The additional payer may transfer electronic money to the payer using the above-mentioned user-to-user transfer function, or may settle the fee by another means.

The following describes the payment collection process executed by the payment server 10 with reference to FIG. 1. In the following description, the terminal device 20 may be regarded as the same as the user. In other words, in the following description, user U1 may also be read as terminal device 20-1.

Assume that user U1 is a payer. Users U2, U3, and U4 are users who should have paid the fee paid by user U1 together with user U1. In other words, users U2, U3, and U4 can be additional payers.

After user U1 pays the fee using the payment app, the payment server 10 starts the collection process. The payment server 10 may start the collection process immediately after the fee is paid, may start the collection process a certain time after the fee is paid, or may start the collection process in response to a request from user U1.

First, the payment server 10 provides the terminal device 20-1 with a payment history (step S1). For example, the payment server 10 causes the terminal device 20-1 to display the payment history selection screen C11 shown in FIG. 2. FIG. 2 is a diagram showing an example of a screen of the terminal device according to the embodiment.

As shown in FIG. 2, area AR111 of the payment history selection screen C11 displays the history of payments made by user U1 using the payment app.

For example, AR111 shows that a payment of "16,000 yen" was made at the store "XX Restaurant Shinagawa Branch" on "2023/2/1 13:30." Also, a check box is associated with each payment history. Also, AR111 displays the check box associated with each payment history.

User U1 can select the payment history to be split (allotted) by checking the checkbox. When one or more payment histories are selected and the button B111 labeled "Next" is pressed, the payment server 10 transitions to another screen and causes the terminal device 20-1 to display the amount setting screen C12.

Initially displayed in area AR121 of the amount setting screen C12 is the total amount calculated by adding up the payment amounts of the selected payment history. The total amount may be changed via operation of the terminal device 20-1.

In the example of Figure 2, a payment history with a payment amount of "16,000 yen" and a payment history with a payment amount of "4,000 yen" were selected on the payment history selection screen C11, so the total amount displayed on the amount setting screen C12 is "20,000 yen."

When the total amount is greater than 0 and the button B121 labeled "Next" is pressed, the payment server 10 transitions to another screen and causes the terminal device 20-1 to display the user selection screen C13.

The total amount (20,000 yen in the example in Figure 2) is displayed in area AR131 of the user selection screen C13.

Text is entered into text box TB131 on user selection screen C13. The text entered into text box TB131 is presented to the additional payer. In the example of FIG. 2, the text "Settlement for last week's dinner party" is entered into text box TB131.

Area AR132 of the user selection screen C13 displays users who are candidates for payers and additional payers.

The payment server 10 may use a chat function provided in the payment app to determine the users to be displayed in area AR132. The chat function is a function for sending and receiving text messages with a specified user. The users displayed in AR132 are a list of users who have been pre-registered as recipients of text messages.

AR132 displays users "U2," "U3," and "U4" in addition to "U1," the payer himself. AR132 also displays check boxes associated with each user.

User U1 can select the payer and additional payer by checking the checkboxes. At this time, user U1 may or may not select himself/herself as the payer.

AR132 also displays a weight text box associated with each user. A weight value is entered into the weight text box. The larger the weight value of a user, the larger the remittance amount.

User U1 can select the payer and additional payer by checking the checkboxes. At this time, user U1 may or may not select himself/herself as the payer.

When one or more additional payers are selected and the button B131 labeled "Confirm" is pressed, the terminal device 20-1 notifies the payment server 10 of the contents of the payment history selection screen C11, the amount setting screen C12, and the user selection screen C13, i.e., the payment history, additional payers, and weights to be split (step S2 in Figure 1).

Returning to FIG. 1, the settlement server 10 determines the remittance amount for each additional payer (step S3). As shown in FIG. 2, "U1", "U3", and "U4" are selected on the user selection screen C13. "U1", "U2", "U3", and "U4" correspond to user U1, user U2, user U3, and user U4 in FIG. 1.

The payment server 10 calculates the remittance amount as "total amount x (weight set by user/total weight)".

The settlement server 10 calculates the remittance amount of the user U1 as follows:
The calculation is 20,000 yen x (1/(1 + 2 + 1)) = 5,000 yen.

The settlement server 10 calculates the remittance amount of the user U3 as follows:
The calculation is 20,000 yen x (2/(1 + 2 + 1)) = 10,000 yen.

The settlement server 10 calculates the remittance amount of the user U4 as follows:
The calculation is 20,000 yen x (1/(1 + 2 + 1)) = 5,000 yen.

Because user U2 is not selected, the remittance amount is not calculated. Also, the remittance amount of user U1, who is the payer, is calculated, but user U1 does not actually need to remit.

The payment server 10 associates the calculated remittance amount with the user and displays it in area AR132 of the user selection screen C13.

Then, the payment server 10 notifies each user of the remittance amount (step S4 in FIG. 1). The payment server 10 causes the terminal device 20 of the additional payer to display the billing screen C21 shown in FIG. 3. FIG. 3 is a diagram showing an example of a screen of the terminal device according to the embodiment.

Here, we will use as an example the billing screen C21 displayed on the terminal device 20-3 of user U3. The text entered in the text box TB131 of the screen C13 in FIG. 2 is displayed in the area AR211 of the billing screen C21.

Area AR212 displays the remittance amount, total amount, and members. The remittance amount is the remittance amount for each user calculated by the payment server 10. The members are the users selected on the user selection screen C13. In the example of FIG. 3, area 212 shows that the remittance amount is "10,000 yen" and that the members are users U1, U3, and U4.

Area 213 displays the payment history of the item to be split. The payment history of the item to be split is the payment history selected on the payment history selection screen C11. In the example of FIG. 3, area 213 displays a payment history with a payment amount of "16,000 yen" and a payment history with a payment amount of "4,000 yen."

When the button B211 labeled "Remit" is pressed, the terminal device 20-3 calls up the remittance function. This allows the user U3 to remit money directly after checking the billing screen C21.

[2. Configuration of the payment server]
Next, the configuration of the payment server 10 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the configuration of the payment server according to the embodiment. As shown in Fig. 4, the payment server 10 includes a communication unit 11, a storage unit 12, and a control unit 13.

(Regarding communication unit 11)
The communication unit 11 is realized by, for example, a network interface card (NIC), etc. The communication unit 11 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the terminal device 20 and the like.

(Regarding the storage unit 12)
The storage unit 12 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk, an optical disk, etc. As shown in FIG. 4, the storage unit 12 has an account database 121 and a user information database 122.

(Regarding the account database 121)
The account database 121 stores various information related to the accounts of users of electronic payment services. An example of information stored in the account database 121 will now be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of an account database according to an embodiment. In the example of Fig. 5, the account database 121 has items such as "account ID", "user ID", and "account balance".

"Account ID" indicates identification information for identifying an account. "User ID" indicates identification information for identifying the owner (user) of the account. "Account balance" indicates the balance of the account owned by the user.

In other words, Figure 5 shows an example in which the owner of the account identified by the account ID "AID#1" is the user identified by the user ID "UID#1" and the account balance is "7800."

(Regarding the user information database 122)
The user information database 122 stores various information related to users of electronic payment services. An example of information stored in the user information database 122 will now be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of a user information database according to an embodiment. In the example of Fig. 6, the user information database 122 has items such as "user ID", "payment history", "remittance history", and "attribute information".

"User ID" indicates identification information for identifying a user. "Payment history" indicates the history of payments made using electronic payment services, and stores information such as the payment destination (business operator), payment object (transaction subject), and payment amount. "Remittance history" indicates the history of remittances made to other users using electronic payment services, and stores information such as the remittance destination (user) and remittance amount. "Attribute information" indicates information about the user's attributes, and stores information indicating, for example, demographic attributes and psychographic attributes.

In other words, Figure 6 shows an example in which the payment history of a user identified by user ID "UID#1" is "Payment History #1", the remittance history is "Remittance History #1", and the attribute information is "Attribute Information #1".

(Regarding the control unit 13)
The control unit 13 is a controller, and is realized, for example, by a central processing unit (CPU) or a micro processing unit (MPU) executing various programs stored in a storage device inside the payment server 10 using a RAM as a working area. The control unit 13 is also a controller, and is realized, for example, by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). As shown in FIG. 4, the control unit 13 according to the embodiment has a reception unit 131, a provision unit 132, a determination unit 133, a display control unit 134, and a remittance control unit 135, and realizes or executes the functions and actions of information processing described below.

(Reception Unit 131)
The reception unit 131 receives a history selected by the payer from among the payment histories, and a designation of an additional payer. The reception unit 131 receives the designation of multiple additional payers. The reception unit 131 further receives the weights of the payer and the additional payers. For example, the reception unit 131 receives each piece of information from a payment history selection screen C11, an amount setting screen C12, and a user selection screen C13.

(Providing Unit 132)
The providing unit 132 provides a history of payments made by the payer via a payment application that provides a predetermined payment service via a terminal device. For example, the history provided by the providing unit 132 is displayed on a payment history selection screen C11.

The provision unit 132 provides the additional payer with remittance information to allow the payer to remit the remittance. For example, the remittance information is information displayed on the billing screen C21.

The provision unit 132 functions as a history provision unit and a remittance information provision unit.

(Determination unit 133)
The determination unit 133 determines the remittance amount to be remitted from the designated additional payer to the payer, based on the history selected by the payer. The determination unit 133 determines the remittance amount by allocating the settlement amount shown in the payment history between the payer and the additional payer. The determination unit 133 determines the remittance amount to be remitted from the designated additional payer to the payer, based on the history selected by the payer, such that the larger the weight, the larger the remittance amount. For example, the determination unit 133 calculates the remittance amount as "total amount x (weight set by the user / sum of weights)".

(Display control unit 134)
The display control unit 134 causes each screen to be displayed on the terminal device 20 of the payer or additional payer.

(Remittance Control Unit 135)
The remittance control unit 135 transfers electronic money of the remittance amount from the account linked to the additional payer to the account linked to the payer. For example, the remittance control unit 135 automatically performs remittance when the button B211 is pressed on the billing screen C21. The remittance control unit 135 may also notify an alert when a certain time (e.g., 24 hours) has passed since the billing screen C21 was displayed on the terminal device 20 of the additional payer, and automatically perform remittance when another certain time has passed.

[3. Remittance Processing Flow]
Next, a procedure of a remittance process of the payment server 10 according to the embodiment will be described with reference to Fig. 7. Fig. 7 is a flowchart showing an example of the procedure of a remittance process according to the embodiment.

As shown in FIG. 7, first, the payment server 10 provides the payment history to the payer (step S101). Next, the payment server 10 accepts the payment history, additional payers, and weights to be split (step S102).

Next, the payment server 10 determines the remittance amount for each additional payer (step S103). Next, the payment server 10 notifies the additional payers of the remittance amount (step S104).

4. Modifications
The above-described embodiment is merely an example, and various modifications and applications are possible.

[4-1. If the additional payer does not use the payment app]
If the users selected as additional payers include a user who does not use the payment app, the payment server 10 may notify the user of the billing information by a means other than the payment app. The payment server 10 may send the billing information by email to a pre-registered email address of the user, or may send the billing information as a message by linking with another message service or chat service.

[4-2. Processing mode]
Among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, and conversely, all or part of the processes described as being performed manually can be performed automatically by a known method. In addition, the information including the processing procedures, specific names, various data and parameters shown in the above text and drawings can be changed arbitrarily unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

Furthermore, the above-mentioned embodiments can be combined as appropriate to the extent that the processing content is not contradictory.

5. Effects
As described above, the payment server 10 according to the embodiment includes the reception unit 131, the provision unit 132, and the determination unit 133. The provision unit 132 provides a history of payments made by the payer via a payment application that provides a predetermined payment service via a terminal device. The reception unit 131 receives a history selected by the payer from the payment history and a designation of an additional payer. The determination unit 133 determines a remittance amount to be remitted from the designated additional payer to the payer based on the history selected by the payer. The provision unit 132 provides remittance information to the additional payer for remittance by the payer. This allows the payment server 10 to meet the user's request to split the payment (split the bill) after the payment has been made. As a result, the payment server 10 can flexibly respond to the user's payment method.

The reception unit 131 accepts the designation of multiple additional payers. This allows the payment server 10 to calculate the remittance amount even if there are three or more users who should pay the fee.

The determination unit 133 determines the remittance amount by allocating the settlement amount shown in the payment history between the payer and the additional payer. The reception unit 131 further receives weights for each of the payer and the additional payer. The determination unit 133 determines the remittance amount to be sent from the specified additional payer to the payer based on the history selected by the payer such that the larger the weight, the larger the remittance amount. This allows the settlement server 10 to determine the remittance amount according to the settlement amount. Furthermore, the settlement server 10 can determine the remittance amount with a gradient between users depending on the weight.

The remittance control unit 135 transfers electronic money for the remittance amount from the account linked to the additional payer to the account linked to the payer. This allows the payment server 10 to carry out a consistent process from determining the remittance amount to remittance, improving processing efficiency.

6. Hardware Configuration
The payment server 10 according to each of the above-described embodiments is realized, for example, by a computer 1000 having a configuration as shown in Fig. 8. The payment server 10 will be described below as an example. Fig. 8 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server. The computer 1000 has a CPU 1100, a ROM 1200, a RAM 1300, a HDD 1400, a communication interface (I/F) 1500, an input/output interface (I/F) 1600, and a media interface (I/F) 1700.

The CPU 1100 operates based on a program stored in the ROM 1200 or the HDD 1400, and controls each component. The ROM 1200 stores a boot program executed by the CPU 1100 when the computer 1000 is started, and programs that depend on the hardware of the computer 1000, etc.

HDD 1400 stores programs executed by CPU 1100 and data used by such programs. Communication interface 1500 receives data from other devices via communication network 500 (corresponding to network N in the embodiment) and sends it to CPU 1100, and also transmits data generated by CPU 1100 to other devices via communication network 500.

The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input/output interface 1600. The CPU 1100 acquires data from the input devices via the input/output interface 1600. The CPU 1100 also outputs data generated via the input/output interface 1600 to the output devices.

The media interface 1700 reads a program or data stored in the recording medium 1800 and provides it to the CPU 1100 via the RAM 1300. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1300 via the media interface 1700 and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable Disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

For example, when the computer 1000 functions as the payment server 10, the CPU 1100 of the computer 1000 executes a program loaded onto the RAM 1300 to realize the functions of the control unit 13. In addition, the HDD 1400 stores each piece of data in the storage device of the payment server 10. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, the CPU 1100 of the computer 1000 may obtain these programs from another device via a specified communication network.

[7. Other]
Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the Disclosure of the Invention section.

In addition, the configuration of the payment server 10 described above can be flexibly changed, for example, by calling external platforms, etc. using an API (Application Programming Interface) or network computing, etc., depending on the function.

In addition, the word "unit" in the claims can be read as "means" or "circuit," etc. For example, an acquisition unit can be read as an acquisition means or an acquisition circuit.

REFERENCE SIGNS LIST 10: settlement server 11: communication unit 12: storage unit 13: control unit 121: account database 122: user information database 131: acceptance unit 132: provision unit 133: decision unit 134: display control unit 135: remittance control unit

Claims (7)

a history providing unit that provides a history of payments made by a payer via a payment application that provides a predetermined payment service via a terminal device;
a reception unit for receiving a history selected by a payer from among the payment histories and a designation of an additional payer;
A determination unit that determines a remittance amount to be remitted from a designated additional payer to the payer based on the history of the selection of the payer;
a remittance information providing unit for providing remittance information to the additional payer for allowing the additional payer to remit money;
13. An information processing device comprising: The information processing device according to claim 1, characterized in that the reception unit receives the designation of multiple additional payers. The information processing device according to claim 1 or 2, characterized in that the determination unit determines the remittance amount by allocating the settlement amount shown in the payment history between the payer and the additional payer. The reception unit further receives weights of the payer and the additional payer,
3. The information processing device according to claim 1, wherein the determination unit determines the remittance amount to be remitted from the specified additional payer to the payer based on the history selected by the payer such that the larger the weight, the larger the remittance amount. The information processing device according to claim 1, further comprising a remittance control unit that transfers electronic money of the remittance amount from an account linked to the additional payer to an account linked to the payer. 1. A computer-implemented information processing method, comprising:
a history providing step of providing a history of payments made by a payer via a payment application that provides a predetermined payment service via a terminal device;
a receiving step of receiving a history selected by a payer from the history of payments and a designation of an additional payer;
determining an amount to be transferred from the designated additional payer to the payer based on the history of the payer's selections;
a remittance information providing step of providing remittance information to the additional payer for allowing the additional payer to remit money;
13. An information processing method comprising: a history providing step of providing a history of payments made by a payer via a payment application that provides a predetermined payment service via a terminal device;
a reception step of receiving a history selected by a payer from the history of payments and a designation of an additional payer;
a determination step for determining a remittance amount to be remitted from a designated additional payer to the payer based on the history of the payer's selections;
a remittance information providing step of providing remittance information to the additional payer for allowing the additional payer to remit money;
An information processing program characterized by causing a computer to execute the above.

Images