JP2016224499A - Prepaid card management system and prepaid card management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a prepaid card management system and a prepaid card management method that are capable of specifying the purpose of use to give money or a point at a low introduction cost and preventing the money or the point from being used for other purposes.SOLUTION: A prepaid card management method comprises: obtaining sales object information 25 including at least one of commodity information relating to a sales object and store information relating to the sales object when a request for payment by a prepaid card B is made and purpose information in which the purpose of use for each of the prepaid cards B is registered; and comparing the sales object information 25 with the purpose information to determine whether the prepaid card B is usable or not.SELECTED DRAWING: Figure 3

Description

  The present invention relates to a prepaid card management system and a prepaid card management method, and more particularly to a prepaid card management system and a prepaid card management method characterized in that a prepaid card limited in purpose of use can be provided.

  There is a demand for giving money or points for the purpose of being used only for a specific purpose.

  For example, there is a need to distribute beneficiaries to tickets that cannot be used outside the intended purpose, such as the food stamp system in the United States, or to distribute vouchers that can be used only in specific areas for regional revitalization. Exists.

Conventionally, since such a ticket has not been digitized, it has been judged whether a person in the store matches the purpose of use visually. Such visual confirmation work is complicated, and when an unfamiliar person such as a part-time worker checks it, the check may not be performed correctly.
In order to solve such a problem, a ticket-dedicated terminal may be provided so that the ticket can be processed by a computer (see, for example, Patent Document 1).

Japanese Patent Laid-Open No. 5-128374

  However, if a ticket-dedicated terminal is provided so that the ticket can be processed by a computer, another problem that the introduction cost of the system becomes high occurs. For example, when distributing a voucher that can be used only in a local shopping district in a campaign for regional revitalization, there is a problem that it is difficult to construct a large-scale system just for that purpose.

  Accordingly, the present invention provides a prepaid card management system and a prepaid card management that can designate money and points by specifying the purpose of use at a low introduction cost and prevent the money and points from being used for other purposes. It is an object to provide a method.

  The present invention has been made to solve the above-described problems, and is characterized by the following.

  The invention according to claim 1 is a purpose of registering sales object information including at least one of product information and store information related to a sales object and a purpose of use for each prepaid card when a payment request by a prepaid card occurs. And determining whether or not the prepaid card can be used by comparing the sales object information with the purpose information.

  The invention described in claim 2 is characterized in that, in addition to the feature of the invention described in claim 1, it is possible to specify whether or not a remittance request by the prepaid card is permitted as an attribute of the prepaid card. And

  In addition to the features of the invention described in claim 1 or 2, the invention described in claim 3 can specify whether or not to allow a withdrawal request by the prepaid card as an attribute of the prepaid card. It is characterized by that.

  The invention according to claim 4 is used by a prepaid card in addition to the features of the invention according to any one of claims 1 to 3 above, using information relating to the location of the store included in the store information. It is characterized by determining whether or not it is possible.

  The invention according to claim 5 is a prepaid card management method to be executed by a computer, and includes at least one of merchandise information or store information related to a sales object when a payment request by the prepaid card occurs. It is characterized by acquiring sales object information and purpose information in which a purpose of use for each prepaid card is registered, and comparing the sales object information with the purpose information to determine whether or not a prepaid card can be used. To do.

  The invention described in claim 6 is characterized in that, in addition to the feature of the invention described in claim 5, it is possible to specify whether or not to allow a remittance request by the prepaid card as an attribute of the prepaid card. To do.

  The invention described in claim 7 can specify whether or not to allow a withdrawal request by the prepaid card as an attribute of the prepaid card, in addition to the feature of the invention described in claim 5 or 6 described above. It is characterized by.

  In addition to the features of the invention described in any of claims 5 to 7, the invention described in claim 8 is used by a prepaid card using information relating to the location of the store included in the store information. It is characterized by determining whether or not it is possible.

  The inventions of claims 1 and 5 are as described above, and when a payment request by a prepaid card is generated, the sales object information including at least one of product information or store information related to the sales object, and the prepaid card The purpose information registered for each purpose of use is acquired, and the sales target information is compared with the purpose information to determine whether or not the prepaid card can be used. That is, the purpose of use can be designated in advance for the prepaid card, and the use purpose of the prepaid card can be determined by checking the purpose of use.

  For example, when a prepaid card is used as a food stamp, a prepaid card whose purpose of use is registered in advance so as to be used only for daily necessities such as food is distributed to beneficiaries. When a beneficiary uses a prepaid card at a store, merchandise information (for example, a JAN code) related to a sales target is checked, and it is determined whether the merchandise information matches the purpose of use of the prepaid card. If the merchandise information matches the purpose of use of the prepaid card, the payment by the prepaid card is completed. On the other hand, if the merchandise information does not match the purpose of use of the prepaid card, payment by the prepaid card can be rejected by notifying an error to the store terminal.

  For example, when a prepaid card is used as a voucher that can be used only in a local shopping street, a prepaid card whose purpose of use has been registered in advance so that it can be used only in that area (or a specific store) is distributed to beneficiaries. . When a beneficiary uses a prepaid card at a store, the store information of the store is checked, and it is determined whether the store information matches the purpose of use of the prepaid card. If the store information matches the purpose of use of the prepaid card, payment by the prepaid card is completed. On the other hand, if the store information does not match the purpose of use of the prepaid card, payment by the prepaid card can be refused by notifying an error to the store terminal.

  As described above, according to this configuration, money or points can be given by specifying the purpose of use, and the money or points can be prevented from being used outside the purpose. In addition, since such a system can be realized by applying an existing prepaid card system, it is not necessary to provide a dedicated ticket terminal, and the introduction cost of the system can be reduced.

  Further, the inventions of claims 2 and 6 are as described above, and it is possible to specify whether or not to allow a remittance request by the prepaid card as an attribute of the prepaid card. It is possible to prevent usage such as remittance and use for other purposes.

  The inventions of claims 3 and 7 are as described above, and it is possible to specify whether or not a withdrawal request by the prepaid card is permitted as an attribute of the prepaid card. It is possible to prevent usage such as use outside the purpose.

  Moreover, invention of Claim 4 and 8 is as above-mentioned, It determines whether a prepaid card can be used using the information which concerns on the position of the store contained in the said store information. Such a configuration is optimal for using, for example, a prepaid card as a cash voucher that can be used only in a local shopping street. That is, even if store information is not specified individually, stores that can use a prepaid card can be limited by information relating to the location of the store. Information relating to the location of the store may be registered in advance, or may be dynamically acquired using GPS or the like.

