Payment device, payment method, and program

Abstract

To provide a technology that enables more effective use of points as a means of payment in place of currency. [Solution] The payment device manages payments using points as a payment means instead of currency, and includes an issuance processing unit that issues the points to users free of charge, and a payment processing unit that, as a payment process when a first user purchases a product from a second user, executes a normal payment transaction in which the points equivalent to the price of the product are transferred from the first user's point account to the second user's point account, or a payment agency transaction in which the first user purchases points sold by a third user and the points equivalent to the price of the product are transferred to the second user's point account.

Description

[Technical field]

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

[0002] Conventionally, as a payment method to replace currency (circulating currency), there are known electronic money obtained by prepaying or postpaying currency, points awarded according to the amount of a product purchased using currency, etc. Note that prepaying or postpaying currency includes not only cash but also payments via financial institutions such as using a credit card or transferring to a bank account.

[0003] For example, Patent Document 1 describes a "depreciation type electronic currency system which depreciates the monetary value according to the holding period of electronic currency, comprising: means for storing information regarding the time and rate of depreciation; means for reading the amount of electronic currency and the expiration date of the electronic currency from a predetermined recording device which stores the electronic currency; means for depreciating the amount of electronic currency based on the information regarding the time and rate of depreciation and updating the expiration date to match the time of depreciation if the time when the recording medium is read is outside the expiration date of the read electronic currency; and means for reflecting the depreciated amount of electronic currency and the updated expiration date in the recording device." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2005-316521 A Summary of the Invention [Problem to be solved by the invention]

[0005] According to the technology described in Patent Document 1, the value of electronic currency (electronic money) held by consumers can be depreciated in accordance with the period of holding it, thereby encouraging consumers to use electronic money, and it is expected that the circulation of electronic currency will revitalize the economy.

[0006] Therefore, if the points held by consumers were allowed to depreciate according to the period they were held, or to be traded at an exchange rate based on market principles, it would be expected that the use of points would be promoted, the economy would be further stimulated, and activities that are meaningful to both consumers who purchase products and companies that sell products would be further promoted.

[0007] The present invention has been made in consideration of the above circumstances, and aims to provide a technique for more effectively utilizing points as a means of payment in place of currency. [Means for solving the problem]

[0008] The present application includes a number of means for solving at least part of the above problems, examples of which are as follows.

[0009] In order to solve the above problems, a payment device according to one embodiment of the present invention is a payment device that manages payments using points as a payment means instead of currency, and includes an issuance processing unit that issues the points to users free of charge, and a payment processing unit that, as a payment process when a first user purchases a product from a second user, executes a normal payment transaction in which the points equivalent to the price of the product are transferred from the first user's point account to the second user's point account, or a payment agency transaction in which the first user purchases points sold by a third user and the points equivalent to the price of the product are transferred to the second user's point account.

[0010] The payment processing unit can execute, in the payment agency transaction, any one of the following patterns: a first pattern in which the points purchased by the first user from the third user are transferred from the third user's point account to the second user's point account via the point account of the issuance processing unit; a second pattern in which the points purchased by the first user from the third user are transferred from the third user's point account to the second user's point account via the first user's point account; or a third pattern in which the points purchased by the first user from the third user are transferred directly from the third user's point account to the second user's point account.

[0011] The settlement device may include a point management unit that manages at least one of the expiration date, depreciation, and extinction of the points held by the user.

[0012] The point management unit can periodically shorten the expiration date of the points held by the user, periodically reduce the number of points held by the user, and delete the points whose expiration date has passed.

[0013] The issuance processing unit can issue prepaid points to the user for a fee and at a predetermined discount rate that can be used as a payment means equivalent to the points, and the point management unit can manage the expiration date of the prepaid points held by the user.

[0014] The prepaid points may include crypto assets.

[0015] In the payment agency transaction, the payment processing unit can allow the first user to purchase points being sold by the third user in accordance with limit orders or market orders specified by the third user and the first user, respectively.

[0016] The settlement device may include a market transaction processing unit that executes buying and selling of the points between users without buying and selling of products.

[0017] The market transaction processing unit can execute buying and selling of the points between the users in accordance with limit orders or market orders designated by each of the users who buy and sell the points.

[0018] The payment processing unit can deposit currency discounted by a predetermined payment / cash exchange fee rate into the currency account of the second user in response to the second user handing over the points equivalent to the price of the product.

[0019] The settlement device may include a profit and loss management unit that calculates profit and loss for the user's use of the points, and a UI control unit that presents the profit and loss to the user.

[0020] A payment method according to another aspect of the present invention is a payment method by a payment device that manages payments using points as a payment means instead of currency, and includes an issuance processing step of issuing the points to a user free of charge, and a payment processing step of executing, as a payment process when a first user purchases a product from a second user, a normal payment transaction in which the points equivalent to the price of the product are transferred from the first user's point account to the second user's point account, or a payment agency transaction in which the first user purchases points sold by a third user and the points equivalent to the price of the product are transferred to the second user's point account.

[0021] A program according to yet another aspect of the present invention causes a computer that manages payments using points as a payment means instead of currency to function as an issuance processing unit that issues the points to users free of charge, and as a payment processing unit that, as a payment process when a first user purchases a product from a second user, performs a normal payment transaction in which the points equivalent to the price of the product are transferred from the first user's point account to the second user's point account, or a payment agency transaction in which the first user purchases points sold by a third user and the points equivalent to the price of the product are transferred to the second user's point account. Effect of the Invention

[0022] According to the present invention, a technique can be provided for more effectively utilizing points as a means of payment in place of currency.

[0023] Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0024] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a payment system according to one embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram for explaining the flow of points, currency, and products in a normal payment transaction and an agent payment transaction in the payment process. [Diagram 3] FIG. 3 is a diagram illustrating an example of a data structure of the user table. [Figure 4] FIG. 4 is a diagram illustrating an example of the data structure of the point account table. [Diagram 5] FIG. 5 is a diagram illustrating an example of a data structure of the currency account table. [Figure 6] FIG. 6 is a diagram showing an example of the data structure of the currency deposit / withdrawal table. [Figure 7] FIG. 7 is a diagram showing an example of the data structure of the point issuing table. [Figure 8]FIG. 8 is a diagram showing an example of the data structure of the prepaid point issuing table. [Figure 9] FIG. 9 is a diagram illustrating an example of the data structure of the point expiration date change table. [Figure 10] FIG. 10 is a diagram showing an example of the data structure of the point depreciation table. [Figure 11] FIG. 11 is a diagram showing an example of the data structure of the point extinction table. [Figure 12] FIG. 12 is a diagram showing an example of the data structure of the points selling / product buying transaction table. [Figure 13] FIG. 13 is a diagram showing an example of the data structure of a company point selling / currency buying transaction table. [Figure 14] FIG. 14 is a diagram showing an example of the data structure of the settlement agent transaction table. [Figure 15] FIG. 15 is a diagram showing an example of the data structure of the settlement agent transaction_point selling table. [Figure 16] FIG. 16 is a diagram illustrating an example of a data structure of the point issuance_point account table. [Figure 17] FIG. 17 is a flowchart for explaining an example of a process for changing the expiration date, depreciating, and extinguishing points or the like. [Figure 18] FIG. 18 is a sequence diagram illustrating an example of a settlement agency transaction. [Figure 19] FIG. 19 is a diagram showing a display example of a payment screen as a UI screen. [Figure 20] FIG. 20 is a diagram showing a display example of a payment screen as a UI screen. [Figure 21] FIG. 21 is a diagram showing a display example of a payment completion screen as a UI screen. [Figure 22] FIG. 22 is a diagram showing a display example of a profit and loss notification screen as a UI screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In all the drawings for explaining the embodiment, the same members are generally given the same reference numerals, and the repeated description thereof will be omitted. In the following embodiment, the components (including element steps, etc.) are not necessarily essential, except when specifically stated or considered to be obviously essential in principle. In addition, when "consists of A", "consists of A", "has A", or "includes A", other elements are not excluded, except when specifically stated to include only that element. Similarly, in the following embodiment, when referring to the shape, positional relationship, etc. of components, etc., it includes those that are substantially similar or similar to the shape, etc., except when specifically stated or considered to be obviously not essential in principle.

