Information processing device, information processing method, and information processing program

Abstract

To manage a purpose restriction balance as a balance that can be used in electronic settlement.SOLUTION: An information processing apparatus comprises: a setting unit that sets a purpose restriction balance, in which a purpose is restricted, being different from a normal balance, in which a purpose is not restricted, as a balance being usable in settlement using a terminal device; and a management unit that individually manages the normal balance and the purpose restriction balance. In another point of view, the information processing apparatus comprises: an issuing unit that issues a prepaid card which is applicable for settlement using the terminal device; and a management unit that individually manages a balance of settlement using the terminal device and a balance of the prepaid card.SELECTED DRAWING: Figure 1

Description

Technical Field

[0004] ,

[0006] , , , , , ,

[0005] , , ,

[0003] , If the purpose indicated by the payment information at the time of payment via the payment application of the terminal device matches the purpose of the limited-use balance, the payment processing unit prioritizes payment using the limited-use balance over payment using the regular balance and automatically applies the limited-use balance to process the payment. , , Within the aforementioned payment application, , , ,

[0001] The present invention relates to an information processing apparatus, an information processing method, and an information processing program.

Background Art

[0002] Conventionally, technologies related to digital prepaid cards have been disclosed.

Prior Art Document

Patent Document

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the above conventional technology is merely a mechanism for performing reception processing including payment settlement at a car wash by outputting a QR code (registered trademark) or the like in which not only payment settings but also car wash settings are coded together to the user's application. In order to realize a prepaid card that can be used for payment (electronic payment) using a terminal device, a mechanism for handling a balance dedicated to the prepaid card is required.

[0005] The present application has been made in view of the above, and an object thereof is to manage a balance with limited use as a balance that can be used for electronic payment.

Means for Solving the Problems

[0006] ​​​​​​​​​​​​

[0007] According to one embodiment of the system, a balance with limited use can be managed as a balance that can be used for electronic payments. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is an explanatory diagram showing an overview of the information processing method according to the embodiment. [Figure 2] Figure 2 is an explanatory diagram illustrating the overview of the management of the balance on a prepaid card according to this embodiment. [Figure 3] Figure 3 is an explanatory diagram showing an overview of the application of the prepaid card according to the embodiment. [Figure 4] Figure 4 shows an example of the configuration of an information processing system according to the embodiment. [Figure 5] Figure 5 shows an example of the configuration of a terminal device according to this embodiment. [Figure 6] Figure 6 shows an example of the configuration of a payment server according to the embodiment. [Figure 7] Figure 7 shows an example of a user information database. [Figure 8] Figure 8 shows an example of a historical information database. [Figure 9] Figure 9 shows an example of a card information database. [Figure 10] Figure 10 shows an example of a payment information database. [Figure 11] Figure 11 is a flowchart showing the processing procedure for prepaid card management according to an embodiment. [Figure 12] Figure 12 is a flowchart showing the processing procedure for using a prepaid card according to the embodiment. [Figure 13] Figure 13 shows an example of a hardware configuration. [Modes for carrying out the invention]

[0009] The following describes in detail, with reference to the drawings, embodiments for implementing the information processing device, information processing method, and information processing program according to the present application (hereinafter referred to as "embodiments"). Note that these embodiments do not limit the information processing device, information processing method, and information processing program according to the present application. Furthermore, the same parts are denoted by the same reference numerals in the following embodiments, and redundant descriptions are omitted.

[0010] [1. Overview of Information Processing Methods] First, with reference to Figure 1, an overview of the information processing method performed by the information processing device according to the embodiment will be described. Figure 1 is an explanatory diagram showing an overview of the information processing method according to the embodiment. In Figure 1, the example of managing a balance with limited use as a balance that can be used for electronic payments will be used for the explanation.

[0011] As shown in Figure 1, the information processing system 1 includes a terminal device 10 and a payment server 100. The terminal device 10 and the payment server 100 are connected to each other via a network N (see Figure 4) by wired or wireless means, enabling communication between them. In this embodiment, the terminal device 10 cooperates with the payment server 100. In the following description, an example is shown in which the terminal device 10 is used by a user U. Also, in the following description, the terminal device 10 may be treated as the same as the user U. That is, in the following, user U can be read as terminal device 10.

[0012] The terminal device 10 is a smart device such as a smartphone or a tablet used by the user U, and is a portable terminal device capable of communicating with an arbitrary server device via a wireless communication network such as 4G (Generation) or LTE (Long Term Evolution). Further, the terminal device 10 has a screen such as a liquid crystal display, which has the function of a touch panel, and receives various operations on display data such as content, such as tap operations, slide operations, and scroll operations, from the user using a finger or a stylus. Among the screens, an operation performed on the area where the content is displayed may be regarded as an operation on the content. Further, the terminal device 10 may be not only a smart device but also an information processing device such as a desktop PC (Personal Computer) or a notebook PC.

[0013] The settlement server 100 is an information processing device that manages a balance with limited use as a balance that can be used for electronic settlement, and is realized by a server device, a cloud system, or the like. For example, the settlement server 100 provides an electronic settlement service related to settlement (electronic settlement) using the terminal device 10. Further, the settlement server 100 manages the accounts of the merchants who provide trading targets such as goods and services and the accounts of the users to whom the trading targets are provided, and realizes various settlements by performing transfer of electronic money between the accounts according to the settlement request from the user. Note that the electronic money may be, for example, points or currencies used independently by various companies, or may be a currency provided by a country such as the Japanese yen or the US dollar that can be electronically traded. In the present embodiment, the settlement server 100 separately manages the balance for normal electronic settlement and the balance for payment of each prepaid card in the user's account. That is, the settlement server 100 manages the balance separately for each prepaid card. Actually, the account for each prepaid card may be managed as a purpose-specific account associated with the user's account.

[0014] In this embodiment, the payment server 100 provides services for issuing, managing, and operating prepaid cards. For example, when the user U purchases a prepaid card available at a franchise in the prepaid card sales corner within an application for payment (electronic payment) using the terminal device 10 of the user U (hereinafter, may be simply referred to as the "payment application"), the payment server 100 provides a prepaid card available within the payment application. For example, the payment server 100 provides a prepaid card application as an application (mini-application) launched within the payment application.

[0015] Then, when the user U purchases and uses a desired transaction target (goods, services) at a franchise where the prepaid card can be used, the user U makes a payment (electronic payment) using the terminal device 10 through the payment application. At the time of electronic payment, the payment server 100 automatically applies the remaining recharge amount of the prepaid card to pay the settlement amount of the target goods and services. That is, the remaining recharge amount of the prepaid card is deducted by the amount of the settlement amount of the target goods and services. When the remaining recharge amount of the prepaid card is insufficient, all of the remaining recharge amount of the prepaid card is used, and the amount of the remaining recharge amount is deducted from the settlement amount of the target goods and services.

[0016] This prepaid card is usable at merchants participating in the electronic payment service. In this embodiment, prepaid cards are issued for each participating merchant. For example, prepaid cards are issued for each participating merchant's brand (corporate brand, product brand, etc.). If a participating merchant has multiple brands (e.g., a main brand and sub-brands), prepaid cards may be issued for each individual brand, or a common prepaid card may be issued for all brands within the same participating merchant. Each participating merchant can design its own prepaid card. The user U's terminal device 10 displays the UI (User Interface) of the prepaid card according to the design of each participating merchant. In addition, a premium (bonus) can be added to the prepaid card using funds provided by the participating merchant. For example, user U can purchase a prepaid card with 5,500 yen charged to it by paying 5,000 yen.

[0017] Furthermore, user U can top up their prepaid cards by pressing (tapping or clicking, etc.) the "Charge" button displayed for each prepaid card on the screen that displays a list of the prepaid cards they own.

[0018] Furthermore, this prepaid card can be gifted via person-to-person transfer. In other words, user U can use terminal device 10 to send a prepaid card as a gift to another person. For example, user U can operate terminal device 10 and, on the screen displaying a list of prepaid cards they own, press the "Gift" button displayed for each prepaid card to gift the prepaid card to another user using the person-to-person transfer function of the payment app. If the user already owns the prepaid card when it is gifted, the amount of the gifted prepaid card will be credited to the prepaid card they already own. At this time, the terminal device 10 of the recipient will display a message indicating that a prepaid card has been gifted and information about the giver. For example, the recipient's terminal device 10 will display a message such as, "You have received a □□ prepaid card worth ×× yen as a gift from ○○."

[0019] Furthermore, if user U possesses a prepaid card usable at the participating merchants, it can be used in conjunction with the payment system when making a payment at those merchants. If the payment amount exceeds the charged balance, the payment server 100 prompts the user to choose whether or not to recharge.

[0020] The payment server 100 may also acquire various information about user U. For example, the payment server 100 may acquire information about user U's attributes, such as gender, age, and residential area. The payment server 100 then stores and manages this information about user U's attributes along with identification information (such as user ID) that identifies user U.

[0021] Furthermore, the payment server 100 may obtain various historical information (log data) indicating user U's actions from user U's terminal device 10, or from various servers based on the user ID, etc. For example, the payment server 100 may obtain location history, which is a history of user U's location and date and time, from the terminal device 10. The payment server 100 may also obtain search history, which is a history of search queries entered by user U, from the search server (search engine). The payment server 100 may also obtain browsing history, which is a history of content viewed by user U, from the content server. The payment server 100 may also obtain purchase history, which is a history of user U's product purchases, from the e-commerce server or payment server. The payment server 100 may also obtain listing history and sales history, which are history of user U's listings on the marketplace, from the e-commerce server or payment server. The payment server 100 may also obtain posting history, which is a history of user U's posts, from posting servers that provide review posting services or SNS servers.

[0022] The payment server 100 may recommend the purchase of a prepaid card suitable for user U based on user U's attribute information and the various historical information described above. For example, the payment server 100 may analyze user U's preferences and purchasing tendencies from the various historical information described above to estimate a prepaid card suitable for user U and push a notification to user U's terminal device 10 with a link to the purchase screen for that prepaid card. Alternatively, the payment server 100 may use collaborative filtering to provide information on prepaid cards held by other users with similar attribute information, historical information, or preferences to user U, and push a notification to user U's terminal device 10 with a link to the purchase screen for that prepaid card.

