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

Description

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

Technology relating to digital prepaid cards has been disclosed in the past.

JP 2020-149717 A

However, the above-mentioned conventional technology is merely a mechanism for carrying out reception processing, including payment at the car wash machine, by outputting a QR code (registered trademark) or the like that encodes not only payment settings but also car wash settings to a user's application. In order to realize a prepaid card that can be used for payments (electronic payments) using a terminal device, a mechanism for handling the balance dedicated to the prepaid card is required.

This application was made in consideration of the above, and aims to manage a limited-use balance as a balance that can be used for electronic payments.

The information processing device of the present application is characterized in that it comprises a setting unit that sets a use-limited balance, which has limited uses, in addition to a normal balance that has no use restrictions within a payment application as a balance available for payment via the payment application of a terminal device, a management unit that manages the normal balance and the use-limited balance separately within the payment application, and a payment processing unit that performs payment processing by automatically applying either payment with the normal balance, payment by normal electronic payment corresponding to credit card payment, or payment with the use-limited balance, depending on the use indicated by payment information at the time of payment via the payment application of the terminal device .

According to one aspect of the embodiment, a limited-use balance can be managed as a balance that can be used for electronic payments.

FIG. 1 is an explanatory diagram showing an overview of an information processing method according to an embodiment. FIG. 2 is an explanatory diagram showing an overview of the management of the balance of a prepaid card according to the embodiment. FIG. 3 is an explanatory diagram showing an outline of application of a prepaid card according to the embodiment. FIG. 4 is a diagram illustrating an example of the configuration of an information processing system according to the embodiment. FIG. 5 is a diagram illustrating an example of the configuration of a terminal device according to the embodiment. FIG. 6 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. FIG. 7 is a diagram illustrating an example of the user information database. FIG. 8 is a diagram illustrating an example of the history information database. FIG. 9 is a diagram showing an example of the card information database. FIG. 10 is a diagram illustrating an example of the payment information database. FIG. 11 is a flowchart showing a processing procedure of prepaid card management according to the embodiment. FIG. 12 is a flowchart showing a processing procedure for using a prepaid card according to the embodiment. FIG. 13 is a diagram illustrating an example of a hardware configuration.

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

[1. Overview of information processing method]
First, an overview of an information processing method performed by an information processing device according to an embodiment will be described with reference to Fig. 1. Fig. 1 is an explanatory diagram showing an overview of an information processing method according to an embodiment. Note that Fig. 1 will be described by taking as an example a case where a balance with limited uses is managed as a balance that can be used for electronic payment.

As shown in FIG. 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 FIG. 4) so as to be able to communicate with each other by wire or wirelessly. In this embodiment, the terminal device 10 cooperates with the payment server 100. Note that in the following description, an example is shown in which the terminal device 10 is used by a user U. In addition, in the following description, the terminal device 10 may be regarded as the same as the user U. That is, in the following description, the user U may also be read as the terminal device 10.

The terminal device 10 is a smart device such as a smartphone or tablet used by a user U, and is a mobile terminal device capable of communicating with any server device via a wireless communication network such as 4G (Generation) or LTE (Long Term Evolution). The terminal device 10 has a screen such as a liquid crystal display with touch panel functionality, and accepts various operations on displayed data such as content, such as tapping, sliding, scrolling, etc., performed by the user with a finger or a stylus. Note that an operation performed on an area of the screen where content is displayed may be considered to be an operation on the content. 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.

The payment server 100 is an information processing device that manages a limited-use balance as a balance that can be used for electronic payments, and is realized by a server device, a cloud system, or the like. For example, the payment server 100 provides an electronic payment service related to payments (electronic payments) using the terminal device 10. The payment server 100 also manages the accounts of businesses that provide transaction objects such as products and services, and the accounts of users to whom the transaction objects are provided, and realizes various payments by transferring electronic money between the accounts in accordance with a payment request from the user. Note that electronic money may be, for example, points or currency that various companies use independently, or may be electronically tradable currency provided by a country, such as Japanese yen or dollars. In this embodiment, the payment server 100 manages the balance for normal electronic payments and the balance for payment of each prepaid card separately in the user's account. That is, the payment server 100 manages the balance separately for each prepaid card. In reality, the account for each prepaid card may be managed as a purpose-specific account attached to the user's account.

In this embodiment, the payment server 100 provides a service of issuing and managing/operating a prepaid card. For example, when a user U purchases a prepaid card that can be used at affiliated stores at a prepaid card sales corner in an application for payment (electronic payment) using the user U's terminal device 10 (hereinafter, sometimes simply referred to as a "payment app"), the payment server 100 provides the prepaid card that can be used in the payment app. For example, the payment server 100 provides a prepaid card app as an application (mini app) that is launched in the payment app.

When user U purchases or uses the desired transaction object (goods, services) at an affiliated store where the prepaid card can be used, the user makes a payment (electronic payment) using the terminal device 10 via the payment app. At the time of electronic payment, the payment server 100 automatically applies the charge balance of the prepaid card to pay the payment amount of the target goods or services. In other words, the charge balance of the prepaid card is deducted by the payment amount of the target goods or services. If the charge balance of the prepaid card is insufficient, the entire charge balance of the prepaid card is used and the charge balance is deducted from the payment amount of the target goods or services.

This prepaid card can be used at affiliated stores of the electronic payment service. In this embodiment, the prepaid card is issued for each affiliated store. For example, the prepaid card is issued for each brand (corporate brand, product brand, etc.) of the affiliated store. If an affiliated store has multiple brands (for example, a main brand and a sub-brand), a prepaid card may be issued for each brand, or a common prepaid card may be issued for brands of the same affiliated store. Each affiliated store can design its own prepaid card. The terminal device 10 of the user U displays a UI (User Interface) of the prepaid card according to the design of each affiliated store. In addition, a premium (surcharge) can be added to the prepaid card using affiliated store funds. For example, the user U can purchase a prepaid card charged with 5,500 yen by paying 5,000 yen.

In addition, user U can charge a prepaid card by pressing (tapping, clicking, etc.) the "charge" button displayed for each prepaid card on a screen that displays a list of prepaid cards owned by the user.

This prepaid card can also be given as a gift by person-to-person remittance. That is, the user U can give the prepaid card as a gift to another person using the terminal device 10. For example, the user U can operate the terminal device 10 and press the "gift" button displayed for each prepaid card on a screen displaying a list of prepaid cards owned by the user U, thereby using the person-to-person remittance function of the payment application to give the prepaid card as a gift to another user. Note that if a prepaid card is given as a gift and the user already owns the prepaid card, the charge amount of the given prepaid card is charged to the prepaid card already owned. At this time, the terminal device 10 of the person who received the prepaid card displays the fact that the prepaid card has been given as a gift and information about the giver. For example, the terminal device 10 of the person who received the gift displays a message such as "Mr./Ms. XX has given you a prepaid card of XX yen for □□."

In addition, if user U has a prepaid card that can be used at a target affiliated store, the card can be used in conjunction with a payment when making a payment at that affiliated store. When the payment amount exceeds the charge balance, the payment server 100 prompts the user to select whether or not to charge again.

The payment server 100 may acquire various information related to the user U. For example, the payment server 100 acquires information related to the attributes of the user U, such as the gender, age, and area of residence of the user U. The payment server 100 then stores and manages the information related to the attributes of the user U together with identification information (such as a user ID) indicating the user U.

The payment server 100 may also obtain various history information (log data) indicating the behavior of the user U from the terminal device 10 of the user U or from various servers based on the user ID, etc. For example, the payment server 100 obtains a location history, which is a history of the location and date and time of the user U, from the terminal device 10. The payment server 100 also obtains a search history, which is a history of search queries entered by the user U, from a search server (search engine). The payment server 100 also obtains a browsing history, which is a history of content viewed by the user U, from a content server. The payment server 100 also obtains a purchase history, which is a history of product purchases by the user U, from an electronic commerce server or a payment server. The payment server 100 may also obtain a listing history or a sales history, which is a history of listings on the marketplace by the user U, from an electronic commerce server or a payment server. The payment server 100 also obtains a posting history, which is a history of posts by the user U, from a posting server or an SNS server that provides a word-of-mouth posting service.

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

Alternatively, the payment server 100 may use machine learning to create a prepaid card estimation model (trained model) that outputs an estimation result of a prepaid card suitable for the user U when the attribute information of the user U is input. That is, the payment server 100 generates an estimation model using the attribute information of the user U and the prepaid card used by the user U as correct answer data. The payment server 100 may then input the attribute information of the user U into the prepaid card estimation model, and based on the output estimation result of the prepaid card, push notification of a link to a purchase screen for the prepaid card, etc. to the terminal device 10 of the user U. Note that in practice, history information may be input together with the attribute information of the user U. That is, the payment server 100 may generate an estimation model using the attribute information and history information of the user U and the prepaid card used by the user U as correct answer data.