[0026] <Payment system 10 according to one embodiment of the present invention> Fig. 1 shows an example of the configuration of a payment system 10 according to one embodiment of the present invention. The payment system 10 assumes that users are consumers who purchase products and companies that sell products, and uses points or prepaid points issued by issuers (both of which will be described in detail later) as a payment method for buying and selling products between users.

[0027] Hereinafter, when there is no need to distinguish between points and prepaid points, they will be referred to as points, etc. Furthermore, a user who is a consumer will be referred to as a consumer user, and a user who is a company will be referred to as a company user. When there is no need to distinguish between consumer users and company users, they will be referred to as users.

[0028] Each user is provided with a points account for managing points and the like owned by the user, and a currency account for managing currency prepared by the user for purchasing points and the like and currency exchanged for points and the like. Note that, in this embodiment, the "yen" is used as the currency unit, but other currency units such as, for example, "dollars" and "euros" may also be used.

[0029] An issuer of points, etc. is, for example, an administrator of the payment device 20 (described later). However, a person other than the administrator of the payment device 20 may be the issuer. Hereinafter, an operation mainly performed by an issuer substantially means an operation by the payment device 20. Also, an operation with respect to an issuer substantially means an operation with respect to the payment device 20.

[0030] The payment system 10 includes a payment device 20, a terminal device 30 used by a consumer user, and a terminal device 40 used by a corporate user, which are connected via a network N. The network N is a two-way communication network represented by the Internet, a mobile phone communication network, and the like.

[0031] The settlement device 20 issues points and the like to be used in commercial transactions such as purchasing products to users, manages the points and the like held by each user, and controls settlement processing using the points and the like.

[0032] The payment device 20 has functional blocks of a processing unit 21, a DB (database) unit 22, and a communication unit 23. The payment device 20 is made up of a general computer such as a server computer equipped with a processor such as a CPU (Central Processing Unit), a memory such as a DRAM (Dynamic Random Access Memory), a storage such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive), input devices such as a keyboard, a mouse, and a touch panel, an output device such as a display, and a communication module such as a NIC (Network Interface Card) (none of which are shown).

[0033] The processing unit 21 is realized by a computer processor. The processing unit 21 has the following functional blocks: an issuance processing unit 211, a points management unit 212, a settlement processing unit 213, a market transaction processing unit 214, a deposit / withdrawal processing unit 215, a profit / loss management unit 216, a remittance processing unit 217, and a UI (User Interface) control unit 218. These functional blocks are realized by the computer processor executing a predetermined program loaded into memory. However, some or all of these functional blocks may be realized as hardware using integrated circuits or the like. Furthermore, these functional blocks may be realized by multiple server computers distributed across the network N.

[0034] <Regarding the issuing processing unit 211> The issuance processing unit 211 executes a point issuing process for issuing points to a user, and a prepaid point issuing process for issuing prepaid points to a user. Note that prepaid points include crypto assets (virtual currencies). Since crypto assets are handled in this embodiment in the same way as prepaid points, "prepaid points" in this specification may be read as "crypto assets."

[0035] <About point issuing processing> The point issuing process periodically (for example, on the first day of each month) issues a certain number of points with an expiration date to a user free of charge. Note that a blockchain may be used to issue points. Hereinafter, n units of points will be referred to as n[P].

[0036] <About prepaid point issuing process> The prepaid point issuing process issues prepaid points to a user for a fee (prepaid in currency). Hereinafter, m units of prepaid points will be referred to as m[PP].

[0037] The prepaid point issuing process allows a predetermined discount rate r (0≦r<1) to be set when issuing prepaid points to a user, i.e., when selling prepaid points to a user. The discount rate r may be made variable for each user or depending on the time of issuance. A user can purchase prepaid points at 100(1-r) yen per 100[PP]. For example, if the discount rate r=0.1, a user can purchase 10,000[PP] for 9,000 (=10,000(1-0.1)) yen. Therefore, if a user purchases prepaid points with a set discount rate r and uses them to pay for a product, the user can purchase the product more cheaply than if they used currency.

[0038] Points are managed electronically and, in principle, do not have a physical form like currency such as paper money or coins. Users can use points to purchase products at a fixed rate of 1 [P] = 1 [PP] = 1 [yen].

[0039] <Currency backing for issuing points, etc.> The issuer holds n(1-p) [yen] (0≦p<1) as the currency backing for issuing n[P]. In addition, the issuer receives m(1-r) [yen] (0≦r<1) from users when issuing m[PP].

[0040] The issuer collects a settlement fee from the corporate user when a consumer user uses points, etc. for settlement to purchase a product. The issuer also collects an exchange fee when exchanging points, etc. for currency at the request of the corporate user. The settlement fee and the exchange fee are collectively referred to as the settlement and exchange fee. If the settlement and exchange fee rate is q (0≦q<1), then if p≦q, the issuer can issue n [P] and cover the exchange of points and currency with only the currency n(1-p) [yen] it holds. If r≦q, the issuer can issue m [PP] and cover the exchange of prepaid points and currency with only the currency m(1-r) [yen] it receives. This can prevent economic collapse due to a currency shortage in the settlement system 10. Of course, if the issuer procures currency in various ways, such as by receiving a loan from a financial institution, the settlement using points, etc. in the settlement system 10 can be made more economically stable.

[0041] <About the point management unit 212> The point management unit 212 manages the expiration dates of points and the like held by the user, and executes depreciation and extinction of points as the expiration dates decrease.

[0042] <About the expiration date and depreciation of points, etc.> Points are set with an expiration date (within six months in principle, for example, from the date of issue to the last day of the fifth month) at the time of issue, and the user is notified of the expiration date at the time of issue. Points are gradually depreciated (reduced) at a set rate periodically (for example, on the 1st of each month), and are completely extinguished when the expiration date has passed.

[0043] For example, n[P] issued in month t with a validity period of 6 months will depreciate at a rate of d on the first day of the first month (t+1). 6 (0≦d 6 <1) and n(1-d 6 )[P]. Similarly, on the first day of the second month (t+2), the depreciation rate is d 5 (0≦d 5 <1) and n(1-d 6 )(1-d 5)[P], and on the 1st day of the third month (t+3), the depreciation rate is d 4 (0≦d 4 <1) and n(1-d 6 )(1-d 5 )(1-d 4 )[P], and on the 1st day of the 4th month (t+4), the depreciation rate is d 3 (0≦d 3 <1) and n(1-d 6 )(1-d 5 )(1-d 4 )(1-d 3 )[P], and on the 1st day of the 5th month (t+5), the depreciation rate is d 2 (0≦d 2 <1) and n(1-d 6 )(1-d 5 )(1-d 4 )(1-d 3 )(1-d 2 )[P]. Then, on the 1st day of the (t+6) month, 6 months after the expiration date, the depreciation rate is calculated as d 1 (0≦d 1 <1) and n(1-d 6 )···(1-d 1 )[P] and then completely eliminated.

[0044] In addition, the expiration date, depreciation period, and depreciation rate d 6 ~d 1 The depreciation rate d may be changed for each user without being limited to the above example. 6 ~d 1 In addition, even if the points are within the validity period, if the balance of the points falls below a predetermined threshold value Bm due to depreciation, the points may be deleted.

[0045] Prepaid points are set with an expiration date (within one month in principle, such as the last day of the month in which they were issued) at the time of issue, and the user is notified of the expiration date at the time of issue. The expiration date of prepaid points is not limited to the above example, and may be changed for each user. There are two methods for depreciating prepaid points. In the first method, prepaid points that have passed their expiration date are extinguished, and instead are depreciated at a predetermined depreciation rate d p (0≦d p <1) are depreciated and issued with a validity period (for example, within 5 months). In other words, m[PP] will be depreciated to m(1-d p ) [P]. The points converted from prepaid points are periodically depreciated and disappear when the expiration date has passed, just like points issued free of charge. In the second method, like points, the value gradually depreciates (is reduced) at a set depreciation rate periodically (for example, on the 1st of each month) and disappears completely when the expiration date has passed. The following explanation will be given assuming the first depreciation method is adopted.

[0046] The expiration date, depreciation cycle, and depreciation rate set for points, etc. are maintained even if the holder is changed.

