Settlement system, settlement method, and program

Abstract

To reliably complete settlement using a balance of settlement means.SOLUTION: A determination unit (102) of a settlement system (1) determines the amount of balance to be used in settlement where a balance of settlement means is used. An execution unit (103) makes the settlement on the basis of the use amount. When the balance is used for another settlement during a period from when the use amount is determined until the settlement is made, and the balance is insufficient at the time of making the settlement, the determination unit (102) determines the use amount again. The execution unit (103) makes the settlement on the basis of the determined the use amount again.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a payment system, a payment method, and a program. [Background technology]

[0002] Conventionally, payment services that allow the use of payment means with a balance (for example, points or electronic money) are known. For example, Patent Document 1 describes a credit card payment processing system that allows the use of electronic money for each purchase of a product using only the infrastructure for credit card payments, and converts points earned by using a credit card, etc., into electronic money and applies it to credit card payments. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-189938 Summary of the Invention [Problem to be solved by the invention]

[0004] However, with the technology of Patent Document 1, the remaining points may be used for another payment between the time the user specifies the amount of points to be used for payment and the time the payment is actually made. In this case, the remaining points may be insufficient when the payment is made, which could result in a payment error. This also applies to payment methods other than points. For this reason, there is a need to ensure that payments that use the remaining balance of a payment method are completed.

[0005] One of the objectives of the present disclosure is to ensure that payments that utilize the balance of a payment instrument are completed. [Means for solving the problem]

[0006] The payment system according to the present disclosure includes a determination unit that determines the amount of the balance to be used in a payment in which the balance of a payment means is used, and an execution unit that executes the payment based on the amount of use, and if the balance is used in another payment between the time the amount of use is determined and the time the payment is executed, and the balance is insufficient at the time the payment is executed, the determination unit again determines the amount of use, and the execution unit executes the payment based on the again determined amount of use. [Effects of the Invention]

[0007] According to the present disclosure, payments using the balance of a payment method can be completed reliably. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 2 is a diagram illustrating an example of a hardware configuration of a payment system. [Figure 2] FIG. 10 is a diagram illustrating an example of a confirmation screen. [Figure 3] FIG. 10 is a diagram illustrating an example of a payment flow between two smartphones. [Figure 4] FIG. 1 is a diagram illustrating an example of functions implemented in a payment system. [Figure 5] FIG. 4 is a diagram illustrating an example of a first user database. [Figure 6] FIG. 10 is a diagram illustrating an example of a second user database. [Figure 7] FIG. 10 is a diagram illustrating an example of a point database. [Figure 8] FIG. 10 is a diagram illustrating an example of processing executed in the payment system. [Figure 9] FIG. 10 is a diagram illustrating an example of payments executed in parallel. [Figure 10] FIG. 10 is a diagram illustrating an example of payments executed in parallel. DETAILED DESCRIPTION OF THE INVENTION

[0009] [1. Overall configuration of the payment system] An example of an embodiment of a payment system according to the present disclosure will be described. Fig. 1 is a diagram showing an example of the hardware configuration of a payment system. A payment system 1 is connected to a network N such as the Internet or a LAN. In this embodiment, a service providing system 2, a card company system 3, a point management system 4, and a user terminal 50 are also connected to the network N.

[0010] For example, the payment system 1 includes a payment server 10. The payment server 10 is a server computer of a payment service provider. The payment server 10 includes a control unit 11, a memory unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory unit 12 includes a volatile memory such as RAM and a non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

[0011] The program stored in the storage unit 12 may be supplied to the payment server 10 via the network N. Also, the program stored in a computer-readable information storage medium may be supplied to the payment server 10 via a reading unit (for example, an optical disk drive or a memory card slot) that reads the information storage medium, or an input / output unit (for example, a USB port) that inputs and outputs data to and from an external device.

[0012] Furthermore, the payment system 1 only needs to include at least one computer and is not limited to the example of Figure 1. For example, the payment system 1 may include the payment server 10 and another server computer. The payment system 1 may also include computers other than the server computer, such as a personal computer, a tablet, or a smartphone. The payment system 1 may not include a server computer, but may include only computers other than the server computer.

[0013] For example, the service providing system 2 provides a predetermined service to a user. The service providing server 20 is a server computer of a provider. A provider is a person who provides a service to a user. The service may be of any type, such as a communication service, an e-commerce service, a travel reservation service, a payment service, a financial service, or a video distribution service. For example, the provider may be a company that comprehensively provides multiple services. The service providing server 20 may be a device that unifies multiple services with one member information.

[0014] For example, service providing server 20 includes control unit 21, storage unit 22, and communication unit 23. The physical configurations of control unit 21, storage unit 22, and communication unit 23 may be similar to those of control unit 11, storage unit 12, and communication unit 13, respectively. The program stored in storage unit 22 may be provided to service providing server 20 from network N or an information storage medium. Service providing system 2 is not limited to the example of FIG. 1 as long as it includes at least one computer. These points are similar to those of payment system 1.

[0015] For example, the card company system 3 includes a card company server 30. The card company server 30 is a server computer of the card company. The card company is the company that issued the user's credit card. The card company server 30 includes a control unit 31, a memory unit 32, and a communication unit 33. The physical configurations of the control unit 31, the memory unit 32, and the communication unit 33 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The program stored in the memory unit 32 may be provided to the card company server 30 from the network N or an information storage medium. The card company system 3 is not limited to the example of FIG. 1 as long as it includes at least one computer. These points are similar to those of the payment system 1.

[0016] For example, the point management system 4 includes a point management server 40. The point management server 40 is a server computer of a point management company. The point management company is a company that manages user points. The point management server 40 includes a control unit 41, a memory unit 42, and a communication unit 43. The physical configurations of the control unit 41, the memory unit 42, and the communication unit 43 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. Note that the program stored in the memory unit 42 may be provided to the point management server 40 from the network N or an information storage medium. Furthermore, the point management system 4 only needs to include at least one computer, and is not limited to the example of FIG. 1. These points are similar to those of the payment system 1.

