Settlement server and settlement method

The payment server and method address the inefficiencies in splitting bills by creating shared accounts with predetermined burden ratios and ensuring fair point distribution among users, preventing errors and ensuring each user receives their share.

WO2026234744A1PCT designated stage Publication Date: 2026-11-12NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2025/016757
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing payment systems for splitting bills among multiple users are cumbersome and prone to errors, and methods using shared accounts often result in unfair distribution of point rewards.

Method used

A payment server and method that generate shared accounts linked to multiple user accounts, perform payment processing based on predetermined burden ratios, and distribute points fairly among users after the transaction is complete.

Benefits of technology

Ensures accurate and fair distribution of points and balances among users, preventing unauthorized use and ensuring that each user receives their rightful share of rewards.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025016757_12112026_PF_FP_ABST
    Figure JP2025016757_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a settlement server (100) and a settlement method for performing appropriate point return. An account generation unit (101) generates a shared account that is shared information shared by a plurality of users. A payment processing unit (104) performs a payment process on the basis of the shared account. A point distribution unit (105) distributes points for the payment process to the plurality of users, the points being imparted after the payment process. The account generation unit (101) generates a shared account in accordance with a generation instruction including a user account that is user information indicating a plurality of users who collaboratively bear the burden of payment. According to this configuration, in cases in which payment using the shared account is performed, points imparted for the payment can be distributed to a user who uses the shared account.
Need to check novelty before this filing date? Find Prior Art

Description

Payment Server and Payment Method

[0001] The present invention relates to a payment server and a payment method that perform payment processing.

[0002] In recent years, with the rapid popularization of smartphones, electronic money, and electronic payment services, payment services that use smartphones to pay charges from credit cards or bank accounts have come into widespread use. Along with this, in drinking parties, meals, or trips, "split bill" that was conventionally done by handing over cash is now often carried out by transferring and receiving electronic money that can be used in electronic payment services.

[0003] Patent Document 1 describes that processing related to a first payment is executed by a first terminal of a first user, based on a common account (shared account of the present disclosure) that allows at least a user of the terminal and the first user different from the user of the terminal to make payments, and a first account different from the common account.

[0004] Japanese Unexamined Patent Application Publication No. 2022-59648

[0005] When splitting a bill using existing services, it is common to perform payment operations with the account of an individual (collector), and users need to calculate the amount that other people should pay to the collector, or individually manage information on whether payment has been completed. This method is cumbersome, and errors or omissions in the amount sent or received may occur. To solve this, there is a method using a shared account as described in Patent Document 1, but many electronic payment services offer a certain percentage of "point rewards" for the payment amount, and the method in Patent Document 1 has a problem of unfairness regarding these point rewards.

[0006] Accordingly, the present disclosure aims to provide a payment server and a payment method that perform appropriate point rewards.

[0007] The payment server of the present disclosure includes a generation unit that generates shared information shared by a plurality of users, a payment processing unit that performs payment processing based on the shared information, and a distribution unit that distributes points for the payment processing granted after the payment processing to the plurality of users.

[0008] According to this disclosure, even if one person makes a payment on behalf of multiple people, the points can be distributed.

[0009] Figure 1 is an explanatory diagram showing the bill-splitting method of this disclosure. Figure 2 is a diagram showing a specific example of the account DB 102 stored in the payment server 100. Figure 3 is a diagram showing the balance when a shared account is used. Figure 4 is a diagram showing an overview of the processing when the use of a shared account ends. Figure 5 is a diagram showing a system including the payment server 100 that performs the payment processing of this disclosure. Figure 6 is a block diagram showing the functional configuration of the payment server 100 of this disclosure. Figure 7 is a flowchart showing the processing of the payment server 100 when a shared account is created. Figure 8 is a flowchart showing the process of activating a shared account by depositing electronic money. Figure 9 is a flowchart showing the 2D barcode payment process using a shared account via scan payment. Figure 10 is a flowchart showing the payment process when a 2D barcode is displayed on the user terminal 300. Figure 11 is a flowchart showing the process of stopping a shared account. Figure 12 is a flowchart showing the case when consent is required for the operation to stop a shared account. Figure 13 is a diagram showing an overview of the processing in a modified example. Figure 14 is a diagram showing a shared group DB. Figure 15 is a conceptual diagram showing the payment process. Figure 16 is a diagram showing the functional configuration of the payment server 100a in a modified example. Figure 17 is a flowchart showing the operation of the shared group creation of the payment server 100a. Figure 18 is a flowchart showing the operation of the payment processing of the payment server 100a. Figure 19 is a diagram showing an example of the hardware configuration of the payment server 100 and payment server 100a according to one embodiment of the present disclosure.