[0047] <Regarding the payment processing unit 213> The payment processing unit 213 executes a payment process to transfer points etc. between users when buying and selling goods. There are two types of payment processes: a normal payment transaction and an agency payment transaction. When purchasing a product, if the points etc. held by the user are equal to or greater than the product price, the payment processing unit 213 executes a normal payment transaction. If the points etc. held by the user are less than the product price, the payment processing unit 213 executes an agency payment transaction. However, even if the user has points etc. equal to or greater than the product price, the user may be allowed to select to have the payment processing unit 213 execute an agency payment transaction.

[0048] Figure 2 shows the flow of points, currency, and products in normal payment transactions and agency payment transactions, with thick solid arrows representing normal payment transactions and thick dashed arrows representing agency payment transactions. Thin solid arrows represent the issuance of points that takes place prior to normal payment transactions, and thin dashed arrows represent the exchange of points, etc., into currency that takes place after normal payment transactions and agency payment transactions.

[0049] <Regarding regular payment transactions> In a normal payment transaction, when consumer user A purchases a product from corporate user X, points etc. held by consumer user A are paid to corporate user X. The points etc. held by consumer user A are points issued free of charge by the issuer, prepaid points purchased by consumer user A from the issuer, or points etc. purchased by consumer user A from another user via the market prior to the purchase of the product (arrow a0).

[0050] In the case of a normal payment transaction, points equivalent to the price of the product are transferred from the points account of consumer user A to the points account of corporate user X via the issuer. In response, corporate user X delivers the product to consumer user A (arrow a1). At this time, the issuer can collect a payment fee from corporate user X.

[0051] In principle, points with the shortest validity period are used for payment, but the user can specify points with a period other than the shortest validity period to use for payment.

[0052] Corporate user X can receive currency from the issuer in exchange for the points etc. that he / she has received (in other words, he / she can exchange the points etc. for currency) (arrow a2). At this time, the issuer can collect an exchange fee from corporate user X.

[0053] For example, if a consumer user purchases a product worth n [yen] from a corporate user using n[P] (or n[PP]) issued during month t, the corporate user will receive n[P]. The corporate user can use the n[P] to purchase products or make payments between corporate users, or can hand it over to the issuer and receive the corresponding currency. For example, if a corporate user hands over all points, etc. received from consumer users to the issuer during month t, the original n[P] has not been depreciated, so at the end of the following month (t+1), the corporate user can receive n(1-q) [yen] minus the settlement and exchange fee rate q from the issuer.

[0054] For example, if a corporate user transfers all points, etc. from consumer users to the issuer within the next month (t+1), the initial n[P] will already be n(1-d 6 )[P], so at the end of the following month (t+2), the corporate user will receive the currency n(1-d 6 )(1-q) [yen] can be received from the issuer.

[0055] The timing from when a corporate user hands over points or the like to an issuer until when the corporate user can receive the currency is not limited to the end of the following month, and may be at another time.

[0056] The points etc. can also be used for settlement between corporate users X and Y. In this case, the issuer can collect a settlement fee from at least one of the corporate user who pays the points etc. and the corporate user Y who receives the points etc.

[0057] <About payment agency transactions> In a payment agency transaction, when a user (e.g., consumer user C) purchases a product from corporate user Y, the shortfall in points etc. held by consumer user C against the price of the product is made by consumer user C purchasing points etc. being sold by another user (e.g., consumer user B) with currency, and the points etc. are paid to corporate user Y. Note that the points etc. held by consumer user B are points issued free of charge by the issuer, prepaid points purchased by consumer user B from the issuer, or points etc. purchased by consumer user B from another user (arrow a10).

[0058] In addition, the user who purchases the product is not limited to a consumer user, but may be a corporate user. In addition, the user who sells the points, etc. is not limited to a consumer user, but may be a corporate user. The number of users who sell the points, etc. in a payment agency transaction is not limited to one, but may be more than one.

[0059] The flow of currency in a payment agency transaction is, for example, that currency to purchase missing points, etc. is moved from consumer user C's currency account to the issuer's currency account (arrow a11), and then moved from the issuer's currency account to consumer user B's currency account (arrow a12).

[0060] The flow of points, etc. is assumed to follow three patterns: In pattern 1, points, etc. are transferred from the point account of consumer user B to the point account of the issuer (arrow a13), and points, etc. are transferred from the point account of the issuer to the point account of corporate user Y (arrow a14).

[0061] In pattern 2, points etc. are transferred from consumer user B's point account to consumer user C's point account, and points etc. are transferred from consumer user C's point account to corporate user Y's point account (not shown).

[0062] In pattern 3, points and the like are transferred directly from the points account of consumer user B to the points account of corporate user Y (not shown).

[0063] After confirming that the points etc. used as payment for the product have been transferred to corporate user Y's point account, corporate user Y delivers the product to consumer user C (arrow a15). Note that the order of transfer of points etc. and currency is not limited to the above example. Corporate user Y can receive currency from the issuer in exchange for the points etc. received (arrow a16). At this time, the issuer can collect an exchange fee from corporate user Y.

[0064] Therefore, from the perspective of Consumer User B who sells points, etc., a payment agency transaction can essentially be considered as a function to exchange points, etc. for currency (a function to sell points, etc. and buy currency). Consumer User B who sells points, etc. can set a different desired exchange rate (the ratio at which points, etc. are exchanged for currency) for each expiration date of the points, etc. he holds, similar to limit orders in securities trading. Also, Consumer User B who sells points, etc. can sell points, etc. at the market price of points, etc., similar to market orders in securities trading. Furthermore, Consumer User B who sells points, etc. can set the number of points, etc. to be sold (number available for sale) for each expiration date of the points, etc. he holds.

[0065] In principle, points etc. will be exchanged for currency (i.e., selling points etc.) in order of expiry date, however, consumer users selling points etc. can specify an expiry date of their choice and give priority to selling points etc.

[0066] For example, if the settings for the sale of points by a consumer user are as follows: for points with a one-month expiration date, the exchange rate per 100 [P] is 80 [yen] and the number of points sold is 100 [P]; for points with a two-month expiration date, the exchange rate per 100 [P] is 86 [yen] and the number of points sold is 400 [P]; and for points with a three-month expiration date, the exchange rate per 100 [P] is 89 [yen] and the number of points sold is 300 [P]; and if a total of 600 [P] is sold, starting with the points with the shortest expiration date, then the average unit price per 100 [P] will be 85.5 [yen], as shown in the following formula.

[0067] Average unit price = (80 x 100 / 100 + 86 x 400 / 100 + 89 x 100 / 100) / (600 / 100) =85.5 [yen]

[0068] On the other hand, from the perspective of consumer user C who purchases goods, a payment agency transaction can be regarded as a function of exchanging currency for points, etc. (a function of buying points, etc. by paying currency) in conjunction with the purchase of goods. In this case, consumer user C who purchases points, etc. can set in advance the number of points, etc. to be purchased and the desired exchange rate between currency and points, etc., similar to limit orders in securities trading. Also, consumer user C who purchases points, etc. can purchase points, etc. at the current trading price in the market, similar to market orders in securities trading.

[0069] In addition, in the case of a limit order, with regard to which one or more consumer users to purchase points from, the settlement processing unit 213 will determine by matching, in principle, the desired exchange rate and sales quantity for each expiration date set by each consumer user selling points, etc., with the desired exchange rate and purchase quantity of consumer user C purchasing points, etc., so that consumer user C purchasing points, etc. can purchase points, etc. at the lowest price.

[0070] For example, assume that consumer user C is short of 10,000 [P] points when purchasing a product, and has set a desired exchange rate of 85 [yen] when purchasing the missing 10,000 [P] from another user. Also, assume that in the exchange market for points and currency, consumer user B is selling 3,000 [P] points with a one-month expiration date at a desired exchange rate of 85 [yen], consumer user D is selling 2,000 [P] points with a one-month expiration date at a desired exchange rate of 85 [yen] and 2,000 [P] points with a two-month expiration date at a desired exchange rate of 87 [yen], and consumer user E is selling 5,000 [P] points with a three-month expiration date at a desired exchange rate of 85 [yen].

[0071] In this case, following the principle, consumer user C will purchase 3,000 [P] points with a one-month expiration date at an exchange rate of 85 [yen] from consumer user B at the lowest possible price, 2,000 [P] points with a one-month expiration date at an exchange rate of 85 [yen] from consumer user D at the exchange rate of 85 [yen], and 5,000 [P] points with a three-month expiration date at an exchange rate of 85 [yen] from consumer user E at a total of 10,000 [P], thereby completing the exchange of currency and points.