Regarding the creation of the trained model, for example, the payment server 100 creates a trained model that estimates a prepaid card suitable for the user U by machine learning using a recurrent neural network (RNN) or a long short-term memory (LSTM). Note that any type and any format of model can be adopted. For example, the payment server 100 may adopt a support vector machine (SVM) or a deep neural network (DNN) as a model. Here, the DNN may be a convolutional neural network (CNN) or an RNN. The model may also be a model realized by combining multiple models, such as a model combining a CNN and an RNN. Note that the RNN or the LSTM may be a neural network based on an attention mechanism. The payment server 100 may also use a similar natural language processing model. In addition, data mining or other machine learning algorithms may be used. The payment server 100 can train the model by the various learning methods described above.

1-1. Payment using the terminal device 10
Here, prior to the information processing according to the embodiment, an example of payment (electronic payment) using the terminal device 10 will be described. In the following description, an example will be described in which a user U makes a payment using the terminal device 10 using a two-dimensional code (QR code (registered trademark)) placed in a store, which indicates store identification information that identifies the store, but the embodiment is not limited to this. The example of payment described below can also be applied when an arbitrary user makes a payment at an arbitrary store using an arbitrary terminal device 10. In addition, the store identification information may be not only a QR code (registered trademark), but also a barcode, a predetermined mark, a number, etc.

For example, when user U makes a payment for the use or purchase of a payment object (transaction object) such as various goods or services at a store, user U launches a payment application (payment app) installed on terminal device 10. User U then photographs the store identification information set up in the store via the payment app. In such a case, terminal device 10 displays a screen for inputting the price of the payment object and accepts input of the payment amount from user U or a store clerk. Terminal device 10 then transmits to payment server 100 payment information indicating 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., affiliated store ID)), and the payment amount.

In such a case, the payment server 100 transfers electronic money in the amount 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 that the payment has been completed to the terminal device 10. In such a case, the terminal device 10 notifies that the payment has been made with electronic money by outputting a screen or a specified sound indicating that the payment has been completed.

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

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

1-2. Information Processing According to the Embodiment
As shown in FIG. 1, when user U purchases a prepaid card that can be used at affiliated stores at the prepaid card sales corner in the payment app for making a payment (electronic payment) using user U's terminal device 10, the payment server 100 issues a prepaid card that can be used within the payment app (step S1).

Next, if user U wishes to give a prepaid card as a gift to another user F, he/she uses the terminal device 10 to provide the prepaid card as a gift through person-to-person remittance (step S2). Conversely, user U can also receive a prepaid card as a gift from another user F through person-to-person remittance. In other words, prepaid cards can be given as gifts to each other. After purchasing a prepaid card, user U may provide the prepaid card as a gift to another user F by selecting a prepaid card he/she owns in the payment app and pressing the "gift" button. When purchasing a prepaid card, user U may also purchase another user F as the recipient (recipient) of the prepaid card.

Next, the terminal device 10 cooperates with the payment server 100 to notify the user U of information about the prepaid card held in order to prevent the user U from forgetting to use the prepaid card (step S3). For example, the terminal device 10 pushes or displays prepaid cards that can be used at stores near the user U's location or stores within the user U's moving range based on the user U's location information. At this time, when the user U is within a predetermined range (e.g., within a radius of 500 m) from a store where a prepaid card can be used, the terminal device 10 may push or display prepaid cards that can be used at the store. In addition, when the user U enters a store where a prepaid card can be used, the terminal device 10 may push or display prepaid cards that can be used at the store. In addition, when the user U launches a payment app to make a payment (electronic payment) using the terminal device 10, the terminal device 10 may push or display prepaid cards that can be used at the store. For example, when a payment app is launched in a store or when a "Pay" button on the payment app is pressed, the terminal device 10 may send a push notification or display prepaid cards that can be used at that store.

Then, the terminal device 10 notifies the payment server 100 of information regarding the usage of the prepaid card held by the user U (step S4). For example, when the terminal device 10 purchases and uses a desired transaction object (goods, service) at an affiliated store where the prepaid card held by the user U can be used, and makes a payment (electronic payment) using the terminal device 10 via a payment app, the terminal device 10 notifies the payment server 100 of the payment information via the network N (see FIG. 4) or the store terminal of the affiliated store. In addition, when the terminal device 10 presents the prepaid card held by the user U to another user F as a gift, the terminal device 10 notifies the payment server 100 that the prepaid card has been transferred from the user U to the other user F.

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

[1-3. Managing the balance of prepaid cards]
Hereinafter, the management of the balance of a prepaid card will be described with reference to Fig. 2. Fig. 2 is an explanatory diagram showing an overview of the management of the balance of a prepaid card according to the embodiment.

As shown in FIG. 2, when user U purchases a prepaid card created for each affiliated store (or receives one as a gift from another person), the terminal device 10 and the payment server 100 set up an account or data area for managing a balance dedicated to the prepaid card (limited-use balance) in addition to the balance for normal electronic payments. In other words, the balance for normal electronic payments and the balance dedicated to the prepaid card are independent. The balance dedicated to the prepaid card can be topped up in the same way as the balance for normal electronic payments, and it is also possible to top up from the balance for normal electronic payments. Note that the balance dedicated to the prepaid card cannot be topped up to the balance for normal electronic payments.

In addition, the balance dedicated to a prepaid card is set for each prepaid card. In other words, the balance dedicated to a prepaid card is independent for each prepaid card. It is not possible to transfer or recharge the balance between prepaid cards owned by the same user. In other words, it is not possible to transfer the balance between prepaid cards.

In addition, the balance dedicated to a prepaid card can be transferred to other users via person-to-person transfers, just like a balance for normal electronic payments. For example, if user U gives prepaid card A as a gift to other user F, the entire balance dedicated to user U's prepaid card A will be transferred to other user F, and that entire amount will be deposited into the balance dedicated to other user F's prepaid card A. In addition, if user U transfers a specified amount from the balance dedicated to prepaid card A, that specified amount will be deposited into the balance dedicated to other user F's prepaid card A.

In addition, because prepaid cards are created for each affiliated store, the balance dedicated to the prepaid card can also be said to be the balance dedicated to the affiliated store that created it. When a prepaid card of the affiliated store is applied to pay for a product purchased at the affiliated store that created it, the payment is made from the balance dedicated to that prepaid card. For example, when prepaid card A of affiliated store A is applied, the payment is made from the balance dedicated to prepaid card A.

In addition, the prepaid card can be used not only for payments at the affiliated store (e.g., flagship store, directly managed store, tenant store, etc.), but also for products of the affiliated store sold at other retail stores (mass retailers, etc.). For example, when user U purchases products from affiliated store A, affiliated store B, and other products at a certain retail store and makes a payment (electronic payment) using user U's terminal device 10, if user U holds prepaid card A of affiliated store A, payment for the products of affiliated store A is made from the balance of prepaid card A, and if user U holds prepaid card B of affiliated store B, payment for the products of affiliated store B is made from the balance of prepaid card B. Payment for other products is made from the balance for normal electronic payments. In other words, payment for products of a specific brand is made from the balance of the prepaid card corresponding to that brand.

Note that affiliated stores are not limited to brand shops selling apparel, shoes, cosmetics, toys, etc., but may also be retail stores, restaurants, etc. For example, affiliated stores may be retail stores such as convenience stores, supermarkets, drug stores, discount stores, home improvement stores, mass retailers, and specialty stores, or may be restaurants such as restaurants, fast food restaurants, coffee chains, coffee shops, and bars. Affiliated stores may also be bookstores, gas stations, etc.

Furthermore, the member store is not limited to a store that handles transaction objects for which electronic coupon tickets can be used, but may also be a facility where electronic coupon tickets can be used. In reality, it may be a large commercial facility (department store/shopping center/outlet mall/underground shopping mall), a large leisure facility (theme park/amusement park/game center/zoo/aquarium/swimming pool/bathing facility/park/garden/famous place), a cultural facility (hall/theater/cinema/art museum/museum), a sports facility (athletic field (ground)/baseball field/tennis court/gymnasium/stadium/indoor pool), an accommodation facility (hotel/inn), a public transportation facility (railway/bus/taxis/ship/airline), a train station, airport, port (boarding point), a parking lot, etc. It may also be an educational institution such as a school, or a medical institution such as a hospital.