[0010] Embodiments of this disclosure will be described with reference to the attached drawings. Where possible, the same parts will be denoted by the same reference numerals, and redundant descriptions will be omitted.

[0011] Figure 1 is an explanatory diagram illustrating the bill-splitting method in this disclosure. In this disclosure, there are user accounts 1 to 3 and a shared account. These user accounts 1 to 3 are accounts for making, for example, 2D barcode payments, and each account contains information indicating the user ID and balance. These user accounts 1 to 3 belong to different users and are generated individually.

[0012] A shared account is a specific account created by one of the users belonging to user accounts 1 through 3. A shared account is linked to user accounts 1 through 3. Therefore, a shared account is created so that any user belonging to user accounts 1 through 3 can use it. Generally, a shared account is linked to at least a shared ID (an ID for sharing), a password, and balance information, and is stored in the payment server described later.

[0013] Users can perform payment operations using a shared account by launching the payment app installed on the user terminal 300 and entering the shared ID and password on its home screen.

[0014] In Figure 1, user account 1 deposits 3,000 yen, and user accounts 2 and 3 deposit 1,500 yen each into the shared account. This is because the contribution ratio for each account is predetermined, and each user processes the payment accordingly.

[0015] Figure 2 shows a specific example of an account database stored in the payment server. As shown in the figure, each user is associated with a specific share of the payment burden. Payments are made from each user account to the shared account according to this burden percentage (e.g., User Account 1 pays 50%, User Account 2 pays 25%, User Account 3 pays 25%).

[0016] In Figure 1, once funds are deposited into the shared account, it becomes available for use. In the figure, 6,000 yen has been deposited into the shared account.

[0017] Figure 3 shows the balance when using a shared account. As shown in the figure, the shared account initially recorded a monetary balance of 6,000 yen, but after using 5,000 yen, the balance was updated to 1,000 yen, and the points balance was updated to 100 points (point redemption rate of 2%). In the following description, the monetary balance will be simply referred to as the balance.

[0018] Figure 4 shows an overview of the process when a shared account is no longer in use. As shown in the figure, once the payment process (splitting the bill) is complete, the shared account is terminated according to the user's instructions. Upon termination, the remaining balance and point balance corresponding to each user account 1 to 3 are sent from the shared account according to their respective share of the cost. After that, the shared account is deactivated. As shown in the figure, after termination, the shared account has a balance of 1000 yen and a point balance of 100 points, and user account 1 receives 500 yen and 50 points according to their respective share of the cost.

[0019] In this way, a shared account is created, and payment processing is carried out using that shared account. This payment processing using the shared account is equivalent to splitting the bill. Then, points and balances, including those earned through the payment processing of the shared account, are refunded to each user account.

[0020] Figure 5 is a diagram showing a system including a payment server 100 that performs payment processing according to this disclosure. As shown in the figure, this system consists of a payment server 100, a store 200, and a user terminal 300. When a user terminal 300 performs a 2D barcode payment process at the store 200, the payment server 100 performs payment processing according to that process. In this disclosure, the user terminal 300 performs payment processing using a shared account. Furthermore, the user terminal 300 is a terminal owned by each user, and each user owns user accounts 1 to 3.

[0021] Figure 6 is a block diagram showing the functional configuration of the payment server 100 of this disclosure. As shown in the figure, the payment server 100 is composed of an account generation unit 101, an account DB 102, an activation unit 103, a payment processing unit 104, and a point distribution unit 105.

