Prepaid card system, method of providing prepaid card services, and program

Abstract

To improve user convenience. [Solution] The acquisition unit (101) of the prepaid card system acquires source means identification information that can identify the source means that will be the source of funds for the prepaid card, and which is associated with prepaid card identification information that can identify the prepaid card. The charge execution unit (101) performs a charge on the prepaid card based on the source means identification information associated with the prepaid card identification information.

Description

Technical Field

[0001] The present disclosure relates to a prepaid card system, a method for providing a prepaid card service, and a program.

Background Art

[0002] Conventionally, a prepaid card is known as one of the prepayment settlement means. For example, in Patent Document 1, a POS terminal that reads a rechargeable prepaid card displays the remaining balance of the prepaid card. When the user designates the recharge amount of the prepaid card to the POS terminal and performs an operation for recharge, the recharge of the prepaid card is executed based on the recharge amount designated by the user. A POS system is described.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the technology of Patent Document 1, every time the user executes the recharge of the prepaid card, the user has to designate the source means that is the source of the prepaid card from the POS terminal to execute the recharge. Since the technology of Patent Document 1 is troublesome for the user, the convenience of the user cannot be sufficiently improved.

[0005] One of the objectives of the present disclosure is to improve the convenience of the user.

Means for Solving the Problems

[0006] The prepaid card system relating to this disclosure includes a fund source identification information that can identify the fund source that serves as the source of funds for a prepaid card, an acquisition unit that acquires the fund source identification information associated with prepaid card identification information that can identify the prepaid card, and a charge execution unit that performs charging of the prepaid card based on the fund source identification information associated with the prepaid card identification information. [Effects of the Invention]

[0007] This disclosure can improve user convenience. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the hardware configuration of a prepaid card system. [Figure 2] This figure shows an example of a screen displayed on the first user terminal. [Figure 3] This figure shows an example of a screen displayed on the first user terminal. [Figure 4] This figure shows an example of a screen displayed on the first user terminal. [Figure 5] This figure shows an example of a screen displayed on the second user terminal. [Figure 6] This figure shows an example of the functions that can be implemented with a prepaid card system. [Figure 7] This figure shows an example of a user database. [Figure 8] This figure shows an example of the process performed by a prepaid card system. [Figure 9] This figure shows an example of the process performed by a prepaid card system. [Figure 10] This figure shows an example of a function that can be achieved through modification. [Figure 11] This figure shows an example of the screen displayed on the first user terminal in the modified example 1. [Figure 12] This figure shows an example of the screen displayed on the first user terminal in the modified example 3. [Figure 13] This figure shows an example of the screens displayed on the first and second user terminals in the modified example 4. [Figure 14] This figure shows an example of the screen displayed on the first user terminal in variation 5. [Figure 15] This figure shows an example of the screen displayed on the second user terminal in the modified example 7. [Figure 16] This figure shows an example of the list screen for variation 14. [Modes for carrying out the invention]

[0009] [1. Hardware configuration of the prepaid card system] This disclosure describes an example of an embodiment of a prepaid card system, a method for providing prepaid card services, and a program. Figure 1 shows an example of the hardware configuration of a prepaid card system. For example, the prepaid card system 1 includes a server 10, a first user terminal 20A, and a second user terminal 20B. Each of the server 10, the first user terminal 20A, and the second user terminal 20B is connected to a network N such as the Internet or a LAN. Note that there may be multiple instances of at least one of the server 10, the first user terminal 20A, and the second user terminal 20B.

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

[0011] The first user terminal 20A is a computer of the first user. For example, the first user terminal 20A is a smartphone, a tablet, a personal computer, or a wearable terminal. The first user terminal 20A includes a control unit 21A, a storage unit 22A, a communication unit 23A, an operation unit 24A, and a display unit 25A. The hardware configurations of the control unit 21A, the storage unit 22A, and the communication unit 23A may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The operation unit 24A is an input device such as a touch panel or a mouse. The display unit 25A is a display such as a liquid crystal or an organic EL.

[0012] The second user terminal 20B is a computer of the second user. The second user is a user different from the first user. In the present embodiment, a case where the second user is a family member of the first user is taken as an example, but the second user may not be a family member of the first user. For example, the second user terminal 20B is a smartphone, a tablet, a personal computer, or a wearable terminal. The second user terminal 20B includes a control unit 21B, a storage unit 22B, a communication unit 23B, an operation unit 24B, and a display unit 25B. The hardware configurations of the control unit 21B, the storage unit 22B, the communication unit 23B, the operation unit 24B, and the display unit 25B may be the same as those of the control unit 21A, the storage unit 22A, the communication unit 23A, the operation unit 24A, and the display unit 25A, respectively.

[0013] Note that the programs stored in the storage units 12, 22A, and 22B may be supplied to the server 10, the first user terminal 20A, or the second user terminal 20B via the network N. Further, at least one of a reading unit (for example, a memory card slot) for reading a computer-readable information storage medium and an input / output unit (for example, a USB port) for inputting / outputting data to / from an external device may be included in the server 10, the first user terminal 20A, or the second user terminal 20B. For example, a program stored in an information storage medium may be supplied to the server 10, the first user terminal 20A, or the second user terminal 20B via at least one of the reading unit and the input / output unit.

[0014] Also, the prepaid card system 1 may include at least one computer. The computer included in the prepaid card system 1 is not limited to the example of FIG. 1. For example, the prepaid card system 1 may include only the server 10. In this case, the first user terminal 20A and the second user terminal 20B exist outside the prepaid card system 1. The prepaid card system 1 may include the server 10 and other computers not shown in FIG. 1 (for example, the server computer of the point service described later).

[0015] [2. Overview of Prepaid Card System] In this embodiment, the first user holds the original fund means that serves as the original fund for the prepaid card. The prepaid card is a card that has a balance used for settlement. The prepaid card is a type of prepaid settlement means. The prepaid card can also be said to be a type of electronic money. In this embodiment, the case where the prepaid card is a virtual card is taken as an example, but the prepaid card may be a physical card (for example, an IC card or a magnetic card). The IC chip of the first user terminal 20A or the IC chip of the second user terminal 20B may be used as the prepaid card.

[0016] The original fund is the funds that are the source of the balance of the prepaid card. The original fund means is the settlement means used as the original fund for the prepaid card. In this embodiment, since a rechargeable prepaid card is taken as an example, the original fund means is the settlement means used for the recharge of the prepaid card. The original fund means can also be said to be the settlement means of the recharge source. The original fund means can be any settlement means. For example, the original fund means may be a credit card, other cards other than credit cards (for example, debit cards or other prepaid cards), bank accounts, other accounts other than bank accounts, electronic money, balances not called electronic money, cryptocurrency, wallets, or other settlement means.

[0017] In this embodiment, we take the example of a credit card held by the first user that constitutes the source of funds. Therefore, any section describing the credit card held by the first user can be read as the source of funds. The credit card held by the first user is a credit card in the name of the first user. The credit card may be a physical card, like a prepaid card, or it may be a virtual card.

[0018] For example, the first user logs into the credit card service provided by the card company that issued the credit card by operating the first user terminal 20A to access the server 10. Once the first user logs into the credit card service, the first user terminal 20A communicates with the server 10 to display a screen on the display unit 25A that allows the first user to use the functions of the credit card service.

[0019] Figures 2 to 4 show examples of screens displayed on the first user terminal 20A. In this embodiment, the screen displayed on the first user terminal 20A is shown as an example when it is displayed on a credit card application, which is an application for credit card services. However, the screen displayed on the first user terminal 20A may be displayed on other applications other than the credit card application, or on a browser. In this embodiment, the first user is shown as an example when he uses the card issuance function of the credit card service to issue various cards such as prepaid cards.

[0020] For example, when the first user selects the card issuance function, the first user terminal 20A displays the card issuance screen SC1 on the display unit 25A, as shown in the upper left of Figure 2, for the first user to use the card issuance function. For example, the first user can instruct the issuance of an ETC card, the second user's credit card, the first user's prepaid card, and the second user's prepaid card from the card issuance screen SC1.

[0021] Hereafter, the prepaid card of the first user will be referred to as the first prepaid card. The prepaid card of the second user will be referred to as the second prepaid card. When the first prepaid card and the second prepaid card are not specifically distinguished, they will simply be referred to as prepaid cards. When the first user and the second user are not specifically distinguished, they will simply be referred to as users. In this embodiment, the card issuance function for issuing the first prepaid card and the second prepaid card will be described.

[0022] For example, when the first user selects display area A10 for issuing the first prepaid card, the first user terminal 20A displays the first issuance screen SC2 on the display unit 25A, as shown in the upper right of Figure 2, which accepts input of information necessary for issuing the first prepaid card. The first user enters the name of the first prepaid card and whether or not to receive an email notification when the first prepaid card is used on the first issuance screen SC2. If there are other necessary items for issuing the first prepaid card, the first issuance screen SC2 may also accept input of those other necessary items.

[0023] For example, when the first user enters the necessary information on the first issuance screen SC2 and selects button B20, the first user terminal 20A displays the first issuance screen SC2 on the display unit 25A to confirm the issuance of the first prepaid card, as shown in the lower left of Figure 2. When the first user confirms the necessary information and selects button B21, the issuance of the first prepaid card is completed. As shown in the lower right of Figure 2, the first user terminal 20A displays the first issuance screen SC2 on the display unit 25A to indicate that the issuance of the first prepaid card is complete.

[0024] In this embodiment, the first user is required to perform a predetermined authentication in order to begin using the first prepaid card. Hereafter, this authentication will be referred to as the first authentication. The first authentication may be any authentication method, but it is a different authentication method from the login authentication used by the first user to log in to the credit card service. For example, the first authentication may be knowledge authentication, possession authentication, or biometric authentication. The first authentication may also be multi-factor authentication, which combines multiple authentication methods. In this embodiment, we will take as an example the case where one-time password authentication, which is an example of knowledge authentication, corresponds to the first authentication.

[0025] For example, when the first user selects button B22, the first user terminal 20A displays the first authentication screen SC3 for the first authentication on the display unit 25A, as shown in the upper left of Figure 3. In this embodiment, the first authentication is performed based on the phone number that the first user has previously registered with the credit card service. When the first user selects button B30, the server 10 sends a one-time password to the first user's phone number via SMS (Short Message Service) message.

[0026] For example, the first user operates the first user terminal 20A to verify the one-time password shown in the SMS message. As shown in the upper right of Figure 3, the first user terminal 20A displays the first authentication screen SC3, which accepts the input of the one-time password, on the display unit 25A. When the first user enters the one-time password into the input form F31 and selects button B32, the first authentication is performed. The first user can also resend the one-time password by selecting button B33.

[0027] For example, when the server 10 verifies the validity of the one-time password, the first user terminal 20A displays a first issuance screen SC2 on the display unit 25A, indicating that the first prepaid card is now available, as shown in the lower left of Figure 3. When the first user selects a function to view a list of prepaid cards from among the functions of the credit card service, the first user terminal 20A displays a list screen SC4 showing a list of prepaid cards on the display unit 25A, as shown in the lower right of Figure 3. The list screen SC4 includes a display area A40 showing the first prepaid card.

[0028] For example, display area A40 shows the name, balance, part of the card number, and expiration date of the first prepaid card. The first user can top up the first prepaid card using their own credit card by selecting button B400. The first user can check the card number of the first prepaid card by selecting button B401. In the example in the lower right of Figure 3, the first user has already performed the first authentication, so button B402 for the first authentication is disabled. If the first user has not yet performed the first authentication, they can perform the first authentication by selecting button B402.

[0029] In this embodiment, since the first prepaid card is a virtual card, the first user can use the first prepaid card without possessing a physical card. For example, the first prepaid card may be usable for online payments such as e-commerce services. The first prepaid card may be set as the payment source for a payment app, which is an application of a payment service that handles electronic payments. The first prepaid card may be usable for a payment method called token payment. The first prepaid card may be usable for other payment methods.

[0030] In this embodiment, the first user can also issue a second prepaid card for a second user, who is a family member of the first user. For example, as shown in the upper left of Figure 4, when the first user selects the display area A11 for issuing the second prepaid card, the first user terminal 20A displays a second issuance screen SC5 on the display unit 25A, as shown in the upper right of Figure 4, which accepts input of the information necessary for issuing the second prepaid card. In the example in the upper right of Figure 4, the general configuration of the second issuance screen SC5 is the same as that of the first issuance screen SC2 in the upper right of Figure 2. The information necessary for issuing the second prepaid card may be the same as or different from the information necessary for issuing the first prepaid card.

[0031] For example, when the first user enters the necessary information on the second issuance screen SC5 and selects button B50, the first user terminal 20A displays the second issuance screen SC5 on the display unit 25A to confirm the issuance of the second prepaid card, as shown in the lower left of Figure 4. In the example in the lower left of Figure 4, the general structure of the second issuance screen SC5 is the same as that of the first issuance screen SC2 in the lower left of Figure 2. In the example in the lower left of Figure 2, the first user enters a string of characters as the name of the second prepaid card to indicate that it is a prepaid card for his son Taro's allowance.

[0032] In this embodiment, the second user is required to perform a predetermined authentication in order to begin using the second prepaid card. Hereafter, this authentication will be referred to as the second authentication. The second authentication may be any authentication method, but it is a different authentication method from the login authentication used by the second user to log in to the prepaid card service. For example, the second authentication may be knowledge authentication, possession authentication, or biometric authentication. The second authentication may also be multi-factor authentication, which combines multiple authentication methods. In this embodiment, we will take the case where security code authentication, which is an example of knowledge authentication, corresponds to the second authentication.