The affiliated store may also be a manufacturer (manufacturer) that produces products. For example, if the products purchased by the user include products manufactured by the affiliated store, the payment server 100 may apply a prepaid card to the payment for the products manufactured by the affiliated store. The affiliated store may also be a business that owns a specific product brand. For example, if the products purchased by the user include products of a specific product brand, the payment server 100 may apply a prepaid card to the payment for the products of that product brand.

In other words, the types of businesses of participating stores are diverse, as long as they are businesses in which prepaid cards can be used.

[1-4. Application of prepaid cards]
Hereinafter, the prepaid card application process executed by the payment server 100 will be described with reference to Fig. 3. Fig. 3 is an explanatory diagram showing an outline of the prepaid card application according to the embodiment. However, this outline is merely an example.

First, the terminal device 10 launches a payment app pre-installed on the device in response to an operation from the user U, and displays a screen for the user U to purchase a prepaid card in the electronic payment service (step S11). Next, the terminal device 10 accepts a prepaid card purchase operation from the user U (step S12). For example, the terminal device 10 accepts a prepaid card purchase operation on the screen displayed in step S11, and transmits information indicating the prepaid card for which the purchase operation has been performed to the payment server 100.

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

Next, the payment server 100 receives information (prepaid card ID) indicating the prepaid card for which the purchase operation was performed (or a prepaid card received from another user) from the terminal device 10 (step S13). Next, the payment server 100 links the user U and the prepaid card and manages them (step S14). For example, the payment server 100 links the user ID of user U and the prepaid card ID received from the terminal device 10 and manages them.

In the example of FIG. 3, it is assumed that user U wishes to make the above-mentioned payment to store A, which is made by the business terminal 200 reading the user identification information (user ID). In this case, the business terminal 200 reads the product ID of each product purchased by user U and the user ID of user U displayed on the terminal device 10 (step S15). For example, the business terminal 200 reads the barcode (product ID) attached to the product using a barcode reader or the like during checkout, and the user ID displayed on the terminal device 10.

Next, the payment server 100 receives payment information related to the payment made by user U to store A from the business terminal 200 (step S16). For example, the payment server 100 receives payment information from the business terminal 200, including the store ID of store A, the product ID read by the business terminal 200 in step S15, the total price (payment amount) of each product linked to the product ID, and the user ID of user U.

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

Next, the payment server 100 executes a payment process based on the payment information and makes the payment by applying the identified prepaid card (step S18). For example, the payment server 100 executes a process to transfer electronic money in the amount indicated by the payment amount from the account of the user U to the account of the store A. Then, the payment server 100 makes the payment by applying the identified prepaid card.

Then, the payment server 100 notifies the user U that the prepaid card has been applied (step S18). For example, the payment server 10 causes the terminal device 10 to display a payment completion screen C1 indicating that the payment to store A has been completed, and notifies the user U of information indicating the applied prepaid card on the payment completion screen C1, the amount used on the prepaid card (payment amount), the balance of the prepaid card, etc.

As described above, the payment server 100 according to the embodiment identifies a prepaid card that is applicable to an affiliated store and applies the identified prepaid card to make a payment. This allows the payment server 100 according to the embodiment to automatically apply an applicable prepaid card without the user having to perform an operation to select the prepaid card to be used. In other words, the payment server 100 according to the embodiment can improve the convenience of users in making payments.

(Payment-linked prepaid card)
At this time, in steps S17 and S18, the payment server 100 may acquire affiliated store information together with the payment information, and automatically apply a prepaid card that can be used for payment at the affiliated store among the prepaid cards held by the user U. That is, a prepaid card is automatically applied in conjunction with the payment for each store (each affiliated store).

(Linked payment by product)
In addition, in steps S17 and S18, the payment server 100 may utilize the product data in cooperation with the POS (Point of Sale System) of the affiliated store to automatically apply the prepaid card corresponding to the product data. In this case, in step S17, the payment server 100 collates the prepaid card information corresponding to the prepaid card that the user U has acquired (purchased or received from another person) with the payment information to identify the prepaid card that is linked to the product ID indicated by the payment information among the prepaid cards that the user U has acquired. In practice, the prepaid card linked to the store ID of the affiliated store that is the manufacturer (provider) of the product corresponding to the product ID indicated by the payment information may be identified. In addition, the prepaid card linked to the product brand may be identified, not limited to the corporate brand of the product manufacturer, etc. In addition, when the user U purchases multiple products, it is sufficient that at least one of the multiple purchased products is a product eligible for the prepaid card. In other words, the prepaid card is automatically applied in conjunction with the payment for each product (each product).

(Reading the prepaid card code installed)
Alternatively, in step S15, the prepaid card may be used when user U uses the terminal device 10 to read a two-dimensional code for prepaid card payment (a code exclusive to prepaid cards) installed in the store (at the cash register, etc.) separately from the two-dimensional code for normal electronic payment (QR code (registered trademark)) using a scanning function associated with the prepaid card app.

(User presents prepaid card code)
Also, in step S15, the user U may display a prepaid card-specific code, such as a barcode or two-dimensional code for prepaid card payment, on the terminal device 10 and present it to the store clerk, and when the store clerk reads it with the store terminal, the prepaid card may be used.

In other words, the prepaid card may be used only if user U actively expresses an intention to use the prepaid card.

The above-mentioned automatic application of the prepaid card and the reading of the two-dimensional code for prepaid card payment (a code exclusive to the prepaid card) may be used together (they can be used together). For example, if the two-dimensional 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.

(Recharge confirmation)
Furthermore, when performing payment processing for a product purchased by the user U, if the balance of the prepaid card held by the user U is insufficient, the payment server 100 may check whether or not to recharge the prepaid card. For example, the payment server 100 inquires of the user U about whether to recharge the prepaid card or to pay the shortfall in the balance of the prepaid card by normal electronic payment. The prepaid card may be recharged by payment (electronic payment) using the terminal device 10. Furthermore, if the prepaid card is not recharged when the balance is insufficient, the payment server 100 may pay the shortfall in the balance of the prepaid card by using the balance for normal electronic payment.

Also, confirmation of recharging the prepaid card may be performed when entering a store. At this time, the terminal device 10 may work in cooperation with the payment server 100 to identify the store based on location information and identify a prepaid card that can be used at that store. For example, when the user U enters a store where prepaid cards can be used, the terminal device 10 inquires whether to recharge if the balance of the prepaid card that can be used at the store is equal to or less than a predetermined amount. Alternatively, when the user U launches a payment app to make a payment (electronic payment) using the terminal device 10, the terminal device 10 inquires whether to recharge if the balance of the prepaid card that can be used at the store is equal to or less than a predetermined amount.

According to this embodiment, the balance of each prepaid card is managed separately for each card and is managed independently from the balance for normal electronic payments, so that an electronic money balance can be secured for use limited to payments at affiliated stores that accept the prepaid card. In addition, the prepaid card is managed within the payment app and is automatically applied when making a payment using the payment app at an affiliated store that accepts the prepaid card, so no operations are required to use the prepaid card and there is no risk of missing out on using the prepaid card, improving convenience for users.

2. Example of information processing system configuration
Next, a configuration of the information processing system 1 including the payment server 100 according to the embodiment will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the configuration of the information processing system 1 according to the embodiment. As shown in Fig. 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 so as to be able to communicate with each other by wire or wirelessly. The network N is, for example, a local area network (LAN) or a wide area network (WAN) such as the Internet.

Furthermore, the number of devices included in the information processing system 1 shown in FIG. 4 is not limited to that shown. For example, in FIG. 4, only one terminal device 10 is shown to simplify the illustration, but this is merely an example and is not limiting, and there may be two or more devices.

The terminal device 10 is an information processing device used by a user U. For example, the terminal device 10 is a smart device such as a smartphone or a tablet terminal, a feature phone, a PC (Personal Computer), a PDA (Personal Digital Assistant), a game console with a communication function, a car navigation system, a wearable device such as a smart watch or a head-mounted display, smart glasses, etc.

In addition, the terminal device 10 can connect to the network N via a wireless communication network such as LTE (Long Term Evolution), 4G (4th Generation), or 5G (5th Generation: 5th generation mobile communication system), or via short-range wireless communication such as Bluetooth (registered trademark) or wireless LAN (Local Area Network), and communicate with the payment server 100.

The terminal device 10 may also be a store terminal of an affiliated store or a terminal device used by a clerk (employee) of an affiliated store. In other words, the store terminal of an affiliated store or the terminal device used by a clerk of an affiliated store may be a device similar to the terminal device 10 described above.

The payment server 100 is, for example, a PC, a server device, a mainframe, a workstation, etc. The payment server 100 may also be realized by cloud computing.

3. Example of terminal device configuration
Next, the configuration of the terminal device 10 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the configuration of the terminal device 10. As shown in Fig. 5, the terminal device 10 includes 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.