[0022] The account generation unit 101 is the part that generates user accounts in response to requests from the user terminal 300. These user accounts include shared accounts. The account generation unit 101 generates a user account with user information such as the user's name, age, and email address set from the user terminal 300, using the user ID assigned to the user at the time of the request. When generating a shared account, the account generation unit 101 assigns a shared ID and, instead of this user information, sets up multiple already generated user accounts linked to the shared ID. In the example shown in Figures 1 to 3, the shared account is linked to user accounts 1 to 3. This linking process is based on a specification by one of the users from user account 1 to user account 3, who is the generator of the shared account.

[0023] The account DB 102 is a database that stores user accounts and shared accounts generated by the account generation unit 101. Specifically, the information shown in Figure 2(a) is stored in the account DB 102.

[0024] The activation unit 103 is responsible for activating the generated shared account. Activating a shared account means enabling payments through the shared account. For example, the activation unit 103 activates the shared account by assigning flag information indicating that it is valid. Activation is performed by at least one of the following: approval by all users or payment.

[0025] The payment processing unit 104 is responsible for processing payments for general user accounts and shared accounts. When the payment processing unit 104 receives a payment request from the user terminal 300, it provides the user terminal 300 with a two-dimensional barcode (for example, QR code®), and the store 200 processes the payment by reading the two-dimensional barcode displayed on the user terminal 300 along with inputting the amount. The payment processing is performed by subtracting an amount specified by the store from the amount indicated by the balance information registered in the user account or shared account stored in the account DB 102.

[0026] The point distribution unit 105 is responsible for awarding predetermined points to the amount processed by the settlement processing unit 104 and distributing them to the multiple user accounts that constitute the shared account. The point distribution unit 105 distributes the points to each user account when the use of the shared account ends or thereafter. In other words, the point distribution unit 105 awards points to the user accounts managed by the settlement server 100, but may also distribute monetary information equivalent to points through cashback or other means. This also includes distributing points according to the settlement amount for settlements made using only user accounts.

[0027] Next, the operation of the payment server 100 configured in this way will be explained. Figure 7 is a flowchart showing the processing of the payment server 100 when a shared account is created. As shown in the figure, this flowchart shows the operation of the payment server 100 and the user terminal 300. The accounts shown as user accounts 1 to 3 in the figure represent the user terminal 300 that logged in with those accounts. Since these user accounts are information managed by the payment server 100, the processing in Figure 7 itself represents the operation of the payment server 100 in terms of processing. The same applies to other flowcharts described later.

[0028] User terminal 300 of user account 1 (hereinafter referred to as user account 1) requests the creation of a shared account in accordance with the user's operation (S101). This creation request specifies, for example, the other user accounts 2 and 3 to be shared, as well as the burden ratio for each account, from user account 1.

[0029] In the payment server 100, when the account generation unit 101 receives a creation request, it creates a shared account (S102). Here, the account generation unit 101 generates a shared ID and processes the process of associating user account 1, as well as other user accounts 2 and 3, with this shared ID.

[0030] The activation unit 103 then sends a participation request (or invitation) specifying the cost-sharing ratio included in the request to the user terminals 300 of user accounts 2 and 3 (S104). This cost-sharing ratio is the proportion that each party will bear when splitting the bill.

[0031] At each user terminal 300 (each user account), the user performs an operation to accept the participation request (S105). The operation of acceptance here is, for example, simply approval.

[0032] When user accounts 2 and 3 approve the shared account (S106), the activation unit 103 activates the shared account (S107). If the user denies the burden sharing ratio, the shared account will not be activated and will not be usable.

[0033] Figure 8 is a modified example, a flowchart showing the process of activating a shared account by depositing electronic money instead of the approval in S106. As shown in the figure, in processes S106 and S106a, when electronic money is deposited into user accounts 1 to 3, the activation unit 103 activates the shared account (S107).

[0034] In process S101, when requesting the creation of a shared account, the user of user account 1 specifies the total amount and the burden ratio, so that other users can understand the amount to be deposited notified by the settlement server 100 in processes S106a and S106b. Note that in Figure 8, user account 1, which created the shared account, may also make the deposit at the time of the request (process S101).

[0035] Figure 9 is a flowchart illustrating the 2D barcode payment process using a shared account. Scan payment is used as an example here.