It is a conceptual diagram of the prepaid card management system which concerns on this embodiment. It is an example of a use purpose table, a merchandise information table, and a store information table. It is a flowchart of a payment process. It is a sequence diagram which shows the usage example of a prepaid card management system.

  Embodiments of the present invention will be described with reference to the drawings.

(About system configuration)
FIG. 1 is a conceptual diagram of a prepaid card management system according to the present embodiment. This prepaid card management system is managed by the prepaid card management server 10. The prepaid card management server 10 is connected to the information database 20 and a processing terminal for the prepaid card B installed in the store C via communication means such as the Internet. When the user A uses the prepaid card B at the store C, a payment request is issued from the terminal of the store C to the prepaid card management server 10, and the prepaid card management server 10 executes a payment process with reference to the information database 20. .

  The prepaid card B may be a type that can be repeatedly charged or a type that can be used only once and cannot be charged.

  The information database 20 stores user information 21, usage history information 22, balance information 23, card information 24, sales target information 25, and the like.

  In the present embodiment, the system configuration is simplified for the sake of explanation, but the actual system configuration may be different from that shown in FIG. That is, in actual operation, the card information 24 and balance information 23 of the prepaid card B are managed by a server on the card issuer side, and the user information 21 and usage history information 22 are managed by a server on the card member store side. The target information 25 may be managed by another database (for example, when a JAN code is used as the sales target information 25, a JAN code integrated product information database). In this way, the present invention can be implemented even if the configuration of the server or database is changed as appropriate.

  The user information 21 stored in the information database 20 is information managed for each user A, and a unique user ID assigned to each user A to identify the user A and a user name associated with the user ID. And passwords. The user A of the prepaid card B performs user registration when using the prepaid card B. When the user registration is performed, the user name and password designated by the user A are associated with the user ID to create user information 21, and the user information 21 is registered in the information database 20.

  The card information 24 stored in the information database 20 is information managed for each prepaid card B, and is associated with a unique card ID and card ID assigned to each prepaid card B in order to identify the prepaid card B. Information such as card name and password. When the prepaid card B is created, the card name and password designated by the user A are associated with the card ID and the user ID to create card information 24, and this card information 24 is registered in the information database 20.

  The card information 24 includes a usage purpose table 24a (see FIG. 2) that defines the usage purpose of the prepaid card B. This purpose-of-use table 24a is registered by the purpose information adding unit 11 described later. When the purpose of use of the prepaid card B is registered, record information is created for each prepaid card B, and this record information is registered in the purpose of use table 24a. The registered record information includes at least a card ID for identifying the prepaid card B and purpose information that defines the purpose of use of the prepaid card B.

  In the present embodiment, the use purpose table 24a is included in the card information 24. However, the present invention is not limited to this, and the use purpose table 24a is even associated with the card information 24 related to a specific prepaid card B. It only has to be. In other words, the usage purpose table 24a only needs to be associated with a specific prepaid card B in a one-to-one relationship.

  The usage history information 22 stored in the information database 20 is information managed for each prepaid card B, and includes detailed information on the card ID of the target prepaid card B and usage history associated with the card ID. When the user A executes the payment process or deposit / withdrawal process with the prepaid card B, the contents are added to the usage history information 22 and stored.

  The balance information 23 stored in the information database 20 is information managed for each prepaid card B, and includes information regarding the card ID of the target prepaid card B and the used balance associated with the card ID. When the user A executes the payment process or deposit / withdrawal process with the prepaid card B, the balance of the prepaid card B is changed according to the result, and the content is stored in the balance information 23.

  The sales target information 25 stored in the information database 20 is information including at least one of product information and store information related to the sales target. In the present embodiment, a product information table 25a for storing product information and a store information table 25b for storing store information are included (see FIG. 2).

  The merchandise information table 25a stores an ID for identifying a merchandise to be sold, and merchandise attributes of the merchandise (for example, attributes classified into categories such as “groceries”, “daily necessities”, “preference”). Yes.

  The store information table 25b stores an ID for identifying the store C and store attributes of the store C (for example, attributes classified into categories such as “retail store”, “restaurant”, and “general store”). Yes.

  Next, the prepaid card management server 10 is composed of a computer, and functions as a purpose information assigning unit 11, a sales target registration unit 12, and a usability determination unit 13 by executing a computer program.