[0023] Alternatively, the payment server 100 may create a prepaid card estimation model (trained model) using machine learning, which takes user U's attribute information as input and outputs an estimated result for a prepaid card suitable for user U. That is, the payment server 100 generates an estimation model using user U's attribute information and the prepaid card user U is using as ground truth data. The payment server 100 then inputs user U's attribute information into the prepaid card estimation model and, based on the outputted prepaid card estimation result, may push a notification to user U's terminal device 10 containing a link to the purchase screen for that prepaid card. In practice, history information may also be input along with user U's attribute information. That is, the payment server 100 may generate an estimation model using user U's attribute information, history information, and the prepaid card user U is using as ground truth data.

[0024] Regarding the creation of a trained model, for example, the payment server 100 creates a trained model that estimates a prepaid card suitable for user U using machine learning with RNN (Recurrent Neural Network) or LSTM (Long Short-Term Memory). Any type and format of model can be used. For example, the payment server 100 may use SVM (Support Vector Machine) or DNN (Deep Neural Network) as the model. Here, DNN may also be CNN (Convolutional Neural Network) or RNN. Furthermore, the model may be a combination of multiple models, such as a model combining CNN and RNN. RNN and LSTM may also be neural networks based on an attention mechanism. The payment server 100 may also use a similar natural language processing model. Additionally, data mining or other machine learning algorithms may be used. The payment server 100 can train the model using the various learning methods described above.

[0025] [1-1. Regarding payment using terminal device 10] Here, prior to describing the information processing according to the embodiment, an example of payment (electronic payment) using the terminal device 10 will be explained. In the following description, an example will be described in which user U makes a payment using the terminal device 10 with a two-dimensional code (QR code®) placed in the store, which is a two-dimensional code indicating store identification information that identifies the store. However, the embodiment is not limited to this. The example of payment described below can also be applied when any user makes a payment at any store using any terminal device 10. Furthermore, the store identification information may be not only a QR code®, but also a barcode, a predetermined mark, a number, etc.

[0026] For example, when user U makes a payment for using or purchasing various goods or services at a store, user U launches a payment application (payment app) installed on terminal device 10. Then, user U takes a picture of the store identification information installed at the store via the payment app. In this case, terminal device 10 displays a screen for entering the price of the payment item and accepts the payment amount from user U or the store employee. Then, terminal device 10 transmits payment information to payment server 100, including user identification information that identifies user U, store identification information (or information indicated by the store identification information, i.e., information indicating the store (e.g., merchant ID)), and the payment amount.

[0027] In such cases, the payment server 100 transfers the amount of electronic money indicated by the payment amount from the account of user U, indicated by the user identification information, to the account of the store, indicated by the store identification information. The payment server 100 then sends a notification to the terminal device 10 that the payment has been completed. In such cases, the terminal device 10 notifies that the payment has been made using electronic money by displaying a screen or outputting a predetermined sound indicating that the payment has been completed.

[0028] It should be noted that payment using terminal device 10 is not limited to the process described above. For example, payment using terminal device 10 may also be made using a store terminal installed in the store. For example, terminal device 10 displays user identification information on its screen to identify user U. In such a case, the store terminal installed in the store reads the user identification information displayed on terminal device 10 and sends payment information to payment server 100, which includes the user identification information (or the information indicated by the user identification information, i.e., information indicating user U (e.g., user ID)), the payment amount, and information identifying the store. In such a case, payment server 100 transfers the amount of electronic money indicated by the payment amount from user U's account, indicated by the user identification information, to the store's account, and may notify the store's store terminal or terminal device 10 that payment has been completed by displaying a screen or a predetermined sound indicating that payment has been completed.

[0029] Furthermore, payment using the terminal device 10 may involve not only transferring electronic money from an account where user U has pre-charged electronic money to the store's account, but also, for example, payment using a credit card that user U has registered in advance. In such a case, for example, the terminal device 10 may transfer the electronic money amount of the payment to the store's account and also bill the credit card company of user U for the payment amount.

[0030] [1-2. Information processing according to the embodiment] As shown in Figure 1, the payment server 100 issues a prepaid card usable within the payment app when user U purchases a prepaid card usable at a merchant in the prepaid card sales section of the payment app for making payments (electronic payments) using user U's terminal device 10 (step S1).

[0031] Next, if user U wants to give a prepaid card as a gift to another user F, they can use terminal device 10 to send the prepaid card as a gift via person-to-person transfer (step S2). Conversely, user U can also receive a prepaid card as a gift from another user F via person-to-person transfer. In other words, prepaid cards can be given as gifts to each other by users. Alternatively, after purchasing a prepaid card, user U may select the prepaid card they own within the payment app and press the "Gift" button to send that prepaid card as a gift to another user F. User U may also purchase a prepaid card with the recipient (sender) set to another user F.

[0032] Next, the terminal device 10 cooperates with the payment server 100 to notify user U of information about the prepaid cards they possess in order to prevent them from forgetting to use their prepaid cards (step S3). For example, based on user U's location information, the terminal device 10 pushes or displays prepaid cards that can be used at stores near user U's location or stores within their range of movement. At this time, the terminal device 10 may push notify or display prepaid cards that can be used at stores if user U is within a predetermined range (e.g., within a radius of 500m) of a store where prepaid cards can be used. The terminal device 10 also pushes or displays prepaid cards that can be used at a store when user U enters a store where prepaid cards can be used. Furthermore, the terminal device 10 may push notify or display prepaid cards that can be used at a store when user U launches a payment application to make a payment (electronic payment) using the terminal device 10. For example, when the payment app is launched in the store, or when the "pay" button on the payment app is pressed, the terminal device 10 may send a push notification or display information about prepaid cards that can be used at that store.

[0033] Next, the terminal device 10 notifies the payment server 100 of information regarding the usage status of the prepaid card held by user U (step S4). For example, if user U purchases and uses a desired transaction item (goods, services) at a merchant where the prepaid card held by user U is accepted, and makes a payment (electronic payment) using the terminal device 10 via the payment application, the terminal device 10 notifies the payment server 100 of the payment information via the network N (see Figure 4) or the merchant's store terminal. Also, if user U gives the prepaid card held by user U as a gift to another user F, the terminal device 10 notifies the payment server 100 that the prepaid card has been transferred from user U to other user F.

[0034] Next, the payment server 100 manages prepaid card information for each user (step S5). Specifically, the payment server 100 manages the balance on the prepaid card for each user. The management of the prepaid card balance is described in detail below.

[0035] [1-3. Managing the balance on prepaid cards] The management of the balance on a prepaid card will be explained below using Figure 2. Figure 2 is an explanatory diagram showing an overview of the management of the balance on a prepaid card according to this embodiment.

[0036] As shown in Figure 2, when a user U purchases a prepaid card created by a merchant (or receives one as a gift), the terminal device 10 and the payment server 100 set up an account or data area to manage a balance specifically for that prepaid card (a balance with limited use), separate from the balance for regular electronic payments. In other words, the balance for regular electronic payments and the balance for the prepaid card are independent. The balance for the prepaid card can be charged in the same way as the balance for regular electronic payments, and it can also be charged from the balance for regular electronic payments. However, it is not possible to charge the balance for regular electronic payments from the balance for the prepaid card.

[0037] Furthermore, the balance for each prepaid card is set individually for each prepaid card. In other words, the balance for each prepaid card is independent. It is not possible to transfer or top up balances between prepaid cards held by the same user. In other words, it is not possible to transfer balances between prepaid cards.

[0038] Furthermore, the balance on a prepaid card can be transferred to other users via person-to-person transfer, just like a regular electronic payment balance. For example, if user U gives prepaid card A as a gift to user F, the entire balance on user U's prepaid card A will be transferred to user F, and that entire amount will be deposited into user F's prepaid card A balance. Also, if user U transfers a predetermined amount from their prepaid card A balance, that predetermined amount will be deposited into user F's prepaid card A balance.

[0039] Furthermore, since prepaid cards are created for each participating merchant, the balance on a prepaid card can be described as the balance specific to the merchant that created it. When a customer uses a prepaid card from the merchant that created it to pay for goods, the payment is made from the balance specific to that prepaid card. For example, if prepaid card A from merchant A is used, the payment is made from the balance specific to prepaid card A.

[0040] Furthermore, prepaid cards can be used not only for payments at the merchant's own stores (e.g., flagship stores, company-owned stores, tenant stores, etc.), but also for purchases of merchant products sold at other retail stores (e.g., mass retailers). For example, if user U purchases products from merchant A, merchant B, and other products at a retail store and makes a payment (electronic payment) using user U's terminal device 10, if user U possesses merchant A's prepaid card A, the payment for merchant A's products will be deducted from the balance on prepaid card A. If user U possesses merchant B's prepaid card B, the payment for merchant B's products will be deducted from the balance on prepaid card B. Payment for other products will be deducted from the balance for regular electronic payments. In other words, payment for products of a specific brand will be deducted from the balance on the prepaid card corresponding to that brand.

[0041] Furthermore, member stores are not limited to brand shops selling apparel, shoes, cosmetics, toys, etc., but may also include retail stores, restaurants, etc. For example, member stores may include convenience stores, supermarkets, drugstores, discount stores, home improvement stores, mass retailers, specialty stores, etc., as well as restaurants, fast food restaurants, coffee chains, cafes, bars, etc. Member stores may also include bookstores, gas stations, etc.

[0042] Furthermore, participating merchants are not limited to stores that handle transactions for which electronic tickets can be used, but may also be facilities where electronic tickets can be used. In practice, these may include large commercial facilities (department stores / shopping centers / outlet malls / underground shopping areas), large leisure facilities (theme parks / amusement parks / game centers / zoos / aquariums / swimming pools / bathing facilities / parks / gardens / landmarks), cultural facilities (halls / theaters / cinemas / art museums / museums), sports facilities (sports fields / baseball fields / tennis courts / gymnasiums / athletic arenas / indoor swimming pools), accommodation facilities (hotels / inns), public transportation (railways / buses / taxi / ships / airlines), train stations and airports, ports (boarding areas), parking lots, etc. They may also include educational institutions such as schools, and medical institutions such as hospitals.