[0036] At store 200, a 2D barcode is displayed (S201). The user of user terminal 300 (any user from user accounts 1 to 3) logs in with a shared account to use for payment (S202). User terminal 300, logged in with a shared account, then reads the 2D barcode (S203). The user then operates user terminal 300 to enter the amount (S204). User terminal 300 queries the payment server 100 for the balance (S205).

[0037] In the settlement server 100, when the settlement processing unit 104 receives an inquiry about the balance, it refers to the balance of the shared account in the account DB 102 to determine whether payment is possible and then informs the user terminal 300 whether payment is possible (S206).

[0038] Subsequently, the payment server 100 processes the payment to the store 200 (store account) from the balance of the shared account (S207). In addition, the point distribution unit 105 in the payment server 100 grants points to user accounts belonging to the shared account according to the amount paid and the proportion of the burden (S208). Figure 2(b) is a diagram showing the point distribution of the shared account in the account DB. As shown in the figure, points are granted to each user account that constitutes the shared account by the point distribution unit 105.

[0039] Figure 10 is a flowchart of the payment process when a 2D barcode is displayed on the user terminal 300. As shown in the figure, the store 200 has a store terminal that reads a 2D barcode for payment. At the store, a store employee operates the store terminal and enters the amount (S201a). In parallel, the user of the user terminal 300 logs in with a shared account (S202a), and the user terminal 300 displays the 2D barcode for the shared account (S204a).

[0040] The store terminal reads the 2D barcode (S203a). The store terminal inquires about the balance of the shared account from the payment server 100 (S205a). The payment server 100 then sends a payment approval / rejection notification to the store terminal (S206a), the payment processing unit 104 performs the payment processing using the shared account, and the point distribution unit 105 performs the point awarding process (S208).

[0041] Figure 11 is a flowchart showing the process for suspending a shared account. In the diagram, other user accounts are shown as nodes, but in reality, it shows the process for the account DB 102 managed by the payment server 100.

[0042] On the user terminal 300, an operation to disable the shared account is performed (S301). An instruction signal based on the disable operation is sent to the payment server 100.

[0043] In the payment server 100, the activation unit 103 suspends the use of the shared account (S302). For example, the activation unit 103 performs processing such as setting a flag indicating that the shared account is available to 0. The point distribution unit 105 performs distribution processing of the balance and points for each user account stored in the account DB in accordance with the timing of the suspension of use (S303). Here, distribution is performed according to the burden ratio of each user account set in the account DB 102. Note that although processing signals for the user terminal and other user accounts are shown as the distribution of balances and points in the figure, as described above, these indicate processing for the user accounts respectively managed in the account DB 102.

[0044] In the payment server 100, points may be granted with a delay after the use is suspended. In general, when performing payment processing using a two-dimensional barcode, points are granted at a later date on a monthly basis or the like. The degree of delay also varies depending on the type of points or the store where they are used. In the present disclosure, such points granted with a delay can also be appropriately distributed based on notifications from businesses and stores.

[0045] In the payment server 100, the point distribution unit 105 stores, in the account DB 102, points corresponding to the amount previously processed for payment that are granted by a store or other entities (S304). When the point distribution unit 105 determines that the receipt of all delayed points for several payment processes has been completed (S305), the point distribution unit 105 distributes the granted points according to the burden ratio (S306).

[0046] For example, the point distribution unit 105 receives in advance from the business operator / store the notification of points to be granted with a delay and their scheduled grant date in accordance with the system specifications of the payment server 100. The point distribution unit 105 maintains the shared account in a temporary state (unusable) until all the points are granted to the shared account, and when the points are obtained, distributes them to the user accounts according to the burden ratio. The temporary state may be managed by a flag, for example, so that the usable state, unusable state, and temporary state can be distinguished from each other.

[0047] FIG. 12 is a flowchart in a case where consent is required for an invalidation operation of a shared account. Compared with FIG. 11, this figure is different in that processes S301a and S301b are added.

[0048] When an operation for invalidating a shared account is performed from the user terminal 300, and the activation unit 103 receives the operation (S301), the activation unit 103 sends a confirmation notification of the end of use of the shared account to each user account linked to the shared account (S301a). When consent is received from each user account (S301b), the activation unit 103 stops the use of the shared account (S302).