(Communication unit 11)
The communication unit 11 is connected to a network N (see FIG. 4 ) by wire or wirelessly, and transmits and receives information to and from the payment server 100 via the network N. For example, the communication unit 11 is realized by a network interface card (NIC), an antenna, or the like.

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

(Input unit 13)
The input unit 13 is an input device that accepts various operations from the user U. The input unit 13 also has, for example, buttons for inputting characters, numbers, and the like. If the display unit 12 is a touch panel display, a part of the display unit 12 functions as the input unit 13. The input unit 13 may be a microphone that accepts voice input from the user U. The microphone may be wireless.

(Positioning unit 14)
The positioning unit 14 receives signals (radio waves) transmitted from satellites of a GPS (Global Positioning System), and acquires position information (e.g., latitude and longitude) indicating the current position of the terminal device 10 based on the received signals. That is, the positioning unit 14 measures the position of the terminal device 10. Note that the GPS is merely an example of a GNSS (Global Navigation Satellite System).

The positioning unit 14 can also measure the position using various methods other than GPS. For example, the positioning unit 14 may measure the position using various communication functions of the terminal device 10 as an auxiliary positioning means for position correction, etc., as described below.

(Wi-Fi positioning)
For example, the positioning unit 14 uses a Wi-Fi (registered trademark) communication function of the terminal device 10 or a communication network provided by each communication company to measure the position of the terminal device 10. Specifically, the positioning unit 14 performs Wi-Fi communication or the like and measures the distance to a nearby base station or access point to measure the position of the terminal device 10.

(Beacon positioning)
Furthermore, the positioning unit 14 may measure the position by using a Bluetooth (registered trademark) function of the terminal device 10. For example, the positioning unit 14 measures the position of the terminal device 10 by connecting to a beacon transmitter connected by the Bluetooth (registered trademark) function.

(geomagnetic positioning)
In addition, the positioning unit 14 locates the position of the terminal device 10 based on a geomagnetic pattern of a structure that has been measured in advance and a geomagnetic sensor provided in the terminal device 10 .

(RFID positioning)
Furthermore, for example, if the terminal device 10 has a function of an RFID (Radio Frequency Identification) tag equivalent to a contactless IC card used at station ticket gates, in stores, etc., or has a function of reading an RFID tag, the location of use is recorded together with information on a payment or the like made by the terminal device 10. The positioning unit 14 may obtain such information to measure the location of the terminal device 10. Furthermore, the location may be measured by an optical sensor, an infrared sensor, or the like provided in the terminal device 10.

If necessary, the positioning unit 14 may use one or a combination of the positioning means described above to determine the position of the terminal device 10.

(Sensor unit 20)
The sensor unit 20 includes various sensors mounted on or connected to the terminal device 10. The connection may be wired or wireless. For example, the sensors may be detection devices other than the terminal device 10, such as wearable devices and wireless devices. In the example shown in FIG. 5, the sensor unit 20 includes an acceleration sensor 21, a gyro sensor 22, an air 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.

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

The acceleration sensor 21 is, for example, a three-axis acceleration sensor, and detects the physical movement of the terminal device 10, such as the direction of movement, speed, and acceleration of the terminal device 10. The gyro sensor 22 detects the physical movement of the terminal device 10, such as the tilt in three axial directions, based on the angular velocity of the terminal device 10. The air pressure sensor 23 detects, for example, the air pressure around the terminal device 10.

Since the terminal device 10 is equipped with the above-mentioned acceleration sensor 21, gyro sensor 22, air pressure sensor 23, etc., it is possible to determine the position of the terminal device 10 using technology such as Pedestrian Dead-Reckoning (PDR) that utilizes these sensors 21 to 23. This makes it possible to obtain indoor position information that is difficult to obtain using positioning systems such as GPS.

For example, the number of steps, walking speed, and distance walked can be calculated using a pedometer that uses the acceleration sensor 21. In addition, the gyro sensor 22 can be used to know the user U's direction of travel, line of sight, and body inclination. In addition, the air pressure detected by the air pressure sensor 23 can be used to know the altitude and floor on which the user U's terminal device 10 is located.

The air temperature sensor 24 detects, for example, the air temperature around the terminal device 10. The sound sensor 25 detects, for example, sound around the terminal device 10. The light sensor 26 detects the illuminance around the terminal device 10. The magnetic sensor 27 detects, for example, the geomagnetism around the terminal device 10. The image sensor 28 captures an image around the terminal device 10.

The above-mentioned air pressure sensor 23, temperature sensor 24, sound sensor 25, light sensor 26, and image sensor 28 can detect the environment and situation around the terminal device 10 by detecting air pressure, temperature, sound, and illuminance, and capturing images of the surroundings. In addition, it is possible to improve the accuracy of the location information of the terminal device 10 based on the environment and situation around the terminal device 10.

(Control unit 30)
The control unit 30 includes, for example, a microcomputer having a central processing unit (CPU), a read only memory (ROM), a RAM, an input/output port, and various other circuits. The control unit 30 may also be configured with hardware such as an integrated circuit, for example, an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The control unit 30 includes a transmission unit 31, a reception unit 32, and a processing unit 33.

(Transmitter 31)
The transmission unit 31 can transmit, for example, various information input by the user U using the input unit 13, various information detected by each sensor 21 to 28 mounted on or connected to the terminal device 10, and location information of the terminal device 10 measured by the positioning unit 14 to the payment server 100 via the communication unit 11.