[0043] Furthermore, a merchant may also be a manufacturer of goods. For example, if the goods purchased by a user include goods manufactured by a merchant, the payment server 100 may apply a prepaid card to the payment for those goods. Also, a merchant may be a business that owns a specific product brand. For example, if the goods purchased by a user include goods of a specific product brand, the payment server 100 may apply a prepaid card to the payment for those goods of that brand.

[0044] In other words, the types of businesses that can accept prepaid cards are diverse and include a wide range of businesses.

[0045] [1-4. Regarding the application of prepaid cards] The following explanation of the prepaid card application process performed by the payment server 100 will be given using Figure 3. Figure 3 is an explanatory diagram showing an overview of the prepaid card application according to this embodiment. However, this overview is only one example.

[0046] First, in response to an operation from user U, terminal device 10 launches a payment application pre-installed on the device and displays a screen for user U to purchase a prepaid card in the electronic payment service (step S11). Next, terminal device 10 accepts the user U's operation to purchase a prepaid card (step S12). For example, terminal device 10 accepts the operation to purchase a prepaid card on the screen displayed in step S11 and sends information indicating the prepaid card that was purchased to the payment server 100.

[0047] Furthermore, if user U receives a prepaid card as a gift from another user F, terminal device 10 transmits information indicating the prepaid card received from other user F to payment server 100.

[0048] Next, the payment server 100 receives information (prepaid card ID) from the terminal device 10 indicating the prepaid card used for the purchase (or a prepaid card received from another user) (step S13). Subsequently, the payment server 100 manages the user U and the prepaid card in association (step S14). For example, the payment server 100 manages the user ID of user U and the prepaid card ID received from the terminal device 10 in association.

[0049] Here, in the example shown in Figure 3, let's assume that user U wishes to make the above-mentioned payment to store A, which is performed by the business terminal 200 reading user identification information (user ID). In this case, the business terminal 200 reads the product ID of each product that user U purchases and the user ID of user U displayed on the terminal device 10 (step S15). For example, at the time of payment, the business terminal 200 reads the barcode (product ID) attached to the product using a barcode reader or the like and the user ID displayed on the terminal device 10.

[0050] Next, the payment server 100 receives payment information from the business terminal 200 regarding user U's payment to store A (step S16). For example, the payment server 100 receives payment information from the business terminal 200 that includes the store ID of store A, the product ID read by the business terminal 200 in step S15, the total price of each product associated with the product ID (payment amount), and the user ID of user U.

[0051] Next, the payment server 100 identifies a prepaid card applicable to user U based on the payment information (step S17). For example, the payment server 100 identifies a prepaid card that user U has obtained (purchased or received from another person) by comparing the prepaid card information with the payment information, thereby identifying the prepaid card linked to the store ID indicated by the payment information among the prepaid cards that user U has obtained.

[0052] Next, the payment server 100 executes the payment process based on the payment information and applies the identified prepaid card to complete the payment (step S18). For example, the payment server 100 executes a process to transfer the amount of electronic money indicated by the payment amount from user U's account to store A's account. Then, the payment server 100 applies the identified prepaid card to complete the payment.

[0053] Next, the payment server 100 notifies user U that the prepaid card has been applied (step S18). For example, the payment server 100 displays a payment completion screen C1 on the terminal device 10 indicating that payment to store A has been completed, and notifies the user of information such as the prepaid card applied, the amount used (payment amount) of the prepaid card, and the balance of the prepaid card on the payment completion screen C1.

[0054] As described above, the payment server 100 according to the embodiment identifies a prepaid card applicable to the merchant and applies the identified prepaid card to complete the payment. This allows the payment server 100 according to the embodiment to automatically apply an applicable prepaid card without requiring the user to select a prepaid card. In other words, the payment server 100 according to the embodiment can improve user convenience in the payment process.

[0055] (Prepaid card linked to payment) In this case, in steps S17 and S18, the payment server 100 may acquire merchant information along with payment information and automatically apply a prepaid card that is usable for payment at the merchant from among the prepaid cards held by user U. In other words, a prepaid card is automatically applied in conjunction with payment on a store-by-store (store-by-store) basis.

[0056] (Integrated payment by product) Furthermore, in steps S17 and S18, the payment server 100 may utilize product data in conjunction with the merchant's POS (Point of Sale system) and automatically apply the prepaid card corresponding to the product data. In this case, in step S17, the payment server 100 identifies the prepaid card linked to the product ID indicated by the payment information among the prepaid cards that user U has obtained (purchased or received from another person) by comparing the prepaid card information with the payment information. In practice, it may identify the prepaid card linked to the store ID of the merchant, which is the manufacturer (supplier) of the product corresponding to the product ID indicated by the payment information. It may also identify the prepaid card linked to the product brand, not limited to the corporate brand of the product manufacturer. If user U purchases multiple products, it is sufficient that at least one of the purchased products is eligible for a prepaid card. In other words, the prepaid card is automatically applied in conjunction with the payment on a product-by-product basis.

[0057] (Reading the dedicated code for the installed prepaid card) Alternatively, in step S15, if user U uses the terminal device 10 to scan a two-dimensional code for prepaid card payments (a code specifically for prepaid cards) installed in the store (such as at the cash register), separate from the usual two-dimensional code for electronic payments (QR code®), using the scanning function attached to the prepaid card app, the prepaid card may be used.

[0058] (Presentation of the prepaid card code by the user) Alternatively, in step S15, user U may display a prepaid card-specific code, such as a barcode or 2D code for prepaid card payment, on the terminal device 10 and present it to the store clerk, who will then scan it with the store terminal and use the prepaid card.

[0059] In other words, a prepaid card may only be used if user U actively expresses their intention to use it.

[0060] Furthermore, the automatic application of the prepaid card described above and the reading of the 2D code for prepaid card payment (a code specifically for prepaid cards) may be used in conjunction (they can be used together). For example, if the 2D code for prepaid card payment is not read, the prepaid card may be automatically applied in conjunction with payment (electronic payment) using the terminal device 10.

[0061] (Check for recharge) Furthermore, when processing payment for goods purchased by user U, the payment server 100 may check whether user U should recharge their prepaid card if the balance on the prepaid card is insufficient. For example, the payment server 100 may ask user U whether they want to recharge the prepaid card or pay the insufficient balance using regular electronic payment. Recharging the prepaid card may also be done through payment (electronic payment) using the terminal device 10. In addition, if the prepaid card balance is insufficient and recharging is not performed, the payment server 100 may use the balance for regular electronic payment to pay the insufficient balance on the prepaid card.

[0062] Furthermore, confirmation of prepaid card recharging may be performed upon entering the store. In this case, the terminal device 10 may cooperate with the payment server 100 to identify the store based on location information and identify the prepaid cards that can be used at that store. For example, when user U enters a store where prepaid cards can be used, the terminal device 10 may ask whether or not to recharge if the balance of the prepaid card usable at that store is below a predetermined amount. Alternatively, when user U launches a payment app to make a payment (electronic payment) using the terminal device 10, the terminal device 10 may ask whether or not to recharge if the balance of the prepaid card usable at that store is below a predetermined amount.

[0063] According to this embodiment, the balance of each prepaid card is managed individually and independently of the balance for regular electronic payments, so that an electronic money balance can be secured that is limited to payments at merchants that accept prepaid cards. In addition, since the prepaid card is managed within the payment app and is automatically applied when making a payment using the payment app at a merchant that accepts prepaid cards, no operation is required to use the prepaid card, and the risk of forgetting to use the prepaid card is eliminated, thus improving convenience for the user.

[0064] [2. Example of an information processing system configuration] Next, the configuration of the information processing system 1, which includes the payment server 100 according to the embodiment, will be described using Figure 4. Figure 4 is a diagram showing an example of the configuration of the information processing system 1 according to the embodiment. As shown in Figure 4, the information processing system 1 according to the embodiment includes a terminal device 10 and a payment server 100. These various devices are connected to each other via a network N, either by wire or wireless communication. The network N is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network) such as the Internet.

[0065] Furthermore, the number of devices included in the information processing system 1 shown in Figure 4 is not limited to those illustrated. For example, in Figure 4, only one terminal device 10 is shown for the sake of illustration, but this is merely an example and not limiting; there may be two or more.

[0066] Terminal device 10 is an information processing device used by user U. For example, terminal device 10 may be a smart device such as a smartphone or tablet, a feature phone, a PC (Personal Computer), a PDA (Personal Digital Assistant), a game console with communication capabilities, a car navigation system, a wearable device such as a smartwatch or head-mounted display, or smart glasses.

[0067] Furthermore, the terminal device 10 can connect to the network N via wireless communication networks such as LTE (Long Term Evolution), 4G (4th Generation), and 5G (5th Generation), or via short-range wireless communication such as Bluetooth (registered trademark) and Wi-Fi (Local Area Network), and communicate with the payment server 100.

[0068] Furthermore, the terminal device 10 may also be a store terminal of a member store or a terminal device used by the store's staff (employees), etc. In other words, the store terminal of a member store or a terminal device used by the store's staff may also be the same type of device as the terminal device 10 described above.

[0069] The payment server 100 may be, for example, a PC, a server device, a mainframe, or a workstation. The payment server 100 may also be implemented using cloud computing.

[0070] [3. Example of terminal device configuration] Next, the configuration of the terminal device 10 will be explained using Figure 5. Figure 5 is a diagram showing an example of the configuration of the terminal device 10. As shown in Figure 5, the terminal device 10 comprises a communication unit 11, a display unit 12, an input unit 13, a positioning unit 14, a sensor unit 20, a control unit 30 (controller), and a storage unit 40.

[0071] (Communications Section 11) The communication unit 11 is connected to the network N (see Figure 4) by wire or wireless connection and transmits and receives information to and from the payment server 100 via the network N. For example, the communication unit 11 can be implemented using a NIC (Network Interface Card) or an antenna.