[0017] For example, the user terminal 50 may be a user's personal computer, smartphone, tablet, or wearable terminal. Although only one user terminal 50 is shown in FIG. 1 , there may be a user terminal 50 for each of multiple users. For example, the user terminal 50 includes a control unit 51, a memory unit 52, a communication unit 53, an operation unit 54, and a display unit 55. The physical configurations of the control unit 51, the memory unit 52, the communication unit 53, the operation unit 54, and the display unit 55 may be similar to those of the control unit 11, the memory unit 12, and the communication unit 13, respectively. The operation unit 54 is an input device such as a keyboard, a mouse, or a touch panel. The display unit 55 is a display such as a liquid crystal display or an organic EL display. The program stored in the memory unit 52 may be provided to the user terminal 50 from a network N or an information storage medium.

[0018] [2. Overview of the payment system] In this embodiment, an example is taken of a case where a provider provides a communication service to a user. Furthermore, an example is taken of a payment for a user who has subscribed to two smartphones for the communication service. The user terminal 50 may be either of the two smartphones, or may be a computer separate from the smartphones. The user can pay the communication fees for each of the two smartphones using any payment method supported by the communication service.

[0019] A payment method is a method used for payment. A payment method is also called a payment instrument. A payment method may be of any type, such as a credit card, points, electronic money, debit card, cryptocurrency, account (e.g., bank account or securities account), carrier billing, wallet, or other name. In this embodiment, an example is given in which a user pays communication fees for two smartphones using a credit card and points in combination. For example, when a user operates the user terminal 50 to log in to a communication service, a confirmation screen for confirming the payment method is displayed on the display unit 55.

[0020] FIG. 2 is a diagram showing an example of a confirmation screen. For example, the confirmation screen SC displays the user's contract plan, information about the payment method specified by the user, point usage conditions for point usage, and the payment date. The confirmation screen SC displays one of the payment methods on two smartphones. In this embodiment, an example is given in which the user specifies the same payment method on two smartphones, but the user may specify different payment methods on the two smartphones.

[0021] In the example of Figure 2, the communication fee for the communication service is 2,600 yen. The user has specified that up to 1,000 points can be used to pay the communication fee for the communication service as a point usage condition. If there are insufficient points to cover the communication fee for the communication service, a credit card can be used. For example, the user can select button B1 to change the point usage conditions. The user can change the upper limit of points or whether or not points can be used. The user can select button B2 to specify another payment method.

[0022] In this embodiment, an example is given in which multiple payments for communication services are executed in batch processing at a fixed date and time each month. For example, at the fixed date and time each month, the service providing system 2 sends a single payment file to the payment system 1 to request multiple payments. The payment system 1 executes multiple payments based on the payment file received from the service providing system 2.

[0023] In this embodiment, payment system 1 executes multiple payments in parallel (concurrently) rather than sequentially executing multiple payments one by one. If payment system 1 includes multiple computers, multiple payments are shared among the multiple computers. If payment system 1 includes only one computer, multiple payments may be shared among multiple processors or multiple cores, or one processor or core may execute payments in parallel.

[0024] Figure 3 is a diagram showing an example of the payment flow between two smartphones. Many payments occur in addition to the payment shown in Figure 3. In the example of Figure 3, the user's point balance before the payment begins is 1,700 points. Hereinafter, the point balance will be simply referred to as the point balance. The upper limit amount specified by the user as a point usage condition is assumed to be 1,000 points. Furthermore, as mentioned above, the point usage conditions of each of the two smartphones are assumed to be the same.

[0025] For example, before starting a payment using the first smartphone, the payment system 1 determines the amount of points to be used in the payment using the first smartphone. Hereinafter, the amount of points to be used is simply referred to as the point usage amount. At this point, the point balance is 1,700 points, which is more than the upper limit of 1,000 points specified by the user, so the payment system 1 determines that 1,000 points will be used in the payment using the first smartphone. At this point, the point balance is not yet locked.

[0026] For example, before starting a payment on a first smartphone, the payment system 1 determines the amount of points to be used in a payment on a second smartphone. At this point, the payment on the first smartphone has not yet been executed, so the point balance is 1,700 points. Because the point balance is 1,700 points, which is more than the upper limit of 1,000 points specified by the user, the payment system 1 determines that 1,000 points will be used in the payment on the second smartphone. At this point, the point balance is not yet locked.

[0027] For example, the payment system 1 starts a payment for a first smartphone before starting a payment for a second smartphone. The payment system 1 communicates with the point management system 4 to lock the user's point balance and executes a point payment so that 1,000 yen is paid. The payment system 1 communicates with the card company system 3 and executes a credit card payment so that the remaining 1,600 yen is paid in points.

[0028] For example, when payment is completed on the first smartphone, the point balance is unlocked. The point balance becomes 700 points. Payment system 1 then starts payment on the second smartphone. At this point, the point balance is 700 points, which is less than the predetermined 1000 points. If the payment fails due to an insufficient point balance, it will cause inconvenience to both the provider and the user. Therefore, payment system 1 re-determines the amount of points to be used in the payment on the second smartphone.

[0029] For example, the payment system 1 determines the entire point balance, 700 points, as the point usage amount. The payment system 1 then starts payment for the second smartphone. Although the point usage amount of the point balance is different from that of the first smartphone, the payment process itself is the same as that of the first smartphone. For the second smartphone, 700 yen of the 2,600 yen communication fee is paid with points, and the remaining 1,900 yen is paid by credit card. When the payment for the second smartphone is completed, the point balance becomes 0 points.