[0049] Note that process S301a is a confirmation notification for the user accounts managed by the payment server 100. Therefore, in terms of information processing, a confirmation flag is assigned to each user account in the payment server 100. When the user of each user account logs in to the payment server 100 using their own user terminal 300, the user can view the confirmation notification based on the confirmation flag. Then, the user can operate the user terminal 300 to perform a consent process for the confirmation notification. When all user accounts have the confirmation flag, the activation unit 103 stops the use of the shared account.

[0050] As shown in FIG. 11 and FIG. 12, respective processes are performed for a case where consent is required for stopping the use of the shared account and a case where consent is not required.

[0051] Next, I will describe a modified version of this disclosure. In this modified version, a shared payment group is created. This is done by inviting and approving members. At this time, a burden ratio may be set for each user. Also, the group does not have to be permanent. For example, a 2D barcode may be scanned immediately before payment, the burden ratio may be set (creating a temporary "group"), and then the payment may be made, and once the payment is completed, the "group" may be dissolved. In other words, it may be a system in which rules are set on who will bear how much, and a payment is made only once according to those rules.

[0052] Members of a shared payment group make payments using the electronic payment service, just as they would with their regular accounts. However, instead of using their individual balances and payment sources, they designate the shared payment group as the payment source. In this case, all group members are billed for an amount proportional to their share of the burden, and a request for approval and the billed amount is sent. To prevent group members from using other members' balances without authorization, approval from all members is required (for each payment) to complete the transaction. If there is no balance or approval is not given, the payment will fail, and no balance or points will be transferred.

[0053] Electronic payment service providers may set different point reward rates for individual balances and shared payment groups. Points earned for payments made using a shared payment group are distributed in proportion to the contribution ratio set for each user account when the group was created.

[0054] Figure 13 shows an overview of the process in a modified example. As shown in Figure 13, a user (user terminal) of user account 1 receives requests (including burden sharing) and approvals from users of user accounts 2 and 3 for the creation of a shared settlement group. The settlement server that manages these user accounts stores a shared group DB that associates user accounts 1 through 3 with shared group 1. This shared group is a collection of multiple user accounts.

[0055] Figure 14 shows the shared group database. As shown in the figure, the shared group database stores user accounts 1 to 3 that constitute shared group 1 and their respective workloads.

[0056] Figure 15 is a conceptual diagram illustrating the payment process. This diagram shows that user account 2 (user terminal) makes a payment of 5,000 yen. As shown in the diagram, user account 2's user terminal makes a payment of 2,500 yen to the payment server. This 2,500 yen is based on user account 2's share of the cost. In return, user account 2 receives a refund of 50 points from the payment server.

[0057] The payment server searches for shared groups that include user account 2 and finds shared group 1. It then detects the other user accounts 1 and 3 that are included in shared group 1. The payment server then bills user accounts 1 and 3 according to their respective share of the burden, and upon receiving their approval, it redeems the points.

[0058] Figure 16 shows the functional configuration of the payment server 100a in a modified example. As shown in the figure, the payment server 100a is composed of a shared group management unit 101a, a shared group DB 102a, a payment processing unit 104a, and a point distribution unit 105a.

[0059] The shared group management unit 101a is the part that generates and manages shared groups based on requests from users who have user accounts.

[0060] The shared group DB 102a is the part that stores shared groups generated based on requests. For example, as shown in Figure 14, user accounts 1 through 3 are associated with shared group ID: 1. A burden ratio is also associated with each of these accounts.

[0061] The payment processing unit 104a is the part that processes payments for each user account.

[0062] The point distribution unit 105a is the part that awards points for payment processing and distributes those points.

[0063] Figures 17 and 18 are flowcharts illustrating the operation of the payment server 100a. As shown in the figures, in this modified example, the operation of the payment server 100a includes the payment server 100a and the user accounts 1 to 3 that it manages. In the figures, these are labeled as user accounts 1 to 3, which represent user terminals logged in with each respective user account. These user accounts are also managed by the payment server 100a. Therefore, although Figures 17 and 18 show processing sequences, they actually represent the operation of the payment server 100a.