[0072] (Display section 12) The display unit 12 is a display device that displays various information such as location information. For example, the display unit 12 may be a liquid crystal display (LCD) or an organic electro-luminescent display (OLED). The display unit 12 may also be a touch panel display, but is not limited to this.

[0073] (Input section 13) The input unit 13 is an input device that receives various operations from the user U. The input unit 13 also includes, for example, buttons for inputting characters, numbers, etc. Furthermore, if the display unit 12 is a touch panel display, a portion of the display unit 12 functions as the input unit 13. The input unit 13 may also be a microphone or similar device that receives voice input from the user U. The microphone may be wireless.

[0074] (Positioning unit 14) The positioning unit 14 receives signals (radio waves) transmitted from GPS (Global Positioning System) satellites and, based on the received signals, acquires position information (e.g., latitude and longitude) indicating the current position of the terminal device 10. In other words, the positioning unit 14 determines the position of the terminal device 10. Note that GPS is just one example of a GNSS (Global Navigation Satellite System).

[0075] Furthermore, the positioning unit 14 can determine its position using various methods other than GPS. For example, the positioning unit 14 may use various communication functions of the terminal device 10 to determine its position as an auxiliary positioning means for position correction, etc., as described below.

[0076] (Wi-Fi positioning) For example, the positioning unit 14 determines the location of the terminal device 10 by utilizing the Wi-Fi® communication function of the terminal device 10 and the communication network provided by each telecommunications company. Specifically, the positioning unit 14 determines the location of the terminal device 10 by performing Wi-Fi communication, etc., and determining the distance to nearby base stations and access points.

[0077] (Beacon positioning) Furthermore, the positioning unit 14 may determine the location using the Bluetooth® function of the terminal device 10. For example, the positioning unit 14 determines the location of the terminal device 10 by connecting to a beacon transmitter connected via the Bluetooth® function.

[0078] (Geomagnetic positioning) Furthermore, the positioning unit 14 determines the position of the terminal device 10 based on the geomagnetic pattern of the structure, which has been measured in advance, and the geomagnetic sensor provided by the terminal device 10.

[0079] (RFID positioning) Furthermore, if, for example, the terminal device 10 is equipped with an RFID (Radio Frequency Identification) tag function equivalent to that of a contactless IC card used at a train station ticket gate or in a store, or if it is equipped with a function to read RFID tags, the location where it was used will be recorded along with the information on the payment or other transactions made by the terminal device 10. The positioning unit 14 may determine the location of the terminal device 10 by acquiring such information. Alternatively, the location may be determined by an optical sensor or infrared sensor equipped in the terminal device 10.

[0080] The positioning unit 14 may, if necessary, determine the position of the terminal device 10 using one or a combination of the positioning means described above.

[0081] (Sensor unit 20) The sensor unit 20 includes various sensors mounted on or connected to the terminal device 10. The connection can be wired or wireless. For example, the sensors may be detection devices other than the terminal device 10, such as wearable devices or wireless devices. In the example shown in Figure 5, the sensor unit 20 includes an acceleration sensor 21, a gyro sensor 22, a barometric pressure sensor 23, a temperature sensor 24, a sound sensor 25, a light sensor 26, a magnetic sensor 27, and an image sensor (camera) 28.

[0082] The sensors 21-28 described above are merely examples and not limiting. In other words, the sensor unit 20 may be configured to include some of the sensors 21-28, or it may include other sensors such as humidity sensors in addition to or instead of the sensors 21-28.

[0083] The acceleration sensor 21 is, for example, a 3-axis acceleration sensor and detects the physical movement of the terminal device 10, such as its direction of movement, velocity, and acceleration. The gyro sensor 22 detects the physical movement of the terminal device 10, such as its tilt in the three axes, based on its angular velocity. The barometric pressure sensor 23 detects the atmospheric pressure around the terminal device 10, for example.

[0084] Since the terminal device 10 is equipped with the acceleration sensor 21, gyroscope 22, barometric pressure sensor 23, etc., it becomes possible to determine the position of the terminal device 10 using technologies such as pedestrian dead-reckoning (PDR) that utilize these sensors 21 to 23. This makes it possible to obtain indoor location information that is difficult to obtain with positioning systems such as GPS.

[0085] For example, a pedometer using an accelerometer 21 can calculate the number of steps, walking speed, and distance walked. Additionally, a gyroscope 22 can be used to determine the user U's direction of movement, gaze direction, and body tilt. Furthermore, the barometric pressure detected by the barometric pressure sensor 23 can be used to determine the altitude and floor number of the user U's terminal device 10.

[0086] The temperature sensor 24 detects, for example, the ambient temperature around the terminal device 10. The sound sensor 25 detects, for example, the ambient sound around the terminal device 10. The light sensor 26 detects the ambient illumination around the terminal device 10. The magnetic sensor 27 detects, for example, the Earth's magnetic field around the terminal device 10. The image sensor 28 captures an image of the area around the terminal device 10.

[0087] The aforementioned pressure sensor 23, temperature sensor 24, sound sensor 25, light sensor 26, and image sensor 28 can detect the surrounding environment and conditions of the terminal device 10 by detecting atmospheric pressure, temperature, sound, and illuminance, respectively, and by capturing images of the surroundings. Furthermore, it becomes possible to improve the accuracy of the location information of the terminal device 10 based on the surrounding environment and conditions.

[0088] (Control Unit 30) The control unit 30 includes, for example, a microcomputer having a CPU (Central Processing Unit), ROM (Read Only Memory), RAM, input / output ports, and various circuits. Alternatively, the control unit 30 may be composed of hardware such as an integrated circuit (ASIC) or FPGA (Field Programmable Gate Array). The control unit 30 comprises a transmission unit 31, a reception unit 32, and a processing unit 33.

[0089] (Transmitter 31) The transmission unit 31 can transmit various information, such as information input by the user U using the input unit 13, various information detected by sensors 21-28 mounted on or connected to the terminal device 10, and location information of the terminal device 10 determined by the positioning unit 14, to the payment server 100 via the communication unit 11.

[0090] (Receiver 32) The receiving unit 32 can receive various information provided by the payment server 100 and requests for various information from the payment server 100 via the communication unit 11.

[0091] (Processing 33) The processing unit 33 controls the entire terminal device 10, including the display unit 12. For example, the processing unit 33 can output and display various information transmitted by the transmission unit 31 and various information received from the payment server 100 by the reception unit 32 to the display unit 12.

[0092] (Storage unit 40) The storage unit 40 is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or by storage devices such as HDD (Hard Disk Drive), SSD (Solid State Drive), and optical discs. Various programs and various data are stored in this storage unit 40.

[0093] [4. Example of Information Processing Device Configuration] Next, the configuration of the payment server 100 according to the embodiment will be described using Figure 6. Figure 6 is a diagram showing an example of the configuration of the payment server 100 according to the embodiment. As shown in Figure 6, the payment server 100 has a communication unit 110, a storage unit 120, and a control unit 130.

[0094] (Communications Department 110) The communication unit 110 is implemented, for example, by a NIC (Network Interface Card). The communication unit 110 is connected to the network N (see Figure 4) by wire or wireless connection.

[0095] (Storage unit 120) The storage unit 120 is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or by storage devices such as hard disks and optical discs. As shown in Figure 6, the storage unit 120 includes a user information database 121, a history information database 122, a card information database 123, and a payment information database 124.

[0096] (User Information Database 121) The user information database 121 stores various information about user U. For example, the user information database 121 stores various information such as user U's attributes. Figure 7 shows an example of the user information database 121. In the example shown in Figure 7, the user information database 121 has items such as "User ID (Identifier)", "Age", "Gender", "Home", "Workplace", and "Interests".

[0097] "User ID" indicates identification information used to identify user U. "Age" indicates the age of user U identified by the user ID. Note that "Age" may be a specific age of user U identified by the user ID, such as 35 years old. "Gender" indicates the gender of user U identified by the user ID.

[0098] Furthermore, "Home" indicates the location information of user U's home, which is identified by the user ID. In the example shown in Figure 7, "Home" is represented by an abstract code such as "LC11," but it could also be latitude and longitude information, etc. Also, for example, "Home" could be a regional name or address.

[0099] Furthermore, "Workplace" indicates the location information of the workplace (or school in the case of a student) of user U, identified by the user ID. In the example shown in Figure 7, "Workplace" is illustrated with an abstract code such as "LC12," but it may also be latitude and longitude information, etc. Also, for example, "Workplace" may be a regional name or address.

[0100] Furthermore, "Interests" indicate the interests of user U, who is identified by their user ID. In other words, "Interests" indicate the subjects of high interest to user U, who is identified by their user ID. For example, "Interests" may be search queries (keywords) that user U enters into a search engine. In the example shown in Figure 7, one "Interest" is shown for each user U, but there may be multiple interests.

[0101] For example, in the example shown in Figure 7, user U, identified by user ID "U1", is in their 20s and is male. Also, for example, user U, identified by user ID "U1", has their home address at "LC11". Furthermore, for example, user U, identified by user ID "U1", has their workplace at "LC12". Finally, for example, user U, identified by user ID "U1", is interested in "sports".

[0102] In the example shown in Figure 7, abstract values ​​such as "U1," "LC11," and "LC12" are used to illustrate the information, but it is assumed that "U1," "LC11," and "LC12" actually store specific strings, numbers, or other information. In the following diagrams relating to other information, abstract values ​​may also be used to illustrate the information.

[0103] The user information database 121 is not limited to the above and may store various types of information depending on the purpose. For example, the user information database 121 may store various types of information about user U's terminal device 10. In addition, the user information database 121 may store information about user U's demographic, psychographic, geographic, and behavioral attributes. For example, the user information database 121 may store information such as name, family structure, place of origin (hometown), occupation, job title, income, qualifications, type of residence (detached house, apartment, etc.), whether or not a car is owned, commuting time, commuting route, commuter pass section (station, line, etc.), frequently used stations (other than the nearest station to home / workplace), lessons / classes (location, time, etc.), hobbies, interests, and lifestyle.