[0033] For example, when the first user selects button B51, the first user terminal 20A displays the second issuance screen SC5 on the display unit 25A, indicating that the issuance of the second prepaid card is complete, as shown in the lower right of Figure 4. In the example in the lower right of Figure 4, the second issuance screen SC5 displays the security code used for the second authentication, along with a message indicating the sharing of the authentication link (for example, a URL for the second authentication), which is the link for the second authentication. Once the second prepaid card is issued, a display area A40 showing the second prepaid card is added to the list screen SC4. The display area A40 showing the second prepaid card may display an image for sharing the authentication link and an image for displaying the security code.

[0034] For example, when the first user selects button B52, the first user terminal 20A performs the process for sharing the authentication link. The authentication link may be shared by any means of sharing. For example, the sharing means may be email, SMS, messaging app, SNS (Social Networking Service), near-field communication, or other means. The first user may share the authentication link for the second prepaid card from the list screen SC4, rather than from the second issuance screen SC5. Once the first user shares the authentication link with the second user, the second user operates the second user terminal 20B to select the authentication link.

[0035] Figure 5 shows an example of a screen displayed on the second user terminal 20B. In this embodiment, the screen displayed on the second user terminal 20B is shown as an example of a screen displayed on a prepaid card app, which is an application for a prepaid card service. However, the screen displayed on the second user terminal 20B may be displayed on an application other than the prepaid card app, or on a browser. If the second user has not downloaded the prepaid card app to the second user terminal 20B, when the second user selects an authentication link, the second user terminal 20B may display a screen for downloading the prepaid card app (for example, a screen from a well-known app store) on the display unit 25B.

[0036] For example, when a second user selects an authentication link, the second user terminal 20B displays a login screen SC6 on the display unit 25B for the second user to log in to the prepaid card service, as shown in the upper left of Figure 5. If the second user has their own user ID, they select display area A60 to log in to the prepaid card service. For example, if the second user does not have their own user ID, they select display area A61 to proceed with the user ID issuance procedure.

[0037] For example, if a second user has a user ID but is using the prepaid card service for the first time, the second user terminal 20B displays a second authentication screen SC7 on the display unit 25B, which accepts the second user's name and date of birth, as shown in the upper right of Figure 5. If the second user has already registered their name and date of birth with the prepaid card service, the display of the second authentication screen SC7 in the upper right of Figure 5 may be omitted.

[0038] For example, when a second user enters their name and date of birth and selects button B70, the second user terminal 20B displays a second authentication screen SC7, which accepts the input of a security code, on the display unit 25B, as shown in the lower left of Figure 5. In this embodiment, we take the case where the first user verbally shares the security code with the second user as an example. When the second user enters the verbally transmitted security code into the input form F71 and selects button B72, the second authentication is performed.

[0039] The security code may also be shared with the second user by other means. For example, the first user may share the security code with the second user by showing the second issuance screen SC5 in the lower right of Figure 4, rather than verbally. The first user may also send the security code to the second user terminal 20B along with the authentication link, or they may share the security code with the second user separately from the authentication link by any of the aforementioned sharing methods.

[0040] For example, when the server 10 verifies the validity of the security code, the second user terminal 20B displays the second authentication screen SC7 on the display unit 25B, indicating that the second prepaid card is now available, as shown in the lower right of Figure 5. When the second user performs an operation to return to the top screen of the prepaid card app, the second user terminal 20B displays the top screen on the display unit 25B for checking information such as the balance of the second prepaid card. When the first user performs a charge on the second prepaid card from the list screen SC4, the balance increased by the charge is reflected on the top screen of the prepaid card app.

[0041] In this embodiment, since the second prepaid card is a virtual card, the second user can use the second prepaid card without possessing a physical card. For example, the second prepaid card may be usable for online payments such as e-commerce services. The second prepaid card may be set as the payment source for a payment app, which is an application of a payment service that handles electronic payments. The second prepaid card may be usable for a payment method called token payment. The second prepaid card may be usable for other payment methods.

[0042] Furthermore, a first user may issue a second prepaid card for each of multiple second users. The process for issuing each second prepaid card may be the same. For example, a first user with two children may issue a second prepaid card for the first child and a second prepaid card for the second child. A first user may also issue a second prepaid card for a second user who is another family member other than a child (e.g., a parent). A first user may issue multiple second prepaid cards for a single second user. A first user may also issue multiple first prepaid cards for their own use. There may be an upper limit on the total number of first and second prepaid cards that a first user can issue.

[0043] As described above, the prepaid card system 1 of this embodiment can charge a prepaid card based on the credit card associated with the prepaid card. Furthermore, the prepaid card system 1 performs a first authentication when a first user starts using the first prepaid card. The prepaid card system 1 performs a second authentication when a second user starts using the second prepaid card. Through these configurations, the prepaid card system 1 enhances security while improving user convenience. The details of the prepaid card system 1 will be described below.

[0044] [3. Functions realized by the prepaid card system] Figure 6 shows an example of the functions realized by the prepaid card system 1. The various components realized by the prepaid card system 1 of this embodiment can be configured by combining them into a single device or by further distributing them among multiple devices.

[0045] Figure 6 shows the functions implemented by the server 10 among the functions implemented by the prepaid card system 1. For example, the server 10 includes a data storage unit 100, a prepaid card issuing unit 101, an acquisition unit 102, a charge execution unit 103, a first authentication unit 104, and a second authentication unit 105. The data storage unit 100 is implemented by a storage unit 12. Each of the prepaid card issuing unit 101, acquisition unit 102, charge execution unit 103, first authentication unit 104, and second authentication unit 105 is implemented by a control unit 11.

[0046] [3-1. Data Storage Unit] The data storage unit 100 stores various data necessary for processing in this embodiment. For example, the data storage unit 100 stores a user database DB containing various information about each of multiple users. In this embodiment, we take the example of a case where information about credit card services and information about prepaid card services are stored in the same user database DB, but this information may be stored in separate user database DBs.

[0047] Figure 7 shows an example of a user database DB. For example, the user database DB stores user information such as user ID, login account, password, telephone number, email address, name and date of birth, credit card information, and prepaid card information. The information stored in the user database DB is not limited to the example in Figure 7. Other information may be stored in the user database DB. For example, the user database DB may store information that can identify whether it is the first user or the second user, credit card usage history, prepaid card usage history, prepaid card charge history, or other information.

[0048] A user ID is an example of user identification information that can identify a user. A login account is also an example of user identification information. A login account is user identification information that a user enters to log in to a payment service. The login account may be freely changed by the user. A user ID is user identification information that is managed separately from the login account. In this embodiment, we take the example of a case where there is a login account separate from the user ID (where there are at least two pieces of user identification information), but there may be only one piece of user identification information. That is, the user ID and login account do not have to be separate. A password is authentication information that is verified during login. The login account and password may be the user's biometric information.

[0049] In this embodiment, we take the example of a case where the prepaid card service is an ancillary service to a credit card service. For example, the prepaid card service is operated by the card company that operates the credit card service. For this reason, we take the example of a case where user identification information such as user ID and login account is common to both the prepaid card service and the credit card service, and the password is also taken as a case where it is common to both the prepaid card service and the credit card service. However, the user identification information and password may not be common to both the prepaid card service and the credit card service, and may be different.

[0050] In the data storage example shown in Figure 7, the first user "Rakuten Daisuke" possesses both a credit card and a first prepaid card. Therefore, not only is his own user ID information stored, but also the credit card information for the credit card that provides the funds for the first prepaid card, and the prepaid card information for the first prepaid card are stored in the user database DB. The first user "Rakuten Daisuke" has also issued a second prepaid card for his child, the second user "Rakuten Taro," so the prepaid card information for the second prepaid card is also associated with the credit card information. In the data storage example shown in Figure 7, the data for the second prepaid card of the second user "Rakuten Taro" exists in two places: in the user information record for "Rakuten Daisuke" and in the user information record for "Rakuten Taro." In this embodiment, of these two data sets, the data in the user information record for "Rakuten Taro," who is the cardholder of the second prepaid card, is considered primary, and the data in the user information record for "Rakuten Daisuke," who is not the cardholder of the second prepaid card, is considered secondary. When the second prepaid card is used by the cardholder "Rakuten Taro," the positive data in the user information record for "Rakuten Taro," who is the same as the cardholder, will be referenced and updated. The secondary data in the user information record for "Rakuten Daisuke," who is different from the cardholder, will have the updated positive data copied and reflected.

[0051] For example, the second user "Rakuten Taro" possesses information such as his / her user ID, but does not possess his / her own credit card (for example, he / she has not reached the age to obtain a credit card), so his / her credit card information is not stored in the user database DB. The second user "Rakuten Taro" possesses a second prepaid card, so the prepaid card information for the second prepaid card is stored in the user database DB. After the second authentication is performed, the prepaid card information for the second prepaid card of the first user "Rakuten Daisuke" may be copied as the prepaid card information for the second prepaid card of the second user "Rakuten Taro". In addition, the credit card information for the first user "Rakuten Daisuke" may be stored in the record for the second user "Rakuten Taro".

[0052] Credit card information is information related to a credit card. For example, credit card information includes the credit card number, expiration date, and cardholder name. Credit card information may also be hashed information. Credit card information can be considered an example of source of payment information. Therefore, wherever "credit card information" is written, it can be read as "source of payment information." If a payment method other than a credit card corresponds to the source of payment, information about that payment method may be stored in the user database DB. Note that for second users who do not have a credit card, credit card information will not be stored in the user database DB.

[0053] Prepaid card information is information relating to a prepaid card. For example, prepaid card information may include the prepaid card number, type (for example, a type that can identify whether it is the first or second prepaid card), name of the prepaid card, expiration date, cardholder name, balance, whether first authentication was performed, a one-time password issued for first authentication, whether second authentication was performed, an authentication link issued for second authentication, a security code issued for second authentication, or other information. Prepaid card information may also be hashed information.

[0054] The information included in the prepaid card information is not limited to the example of this embodiment. The prepaid card information may include information that can identify the second user terminal 20B that performed the second authentication. The second prepaid card may be usable from the second user terminal 20B that performed the second authentication. For example, if the second user logs into the prepaid card service from a second user terminal 20B that has not performed the second authentication, the server 10 may restrict the second user from using the second prepaid card. The prepaid card information may also indicate the user identification information of the first user who issued the second prepaid card. The server 10 may use this user identification information to identify which first user issued the second prepaid card.

[0055] In this embodiment, the user database DB is an example of a database associated with source means identification information that can identify the source means that serves as the source of funds for a prepaid card, and prepaid card identification information that can identify a prepaid card. Therefore, any section describing the user database DB can be read as referring to a database associated with source means identification information and prepaid card identification information. This database may be another database other than the user database DB (for example, a prepaid card database).

[0056] In this embodiment, since the credit card corresponds to the source of funds, the source of funds identification information is information that can identify the credit card. For example, the credit card number corresponds to the source of funds identification information. If a user possesses only one credit card, user identification information such as a user ID or login account may correspond to the source of funds identification information. In the case of a credit card with attached electronic money or point card, the credit card can be identified by the electronic money number or point card number, so the electronic money number or point card number may correspond to the source of funds identification information.

[0057] For example, if a card other than a credit card (e.g., a debit card or another prepaid card) constitutes the source of funds, the source of funds identification information only needs to be information that can identify the other card (e.g., a debit card number or prepaid card number). If a bank account constitutes the source of funds, the source of funds identification information only needs to be information that can identify the bank account (e.g., a financial institution code, branch code, account type, and account number). Similarly, if another payment method constitutes the source of funds, the source of funds identification information only needs to be information that can identify the other payment method.

[0058] In this embodiment, we take the example where the prepaid card number corresponds to the prepaid card identification information. The prepaid card number is an identification number assigned to the prepaid card. The prepaid card number may use the same numbering system as the credit card number, or it may use a different numbering system. The prepaid card identification information may be any information that can identify the prepaid card, and is not limited to the prepaid card number. For example, the prepaid card identification information may not be a number, but information that includes letters or symbols. If a user possesses only one prepaid card, user identification information such as a user ID or login account may correspond to the prepaid card identification information.

[0059] The data stored in the data storage unit 100 is not limited to the above example. The data storage unit 100 may store other data necessary for issuing prepaid cards. For example, the data storage unit 100 may store a program for issuing a one-time password used in first authentication and a program for issuing a security code used in second authentication. The data storage unit 100 may also store data necessary for displaying the card issuance screen SC1, the first issuance screen SC2, the first authentication screen SC3, the list screen SC4, the second issuance screen SC5, the login screen SC6, the second authentication screen SC7, or other screens.

[0060] [3-2. Prepaid Card Issuance Department] The prepaid card issuing unit 101 issues prepaid cards. For example, when the prepaid card issuing unit 101 issues a new prepaid card, it generates prepaid card information for that prepaid card and adds it to the user database DB. Details of the prepaid card information are as described in the description of the data storage unit 100. When a first user performs the procedure for issuing a prepaid card, the prepaid card issuing unit 101 associates the credit card information of the first user's credit card with the prepaid card information of that prepaid card and stores it in the user database DB. The association between credit card information and prepaid card information may be performed retrospectively rather than at the time of issuance of the prepaid card.

[0061] For example, by associating credit card information and prepaid card information from the time of issuance of the prepaid card, the user does not need to register a source of funds, thus increasing user convenience. If there is one source of funds, the charge execution unit 103 described later will charge the prepaid card from that source of funds. If there are multiple sources of funds, multiple sources of funds may be associated with the prepaid card at the time of issuance. In this case, the user can select any source of funds from the multiple sources of funds, thus avoiding situations where charging is not possible due to an unavailable source of funds. In this case, the charge may be made from the source of funds selected from the multiple sources of funds at the time of charging.