(About the purpose information giving unit 11)
The purpose information giving unit 11 executes a process for giving purpose information to the prepaid card B. For example, when a request for registering the purpose of use of the prepaid card B is issued from the user A, record information is created based on the card ID and the purpose of use of the prepaid card B specified in the request, and the record information is Register in the purpose table 24a.

  In the present embodiment, product information and store information are provided as purpose information registered in the use purpose table 24a. The merchandise information is information that defines merchandise that can be purchased with the prepaid card B. The store information is information that defines a store C where the prepaid card B can be used.

(About the sales target registration unit 12)
The sales target registration unit 12 executes processing for registering product information and store information in the information database 20.

  The processing by the sales target registration unit 12 is executed by acquiring a request for registering the sales target information 25 from the system administrator. When the request is a request for registering product information, record information is created based on the product ID and product attribute specified in the request, and the record information is registered in the product information table 25a. When the request is a request for registering store information, record information is created based on the store ID and store attribute specified in the request, and the record information is registered in the store information table 25b.

  For example, an existing code such as a JAN code may be used as the product ID. Further, as the store ID, the POS terminal of the store C or the store server ID may be used.

  Incidentally, the product information in the usage purpose table 24a corresponds to the product attributes in the product information table 25a. For example, products are classified by registering in the product attribute in the product information table 25a such that the product attribute of food is “A”, and the product attribute of daily necessities other than food is “I”. Whether or not the product can be purchased with the prepaid card B is managed by the use purpose table 24a.

  The store information in the usage purpose table 24a corresponds to the store attribute in the store information table 25b. For example, the store attribute of the retail store such as a supermarket is classified as “A”, the store attribute of the restaurant is “B”, and the store attribute is registered in the store information table 25b to classify the store C. The use purpose table 24a manages whether the prepaid card B can be used in the classified store C.