[0072] In addition, if points etc. are not being sold at an exchange rate lower than consumer user C's desired exchange rate, consumer user C may be notified of this and encouraged to increase the desired exchange rate or change to a market order.

[0073] In the case of a market order, the payment processing unit 213 will perform matching to determine the desired exchange rate for the sale of points, etc., starting with the lowest (cheapest) so that consumer user C who is buying points, etc. can purchase the desired number of points, etc.

[0074] <Regarding payment fees for agency transactions> In a settlement agency transaction, the issuer can collect settlement agency fees by adding a spread to the desired exchange rate of points, etc. set by the consumer user selling points, etc., in the case of a limit order, similar to the spread in foreign exchange transactions, and presenting and selling it to consumer user C, who purchases points, etc. For example, if consumer user B's desired exchange rate of points, etc. is 85 [yen] per 100 [P] and the issuer's spread is 10 [yen] per 100 [P], the issuer can present 95 [yen] as the desired exchange rate per 100 [P] to consumer user C and sell it. When points, etc. are bought and sold at a desired exchange rate of 95 [yen] per 100 [P], 10 [yen] per 100 [P] becomes the issuer's profit as a settlement fee. In the case of a market order, the spread can be added to the current transaction price in the market.

[0075] <Promotion of use of payment agency transactions> The issuer reduces points or the like according to a reduction rate corresponding to the usage amount for both a user who sells points or the like using an agency settlement transaction and a user who purchases goods with currency. This can promote the use of agency settlement for users.

[0076] The reduction rate can be set as follows, for example. When a consumer user sells points or the like in an agency settlement transaction, if the number of sales is less than j[P] (or less than j[PP]; the same applies hereinafter), the reduction rate is a[%], and if it is j[P] or more, the reduction rate is b[%]. When a corporate user sells points or the like in an agency settlement transaction, if the number of sales is less than k[P], the reduction rate is c[%], and if it is k[P] or more, the reduction rate is d[%]. When a consumer user buys goods with currency in an agency settlement transaction, if the payment amount is less than m[yen], the reduction rate is e[%], and if it is m[P] or more, the reduction rate is f[%]. When a corporate user buys goods with currency in an agency settlement transaction, if the payment amount is less than n[yen], the reduction rate is g[%], and if it is n[P] or more, the reduction rate is h[%].

[0077] For the reduction rates a, b, c, d, e, f, g, h, by setting a < b, c < d, e < f, g < h, the usage amount of the agency settlement transaction can be further increased. Also, since it is conceivable that corporate users will hold more points or the like by selling goods, if a < c and b < d are set, the sale of points or the like to corporate users can be promoted.

[0078] Furthermore, in the case of the above-mentioned normal settlement transaction, when a corporate user exchanges points or the like from a consumer user who has purchased goods, it takes more than one month to receive currency. However, in the case where a corporate user sells out points or the like held through an agency settlement transaction, if the period until currency can be received is made shorter, the company's cash flow can be improved, so the use of agency settlement can be promoted.

[0079] <The essence of agency settlement transactions> In the above example of a payment agency transaction, consumer user B pays points, etc. to the issuer, which acts as an intermediary, and assumes the payment for consumer user C's purchase of a product, thereby coming to have a claim against consumer user C. The issuer is entrusted with the authority to receive the payment for the target claim from consumer user B, and collects currency from consumer user C and pays it to consumer user B. Thus, as explained above, a payment agency transaction can be considered as a function to exchange points, etc. for currency, but the essence of a payment agency transaction is ultimately the payment agency at the time of product purchase. Also, if consumer user B, who sells points, etc., provides points, etc. and acts as an agent for payment to corporate user Y, who sells products, as a type of service, the issuer acts as an intermediary between the seller and buyer of points, etc., to ensure the safety of the transaction.

[0080] <About the market transaction processing unit 214> The market transaction processing unit 214 executes market transaction processing and exchange reservation processing.

[0081] <Market transaction processing> The market transaction process involves buying and selling points and the like between users without the purchase of any products. In the market transaction process, users can buy and sell points and the like by limit orders or market orders, similar to the above-mentioned settlement agency transactions.

[0082] <About exchange reservation processing> The exchange reservation process is, for example, a reservation for the sale of remaining points, etc., immediately before the point depreciation date, etc. In the exchange reservation process, the user can set the sales timing for each expiration date of points, etc., the desired exchange rate for limit orders or market orders, and the number of points to be sold.

[0083] The exchange reservation process allows users who sell points, etc. to avoid forgetting that the depreciation or expiration date of points, etc. is approaching, and causing the points, etc. to depreciate or expire. Also, for users who purchase points, etc. and want to use them immediately to pay for products, etc., the sales volume of points, etc. increases just before the depreciation or expiration date, and the exchange rate between points, etc. and currency is expected to be favorable for buyers of points, etc., so points, etc. can be purchased cheaply. For companies, an increase in sales is expected as points, etc. become cheaper.

[0084] <About the deposit / withdrawal processing unit 215> The deposit / withdrawal processing unit 215 executes deposit / withdrawal processing for depositing and withdrawing currency from a user's currency account.

[0085] <About the Profit and Loss Management Department 216> The profit and loss management unit 216 calculates profit and loss for each user for a given period of time for purchasing products using points or the like, or for buying and selling points or the like in the settlement system 10.

[0086] <Profit and loss calculation formula> The profit and loss management unit 216 calculates profit and loss using, for example, the following formula. Profit / loss = Amount of product purchased using points etc. [yen] + Currency purchase amount by exchanging points etc. [yen] + Currency equivalent of points held [yen] - Currency payment amount for prepaid points [yen] -Currency selling amount [yen]

[0087] The first term on the right side of the profit and loss calculation formula, "product purchase amount using points, etc. [yen]," is the sum of the cumulative amount of points sales and product purchases in normal settlement transactions and the cumulative amount of points sales and product purchases in agency settlement transactions. Specifically, it is the sum of the cumulative amount of product amounts in each transaction record including the point account ID (FK) of the user's point sales and product purchase consumer in the point sales and product purchase transaction table 2210 (FIG. 12) that represents information related to normal settlement transactions, and the cumulative amount of product amounts in each transaction record including the point account ID (FK) of the user's currency sales and product purchase consumer in the agency settlement transaction table 2212 (FIG. 14) that represents information related to agency settlement transactions.

[0088] The second term on the right side of the profit and loss calculation formula, "Amount of currency purchased in exchange for points, etc. [yen]," is the cumulative amount of points sold and currency bought in the payment agency transaction. Specifically, it is the cumulative amount of "Number of prepaid points sold with an expiration date of 6 months" x their currency converted price + "Number of points sold each with an expiration date of 6 to 1 month" x the currency converted price for each of the expiration dates of 6 to 1 month for each point selling record that contains the user's point account ID (FK) in the payment agency transaction_point selling table 2213 (FIG. 15). In other words, it is the total amount of currency obtained by selling prepaid points and points in the payment agency transaction.

[0089] The third term on the right side of the profit and loss calculation formula, "currency converted value of owned points [yen]," is the total amount of currently owned points and prepaid points (1 [P] = 1 [PP] = 1 [yen]). Specifically, it is "prepaid points with an expiration date of 6 months" + "number of points with an expiration date of 6 to 1 month" in the user's point account table 222 (FIG. 4).

[0090] The fourth term on the right side of the profit and loss calculation formula, "Currency payment amount for prepaid points [yen]," is the cumulative amount of yen sales and prepaid points purchases. Specifically, it is the sum of the currency amounts of each issuance record that includes the point account ID (FK) of the user in the prepaid point issuance table 226 (FIG. 8).

[0091] The fifth term on the right-hand side of the profit and loss calculation formula, "Currency sales amount [yen]", is the cumulative amount of currency sales and points, etc. purchases in payment agency transactions. Specifically, it is the sum of the currency sales amounts of currency sellers and product buyers in each transaction record that includes the points account ID (FK) of the user's currency seller and product buyer in the payment agency transaction table 2212 (Figure 14).

[0092] However, the profit and loss calculation formula is not limited to the above example, and other formulas may be used to calculate the profit and loss.