(Receiving unit 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.

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

(Memory unit 40)
The storage unit 40 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk drive (HDD), a solid state drive (SSD), an optical disk, etc. Various programs and various data are stored in the storage unit 40.

4. Configuration example of information processing device
Next, a configuration of the payment server 100 according to the embodiment will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the configuration of the payment server 100 according to the embodiment. As shown in Fig. 6, the payment server 100 includes a communication unit 110, a storage unit 120, and a control unit 130.

(Communication unit 110)
The communication unit 110 is realized by, for example, a network interface card (NIC), etc. The communication unit 110 is also connected to a network N (see FIG. 4) in a wired or wireless manner.

(Memory unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk, an optical disk, etc. As shown in Fig. 6, the storage unit 120 has a user information database 121, a history information database 122, a card information database 123, and a payment information database 124.

(User information database 121)
The user information database 121 stores various information related to the user U. For example, the user information database 121 stores various information such as attributes of the user U. Fig. 7 is a diagram showing an example of the user information database 121. In the example shown in Fig. 7, the user information database 121 has items such as "User ID (Identifier)", "Age", "Gender", "Home", "Workplace", and "Interests".

"User ID" indicates identification information for identifying user U. Furthermore, "age" indicates the age of user U identified by the user ID. Note that "age" may be the specific age of user U identified by the user ID, such as 35 years old. Furthermore, "gender" indicates the gender of user U identified by the user ID.

"Home" indicates the location information of the home of user U, which is identified by the user ID. In the example shown in FIG. 7, "Home" is illustrated as an abstract code such as "LC11", but it may also be latitude and longitude information, etc. For example, "Home" may also be the name of a region or an address.

"Workplace" indicates the location information of the workplace (school in the case of a student) of user U identified by the user ID. In the example shown in FIG. 7, "workplace" is illustrated as an abstract code such as "LC12", but it may also be latitude and longitude information, etc. For example, "workplace" may also be the name of a region or an address.

Furthermore, "interests" indicate the interests of user U identified by the user ID. In other words, "interests" indicate subjects in which user U identified by the user ID is highly interested. For example, "interests" may be search queries (keywords) entered by user U into a search engine. Note that, in the example shown in FIG. 7, one "interest" is illustrated for each user U, but there may be multiple "interests."

For example, in the example shown in FIG. 7, the age of user U identified by user ID "U1" is "20s" and the gender is "male." Also, for example, user U identified by user ID "U1" indicates that his home address is "LC11." Also, for example, user U identified by user ID "U1" indicates that his workplace is "LC12." Also, for example, user U identified by user ID "U1" indicates that he is interested in "sports."

In the example shown in FIG. 7, abstract values such as "U1", "LC11", and "LC12" are used to illustrate the data, but it is assumed that concrete information such as character strings and numerical values is stored in "U1", "LC11", and "LC12". In the following figures relating to other information, abstract values may also be illustrated.

The user information database 121 may store various information according to the purpose, not limited to the above. For example, the user information database 121 may store various information related to the terminal device 10 of the user U. The user information database 121 may also store information related to the attributes of the user U, such as demographic attributes, psychographic attributes, geographic attributes, 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 the user has a car, commuting time, commuting route, commuter pass section (station, line, etc.), frequently used station (other than the nearest station to home or workplace), extracurricular activities (location, time zone, etc.), hobbies, interests, and lifestyle.

(History information database 122)
The history information database 122 stores various information related to history information (log data) indicating the behavior of the user U. Fig. 8 is a diagram showing an example of the history information database 122. In the example shown in Fig. 8, the history information database 122 has items such as "user ID", "location history", "search history", "browsing history", "purchase history", and "posting history".

"User ID" refers to identification information for identifying user U. "Location history" refers to location history, which is a history of user U's location and movements. "Search history" refers to search history, which is a history of search queries entered by user U. "Browse history" refers to browse history, which is a history of content viewed by user U. "Purchase history" refers to purchase history, which is a history of purchases made by user U. "Post history" refers to posting history, which is a history of posts made by user U. "Post history" may include questions about user U's possessions.

For example, in the example shown in FIG. 8, user U identified by user ID "U1" moved as shown in "location history #1," searched as shown in "search history #1," viewed content as shown in "browsing history #1," purchased specific products at specific stores as shown in "purchase history #1," and posted as shown in "posting history."

In the example shown in FIG. 8, abstract values such as "U1", "Location History #1", "Search History #1", "Browse History #1", "Purchase History #1", and "Post History #1" are used for illustration, but specific information such as character strings and numerical values is stored in "U1", "Location History #1", "Search History #1", "Browse History #1", "Purchase History #1", and "Post History #1".

The history information database 122 may store various information depending on the purpose, not limited to the above. For example, the history information database 122 may store the usage history of a specific service by the user U. The history information database 122 may also store the history of the user U's visits to a physical store or facility. The history information database 122 may also store the payment history of the user U's electronic payments.

(Card information database 123)
Card information database 123 stores various information related to prepaid cards. Fig. 9 is a diagram showing an example of card information database 123. In the example shown in Fig. 9, card information database 123 has items such as "user ID", "affiliated store ID", "card ID", "account ID", "balance", "maximum amount", and "expiration date".

"User ID" indicates identification information for identifying the user U who purchased the prepaid card. "Member store ID" indicates identification information for identifying a member store where the prepaid card can be used. The member store 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 the user U. In this embodiment, the prepaid card is issued for each member store. "Account ID" indicates identification information for identifying an account linked to the prepaid card. 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 products (or use services) at member stores 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. The maximum amount may be an upper limit set by the user U as a daily or monthly usage limit. Additionally, "Expiration date" indicates the expiration date of the prepaid card held by user U. For example, the expiration date is indicated by the year, month, and day.

For example, in the example shown in FIG. 9, it is shown that user U, identified by user ID "U1", holds a card identified by card ID "card #A" that can be used at the brand identified by affiliated store ID "store #A". In addition, 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".

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 specific information such as character strings and numerical values is stored in "U1", "Store #A", "Card #A", and "Account #A".

The card information database 123 may store various information depending on the purpose, not limited to the above. For example, the card information database 123 may store the usage history of the prepaid card of the user U. The card information database 123 may also store information regarding the prepaid cards that the user U has purchased in the past (for example, the purchasing history of the prepaid cards). The card information database 123 may also store information regarding benefits (bonuses, premiums, etc.) according to the frequency of use and number of purchases of the prepaid card of the user U.

(Payment information database 124)
The payment information database 124 stores various information related to payments (electronic payments) using the terminal device 10. Fig. 10 is a diagram showing an example of the payment information database 124. In the example shown in Fig. 10, the payment information database 124 has items such as "user ID", "store ID", "transaction object ID", "unit price", "quantity", "card ID", "amount used", and "payment amount".

"User ID" indicates identification information for identifying user U who used a prepaid card in a payment (electronic payment) using the terminal device 10. "Store ID" indicates identification information for identifying the affiliated store (shop) where the prepaid card was used in a payment (electronic payment) using the terminal device 10. The store ID may be identification information for identifying a chain store. "Transaction object ID" indicates identification information for identifying the transaction object such as a product or service that is covered by the prepaid card in a payment (electronic payment) using the terminal device 10. "Unit price" indicates the unit price of the transaction object such as a product or service that is covered by the prepaid card. "Quantity" indicates the quantity of the transaction object such as a product or service that is covered by the prepaid card. In other words, the quantity indicates the number of products (purchases) that are covered by the prepaid card or the number of times a service is used.

Furthermore, "card ID" indicates identification information for identifying the prepaid card used by user U. Furthermore, "amount used" indicates the amount used on the prepaid card in payment (electronic payment) using terminal device 10. For example, if the balance of the prepaid card is greater than the total amount of the transaction objects to be settled, the amount used will be the same as the total amount of the transaction objects. Furthermore, if the balance of the prepaid card is less than the total amount of the transaction objects to be settled, the amount used will be the entire balance of the prepaid card. Furthermore, the shortfall may be selected to be paid by recharging the prepaid card or by normal electronic payment. Furthermore, "payment amount" indicates the payment amount after using the prepaid card. The price of the transaction objects for which the prepaid card can be used will be free (0 yen) by using the prepaid card.

For example, in the example shown in FIG. 10, user U identified by user ID "U1" purchased a quantity of "1" of a transaction object identified by transaction object ID "transaction object #A1" at a store identified by store ID "store #A" at a unit price of "1,200" yen. In addition, the above user U used a prepaid card identified by card ID "card #A" for the above transaction object for a usage amount of "1,200" yen, resulting in a settlement amount of "0" yen.

In the example shown in FIG. 10, abstract values such as "U1", "Store #A", "Transaction object #A1", and "Card #A" are used for illustration, but specific information such as character strings and numerical values is stored in "U1", "Store #A", "Transaction object #A1", and "Card #A".

The payment information database 124 may store various information according to the purpose, not limited to the above. For example, the payment information database 124 may store a payment method such as a payment using the terminal device 10 (electronic payment) or identification information for identifying a payment service provider.

Furthermore, the history information database 122, the card information database 123, and the payment information database 124 may be linked to the user information database 121 or may be integrated with the user information database 121. For example, the user information database 121, the history information database 122, the card information database 123, and the payment information database 124 may be a relational database (RDB).

(Control unit 130)
Returning to Fig. 6, the description will be continued. The control unit 130 is a controller, and is realized by, for example, a central processing unit (CPU), a micro processing unit (MPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like, executing various programs (corresponding to an example of an information processing program) stored in a storage device inside the payment server 100 using a storage area such as a RAM as a working area. In the example shown in Fig. 6, the control unit 130 has an acquisition unit 131, an issue unit 132, a setting unit 133, a management unit 134, a payment processing unit 135, an estimation unit 136, and a provision unit 137.

(Acquisition unit 131)
The acquisition unit 131 acquires various information related to the user U via the communication unit 110. For example, the acquisition unit 131 acquires location information of the user U, attribute information of the user U, and the like, based on information (such as a user ID) indicating the user U who uses the payment app. Then, the acquisition unit 131 registers the information in the user information database 121 of the storage unit 120.

The acquisition unit 131 also acquires various types of history information (log data) indicating the actions of the user U via the communication unit 110. The acquisition unit 131 then registers the information in the history information database 122 of the storage unit 120.

The acquisition unit 131 also accepts a purchase request (issuance request), a charge request, and a provision request (gift request) for a prepaid card from the user U via the communication unit 110. For example, when the user U performs an operation to purchase a prepaid card for a desired transaction object (goods, service) at a desired store at a prepaid card sales corner in the payment app, the acquisition unit 131 accepts this as a purchase request for a prepaid card. When the user U performs an operation to charge the balance of the prepaid card by specifying an amount in the payment app, the acquisition unit 131 charges the amount specified by the user U to the balance of the prepaid card. When the user U specifies a person other than himself/herself as the recipient when purchasing a prepaid card or performs an operation to transfer the prepaid card to another person after purchasing the prepaid card in the payment app, the acquisition unit 131 accepts this as a provision request (gift request) for a prepaid card. That is, the acquisition unit 131 also functions as a reception unit that receives prepaid card purchase requests (issuance requests), charge requests, and provision requests (gift requests).

(Issuing Department 132)
The issuing unit 132 issues a prepaid card in response to a purchase request (issuance request) for a prepaid card from the user U. For example, the issuing unit 132 issues a prepaid card to the user U at a prepaid card sales corner in the payment application. At this time, the issuing unit 132 issues a prepaid card that is linked to a payment (electronic payment) using the terminal device 10. From another perspective, the issuing unit 132 issues a prepaid card that can be used in a payment (electronic payment) using the terminal device 10. Furthermore, the issuing unit 132 issues a prepaid card for each affiliated store. For example, the issuing unit 132 issues a prepaid card for each corporate brand. Furthermore, the issuing unit 132 may issue a prepaid card for each product brand.

(Setting unit 133)
The setting unit 133 sets a limited use balance, which is used for limited use, as a balance available for payment using a terminal device, separate from a normal balance, which has no limited use. At this time, the setting unit 133 sets a limited use balance for each use. The setting unit 133 also sets a limited use balance for each affiliated store of the payment service. The setting unit 133 also sets a limited use balance for each user U.

Furthermore, when a prepaid card is issued, the setting unit 133 sets a balance exclusive to the prepaid card. Since a prepaid card is issued for each affiliated store, it can be said that the setting unit 133 sets a balance exclusive to the affiliated store. For example, when a prepaid card is issued for each corporate brand, the setting unit 133 sets a balance exclusive to the corporate brand. Furthermore, when a prepaid card is issued for each product brand, the setting unit 133 may set a balance exclusive to the product brand.

The setting unit 133 may cooperate with the issuing unit 132 or the management unit 134, or 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 function of the issuing unit 132 or the management unit 134. For example, the issuing unit 132 may set a balance dedicated to the prepaid card when the prepaid card is issued. Furthermore, the management unit 134 may set a balance dedicated to the prepaid card when starting management of the prepaid card.

(Management Unit 134)
The management unit 134 manages the normal balance, which has no usage restrictions, and the usage-limited balance separately as balances available for payments using a terminal device. At this time, the management unit 134 manages the usage-limited balances set for each usage separately. The management unit 134 also manages the usage-limited balances set for each affiliated store separately. For example, the management unit 134 manages the corporate brand-limited balances set for each corporate brand separately. The management unit 134 also manages the product brand-limited balances set for each product brand separately. The management unit 134 also manages the usage-limited balances set for each user U separately.

In addition, when user U uses the person-to-person remittance function to remit a specified amount from user U's limited use balance to another user F, the management unit 134 transfers the remitted amount to the limited use balance of the other user F that corresponds to user U's limited use balance.

The management unit 134 also manages the limited use balance in association with the prepaid card, and when user U transfers the prepaid card to another user F, the entire amount of the limited use balance associated with the prepaid card is transferred from user U's limited use balance to the other user F's limited use balance.

The management unit 134 also manages the prepaid card held by the user U. For example, the management unit 134 manages the prepaid card issued to the user U by the issuing unit 132. Furthermore, the management unit 134 manages the balance of the prepaid card (limited-use balance). At this time, the management unit 134 separately manages the balance of payment (electronic payment) using the terminal device 10 and the balance of the prepaid card. That is, the management unit 134 separately manages the balance for payment in normal electronic payment and the balance for payment with the prepaid card. The management unit 134 also manages the balance of the prepaid card for each affiliated store separately. That is, the management unit 134 separately manages the balance for each prepaid card.

Furthermore, when the payment processing unit 135 performs payment processing, the management unit 134 determines whether or not a prepaid card is applied to the transaction object to be paid. That is, the management unit 134 applies a prepaid card to the transaction object to be paid in conjunction with and in cooperation with the payment processing unit 135. Note that, in practice, the payment processing unit 135 may apply a prepaid card to the transaction object to be paid in conjunction with and in cooperation with the management unit 134. Furthermore, when a prepaid card is applied to the transaction object to be paid, the management unit 134 manages the balance of the prepaid card. Furthermore, the management unit 134 manages the expiration date of the prepaid card.

In addition, when user U of the terminal device 10 transfers a prepaid card held by user U to another user using the person-to-person remittance 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. That is, when user U presents a prepaid card to another user, the management unit 134 transfers the balance of the prepaid card from the account of user U to the account of the other user. In reality, the management unit 134 may transfer the account itself linked to the prepaid card from user U to the other user. Note that in the above explanation, user U and the other user may be interchanged. Note that when user U transfers a prepaid card from another user, if user U already holds a prepaid card identical to the transferred prepaid card, the management unit 134 may add the balance of the transferred prepaid card to the balance of the prepaid card. Alternatively, the balance of the prepaid card already owned and the balance of the transferred prepaid card may be managed separately.

(Payment Processing Unit 135)
The payment processing unit 135 performs payment processing when the user U makes a payment (electronic payment) using the terminal device 10 with the payment app. For example, the payment processing unit 135 performs payment processing by transferring electronic money from the account of the user U to the account of the affiliated store in accordance with a payment request from the user U.

In this embodiment, when the user U purchases and uses a transaction object (goods, services) at a store where a prepaid card can be used, and makes a payment (electronic payment) using the terminal device 10 via a payment app, the payment processing unit 135 performs the payment process by applying the prepaid card. In other words, when making a payment at an affiliated store, the payment processing unit 135 performs the payment process using the balance of the prepaid card corresponding to the affiliated store.

At this time, the payment processing unit 135 acquires store information indicating the store when making a payment using the terminal device 10, and automatically applies a prepaid card that can be used at the store among the prepaid cards held by the user U.

Alternatively, when a prepaid card is used by the user U when a payment (electronic payment) is made using the terminal device 10 with the payment processing unit 135, the payment processing unit 135 applies the prepaid card to perform the payment processing. For example, when a prepaid card-specific code for using a prepaid card installed in a store is read by the terminal device 10 when a payment is made using the terminal device 10, the payment processing unit 135 applies the prepaid card to perform the payment processing. Alternatively, when a prepaid card-specific code for using a prepaid card displayed on the terminal device 10 is read by the store terminal when a payment is made using the terminal device 10, the payment processing unit 135 applies the prepaid card to perform the payment processing.

Furthermore, when the balance of the prepaid card corresponding to the affiliated store is insufficient at the time of payment at the affiliated store, the payment processing unit 135 performs the payment process by charging the balance of the prepaid card from the balance for payment using the terminal device 10. Alternatively, when the balance of the prepaid card corresponding to the affiliated store is insufficient at the time of payment at the affiliated store, the payment processing unit 135 performs the payment process using the balance for payment using the terminal device 10. Note that when the balance of the prepaid card is insufficient, the payment processing unit 135 may inquire of the user U as to whether to pay the shortfall by recharging or normal electronic payment, and when permission is obtained, perform recharging or normal electronic payment, or may perform recharging or normal electronic payment automatically.

In other words, when the limited-use balance is insufficient at the time of payment for a particular use, the payment processing unit 135 charges the limited-use balance from the normal balance to perform the payment process. Alternatively, when the limited-use balance is insufficient at the time of payment for a particular use, the payment processing unit 135 uses the normal balance to perform the payment process.

(Estimation unit 136)
The estimation unit 136 estimates a prepaid card suitable for user U based on the attribute information and various historical information of user U. 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 the attribute information and historical information of user U are input. Then, the estimation unit 136 inputs the attribute information and various historical information of user U into the prepaid card estimation model, and estimates a prepaid card suitable for user U based on the output information.

For example, the estimation unit 136 creates a trained model that estimates a prepaid card suitable for user U by machine learning using a recurrent neural network (RNN) or a long short-term memory (LSTM). Note that the model can be of any type and any format. For example, the estimation unit 136 may employ a support vector machine (SVM) or a deep neural network (DNN) as a model. Here, the DNN may be a convolutional neural network (CNN) or an RNN. The model may also be realized by combining multiple models, such as a model that combines a CNN and an RNN.

Note that the RNN and LSTM may be neural networks based on an attention mechanism. The estimation unit 136 may also use a similar natural language processing model. It may also use data mining or other machine learning algorithms. The estimation unit 136 can learn the model using the various learning methods described above.

(Providing unit 137)
The providing unit 137 provides information on a prepaid card suitable for the user U to the terminal device 10 of the user U via the communication unit 110. For example, the prepaid card suitable for the user U estimated by the estimation unit 136 is preferentially posted in a prepaid card sales corner in a payment app used by the user U. Alternatively, the providing unit 137 provides a link to a purchase screen for the prepaid card suitable for the user U estimated by the estimation unit 136 to the terminal device 10 of the user U by push notification.

The timing at which the providing unit 137 provides information about a prepaid card suitable for the user U may be when the user U enters a store where the prepaid card can be used, or when the user U purchases and uses a desired transaction object (goods, services) a predetermined number of times at an affiliated store where the prepaid card can be used. The predetermined number of times may be one time or multiple times.

In addition, when a prepaid card is presented (transferred) as a gift from user U to another user, the providing unit 137 notifies the other user that the prepaid card has been transferred from user U. For example, the providing unit 137 notifies the terminal device 10 of the other user of information regarding user U who transferred the prepaid card and information regarding the transferred prepaid card.

The providing unit 137 also notifies the user U of information regarding the prepaid card held by the user U at a predetermined timing in order to prevent the user U from forgetting to use the prepaid card. In other words, the providing unit 137 also functions as a notification unit that notifies the user U of the existence of a prepaid card in order to encourage the use of the prepaid card.

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

In addition, when the expiration date of the prepaid card approaches, the providing 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. In other words, the providing unit 137 also functions as an expiration date notification unit that notifies the terminal device 10 of the expiration date of the prepaid card.

In practice, the providing unit 137 may notify information regarding a prepaid card held by the user U in response to a request from the terminal device 10. For example, when the terminal device 10 detects that the user U has approached or entered an affiliated store, made a payment, etc., it notifies the payment server 100 of location information. Then, the providing unit 137 of the payment server 100 identifies the affiliated store according to the location information from the terminal device 10, and notifies the terminal device 10 of information regarding a prepaid card that can be used at the affiliated store.

5. Processing Procedure
Next, a processing procedure performed by the terminal device 10 and the payment server 100 according to the embodiment will be described with reference to FIGS.
[5-1. Prepaid card management processing procedure]
First, a processing procedure of prepaid card management according to the embodiment will be described with reference to Fig. 11. Fig. 11 is a flowchart showing the processing procedure of prepaid card management 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.

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

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

Next, the management unit 134 of the payment server 100 secures an area for the prepaid card-only balance (step S103). Here, the management unit 134 sets up an account or data area for managing the prepaid card-only balance (limited-use balance) separately from the balance for normal electronic payments. In other words, the balance for normal electronic payments and the balance for the prepaid card are independent. In addition, the balance for the prepaid card is set for each prepaid card. In other words, the balance for the prepaid card is independent for each prepaid card.

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

Then, the management unit 134 of the payment server 100 determines whether the user U has received a prepaid card from another person (step S105). In other words, the management unit 134 determines whether the user U has received a prepaid card as a gift from another person.

When user U has received a prepaid card from another person (step S105; Yes), the management unit 134 of the payment server 100 secures an area for the balance of the prepaid card (return to step S103) and also manages the prepaid card transferred to user U from the other person (step S104). Note that when user U already has a prepaid card identical to the transferred prepaid card, the management unit 134 may add the balance of the transferred prepaid card to the balance of the prepaid card. Conversely, when user U has not received a prepaid card from another person (step S105; No), the management unit 134 of the payment server 100 proceeds to the next process (proceed to step S106).

Then, the management unit 134 of the payment server 100 determines whether or not the user U of the terminal device 10 has used the person-to-person remittance function of the payment app to transfer the prepaid card held by the user U to another user (step S106). For example, the management unit 134 determines whether or not the user U operates the terminal device 10 and presses the "gift" button displayed for each prepaid card on a screen displaying a list of the prepaid cards held by the user U. Note that if the management unit 134 of the payment server 100 has not transferred the prepaid card held by the user U to another user (step S106; No), it continues to manage the prepaid card held by the user U and ends the series of processes.

When user U of the terminal device 10 transfers a prepaid card held by user U to another user using the person-to-person remittance function of the payment app (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).

Then, the management unit 134 of the payment server 100 releases the area for the prepaid card-only balance that was transferred to the other user (step S108). Then, the series of processes ends.

[5-2. Processing procedure for using prepaid cards]
Next, a processing procedure for using a prepaid card according to the embodiment will be described with reference to Fig. 12. Fig. 12 is a flowchart showing a 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.

As shown in FIG. 12, the provision unit 137 of the payment server 100 notifies the user U of information about the prepaid card held by the user U in order to prevent the user U from forgetting to use the prepaid card (step S111). For example, the provision unit 137 notifies the terminal device 10 of prepaid cards that can be used in stores near the user U's location or stores within the user U's travel range, based on the user U's location information. When the 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 the store. When the user U starts a payment app to make a payment (electronic payment) using the terminal device 10, the terminal device 10 notifies the terminal device 10 of prepaid cards that can be used at the store. When the prepaid card's expiration date is approaching, the provision unit 137 notifies the terminal device 10 of the prepaid card and the expiration date at a predetermined timing, such as two weeks before the expiration date.

Then, the payment processing unit 135 of the payment server 100 judges whether the user U will make a payment for the affiliated store (step S112). For example, the payment processing unit 135 judges whether the user U will visit an affiliated store where a prepaid card can be used and make a payment (electronic payment) using the terminal device 10 at the store. The payment processing unit 135 or the payment processing unit 135 judges whether the product purchased by the user U is a product of the affiliated store when the user makes a payment (electronic payment) using the terminal device 10. In reality, the purchase is not limited to the purchase of a product, and may be the use of a service at the store. Here, if the user U does not make a payment for the affiliated store (step S112; No), the payment processing unit 135 of the payment server 100 performs normal payment processing using the balance for normal electronic payment without applying the prepaid card (step S113).

Next, when user U makes a payment to an affiliated store (step S112; Yes), the payment processing unit 135 of the payment server 100 determines whether or not the balance of the prepaid card of the affiliated store is insufficient (step S114). Here, when the balance of the prepaid card of the affiliated store is sufficient (step S114; No), the payment processing unit 135 of the payment server 100 applies the prepaid card of the affiliated store to the payment to the affiliated store and performs the payment process using the balance of the prepaid card of the affiliated store (step S115).

On the other hand, if the balance of the prepaid card of the affiliated store 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 prepaid card of the affiliated store (step S116).

If the payment processing unit 135 of the payment server 100 does not recharge the prepaid card of the affiliated store (step S116; No), it does not apply the prepaid card to the payment related to the affiliated store, but performs normal payment processing using the balance for normal electronic payment (step S113).

On the other hand, when recharging a prepaid card of an affiliated store (step S116; Yes), the payment processing unit 135 of the payment server 100 applies the prepaid card of the affiliated store to the payment related to the affiliated store and performs the payment process using the balance of the prepaid card of the affiliated store (step S115).

6. Modifications
The above-described terminal device 10 and the payment server 100 may be implemented in various different forms other than the above-described embodiment. Therefore, the following describes modified examples of the embodiment.

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 stand-alone manner (by the terminal device 10 alone). In this case, the terminal device 10 is assumed to have the functions of the payment server 100 in the above embodiment. Also, in the above embodiment, since the terminal device 10 is linked to the payment server 100, from the perspective of the user U, it appears that 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.

In addition, in the above embodiment, when the terminal device 10 displays a list of prepaid cards owned by the user U, the terminal device 10 may automatically sort (rearrange) the prepaid cards owned by the user U in order of frequency of use or in order of the closest expiration date at any time. Alternatively, the terminal device 10 may sort (rearrange) the prepaid cards owned by the user U in response to an operation by the user U.

In addition, in the above embodiment, when displaying a list of prepaid cards owned by user U, terminal device 10 may display only those prepaid cards owned by user U that meet certain conditions selected and specified by user U.

In addition, in the above embodiment, user U may present a prepaid card given to him by another user as a gift to another user. In other words, once a prepaid card given to him by another user becomes a prepaid card owned by user U, user U can then freely present it as a gift to another user as a prepaid card owned by user U.

In addition, in the above embodiment, the prepaid card that is exclusive to affiliated stores is merely one example. In reality, the prepaid card may be managed in association with a specific purpose, rather than with an affiliated store.

7. Effects
As described above, the information processing device (terminal device 10 or payment server 100) according to the present application comprises a setting unit 133 that sets a use-limited balance, which has limited uses, in addition to a normal balance, which has no use-limiting purposes, as a balance available for payment using the terminal device 10, and a management unit 134 that manages the normal balance and the use-limited balance separately.

The setting unit 133 also sets the limited use balance for each purpose. The management unit 134 then manages the limited use balance set for each purpose individually.

In addition, the setting unit 133 sets a limited use balance for each affiliated store of the payment service. The management unit 134 then manages the limited use balance set for each affiliated store individually.

The setting unit 133 also 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.

In addition, when user U uses the person-to-person remittance function to remit a specified amount from user U's limited use balance to another user F, the management unit 134 transfers the remitted amount to the limited use balance of the other user F that corresponds to user U's limited use balance.

The management unit 134 also manages the limited use balance in association with the prepaid card, and when user U transfers the prepaid card to another user F, the entire amount of the limited use balance associated with the prepaid card is transferred from user U's limited use balance to the other user F's limited use balance.

The information processing device according to the present application further includes a payment processing unit that, when the limited-use balance is insufficient at the time of payment for a use, charges the limited-use balance from the normal balance to perform payment processing.

Alternatively, the information processing device according to the present application further includes a payment processing unit that performs payment processing using the normal balance when the limited-use balance is insufficient at the time of payment for the use.

From another perspective, the information processing device (terminal device 10 or payment server 100) according to the present application includes a setting unit 133 that sets an affiliated store-limited balance that limits the affiliated store that can be used as a balance available for payment using the terminal device 10, in addition to a normal balance that does not limit the affiliated store that can be used, and a management unit 134 that manages the normal balance and the affiliated store-limited balance separately.

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

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

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 a payment using the terminal device 10, and a management unit 134 that manages the balance of the payment using the terminal device 10 and the balance of the prepaid card separately.

In addition, the issuing unit 132 issues a prepaid card for each affiliated store. The management unit 134 then manages the balance of the prepaid card individually for each affiliated store.

In addition, the information processing device according to the present application further includes a payment processing unit 135 that performs payment processing using the balance of a prepaid card corresponding to the affiliated store when making a payment at the affiliated store.

In addition, when the balance of the prepaid card corresponding to the affiliated store is insufficient at the time of payment at the affiliated store, the payment processing unit 135 charges the balance of the prepaid card from the balance for payment using the terminal device 10 to perform the payment processing.

Alternatively, when a payment is made at an affiliated store and the balance of the prepaid card corresponding to the affiliated store is insufficient, the payment processing unit 135 performs the payment process using the balance for payment made using the terminal device 10.

In addition, when user U of terminal device 10 uses the person-to-person remittance function to transfer a prepaid card held by user U to another user, the management unit 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.

The information processing device according to the present application further includes a notification unit 133 that notifies the terminal device 10 of the prepaid cards that can be used at a store when the user U enters the store where the prepaid cards can be used.

By using any one or a combination of the above-mentioned processes, the information processing device according to the present application can manage a limited-use balance as a balance that can be used for electronic payments. This makes it possible to provide a prepaid card that can only be used at affiliated stores of the electronic payment service. In addition, the card can be used in conjunction with payments when making payments at affiliated stores that hold the prepaid card. In addition, the user can be allowed to select whether or not to recharge the card when a payment exceeds the charged balance. In addition, the affiliated store can provide a My Prepaid Card UI with a unique design. In addition, a premium can be added using affiliated store funds. Furthermore, the prepaid card can be presented as a gift by person-to-person remittance.

8. Hardware Configuration
Moreover, the terminal device 10 and the payment server 100 according to the above-described embodiment are realized by a computer 1000 having a configuration as shown in Fig. 13, for example. The payment server 100 will be described below as an example. Fig. 13 is a diagram showing an example of a hardware configuration. The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which a calculation device 1030, a primary storage device 1040, a secondary storage device 1050, an output I/F (Interface) 1060, an input I/F 1070, and a network I/F 1080 are connected by a bus 1090.

The arithmetic device 1030 operates based on programs stored in the primary storage device 1040 and the secondary storage device 1050, programs read from the input device 1020, and the like, and executes various processes. The arithmetic device 1030 is realized, for example, by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or the like.

The primary storage device 1040 is a memory device such as a RAM (Random Access Memory) that primarily stores data used by the arithmetic device 1030 for various calculations. The secondary storage device 1050 is a storage device in which data used by the arithmetic device 1030 for various calculations and various databases are registered, and is realized by a ROM (Read Only Memory), a HDD (Hard Disk Drive), a SSD (Solid State Drive), a flash memory, or the like. The secondary storage device 1050 may be an internal storage device or an external storage device. The secondary storage device 1050 may be a removable storage medium such as a USB memory or a SD (Secure Digital) memory card. The secondary storage device 1050 may be a cloud storage device (online storage device), a NAS (Network Attached Storage), a file server, or the like.

The output I/F 1060 is an interface for transmitting information to be output to an output device 1010 that outputs various types of information, such as a display, projector, printer, etc., and is realized by a connector conforming to a standard such as USB (Universal Serial Bus), DVI (Digital Visual Interface), or HDMI (registered trademark) (High Definition Multimedia Interface). The input I/F 1070 is an interface for receiving information from various input devices 1020, such as a mouse, keyboard, keypad, button, scanner, etc., and is realized by a USB, etc.

In addition, the output I/F 1060 and the input I/F 1070 may be wirelessly connected to the output device 1010 and the input device 1020, respectively. That is, the output device 1010 and the input device 1020 may be wireless devices.

The output device 1010 and the input device 1020 may be integrated together, such as a touch panel. In this case, the output I/F 1060 and the input I/F 1070 may also be integrated together as an input/output I/F.

The input device 1020 may be a device that reads information from, for example, an optical recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a 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.

The network I/F 1080 receives data from other devices via the network N and sends it to the computing device 1030, and also transmits data generated by the computing device 1030 to other devices via the network N.

The arithmetic unit 1030 controls the output device 1010 and the input device 1020 via the output I/F 1060 and the input I/F 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.

For example, when the computer 1000 functions as the payment server 100, the arithmetic unit 1030 of the computer 1000 realizes the functions of the control unit 130 by executing a program loaded onto the primary storage device 1040. The arithmetic unit 1030 of the computer 1000 may also load a program acquired from another device via the network I/F 1080 onto the primary storage device 1040 and execute the loaded program. The arithmetic unit 1030 of the computer 1000 may also cooperate with other devices via the network I/F 1080 and use the functions and data of a program by calling them from other programs of the other devices.

[9. Other]
Although the embodiments of the present application have been described above, the present invention is not limited to the contents of these embodiments. The above-described components include those that can be easily imagined by a person skilled in the art, those that are substantially the same, and those that are within the so-called equivalent range. Furthermore, the above-described components can be appropriately combined. Furthermore, various omissions, substitutions, or modifications of the components can be made without departing from the spirit of the above-described embodiments.

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 using known methods. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

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

For example, the payment server 100 described above may be realized by multiple server computers, and depending on the function, the configuration can be flexibly changed, such as by calling an external platform using an API (Application Programming Interface) or network computing.

The above-described embodiments and variations can be combined as appropriate to the extent that they do not cause inconsistencies in the processing content.

The above-mentioned "section, module, unit" can be read as "means" or "circuit." For example, an acquisition unit can be read as an acquisition means or an acquisition circuit.

REFERENCE SIGNS LIST 1 Information processing system 10 Terminal device 100 Payment server 110 Communication unit 120 Storage unit 121 User information database 122 History information database 123 Card information database 124 Payment information database 130 Control unit 131 Acquisition unit 132 Issuance unit 133 Setting unit 134 Management unit 135 Payment processing unit 136 Estimation unit 137 Provision unit

Claims (7)

a setting unit that sets a limited-use balance, which is a balance available for payment via a payment application of a terminal device, in addition to a normal balance, which is not limited to a use;
a management unit that manages the normal balance and the limited use balance separately within the payment application;
a payment processing unit that automatically applies either a payment using the normal balance or a payment using a normal electronic payment corresponding to a credit card payment, or a payment using the limited-use balance, depending on the purpose indicated by payment information at the time of payment via a payment application on the terminal device; and
An information processing device comprising: The information processing device according to claim 1, characterized in that, when the limited use balance is insufficient at the time of payment for the purpose for which the limited use balance is to be paid, the payment processing unit automatically applies the payment by the normal electronic payment to perform the payment processing. The information processing device according to claim 1, characterized in that, when the limited use balance is insufficient at the time of payment for the purpose for which the limited use balance is to be paid, the payment processing unit performs a payment process to cover the shortfall by paying the shortfall through the normal electronic payment. The information processing device according to claim 1, characterized in that, when the limited use balance is insufficient at the time of payment for the purpose for which the limited use balance is to be paid, the payment processing unit charges the shortfall from the normal balance to the limited use balance and performs the payment processing. The information processing device according to claim 1, characterized in that, when the limited use balance is insufficient at the time of payment for the purpose for which the limited use balance is to be paid, the payment processing unit performs payment processing using the normal balance to make up the shortfall. An information processing method executed by an information processing device,
a setting step of setting a limited-use balance, which is a balance available for payment via a payment application of a terminal device, in addition to a normal balance, which is not limited to a use;
a management step of managing the normal balance and the limited use balance separately within the payment application;
a payment processing step of automatically applying either a payment using the normal balance or a normal electronic payment corresponding to a credit card payment, or a payment using the limited-use balance, according to the purpose indicated by the payment information at the time of payment via the payment application of the terminal device;
13. An information processing method comprising: a setting step of setting a limited-use balance, which is a balance available for payments via a payment application of a terminal device, in addition to a normal balance, which is not limited to a particular use;
a management procedure for managing the normal balance and the limited use balance separately within the payment application;
a payment processing procedure for automatically applying either a payment using the normal balance or a payment using a normal electronic payment corresponding to a credit card payment, or a payment using the limited-use balance, depending on the purpose indicated by payment information at the time of payment via a payment application on the terminal device;
An information processing program for causing a computer to execute the above.

Images