[0104] (History Information Database 122) The history information database 122 stores various information related to the history information (log data) that shows the user U's actions. Figure 8 shows an example of the history information database 122. In the example shown in Figure 8, the history information database 122 has items such as "User ID", "Location History", "Search History", "Browsing History", "Purchase History", and "Posting History".

[0105] "User ID" indicates identification information used to identify user U. "Location History" indicates the location history, which is the history of user U's location and movements. "Search History" indicates the search history, which is the history of search queries entered by user U. "Browsing History" indicates the browsing history, which is the history of content viewed by user U. "Purchase History" indicates the purchase history, which is the history of purchases made by user U. "Posting History" indicates the posting history, which is the history of posts made by user U. Note that "Posting History" may include questions about user U's possessions.

[0106] For example, in the example shown in Figure 8, user U, identified by user ID "U1", moves as described in "Location History #1", searches as described in "Search History #1", views content as described in "Browsing History #1", purchases specified goods at specified stores as described in "Purchase History #1", and posts as described in "Posting History".

[0107] In the example shown in Figure 8, abstract values ​​such as "U1", "Location History #1", "Search History #1", "Browsing History #1", "Purchase History #1", and "Posting History #1" are used for illustration. However, it is assumed that "U1", "Location History #1", "Search History #1", "Browsing History #1", "Purchase History #1", and "Posting History #1" will actually store specific strings, numbers, and other information.

[0108] The history information database 122 is not limited to the above and may store various types of information depending on the purpose. For example, the history information database 122 may store the usage history of user U for a specified service. The history information database 122 may also store the visit history of user U to a physical store or a facility. The history information database 122 may also store the payment history of user U using electronic payment.

[0109] (Card Information Database 123) The card information database 123 stores various information about the prepaid card. Figure 9 shows an example of the card information database 123. In the example shown in Figure 9, the card information database 123 has items such as "User ID", "Merchant ID", "Card ID", "Account ID", "Balance", "Maximum Amount", and "Expiration Date".

[0110] "User ID" indicates identification information for identifying user U who purchased the prepaid card. "Merchant ID" indicates identification information for identifying the merchant where the prepaid card can be used. Note that the merchant ID may be identification information for identifying a chain store. "Card ID" indicates identification information (prepaid card ID) for identifying the prepaid card held by user U. In this embodiment, prepaid cards are issued for each merchant. "Account ID" indicates identification information for identifying the account linked to the prepaid card. Note that the account ID may be identification information for identifying an account common to multiple prepaid cards. "Balance" indicates the balance of the account linked to the prepaid card. This balance can only be used to purchase goods (or use services) at merchants where the prepaid card can be used. "Maximum Amount" indicates the maximum amount that can be charged to the account linked to the prepaid card. Note that the maximum amount may be a limit set by user U as a daily or monthly usage limit. Furthermore, the "Expiration Date" indicates the expiration date of the prepaid card held by user U. For example, the expiration date is shown as year, month, and day.

[0111] For example, in the example shown in Figure 9, user U, identified by user ID "U1", possesses a card identified by card ID "Card #A" that is usable at the brand identified by merchant ID "Store #A". Furthermore, this card is linked to account ID "Account #A", has a balance of "2,000" yen, a maximum limit of "200,000" yen, and is valid until the expiration date of "2021 / 1 / 21".

[0112] In the example shown in Figure 9, abstract values ​​such as "U1", "Store #A", "Card #A", and "Account #A" are used for illustration, but it is assumed that "U1", "Store #A", "Card #A", and "Account #A" will actually store specific strings, numbers, or other information.

[0113] The card information database 123 may store various types of information depending on the purpose, not limited to those mentioned above. For example, the card information database 123 may store the usage history of user U's prepaid cards. The card information database 123 may also store information about prepaid cards that user U has purchased in the past (for example, prepaid card purchase history). Furthermore, the card information database 123 may store information about benefits (bonuses, premiums, etc.) that are based on the frequency of use and number of purchases of user U's prepaid cards.

[0114] (Payment Information Database 124) The payment information database 124 stores various information related to payments (electronic payments) made using the terminal device 10. Figure 10 shows an example of the payment information database 124. In the example shown in Figure 10, the payment information database 124 has items such as "User ID", "Store ID", "Transaction Target ID", "Unit Price", "Quantity", "Card ID", "Amount Used", and "Payment Amount".

[0115] The "User ID" indicates identification information for identifying user U who used a prepaid card in a payment (electronic payment) using terminal device 10. The "Store ID" indicates identification information for identifying the merchant (store) where the prepaid card was used in a payment (electronic payment) using terminal device 10. Note that the Store ID may be identification information for identifying a chain store. The "Transaction Target ID" indicates identification information for identifying the transaction target, such as goods or services, that are eligible for the prepaid card in a payment (electronic payment) using terminal device 10. The "Unit Price" indicates the unit price of the transaction target, such as goods or services, that are eligible for the prepaid card. The "Quantity" indicates the quantity of the transaction target, such as goods or services, that are eligible for the prepaid card. In other words, the quantity indicates the number of items (number of purchases) of goods eligible for the prepaid card, the number of times the service has been used, etc.

[0116] Furthermore, "Card ID" indicates identification information used to identify the prepaid card used by user U. "Amount Used" indicates the amount used on the prepaid card in a payment (electronic payment) using terminal device 10. For example, if the balance on the prepaid card is greater than the total amount of the transactions subject to payment, the amount used will be equal to the total amount of the transactions. If the balance on the prepaid card is less than the total amount of the transactions subject to payment, the amount used will be the entire balance on the prepaid card. Additionally, the user may be given the option to either recharge the prepaid card or pay the remaining amount using regular electronic payment. "Payment Amount" indicates the payment amount after using the prepaid card. For transactions where a prepaid card can be used, using the prepaid card makes the transaction free (0 yen).

[0117] For example, in the example shown in Figure 10, user U, identified by user ID "U1", purchased only one unit of the transaction item identified by transaction item ID "transaction item #A1" at the store identified by store ID "store #A", at a unit price of "1,200" yen. Furthermore, user U used a prepaid card identified by card ID "card #A" for the above transaction item, with a transaction amount of "1,200" yen, resulting in a settlement amount of "0" yen.

[0118] In the example shown in Figure 10, abstract values ​​such as "U1", "Store #A", "Transaction Target #A1", and "Card #A" are used for illustration, but it is assumed that "U1", "Store #A", "Transaction Target #A1", and "Card #A" will actually store specific strings, numbers, or other information.

[0119] The payment information database 124 is not limited to the above and may store various types of information depending on the purpose. For example, the payment information database 124 may store identification information for identifying payment methods such as payments using the terminal device 10 (electronic payments) and payment service providers.

[0120] Furthermore, the transaction history database 122, the card information database 123, and the payment information database 124 may be linked to or integrated with the user information database 121. For example, the user information database 121, the transaction history database 122, the card information database 123, and the payment information database 124 may be relational databases (RDBs).

[0121] (Control unit 130) Returning to Figure 6, let's continue the explanation. The control unit 130 is a controller, and is realized by various programs (corresponding to an example of an information processing program) stored in the internal memory of the payment server 100, which are executed using a memory area such as RAM as the working area, by means of a CPU (Central Processing Unit), MPU (Micro Processing Unit), ASIC (Application Specific Integrated Circuit), FPGA (Field Programmable Gate Array), etc. In the example shown in Figure 6, the control unit 130 has an acquisition unit 131, an issuance unit 132, a setting unit 133, a management unit 134, a payment processing unit 135, an estimation unit 136, and a provision unit 137.

[0122] (Acquisition part 131) The acquisition unit 131 acquires various information about user U via the communication unit 110. For example, based on information indicating user U using the payment app (such as user ID), the acquisition unit 131 acquires user U's location information, user U's attribute information, etc. Then, the acquisition unit 131 registers this information in the user information database 121 of the storage unit 120.

[0123] Furthermore, the acquisition unit 131 acquires various historical information (log data) indicating the user U's actions via the communication unit 110. The acquisition unit 131 then registers this information in the historical information database 122 of the storage unit 120.

[0124] Furthermore, the acquisition unit 131 receives requests from user U via the communication unit 110 for the purchase (issuance), charging, and provision (gift) of prepaid cards. For example, if user U performs an operation to purchase a prepaid card for a desired transaction (goods, services) at a desired store in the prepaid card sales section of the payment app, the acquisition unit 131 accepts this as a prepaid card purchase request. Also, if user U performs an operation within the payment app to charge the balance of a prepaid card by specifying an amount, the acquisition unit 131 charges the balance of the prepaid card by the amount specified by user U. In addition, if user U specifies someone other than themselves as the recipient when purchasing a prepaid card, or performs an operation to transfer a prepaid card to someone else after purchasing it, the acquisition unit 131 accepts this as a prepaid card provision request (gift request). In other words, the acquisition unit 131 also functions as a reception unit that accepts requests for the purchase (issuance), charging, and provision (gift) of prepaid cards.

[0125] (Publishing Section 132) The issuing unit 132 issues a prepaid card in response to a purchase request (issuance request) from user U. For example, the issuing unit 132 issues a prepaid card to user U in the prepaid card sales section of the payment app. At this time, the issuing unit 132 issues a prepaid card that is linked to payment (electronic payment) using the terminal device 10. From another perspective, the issuing unit 132 issues a prepaid card that can be used for payment (electronic payment) using the terminal device 10. Furthermore, the issuing unit 132 issues a prepaid card for each merchant. For example, the issuing unit 132 issues a prepaid card for each corporate brand. The issuing unit 132 may also issue a prepaid card for each product brand.

[0126] (Settings section 133) The configuration unit 133 sets a usage-restricted balance, separate from the regular balance which has no restrictions on its use, as a balance that can be used for payments using the terminal device. In this case, the configuration unit 133 sets usage-restricted balances for each use. Furthermore, the configuration unit 133 sets a usage-restricted balance for each merchant of the payment service. Furthermore, the configuration unit 133 sets a usage-restricted balance for each user U.