[0093] <About the remittance processing unit 217> The remittance processing unit 217 executes remittance processing for sending points or the like between users without buying or selling products.

[0094] <About remittance processing> For example, when consumer user A sends points or the like to consumer user B, consumer user A designates consumer user B as the remittance destination. Various methods for designation can be adopted, such as creating a URL (Uniform Resource Locator) link where points or the like can be received and notifying only consumer user B of the link. Next, consumer user A designates the quantity n of points or the like to be remitted. In response to this, remittance processing unit 217 presents to consumer user A the lower of the price [yen] of n[P] when selling currency and purchasing points is applied to the current market exchange rate, or n(1-r) [yen], which is the price of n[PP] when discount rate r is applied when selling prepaid points, plus a predetermined fee. Then, when consumer user A pays the presented price of currency to the issuer, the issuer issues n[P] or n[PP] to consumer user B.

[0095] Unlike the remittance process described above, points and the like may be remitted from a remitter's point account to a remitter's point account between a predetermined number of pre-registered consumer users (e.g., family, friends, etc.). In this case, the issuer may or may not collect a predetermined fee.

[0096] <Regarding the UI control unit 218> The UI control unit 218 generates a UI screen and causes it to be displayed on the terminal devices 30 and 40, and receives information input by the user using the UI screen.

[0097] <Regarding the DB unit 22> The DB unit 22 is realized by a computer's processor, memory, and storage. The DB unit 22 generates and holds a user table, a point account table, a currency account table, a currency deposit / withdrawal table, a point issuance table, a prepaid point issuance table, a point expiration date change table, a point depreciation table, a point extinction table, a point selling product buying transaction table, a corporate point selling currency buying transaction table, a settlement agency transaction table, a settlement agency transaction_point selling table, and a point issuance_point account table. Note that the DB unit 22 may hold information and data other than the above-described tables. Details of each table will be described later.

[0098] The communication unit 23 is realized by a computer's communication module. The communication unit 23 connects to the terminal devices 30 and 40 via the network N and communicates various data and information.

[0099] The terminal devices 30 and 40 used by the user are composed of computers such as personal computers, smartphones, tablet terminals, and wearable terminals. As an example, the user uses the settlement system 10 using the terminal devices 30 and 40. When making a settlement using the terminal devices 30 and 40, in the case of a transaction on a website or application provided by an EC site or the like, the settlement can be made by inputting a settlement instruction. In the case of a settlement at a physical store, various settlement methods such as QR code (trademark) settlement, barcode settlement, and contactless settlement using an installed IC chip can be used. As another example, the user can use the settlement system 10 using a pre-created IC card.

[0100] <Regarding the data structures of various tables> 3 shows an example of the data structure of the user table 221. The user table 221 is for managing information about users, and a user record is generated in association with each user based on information input by the user at the time of user registration.

[0101] The user table 221 has a user ID, which is an identifier for uniquely identifying a user, as a PK (primary key), and columns for recording the user name, password, consumer or company flag, issuer flag indicating whether the user is an issuer of points or the like, date of birth (date of establishment), address, telephone number, email address, My Number or corporate number, and registration date and time. By recording the My Number or corporate number, the payment system 10 can also be used for transactions related to taxes and social security.

[0102] 4 shows an example of the data structure of the point account table 222. The point account table 222 is for managing information related to points and the like held by a user, and a point account record is generated in association with the user table of each user. The point account table 222 is recorded and updated according to the issuance process of points and the like by the issuance processing unit 211, the expiration date management of points and the like by the point management unit 212, depreciation, settlement process by the settlement processing unit 213, extinction process, and the desired exchange rate when buying and selling points and the like input by the user.

[0103] Note that each table from Figure 4 onwards corresponds to an example in which the expiration date of points is within six months, the expiration date of prepaid points is one month and they will expire after one month has passed, and instead points with an expiration date of five months are issued.

[0104] The point account table 222 has columns for recording the number of prepaid points with an expiration date of 6 months and the number of points with expiration dates of 6 to 0 months, with the point account ID, which is an identifier for uniquely identifying a point account, as the PK and the user ID as the FK (Foreign key). Note that the number of prepaid points with an expiration date of 6 months refers to the number of prepaid points that have an expiration date of 1 month or less and will be expired after the expiration date has passed, and instead will be issued points with an expiration date of 5 months or less. The same applies to the other tables described below.

[0105] For example, if a user purchases m[PP] prepaid points from an issuer during month t, m[PP] is recorded in the column for the number of prepaid points with a 6-month expiration date in the user's point account record. Then, on the 1st of month (t+1), m[PP] is deleted from the column for the number of prepaid points with a 6-month expiration date, and at the same time, the depreciation rate d is recorded in the column for the number of points with a 5-month expiration date. p Depreciated by m(1-d p )[P] is recorded.

[0106] For example, if a user is issued n[P] for free during month t, n[P] is recorded in the column for the number of points with a 6-month validity period in the point account record of the user. Then, on the 1st of month (t+1), n[P] is deleted from the column for the number of points with a 6-month validity period, and the depreciation rate d 6 Depreciated by n(1-d 6 )[P] is recorded. Similarly, points are periodically depreciated until the 1st of month (t+5), and on the 1st of month (t+6), n(1-d 6 )···(1-d 2 )[P] is deleted, and at the same time, the column for the number of points with a validity period of 0 months is updated with the number of expired points n(1-d 6 )···(1-d 1) [P] is recorded. The column for the number of points with an expiration date of 0 months is provided for convenience in order to allow for the expiry of points, and the number of points recorded in this column cannot be used for payments, etc.

[0107] Furthermore, the point account table 222 has columns for recording a flag indicating whether to make a limit order or a market order when purchasing points, a flag indicating whether to automatically change to purchasing prepaid points when a market order is selected when purchasing points and the market price is higher than the price of prepaid points, a desired exchange rate when making a limit order when purchasing points, a sales setting flag indicating whether to sell points held, a flag indicating whether to make a limit order or a market order when selling points, the number of points sold and the limit exchange rate for each validity period from 6 to 0 months, and a reservation for selling points (for example, selling 3 days before the expiration date).In addition, information regarding the purchase and sale of points is recorded based on settings made by the user and can be changed by the user as appropriate.

[0108] 5 shows an example of the data structure of the currency account table 223. The currency account table 223 is for managing information related to currencies held by users, and a currency account record is generated in association with the user record of each user.

[0109] The currency account table 223 has columns for recording the currency balance in the currency account, with the currency account ID, which is an identifier for uniquely identifying the currency account, as PK and the user ID as FK.

[0110] 6 shows an example of the data structure of the currency deposit / withdrawal table 224. The currency deposit / withdrawal table 224 is for managing information related to the deposit / withdrawal of currency between a user's currency account and the user's bank account, etc., and for each transaction (currency deposit / withdrawal) by the deposit / withdrawal processing unit 215, a currency deposit / withdrawal record is generated in association with the user's currency account record.

[0111] It should be noted that the method of depositing currency into a user's currency account is not limited to a bank account, and may also be, for example, a credit card or a dedicated terminal such as an ATM (automated teller machine).

[0112] The currency deposit / withdrawal table 224 has columns for recording the date and time of the currency deposit / withdrawal, the bank account name, the bank account number, and the amount of the currency deposit / withdrawal, with the currency deposit / withdrawal ID, which is an identifier for uniquely identifying the currency deposit / withdrawal to the user's currency account, as PK and the currency account ID as FK.

[0113] 7 shows an example of the data structure of the point issuance table 225. The point issuance table 225 is for managing information related to points issued by an issuer to a user, and every time the issuance processing unit 211 issues points to a user, a point issuance record is generated in association with the point account record of the user.

[0114] The point issuance table 225 has columns for recording the point issuance date and time, the point account ID (FK) to which the points are issued, and the number of points issued with each expiration date of 6 to 1 month, with the point issuance ID being used as the PK, which is an identifier for uniquely identifying the issuance of points by the issuer to the user.

[0115] 8 shows an example of the data structure of the prepaid point issuance table 226. The prepaid point issuance table 226 is for managing information regarding prepaid points issued by an issuer to a user, and every time the issuance processing unit 211 issues prepaid points to a user, a prepaid point issuance record is generated in association with the point account record of the user.