(About the usability determination unit 13)
The usability determination unit 13 determines whether or not the prepaid card B is usable when a payment process using the prepaid card B occurs.

  For example, when the user A uses the prepaid card B at the store C, a payment processing request is issued from the terminal of the store C to the prepaid card management server 10. When the prepaid card management server 10 acquires the payment processing request, the availability determination unit 13 extracts the product information from the product information table 25a of the information database 20 using the product ID of the purchase target product included in the payment processing request as a key. . Further, the availability determination unit 13 extracts store information from the store information table 25b of the information database 20 using the store ID of the store C included in the payment processing request as a key. Further, the usability determination unit 13 extracts purpose information from the purpose-of-use table 24a of the information database 20 using the card ID of the prepaid card B included in the payment processing request as a key.

  The usability determination unit 13 compares the “product information” and “store information” thus extracted with “purpose information” to determine whether or not the prepaid card B is usable. When the availability determination unit 13 determines that the prepaid card B can be used, the determination result is notified to the terminal of the store C, and the payment by the prepaid card B is completed. On the other hand, when the availability determination unit 13 determines that the prepaid card B is unusable, the determination result is notified to the terminal of the store C, and payment by the prepaid card B becomes an error.

  The determination process by the usability determination unit 13 will be specifically described with reference to the table of FIG. In the example of FIG. 2, six prepaid cards B with card IDs “0” to “5” are registered in the use purpose table 24a. Also, four products with product IDs “0” to “3” are registered in the product information table 25a. Also, four stores C with store IDs “0” to “3” are registered in the store information table 25b.

  First, since the prepaid card B with the card ID “0” has “A” registered in the product information, it can be used to purchase a product with the product attribute “A”. Moreover, since the prepaid card B has no store information registered, it can be used at any store C. Therefore, when trying to purchase a product with the product ID “0” or “1” with this prepaid card B, the availability determination unit 13 determines that the prepaid card B is usable, and the product ID is “2”. Or when it is going to purchase the goods of "3", it determines with the prepaid card B being unusable.

  Since the prepaid card B with the card ID “1” has “A, B” registered in the product information, it can be used to purchase a product with the product attribute “A” or “I”. Moreover, since the prepaid card B has no store information registered, it can be used at any store C. Therefore, when trying to purchase any of the products with product IDs “0”, “1”, and “2” with this prepaid card B, the availability determination unit 13 determines that the prepaid card B is usable, and the product When trying to purchase a product whose ID is “3”, it is determined that the prepaid card B is unusable.

  The prepaid card B with the card ID “2” can be used in the store C whose store attribute is “A” because “A” is registered in the store information. In addition, since the prepaid card B has no product information registered, any product can be purchased. Therefore, when the prepaid card B is used in the store C whose store ID is “0”, the use determination unit 13 determines that the prepaid card B is usable, and the store IDs are “1”, “2”, “ When the prepaid card B is used in any store C of “3”, it is determined that the prepaid card B is unusable.

  The prepaid card B with the card ID “3” can be used at the store C having the store attribute “A” or “B” because “A, B” is registered in the store information. In addition, since the prepaid card B has no product information registered, any product can be purchased. Therefore, when this prepaid card B is used in any store C whose store ID is “0”, “1”, or “2”, the availability determination unit 13 determines that the prepaid card B is usable, When the prepaid card B is used at the store C whose ID is “3”, it is determined that the prepaid card B cannot be used.

  Since the prepaid card B with the card ID “4” has neither product information nor store information registered, any product can be purchased at any store C. Therefore, it can be used without any particular limitation, and the availability determination unit 13 always determines that the prepaid card B can be used.

  Since the prepaid card B with the card ID “5” has “A” registered in the product information, it can be used to purchase a product with the product attribute “A”. Further, since “A” is registered in the store information, it can be used in the store C whose store attribute is “A”. Therefore, when the store ID is “0” and the product ID “0” or “1” is to be purchased, the availability determination unit 13 determines that the prepaid card B can be used. In other cases, it is determined that the prepaid card B is unusable.