[0127] Furthermore, the setting unit 133 sets a balance specifically for the prepaid card when the prepaid card is issued. Since prepaid cards are issued by each merchant, it can be said that the setting unit 133 sets a balance that is exclusive to each merchant. For example, if prepaid cards are issued for each company brand, the setting unit 133 sets a balance that is exclusive to that company brand. Also, if prepaid cards are issued for each product brand, the setting unit 133 may set a balance that is exclusive to that product brand.

[0128] The setting unit 133 may be linked to the issuing unit 132 or the management unit 134, or it may be integrated with the issuing unit 132 or the management unit 134. In other words, the setting unit 133 may be part of the functions of the issuing unit 132 or the management unit 134. For example, the issuing unit 132 may set a balance specifically for the prepaid card when it issues a prepaid card. The management unit 134 may also set a balance specifically for the prepaid card when it starts managing the prepaid card.

[0129] (Management Department 134) The management unit 134 separately manages both a general balance (unrestricted use) and a restricted-use balance as balances available for payment using terminal devices. In this case, the management unit 134 separately manages the restricted-use balances set for each purpose. Furthermore, the management unit 134 separately manages the restricted-use balances set for each merchant. For example, the management unit 134 separately manages the corporate brand-specific balances set for each corporate brand. Furthermore, the management unit 134 separately manages the product brand-specific balances set for each product brand. Furthermore, the management unit 134 separately manages the restricted-use balances set for each user U.

[0130] Furthermore, if user U uses the person-to-person transfer function to transfer a predetermined amount from user U's limited-use balance to another user F, the management unit 134 transfers the transferred amount to the limited-use balance of other user F corresponding to user U's limited-use balance.

[0131] Furthermore, the management unit 134 manages the limited-use balance and the prepaid card in a linked manner, and when user U transfers the prepaid card to another user F, the entire amount of the limited-use balance linked to the prepaid card is transferred from user U's limited-use balance to user F's limited-use balance.

[0132] Furthermore, the management unit 134 manages the prepaid cards held by user U. For example, the management unit 134 manages the prepaid cards issued by the issuing unit 132 to user U. In addition, the management unit 134 manages the balance (limited-use balance) of the prepaid cards. At this time, the management unit 134 separately manages the balance of payments made using the terminal device 10 (electronic payment) and the balance of the prepaid cards. That is, the management unit 134 separately manages the balance for payments made using regular electronic payment and the balance for payments made using prepaid cards. Furthermore, the management unit 134 separately manages the balance of prepaid cards for each merchant. That is, the management unit 134 separately manages the balance for each prepaid card.

[0133] Furthermore, the management unit 134 determines whether or not a prepaid card is applicable to the transaction subject to settlement when the settlement processing unit 135 processes the settlement. That is, the management unit 134 works in conjunction with the settlement processing unit 135 to apply the prepaid card to the transaction subject to settlement. In practice, the settlement processing unit 135 may work in conjunction with the management unit 134 to apply the prepaid card to the transaction subject to settlement. In addition, if a prepaid card is applied to the transaction subject to settlement, the management unit 134 manages the balance of the prepaid card. The management unit 134 also manages the expiration date of the prepaid card.

[0134] Furthermore, if user U of terminal device 10 transfers a prepaid card owned by user U to another user using the person-to-person transfer function of the payment app, the management unit 134 changes the owner of the prepaid card from user U to the other user and transfers the balance of the prepaid card from user U to the other user. In other words, when a prepaid card is gifted from user U to another user, the management unit 134 transfers the balance of the prepaid card from user U's account to the other user's account. In practice, the management unit 134 may also transfer the account linked to the prepaid card itself from user U to the other user. Note that in the above explanation, user U and the other user may be swapped. Note that if user U already owns the same prepaid card as the one transferred from user U, the management unit 134 may add the balance of the transferred prepaid card to the balance of the prepaid card that user U already owns. Alternatively, you may manage the balances of prepaid cards you already own and the balances of transferred prepaid cards separately.

[0135] (Payment processing unit 135) The payment processing unit 135 processes the payment when user U makes a payment (electronic payment) using the terminal device 10 via a payment application. For example, the payment processing unit 135 processes the payment by transferring electronic money from user U's account to the merchant's account in accordance with the payment request from user U.

[0136] In this embodiment, when a user U purchases and uses a transaction item (goods, services) at a store that accepts prepaid cards, the payment processing unit 135 applies the prepaid card and processes the payment when the user makes a payment (electronic payment) using the terminal device 10 via a payment application. In other words, when a payment is made at a merchant, the payment processing unit 135 processes the payment using the balance of the prepaid card corresponding to the merchant.

[0137] At this time, the payment processing unit 135 acquires store information indicating the store when payment is made using the terminal device 10, and automatically applies a prepaid card that is usable at that store from among the prepaid cards held by user U.

[0138] Alternatively, when a payment (electronic payment) is made using the terminal device 10 and a prepaid card is used by the user U, the payment processing unit 135 applies the prepaid card and processes the payment. For example, when a payment is made using the terminal device 10, if the terminal device 10 reads a prepaid card-specific code for using a prepaid card installed in the store, the payment processing unit 135 applies the prepaid card and processes the payment. Alternatively, when a payment is made using the terminal device 10, if the store terminal reads a prepaid card-specific code for using a prepaid card displayed on the terminal device 10, the payment processing unit 135 applies the prepaid card and processes the payment.

[0139] Furthermore, when payment is made at a merchant, if the balance on the prepaid card corresponding to the merchant is insufficient, the payment processing unit 135 will charge the balance on the prepaid card from the balance used for payments via the terminal device 10 and process the payment. Alternatively, when payment is made at a merchant, if the balance on the prepaid card corresponding to the merchant is insufficient, the payment processing unit 135 will process the payment using the balance used for payments via the terminal device 10. In addition, if the balance on the prepaid card is insufficient, the payment processing unit 135 may either recharge the card or pay the insufficient amount through regular electronic payment, or it may inquire with the user U and perform recharging or regular electronic payment after obtaining permission, or it may perform recharging or regular electronic payment automatically.

[0140] In other words, when the settlement processing unit 135 is settling a payment for a specific purpose, if the balance in the limited-use balance is insufficient, it will charge the limited-use balance from the normal balance and then process the payment. Alternatively, when the settlement processing unit 135 is settling a payment for a specific purpose, if the balance in the limited-use balance is insufficient, it will use the normal balance to process the payment.

[0141] (Estimation part 136) The estimation unit 136 estimates a prepaid card suitable for user U based on user U's attribute information and various historical information. For example, the estimation unit 136 creates a prepaid card estimation model (trained model) that outputs information indicating a prepaid card suitable for user U when user U's attribute information and historical information are input. Then, the estimation unit 136 inputs user U's attribute information and various historical information into the prepaid card estimation model and estimates a prepaid card suitable for user U based on the output information.

[0142] For example, the estimation unit 136 creates a trained model that estimates a prepaid card suitable for user U using machine learning such as RNN (Recurrent Neural Network) or LSTM (Long Short-Term Memory). The model can be of any type and format. For example, the estimation unit 136 may use SVM (Support Vector Machine) or DNN (Deep Neural Network) as its model. Here, DNN may be a CNN (Convolutional Neural Network) or an RNN. Furthermore, the model may be a combination of multiple models, such as a model combining a CNN and an RNN.

[0143] Furthermore, RNNs and LSTMs may be neural networks based on the attention mechanism. The estimation unit 136 may also use a similar natural language processing model. Additionally, data mining and other machine learning algorithms may be utilized. The estimation unit 136 can train the model using the various learning methods described above.

[0144] (Providing Department 137) The provision unit 137 provides information about a prepaid card suitable for user U to user U's terminal device 10 via the communication unit 110. For example, it prioritizes listing a prepaid card suitable for user U, as estimated by the estimation unit 136, in the prepaid card sales section of the payment app used by user U. Alternatively, the provision unit 137 provides a link to the purchase screen of the prepaid card suitable for user U, as estimated by the estimation unit 136, to user U's terminal device 10 via push notification.

[0145] The timing at which the provision unit 137 provides information about a prepaid card suitable for user U may be when user U enters a store where the prepaid card can be used, or when user U purchases or uses the desired transaction item (goods, services) a predetermined number of times at a merchant where the prepaid card can be used. The predetermined number of times may be one or multiple times.

[0146] Furthermore, if a prepaid card is gifted (transferred) by user U to another user, the provision unit 137 notifies the other user that the prepaid card has been transferred from user U. For example, the provision unit 137 notifies the other user's terminal device 10 of information about user U who transferred the prepaid card and information about the transferred prepaid card.

[0147] Furthermore, the provision unit 137 notifies user U of information regarding the prepaid card they possess at predetermined times to prevent them from forgetting to use the prepaid card. In other words, the provision unit 137 also functions as a notification unit that notifies the user of the existence of the prepaid card in order to encourage its use.

[0148] For example, the provision unit 137 notifies the terminal device 10 of prepaid cards that can be used at stores near user U's location or stores within its range of movement, based on user U's location information. In addition, when user U enters a store where prepaid cards can be used, the provision unit 137 notifies the terminal device 10 of prepaid cards that can be used at that store.

[0149] Furthermore, when the expiration date of a prepaid card approaches, the supply unit 137 notifies the terminal device 10 of the prepaid card and its expiration date at a predetermined time, such as two weeks before the expiration date. In other words, the supply unit 137 also functions as an expiration date notification unit that notifies the expiration date of a prepaid card.

[0150] In practice, the provisioning unit 137 may also notify the terminal device 10 of information regarding the prepaid card held by user U in response to a request from the terminal device 10. For example, when the terminal device 10 detects user U approaching, entering, or making a payment at a merchant, it notifies the payment server 10 of the location information. The provisioning unit 137 of the payment server 100 then identifies the merchant based on the location information from the terminal device 10 and notifies the terminal device 10 of information regarding prepaid cards that can be used at that merchant.

[0151] [5. Processing Procedure] Next, the processing procedure by the terminal device 10 and payment server 100 according to the embodiment will be described using Figures 11 and 12. [5-1. Prepaid Card Management Processing Procedure] First, the processing procedure for prepaid card management according to the embodiment will be explained using Figure 11. Figure 11 is a flowchart of the processing procedure for prepaid card management according to the embodiment. The processing procedure shown below is repeatedly executed by the control unit 30 of the terminal device 10 and the control unit 130 of the payment server 100.