[0116] The prepaid point issuance table 226 has columns for recording the date and time of issuance of the prepaid points, the number of prepaid points issued with a one-month validity period, and the amount of currency paid by the user in exchange for the issuance of the prepaid points, with the prepaid point issuance ID as PK, which is an identifier for uniquely identifying the issuance of prepaid points by the issuer to the user, and the point account ID to which the points are issued as FK.

[0117] 9 shows an example of the data structure of the point expiration date change table 227. The point expiration date change table 227 is for managing information related to changes in the expiration date of points, and each time the point management unit 212 changes the expiration date of points, a point expiration date change record is generated in association with the point account record of the user.

[0118] The point expiration date change table 227 has columns for recording the date and time when the expiration date was changed and the number of months for which the expiration date was changed (basically one month), with the point expiration date change ID, which is an identifier for uniquely identifying the process that changed the point expiration date, the new point account ID, and the new point issue ID as PK. The new point account ID and new point issue ID also serve as FK.

[0119] 10 shows an example of the data structure of the point depreciation table 228. The point depreciation table 228 is for managing information related to the depreciation of points, and every time the point management unit 212 depreciates points, a point depreciation record is generated in association with the point account record of the user.

[0120] The point depreciation table 228 has columns for recording the date and time when points were depreciated and the point depreciation rate, with the point depreciation ID, which is an identifier for uniquely identifying the process that depreciated the points, the point account ID of the depreciation destination, and the point issue ID of the depreciation destination as PK. The point account ID of the depreciation destination and the point issue ID of the depreciation destination also serve as FK.

[0121] 11 shows an example of the data structure of the point extinction table 229. The point extinction table 229 is for managing information regarding the extinction of points, etc., and each time the point management unit 212 extinguishes points, a point extinction record is generated in association with the point account record of the user.

[0122] The point extinction table 229 has columns for recording the date and time when points were extinguished, with a point extinction ID, which is an identifier for uniquely identifying the process that extinguished points, a point account ID of the extinction destination, and a point issue ID of the extinction destination as PK. The point account ID of the extinction destination and the point issue ID of the extinction destination also serve as FK.

[0123] 12 shows an example of the data structure of the point selling / product buying transaction table 2210. The point selling / product buying transaction table 2210 is for managing information on normal payment transactions (point selling / product buying transactions), and each time the payment processing unit 213 executes payment processing for a product purchase by a user through a normal payment transaction, a point selling / product buying transaction record is generated in association with the point account record of the point selling / product buying consumer user.

[0124] The points selling / product buying transaction table 2210 has a points selling / product buying transaction ID as the PK, which is an identifier for uniquely identifying a points selling / product buying transaction, and columns for recording the date and time of the transaction, the points account ID (FK) of the consumer user selling points / product buying, the points account ID (FK) of the corporate user selling the product, the number of prepaid points with a 6-month expiration date that the consumer user paid (sold) to purchase a product, the number of points sold with expiration dates from 6 months to 1 month, the product name, and the product price.

[0125] 13 shows an example of the data structure of the company point selling / currency buying transaction table 2211. The company point selling / currency buying transaction table 2211 is for managing information regarding point selling / currency buying transactions (cash exchange transactions in which owned points are sold and currency is bought) by company users. In the company point selling / currency buying transaction table 2211, a company point selling / currency buying transaction record is generated in association with the point account record of the company user each time the market transaction processing unit 214 performs a cash exchange transaction with a company.

[0126] The corporate point sell / currency buy transaction table 2211 has a point sell / currency buy transaction ID, which is an identifier for uniquely identifying a point sell / currency buy transaction, as the PK, and columns for recording the date and time of the transaction, the point account ID (FK) of the corporate user selling the points, etc., the user ID (FK) of the issuer buying the points, etc., the number of prepaid points with a 6-month expiration date sold (i.e., converted into cash) by the corporate user, the number of points sold with expiration dates from 6 months to 1 month, and the currency buy amount.

[0127] 14 shows an example of the data structure of the payment agency transaction table 2212. The payment agency transaction table 2212 is for managing information related to payment agency transactions, and each time the payment processing unit 213 executes a payment agency transaction for a product purchase by a user, a payment agency transaction record is generated in association with the point account record of the consumer user who sells currency and buys products.

[0128] The payment agency transaction table 2212 has a payment agency transaction ID, which is an identifier for uniquely identifying a payment agency transaction, as the PK, and columns for recording the date and time of the transaction, the points account ID (FK) of the currency selling / product buying consumer, the number of prepaid points sold by the currency selling / product buying consumer with a 6 month expiration date, the number of points sold by the currency selling / product buying consumer with expiration dates of 6 to 1 month, the total number of points sold by the point selling / currency buying consumer, the currency account ID (FK) of the currency selling / product buying consumer, the currency selling amount by the currency selling / product buying consumer, the points account ID (FK) of the product selling company, the product name, and the product price.

[0129] Fig. 15 shows an example of the data structure of the payment agency transaction_point selling table 2213. The payment agency transaction_point selling table 2213 is for managing information regarding the selling of points by point selling / currency buying consumers in payment agency transactions, and for each payment agency transaction, a payment agency transaction_point selling record is generated for one or more point selling / currency buying consumers in association with the payment agency transaction record of the payment agency transaction.

[0130] The payment agency transaction_point selling table 2213 has columns for recording the date and time of the transaction, the payment agency transaction ID (FK), the points account ID (FK) of the point selling / currency buying consumer, the currency account ID (FK), the number of prepaid points sold with an expiration date of 6 months, the number of points sold with expiration dates of 6 to 1 month, the currency converted price (per unit) of the prepaid points sold, and the currency converted price (per unit) of the points sold with expiration dates of 6 to 1 month, as well as the transaction date and time.

[0131] 16 shows an example of the data structure of the point issuance_point account table 2214. The point issuance_point account table 2214 is provided to enable tracing of multiple past point issuance IDs and prepaid point issuance IDs included in points for each expiration date when points, etc. are issued multiple times in the same month to the same user, and each time the issuance processing unit 211 issues points, etc. to a user, a point issuance_point account record is generated in association with the point account record of the user.

[0132] The point issuance_point account table 2214 has columns for recording the date and time when points were issued, the point issuance ID (FK), the prepaid point issuance ID (FK), the issuing point account ID (FK), the latest prepaid point issuance ID (FK) with an expiration date of 6 months, and the latest point issuance ID (FK) for each of the expiration dates 6 to 1 month, with the point issuance_point account ID as the PK, which is an identifier for uniquely identifying a point issuance_point account record.

[0133] <Regarding changes to expiration dates, depreciation, and extinction of points, etc.> FIG. 17 is a flowchart for explaining an example of processing for changing the expiration date, depreciating, and extinguishing points, etc., by the point management unit 212.

[0134] This process is executed periodically (for example, on the first day of each month) for each user's point account record in the point account table 222.

[0135] First, the point management unit 212 initializes a parameter y to 1 (step S1). Next, the point management unit 212 refers to the column of the number of points with an expiration date of y months in the point account record, obtains the balance n[P], and erases the record in that column (step S2). Next, the point management unit 212 multiplies the balance n[P] obtained in step S2 by a depreciation rate d y Next, the point management unit 212 calculates the n(1-d y) [P] is stored in the point number column for the expiration date (y-1) months of the point account record (step S2).

[0136] In this case, since the parameter y = 1, the number of points n[P] for the point account record with a one-month validity period is obtained, and n(1-d 1 ) [P] and then stored in the points column with a 0 month expiration date in the points account record.

[0137] Next, the point management unit 212 determines whether the expiration date parameter y is 6 (step S5), and if it determines that the expiration date parameter y is not 6 (NO in step S5), it increments the parameter y by 1 (step S6) and returns the processing to step 2.

[0138] From this point on, steps S2 to S6 are repeated until it is determined in step S5 that the parameter y is 6, and the number of points n in the point account record with an expiration date of 2 to 6 months is deducted and moved to the column of the number of points with an expiration date of 1 to 5 months.

[0139] Then, if it is determined that the parameter y is 6 (YES in step S5), the point management unit 212 erases (rewrites to 0) the number of points stored in the point number column with an expiration date of 0 months in the point account record (step S7).