[0062] For example, if there are multiple funding sources, the user may be asked to select one funding source to associate with the prepaid card when it is issued. In this case, the charge will be made from the selected funding source. The user may be able to change to another funding source at the time of charging. The user can charge from their preferred funding source and manage them more easily by establishing a one-to-one correspondence between funding sources and prepaid cards.

[0063] [3-3. Acquisition part] The acquisition unit 102 acquires a credit card number (an example of source of funds identification information) that can identify the source of funds for the prepaid card, and a credit card number associated with a prepaid card (an example of prepaid card identification information) that can identify the prepaid card. In this embodiment, since the credit card number and the prepaid card number are directly associated with the user database DB, the acquisition unit 102 refers to the user database DB and acquires the credit card number associated with the prepaid card number.

[0064] Note that credit card numbers and prepaid card numbers may be stored in separate databases. For example, the user ID and credit card number may be stored in the first database, and the user ID and prepaid card number may be stored in the second database. In this case, the credit card number and prepaid card number are indirectly linked through the user ID. The acquisition unit 102 may acquire the credit card number indirectly associated with the prepaid card number.

[0065] [3-4. Charge Execution Unit] The charge execution unit 103 performs a charge on the prepaid card based on the credit card number associated with the prepaid card number. That is, the charge execution unit 103 performs a charge on the prepaid card based on the credit card number associated with the prepaid card to be charged. Charging is the process of increasing the balance. The charging of the prepaid card itself may be performed in the same manner as charging a publicly known prepaid card.

[0066] For example, the charge execution unit 103 executes a credit card payment based on the credit card number for the amount specified by the first user. If the credit card payment is successful, the charge execution unit 103 updates the balance of the prepaid card so that the balance of the prepaid card increases by the amount specified by the first user. Similarly, if a payment method other than a credit card is used as the source of funds, the charge execution unit 103 should execute a payment based on the other payment method and then charge the prepaid card.

[0067] The charging of the second prepaid card may be performed by the second user, or by the first user, as shown in Modification Example 3 described later. In this embodiment, the second user may be able to charge the second prepaid card using the first user's credit card as the source of funds. An embodiment in which the charging execution unit 103 performs the charging of the second prepaid card using the first user's credit card as the source of funds, based on the instructions of the second user, is also within the scope of this disclosure.

[0068] [3-5. First Certification Department] The first authentication unit 104 performs first authentication regarding the commencement of use of the first prepaid card, which is a prepaid card of the first user who possesses a credit card, which is an example of a source of funds. First authentication is an authentication that is a condition for the first user to commence use of the first prepaid card. The first user cannot commence use of the first prepaid card unless first authentication is successful. Since the first user cannot commence use of the first prepaid card unless the first prepaid card is issued, first authentication may also be an authentication that is a condition for whether or not the first prepaid card is issued.

[0069] In this embodiment, we take the case where one-time password authentication corresponds to the first authentication as an example, but the first authentication may be other knowledge authentication methods other than one-time password authentication (for example, non-one-time password authentication or secret question authentication), possession authentication using an item such as a credit card or My Number card, biometric authentication using biometric information such as a face or fingerprint, or a combination thereof. The sections describing the first authentication can be read as referring to authentication using other authentication methods other than one-time password authentication.

[0070] For example, if the first user performs an operation to issue the first prepaid card in the flow shown in Figure 2, the server 10 issues the first prepaid card by generating the prepaid card information for the first prepaid card and storing it in the user database DB. The server 10 stores the prepaid card information for the first prepaid card in the user database DB, associating it with the user ID, login account, and credit card information of the first user who instructed the issuance of the first prepaid card.

[0071] For example, Server 10 issues a prepaid card number for the first prepaid card in a way that does not overlap with other prepaid card numbers. Server 10 sets the expiration date of the first prepaid card to a date a predetermined period after the current date. Server 10 sets the name of the credit card holder to be the name of the first prepaid card holder. Server 10 also sets other items included in the prepaid card information as appropriate. These processes of Server 10 may be executed as the processes of the first prepaid card issuing unit 101A in the modified example 8 described later.

[0072] For example, the first authentication unit 104 issues a one-time password for first authentication. The first authentication unit 104 may store the one-time password in the user database DB as part of the prepaid card information of the first prepaid card. The first authentication unit 104 sends an SMS message containing the one-time password to the first user's phone number. In this embodiment, we take the case where the first user's phone number is stored in the user database DB in advance as an example, but the first user's phone number may be entered by the first user on the spot.

[0073] For example, the first authentication unit 104 receives a one-time password entered by the first user from the first user terminal 20A. The first authentication unit 104 performs the first authentication by determining whether the one-time password received from the first user terminal 20A matches a previously issued one-time password. If they match, the first authentication is successful. If they do not match, the first authentication fails. The first authentication unit 104 updates the prepaid card information so that the prepaid card information indicates the result of the first authentication. For example, if the first authentication is successful, the first authentication unit 104 updates the prepaid card information of the first prepaid card so that the prepaid card information indicates that the first authentication has been performed (that the first authentication was successful).

[0074] If an authentication method other than one-time password authentication corresponds to the first authentication, the first authentication unit 104 may perform the other authentication as the first authentication. The flow of the other authentication may be the same as that of a known authentication method. Once the first authentication is performed by the first authentication unit 104, the server 10 permits the first user to use the first prepaid card. In this embodiment, the use of the first prepaid card is permitted if the prepaid card information indicates success in the first authentication. The server 10 restricts the first user from using the first prepaid card until the first authentication is performed by the first authentication unit 104.

[0075] [3-6. Second Certification Department] The second authentication unit 105 performs a second authentication, which is a prepaid card belonging to a second user different from the first user, relating to the start of use of the second prepaid card, and uses a different authentication method than the first authentication. The second authentication is an authentication that is a condition for the second user to start using the prepaid card. The second user cannot start using the second prepaid card unless the second authentication is successful. Since the second user cannot start using the second prepaid card unless the second prepaid card is issued, the second authentication may also be an authentication that is a condition for whether or not the second prepaid card is issued. Note that the second authentication may be performed by the first user instead of the second user. The second authentication may be performed by both the first user and the second user.

[0076] In this embodiment, we take the case where security code authentication corresponds to the second authentication as an example, but the second authentication may be other knowledge authentication methods other than security code authentication (for example, password authentication that is not a security code, or secret question authentication), possession authentication using an item such as a credit card or My Number card, biometric authentication using biometric information such as a face or fingerprint, or a combination of these. The sections describing the second authentication can be read as referring to authentication using other authentication methods other than security code authentication.

[0077] For example, if the first user performs an operation to issue a second prepaid card in the flow shown in Figure 4, the server 10 issues the second prepaid card by generating the prepaid card information for the second prepaid card and storing it in the user database DB. The server 10 stores the prepaid card information for the second prepaid card in the user database DB, associating it with the user ID, login account, and credit card information of the first user who instructed the issuance of the second prepaid card.

[0078] Furthermore, if the first user possesses multiple credit cards, the credit card information of the credit card selected by the first user from among the multiple credit cards may be associated with the prepaid card information of the second prepaid card. The credit card selected by the first user from among the multiple credit cards will be used as the source of funds for the second prepaid card. Information that can identify which credit card is the source of funds from among the multiple credit cards may be stored in the user database DB. The first user may be able to switch which credit card is used as the source of funds from among the multiple credit cards.

[0079] For example, Server 10 issues a prepaid card number for the second prepaid card in a way that does not overlap with other prepaid card numbers. Server 10 sets the expiration date of the second prepaid card to a date a predetermined period after the current date. Server 10 may designate the name entered by the first user as the name on the second prepaid card, or it may reserve the name on the second prepaid card and designate the second user who performed the second authentication as the name on the second prepaid card. Server 10 also sets other items included in the prepaid card information as appropriate. This series of processes by Server 10 may be executed as the processing of the second prepaid card issuing unit 101B in the modified example 9 described later.

[0080] In this embodiment, the second authentication unit 105 performs a second authentication regarding the start of use of the second prepaid card, which is the second user's prepaid card, based on the second user terminal 20B of the second user, which is different from the first user who holds the source means. For example, the second authentication unit 105 receives input authentication information, which is authentication information entered by the second user, from the second user terminal 20B. The second authentication unit 105 performs a second authentication based on the issued authentication information issued as the correct authentication information in the second authentication and the input authentication information.

[0081] In this embodiment, the security code issued for the second authentication is an example of issued authentication information. Therefore, sections describing the security code issued for the second authentication can be interpreted as referring to issued authentication information. Issued authentication information is the correct authentication information in the second authentication. Issued authentication information is authentication information held on the server 10 side. The security code entered by the second user is an example of input authentication information. Therefore, sections describing the security code entered by the second user can be interpreted as referring to input authentication information. Input authentication information is authentication information that is compared with the issued authentication information in the second authentication.

[0082] For example, the second authentication unit 105 issues a security code for second authentication. The second authentication unit 105 may store the security code in the user database DB as part of the prepaid card information of the second prepaid card. The second authentication unit 105 transmits the security code to the first user terminal 20A. If the first user has entered the second user's email address or phone number when issuing the second prepaid card, the second authentication unit 105 may send the security code to the second user's email address or phone number via email or SMS.

[0083] For example, the second authentication unit 105 receives a security code entered by the second user from the second user terminal 20B. The second authentication unit 105 performs second authentication by determining whether the security code received from the second user terminal 20B matches an issued security code. If they match, second authentication is successful. If they do not match, second authentication fails. The second authentication unit 105 updates the prepaid card information so that the prepaid card information indicates the result of the second authentication. For example, if the second authentication is successful, the second authentication unit 105 updates the prepaid card information of the second prepaid card so that the prepaid card information indicates that the second authentication has been performed (that the second authentication was successful). The second authentication unit 105 may include information that can identify the second user terminal 20B that performed the second authentication (for example, individual identification information, an ID issued by the server 10, or a number in the SIM card) in the prepaid card information. Based on this information, server 10 may permit the use of the second prepaid card from the second user terminal 20B and prohibit the use of the second prepaid card from other second user terminals 20B.

[0084] In this embodiment, the second authentication unit 105 transmits an authentication link related to the second authentication and a security code issued for the second authentication to the first user terminal 20A of the first user. For example, the authentication link includes search information that allows searching for the security code issued as issued authentication information. The search information is information for searching for issued authentication information that is to be compared with the input authentication information entered by the second user. The search information may be any information associated with the issued authentication information. For example, the search information may be the prepaid card number of the second prepaid card, or it may be information such as a temporary ID issued for the second authentication. The search information may also be the user identification information of the first user.

[0085] For example, when the authentication link notified to the second user terminal 20B is selected by the second user terminal 20B, the second authentication unit 105 performs second authentication based on the input authentication information entered by the second user terminal 20B and the issued authentication information. In this embodiment, the prepaid card number of the second prepaid card is included as search information in the authentication link. This allows the server 10 to identify which first user issued the second prepaid card for which second authentication when the second user selects the authentication link. For example, the authentication link may include search information as an argument to the URL.

[0086] For example, when a second user selects an authentication link, the second user terminal 20B sends search information contained in the authentication link to the server 10. The search information may also be included in a request such as an HTTP request. The second authentication unit 105 obtains the search information contained in the authentication link from the second user terminal 20B. The second authentication unit 105 receives the security code entered by the second user from the second user terminal 20B. The second authentication unit 105 performs second authentication by determining whether the security code received from the second user terminal 20B matches the security code stored in the user database DB associated with the search information. If they match, second authentication is successful. If they do not match, second authentication fails. The second authentication unit 105 updates the prepaid card information so that the prepaid card information indicates the result of the second authentication.

[0087] The second authentication unit 105 may also identify which second prepaid card's second authentication is being performed by means other than the authentication link. For example, the second authentication unit 105 may send search information to the first user terminal 20A without using the authentication link. The second user may enter the search information and security code from the second authentication screen displayed on the second user terminal 20B. The second authentication unit 105 may identify which second prepaid card's second authentication is being performed based on the search information entered from the screen. For example, the second user may enter the first user's user identification information, and the second authentication unit 105 may identify which second prepaid card's second authentication is being performed by obtaining the first user's user identification information from the second user terminal 20B.

[0088] Furthermore, the second authentication unit 105 may perform the second authentication based on the first user terminal 20A instead of the second user terminal 20B. That is, the input authentication information may be entered from the first user terminal 20A instead of the second user terminal 20B. Also, if an authentication other than security code authentication corresponds to the second authentication, the second authentication unit 105 may perform the other authentication as the second authentication. The flow of the other authentication may be the same as that of a known authentication. Once the second authentication is performed by the second authentication unit 105, the server 10 allows the second user to use the second prepaid card. The server 10 restricts the second user from using the second prepaid card until the second authentication is performed by the second authentication unit 105.

[0089] [4. Processes performed by the prepaid card system] Figures 8 and 9 illustrate an example of processing performed by the prepaid card system 1. Figures 8 and 9 show the processing related to the issuance of prepaid cards, which is performed by the prepaid card system 1. The control units 11, 21A, and 21B execute programs stored in the storage units 12, 22A, and 22B, respectively, thereby executing the processing shown in Figures 8 and 9. The steps in Figures 8 and 9 represent an example of a method for providing prepaid card services.

[0090] As shown in Figure 8, the first user terminal 20A performs a login process with the server 10 for the first user to log in to the credit card service based on the login account and password entered by the first user and the user database DB (S1). When the first user performs an operation to display the card issuance screen SC1, the first user terminal 20A performs a process with the server 10 to display the card issuance screen SC1 (S2). The first user terminal 20A accepts the first user's operation on the card issuance screen SC1 (S3).