[0064] As shown in the figure, in the payment server 100a, the shared group management unit 101a creates a shared group in response to a request from the user terminal of user account 1 (hereinafter simply referred to as user account 1) (S401). This request includes the other user accounts 2 and 3 that will be included in the shared group, and their respective share of the burden.

[0065] In addition, user account 1 sends invitations (including burden sharing) to user accounts 2 and 3 to join the shared group. User accounts 2 and 3 accept the invitation (S402). For example, an invitation is sent to user accounts 2 and 3 with a notification message indicating the invitation, and the users of user accounts 2 and 3 see the notification message and take action to accept the invitation. In the diagram, user account 1 sends invitations to user accounts 2 and 3, but in terms of information processing, the invitation process is performed from user account 1 to user accounts 2 and 3 via the settlement server 100a.

[0066] When a user accepts the invitation, user accounts 2 and 3 send an approval message to the payment server 100a (S403).

[0067] In the settlement server 100a, the shared group management unit 101a processes the burden ratio to the shared group and stores it in the shared group DB 102a (S404).

[0068] Figure 18 is a flowchart illustrating the process when any user stored in the shared group DB 102a makes a payment using the shared group. As shown in the figure, user account 1 performs the payment process using the shared group. For example, the store's terminal reads the 2D barcode (belonging to the account in the shared group) displayed on user account 1's user terminal to perform the payment process (S501). At the time of reading by the store's terminal, the payment amount is entered by the store.

[0069] In the payment server 100a, the payment processing unit 104a receives a payment processing request (including the payment amount) from the store's terminal (S502). In the payment server 100a, the shared group management unit 101a refers to the shared group DB 102a to confirm the user accounts that make up the shared group (S503).

[0070] Then, in the settlement server 100a, the shared group management unit 101a requests approval for the settlement amount from each user account. First, the settlement server 100a sends an approval request for the settlement amount to user account 1 (S504). Here, the shared group management unit 101a calculates the amount based on the burden ratio managed in the shared group DB 102a and sends an approval request including that amount. User account 1 approves the payment (S505).

[0071] Similarly, the shared group management unit 101a calculates the amount based on the burden ratio managed in the shared group DB 102a and sends an approval request including that amount to user accounts 2 and 3 (S506). Approval is then performed by user accounts 2 and 3 (S507).

[0072] In the settlement server 100a, once approval is obtained from all user accounts indicated in the shared group by the shared group management unit 101a, the settlement processing unit 104a performs settlement processing for each user account (S508, S509). Here, the settlement processing unit 104a uses each managed user account to perform settlement processing for the amount calculated based on the burden ratio.

[0073] Then, the point distribution unit 105a calculates the points for each amount processed in the settlement and performs the point distribution process (S510, S511).

[0074] The settlement process using the shared group will be carried out according to the above procedure. In this disclosure, anyone who is a member (not just the creator) can perform the settlement operation using the shared group (designating the shared group as the payer). The settlement requires the approval of all members to be completed. Points will then be distributed according to the amount determined by the burden ratio.

[0075] Next, the effects of the settlement server 100 of this disclosure and the modified settlement server 100a will be described. Unless otherwise specified, the operation of the settlement server 100a is the same as that of the settlement server 100.

[0076] In the settlement server 100 of this disclosure, the account generation unit 101 generates a shared account, which is shared information shared by multiple users. The settlement processing unit 104 then performs settlement processing based on the shared account. The point distribution unit 105 distributes the points awarded for the settlement processing to the multiple users after the settlement processing.

[0077] The account generation unit 101 generates a shared account in accordance with a generation instruction that includes a user account, which is user information indicating multiple users who jointly bear the cost of payment.

[0078] This configuration allows points awarded for payments made using a shared account to be distributed to the users who use that shared account.

[0079] The account generation unit 101 includes an activation unit 103 that activates the shared account when it receives notification of predetermined information from a user (any one of the users) who will be using the shared account. Notification of predetermined information here includes receiving a specified amount of money and receiving a response to an approval request. Activating the shared account involves, for example, a flag indicating activation, which identifies whether the account is active or inactive. For example, if the flag is 0, the account is inactive.

[0080] This prevents unauthorized use of shared accounts and allows for proper allocation of points.