(About payment processing)
Next, a payment process when the user A tries to purchase a product using the prepaid card B at the store C will be described with reference to the flow of FIG.

  When the user A uses the prepaid card B at the store C, the card ID of the prepaid card B is read at the terminal of the store C. This card ID is transmitted to the prepaid card management server 10 together with the merchandise ID and store ID to be settled. As shown in step S100 shown in FIG. 3, the payment process is started when the prepaid card management server 10 acquires the transmitted information (payment request). If a payment request is acquired, it will progress to step S101.

  In step S101, the availability determination unit 13 acquires the sales target information 25 related to the payment process. In the present embodiment, product information is extracted based on the product ID included in the payment request with reference to the product information table 25a stored in the information database 20. In addition, when there are a plurality of product IDs included in the payment request, each product information is extracted. Further, with reference to the store information table 25b stored in the information database 20, the store information is extracted by the store ID included in the payment request. Thus, if product information and store information are extracted, it will progress to step S102.

  In step S102, the availability determination unit 13 acquires purpose information related to payment processing. In the present embodiment, the purpose information is extracted based on the card ID included in the payment request with reference to the use purpose table 25a stored in the information database 20. After the purpose information is extracted in this way, the process proceeds to step S103.

  In step S103, the usability determination unit 13 compares the sales target information 25 acquired in step S101 with the purpose information acquired in step S102, and determines whether or not the prepaid card B is usable. Then, the process proceeds to step S104.

  In step S104, the determination result of the usability determination unit 13 in step S103 is checked. If it is determined that the prepaid card B is usable, the process proceeds to step S105, where it is determined that the prepaid card B is unusable. In this case, the process proceeds to step S106.

  When the process proceeds to step S105, the prepaid card management server 10 performs a predetermined settlement process. For example, by rewriting the balance information 23 in the information database 20, the balance of the prepaid card B is reduced by the amount of payment, or a usage history is created based on the purchased product and information on the store C, and this usage history is stored in the information database 20. Processing such as storing in the usage history information 22 is performed. And it notifies that the sale was permitted with respect to the terminal of the shop C, and complete | finishes a process.

  On the other hand, when it progresses to step S106, the prepaid card management server 10 does not perform a predetermined clearing process and notifies the terminal of the store C that the sale is impossible. Then, the process ends.

(Example of use)
A usage example when the above-described prepaid card management system and prepaid card management method are used in a campaign for regional activation will be described with reference to FIG.

  In this example, a privilege granter (for example, a shopping district promotion association) distributes a prepaid card B that can be used only in a shopping district in a specific area to a beneficiary (for example, a lottery winner), for example as a lottery prize. Such a case is assumed.

  In this example, the privilege giver first registers the purpose of use of the prepaid card B. Specifically, the purpose information is given to the prepaid card B, and the process of registering product information and store information in the information database 20 is executed. Thereby, the registered prepaid card B can be used only for purchasing a specific store C or a specific product.

  The prepaid card B thus registered is given to the beneficiary and used for shopping at the store C. When the prepaid card B is used at the store C, the above-described payment process is started. That is, if the prepaid card B is used for the purpose, payment is completed normally, but if the prepaid card B is used for a purpose, a payment error occurs.

  Note that the privilege giver may be able to refer to the use history information 22 of the prepaid card B used by the beneficiary. In this way, if the grantee can refer to the usage history, it will be possible to check in more detail whether the beneficiary has used the fraudulent usage method, and it will be possible to see what products have been purchased. It can also be used for analysis.

  When the usage history can be referred to, for example, the usage history reference authority may be given to a specific user in advance. In the above example, the privilege giver can issue a request to the prepaid card management system so that the privilege granter can be given the authority to refer to the use history of the prepaid card B. And the privilege granter should just be able to access a prepaid card management system via the internet, and to refer to a use log | history freely.