[0091] In S3, when the first user selects display area A10 (S3:A10), the first user terminal 20A performs a process with the server 10 to display the first issuance screen SC2 (S4). Based on the operation on the first issuance screen SC2, the first user terminal 20A performs a process with the server 10 to issue the first prepaid card (S5). In S5, the prepaid card information for the first prepaid card is added to the user database DB.

[0092] The first user terminal 20A performs a process to display the first authentication screen SC3 with the server 10 (S6). The first user terminal 20A performs the first authentication with the server 10 (S7). In S7, the server 10 issues a one-time password, stores it in the user database DB, and also sends the one-time password as an SMS message to the first user's phone number. The first user terminal 20A displays the SMS message and accepts the first user's input of the one-time password. The first user terminal 20A sends the one-time password entered by the first user to the server 10. The server 10 performs the first authentication by verifying the validity of the one-time password.

[0093] In S7, if the first authentication is successful, the prepaid card information of the first prepaid card will indicate that the first authentication has been performed. From there, the first prepaid card becomes available for use. When the first user performs an operation to display the list screen SC4, the first user terminal 20A executes a process with the server 10 to display the list screen SC4 based on the user database DB (S8). When the first user performs an operation to charge the first prepaid card from the list screen SC4, the first user terminal 20A executes the charge of the first prepaid card with the server 10 (S9), and this process ends.

[0094] In S3, if the first user selects display area A11 (S3:A11), the process moves to Figure 9, and the first user terminal 20A performs a process with the server 10 to display the second issuance screen SC5 (S10). Based on the operation on the second issuance screen SC5, the first user terminal 20A performs a process with the server 10 to issue the second prepaid card (S11). In S11, the prepaid card information for the second prepaid card is added to the user database DB.

[0095] The first user terminal 20A performs a process with the server 10 to display a security code, etc., on the second issuance screen SC5 (S12). In S12, the server 10 issues a security code and an authentication link, stores them in the user database DB, and sends them to the first user terminal 20A. The first user terminal 20A sends the authentication link to the second user terminal 20B based on a sharing means such as email (S13). Note that the order of the processes in S12 and S13 may be reversed. That is, the process in S12 may be executed after the process in S13. The second user terminal 20B receives the authentication link (S14). When the second user selects the authentication link, the second user terminal 20B performs a process to display the login screen SC6 (S15). Here, it is assumed that the second user already possesses a user ID and is logging in to the prepaid card service for the first time.

[0096] The second user terminal 20B performs a login process with the server 10 for the second user to log in to the prepaid card service (S16). The second user terminal 20B performs a process with the server 10 to display the second authentication screen SC7 (S17). The second user terminal 20B performs the second authentication with the server 10 (S18). In S18, the second user terminal 20B sends the security code entered by the second user to the server 10. The server 10 performs the second authentication by verifying the validity of the security code. When access is made by selecting an authentication link, the server 10 can identify which second prepaid card the second authentication is for by using the search information contained in the authentication link. That is, the server 10 can search for a security code to be compared with the security code entered by the second user using the search information.

[0097] In S18, if the second authentication is successful, the prepaid card information of the second prepaid card will indicate that the second authentication has been performed. From there, the second prepaid card becomes available for use. When the first user performs an operation to display the list screen SC4, the first user terminal 20A executes a process with the server 10 to display the list screen SC4 based on the user database DB (S19). When the first user performs an operation to charge the second prepaid card from the list screen SC4, the first user terminal 20A executes the charge of the second prepaid card with the server 10 (S20), and this process ends.

[0098] [5. Summary of Embodiments] The prepaid card system 1 of this embodiment stores a user database DB in which credit card numbers and prepaid card numbers are associated. The prepaid card system 1 performs prepaid card charging based on the credit card number associated with the prepaid card number. As a result, when a user performs prepaid card charging, the user does not need to have a source of funds such as a credit card read by a computer such as a POS terminal, so the prepaid card system 1 can reduce the effort required of the user when charging and thus improve user convenience.

[0099] Furthermore, the prepaid card system 1 performs a first authentication for the activation of the first prepaid card. The prepaid card system 1 also performs a second authentication for the activation of the second prepaid card, using a different authentication method than the first authentication. By performing authentication according to the prepaid card, the prepaid card system 1 can enhance user convenience while preventing fraudulent use of the first and second prepaid cards and thereby increasing security. For example, suppose a malicious third party illegally obtains the first user's login account and password through phishing or other means. The third party may impersonate the first user, log in to the credit card service, and fraudulently issue the first prepaid card using the procedure shown in Figure 2 as an example. In this case, if the first authentication is not required, the third party may impersonate the first user, log in to the prepaid card service, and fraudulently use the first prepaid card. In this regard, even if a third party illegally obtains the login account and password, they cannot succeed in the first authentication, so the prepaid card system 1 can prevent the fraudulent use of the first prepaid card. For example, suppose the first authentication is one-time password authentication, and the second user has not registered their phone number with the credit card service or prepaid card service. In this case, the second user cannot perform the second authentication using the same authentication method as the first authentication. In this respect, the prepaid card system 1 can improve the convenience for the second user by enabling the second user to perform the second authentication using a different authentication method than the first authentication.

[0100] Furthermore, the prepaid card system 1 performs a second authentication for initiating use of the second prepaid card based on the second user's second user terminal 20B. This allows the second user to perform the second authentication using their own second user terminal 20B, thereby enhancing convenience for the second user while also improving security by preventing fraudulent use of the second prepaid card through the second authentication.

[0101] Furthermore, the prepaid card system 1 transmits an authentication link for the second authentication and a security code issued for the second authentication to the first user terminal 20A of the first user. When the authentication link transmitted from the first user terminal 20A to the second user terminal 20B is selected by the second user terminal 20B, the prepaid card system 1 performs the second authentication based on the security code entered by the second user terminal 20B and the security code issued as issued authentication information. As a result, the second user can perform the second authentication by selecting the authentication link, so the prepaid card system 1 can enhance security by preventing fraudulent use of the second prepaid card while improving convenience for the second user. For example, if search information is included in the authentication link, the prepaid card system 1 can identify which second prepaid card the second authentication is for based on the search information included in the authentication link.

[0102] [6. Variant] This disclosure is not limited to the embodiments described above. This disclosure may be modified as appropriate without departing from the spirit of this disclosure.

[0103] Figure 10 shows an example of a function realized by a modified example. For example, the server 10 includes a first prepaid card issuing unit 101A, a second prepaid card issuing unit 101B, a payment execution unit 106, a charge request unit 107, a usage restriction unit 108, a restriction removal unit 109, an application guidance transmission unit 110, a first payment method addition unit 111, a second payment method addition unit 112, a periodic charge setting storage unit 113, a summation unit 114, a usage benefit granting unit 115, a charge benefit granting unit 116, and a display control unit 117. Each of the following is implemented by the control unit 11: the first prepaid card issuing unit 101A, the second prepaid card issuing unit 101B, the payment execution unit 106, the charge request unit 107, the usage restriction unit 108, the restriction removal unit 109, the application guidance transmission unit 110, the first payment method addition unit 111, the second payment method addition unit 112, the regular charge setting storage unit 113, the aggregation unit 114, the usage benefit granting unit 115, the charge benefit granting unit 116, and the display control unit 117.

[0104] [6-1. Variation 1] For example, if a payment fails due to insufficient funds on a prepaid card, the user will need to top up their prepaid card and then use it again, or use another payment method, which reduces user convenience. Therefore, in Modification 1, we will explain a case where, if the prepaid card balance is insufficient, the payment is executed in such a way that the insufficient amount is covered by a credit card, which is one example of a source of funds. Note that the credit card replenishment described below may also be executed if the user has set up the system to replenish funds by credit card when the balance is insufficient.

[0105] The prepaid card system 1 of Modification 1 includes a settlement execution unit 106. The settlement execution unit 106 executes a prepaid card settlement, which is a settlement using a prepaid card. If the settlement amount in a settlement using a prepaid card is less than or equal to the balance of the prepaid card, the settlement execution unit 106 executes the prepaid card settlement based on the balance of the prepaid card without making any compensation from the source of funds. If the settlement amount in a settlement using a prepaid card is greater than the balance of the prepaid card, the settlement execution unit 106 executes the settlement so that the deficit is compensated by the source of funds.

[0106] Figure 11 shows an example of the screen displayed on the first user terminal 20A in Modification 1. Modification 1 takes the example of a first user using the first prepaid card from a payment app. Furthermore, it takes the example of a payment method in which the code C80 displayed on the payment app is read by a facility terminal at a store or other facility. The payment method may be any other known payment method and is not limited to the example in Modification 1. For example, the first prepaid card may be used by a payment method in which a code displayed on a facility terminal is read by the first user terminal 20A, a payment method that is completed solely by operations on the first user terminal 20A, or any other type of payment method.

[0107] For example, when the first user launches the payment application on the first user terminal 20A, the first user terminal 20A displays a code screen SC8 showing code C80 on the display unit 25A, as shown in the upper left of Figure 11. Code C80 is an image generated based on a code ID that can temporarily identify the user in the payment service. For example, code C80 is at least one of a barcode and a two-dimensional code. The processing for displaying code C80 may be the same as that of known payment services. The first user can specify any payment method available in the payment application as the source of payment.

[0108] In the upper left example of Figure 11, the first user specifies the first prepaid card as the payment source for the payment application. When the first user has the facility terminal read code C80, the facility terminal sends a payment request to the payment service server computer to settle the payment using the payment method set as the payment source. The payment request includes the information necessary for settlement. For example, the payment request includes information that can identify the facility terminal, the code ID obtained from code C80, and the settlement amount. The data format of the payment request may be the same as the format adopted by known payment services. For example, the payment request may include information about the goods to be settled. It is assumed that the payment source information indicating the payment source specified by the first user is managed on the payment service server computer side in association with the code ID.

[0109] For example, when the payment service server computer receives a payment request from a facility terminal, it identifies the payee indicated by the payer information associated with the code ID included in the payment request. If the payer information indicates a first prepaid card, the payment service server computer requests server 10 to make a prepaid card payment. The prepaid card payment request only needs to include the information necessary for a prepaid card payment and may be in a format similar to that of a publicly known prepaid card service. For example, the prepaid card payment request includes the first prepaid card number and the payment amount. The payment service server computer is assumed to store the first prepaid card number. Server 10 receives the prepaid card payment request.

[0110] For example, the payment execution unit 106 executes a prepaid card payment based on a prepaid card payment request. The payment execution unit 106 retrieves the balance of the first prepaid card associated with the prepaid card number included in the prepaid card payment request based on the user database DB. The payment execution unit 106 compares the balance of the first prepaid card with the payment amount included in the prepaid card payment request. That is, the payment execution unit 106 determines whether the payment amount is less than or equal to the balance of the first prepaid card. Based on the result of this determination, the processes described below are executed.

[0111] For example, if the payment amount is less than or equal to the balance of the first prepaid card, the payment execution unit 106 will perform the prepaid card payment using only the balance of the first prepaid card. The prepaid card payment itself may be processed in the same way as a known prepaid card service. The payment execution unit 106 performs the prepaid card payment by reducing the balance of the first prepaid card by the payment amount. Subsequently, the result of the processing performed by the payment execution unit 106 is sent to the payment service server computer. Through processing by the payment service server computer, the first user terminal 20A displays a payment completion screen SC9 on the display unit 25A, indicating that the prepaid card payment has been completed, as shown in the upper right of Figure 11. In the example in the upper right of Figure 11, the payment completion screen SC9 indicates that only the first prepaid card, which was set as the payment source, was used.

[0112] For example, if the payment amount is greater than the balance of the first prepaid card, the payment execution unit 106 executes a prepaid card payment equal to the balance of the first prepaid card from the payment amount. As a result, the balance of the first prepaid card becomes 0. The payment execution unit 106 calculates the difference between the payment amount and the balance of the first prepaid card as the deficit. The payment execution unit 106 compensates for the deficit with a credit card by executing a credit card payment for the deficit, based on the credit card that is the source of funds for the first prepaid card. Subsequently, the result of the processing executed by the payment execution unit 106 is transmitted to the payment service server computer. Processing by the payment service server computer causes the first user terminal 20A to display the payment completion screen SC9 on the display unit 25A, as shown in the lower right of Figure 11. In the example in the lower right of Figure 11, the payment completion screen SC9 indicates that the first prepaid card set as the payment source was used and that compensation by credit card was executed.

[0113] The payment execution unit 106 may first execute a credit card payment, then auto-charge the first prepaid card so that its balance exceeds the payment amount, and finally execute the prepaid card payment based on the balance of the first prepaid card after the auto-charge. Also, although Figure 11 shows an example where the first prepaid card is used, the same process may be performed when the second prepaid card is used. Furthermore, the payment request may be sent from another terminal (for example, the first user terminal 20A or the second user terminal 20B) instead of the facility terminal. Similarly, when the first or second prepaid card is used in a situation other than the payment application (for example, online payment), the payment execution unit 106 may execute the payment in such a way that the insufficient balance is covered by a credit card, which is one example of a source of funds.

[0114] In the modified example 1, the prepaid card system 1 executes a payment in which a prepaid card is used, and if the payment amount exceeds the balance on the prepaid card, the difference is covered by a credit card. As a result, the prepaid card system 1 can execute a payment without an error occurring even if the balance on the prepaid card is insufficient, thereby improving user convenience.