[0030] As described above, the payment system 1 of this embodiment re-determines the point usage amount if the point balance is used for another payment between the time the point usage amount is determined and the time the payment is executed, resulting in an insufficient point balance at the time the payment is executed. The payment system 1 executes the payment based on the re-determined point usage amount. In this way, the payment system 1 ensures that the payment in which the point balance is used is completed. Details of the payment system 1 are explained below.

[0031] [3. Functions realized by the payment system] Fig. 4 is a diagram showing an example of functions realized by the payment system 1. Fig. 4 also shows an example of functions realized by each of the service providing system 2, the card company system 3, the point management system 4, and the user terminal 50.

[0032] [3-1. Functions realized by the payment system] For example, the payment server 10 includes a data storage unit 100, a management unit 101, a determination unit 102, and an execution unit 103. The data storage unit 100 is realized by the storage unit 12. The management unit 101, the determination unit 102, and the execution unit 103 are realized by the control unit 11.

[0033] [Data storage section] The data storage unit 100 stores data necessary for settlement. For example, the data storage unit 100 stores a first user database DB1.

[0034] FIG. 5 is a diagram showing an example of the first user database DB1. The first user database DB1 is a database that stores various information related to the user's payment method. For example, the first user database DB1 stores a user ID, a first token, a first card number, a first expiration date, and a first name. The first user database DB1 only needs to store any information related to the user's payment method, and the information stored in the first user database DB1 is not limited to the example of FIG. 5. For example, the user's point balance may be stored in the first user database DB1.

[0035] The user ID is an example of user identification information that can identify a user. Therefore, the description of user ID can be replaced with user identification information. The user identification information may be information other than a user ID and is not limited to a user ID. For example, the user identification information may be an email address or a telephone number. The user identification information may be information that can identify a user in some way. In this embodiment, an example is given in which the user ID is common to all services, but the user ID may be different for each service. If the user ID is different for each service, it is assumed that a correspondence indicating which user IDs correspond to the same user is recorded in the data storage unit 100.

[0036] In this embodiment, an example is given in which points held by a user are identified by a user ID. Therefore, the user ID can also be referred to as point identification information that can identify points. The point identification information may be information other than the user ID and is not limited to the user ID. For example, the point identification information may be a point ID, an email address, or a telephone number. The point ID is an ID different from the user ID. The user ID is used to log in to various services such as communication services, and the point ID is used to identify points.

[0037] The first token, first card number, first expiration date, and first name are the token, card number, expiration date, and name of a credit card managed by the payment system 1, respectively. The token is an example of card identification information that can identify a credit card. The card number also corresponds to card identification information, but a credit card can also be identified by a token. However, while the card number does not change in principle, the token may change even for the same credit card. For example, the token is information in which the card number has been tokenized. Tokenization is sometimes called encryption or hashing.

[0038] The data storage unit 100 can store any data. The data stored in the data storage unit 100 is not limited to the first user database DB1. For example, the data storage unit 100 may store a function for tokenization, a program for sharing information with the service providing system 2, or a program for payment. When payment methods other than credit cards and points are used, the data storage unit 100 may store information about the other payment methods. The information about the other payment methods itself may be publicly known information.

[0039] [Management Department] The management unit 101 manages a first token, a first card number, a first expiration date, and a first name related to a user's credit card in an associated manner. Managing in an associated manner means storing multiple pieces of information in memory in a state in which one piece of information can be searched for from the other piece of information. In this embodiment, storing information in the same record in the first user database DB1 corresponds to associating the information. The management unit 101 manages the first token, the first card number, the first expiration date, and the first name in an associated manner by storing the first token, the first card number, the first expiration date, and the first name in the same record in the first user database DB1.

[0040] For example, when a user performs a procedure to register a credit card, the management unit 101 issues a first token. The management unit 101 inputs the first card number into a function for tokenization and obtains the first token output from the function. The tokenization itself can use a known method, such as a one-way hash function, a pseudorandom function, or an encryption algorithm. The payment server 10 associates the obtained first token, the first card number, the first expiration date, and the first name, and stores them in the first user database DB1. The payment server 10 transmits the first token to the service providing server 20. This first token is managed by the service providing server 20 as a second token.

[0041] The first token may be any information that can identify a credit card and is different from a card number, and is not limited to the example of this embodiment. For example, the management unit 101 may generate a random character string unrelated to the first card number as the first token. The management unit 101 may generate the first token by tokenizing information other than a credit card, such as a user's name, address, telephone number, or email address. For example, the management unit 101 may periodically update the token for the same credit card.

[0042] [Decision section] The determination unit 102 determines the amount of points to be used from the point balance in a payment in which the point balance is used. Points are an example of a payment method. Therefore, any section describing points can be read as "payment method." For example, any section describing points can be read as "other payment methods," such as electronic money, debit cards, crypto assets, accounts, carrier billing, or wallets. The determination unit 102 may also determine the amount of balance to be used for a payment method other than points.

[0043] The point usage amount is the amount of the point balance that is used for payment. The point usage amount can also be called the allocation amount. The entire point balance may become the point usage amount, or only a portion of the point balance may become the point usage amount. The point usage amount may match the payment amount, or may be less than the payment amount. The point usage amount may be a fixed value or a variable value. If the point usage amount is a fixed value, the determination unit 102 determines the point usage amount so that it becomes a value specified in advance by the user. If the point usage amount is a variable value, the determination unit 102 may determine the point usage amount based on a predetermined determination method.

[0044] In this embodiment, the determination unit 102 determines the point usage amount based on the upper limit amount specified by the user who holds the points. For example, the upper limit amount is included in a payment file transmitted from the service providing server 20. The payment file is a file that shows details of each of multiple payments. For example, the payment file includes, for each individual payment, the user ID of the user making the payment, the payment amount, the second token, and the point usage conditions. The upper limit amount may be stored in the first user database DB1 instead of the payment file. In this case, the determination unit 102 references the first user database DB1 to obtain the upper limit amount.