(Summary)
As described above, according to the present embodiment, when a payment request by the prepaid card B is generated, the sales object information 25 including at least one of the product information and the store information related to the sales object, and the prepaid card B The purpose information registered for each purpose of use is acquired, and the sales object information 25 is compared with the purpose information to determine whether or not the prepaid card B is usable. That is, the purpose of use can be designated in advance for the prepaid card B, and the use purpose of the prepaid card B can be determined by checking the purpose of use.

  Therefore, according to the present embodiment, money or points can be given by specifying the purpose of use, and the money or points can be prevented from being used outside the purpose. In addition, since such a system can be realized by applying an existing prepaid card system, it is not necessary to provide a dedicated ticket terminal, and the introduction cost of the system can be reduced.

  Although not specifically described above, as an attribute of the prepaid card B, it may be possible to designate whether or not a remittance request by the prepaid card B is permitted. For example, in the card information 24 related to a specific prepaid card B, it is possible to register whether or not money can be transferred to another account using the balance of the prepaid card B. An error may occur when attempting to execute the remittance process. If it is possible to specify whether or not to permit a remittance request in this way, it is possible to prevent usage such as transferring the balance of the prepaid card B to another account and using it for other purposes.

  Although not specifically described above, as an attribute of the prepaid card B, it may be possible to designate whether or not a withdrawal request by the prepaid card B is permitted. For example, when it is possible to register in the card information 24 related to a specific prepaid card B whether or not the balance of the prepaid card B can be withdrawn and an attempt is made to execute a withdrawal process with the prepaid card B from which the balance cannot be withdrawn May cause an error. If it is possible to specify whether or not to allow the withdrawal request in this way, it is possible to prevent the usage of drawing out the balance of the prepaid card B and using it for a purpose other than the intended purpose.

  In the above-described embodiment, the store attribute that is an attribute for each store C is registered in the store information table 25b, but the embodiment of the present invention is not limited thereto. For example, instead of the store attribute or in addition to the store attribute, information regarding the position of the store C may be registered. Then, it may be determined whether or not the prepaid card B is usable by using the information relating to the position of the store C. If the information relating to the location of the store C is used, the store C where the prepaid card B can be used can be limited without specifying store information individually. For example, the prepaid card B can be used only in a local shopping street. This is convenient when used as a usable voucher. Note that the information related to the position of the store C may be registered in advance, or may be dynamically acquired using GPS or the like.

  In the above-described embodiment, the product information and the store information are provided as the sales target information 25. However, the embodiment of the present invention is not limited to this, and the product information and the store information as the sales target information 25. Only one of them may be provided.

  In the above-described embodiment, the product information is registered in the product information table 25a. However, the embodiment of the present invention is not limited to this. For example, the JAN code may be registered directly in the product information of the usage purpose table 24a without using the product information table 25a.

  In the above-described embodiment, the example in which the availability determination unit 13 refers to the usage purpose table 24a of the information database 20 has been described. However, the embodiment of the present invention is not limited thereto. For example, the target information may be stored in an IC chip or a magnetic tape incorporated in the prepaid card B. In this case, the purpose information of the prepaid card B can be acquired without referring to the information database 20.

  Moreover, although the case where the prepaid card B was used in the actual store was described in the above-described embodiment, the same processing can be performed when the prepaid card B is used in the store C on the net.

  Further, in the above description, the prepaid card B handles money. However, the embodiment of the present invention is not limited to this, and the card has a value equivalent to money, for example, points for a point service. Also good.

DESCRIPTION OF SYMBOLS 10 Prepaid card management server 11 Purpose information grant part 12 Sales object registration part 13 Usability determination part 20 Information database 21 User information 22 Usage history information 23 Balance information 24 Card information 24a Use purpose table 25 Sale object information 25a Product information table 25b Store Information table A User B Prepaid card C Store

Claims (8)

  When a payment request by a prepaid card occurs, obtain sales target information including at least one of product information or store information related to the sales target, and purpose information that registers the purpose of use for each prepaid card, A prepaid card management system, wherein the prepaid card is determined whether or not the prepaid card can be used by comparing the sales object information and the purpose information.   2. The prepaid card management system according to claim 1, wherein it is possible to designate whether or not to permit a remittance request by the prepaid card as an attribute of the prepaid card.   3. The prepaid card management system according to claim 1, wherein whether or not to allow a withdrawal request by the prepaid card can be specified as an attribute of the prepaid card.   The prepaid card management according to any one of claims 1 to 3, wherein it is determined whether or not a prepaid card is usable by using information related to a store position included in the store information. system. A prepaid card management method for causing a computer to execute,
When a payment request by a prepaid card occurs, obtain sales target information including at least one of product information or store information related to the sales target, and purpose information that registers the purpose of use for each prepaid card, A prepaid card management method, comprising: comparing sales target information with the purpose information to determine whether or not a prepaid card can be used.   6. The prepaid card management method according to claim 5, wherein whether the remittance request by the prepaid card is permitted or not can be specified as an attribute of the prepaid card.   7. The prepaid card management method according to claim 5 or 6, characterized in that it is possible to designate whether or not a withdrawal request by the prepaid card is permitted as an attribute of the prepaid card.   The prepaid card management according to any one of claims 5 to 7, wherein it is determined whether or not a prepaid card can be used using information related to a store location included in the store information. Method.

Images