[0115] [6-2. Variation 2] For example, the replenishment of insufficient funds, as described in Modification 1, may be performed not as a first payment, which is a one-time payment, but as a second payment, which is a repeatedly performed payment. The first payment is a payment that occurs each time the user gives instructions. The first payment can also be described as a one-time payment that the user makes each time. For example, the first payment is a payment made by the user at a store or other facility, or a payment made when the user purchases goods or services at an online store or similar.

[0116] A secondary payment is a payment that is executed periodically. It can also be described as a payment that is executed multiple times. The first secondary payment is executed at the user's instruction, but subsequent secondary payments are executed automatically without any specific instructions from the user. Because secondary payments are executed continuously, they are sometimes called recurring payments. For example, secondary payments can be payments for utilities, communication services, subscriptions, recurring purchases, or savings plans in financial services. The frequency of secondary payments can be any frequency. For example, secondary payments may be executed monthly, bi-weekly, weekly, or daily.

[0117] In Modification 2, the settlement execution unit 106 determines whether the prepaid card payment to be processed is a first payment or a second payment based on a predetermined determination method. For example, the settlement execution unit 106 may determine whether the prepaid card payment is a first payment or a second payment based on which server computer the prepaid card payment request was received from. If the server 10 uses different APIs for the first payment and the second payment, the settlement execution unit 106 may determine whether the prepaid card payment is a first payment or a second payment by determining whether it received a request for one of these APIs.

[0118] For example, the payment execution unit 106 determines that a payment is a first payment if it is based on a prepaid card payment request received from a server computer of a payment service. The payment execution unit 106 may also receive information from a server computer of an e-commerce service, etc., indicating whether it is a first payment or a second payment, and determine whether the payment to be processed is a first payment or a second payment based on that information.

[0119] For example, if the settlement execution unit 106 receives a prepaid card payment request from a server computer that is the subject of the first settlement (for example, a server computer for an e-commerce service that handles goods or services that are the subject of the first settlement), it may determine that the settlement to be processed is the first settlement. If the settlement execution unit 106 receives a prepaid card payment request from a server computer that is the subject of the second settlement (for example, a server computer for a subscription service), it may determine that the settlement to be processed is the second settlement. Data indicating which server computer is the subject of the first settlement or the second settlement is stored in the data storage unit 100. Based on this data, the settlement execution unit 106 may determine whether the settlement to be processed is the first settlement or the second settlement.

[0120] For example, if the settlement amount in the first settlement is greater than the balance on the prepaid card, the settlement execution unit 106 will issue an error to the first settlement. The settlement execution unit 106 obtains the settlement amount and the balance on the prepaid card and compares them in the same manner as in Modification 1. If the settlement execution unit 106 determines that the settlement to be processed is the first settlement and that the settlement amount is greater than the balance on the prepaid card, it will issue an error to the prepaid card settlement without performing a credit card replenishment as in Modification 1. The settlement execution unit 106 will notify the server computer of the settlement service, etc., that the prepaid card settlement has failed. In other words, the settlement execution unit 106 will not execute the first settlement.

[0121] For example, the settlement execution unit 106 executes the second settlement if the settlement amount in the second settlement is greater than the balance on the prepaid card, so that the deficit is covered by the source of funds. The settlement execution unit 106 obtains the settlement amount and the balance on the prepaid card and compares them in the same manner as in Modification 1. If the settlement execution unit 106 determines that the settlement to be processed is the second settlement and that the settlement amount is greater than the balance on the prepaid card, it executes the credit card replenishment as in Modification 1. The process for credit card replenishment is as described in Modification 1.

[0122] In the modified version 2, the prepaid card system 1 will flag the first payment as an error if the payment amount in the first payment exceeds the balance. If the payment amount in the second payment exceeds the balance, the prepaid card system 1 will execute the second payment so that the insufficient balance is covered by the credit card. This allows the prepaid card system 1 to cover insufficient balances with the credit card when the second payment is made, thereby improving user convenience. For example, if the second payment, which is executed repeatedly, fails, the user may be unable to use services that they use continuously (e.g., subscriptions) due to the second payment. However, even if the prepaid card balance is insufficient, it will be covered by the credit card, allowing the user to continue using the service. On the other hand, this risk does not exist with the one-time first payment, so the prepaid card system 1 can prevent unintended credit card payments from being executed by flagging the first payment as an error. For example, if the second user is the first user's child, even if the second user tries to purchase an expensive item at a store or other facility for some reason, such a payment would be considered a first payment, and the first payment would fail. Thus, prepaid card system 1 can prevent the second user from purchasing expensive items. On the other hand, since second payments such as subscriptions used by the second user are often approved in advance by the first user, prepaid card system 1 can prevent the second user from being unable to use subscriptions by covering any shortfalls with the first user's credit card.

[0123] [6-3. Modified Example 3] For example, as briefly explained in the embodiment, the charge execution unit 103 may perform a charge on a second prepaid card, which is a prepaid card of a second user different from the first user, based on a charge execution operation performed on the first user terminal 20A of the first user who holds the source of funds. In modified example 3, the second user is unable to perform a charge execution operation from the second user terminal 20B. For example, the prepaid card application stored on the second user terminal 20B does not display a screen for charging the second prepaid card. The credit card application stored on the first user terminal 20A displays a screen for charging the second prepaid card.

[0124] Figure 12 shows an example of a screen displayed on the first user terminal 20A in the modified example 3. For example, as shown in the upper left of Figure 12, the first user terminal 20A displays a list screen SC4, which includes a display area A40 showing the second prepaid card, on the display unit 25A. In the example in the upper left of Figure 12, it is assumed that the first user has issued only the second prepaid card and not the first prepaid card. When the first user selects button B400, as shown in the upper right of Figure 12, the first user terminal 20A displays a window W41 on the list screen SC4 that accepts the specification of the charge amount.

[0125] For example, if the first user specifies a charge amount and selects button B410, the charge execution unit 103 performs a charge on the second prepaid card based on the charge amount specified by the first user. The charge execution unit 103 performs a credit card payment for the amount specified by the first user based on the credit card number of the credit card associated with the second prepaid card. If the credit card payment is successful, the charge execution unit 103 updates the balance of the second prepaid card so that the balance of the second prepaid card increases by the amount specified by the first user. The first user may also specify the balance after the charge instead of the charge amount. In this case, the charge amount will be the amount obtained by subtracting the current balance of the second prepaid card from the balance after the charge specified by the first user.

[0126] In variation 3, we take an example where specifying the charge amount in window W41 and selecting button B410 correspond to the charge execution operation. After specifying the charge amount, the specification of the source of funds (charging source) may also be accepted. In this case, specifying the source of funds corresponds to the charge execution operation. For example, if the first user has multiple credit cards, the first user will specify one of the multiple credit cards as the source of funds. Authentication for charging may also be performed. In this case, the authentication operation corresponds to the charge execution operation. When the charge of the second prepaid card is executed, as shown in the lower left of Figure 12, the first user terminal 20A displays window W42 on the list screen SC4 indicating that the charge of the second prepaid card has been executed.

[0127] In the modified example 3, the prepaid card system 1 performs a charge on the second prepaid card, which belongs to a second user different from the first user, based on a charge operation performed on the first user terminal 20A. This allows the first user to manage the charge on the second prepaid card, thus improving the convenience of the first user. For example, the prepaid card system 1 can prevent the second user, who is the first user's child, from arbitrarily charging the second prepaid card using the first user's credit card.

[0128] [6-4. Modification 4] For example, in Modification Example 3, the case where the first user performs a charge operation to top up the second prepaid card is given as an example. Since the second user cannot perform the charge operation themselves, they may be able to request the first user terminal 20A to perform the charge operation. After the first user confirms the request for the charge operation from the second user, they may perform the charge operation on the second prepaid card in the manner described in Modification Example 3.

[0129] The prepaid card system 1 of Modification 4 includes a charge request unit 107. The charge request unit 107 requests a charge execution operation from the first user terminal 20A based on a charge request operation performed by the second user's second user terminal 20B. A charge request operation is an operation performed by the second user to request a charge execution operation. A charge request operation may be any operation performed on the second user terminal 20B. For example, a charge request operation may be an operation performed on a prepaid card application, or an operation performed on a prepaid card service website displayed in a browser.

[0130] Figure 13 shows an example of the screens displayed on the first user terminal 20A and the second user terminal 20B in the modified example 4. For example, when the second user operates the second user terminal 20B to launch the prepaid card application, the second user terminal 20B displays the top screen SC10 of the prepaid card application on the display unit 25B. The top screen SC10 displays information such as the balance of the second prepaid card. When the second user selects button B100, the second user terminal 20B displays a window W101 that accepts charge requests on the top screen SC10, as shown in the upper right of Figure 13.

[0131] For example, the second user may be able to specify the charge amount to request from the first user in window W101. The second user may also be able to enter a message for the first user in window W101. When the second user selects button B102, the charge request unit 107 requests the first user terminal 20A to perform a charge operation. In the modified example 4, the selection of button B102 corresponds to the charge request operation, but specifying the charge amount or entering a message may also correspond to the charge request operation.

[0132] For example, when a second user performs a charge request operation, the charge request unit 107 stores charge request information in the user database DB, associated with the first user's user ID, indicating that a charge request operation has been performed. The charge request information may indicate at least one of the charge amount specified by the second user and the message entered by the second user. When the first user accesses the server 10 by operating the first user terminal 20A, the charge request unit 107 notifies the first user that the second user has performed a charge request operation, based on the charge request information. The charge request unit 107 may notify the first user via an application such as a credit card application, or it may notify the first user via email or other means without using an application.

[0133] For example, as shown in the lower left of Figure 13, the first user terminal 20A displays message M403 on the list screen SC4 indicating that a charge request operation has been performed. The first user confirms message M403 and performs the operation to charge the second prepaid card in the same manner as in Modification Example 3. The first user terminal 20A may notify the first user that a charge request operation has been performed by means other than the list screen SC4. For example, the first user terminal 20A may notify the first user that a charge request operation has been performed using other means such as a screen other than the list screen SC4 (for example, the notification function screen of a credit card app), email, SMS, messaging app, or SNS.

[0134] In the modified example 4, the prepaid card system 1 requests the first user terminal 20A to perform a charge operation based on a charge request operation performed by the second user terminal 20B. This allows the second user to request the first user to charge the second prepaid card even if the second user is unable to perform the charge operation themselves, thus improving the convenience of the second user.

[0135] [6-5. Variation 5] For example, the first user may restrict the use of the second prepaid card from the first user terminal 20A. Restricting the use of the second prepaid card means making it unusable (prohibiting its use), setting a limit on the amount that can be spent using the second prepaid card, setting a limit on the number of times the second prepaid card can be used, or setting the purpose for which the second prepaid card can be used (for example, goods or services that can be purchased with the second prepaid card).

[0136] The prepaid card system 1 of Modification 5 includes a usage restriction unit 108. The usage restriction unit 108 restricts the use of a second prepaid card, which is a prepaid card of a second user different from the first user, based on a usage restriction operation performed on the first user terminal 20A of the first user who holds the source of funds. The usage restriction operation is an operation to restrict the use of the second prepaid card. The usage restriction operation may be any operation performed on the first user terminal 20A. For example, the usage restriction operation may be an operation performed on a credit card app or a prepaid card app, or an operation performed on a website of a credit card service or a prepaid card service displayed on a browser.

[0137] Figure 14 shows an example of a screen displayed on the first user terminal 20A in Modification 5. For example, as shown on the left side of Figure 14, the first user terminal 20A displays a list screen SC4 on the display unit 25A, which includes a button B402 for restricting the use of the second prepaid card. In the example on the left side of Figure 14, the operation in which the first user selects button B402 corresponds to the operation to restrict use. When the first user selects button B402, the first user terminal 20A requests the server 10 to restrict the use of the second prepaid card. If multiple second prepaid cards are displayed on the list screen SC4, the first user terminal 20A also sends to the server 10 information that can identify the second prepaid card selected by the first user (for example, the prepaid card number).

[0138] For example, the prepaid card information in Modification 5 includes usage restriction information indicating whether or not it is subject to usage restrictions. The usage restriction information is either a first value indicating that usage is restricted, or a second value indicating that usage is not restricted. If the first user can specify the specific content of the usage restriction (e.g., upper limit), the usage restriction information will indicate the content specified by the first user. When the server 10 receives a request from the first user terminal 20A to restrict the use of the second prepaid card, the usage restriction unit 108 updates the prepaid card information of the second prepaid card subject to usage restrictions to indicate that the use of the second prepaid card is restricted.

[0139] For example, the usage restriction unit 108 restricts the use of a second prepaid card if the usage restriction information indicates that the card is subject to usage restriction. The usage restriction unit 108 does not restrict the use of a second prepaid card if the usage restriction information indicates that the card is not subject to usage restriction. If the first user can specify the specific content of the usage restriction, the usage restriction unit 108 restricts the use of the second prepaid card based on the content indicated by the usage restriction information. When the second prepaid card becomes subject to usage restriction, the first user terminal 20A displays in the display area A40 of the second prepaid card that the card is under usage restriction, as shown on the right side of Figure 14. The method for lifting the usage restriction will be explained in Modification 6 below, but in Modification 5, the usage restriction may be left unrestricted.

[0140] For example, the usage restriction unit 108 may restrict the use of the second prepaid card so that it cannot be used at a predetermined time (for example, during times when the child is not using it). The usage restriction unit 108 may restrict the use of the second prepaid card if the payment information transmitted when the second prepaid card is used is predetermined information. The payment information may indicate the store to which the payment is to be made. The usage restriction unit 108 may restrict the use of the second prepaid card so that it cannot be used at a predetermined store (for example, a store in an area that the child is unlikely to go to).