[0045] For example, the determination unit 102 determines the point usage amount based on the upper limit amount included in the payment file. The determination unit 102 sends a reference request to the point management server 40 to inquire about the point balance. The reference request includes the user ID. The determination unit 102 determines the point usage amount based on the upper limit amount included in the payment file and the point balance received from the point management server 40.

[0046] For example, the determination unit 102 determines the point usage amount so as not to exceed the upper limit amount and the point balance. If the payment amount is equal to or greater than the upper limit amount and the point balance is equal to or greater than the upper limit amount, the determination unit 102 determines the upper limit amount as the point usage amount. If the payment amount is equal to or greater than the upper limit amount and the point balance is less than the upper limit amount, the determination unit 102 determines the point balance as the point usage amount. If the payment amount is less than the upper limit amount and the point balance is equal to or greater than the payment amount, the determination unit 102 determines the payment amount as the point usage amount.

[0047] In this embodiment, the determination unit 102 determines the point usage amount for each of multiple payments that are executed in parallel. "Parallel" means that processing for one payment and processing for another payment are executed simultaneously. The processing here includes not only the payment processing itself but also preparations such as determining the point usage amount. For example, the determination unit 102 can simultaneously execute processing to determine the point usage amount for one payment and processing to determine the point usage amount for another payment.

[0048] For example, if the point balance is used in a second payment of the multiple payments between the time the point usage amount for a first payment of the multiple payments is determined and the time the first payment is executed, and the point balance is insufficient when the first payment is executed, the determination unit 102 re-determines the point usage amount for the first payment. The first payment and the second payment are payments in which the same points are used. In this embodiment, if the point balance is used in a second payment of the communication service between the time the point usage amount for a first payment of the communication service is determined and the time the first payment is executed, and the point balance is insufficient when the first payment is executed, the determination unit 102 re-determines the point usage amount for the first payment. In other words, the first payment and the second payment are payments for the same communication service.

[0049] For example, if the point balance is used in another payment between the time the point usage amount is determined and the time the payment is executed, and the point balance is insufficient at the time the payment is executed, the determination unit 102 again determines the point usage amount. The other payment is a payment that uses the same points as the payment for which the point usage amount is determined. In the example of FIG. 3, the payment made by the first smartphone corresponds to the other payment. That is, if the point balance is used in the payment made by the first smartphone between the time the point usage amount for the second smartphone is determined and the time the payment made by the second smartphone is executed, and the point balance is insufficient at the time the payment made by the second smartphone is executed, the determination unit 102 again determines the point usage amount for the payment made by the second smartphone.

[0050] In the example of Figure 3, multiple payments by the same user are executed in parallel. However, the same point balance may be used for a payment by one user and a payment by another user. For example, the same point balance may be used for a payment by a father's smartphone and a payment by a child's smartphone. In this case, if the point balance is used for the payment by the father's smartphone between the determination of the point usage amount for the payment by the child's smartphone and the execution of the payment by the child's smartphone, and the point balance is insufficient when the payment by the child's smartphone is executed, the determination unit 102 again determines the point usage amount for the payment by the child's smartphone.

[0051] For example, the determination unit 102 determines the point usage amount without locking the point balance. Locking means preventing the point balance from being used for other purposes. In this embodiment, turning on the lock information described below corresponds to locking the point balance. When a payment or other payment is executed, the point balance is locked. For example, when the determination unit 102 determines the point usage amount, it does not send a lock request to the point management server 40. When the execution unit 103 described below executes a payment, the execution unit 103 sends a lock request to the point management server 40.

[0052] For example, the determination unit 102 may be capable of repeatedly determining the point usage amount until the number of times the point usage amount has been determined reaches a predetermined number. In this embodiment, the predetermined number is three, but the predetermined number may be any number that is determined in advance and is not limited to three. For example, the predetermined number may be one, two, or four or more. Each time the determination unit 102 determines the point usage amount for a payment, it increments the number of determinations for that payment. For a payment for which the number of determinations has reached the predetermined number, the determination unit 102 does not further repeat the process of determining the point usage amount.

[0053] The method for determining the point usage amount is not limited to the above example. For example, the determination unit 102 may determine the point usage amount based on a value obtained by subtracting a predetermined amount from the point balance and the upper limit amount included in the payment file. The predetermined amount may be an amount specified by the user as the minimum remaining point balance. For example, if the point balance is 1,700 points and the user specifies 800 points as the predetermined amount, the determination unit 102 determines the point usage amount based on 900 points (1,700 points minus 800 points) and the upper limit amount included in the payment file. If the upper limit amount is 1,000 points, the determination unit 102 determines 900 points as the point usage amount. For example, the determination unit 102 may determine the upper limit amount as the point usage amount regardless of the point balance. The determination unit 102 may determine the point usage amount so that the point usage amount is gradually reduced each time the point balance becomes insufficient.

[0054] [Executive Department] The execution unit 103 executes the payment. The execution unit 103 may execute the payment in a manner similar to known processing. For example, the execution unit 103 executes credit card payment by communicating with the card company server 30. The execution unit 103 executes point payment by communicating with the point management server 40. Credit card payment and point payment may be similar to known processing. In this embodiment, when there is no need to distinguish between credit card payment and point payment, they are simply referred to as payment.

[0055] For example, the execution unit 103 executes payment based on the point usage amount determined by the determination unit 102. The execution unit 103 executes point payment by communicating with the point management server 40 so that the point balance is used by the point usage amount determined by the determination unit 102. When the point usage amount is determined again by the determination unit 102, the execution unit 103 executes payment based on the point usage amount determined again. The execution unit 103 executes point payment by communicating with the point management server 40 so that the point balance is used by the point usage amount determined again by the determination unit 102.