[0140] Next, the point management unit 212 refers to the column of the number of prepaid points with a validity period of six months in the point account record, obtains the balance m[PP], and erases the record in the column (step S8). Next, the point management unit 212 calculates m[P], which is the same amount as the balance m[PP] obtained in step S8, at a depreciation rate d p Next, the point management unit 212 calculates the m(1-d p ) [P] is added to the column of the number of points with a 5 month expiration date in the point account record (step S10).

[0141] This completes the process of changing the expiration date, depreciation, and extinction of points, etc., by the point management unit 212.

[0142] <About payment agency transactions> FIG. 18 is a sequence diagram illustrating an example of a payment agent transaction performed by the payment processing unit 213.

[0143] First, for example, when consumer user A uses a terminal device 30 (hereinafter referred to as terminal device 30A) to access an EC site that uses payment system 10 (step S11), a product introduction screen (not shown) for introducing and purchasing products is displayed on terminal device 30A (step S21).

[0144] In addition, an EC site may be one set up independently by a corporate user selling products, a marketplace type site that collects products offered by multiple corporate users, or a mall type site in which multiple corporate users manage their own sales areas.

[0145] Next, when consumer user A selects a product he / she wants to purchase on the product introduction screen displayed on terminal device 30A and instructs purchase (step S12), the EC site requests payment processing from payment processor 213 of payment device 20 (step S22). The request for payment processing includes the transmission of payment processing information required for payment processing, such as the user ID of consumer user A who purchases the product, the user ID of corporate user X who sells the product, the product name (which may be identification information such as product ID), and the product price.

[0146] In the example shown in the figure, the payment processing information is transmitted all at once, but some information may be transmitted at different times. Furthermore, the payment processing information is not limited to the EC site, and may be transmitted from, for example, another device linked to the EC site or the terminal device 30A of consumer user A.

[0147] In this example, it is assumed that consumer user A selects a product (book) for 10,000 yen sold by corporate user X, instructs to purchase it, and does not have points or the like.

[0148] Next, the payment processing unit 213, based on the user ID of consumer user A purchasing the product, refers to the point account record associated with the user record of consumer user A to confirm whether consumer user A has points etc. equal to or greater than the price of the product, and calculates the number of points that are lacking relative to the price of the product (step S31).

[0149] Then, the UI control unit 218 causes the terminal device 30A to display the number of points that is lacking (in this case, 10,000 [P]) and a settlement screen 1000 (Figure 19, etc.) on which consumer user A can select a limit order or a market order (step S32).

[0150] 19 and 20 show examples of the payment screen 1000, with Fig. 19 being an example of the display when consumer user A has selected limit order as the initial setting when purchasing points, etc., and Fig. 20 being an example of the display when consumer user A has selected market order as the initial setting when purchasing points, etc. When checking the initial setting when purchasing points, etc., the points account table 222 corresponding to consumer user A is referenced.

[0151] The payment screen 1000 has a display field 1001 that displays the number of points required to purchase a product compared to the number of points required to purchase the product, radio buttons 1002 that allow the user to select a limit order, a market order, or the purchase of prepaid points, a display field 1003 that displays the purchase price of points, etc., and a "Charge & Pay" button 1004 that allows the user to instruct the purchase of points, etc.

[0152] As shown in FIG. 19, when limit order is selected with radio button 1002, the user can change the desired exchange rate (90 [yen] (including spread) in the figure) on settlement screen 1000.

[0153] Returning to Fig. 18, when consumer user A selects limit order or market order with radio button 1002 on payment screen 1000 and operates "Charge & Pay" button 1004 to instruct payment (step S13), payment processing unit 213 matches the buying and selling of points, etc., and determines a user who will sell points, etc. to consumer user A (step S33).

[0154] For simplicity's sake, let us assume that matching has been performed so that consumer user A places a limit order to purchase 10,000 [P] points with a one-month expiration date from consumer user B at an exchange rate of 90 [yen] (including spread).

[0155] Next, the settlement processing unit 213 executes the buying and selling of points, etc. Specifically, 9,000 [yen], which is the purchase price of points, etc., is transferred from consumer user A's currency account to the currency account of the issuer. Also, 10,000 [P] is transferred from consumer user B's point account to consumer user A's point account, and the point account records of consumer users A and B are updated. Furthermore, the sales price of points, etc., which is 9,000 [yen] paid by consumer user A as the purchase price of points, etc. minus the spread, is transferred from the issuer's currency account to consumer user B's currency account (step S34). However, the timing of the transfer of the sales price of points, etc. to consumer user B's currency account may be at a later date.

[0156] Next, the payment processing unit 213 transfers 10,000 [P], which is equivalent to the product price, from the points account of consumer user A to the points account of corporate user X (step S35). Next, the payment processing unit 213 records information related to steps S34 and S35 in the payment agency transaction table 2212 and the payment agency transaction_point selling table 2213 (step S36).

[0157] Specifically, a payment agency transaction record is generated, and the issued payment agency transaction ID, date and time, consumer user A's point account ID, consumer user A's point sales amount with one month validity (10,000 [P]), consumer user B's total point sales amount (10,000 [P]), consumer user A's currency account ID, consumer user A's currency sales amount (9,000 [yen]), corporate user X's point account ID, product name (book), and product amount (10,000 [yen]) are recorded. Also, a payment agency transaction_point selling record is generated, and the issued payment agency transaction_point selling ID, date and time, payment agency transaction ID, consumer user B's point account ID, consumer user B's currency account ID, consumer user B's point sales amount with one month validity (10,000 [P]), and point currency converted price with one month validity (0.9 [yen] per unit) are recorded.

[0158] The order of steps S33 to S35 is not limited to the above example, and may be any order. For example, the issuer may advance the points to be paid to the corporate user X to perform step S35, and then steps S33 and S34 may be performed.

[0159] After the buying and selling of points and the payment of points to corporate user X are completed in the above manner, the UI control unit 218 then causes the terminal device 30A to display a payment completion screen 1100 (FIG. 21) (step S37).

[0160] 21 shows an example of a payment completion screen 1100. The payment completion screen 1100 displays the number of points, etc. purchased through the payment agent transaction, the number of points, etc. paid as the purchase price of the product, and the remaining balance of points, etc.

[0161] Returning to Fig. 18, next, when the payment processing unit 213 notifies the EC site of the completion of the settlement process through the agent transaction (step S38), the EC site causes the terminal device 30A to display a purchase procedure completion screen (not shown) (step S23).

[0162] This concludes the explanation of the settlement agent transaction by the settlement processing unit 213. When using the settlement agent transaction, the user may be able to purchase points, etc. at a lower price than when purchasing prepaid points, depending on the desired exchange rate when selecting a limit order, or the market price when selecting a market order. However, there may be cases where there are no other users selling points, etc. at the desired exchange rate of the limit order set by the user, or where the market price of points, etc. in a market order is higher than the selling price of prepaid points. In such cases, the user may select prepaid point purchase using the radio button 1002 on the settlement screen 1000. In addition, the user may set in advance that in such cases, the limit order or market order is automatically changed to prepaid point purchase.

[0163] As a variant example, the process of displaying the settlement screen 1000 on the terminal device 30A and having consumer user A select a limit order or a market order (steps S32, S13) may be omitted, and the buying and selling of points, etc. may be matched according to the desired exchange rate for limit orders or market orders that consumer user A has set in advance.

[0164] In FIG. 18, the payment at the time of purchasing a product on an EC site is described as an example, but it goes without saying that the payment device 20 can be applied to other payment methods. As an example, in code payment, when a store terminal (terminal device 40) of a real store scans a code displayed on a consumer user's terminal device 30, the store terminal may transmit payment request information to the payment device 20. In that case, the payment screen 1000 and the payment completion screen 1100 may be displayed on the store terminal or the user's terminal device 30. As another example, in code payment, when a consumer user's terminal device 30 scans a code displayed on a real store, the user's terminal device 30 may transmit payment request information to the payment device 20. In that case, the payment screen 1000 and the payment completion screen 1100 may be displayed on the user's terminal device 30. As yet another example, when payment is made with an IC chip mounted on the consumer user's terminal device 30 or an IC card of the consumer user, the store terminal (terminal device 40) that scans the IC chip or IC card may transmit payment request information to the payment device 20. The payment screen 1000 and the payment completion screen 1100 may be displayed on the store terminal or the terminal device 30 of the user.