[0141] For example, the payment information may indicate the goods or services to be paid for. The usage restriction unit 108 may restrict the use of the second prepaid card if the payment information does not indicate specific goods or services such as food, books, or educational materials. The usage restriction unit 108 may restrict the use of the second prepaid card if the payment amount indicated by the payment information is equal to or greater than a predetermined amount (for example, an amount specified by the first user). The usage restriction unit 108 may restrict the use of the second prepaid card if the number of payments made in a predetermined period in the past exceeds a predetermined number.

[0142] For example, the usage restriction operation may be made possible from the second user terminal 20B. If the second user restricts the use of the second prepaid card from the second user terminal 20, the second user is more likely to notice if they lose the second prepaid card as a physical card or if the second prepaid card is misused. Therefore, the second user can reduce losses due to the misuse of the second prepaid card by quickly performing the usage restriction operation on their own without having to ask the first user.

[0143] In the modified example 5, the prepaid card system 1 implements usage restrictions on the second prepaid card based on usage restriction operations performed by the first user terminal 20A. This allows the first user to manage the usage restrictions on the second prepaid card, thereby improving the convenience of the first user. For example, if the second user uses the second prepaid card in a manner not intended by the first user, the first user can restrict the use of the second prepaid card by performing usage restriction operations.

[0144] [6-6. Variation 6] For example, in variation 5, we have given an example where the first user restricts the use of the second prepaid card. The second prepaid card that is subject to the restriction may be kept restricted indefinitely, or it may be restricted by the first user. Removing the restriction on the second prepaid card means making the second prepaid card usable (permitting the use of the second prepaid card), raising or eliminating the upper limit on the amount that can be used with the second prepaid card, raising or eliminating the upper limit on the number of times the second prepaid card can be used, or eliminating the purpose of use set for the second prepaid card.

[0145] The prepaid card system 1 of Modification 6 includes a restriction removal unit 109. The restriction removal unit 109 removes the usage restrictions on the second prepaid card based on a restriction removal operation performed on the first user terminal 20A. The restriction removal operation is an operation to remove the usage restrictions on the second prepaid card. The restriction removal operation may be any operation performed on the first user terminal 20A. For example, the restriction removal operation may be an operation performed on a credit card app or prepaid card app, or an operation performed on a website of a credit card service or prepaid card service displayed on a browser.

[0146] Furthermore, the restriction removal operation may be performed only from the first user terminal 20A and not from the second user terminal 20B. For example, the usage restriction operation may be performed from both the first user terminal 20A and the second user terminal 20B, but the restriction removal operation may be performed only from the first user terminal 20A. By doing so, it is possible to prevent a second user, who is a young child, from accidentally resuming use of the second prepaid card. This prevents misuse of the second prepaid card and enhances security. For example, even if the second user terminal 20B is lost or otherwise falls into the hands of a third party other than the second user, and the third party is able to bypass security and access the payment app, the restriction on the use of the second prepaid card will not be removed, and the card number will remain unverified, thus preventing misuse of the second prepaid card.

[0147] For example, in the example on the right side of Figure 14, the operation by the first user to select button B402 corresponds to the restriction removal operation. When the first user selects button B402, the first user terminal 20A requests the server 10 to remove the usage restriction on the second prepaid card. The restriction removal operation is not limited to selecting button B402, but may be any other operation. If multiple second prepaid cards are displayed on the list screen SC4, the first user terminal 20A also sends information to the server 10 that identifies the second prepaid card selected by the first user. Note that the request to remove the usage restriction on the second prepaid card may also be made by the second user. In this case, the first user may be notified that a request to remove the usage restriction has been made, and the usage restriction on the second prepaid card may be removed when the first user approves the request.

[0148] For example, when server 10 receives a request from first user terminal 20A to lift the usage restriction on the second prepaid card, the restriction removal unit 109 updates the prepaid card information of the second prepaid card subject to the usage restriction so that it indicates that the use of the second prepaid card is not restricted. The restriction removal unit 109 may also lift the usage restriction on the second prepaid card by deleting information indicating that the use of the second prepaid card is restricted from the user database DB, rather than by changing the configuration of the prepaid card information.

[0149] In the modified example 6, the prepaid card system 1 removes the usage restrictions on the second prepaid card based on the restriction removal operation performed by the first user terminal 20A. This allows the first user to manage the removal of the usage restrictions on the second prepaid card, thus improving the convenience of the first user. The second user can also resume using the second prepaid card once the first user performs the restriction removal operation, thus improving the convenience of the second user as well.

[0150] [6-7. Variation 7] For example, a second user can obtain their own credit card when they reach a certain age (e.g., 18 years old). Until they reach that age, the second user can become familiar with electronic payments using a second prepaid card without needing a credit card, but after reaching that age, they may want to have a credit card. Therefore, in variation 7, we take the example of a case where a credit card application invitation is sent to the second user, who holds a second prepaid card, when they reach a certain age. The application invitation may also be sent to the first user.

[0151] In Modification 7, the charge execution unit 103 performs a charge on a second prepaid card, which is a prepaid card belonging to a second user different from the first user who holds the source of funds. This is as explained in the embodiment and Modification 3. In Modification 7, as in the embodiment, not only the first user but also the second user may be able to instruct the charging of the second prepaid card. The data storage unit 100 in Modification 7 is assumed to store information indicating a predetermined age. The application guidance transmission unit 110, described later, can identify the predetermined age based on this information. The predetermined age shall be determined according to the payment method that serves as the source of funds. For example, if the source of funds is a credit card, the predetermined age is the age at which one can hold a credit card.

[0152] The prepaid card system 1 of Modification 7 includes an application guidance transmission unit 110. When the second user reaches a predetermined age, the application guidance transmission unit 110 sends an application guidance for the second user's credit card to at least one of the first user and the second user. The application guidance is a guide that encourages the application for a credit card, which is one example of a means of obtaining funds. For example, the application guidance includes a message encouraging the application for a credit card and a link to a website for applying for a credit card. Data indicating the format of the application guidance is pre-stored in the data storage unit 100. The application guidance transmission unit 110 only needs to generate the application guidance based on this data.

[0153] Figure 15 shows an example of a screen displayed on the second user terminal 20B in the modified example 7. For example, the application guidance transmission unit 110 determines whether the second user will reach a predetermined age based on the second user's user information (e.g., date of birth or age) stored in the user database DB. The application guidance transmission unit 110 may also consider the second user to have reached a predetermined age even if the second user has not actually reached that age, if the time until the second user reaches the predetermined age falls below a threshold (for example, if the date is a predetermined amount of time before the birthday on which the second user will reach the predetermined age).

[0154] For example, if the application guidance transmission unit 110 does not determine that the second user has reached a predetermined age, it will not send an application guidance to at least one of the first user and the second user. The application guidance transmission unit 110 will send an application guidance to at least one of the first user and the second user if it determines that the second user has reached a predetermined age. The application guidance transmission unit 110 may send the application guidance immediately after the second user reaches the predetermined age, or it may send the application guidance after a certain amount of time has passed since the second user reached the predetermined age. The application guidance transmission unit 110 may send the application guidance to both the first user and the second user, or it may send the application guidance to only the first user or only the second user.

[0155] For example, when the second user terminal 20B receives the application instructions, the second user terminal 20B displays the application instructions screen SC11 on the display unit 25B, as shown in Figure 15. In the example in Figure 15, the application instructions are sent by email, but the application instructions sending unit 110 may send the application instructions using other means of notification besides email. For example, the application instructions sending unit 110 may send the application instructions using the notification function of a credit card app, the notification function of a prepaid card app, SMS, a messaging app, or SNS. Similarly, when the application instructions sending unit 110 sends the application instructions to the first user, it may send the application instructions using any means of notification.

[0156] In the modified example 7, the prepaid card system 1 sends an application notification for the second user's credit card to at least one of the first user and the second user when the second user reaches a predetermined age. This allows the prepaid card system 1 to encourage at least one of the first user and the second user to apply for the second user's credit card. The prepaid card system 1 can facilitate the issuance of credit cards.

[0157] [6-8. Variation 8] For example, as briefly explained in the embodiment, when the first prepaid card is issued, the first prepaid card may be automatically added as a payment method for the first user in services other than the credit card service and the prepaid card service. In Modification 8, an example is given where the payment service corresponds to another service, but the other service may be any service and is not limited to the payment service. For example, the other service may be an e-commerce service, a travel booking service, a communication service, a financial service, or a service that comprehensively manages payment methods for multiple services.

[0158] The modified example 8 of the prepaid card system 1 includes a first prepaid card issuing unit 101A and a first payment method addition unit 111. The first prepaid card issuing unit 101A issues a first prepaid card, which is the first user's prepaid card, based on a first issuance operation performed by the first user terminal 20A of the first user who holds the source means. The first issuance operation is an operation performed by the first user to instruct the issuance of the first prepaid card. The first issuance operation may be any operation performed on the first user terminal 20A. In the example of the embodiment, a series of operations performed after the selection of the display area A10 corresponds to the first issuance operation. The processing of the first prepaid card issuing unit 101A is as described in the function of the first authentication unit 104 in the embodiment as the processing of the server 10. The first prepaid card issuing unit 101A issues the first prepaid card by issuing prepaid card information for the first prepaid card and storing it in the user database DB.

[0159] The first payment method addition unit 111 adds the first prepaid card as a payment method for the first user in other services different from the prepaid card service relating to the first prepaid card when the first prepaid card is issued. For example, the first payment method addition unit 111 adds the first prepaid card as a payment method for the first user in other services by sending a first addition request to the server computer of the other service indicating that the first prepaid card should be added as a payment method for the first user. The first addition request includes user identification information such as the first user's user ID and prepaid card information such as the prepaid card number of the first prepaid card.

[0160] In Modification 8, we take the example of a case where the user IDs for the credit card service and the prepaid card service are the same as the user IDs for other services, but these user IDs may be different from each other. If these user IDs are different from each other, a correspondence database showing the correspondence between these user IDs is stored in the data storage unit 100 or the server computer of the other service. The server 10 or the server computer of the other service can then identify which user corresponds to which user ID based on the correspondence database.

[0161] For example, the server computer of another service stores a payment method database that shows the payment methods of the first user. When the server computer of the other service receives the first add request, it adds the first prepaid card to the first user's payment methods by associating the prepaid card number indicated in the first add request with the payment method associated with the user ID indicated in the first add request. Subsequently, as shown in Modification 1, the first user can set the first prepaid card as the payment source in a payment application or use the first prepaid card as a payment method other than a payment application.

[0162] The prepaid card system 1 of the modified example 8 issues a first prepaid card based on a first issuance operation performed on the first user terminal 20A. When the first prepaid card is issued, the prepaid card system 1 adds the first prepaid card as a payment method for the first user in services other than the prepaid card service. This allows the prepaid card system 1 to automatically add the first prepaid card to the first user's payment methods, thereby improving the convenience for the first user.

[0163] [6-9. Modification 9] For example, as briefly explained in the embodiment, when a second prepaid card is issued, the second prepaid card may be automatically added as a payment method for the second user in services other than the credit card service and the prepaid card service. In Modification 9, similar to Modification 8, an example is given where the payment service corresponds to another service, but the other service may be any service.

[0164] The modified example 9 of the prepaid card system 1 includes a second prepaid card issuing unit 101B and a second payment method addition unit 112. The second prepaid card issuing unit 101B issues a second prepaid card, which is a prepaid card for a second user different from the first user, based on a second issuance operation performed by the first user terminal 20A of the first user who holds the source means. The second issuance operation is an operation performed by the first user to instruct the issuance of the second prepaid card. The second issuance operation may be any operation performed on the first user terminal 20A. In the example of the embodiment, a series of operations performed after the selection of the display area A11 corresponds to the second issuance operation. The processing of the second prepaid card issuing unit 101B is as described in the function of the second authentication unit 105 in the embodiment, as processing of the server 10. The second prepaid card issuing unit 101B issues the second prepaid card by issuing prepaid card information for the second prepaid card and storing it in the user database DB.

[0165] The second payment method addition unit 112 adds the second prepaid card as a payment method for the second user in a service other than the prepaid card service relating to the second prepaid card, when the second prepaid card is issued. For example, the second payment method addition unit 112 adds the second prepaid card as a payment method for the second user in the other service by sending a second addition request to the server computer of the other service indicating that the second prepaid card should be added as a payment method for the second user. The second addition request includes user identification information such as the user ID of the second user and prepaid card information such as the prepaid card number of the second prepaid card.

[0166] In Modification 9, as in Modification 8, we will use the example where the user IDs for the credit card service and prepaid card service are the same as those for the other service, but these user IDs may be different from each other. For example, the server computer for the other service stores a payment method database that shows the payment methods of the second user. When the server computer for the other service receives a second add request, it adds the second prepaid card to the second user's payment methods by associating the prepaid card number indicated in the second add request with the payment method associated with the user ID indicated in the second add request. Subsequently, as in Modification 1, the second user can set the second prepaid card as the payment source in the payment application or use the second prepaid card as a payment method other than the payment application.

[0167] In the modified example 9, the prepaid card system 1 issues a second prepaid card based on a second issuance operation performed on the first user terminal 20A. When the second prepaid card is issued, the prepaid card system 1 adds the second prepaid card as a payment method for the second user in services other than the prepaid card service. This allows the prepaid card system 1 to automatically add the second prepaid card as a payment method for the second user, thereby improving the convenience for the second user.