[0152] As shown in Figure 11, the acquisition unit 131 of the payment server 100 acquires a prepaid card purchase request (issuance request) from user U via the communication unit 110 (step S101).

[0153] Next, the issuing unit 132 of the payment server 100 issues a prepaid card in response to a prepaid card purchase request from user U (step S102). For example, when a user purchases a prepaid card from the prepaid card sales corner in the payment app using payment (electronic payment) via the terminal device 10, the issuing unit 132 issues a prepaid card. At this time, the issuing unit 132 issues a prepaid card that is linked to payment (electronic payment) using the terminal device 10. From another perspective, the issuing unit 132 issues a prepaid card that can be used for payment (electronic payment) using the terminal device 10.

[0154] Next, the management unit 134 of the payment server 100 reserves an area for the prepaid card balance (step S103). Here, the management unit 134 sets up an account or data area for managing the prepaid card balance (usage-limited balance), separate from the balance for regular electronic payments. In other words, the balance for regular electronic payments and the balance for prepaid cards are independent. Furthermore, the balance for prepaid cards is set for each prepaid card. That is, the balance for prepaid cards is independent for each prepaid card.

[0155] Next, the management unit 134 of the payment server 100 manages the prepaid card held by user U (step S104). Here, the management unit 134 manages the prepaid card by linking it to user U.

[0156] Next, the management unit 134 of the payment server 100 determines whether or not user U received the prepaid card from another person (step S105). That is, the management unit 134 determines whether or not user U received the prepaid card as a gift from another person.

[0157] If user U is transferred a prepaid card from another person (step S105; Yes), the management unit 134 of the payment server 100 reserves an area for the balance of that prepaid card (returns to step S103) and also manages the prepaid card that user U was transferred to (step S104). If user U already possesses the same prepaid card as the one that was transferred, the management unit 134 may add the balance of the transferred prepaid card to the balance of the prepaid card that user U already possesses. Conversely, if user U has not been transferred a prepaid card from another person (step S105; No), the management unit 134 of the payment server 100 proceeds to the next process (progresses to step S106).

[0158] Next, the management unit 134 of the payment server 100 determines whether user U of the terminal device 10 has transferred a prepaid card owned by user U to another user using the person-to-person transfer function of the payment application (step S106). For example, the management unit 134 determines whether user U operated the terminal device 10 and pressed the "Gift" button displayed for each prepaid card on the screen that displays a list of prepaid cards owned by user U. If user U has not transferred a prepaid card owned by user U to another user (step S106; No), the management unit 134 of the payment server 100 continues to manage the prepaid card owned by user U and terminates the series of processes.

[0159] If user U of terminal device 10 transfers a prepaid card owned by user U to another user using the person-to-person transfer function of the payment application (step S106; Yes), the management unit 134 of the payment server 100 changes the owner of the prepaid card from user U to the other user and transfers the balance of the prepaid card from user U to the other user (step S107).

[0160] Next, the management unit 134 of the payment server 100 releases the area of ​​the prepaid card balance that was transferred to another user (step S108). Then, the series of processes ends.

[0161] [5-2. Procedure for using a prepaid card] Next, the processing procedure for using a prepaid card according to the embodiment will be explained using Figure 12. Figure 12 is a flowchart of the processing procedure for using a prepaid card according to the embodiment. Note that the processing procedure shown below is repeatedly executed by the control unit 30 of the terminal device 10 and the control unit 130 of the payment server 100.

[0162] As shown in Figure 12, the provision unit 137 of the payment server 100 notifies user U of information regarding prepaid cards held by the user U in order to prevent the user U from forgetting to use the prepaid card (step S111). For example, based on user U's location information, the provision unit 137 notifies the terminal device 10 of prepaid cards that can be used at stores near user U's location or stores within their range of movement. The provision unit 137 also notifies the terminal device 10 of prepaid cards that can be used at a store when user U enters a store where prepaid cards can be used. Furthermore, when user U launches a payment application to make a payment (electronic payment) using the terminal device 10, the terminal device 10 is notified of prepaid cards that can be used at that store. In addition, when the expiration date of a prepaid card is approaching, the provision unit 137 notifies the terminal device 10 of the prepaid card and its expiration date at a predetermined timing, such as two weeks before the expiration date.

[0163] Next, the payment processing unit 135 of the payment server 100 determines whether or not user U will make a payment related to the merchant (step S112). For example, the payment processing unit 135 determines whether or not user U will visit a store of a merchant that accepts prepaid cards and make a payment (electronic payment) using the terminal device 10 at that store. The payment processing unit 135, or the payment processing unit 135, determines whether or not the goods purchased by user U are goods of the merchant when the user makes a payment (electronic payment) using the terminal device 10. In practice, this is not limited to the purchase of goods, but may also include the use of services at the store. Here, if user U does not make a payment related to the merchant (step S112; No), the payment processing unit 135 of the payment server 100 does not apply the prepaid card and performs a normal payment process using the balance for normal electronic payments (step S113).

[0164] Next, the payment processing unit 135 of the payment server 100 determines whether the balance on the merchant's prepaid card is insufficient when user U makes a payment to the merchant (step S112; Yes) (step S114). If the balance on the merchant's prepaid card is sufficient (step S114; No), the payment processing unit 135 of the payment server 100 applies the merchant's prepaid card to the payment to the merchant and processes the payment using the balance on the merchant's prepaid card (step S115).

[0165] Conversely, if the balance on the merchant's prepaid card is insufficient (step S114; Yes), the payment processing unit 135 of the payment server 100 inquires with the user U to confirm whether or not to recharge the merchant's prepaid card (step S116).

[0166] If the merchant does not recharge their prepaid card (step S116; No), the payment processing unit 135 of the payment server 100 does not apply the prepaid card to the payment for the merchant and instead uses the balance for regular electronic payments to perform the normal payment processing (step S113).

[0167] Conversely, if the payment processing unit 135 of the payment server 100 recharges a merchant's prepaid card (step S116; Yes), it applies the merchant's prepaid card to the payment related to the merchant and processes the payment using the balance of the merchant's prepaid card (step S115).

[0168] [6. Variant Example] The terminal device 10 and payment server 100 described above may be implemented in various different forms other than those of the embodiment described above. Therefore, the following describes modifications of the embodiment.

[0169] In the above embodiment, some or all of the processing performed by the payment server 100 may actually be performed by the terminal device 10. For example, the processing may be completed in a standalone manner (by the terminal device 10 alone). In this case, the terminal device 10 is assumed to be equipped with the functions of the payment server 100 in the above embodiment. Furthermore, in the above embodiment, since the terminal device 10 is in cooperation with the payment server 100, from the perspective of the user U, it appears as if the processing of the payment server 100 is also being performed by the terminal device 10. In other words, from another perspective, it can be said that the terminal device 10 is equipped with the payment server 100.

[0170] Furthermore, in the above embodiment, when the terminal device 10 displays a list of prepaid cards owned by user U, it may automatically sort the prepaid cards owned by user U in order of frequency of use or in order of approaching expiration date. Alternatively, the terminal device 10 may sort the prepaid cards owned by user U in response to user U's actions.

[0171] Furthermore, in the above embodiment, when the terminal device 10 displays a list of prepaid cards owned by user U, it may display only the prepaid cards owned by user U that meet the predetermined conditions selected and specified by user U.

[0172] Furthermore, in the above embodiment, user U may give a prepaid card that was gifted to him by another user as a gift to yet another user. In other words, once a prepaid card gifted to user U becomes a prepaid card owned by user U, user U can then freely give it as a gift to other users.

[0173] Furthermore, in the above embodiment, the prepaid card limited to participating merchants is merely one example. In practice, the prepaid card may be managed in conjunction with a specific use rather than being linked to a participating merchant.

[0174] [7. Effects] As described above, the information processing device (terminal device 10 or settlement server 100) according to the present invention includes a setting unit 133 that sets a usage-limited balance in addition to a normal balance that is not limited in use, as a balance that can be used for settlement using the terminal device 10, and a management unit 134 that manages the normal balance and the usage-limited balance separately.

[0175] Furthermore, the setting unit 133 sets purpose-specific balances for each use. The management unit 134 then individually manages the purpose-specific balances that have been set for each use.

[0176] Furthermore, the settings unit 133 sets a limited-use balance for each merchant of the payment service. The management unit 134 then individually manages the limited-use balance set for each merchant.

[0177] Furthermore, the setting unit 133 sets a limited-use balance for each user U. The management unit 134 then individually manages the limited-use balance set for each user U.

[0178] Furthermore, if user U uses the person-to-person transfer function to transfer a predetermined amount from user U's limited-use balance to another user F, the management unit 134 transfers the transferred amount to the limited-use balance of other user F corresponding to user U's limited-use balance.

[0179] Furthermore, the management unit 134 manages the limited-use balance and the prepaid card in a linked manner, and when user U transfers the prepaid card to another user F, the entire amount of the limited-use balance linked to the prepaid card is transferred from user U's limited-use balance to user F's limited-use balance.

[0180] Furthermore, the information processing device according to the present application further comprises a settlement processing unit that, when settling for a particular use, charges the limited-use balance from the normal balance and performs settlement processing if the balance of the limited-use balance is insufficient.

[0181] Alternatively, the information processing device according to the present application further comprises a settlement processing unit that, when settling for a use, uses the normal balance to perform settlement processing if the balance of the limited-use balance is insufficient.

[0182] From another perspective, the information processing device (terminal device 10 or payment server 100) according to the present invention includes a setting unit 133 that sets a merchant-limited balance that is limited to certain merchants, in addition to a normal balance that is not limited to any merchant, as a balance that can be used for payments using the terminal device 10, and a management unit 134 that manages the normal balance and the merchant-limited balance separately.