[0165] <Example of profit and loss notification screen> FIG. 22 shows an example of a profit and loss notification screen 1200 displayed on the terminal device 30 to notify the user of the profit and loss calculated by the profit and loss management unit 216. As shown in FIG.

[0166] The profit and loss notification screen 1200 is displayed on the terminal device 30 in response to a predetermined operation by the user. The profit and loss notification screen 1200 displays the profit and loss (+8,000 "yen" in the figure) of the user for purchasing products using points or buying and selling points during a predetermined period. As reference information, the exchange rate when selling currency and purchasing points (100 [yen] = 102 [P] in the figure) and the exchange rate when buying currency and selling points (100 [yen] = 110 [P] in the figure) may be displayed.

[0167] According to the profit and loss notification screen 1200, the profit obtained by using the payment system 10 can be clearly shown to the user as a numerical value, and therefore the user can be encouraged to use the payment system 10.

[0168] The present invention is not limited to the above-described embodiment and modifications, and various modifications are possible. For example, the above-described embodiment and modifications have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those having all of the configurations described. In addition, it is possible to replace a part of a modification with another modification, or to combine the modifications.

[0169] In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware, for example, by designing a part or all of them as an integrated circuit. In addition, each of the above configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as a program, table, file, etc. that realizes each function can be placed in a memory, a recording device such as a hard disk or SSD, or a recording medium such as an IC card, an SD card, or a DVD. In addition, the control lines and information lines are shown as those considered necessary for explanation, and not all control lines and information lines are necessarily shown in the product. In reality, it may be considered that almost all configurations are connected to each other. [Explanation of symbols]

[0170] 10....Payment system, 20....Payment device, 21....Processing unit, 211....Issuance processing unit, 212....Point management unit, 213....Payment processing unit, 214....Market transaction processing unit, 215....Deposit / withdrawal processing unit, 216....Profit and loss management unit, 217....Remittance processing unit, 218....UI control unit, 22....DB unit, 221....User table, 222....Point account table, 223....Currency account table, 224....Currency deposit / withdrawal table, 225....Point issuance table, 226....Prepaid point issuance table, 227...Point expiration date change table, 228...Point depreciation table, 229...Point disappearance table, 2210...Point sell / product buy transaction table, 2211...Company point sell / currency buy transaction table, 2212...Settlement agency transaction table, 2213...Settlement agency transaction_point sell table, 2214...Point issue_point account table, 23...Communication unit, 30...Terminal device, 40...Terminal device, 1000...Settlement screen, 1100...Settlement completion screen, 1200...Profit and loss notification screen

Claims

1. A payment device that manages payments using points as a payment means instead of currency, an issuance processing unit that issues the points to a plurality of users free of charge; a point management unit that manages the expiration date, depreciation, and extinction of the points held by each of the users, periodically shortens the expiration date of the points held by each of the users, periodically reduces the number of the points held by each of the users, and extinguishes the points whose expiration date has passed; As a payment process when a first user purchases a product from a second user, a normal settlement transaction for transferring the points equivalent to the price of the product from the point account of the first user to the point account of the second user; a payment processing unit that executes a payment agency transaction in which the first user purchases points sold by a third user and the number of points corresponding to the price of the product is transferred to the point account of the second user; The payment processing unit calculates the number of points that the first user's owned points are short of for the price of the product in the payment agency transaction, determines one or more of the third users from among the multiple users selling their owned points by matching based on a desired exchange rate or market price, transfers currency as payment for purchasing the shortfall in points from the determined third user from the currency account of the first user to the currency account of the determined third user via the currency account of an issuer of the points, and transfers the number of points equivalent to the price of the product, including the owned points of the first user and the points purchased from the third user, to the point account of the second user. Payment device.

2. The payment device according to claim 1, The payment processing unit, If the first user's points are equal to or greater than the price of the product, the normal payment transaction is executed; If the first user's points are less than the price of the product, the payment agent transaction is executed. Payment device.

3. The payment device according to claim 2, The payment processing unit, Even if the first user's owned points are equal to or greater than the price of the product, if the first user selects the payment agency transaction, the payment agency transaction is executed. Payment device.

4. The payment device according to any one of claims 1 to 3, The payment processing unit, in the payment agency transaction, A first pattern in which the points purchased by the first user from the third user are transferred from the point account of the third user to the point account of the second user via the point account of the issuing processing unit; A second pattern in which the points purchased by the first user from the third user are transferred from the point account of the third user to the point account of the second user via the point account of the first user; Or, a third pattern in which the points purchased by the first user from the third user are directly transferred from the point account of the third user to the point account of the second user; Do one of the following: Payment device.

5. The payment device according to any one of claims 1 to 3, the issuance processing unit issues prepaid points to the user, which can be used as a payment means equivalent to the points at a predetermined discount rate, The point management unit manages the expiration date of the prepaid points held by the user. Payment device.

6. The payment device according to claim 5, The prepaid points include crypto assets. Payment device.

7. The payment device according to any one of claims 1 to 3, The settlement processing unit, in the settlement agency transaction, causes the first user to purchase points being sold by the third user in accordance with limit orders or market orders designated by the third user and the first user, respectively. Payment device.

8. The payment device according to any one of claims 1 to 3, a market transaction processing unit that executes buying and selling of the points between users without buying and selling of products; Payment device.

9. The payment device according to claim 8, The market transaction processing unit executes buying and selling of the points between the users in accordance with limit orders or market orders designated by each of the users who buy and sell the points. Payment device.

10. The payment device according to any one of claims 1 to 3, The settlement processing unit deposits currency, with a predetermined settlement / cash exchange fee discounted, into the currency account of the second user in response to the second user transferring the points equivalent to the price of the product. Payment device.

11. The payment device according to any one of claims 1 to 3, a profit and loss management unit that calculates profit and loss for the user's use of the points using a profit and loss calculation formula; a UI control unit that presents the profit and loss to the user; The profit and loss calculation formula is as follows: Profit / loss = Amount of product purchased using points or prepaid points [yen] + Currency purchase amount by exchanging points or prepaid points [yen] + Currency conversion value of points and prepaid points held [yen] - Currency payment amount for prepaid points [yen] - Currency selling amount [yen] Payment device.

12. A payment method using a payment device that manages payments using points as a payment means instead of currency, comprising: an issuing process step of issuing the points to a plurality of users free of charge; a point management step of managing the expiration date, depreciation, and extinction of the points held by each of the users, periodically shortening the expiration date of the points held by each of the users, periodically reducing the number of the points held by each of the users, and extinguishing the points whose expiration date has passed; As a payment process when a first user purchases a product from a second user, a normal settlement transaction for transferring the points equivalent to the price of the product from the point account of the first user to the point account of the second user; a payment processing step of having the first user purchase points sold by a third user and transferring the number of points equivalent to the price of the product to the point account of the second user; The settlement processing step calculates the number of points owned by the first user that is insufficient for the price of the product in the settlement agency transaction, determines one or more third users from among the multiple users selling their owned points by matching based on a desired exchange rate or a market price, transfers currency as payment for purchasing the missing number of points from the determined third user from the currency account of the first user to the currency account of the determined third user via the currency account of an issuer of the points, and transfers the number of points equivalent to the price of the product, including the owned points of the first user and the points purchased from the third user, to the point account of the second user. Payment method.

13. A computer that manages payments using points as a payment method instead of currency, an issuance processing unit that issues the points to a plurality of users free of charge; a point management unit that manages the expiration date, depreciation, and extinction of the points held by each of the users, periodically shortens the expiration date of the points held by each of the users, periodically reduces the number of the points held by each of the users, and extinguishes the points whose expiration date has passed; As a payment process when a first user purchases a product from a second user, a normal settlement transaction for transferring the points equivalent to the price of the product from the point account of the first user to the point account of the second user; a payment processing unit that executes a payment agency transaction in which the first user purchases points sold by a third user and the number of points corresponding to the price of the product is transferred to the point account of the second user; The payment processing unit calculates the number of points that the first user's owned points are short of for the price of the product in the payment agency transaction, determines one or more of the third users from among the multiple users selling their owned points by matching based on a desired exchange rate or market price, transfers currency as payment for purchasing the shortfall in points from the determined third user from the currency account of the first user to the currency account of the determined third user via the currency account of an issuer of the points, and transfers the number of points equivalent to the price of the product, including the owned points of the first user and the points purchased from the third user, to the point account of the second user. program.

Images