[0168] [6-10. Variation 10] For example, User 1 may issue a second prepaid card for User 2's (their child's) allowance. In this case, User 1 may charge a predetermined amount to User 2's second prepaid card each month for User 2's monthly allowance. The same applies if User 1 issues a first prepaid card for their own allowance. Regular top-ups may also be necessary when the prepaid card is used for purposes other than allowance. The same applies even if User 2 is not a family member of User 1. Therefore, Variation 10 provides an example of a case where this is performed regularly.

[0169] The prepaid card system 1 of Modification 10 includes a periodic charge setting storage unit 113. The periodic charge setting storage unit 113 stores periodic charge settings for each prepaid card, relating to the settings for charges that are performed periodically using the source of funds. Periodic charges are a type of auto-charge. Periodic charge settings may include the timing of the charge, the charge cycle, the charge amount, the balance after the charge, or other settings. Modification 10 gives an example where the periodic charge settings are stored in the user database DB, but periodic charge settings may be stored in a database other than the user database DB, a computer other than the server 10, or an information storage medium.

[0170] For example, the first user operates the first user terminal 20A to specify a recurring charge setting for the second prepaid card so that a predetermined charge amount is executed on a predetermined day each month. The recurring charge setting storage unit 113 stores the recurring charge setting specified by the first user, associating it with the prepaid card number of the second prepaid card. Similarly, if the first user specifies a recurring charge setting for the first prepaid card, the recurring charge setting storage unit 113 stores the recurring charge setting specified by the first user, associating it with the prepaid card number of the first prepaid card. In this way, the recurring charge setting storage unit 113 stores the recurring charge setting for each prepaid card.

[0171] In the modified example 10, the charge execution unit 103 performs periodic charges based on the periodic charge setting. For example, the charge execution unit 103 determines whether or not the time for a periodic charge has arrived, based on the periodic charge setting. If the charge execution unit 103 determines that the time for a periodic charge has not arrived, it does not perform a periodic charge; if it determines that the time for a periodic charge has arrived, it performs a periodic charge. The charge execution unit 103 performs a charge of the charge amount indicated by the periodic charge setting as a periodic charge. In this way, the charge execution unit 103 only needs to perform periodic charges for each prepaid card based on the periodic charge setting of that prepaid card.

[0172] The prepaid card system 1 in modified example 10 saves a recurring charge setting for each prepaid card. The prepaid card system 1 performs recurring charges periodically based on the recurring charge setting. This allows the prepaid card system 1 to reduce the user's operational burden for recurring charges and improve user convenience.

[0173] [6-11. Variation 11] For example, when a user issues a new prepaid card, there may be a remaining balance on an already issued prepaid card (an old prepaid card). In this case, the user may be able to add the balance of the already issued prepaid card to the balance of the new prepaid card. In Modification 11, when the first user issues a new first prepaid card or second prepaid card in the same manner as in the embodiment, the user specifies that the balance of the already issued prepaid card should be added. For example, the first user specifies from the first issuance screen SC2 whether or not to add the balance of the already issued prepaid card to the new first prepaid card. The balance of the already issued first prepaid card can be added, but the balance of the already issued second prepaid card may also be added. The first user specifies from the second issuance screen SC5 whether or not to add the balance of the already issued prepaid card to the new second prepaid card. The balance of the issued second prepaid card can be added, but the balance of the issued first prepaid card may also be added.

[0174] The prepaid card system 1 of Modification 11 includes a summing unit 114. When a new prepaid card is issued, the summing unit 114 adds the balance of the issued prepaid card to the new prepaid card. If no initial value is specified for the balance of the new prepaid card, the summing unit 114 sets the balance of the new prepaid card to the same amount as the balance of the issued prepaid card. The summing unit 114 may set the balance of the issued prepaid card to 0, delete the issued prepaid card, or restrict the use of the issued prepaid card. Modification 11 gives an example where the first user can specify only one issued prepaid card, but the first user may specify multiple issued prepaid cards, and the summing unit 114 may add the balance of each of the specified multiple prepaid cards to the new prepaid card.

[0175] For example, if an initial value for the balance of a new prepaid card (the balance immediately after issuance of the new prepaid card) is specified, the summing unit 114 calculates the difference between the initial value for the new prepaid card's balance and the balance of the issued prepaid card as the initial charge. The summing unit 114 then sets the sum of this charged difference and the balance of the issued prepaid card as the initial value for the balance of the new prepaid card.

[0176] For example, unlike the example above, if a charge amount is specified for the initial charge of a new prepaid card, the summing unit 114 will execute the charge of that amount and set the sum of that charge amount and the balance of the issued prepaid card as the initial balance of the new prepaid card. If the sum of the charge amount specified by the user and the balance of the issued prepaid card exceeds the maximum amount of the prepaid card, the available charge amount may be displayed.

[0177] In the modified example 11, the prepaid card system 1 adds the balance of the issued prepaid card to the new prepaid card when a new prepaid card is issued. This allows the prepaid card system 1 to effectively utilize the balance of the issued prepaid card, thereby improving user convenience.

[0178] [6-12. Variation 12] For example, in order to encourage a second user to use a second prepaid card, the second user may be given a predetermined benefit when the second prepaid card is used. This predetermined benefit does not have to be given when the first prepaid card is used. In variation 12, an example is given in which a lottery ticket, which has a predetermined probability of being won, is given as a predetermined benefit when the second user, who is the child of the first user, uses the second prepaid card. The second user may find the idea of ​​drawing a lottery ticket appealing and actively gain experience using the second prepaid card as an electronic payment method.

[0179] The prepaid card system 1 of Modification 12 includes a reward granting unit 115. The reward granting unit 115 grants a predetermined reward to the second user when the first prepaid card, which is the prepaid card of the first user who holds the source of funds, is used, but grants a predetermined reward to the second user when the second prepaid card, which is the prepaid card of a second user different from the first user, is used. The predetermined reward may be various rewards adopted in publicly known services. For example, the predetermined reward may be points themselves, an increase in the point redemption rate, a lottery, goods, services, content such as videos, or coupons.

[0180] For example, when a prepaid card is used, the reward granting unit 115 determines whether the prepaid card is the first prepaid card or the second prepaid card. That is, the reward granting unit 115 determines whether the first prepaid card or the second prepaid card was used. Information indicating whether the prepaid card is the first prepaid card or the second prepaid card (in the data storage example in Figure 7, this is the type) is included in the prepaid card information. The reward granting unit 115 can then determine whether the prepaid card is the first prepaid card or the second prepaid card based on this information.

[0181] For example, if the reward granting unit 115 determines that the first prepaid card has been used, it will not grant the first user a predetermined reward. If the reward granting unit 115 determines that the second prepaid card has been used, it will grant the second user a predetermined reward. The method of granting the reward itself may be any of the various methods used in publicly known services. For example, the reward granting unit 115 may grant points to the second user, or it may increase the point granting rate and then calculate the points to be granted to the second user. The reward granting unit 115 may also execute a predetermined lottery when the second prepaid card is used. The program for executing the lottery is stored in the data storage unit 100. Similarly, for other rewards, the reward granting unit 115 may grant the second user other rewards by executing processing corresponding to the other rewards.

[0182] In the modified version 12, the prepaid card system 1 does not grant a predetermined benefit to the first user when the first prepaid card is used, but grants a predetermined benefit to the second user when the second prepaid card is used. This allows the prepaid card system 1 to incentivize the second user to use the second prepaid card. For example, if the second user is the first user's child, they may be young and unfamiliar with electronic payments, but the prepaid card system 1 can incentivize the second user to become accustomed to electronic payments using the second prepaid card through the predetermined benefit.

[0183] [6-13. Variation 13] For example, while Modification 13 describes benefits for the second user, benefits may also be granted to the first user when the second prepaid card is charged. An example of a benefit for the first user at the time of charging is shown in the lower left of Figure 12 in Modification 3 as "Points Earned: 50". Benefits may also be granted when the first user charges the first prepaid card, but Modification 13 describes benefits when the second prepaid card is charged. The meaning of the benefit is the same as in Modification 12. The benefit for the first user may be various types of benefits, as in Modification 12.

[0184] The modified prepaid card system 1 of the 13th variation includes a usage benefit granting unit 115 and a charge benefit granting unit 116. The charge benefit granting unit 116 grants a charge benefit to the first user when a charge is performed on the second prepaid card, which is a prepaid card belonging to a second user different from the first user who holds the source of funds. The charge benefit granting unit 116 grants the charge benefit to the first user on the condition that the first user has performed a charge on the second prepaid card. The charge benefit is a benefit granted on the condition that a charge is made to the second prepaid card. The method of granting the benefit itself may be the same as known methods. For example, as shown in the lower left of Figure 12, if points correspond to the charge benefit, the charge benefit granting unit 116 can grant the charge benefit by increasing the balance of points held by the first user.

[0185] The reward granting unit 115 grants the second user a reward different from the charge reward when the second prepaid card is used. The reward differs from that in modified example 12 in that it is a reward different from the charge reward, but the processing for granting the reward is as described in modified example 12.

[0186] In the modified version 13, the prepaid card system 1 grants the first user a charge benefit related to the charge benefit when the second prepaid card is charged. When the second prepaid card is used, the prepaid card system 1 grants the second user a usage benefit different from the charge benefit. This allows the prepaid card system 1 to incentivize the first user to charge the second prepaid card. The prepaid card system 1 also incentivizes the second user to use the second prepaid card.

[0187] [6-14. Variation 14] For example, the list screen SC4 is not limited to the examples of Embodiments and Modifications 1 to 13. The list screen SC4 may display the status of prepaid cards. The status is the current state of the prepaid card. A prepaid card can be in one of several predetermined statuses. The status may be anything, for example, in use, suspended, incomplete, or unavailable. Information indicating the status of individual prepaid cards may be stored in a user database DB or another database. When the conditions for changing the status of a prepaid card are met, the server 10 changes the status of that prepaid card. The information processing for changing the status itself may be the same as known information processing.

[0188] The modified example 14 of the prepaid card system 1 includes a display control unit 117. The display control unit 117 causes various screens to be displayed on the user terminal 20. For example, the display control unit 117 causes the status of a prepaid card to be displayed on a list screen SC4 that shows a list of prepaid cards. The display control unit 117 causes the status to be displayed on the list screen SC4 by transmitting display data (e.g., HTML data) for the list screen SC4 that shows the status. When the display control unit 117 receives a request to display the list screen SC4 from a first user terminal 20A of a first user, it obtains information on the status of the prepaid card associated with the first user's credit card from the user database DB, and based on this information, it causes the list screen SC4 showing the status of the prepaid card to be displayed on the first user terminal 20A.

[0189] For example, the display control unit 117 may display a detailed status on the list screen SC4 indicating the reason why a prepaid card's status is either incomplete or unavailable. The detailed status information is also stored in the user database DB. The detailed status may indicate that the procedure is incomplete and the initiation procedure should be performed, that the procedure is incomplete and the link should be shared, that the procedure is incomplete and the code should be shared, or other reasons. In other words, the detailed status may indicate which procedure should be performed first. The detailed status may also indicate that the prepaid card is unavailable because it has been migrated, that the prepaid card is unavailable because it has expired, or that the prepaid card is unavailable because it has been canceled.

[0190] Figure 16 shows an example of the list screen SC4 of modified example 14. In the example in Figure 16, three prepaid cards are associated with the first user's credit card. The list screen SC4 includes display areas A40A to 40C corresponding to each of the three prepaid cards. The list screen SC4 may also include a button B43 for switching between a state that displays all prepaid cards and a state that displays only prepaid cards that are still within their expiration date.

[0191] For example, when a user selects button B43, the display of the list screen SC4 switches between these two states. The display control unit 117 may control the display of the list screen SC4 according to the selected state of button B43. If there are prepaid cards whose expiration date is approaching, the display control unit 117 may display information that identifies this fact on the list screen SC4. An approaching expiration date means that the remaining period until the expiration date becomes shorter than a threshold. The display control unit 117 may also display a message on the list screen SC4 indicating that a prepaid card is approaching its expiration date.

[0192] For example, display area A40A indicates the first prepaid card. Buttons B400A, B401A, and B402A are the same as buttons B400, B401, and B402 in Figure 3, respectively. Status S404A is the status of the first prepaid card. In the example in Figure 16, status 404A indicates that the first user is using the first prepaid card.

[0193] For example, display area A40B indicates the second prepaid card. Buttons B400B, B401B, and B402B are the same as buttons B400, B401, and B402 in Figure 12, respectively. Status S404B is the status of the second prepaid card. In the example in Figure 16, status 404B indicates that the procedure for the second prepaid card has not been completed. The display control unit 117 may display message M405B near status 404B prompting the user to complete the procedure for the second prepaid card.

[0194] For example, display area A40C shows the third prepaid card. Status S404C is the status of the third prepaid card. In the example in Figure 16, status 404C indicates that the third prepaid card is unavailable. In this case, button B401C indicates that the usage details for the third prepaid card can be displayed. When the user selects button B401C, the display control unit 117 refers to the user database DB to obtain the usage history of the third prepaid card and displays the usage details on the list screen SC4. The display control unit 117 may also display the usage screen for prepaid cards with statuses other than unavailable. The display control unit 117 may display the usage details for each prepaid card on separate screens or on the same screen.

[0195] In the modified example 14, the prepaid card system 1 displays the status S404A, S404B, and S404C related to the prepaid cards on the list screen SC4, which shows a list of prepaid cards. This makes it easier for the user to understand the status of their prepaid cards, thus improving user convenience.

[0196] [6-15. Other variations] For example, the above variations may be combined.

[0197] For example, server 10 does not need to have the function to issue a second prepaid card. Server 10 does not need to have the function to issue prepaid cards for other users, but it does have the function to issue prepaid cards for other users. It is understandable to a person skilled in the art from the description in this disclosure that functions that do not presuppose a second prepaid card can be implemented even if server 10 does not have the function to issue a second prepaid card.