[0056] For example, the execution unit 103 executes each of the multiple payments in parallel based on the amount of points used in each of the multiple payments. The execution unit 103 executes each of the first and second payments in parallel based on the amount of first points used in a first payment among the multiple payments and the amount of second points used in a second payment. If the second payment is executed before the first payment and the point balance becomes less than the amount of first points used, the amount of points used in the first payment is determined again, and the execution unit 103 executes the first payment based on the amount of points used again.

[0057] For example, the execution unit 103 may execute payment without using the point balance when the number of determinations reaches the upper limit. When the number of determinations reaches the upper limit, the execution unit 103 executes credit card payment without executing point payment. In this case, the execution unit 103 executes credit card payment so that the full payment amount is paid by credit card. Note that the execution unit 103 may cause the payment to fail when the number of determinations reaches the upper limit.

[0058] [3-2. Functions realized by the service provision system] For example, the service providing server 20 includes a data storage unit 200, a payment request unit 201, and a display control unit 202. The data storage unit 200 is realized by the storage unit 22. The payment request unit 201 and the display control unit 202 are realized by the control unit 21.

[0059] [Data storage section] The data storage unit 200 stores data necessary for providing services. For example, the data storage unit 200 stores a second user database DB2.

[0060] FIG. 6 is a diagram showing an example of the second user database DB2. The second user database DB2 stores various information related to the payment of communication fees for communication services. For example, the second user database DB2 stores a user ID, a payment amount, a second token, a second card number, a second expiration date, a second name, and point usage conditions. The second user database DB2 only needs to store any information related to the payment of communication fees for communication services, and the information stored in the second user database DB2 is not limited to the example shown in FIG. 6. For example, the second user database DB2 may store personal information registered by the user. If the user specifies a payment method other than a credit card, information related to the other payment method may be stored in the second user database DB2.

[0061] The second token, second card number, second expiration date, and second name are the token, card number, expiration date, and name, respectively, managed by the service providing system 2. In this embodiment, the second card number has less information than the first card number. For example, the second card number is only the last four digits of the first card number. When a user specifies point usage conditions on the confirmation screen SC or another screen, the point usage conditions associated with the user ID of this user are updated. The point usage conditions include at least one of whether or not points are to be used and the upper limit of points.

[0062] [Payment request section] The payment request unit 201 sends a payment request to the payment system 1. The payment request is data in a predetermined format that indicates the execution of a payment. For example, the payment request unit 201 sends a payment request that includes a payment file. The payment request unit 201 may send the payment file to the payment system 1 as data separate from the payment request. The payment request unit 201 may send multiple payments to the payment system 1 as separate data without combining them into a single payment file.

[0063] [Display control section] The display control unit 202 transmits display data for each screen to the user terminal 50. The display data may be any data for displaying some screen on the user terminal 50, such as HTML data or image data.

[0064] [3-3. Functions realized by the card company system] For example, the card company server 30 includes a data storage unit 300 and an execution unit 301. The data storage unit 300 is realized by the storage unit 32. The execution unit 301 is realized by the control unit 31.

[0065] [Data storage section] Data storage unit 300 stores data necessary for credit card payments. For example, data storage unit 300 stores a third card database that stores a third card number, a third expiration date, and a third name. The third card number, the third expiration date, and the third name are the card number, the expiration date, and the name, respectively, managed by the card company. The data stored in data storage unit 300 may be any known data necessary for credit card payments.

[0066] [Executive Department] The execution unit 301 executes a credit card payment. The credit card payment itself can be performed using a known process. For example, when the execution unit 301 receives a request to execute a credit card payment from the payment system 1, the execution unit 301 executes the credit card payment. This execution request includes information necessary for the credit card payment, such as the card number and the payment amount.

[0067] [3-4. Functions realized by the point management system] For example, the point management server 40 includes a data storage unit 400, a response unit 401, and an execution unit 402. The data storage unit 400 is realized by the storage unit 42. The response unit 401 and the execution unit 402 are realized by the control unit 41.

[0068] [Data storage section] The data storage unit 400 stores data necessary for point payment. For example, the data storage unit 400 stores a point database DB3.

[0069] Fig. 7 is a diagram showing an example of the point database DB3. The point database DB3 is a database in which various information related to points is stored. For example, the point database DB3 stores a user ID, a point balance, and lock information. The point database DB3 only needs to store any information related to points, and the information stored in the point database DB3 is not limited to the example of Fig. 7. For example, the point database DB3 may store a point usage history.

[0070] The point balance decreases when points are used. The point balance increases as a reward when a communication service or other service is used. The point balance may also increase due to some other reward. The point balance may have an expiration date. The lock information is information indicating whether the point balance is locked. For example, the lock information indicates a first value meaning that the point balance is locked, or a second value meaning that the point balance is not locked.

[0071] [Answer section] The reply unit 401 replies with the point balance to the payment system 1. In this embodiment, the determination unit 102 of the payment server 10 sends a point balance reference request to the point management system 4 in order to determine the point usage amount. The reference request is data in a predetermined format for referencing the point balance. For example, the reference request includes a user ID indicating the points to be referenced. The reply unit 401 refers to the point database DB3 and obtains the point balance associated with the user ID included in the reference request. The reply unit 401 obtains the obtained point balance from the payment system 1.

[0072] [Executive Department] The execution unit 402 executes the point payment. The point payment itself can use publicly known processing. For example, the execution unit 402 executes the point payment when it receives a request to execute the point payment from the payment system 1. This execution request includes information necessary for the point payment, such as the user ID and the amount of points used. When executing the point payment, the execution unit changes the lock information to a first value. In this state, the point balance cannot be changed by any other payment other than the payment currently being executed. Even if a request for another payment is accepted, the execution unit waits for the execution of that other payment. When the point payment is completed, the execution unit changes the lock information to a second value. In this state, the point balance can be changed by any other payment.