[0081] This shared account is associated with a burden-sharing ratio for each user who uses the account. The payment processing unit 104 then performs payment processing based on the burden-sharing ratio.

[0082] For example, a shared account is associated with the financial information deposited and the user's share of the costs for each user using that shared account. The settlement processing unit 104 then performs settlement processing from the financial information based on the share of costs set for each user. In other words, it performs settlement processing by subtracting the settlement amount from the financial information deposited in the shared account.

[0083] The point distribution unit 105 then distributes the points based on the burden ratio associated with the shared account.

[0084] This allows for a fair distribution of points.

[0085] In the payment server 100 of this disclosure, the activation unit 103 functions as an account management unit that receives a request from any user to suspend the use of a shared account. When the activation unit 103 receives a suspension request, the point distribution unit 105 distributes the points obtained through payments using the shared account.

[0086] This configuration allows for proper point distribution by distributing points after the shared account has been deactivated. For example, if points are awarded through the use of a shared account before or after the point distribution process, it becomes difficult to award those points. However, by deactivating the shared account, this problem does not occur.

[0087] Points may not be awarded simultaneously with payment, depending on the circumstances of the business or store. Therefore, the point distribution unit 105 manages points awarded after the suspension of use of the shared account, and once all points have been received, it distributes the points based on the burden ratio. For example, the point distribution unit 105 receives notifications of points to be awarded later and the scheduled award date from the business or store in advance. The point distribution unit 105 maintains the shared account in a temporary state (unusable) until all points have been awarded to the shared account, and once the points are obtained, it distributes them to the user accounts according to the burden ratio.

[0088] The above describes the operation and effects of the settlement server 100 of this disclosure, but in a modified version thereof, multiple user accounts may be managed as a shared group. In the modified version, the settlement processing unit 104a uses the user account information indicated by the shared group, which is shared information, to perform settlement processing for each user. Here, the settlement processing unit 104a performs settlement processing individually for each user account indicated by the shared group according to their respective share of the burden. Then, the point distribution unit 105a distributes points according to the settlement processing.

[0089] Here, payment processing is carried out individually using user accounts, resulting in a fair distribution of points.

[0090] In the modified example, the shared group management unit 101a generates a shared group according to a generation instruction that includes user information indicating multiple users who jointly bear the cost of payment. This shared group associates user accounts for payment with their respective cost-sharing ratios.

[0091] The shared group management unit 101a then functions as an activation unit that activates the shared group when it receives approval for a group invitation from a user (one of the users) who will be using the shared group. This shared group includes the burden ratio for each user who will be using the shared group. The settlement processing unit 104a then performs settlement processing based on the burden ratio.

[0092] The settlement server and method described herein have the following configuration.

[0093] [1] A settlement server comprising: a generation unit that generates shared information shared by multiple users; a settlement processing unit that performs settlement processing based on the shared information; and a distribution unit that distributes points for settlement processing that are awarded after the settlement processing to the multiple users.

[0094] [2] The settlement server according to [1], wherein the generation unit generates the shared information in accordance with a generation instruction that includes user information indicating multiple users who jointly bear the cost of settlement.

[0095] [3] The settlement server according to [1] or [2], wherein the generation unit further comprises an activation unit that activates the shared information when it receives notification of predetermined information from a user who uses the shared information.

[0096] [4] The payment server according to any one of [1] to [3], wherein the shared information includes the burden ratio for each user using the shared information, and the payment processing unit performs payment processing based on the burden ratio.

[0097] [5] The settlement server according to any one of [1] to [4], wherein the shared information includes a shared account and financial information deposited for each user using the shared account and the burden ratio for each user, and the settlement processing unit performs settlement processing from the financial information based on the burden ratio set for each user.

[0098] [6] The settlement server according to [5], further comprising an account management unit that receives a request from any of the users to suspend the use of the shared account, wherein the point distribution unit distributes the points obtained through settlement using the shared account when it receives the suspension request.

[0099] [7] The payment server described in [6], wherein the point distribution unit manages the points to be awarded after the suspension of the shared account, and when all points have been received, distributes the points based on the burden ratio.

[0100] [8] The point distribution unit distributes points based on the burden ratio, the settlement server according to any one of [4] to [7].