[0198] For example, server 10 does not need to have the function to issue the first prepaid card. Server 10 does not need to have the function to issue its own prepaid card, but the first user has the function to issue the second user's prepaid card. It is understandable to a person skilled in the art from the description in this disclosure that functions that do not presuppose the first prepaid card can be implemented even if server 10 does not have the function to issue the first prepaid card.

[0199] For example, the functions described as being implemented on server 10 may be implemented on the first user terminal 20A, the second user terminal 20B, or other computers. The functions described as being implemented on server 10 may be shared among multiple computers. For example, the functions described as being implemented on server 10 may be shared between the computer for the credit card service and the computer for the prepaid card service.

[0200] [7. Addendum] For example, prepaid card system 1 can also be configured as follows:

[0201] (1) A unit that acquires source means identification information that can identify the source means that serves as the source of funds for a prepaid card, and that acquires the source means identification information associated with prepaid card identification information that can identify the prepaid card, A charge execution unit that performs a charge on the prepaid card based on the source means identification information associated with the prepaid card identification information, A prepaid card system that includes [this]. (2) The aforementioned prepaid card system is A first authentication unit performs a first authentication regarding the commencement of use of the first prepaid card, which is the prepaid card of the first user who possesses the aforementioned source means, A second authentication relating to the commencement of use of a second prepaid card, which is the prepaid card of a second user different from the first user, comprising a second authentication unit that performs the second authentication using an authentication method different from the first authentication, The prepaid card system described in (1) further includes the following. (3) The prepaid card system further includes a second authentication unit that performs a second authentication regarding the commencement of use of the second prepaid card, which is the second user's prepaid card, based on the second user terminal of a second user different from the first user who possesses the source means. The prepaid card system described in (1) or (2). (4) The aforementioned second authentication unit is, The authentication link for the second authentication and the issued authentication information issued for the second authentication are transmitted to the first user terminal of the first user. When the authentication link transmitted from the first user terminal to the second user terminal is selected by the second user terminal, the second authentication is performed based on the input authentication information entered by the second user terminal and the issued authentication information. (3) The prepaid card system described in (3). (5) The prepaid card system includes a settlement execution unit that executes the settlement, such that if the settlement amount in a settlement using the prepaid card is greater than the balance on the prepaid card, the deficit is covered by the source of funds. A prepaid card system as described in any of (1) to (4), further including the above. (6) The aforementioned settlement execution unit, If the settlement amount in the first settlement, which is executed only once, is greater than the balance, the first settlement is set to an error. If the settlement amount in the second settlement, which is a settlement that is repeatedly performed, is greater than the balance, the second settlement is performed so that the deficit in the balance is covered by the source of funds. (5) The prepaid card system described in (5). (7) The charge execution unit performs the charge on the second prepaid card, which is the prepaid card of a second user different from the first user, based on a charge execution operation performed on the first user terminal of the first user who possesses the source means. A prepaid card system as described in any of (1) to (6). (8) The prepaid card system further includes a charge request unit that requests the first user terminal to perform the charge execution operation based on a charge request operation performed at the second user terminal of the second user. The prepaid card system described in (7). (9) The prepaid card system further includes a usage restriction unit that, based on a usage restriction operation performed at the first user terminal of the first user who possesses the source means, performs usage restrictions on a second prepaid card, which is the prepaid card of a second user different from the first user. A prepaid card system as described in any of (1) to (8). (10) The prepaid card system further includes a restriction removal unit that removes the usage restrictions on the second prepaid card based on a restriction removal operation performed at the first user terminal. (9) The prepaid card system described above. (11) The charge execution unit performs the charge on the second prepaid card, which is the prepaid card of a second user different from the first user who possesses the source means. The prepaid card system further includes an application notification transmission unit that, when the second user reaches a predetermined age, transmits an application notification for the second user's source of funds to at least one of the first user and the second user. A prepaid card system as described in any of (1) to (10). (12) The aforementioned prepaid card system is A first prepaid card issuing unit issues a first prepaid card, which is the first user's prepaid card, based on a first issuance operation performed at the first user terminal of the first user who possesses the aforementioned source means. When the first prepaid card is issued, the first payment method addition unit adds the first prepaid card as a payment method for the first user in a service other than the prepaid card service relating to the first prepaid card, A prepaid card system as described in any of (1) to (11), further including the above. (13) The aforementioned prepaid card system is A second prepaid card issuing unit issues a second prepaid card, which is the prepaid card of a second user different from the first user, based on a second issuance operation performed at the first user terminal of the first user who possesses the aforementioned source means. When the second prepaid card is issued, a second payment method addition unit adds the second prepaid card as a payment method for the second user in a service other than the prepaid card service relating to the second prepaid card, A prepaid card system as described in any of (1) to (12), further including the above. (14) The prepaid card system further includes a periodic charge setting storage unit that stores periodic charge settings for each prepaid card, relating to the setting of the charge that is performed periodically using the source of funds. The charge execution unit performs the charge periodically based on the periodic charge setting. A prepaid card system as described in any of (1) to (13). (15) The prepaid card system further includes a consolidation unit that, when a new prepaid card is issued, adds the balance of the issued prepaid card to the balance of the new prepaid card. A prepaid card system as described in any of (1) to (14). (16) The prepaid card system further includes a usage benefit granting unit that, when the first prepaid card, which is the prepaid card of the first user who possesses the source means, is used, grants the first user the predetermined benefit, and when the second prepaid card, which is the prepaid card of a second user different from the first user, is used, grants the second user the predetermined benefit. A prepaid card system as described in any of (1) to (15). (17) The aforementioned prepaid card system is When the charge is performed on a second prepaid card, which is a prepaid card belonging to a second user different from the first user who possesses the aforementioned source means, a charge benefit granting unit grants the first user a charge benefit related to the charge benefit, A usage benefit granting unit that grants the second user a usage benefit different from the charge benefit when the second prepaid card is used, A prepaid card system as described in any of (1) to (16), further including the above. (18) The prepaid card system includes a display control unit that displays the status of the prepaid card on a list screen showing a list of the prepaid cards. A prepaid card system as described in any of (1) to (17), further including the above. [Explanation of symbols]

[0202] 1 Prepaid card system, 10 Server, 11,21A,21B Control unit, 12,22A,22B Storage unit, 13,23A,23B Communication unit, 20A First user terminal, 20B Second user terminal, 24A,24B Operation unit, 25A,25B Display unit, 100 Data storage unit, 101 Prepaid card issuance unit, 101A First prepaid card issuance unit, 101B Second prepaid card issuance unit, 102 Charge execution unit, 103 First authentication unit, 104 Second authentication unit, 105 Payment execution unit, 106 Charge request unit, 107 Usage restriction unit, 108 Restriction removal unit, 109 Application guidance transmission unit, 110 First payment method addition unit, 111 Second payment method addition unit, 112 Regular charge setting storage unit, 113 Aggregation unit, 114 Usage benefit granting section, 115 Charge benefit granting section, A10, A11, A40, A60, A61 Display area, B20, B21, B22, B30, B32, B33, B43, B50, B51, B52, B70, B72, B100, B102, B400, B401, B402, B400A, B401A, B402A, B400B, B401B, B402B, B401C, B410 Button, S404A, S404B, S404C Status, C80 Code, DB User database, F31, F71 Input form, N Network, SC1 Card issuance screen, SC2 First issuance screen, SC3 First authentication screen, SC4 List screen, SC5 Second issuance screen, SC6 Login screen, SC7 Second authentication screen, SC8 code screen, SC9 payment completion screen, SC10 top screen, SC11 application guidance screen, W41, W42, W81, W101 windows, M403 message.

Claims

1. A unit that acquires source means identification information that can identify the source means that serves as the source of funds for a prepaid card, and that acquires the source means identification information associated with prepaid card identification information that can identify the prepaid card, A charge execution unit that performs a charge on the prepaid card based on the source means identification information associated with the prepaid card identification information, A prepaid card system that includes [this].

2. The aforementioned prepaid card system is A first authentication unit performs a first authentication regarding the commencement of use of the first prepaid card, which is the prepaid card of the first user who possesses the aforementioned source means, A second authentication relating to the commencement of use of a second prepaid card, which is the prepaid card of a second user different from the first user, comprising a second authentication unit that performs the second authentication using an authentication method different from the first authentication, The prepaid card system according to claim 1, further comprising:

3. The prepaid card system further includes a second authentication unit that performs a second authentication regarding the commencement of use of the second prepaid card, which is the prepaid card of the second user, based on the second user terminal of a second user different from the first user who possesses the source means. The prepaid card system according to claim 1 or 2.

4. The second authentication unit is, The authentication link for the second authentication and the issued authentication information issued for the second authentication are transmitted to the first user terminal of the first user. When the authentication link transmitted from the first user terminal to the second user terminal is selected by the second user terminal, the second authentication is performed based on the input authentication information entered by the second user terminal and the issued authentication information. The prepaid card system according to claim 3.

5. The prepaid card system includes a settlement execution unit that executes the settlement, such that if the settlement amount in a settlement using the prepaid card is greater than the balance on the prepaid card, the deficit is covered by the source of funds. The prepaid card system according to claim 1 or 2, further comprising:

6. The aforementioned settlement execution unit, If the settlement amount in the first settlement, which is executed only once, is greater than the balance, the first settlement is set to an error. If the settlement amount in the second settlement, which is a settlement that is repeatedly performed, is greater than the balance, the second settlement is performed so that the deficit in the balance is covered by the source of funds. The prepaid card system according to claim 5.

7. The charge execution unit performs the charge on the second prepaid card, which is the prepaid card of a second user different from the first user, based on a charge execution operation performed on the first user terminal of the first user who possesses the source means. The prepaid card system according to claim 1 or 2.

8. The prepaid card system further includes a charge request unit that requests the first user terminal to perform the charge execution operation based on a charge request operation performed at the second user terminal of the second user. The prepaid card system according to claim 7.

9. The prepaid card system further includes a usage restriction unit that, based on a usage restriction operation performed at a first user terminal of a first user who possesses the source means, restricts the use of a second prepaid card, which is the prepaid card of a second user different from the first user. The prepaid card system according to claim 1 or 2.

10. The prepaid card system further includes a restriction removal unit that removes the usage restrictions on the second prepaid card based on a restriction removal operation performed at the first user terminal. The prepaid card system according to claim 9.

11. The charge execution unit performs the charge on the second prepaid card, which is the prepaid card of a second user different from the first user who possesses the source means. The prepaid card system further includes an application notification transmission unit that, when the second user reaches a predetermined age, transmits an application notification for the second user's source of funds to at least one of the first user and the second user. The prepaid card system according to claim 1 or 2.

12. The aforementioned prepaid card system is A first prepaid card issuing unit issues a first prepaid card, which is the first user's prepaid card, based on a first issuance operation performed at a first user terminal of a first user who possesses the aforementioned source means. When the first prepaid card is issued, the first payment method addition unit adds the first prepaid card as a payment method for the first user in a service other than the prepaid card service relating to the first prepaid card, The prepaid card system according to claim 1 or 2, further comprising:

13. The aforementioned prepaid card system is A second prepaid card issuing unit issues a second prepaid card, which is the prepaid card of a second user different from the first user, based on a second issuance operation performed at the first user terminal of the first user who possesses the aforementioned source means. When the second prepaid card is issued, a second payment method addition unit adds the second prepaid card as a payment method for the second user in a service other than the prepaid card service relating to the second prepaid card, The prepaid card system according to claim 1 or 2, further comprising:

14. The prepaid card system further includes a periodic charge setting storage unit that stores periodic charge settings for each prepaid card, relating to the setting of the charge that is performed periodically using the source of funds. The charge execution unit performs the charge periodically based on the periodic charge setting. The prepaid card system according to claim 1 or 2.

15. The prepaid card system further includes a consolidation unit that, when a new prepaid card is issued, adds the balance of the issued prepaid card to the balance of the new prepaid card. The prepaid card system according to claim 1 or 2.

16. The prepaid card system further includes a usage benefit granting unit that, when the first prepaid card, which is the prepaid card of the first user who possesses the source means, is used, grants the first user the predetermined benefit, and when the second prepaid card, which is the prepaid card of a second user different from the first user, is used, grants the second user the predetermined benefit. The prepaid card system according to claim 1 or 2.

17. The aforementioned prepaid card system is When the charge is performed on a second prepaid card, which is a prepaid card belonging to a second user different from the first user who possesses the aforementioned source means, a charge benefit granting unit grants the first user a charge benefit related to the charge benefit, A usage benefit granting unit that grants the second user a usage benefit different from the charge benefit when the second prepaid card is used, The prepaid card system according to claim 1 or 2, further comprising:

18. The prepaid card system includes a display control unit that displays the status of the prepaid card on a list screen showing a list of the prepaid cards. The prepaid card system according to claim 1 or 2, further comprising:

19. A fund source identification information that can identify the fund source that serves as the source of funds for a prepaid card, and an acquisition step of acquiring the fund source identification information associated with prepaid card identification information that can identify the prepaid card, A charge execution step in which the prepaid card is charged based on the source means identification information associated with the prepaid card identification information, A method of providing prepaid card services, including [the specified term].

20. A source means identification information that can identify the source means that serves as the source of funds for a prepaid card, and an acquisition unit that acquires the source means identification information associated with prepaid card identification information that can identify the prepaid card, A charge execution unit that performs a charge on the prepaid card based on the source means identification information associated with the prepaid card identification information. A program that makes a computer function.

Images