[0073] [3-5. Functions implemented on user devices] The user terminal 50 includes a data storage unit 500 and a display control unit 501. The data storage unit 500 is realized by the storage unit 52. The display control unit 501 is realized by the control unit 51.

[0074] [Data storage section] The data storage unit 500 stores data necessary for the user to use the service. For example, the data storage unit 500 stores a browser or a dedicated application for displaying the confirmation screen SC.

[0075] [Display control section] The display control unit 501 displays the confirmation screen SC on the display unit 55 based on the display data received from the service providing system 2.

[0076] [4. Processing performed by the payment system] Fig. 8 is a diagram showing an example of processing executed in the payment system 1. Fig. 8 also shows an example of processing executed in each of the service providing system 2, the card company system 3, the point management system 4, and the user terminal 50. The processing in Fig. 8 is executed by the control units 11, 21, 31, 41, and 51 operating in accordance with the programs stored in the storage units 12, 22, 32, 42, and 52, respectively.

[0077] 8, a process for the user to set a payment method for the communication service is executed between the service providing server 20 and the user terminal 50 (S1). In S1, when the user operates the user terminal 50 to log in to the communication service, a confirmation screen SC is displayed on the display unit 55. When the user changes the payment method or point usage conditions from the confirmation screen SC, the service providing server 20 updates the second user database DB2.

[0078] As a predetermined date and time approaches each month, the service providing server 20 creates a payment file indicating a large number of payments based on the second user database DB2 (S2). In S2, the service providing server 20 references the second user database DB2 and acquires, for each payment, the user ID of the user making the payment, the payment amount, the second token, and the point usage conditions. The service providing server 20 creates a payment file that consolidates this information for a large number of payments.

[0079] The service providing server 20 sends a payment request including a payment file to the payment server 10 (S3). When the payment server 10 receives the payment request from the service providing server 20 (S4), it executes multiple payments indicated in the payment file included in the payment request in parallel based on the first user database DB1 (S5). In S5, the payment server 10 selects multiple payments from the payment file and executes the selected multiple payments in parallel. Hereinafter, the payment for which the process of S5 is executed is referred to as the payment to be processed.

[0080] Figures 9 and 10 are diagrams showing an example of payments executed in parallel in S5 above. The payment server 10 executes the process shown in Figure 9 in parallel for each payment to be processed. The payment server 10 determines whether the user has specified the use of points based on the point use conditions of the payment to be processed (S500). If it is not determined in S500 that points will be used (S500:N), the payment server 10 determines the point usage amount so that the point usage amount becomes 0 (S501).

[0081] If it is determined in S500 that the user has specified the use of points (S500: Y), the payment server 10 executes a process to obtain the point balance with the point management server 40 (S502). In S502, the payment server 10 sends a reference request including the user ID to the point management server 40. Upon receiving the reference request, the point management server 40 refers to the point database DB3 and obtains the point balance associated with the user ID included in the reference request. The point management server 40 transmits the obtained point balance to the payment server 10.

[0082] The payment server 10 compares the upper limit of points specified by the user with the point balance acquired in S502 (S503). If it is determined in S503 that the point balance is equal to or greater than the upper limit (S503: equal to or greater than upper limit), the payment server 10 determines the point usage amount so that the upper limit is equal to the point usage amount (S504). If it is determined in S503 that the point balance is less than the upper limit (S503: less than upper limit), the payment server 10 determines the point usage amount so that the point balance is equal to the point usage amount (S505).

[0083] The payment server 10 compares the payment amount for the payment to be processed with the point usage amount (S506). If it is determined that the point usage amount is equal to or greater than the payment amount (S506: payment amount or greater), the payment server 10 executes point payment with the point management server 40 (S507). In S507, credit card payment is not executed. The payment server 10 determines whether or not the point payment has been successful (S508). If it is determined in S508 that the point payment has been successful (S508: Y), the process proceeds to S6 in FIG. 8.

[0084] If it is determined in S508 that the point payment has failed (S508: N), the payment server 10 increments the number of determinations of the point usage amount for the payment being processed (S509). The initial value of the number of determinations is 0. The payment server 10 determines whether the number of determinations has reached a predetermined number (S510). If it is determined that the number of determinations has not reached the predetermined number (S510: N), the process returns to S500. In this case, the payment server 10 determines the point usage amount again. If it is determined in S60 that the number of determinations has reached the predetermined number (S510: Y), the payment server 10 executes credit card payment with the card company server 30 (S511).

[0085] In S506, if it is determined that the amount of points used is less than the payment amount (S506: Less than payment amount), the process proceeds to FIG. 10, and point payment is executed with the point management server 40 (S512). The payment server 10 determines whether or not the point payment has been successful (S513). In S513, if it is determined that the point payment has not been successful (S513: N), the process proceeds to S509.

[0086] If it is determined in S513 that the point payment is successful (S513: Y), the payment server 10 executes a credit card payment with the card company server 30 (S514) and proceeds to the processing of S6 in FIG. 8. In S514, a credit card payment is executed for the payment amount of the payment to be processed that is not covered by the point payment. Note that before the point payment is executed in S512, a credit card may be pre-authorized to secure a credit card shopping limit. If the pre-authorization does not cover the shopping limit, the point payment in S512 may not be executed, and the payment to be processed may result in an error.

[0087] Returning to Figure 8, the payment server 10 determines whether all payments indicated in the payment file have been completed (S6). If it is determined in S6 that there are payments that have not yet been completed (S6: N), the process returns to S5. In this case, the process of S5 is executed for the payments that have not yet been completed. If it is determined in S6 that all payments have been completed (S6: Y), the payment server 10 transmits the result of the payment execution to the service providing server 20 (S7), and this process ends.