[0101] [9] The payment server according to any one of [1] to [4], wherein the shared information indicates a shared group containing account information of multiple users, and the payment processing unit performs payment processing for each user using the account information indicated in the shared group.

[0102]

[10] A method for a payment server comprising: a generation step of generating shared information shared by multiple users; a payment processing step of performing payment processing based on the shared information; and a distribution step of distributing points for the payment processing that are awarded after the payment processing to the multiple users.

[0103] The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one or more devices with software.

[0104] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0105] For example, the settlement server 100 and settlement server 100a in one embodiment of the present disclosure may function as computers that perform the settlement processing method of the present disclosure. Figure 19 is a diagram showing an example of the hardware configuration of the settlement server 100 and settlement server 100a according to one embodiment of the present disclosure. The settlement server 100 and settlement server 100a described above may be physically configured as computer devices including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0106] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of payment server 100 and payment server 100a may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0107] Each function in payment server 100 and payment server 100a is realized by loading predetermined software (programs) onto hardware such as processor 1001 and memory 1002, which causes processor 1001 to perform calculations, control communication by communication device 1004, and control at least one of data reading and writing in memory 1002 and storage 1003.

[0108] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the account generation unit 101, activation unit 103, settlement processing unit 104, point distribution unit 105, etc., described above may be implemented by the processor 1001.

[0109] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the account generation unit 101, the activation unit 103, the settlement processing unit 104, and the point distribution unit 105 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0110] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out the settlement processing method according to one embodiment of the present disclosure.

[0111] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0112] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). The communication device 1004 may be implemented with physically or logically separated transmitting and receiving units.

[0113] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0114] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0115] Furthermore, the payment server 100 and payment server 100a may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0116] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0117] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they do not contradict each other. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0118] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0119] The determination may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0120] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0121] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Accordingly, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0122] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0123] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technologies (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0124] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0125] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0126] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0127] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0128] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0129] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0130] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0131] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0132] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0133] Any reference to elements using designations such as “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0134] Where the terms “include,” “including,” and their variations are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.

[0135] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0136] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0137] 100, 100a...Payment server, 200...Store, 300...User terminal, 101...Account generation unit, 102...Account DB, 103...Activation unit, 104...Payment processing unit, 105...Point distribution unit, 101a...Shared group management unit, 102a...Shared group DB, 104a...Payment processing unit, 105a...Point distribution unit.

Claims

1. A payment server comprising: a generation unit that generates shared information shared by multiple users; a payment processing unit that performs payment processing based on the shared information; and a point distribution unit that distributes points awarded for the payment processing after the payment processing to the multiple users.

2. The settlement server according to claim 1, wherein the generation unit generates the shared information according to a generation instruction that includes user information indicating a plurality of users who jointly bear the cost of settlement.

3. The settlement server according to claim 1, further comprising: an activation unit that activates the shared information when it receives notification of predetermined information from a user who uses the shared information.

4. The payment server according to claim 1, wherein the shared information includes the burden ratio for each user who uses the shared information, and the payment processing unit performs payment processing based on the burden ratio.

5. The settlement server according to claim 1, wherein the shared information includes a shared account, financial information deposited for each user using the shared account, and each user's share of the cost, and the settlement processing unit performs settlement processing from the financial information based on the share of the cost set for each user.

6. The settlement server according to claim 5, further comprising an account management unit that receives a request from any of the users to suspend the use of the shared account, wherein the point distribution unit, upon receiving the suspension request, distributes the points obtained through settlement using the shared account.

7. The payment server according to claim 6, wherein the point distribution unit manages the points to be awarded after the suspension of the shared account, and when all points have been received, distributes the points based on the burden ratio.

8. The payment server according to claim 4, wherein the point distribution unit distributes points based on the burden ratio.

9. The payment server according to claim 1, wherein the shared information indicates a shared group containing account information of multiple users, and the payment processing unit performs payment processing for each user using the account information indicated in the shared group.

10. A payment method for a payment server comprising: a generation step of generating shared information shared by multiple users; a payment processing step of performing payment processing based on the shared information; and a distribution step of distributing points for the payment processing that are awarded after the payment processing to the multiple users.