[0183] From another perspective, the information processing device (terminal device 10 or settlement server 100) according to the present invention includes a setting unit 133 that sets a corporate brand-limited balance, which limits the corporate brands that can be used, in addition to a normal balance that does not limit the corporate brands that can be used, as a balance that can be used for settlement using the terminal device 10, and a management unit 134 that manages the normal balance and the corporate brand-limited balance separately.

[0184] From another perspective, the information processing device (terminal device 10 or payment server 100) according to the present invention includes a setting unit 133 that sets a product brand-limited balance, which limits the product brands that can be used, in addition to a normal balance that does not limit the product brands that can be used, as a balance that can be used for payment using the terminal device 10, and a management unit 134 that manages the normal balance and the product brand-limited balance separately.

[0185] Furthermore, from another perspective, the information processing device (terminal device 10 or payment server 100) according to the present application includes an issuing unit 132 that issues a prepaid card linked to payment using the terminal device 10, and a management unit 134 that separately manages the balance of the payment using the terminal device 10 and the balance of the prepaid card.

[0186] Furthermore, the issuing unit 132 issues prepaid cards to each participating store. The management unit 134 then individually manages the balance of each prepaid card for each participating store.

[0187] Furthermore, the information processing device according to the present invention further comprises a settlement processing unit 135 that performs settlement processing using the balance of a prepaid card corresponding to the merchant when a settlement is made at a merchant.

[0188] Furthermore, when a payment is made at a merchant, if the balance on the prepaid card corresponding to the merchant is insufficient, the payment processing unit 135 will charge the balance on the prepaid card from the balance used for payment via the terminal device 10 and then process the payment.

[0189] Alternatively, if the balance on the prepaid card corresponding to the merchant is insufficient when making a payment at a merchant, the payment processing unit 135 will use the balance for payment using the terminal device 10 to process the payment.

[0190] Furthermore, if user U of terminal device 10 uses the person-to-person transfer function to transfer a prepaid card owned by user U to another user, the management department will change the ownership of the prepaid card from user U to the other user and transfer the balance of the prepaid card from user U to the other user.

[0191] Furthermore, the information processing device according to the present invention further includes a notification unit that notifies the terminal device 10 of the prepaid cards that can be used at the store when user U enters a store where prepaid cards can be used.

[0192] Through any or a combination of the above-described processes, the information processing device according to this application can manage a limited-use balance that can be used for electronic payments. This makes it possible to provide a prepaid card that can only be used at merchants that are members of the electronic payment service. Furthermore, it can be used in conjunction with payments when making a payment at a merchant that holds the prepaid card. In addition, users can be given the option to recharge if the payment exceeds the charged balance. Furthermore, a UI for My Prepaid Card with a design unique to the merchant can be provided. Furthermore, a premium can be added using the merchant's own funds. Moreover, the prepaid card can be given as a gift via person-to-person transfer.

[0193] [8. Hardware Configuration] Furthermore, the terminal device 10 and payment server 100 according to the above-described embodiment are implemented by a computer 1000 having a configuration such as that shown in Figure 13. The following explanation will use the payment server 100 as an example. Figure 13 is a diagram showing an example of the hardware configuration. The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which an arithmetic unit 1030, a primary storage device 1040, a secondary storage device 1050, an output interface 1060, an input interface 1070, and a network interface 1080 are connected by a bus 1090.

[0194] The arithmetic unit 1030 operates based on programs stored in the primary storage device 1040 and the secondary storage device 1050, as well as programs read from the input device 1020, and executes various processes. The arithmetic unit 1030 can be implemented using, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), an ASIC (Application Specific Integrated Circuit), or an FPGA (Field Programmable Gate Array).

[0195] The primary storage device 1040 is a memory device, such as RAM (Random Access Memory), that temporarily stores data used by the arithmetic unit 1030 for various calculations. The secondary storage device 1050 is a storage device where data used by the arithmetic unit 1030 for various calculations and various databases are registered, and can be implemented using ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, etc. The secondary storage device 1050 may be internal storage or external storage. The secondary storage device 1050 may also be a removable storage medium such as a USB memory stick or an SD (Secure Digital) memory card. Furthermore, the secondary storage device 1050 may be cloud storage (online storage), NAS (Network Attached Storage), a file server, etc.

[0196] The output I / F 1060 is an interface for transmitting information to be output to output devices 1010, such as displays, projectors, and printers, and is implemented using connectors of standards such as USB (Universal Serial Bus), DVI (Digital Visual Interface), and HDMI (High Definition Multimedia Interface). The input I / F 1070 is an interface for receiving information from various input devices 1020, such as mice, keyboards, keypads, buttons, and scanners, and is implemented using, for example, USB.

[0197] Furthermore, the output interface 1060 and input interface 1070 may be wirelessly connected to the output device 1010 and input device 1020, respectively. In other words, the output device 1010 and input device 1020 may be wireless devices.

[0198] Furthermore, the output device 1010 and the input device 1020 may be integrated as a touch panel. In this case, the output I / F 1060 and the input I / F 1070 may also be integrated as an input / output I / F.

[0199] The input device 1020 may also be a device that reads information from, for example, an optical recording medium such as a CD (Compact Disc), DVD (Digital Versatile Disc), or PD (Phase Change Rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0200] The network interface 1080 receives data from other devices via network N and sends it to the computing unit 1030, and also transmits data generated by the computing unit 1030 to other devices via network N.

[0201] The arithmetic unit 1030 controls the output device 1010 and the input device 1020 via the output interface 1060 and the input interface 1070. For example, the arithmetic unit 1030 loads a program from the input device 1020 or the secondary storage device 1050 onto the primary storage device 1040 and executes the loaded program.

[0202] For example, if computer 1000 functions as a payment server 100, the arithmetic unit 1030 of computer 1000 implements the functions of the control unit 130 by executing a program loaded onto the primary storage device 1040. Alternatively, the arithmetic unit 1030 of computer 1000 may load a program obtained from another device via the network interface 1080 onto the primary storage device 1040 and execute the loaded program. Furthermore, the arithmetic unit 1030 of computer 1000 may cooperate with other devices via the network interface 1080 and call and use program functions, data, etc., from other programs on other devices.

[0203] [9. Other] Although embodiments of the present invention have been described above, the present invention is not limited by the content of these embodiments. Furthermore, the aforementioned components include those that can be easily conceived by those skilled in the art, those that are substantially the same, and those that fall within the so-called equivalent range. Moreover, the aforementioned components can be combined as appropriate. Furthermore, various omissions, substitutions, or modifications of the components can be made without departing from the gist of the embodiments described above.

[0204] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods. In addition, the processing procedures, specific names, and information including various data and parameters shown in the above document and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown.

[0205] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

[0206] For example, the payment server 100 described above may be implemented using multiple server computers, and depending on the function, it may be implemented by calling external platforms, etc., via APIs (Application Programming Interfaces) or network computing, allowing for flexible configuration changes.

[0207] Furthermore, the embodiments and modifications described above can be combined as appropriate, provided that the processing content is not inconsistent.

[0208] Furthermore, the terms "section, module, unit" mentioned above can be replaced with "means" or "circuit," etc. For example, the acquisition unit can be replaced with acquisition means or acquisition circuit. [Explanation of Symbols]

[0209] 1. Information Processing System 10 Terminal devices 100 Payment Servers 110 Communications Department 120 Storage section 121 User Information Database 122 History Information Database 123 Card Information Database 124 Payment Information Database 130 Control Unit 131 Acquisition Department 132 Publishing Department 133 Settings Section 134 Management Department 135 Payment Processing Unit 136 Estimation Department 137 Provision Department

Claims

1. A setting unit sets a balance within the payment application of a terminal device that can be used for payments via the payment application, in addition to a regular balance that is not restricted in its use, and sets a balance that is restricted in its use. Within the aforementioned payment application, there is a management unit that separately manages the regular balance and the limited-use balance, If the purpose indicated by the payment information at the time of payment via the payment application of the terminal device matches the purpose of the limited-use balance, the payment processing unit prioritizes payment using the limited-use balance over payment using the regular balance and automatically applies the limited-use balance to process the payment. An information processing device characterized by comprising:

2. When the settlement processing unit settles a payment for an application for which payment is to be made using the limited-use balance, if the balance of the limited-use balance is insufficient, it automatically applies the payment method of normal electronic payment and processes the settlement. The information processing apparatus according to feature 1.

3. When the settlement processing unit settles a payment for an application for which payment is to be made using the limited-use balance, if the balance of the limited-use balance is insufficient, it will settle the insufficient amount using the normal electronic payment method. The information processing apparatus according to feature 1.

4. When the settlement processing unit settles a payment for an application for which payment is to be made using the limited-use balance, if the balance of the limited-use balance is insufficient, it charges the insufficient amount from the normal balance to the limited-use balance and performs the settlement process. The information processing apparatus according to feature 1.

5. When the settlement processing unit settles a payment for an application for which payment is to be made using the limited-use balance, if the balance of the limited-use balance is insufficient, it will use the normal balance to settle the payment for the insufficient amount. The information processing apparatus according to feature 1.

6. An information processing method performed by an information processing device, A setting step involves setting a usage-restricted balance within the payment application of a terminal device, in addition to a regular balance that is not restricted in its use, as a balance that can be used for payments via the payment application of the terminal device. Within the aforementioned payment application, a management process is provided for separately managing the regular balance and the limited-use balance. A settlement processing step in which, if the purpose indicated by the settlement information at the time of settlement via the settlement application of the terminal device matches the purpose of the limited-use balance, the payment using the limited-use balance is prioritized over the payment using the regular balance, and the limited-use balance is automatically applied to perform the settlement process, An information processing method characterized by including

7. A setting procedure for setting a usage-restricted balance within a payment application, separate from a regular balance that can be used for any purpose, as a balance available for payment via the payment application of a terminal device, and Within the aforementioned payment application, a management procedure for separately managing the regular balance and the limited-use balance, A settlement processing procedure that, when the purpose indicated by the settlement information at the time of settlement via the settlement application of the terminal device matches the purpose of the limited-use balance, prioritizes payment using the limited-use balance over payment using the regular balance, and automatically applies the limited-use balance to perform the settlement process; An information processing program that causes a computer to execute something.

Images