[0088] [5. Summary of embodiments] In this embodiment, if the point balance is used for another payment between the time the point usage amount is determined and the time the payment is executed, and the point balance is insufficient at the time the payment is executed, the payment system 1 re-determines the point usage amount. The payment system 1 executes the payment based on the re-determined point usage amount. This prevents a payment error due to an insufficient point balance and ensures that the payment is completed reliably.

[0089] Furthermore, if the point balance is used in a second payment of the multiple payments between the determination of the point usage amount for a first payment of the multiple payments and the execution of the first payment, and the point balance is insufficient at the time of execution of the first payment, the payment system 1 re-determines the point usage amount for the first payment. The payment system 1 executes the first payment based on the re-determined point usage amount. This prevents a payment error due to insufficient point balance, even if multiple payments using a user's points are executed in parallel, and ensures that the payments are completed reliably. Executing payments in parallel allows for rapid completion of payments.

[0090] Furthermore, if the point balance is used in a second payment for a given service between the determination of the point usage amount for a first payment for a given service and the execution of the first payment, and the point balance is insufficient when the first payment is executed, the payment system 1 again determines the point usage amount for the first payment. This prevents a payment error due to insufficient point balance even when multiple payments using a user's points for a given service are executed in parallel, and ensures that the payments are completed reliably. Because multiple payments are executed in parallel, the payments can be completed quickly.

[0091] Furthermore, the payment system 1 determines the amount of points to be used without locking the point balance. When a payment and another payment are executed, the point balance is locked. This allows the process of determining the amount of points to be used to be executed in parallel, allowing the payment to be completed quickly. Since the point balance is locked when a payment is executed, inconsistencies in the point balance can be prevented.

[0092] Furthermore, the payment system 1 determines the amount of points to be used based on the upper limit specified by the user who holds the points. This prevents the user from using more points than intended, thereby improving user convenience.

[0093] Furthermore, the payment system 1 can repeatedly determine the point usage amount until the number of times the point usage amount has been determined reaches a predetermined number. When the number of times the determination has reached the upper limit, the payment system 1 executes the payment without using the point balance. This prevents delays in completing the payment and ensures that the payment is completed reliably.

[0094] [6. Modifications] The present disclosure is not limited to the above-described embodiments, and can be modified as appropriate without departing from the spirit of the present disclosure.

[0095] [6-1. Variation 1] For example, in the embodiment, a case where a first payment and a second payment are executed in a communication service has been described, but the first payment and the second payment may be payments in different services. In the first modification, if the point balance is used in a second payment in a second service different from the first service between the determination of the point usage amount for the first payment in the first service and the execution of the first payment, and the point balance is insufficient at the time of execution of the first payment, the determination unit 102 again determines the point usage amount for the first payment.

[0096] For example, suppose the first service is a communication service and the second service is an e-commerce service. In this case, there is a possibility that points will be used in the e-commerce service between the time the point usage amount in the communication service is determined and the time the payment is actually made. In this case, the determination unit 102 may again determine the point usage amount in the communication service. The second service is not limited to an e-commerce service, and may be another service such as a travel reservation service. The second service may also be a point service that a user uses by presenting a point card at a physical store.

[0097] In the payment system 1 of the first variation, if the point balance is used in a second payment in a second service different from the first service between the determination of the point usage amount for a first payment in the first service and the execution of the first payment, and if the point balance is insufficient at the time the first payment is executed, the payment system 1 again determines the point usage amount for the first payment. This prevents a payment error due to an insufficient point balance, even if payments for multiple services are executed in parallel, and ensures that the payment is completed reliably.

[0098] [6-2. Variation 2] For example, as described in the embodiment, the execution unit 103 may execute a periodic payment. A periodic payment is a payment that is executed repeatedly. A periodic payment is also called a subscription. For example, a periodic payment may be a payment for a monthly billing service. A periodic payment may be a payment for a utility fee such as an electricity service other than a communication service. Data indicating the timing at which a periodic payment is executed is assumed to be recorded in advance in the service providing server 20. The service providing server 20 determines whether the time to execute a payment has arrived based on this data.

[0099] In the second modification, if the point balance is used for another non-periodic payment between the determination of the point usage amount for the periodic payment and the execution of the periodic payment, and the point balance is insufficient at the time of execution of the periodic payment, the determination unit 102 re-determines the point usage amount for the periodic payment. The execution unit 103 executes the periodic payment based on the re-determined point usage amount.

[0100] An irregular payment is a payment that is not made periodically. An irregular payment is a one-off payment that is not executed repeatedly. For example, a payment for purchasing a product in an e-commerce service, making a reservation in a travel booking service, or purchasing a product or service in a physical store corresponds to an irregular payment. The irregular payment itself may be a known process. Although it differs from the embodiment in that the point balance is less due to an irregular payment than the point usage amount in a regular payment, the processing of the determination unit 102 and the execution unit 103 may be the same as in the embodiment.

[0101] In the payment system 1 of the second variation, if the point balance is used for another non-periodic payment between the determination of the point usage amount for a periodic payment and the execution of the periodic payment, resulting in an insufficient point balance when the periodic payment is executed, the payment system 1 re-determines the point usage amount for the periodic payment. The payment system 1 executes the periodic payment based on the re-determined point usage amount. This prevents a payment error due to an insufficient point balance, even if the periodic payment and the non-periodic payment are executed in parallel, and ensures that the payment is completed reliably.

[0102] [6-3. Other Modifications] For example, the functions described as being realized by the payment server 10 may be shared among multiple computers in the payment system 1. In this case, each of the multiple computers may transmit its own processing results to the other computers, thereby realizing the sharing of functions. The payment system 1 may include at least one of a service providing system 2, a card company system 3, and a point management system 4.

[0103] [7. Notes] For example, the payment system according to the present disclosure can also be configured as follows. (1) a determination unit for determining the amount of the balance to be used in a payment in which the balance of the payment instrument is used; an execution unit that executes the payment based on the usage amount; Including, the determination unit determines the usage amount again if the balance is used for another payment during the period from when the usage amount is determined until the payment is executed, and the balance is insufficient at the time of execution of the payment; the execution unit executes the payment based on the re-determined usage amount. Payment system. (2) the determination unit determines the usage amount for each of the plurality of payments executed in parallel; the execution unit executes each of the plurality of payments in parallel based on the usage amount in each of the plurality of payments; the determination unit determines the usage amount for the first payment again when the balance is used for a second payment of the plurality of payments between the determination of the usage amount for a first payment of the plurality of payments and the execution of the first payment, and the balance is insufficient at the time of execution of the first payment; the execution unit executes the first payment based on the re-determined usage amount. (1) A payment system as described above. (3) the determination unit determines the usage amount for the first payment again when the balance is used for the second payment for the service during the period from when the usage amount for the first payment for the predetermined service is determined until when the first payment is executed, and when the balance is insufficient at the time of execution of the first payment; (2) A payment system as described above. (4) the determination unit determines the usage amount for the first payment again when the balance is used for the second payment in a second service different from the first service during the period from when the usage amount for the first payment in the first service is determined until when the first payment is executed, and the balance is insufficient at the time of execution of the first payment; A payment system according to (2) or (3). (5) the execution unit executes the periodic settlement; the determination unit determines the usage amount for the periodic payment again when the balance is used for the other non-periodic payment between the determination of the usage amount for the periodic payment and the execution of the periodic payment, and the balance is insufficient at the time of execution of the periodic payment; the execution unit executes the periodic payment based on the re-determined usage amount. A payment system according to any one of (1) to (4). (6) The determination unit determines the usage amount without locking the balance, When the payment and the other payment are executed, the balance is locked. A payment system according to any one of (1) to (5). (7) the determination unit determines the usage amount based on an upper limit amount specified by a user who holds the payment method. A payment system according to any one of (1) to (6). (8) the determination unit is capable of repeatedly determining the usage amount until the number of times the usage amount has been determined reaches a predetermined number, the execution unit executes the payment without using the balance when the number of determinations reaches the upper limit number. A payment system according to any one of (1) to (7). [Explanation of symbols]

[0104] 1 settlement system, 2 service providing system, 3 card company system, 4 point management system, N network, 10 settlement server, 11, 21, 31, 41, 51 control unit, 12, 22, 32, 42, 52 memory unit, 13, 23, 33, 43, 53 communication unit, 20 service providing server, 30 card company server, 40 point management server, 50 user terminal, 54 operation unit, 55 display unit, B1, B2 button, SC confirmation screen, 100 data memory unit, 101 management unit, 102 decision unit, 103 execution unit, 200 data memory unit, 201 settlement request unit, 202 display control unit, 300 data memory unit, 301 execution unit, 400 data memory unit, 401 response unit, 402 execution unit, 500 data memory unit, 501 display control unit, DB1 first user database, DB2 second user database, DB3 Points database.

Claims

1. a determination unit for determining the amount of the balance to be used in a payment in which the balance of the payment instrument is used; an execution unit that executes the payment based on the usage amount; Including, the determination unit determines the usage amount again when the settlement based on the usage amount fails; the execution unit executes the payment based on the re-determined usage amount. Payment system.

2. the determination unit determines the usage amount for each of the plurality of payments executed in parallel; the execution unit executes each of the plurality of payments in parallel based on the usage amount in each of the plurality of payments; the determination unit determines the usage amount for the first payment again when the balance is used for a second payment of the plurality of payments between the determination of the usage amount for a first payment of the plurality of payments and the execution of the first payment, and the balance is insufficient at the time of execution of the first payment; the execution unit executes the first payment based on the re-determined usage amount. The payment system according to claim 1 .

3. the determination unit determines the usage amount for the first payment again when the balance is used for the second payment for the service during the period from when the usage amount for the first payment for the predetermined service is determined until when the first payment is executed, and when the balance is insufficient at the time of execution of the first payment; The payment system according to claim 2 .

4. the determination unit determines the usage amount for the first payment again when the balance is used for the second payment in a second service different from the first service during the period from when the usage amount for the first payment in the first service is determined until when the first payment is executed, and the balance is insufficient at the time of execution of the first payment; The payment system according to claim 2 .

5. the execution unit executes the periodic settlement; the determination unit determines the usage amount for the periodic payment again if the balance is used for another non-periodic payment between the determination of the usage amount for the periodic payment and the execution of the periodic payment, and the balance is insufficient at the time of execution of the periodic payment; the execution unit executes the periodic payment based on the re-determined usage amount. A payment system according to any one of claims 1 to 4.

6. The determination unit determines the usage amount without locking the balance, When the payment and other payments are made, the balance is locked; A payment system according to any one of claims 1 to 4.

7. the determination unit determines the usage amount based on an upper limit amount specified by a user who holds the payment method. A payment system according to any one of claims 1 to 4.

8. the determination unit is capable of repeatedly determining the usage amount until the number of times the usage amount has been determined reaches a predetermined number, the execution unit executes the payment without using the balance when the number of determinations reaches the upper limit number. A payment system according to any one of claims 1 to 4.

9. 1. A computer-implemented payment method comprising: a determination step of determining a utilization amount of the balance in a payment in which the balance of the payment instrument is utilized; an execution step of executing the payment based on the usage amount; Including, The determining step determines the usage amount again when the settlement based on the usage amount fails, the execution step executes the payment based on the determined usage amount again. Payment method.

10. a determination unit for determining the amount of the balance to be used in a payment in which the balance of the payment means is used; an execution unit that executes the payment based on the usage amount; Make the computer function as the determination unit determines the usage amount again when the settlement based on the usage amount fails; the execution unit executes the payment based on the re-determined usage amount. program.

Images