JP7358324B2 - Prepaid payment service system, prepaid payment processing method, and program - Google Patents

Description

The present invention relates to a prepaid payment service system, a prepaid payment processing method, and a program.

Prepaid payment instruments such as prepaid cards are widely used. Some prepaid payment methods can be used in the same manner as credit cards at participating credit card stores.
Regarding prepaid payment methods that use credit card mechanisms, there is a known technology in which when a credit card company receives a sales claim for an amount that exceeds the balance on the prepaid card, it recovers funds equivalent to the shortfall from the user. (For example, see Patent Document 1).
This technology applies data to identify the initial available amount set within the prepaid amount associated with an application for issuance of prepaid payment instruments that can be used at a member store. a setting unit for storing in the storage unit in association with the ID information of the prepaid payment means; a determining unit for determining the guaranteed amount within the remaining amount of the available amount corresponding to the prepaid payment method; and the determined guaranteed amount. In addition, the data stored in the storage unit is changed so that the amount is not included in the remaining amount of the available amount, and at least a part of the billed amount included in the sales information is changed in advance in the payment process related to any prepaid payment method. Change the pool amount so that the determined guarantee amount is included in the pool amount, which indicates the accumulated amount of guarantee deposits that will be used as the source to cover the loss in the event that a loss occurs due to non-approval. and a changing section.

International Publication No. 2014/178121

With the above-mentioned technology, the initial available amount is set within the range of the prepaid amount associated with the application for issuance of a prepaid payment instrument, so when applying for the issuance of a prepaid payment instrument, the usage that you want to set If the prepaid amount is less than the available amount, the available amount must be set to the same amount as the prepaid amount.
In order to increase the available amount, new procedures are required after paying the prepaid amount.

The present invention has been made in consideration of such circumstances, and its purpose is to provide a prepaid payment service system, a prepaid payment processing method, and a program that can improve the convenience of prepaid payment means. Our goal is to provide the following.

(1) One aspect of the present invention is a determining unit that determines the available amount of each of the plurality of payment tools based on the total amount of prepayments paid into the deposit/withdrawal account of the prepaid payment method; a processing unit that sets a usage limit for each of the plurality of payment tools; The limit amount is set as the usage limit amount, and when the total amount of the advance payment is changed, the determining unit is configured to set the limit amount as the usage limit amount, and when the total amount of the advance payment is changed, the determining unit determines the amount of each of the plurality of payment tools based on the changed total amount. It is a prepaid payment service system that updates the available amount.
(2) One aspect of the present invention is that in the prepaid payment service system according to (1) above, the determining unit is configured to determine whether the prepaid payment is paid into the deposit/withdrawal account of the prepaid payment means. , the prepaid payment service system updates the available amount of each of the plurality of payment tools based on the changed total amount when the total amount of the prepaid amount is changed.
(3) One aspect of the present invention is the prepaid payment service system described in (1) or (2) above, in which the determining unit determines whether the payment has been made to the deposit/withdrawal account of the prepaid payment means. A prepaid payment service system that determines the usable amount of each of the plurality of payment tools based on the total amount of the advance payment and the usage limit of each of the plurality of payment tools set by the processing unit. It is.
(4) One aspect of the present invention is that in the prepaid payment service system according to (3) above, the determining unit determines the total amount of the prepaid amount by using any of the plurality of payment tools. This is a prepaid payment service system that updates the available amount of the used payment tool when the amount is debited.
(5) One aspect of the present invention is the prepaid payment service system according to (3) or (4) above, in which the determining unit determines the available amount of each of the plurality of payment tools to the processing unit. If the usage limit of each of the plurality of payment tools set by In the prepaid payment service system, if the prepaid amount is less than the total amount, the available amount is determined for each of the plurality of payment tools.
(6) One aspect of the present invention is the prepaid payment service system according to any one of (3) to (5) above, in which the processing unit selects one of the payment tools from among the plurality of payment tools. This is a prepaid payment service system that sets the usage limit of one of the payment tools to zero when restricting the usage of the tool.
(7) One aspect of the present invention is a prepaid payment processing method executed by a prepaid payment service system including a processor, the total amount of prepaid money paid into the deposit/withdrawal account of a prepaid payment means. a step of determining the available amount of each of the plurality of payment tools based on the step, a step of setting a usage limit of each of the plurality of payment tools, and when the total amount of the advance payment is changed, and updating the available amount of each of the plurality of payment tools based on the changed total amount, wherein the entered limit amount is higher than the total amount of the advance payment. In this prepaid payment processing method, the input limit amount is set as the usage limit amount in some cases.
(8) One aspect of the present invention is the step of causing the computer to determine the available amount of each of the plurality of payment tools based on the total amount of prepayments paid into the deposit/withdrawal account of the prepaid payment means. and setting a usage limit for each of the plurality of payment tools, and when the total amount of the advance payment is changed, each of the plurality of payment tools is set based on the total amount after the change. updating the available amount, and when the input limit amount is higher than the total amount of the advance payment, the input limit amount is set as the usage limit amount. , is a program.

According to the present invention, it is possible to obtain the effect that the convenience of the prepaid payment means can be improved.

FIG. 1 is a block diagram illustrating a configuration example of a prepaid payment service system according to an embodiment. FIG. 1 is a diagram showing an overview of a prepaid payment service system according to the present embodiment. It is a diagram showing an example of a card DB. It is a diagram showing an example of a user information DB. 2 is a sequence chart showing an example 1 of operation of the prepaid payment service system according to the present embodiment. It is a sequence chart showing example 2 of operation of the prepaid payment service system according to the present embodiment. 12 is a sequence chart showing a third example of the operation of the prepaid payment service system according to the present embodiment. It is a sequence chart showing example 4 of the operation of the prepaid payment service system according to the present embodiment.

Next, the prepaid payment service system, prepaid payment processing method, and program of this embodiment will be explained with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.
In addition, in all the figures for explaining the embodiment, parts having the same functions are denoted by the same reference numerals, and repeated explanations will be omitted.
Furthermore, "based on XX" as used herein means "based on at least XX", and includes cases where it is based on another element in addition to XX. Moreover, "based on XX" is not limited to the case where XX is used directly, but also includes the case where XX is subjected to calculations or processing. "XX" is an arbitrary element (for example, arbitrary information).

(Embodiment)
Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a block diagram showing a configuration example of a prepaid payment service system according to an embodiment. In FIG. 1, a prepaid payment service system 1 includes a management device 30 and a payment processing device 40. The terminal device 10, the financial institution 15, the store terminal 20, the management device 30, and the payment processing device 40 can communicate with each other via the communication network NW. The communication network NW includes the Internet, a WAN (Wide Area Network), a LAN (Local Area Network), a public line, a provider device, a private line, a wireless base station, and the like.
The terminal device 10 is a terminal used by the administrator M. An example of the administrator M is a person who requests the prepaid payment service system to issue a payment tool. As the terminal device 10, for example, a stationary computer device may be used, or a portable computer device such as a smartphone or a tablet computer (tablet PC) may be used.

The management device 30 and the payment processing device 40 create a wallet in response to a request made by the administrator M to create a deposit/withdrawal account (hereinafter referred to as a "wallet") for a prepaid payment method.
The management device 30 and the payment processing device 40 are associated (linked) with the wallet in response to a request made by the administrator M to issue a payment tool. Issue multiple payment tools. Examples of payment tools are prepaid cards, credit cards, virtual cards. For example, in the case of a credit card, the function of a payment tool may be added to the function of a deferred payment method that the credit card has. In this embodiment, as an example, the case where a payment tool function is added to a credit card will be explained. Hereinafter, credit cards with payment tool functions may be collectively referred to as cards.
The payment processing device 40 sets a usage limit for each of the plurality of payment tools. The payment processing device 40 also processes multiple payment methods based on the total amount of prepayments paid (deposited) into the deposit/withdrawal account of the prepaid payment method and the usage limit of each of the multiple payment tools. Determine the amount available for each of the payment tools.

The administrator M requests the prepaid payment service system to create a wallet by operating the terminal device 10. The administrator M inputs a user identifier (user ID) and information indicating that a wallet creation request is to be made into the terminal device 10. Here, the user ID is information that can uniquely identify the administrator M, such as the administrator M's e-mail address.
The terminal device 10 acquires the user ID and information indicating that a request is made to create a wallet. The terminal device 10 creates a wallet creation request message addressed to the management device 30, including the acquired user ID and information indicating that a wallet creation is requested. The terminal device 10 transmits the created wallet creation request message to the management device 30.
The management device 30 receives the wallet creation request message sent by the terminal device 10. The management device 30 acquires the user ID included in the received wallet creation request message and information indicating that the wallet creation is requested. The management device 30 creates (opens) a wallet based on the acquired information indicating that a wallet creation is requested. The management device 30 associates and stores the wallet ID of the created wallet and the user ID. Here, the wallet ID is information for identifying a deposit/withdrawal account of a prepaid payment means that can be used with each of a plurality of card IDs.
The management device 30 creates a wallet registration request message that includes the wallet ID of the created wallet and is addressed to the payment processing device 40. The management device 30 transmits the created wallet registration request message to the payment processing device 40.

The payment processing device 40 stores a user information DB. The user information DB is user information that associates multiple confidential IDs, multiple card IDs, multiple usage limits, multiple usage availability, multiple wallet IDs, and multiple usage amounts. Store one or more.
The payment processing device 40 receives the wallet registration request message sent by the management device 30. The payment processing device 40 acquires the wallet ID included in the received wallet registration request message. The payment processing device 40 creates user information including the acquired wallet ID. The processing unit 43 includes the created user information in the user information DB 49a. The payment processing device 40 creates a wallet registration response message that includes the wallet ID and is addressed to the management device 30. The payment processing device 40 transmits the created wallet registration response message to the management device 30.

The management device 30 receives the wallet registration response message sent by the payment processing device 40. The management device 30 acquires the wallet ID included in the received wallet registration response message. The management device 30 creates a wallet creation response message that includes the acquired wallet ID and is addressed to the terminal device 10. The management device 30 transmits the created wallet creation response message to the terminal device 10.

The terminal device 10 receives the wallet creation response message sent by the management device 30. The terminal device 10 acquires the wallet ID included in the received wallet creation response message. The terminal device 10 displays the acquired wallet ID.
By operating the terminal device 10, the manager M requests the prepaid payment service system to issue a payment tool. The administrator M inputs the wallet ID, the number of issued cards, the usage limit for each card, and the availability of each card into the terminal device 10. Here, the number of issued cards is the number of cards issued in association with (linked to) the wallet opened by the administrator M. The usage limit for each card is the amount that can be paid with the card within a predetermined period. Here, the predetermined period can be specified as any period such as daily, weekly, monthly, quarterly, semiannually, annually, or semiannually. Card usage can be temporarily restricted by setting the usage limit to zero. Usage availability for each card is information indicating whether or not each card can be used.
The terminal device 10 acquires the wallet ID, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used. The terminal device 10 includes the acquired wallet ID, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used, and issues a payment tool whose destination is the management device 30. Create a request message. The terminal device 10 transmits the created payment tool issue request message to the management device 30.

The management device 30 requests the card issuing company to issue a card number. The management device 30 acquires a plurality of card numbers issued by a card issuing company, and registers each of the acquired card numbers in a card DB. The card DB stores a card number, a secret ID (hereinafter referred to as a "confidential ID") used by the management device 30 and the payment processing device 40, and an expiration date in association with each other.
The management device 30 receives the payment tool issue request message sent by the terminal device 10. The management device 30 acquires the wallet ID included in the received payment tool issue request message, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used. do. The management device 30 sets each of the plurality of payment tools based on the obtained information indicating the number of issued cards.

The management device 30 allocates and associates a plurality of card numbers with a plurality of payment tools from among the card numbers registered in the card DB.
The management device 30 stores a wallet ID, a confidential ID stored in association with each of a plurality of card numbers respectively assigned to a plurality of payment tools, information indicating a usage limit for each card, and usage information for each card. A payment tool registration request message is created that includes information indicating whether or not the payment tool is accepted and is addressed to the payment processing device 40. The management device 30 transmits the created payment tool registration request message to the payment processing device 40.

The payment processing device 40 receives the payment tool registration request message sent by the management device 30. The payment processing device 40 acquires a wallet ID, a plurality of confidential IDs, information indicating a usage limit for each card, and information indicating availability for each card included in the received payment tool registration request message. . The payment processing device 40 creates the same number of card IDs as the plurality of confidential IDs, and associates each of the created plurality of card IDs with each of the plurality of confidential IDs. Here, the card ID refers to a name, a code, a character string, a numerical value, or a combination of one or more of these used to uniquely distinguish a certain card from a plurality of cards.
The payment processing device 40 associates a plurality of confidential IDs, a plurality of card IDs, a plurality of information indicating usage limits, a plurality of information indicating availability of usage, and a wallet ID in the user information DB. memorize it.
The payment processing device 40 creates a payment tool registration response message that includes a plurality of pieces of information that associate confidential IDs and wallet IDs and is addressed to the management device 30. The payment processing device 40 transmits the created payment tool registration response message to the management device 30.

The management device 30 receives the payment tool registration response message sent by the payment processing device 40. The management device 30 acquires a plurality of pieces of information that associate the confidential ID and wallet ID included in the received payment tool registration response message. The management device 30 acquires a plurality of card numbers stored in association with each of the plurality of confidential IDs from the card DB based on the plurality of pieces of information in which the obtained confidential IDs and wallet IDs are associated with each other. The management device 30 creates a payment tool issue response message that includes a plurality of pieces of information that associate the card number and wallet ID and is addressed to the terminal device 10 . The management device 30 transmits the created payment tool issue response message to the terminal device 10.

The terminal device 10 receives the payment tool issue response message sent by the management device 30. The terminal device 10 acquires a plurality of pieces of information that associate the card number and wallet ID included in the received payment tool issue response message. The terminal device 10 displays the acquired information. Administrator M refers to multiple pieces of information that associate card numbers and wallet IDs, and transfers the card 5 with the card number to the corresponding multiple users (messengers) (hereinafter referred to as "user U"). Issued to.

The administrator M uses the terminal device 10 to designate the wallet ID and the amount to be deposited, thereby performing an operation for depositing money into the wallet corresponding to the wallet ID. Based on the operation of the administrator M, the terminal device 10 creates a prepaid payment method (electronic money) deposit request message addressed to the financial institution 15, including information indicating the wallet ID and information indicating the deposit amount. do. The terminal device 10 transmits the created prepaid payment means (electronic money) deposit request message to the financial institution 15.

The financial institution 15 receives the prepaid payment method (electronic money) deposit request message sent by the terminal device 10 . The financial institution 15 deposits the amount corresponding to the deposit amount into the wallet corresponding to the wallet ID, based on the wallet ID included in the prepaid payment method (electronic money) deposit request message and the information indicating the deposit amount. Perform processing. The financial institution 15 creates a prepaid payment method (electronic money) deposit completion message that includes the wallet ID and information indicating the deposit amount and addresses the payment processing device 40 . The financial institution 15 transmits the created prepaid payment method (electronic money) deposit completion message to the payment processing device 40 .

The payment processing device 40 receives the prepaid payment method (electronic money) deposit completion message sent by the financial institution 15 . Based on the wallet ID included in the received prepaid payment method (electronic money) deposit completion message and the information indicating the deposit amount, the payment processing device 40 sends the information indicating the deposit amount to the wallet corresponding to the wallet ID. Confirm that the appropriate amount has been deposited.
After confirming that the amount corresponding to the deposit amount has been deposited into the wallet corresponding to the wallet ID, the payment processing device 40 associates the wallet ID with each of the plurality of card IDs associated with the wallet ID. The available amount is determined and the determined available amount is stored.

FIG. 2 is a diagram showing an overview of the prepaid payment service system according to the present embodiment.
FIG. 2 shows a financial institution 15, a wallet W to which money is deposited from the financial institution, and payment tools PT-1, payment tools PT-2, . . . , payment tools PT- associated with the wallet ID of the wallet W. N (N is an integer with N>1).
Wallet W is a deposit/withdrawal account for a prepaid payment method and has a balance. One wallet W is associated with payment tool PT-1, payment tool PT-2, . . . , payment tool PT-N.
Payment tool PT-1, payment tool PT-2, . . . , payment tool PT-N are each associated (linked) with the wallet account (wallet ID) of wallet W. Each of payment tool PT-1, payment tool PT-2, . . . , payment tool PT-N does not have a balance.
Based on the wallet ID included in the prepaid payment method (electronic money) deposit request message sent by the terminal device 10 and the information indicating the deposit amount, the financial institution 15 transfers the deposit amount to the wallet W corresponding to the wallet ID. The corresponding amount will be deposited. After confirming that the amount corresponding to the deposit amount has been deposited into the wallet W corresponding to the wallet ID, the payment processing device 40 sends the payment tool PT-1 and payment tool PT-2 associated with the wallet ID. , . . . determines the available amount of payment tool PT-N and stores the determined available amount. A usage limit is set for each of the payment tools PT-2, . In other words, the usage limit of each of the payment tools PT-2, . . . , payment tools PT-N can be set to an amount higher than the balance of the wallet W. As a result, it is not possible to make a payment for an amount exceeding the balance of Wallet W. Returning to FIG. 1, the explanation will be continued.
The payment processing device 40 creates a prepaid payment means (electronic money) deposit response message that includes information indicating that the money has been deposited into the wallet and is addressed to the terminal device 10 . The payment processing device 40 transmits the created prepaid payment means (electronic money) deposit response message to the terminal device 10.
The terminal device 10 receives the prepaid payment method (electronic money) deposit response message sent by the payment processing device 40. The terminal device 10 acquires information indicating that the prepaid payment means (electronic money) has been deposited in the wallet, which is included in the received prepaid payment means (electronic money) deposit response message. The terminal device 10 notifies the administrator M that the deposit has been made by displaying information indicating that the deposit has been deposited in the acquired wallet.

One user U who has been issued a card 5 presents the card 5 when making a purchase. Here, as an example, we will continue to explain the case where user U goes shopping at a store. For example, an information code is assigned to a product to be purchased. Commodities are physical goods that are produced, distributed, and exchanged in economic activities. The information code represents product identification information, which is information for identifying a product, using information such as numerical values and characters. Examples of information codes are barcodes, which are information such as numbers, letters, and symbols converted into one-dimensional codes according to certain rules, two-dimensional codes, which represent a lot of information by arranging dots vertically and horizontally, and QR. Includes code (registered trademark), etc.
The store terminal 20 uses an imaging device to image the information code attached to the product. The store terminal 20 acquires information indicating the price of the product based on the image captured by the imaging device. Further, the store terminal 20 acquires the card number represented on the card 5 presented by the user U using a reading device such as an IC card reader.
The store terminal 20 creates a debit request message addressed to the management device 30, including the acquired card number and information indicating the price P of the product. The store terminal 20 transmits the created withdrawal request message to the management device 30.
The management device 30 receives the debit request message sent by the store terminal 20. The management device 30 acquires the card number and information indicating the price P included in the received debit request message. The management device 30 acquires the expiration date stored in association with the acquired card number from the card DB. The management device 30 confirms that the card 5 is within its expiration date based on the acquired expiration date. After confirming that the card 5 is within its expiration date, the management device 30 acquires a confidential ID stored in association with the acquired card number. The management device 30 creates a payment request message that includes the acquired confidential ID and information indicating the price P and is addressed to the payment processing device 40. The management device 30 transmits the created payment request message to the payment processing device 40.

The payment processing device 40 receives the payment request message sent by the management device 30. The payment processing device 40 acquires the confidential ID and information indicating the price P included in the received payment request message. The payment processing device 40 acquires, from the user information DB, information indicating the usage limit, information indicating availability, and information indicating the available amount that are stored in association with the acquired confidential ID.
The payment processing device 40 determines whether or not the service is available based on the acquired information indicating the availability. When determining that the payment processing device 40 can be used, the payment processing device 40 determines whether the price P is less than or equal to the available amount based on the acquired information indicating the price P and the information indicating the available amount. . The payment processing device 40 performs payment processing when determining that the price P is less than or equal to the available amount.
The payment processing device 40 creates a payment response message that includes the confidential ID and information indicating the payment result and is addressed to the management device 30. The payment result may indicate that the payment has been completed, and if the payment is not completed, the reason may be provided. The payment processing device 40 transmits the created payment response message to the management device 30.

The management device 30 receives the payment response message sent by the payment processing device 40. The management device 30 acquires the confidential ID included in the received payment response message, and acquires the card number stored in association with the acquired confidential ID from the card DB. The management device 30 creates a debit response message containing the acquired card number and the payment result and addressed to the store terminal 20. The management device 30 transmits the created withdrawal response message to the store terminal 20.

The store terminal 20 receives the withdrawal response message sent by the management device 30. The store terminal 20 acquires the card number included in the received debit response message and the payment result. The store terminal 20 notifies the user U of the payment result regarding the card number by displaying the acquired card number and the payment result.
Details of the management device 30, the payment processing device 40, and the terminal device 10 included in the prepaid payment service system will be sequentially described below.

[Management device 30]
The management device 30 is realized by a device such as a personal computer, a server, or an industrial computer. The management device 30 includes, for example, a communication section 31, a reception section 32, a setting section 35, a conversion section 36, a determination section 37, a creation section 38, and a storage section 39.
The communication unit 31 is realized by a communication module. Specifically, the communication unit 31 is configured by a device that performs wired communication. Further, the communication unit 31 may be configured by a wireless device that performs wireless communication using a wireless communication technology such as LTE or wireless LAN. The communication unit 31 communicates between the terminal device 10, the store terminal 20, and the payment processing device 40 via the communication network NW.
Specifically, the communication unit 31 receives the wallet creation request message transmitted by the terminal device 10 and transmits the wallet creation response message outputted by the creation unit 38 to the terminal device 10. The communication unit 31 transmits the wallet registration response message output by the creation unit 38 to the payment processing device 40, and receives the wallet registration response message transmitted by the payment processing device 40. The communication unit 31 receives the payment tool issue request message sent by the terminal device 10 and sends the payment tool issue response message output by the creation unit 38 to the terminal device 10. The communication unit 31 transmits the payment tool registration request message output by the creation unit 38 to the payment processing device 40, and receives the payment tool registration response message transmitted by the payment processing device 40. The communication unit 31 receives the withdrawal request message sent by the store terminal 20 and transmits the withdrawal response message outputted by the creation unit 38 to the store terminal 20. The communication unit 31 transmits the payment request message output by the creation unit 38 to the payment processing device 40, and receives the payment response message sent by the payment processing device 40.

The storage unit 39 is realized by an HDD (Hard Disk Drive), a flash memory, a RAM (Random Access Memory), a ROM (Read Only Memory), or the like. The storage unit 39 stores a card DB 39a. The card DB 39a may be stored on the cloud.
FIG. 3 is a diagram showing an example of a card DB. The card DB 39a is information in a table format that associates card numbers, confidential IDs, and expiration dates. In the example shown in FIG. 3, the card ID 39a is associated with the card number "Card Number #1", the confidential ID "Confidential ID #1", and the expiration date "2020/04", and the card number "Card Number #2", the confidential ID "Confidential ID #2", and the expiration date "2021/05" are associated, and the card number "Card number #3", the confidential ID "Confidential ID #3", and the expiration date "2021/05" are associated. 2022/03” are stored in association with each other. These pieces of information are registered when the management device 30 acquires a plurality of card numbers issued by a card issuing company. Returning to FIG. 1, the explanation will be continued.

In the receiving unit 32, setting unit 35, converting unit 36, determining unit 37, and creating unit 38, a hardware processor such as a CPU (Central Processing Unit) executes a program (software) stored in a storage unit 39. This is achieved by In addition, some or all of these functional units may be implemented using hardware (circuits) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit). (including circuitry), or may be realized by collaboration between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage device such as a DVD or CD-ROM. It is stored in a medium (non-transitory storage medium), and may be installed by loading the storage medium into a drive device.

Regarding the reception unit 32, the setting unit 35, the conversion unit 36, the determination unit 37, and the creation unit 38, the processing when the administrator M requests the prepaid payment service system to create a wallet, and the process that the administrator M The issuance of a payment tool will be explained separately into a process when the prepaid payment service system is requested and a process when the user U makes a purchase at a store.
The following describes the process when administrator M requests the prepaid payment service system to create a wallet.
The communication unit 31 receives the wallet creation request message sent by the terminal device 10. The communication unit 31 outputs the received wallet creation request message to the reception unit 32.
The reception unit 32 receives the wallet creation request message output by the communication unit 31. The reception unit 32 acquires the user ID included in the received wallet creation request message and information indicating that the wallet creation is requested. The reception unit 32 outputs the acquired user ID and information indicating that a wallet creation is requested to the setting unit 35.

The setting unit 35 acquires the user ID output by the reception unit 32 and information indicating that a wallet creation is requested. The setting unit 35 creates (opens) a wallet based on the acquired information indicating that a wallet creation is requested. The setting unit 35 associates the wallet ID of the created wallet with the user ID and stores them in the storage unit 39.
The creation unit 38 creates a wallet registration request message that includes the wallet ID and is addressed to the payment processing device 40 . The creation unit 38 outputs the created wallet registration request message to the communication unit 31.

The communication unit 31 receives the wallet registration response message sent by the payment processing device 40 in response to the wallet registration request message. The communication unit 31 outputs the received wallet registration request message to the reception unit 32.
The reception unit 32 receives the wallet registration request message output by the communication unit 31. The receiving unit 32 obtains the wallet ID included in the received wallet registration request message. The reception unit 32 outputs the acquired wallet ID to the creation unit 38.
The creation unit 38 acquires the wallet ID output by the reception unit 32. Based on the acquired wallet ID, the creation unit 38 acquires, from the storage unit 39, a user ID stored in association with the wallet ID. The creation unit 38 creates a wallet creation response message that includes the user ID and wallet ID and is addressed to the terminal device 10 . The creation unit 38 outputs the created wallet creation response message to the communication unit 31.

The following describes the process when the administrator M requests the prepaid payment service system to issue a payment tool.
The communication unit 31 receives the payment tool issue request message sent by the terminal device 10. The communication unit 31 outputs the received payment tool issue request message to the reception unit 32 .
The reception unit 32 receives the payment tool issue request message output by the communication unit 31. The reception unit 32 acquires the wallet ID included in the received payment tool issue request message, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used. do. The reception unit 32 outputs the acquired wallet ID, information indicating the number of cards issued, information indicating the usage limit for each card, and information indicating whether each card can be used, to the setting unit 35.

The setting unit 35 acquires the wallet ID output by the receiving unit 32, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used. The setting unit 35 issues a plurality of payment tools based on the obtained information indicating the number of issued cards. The setting unit 35 sets the plurality of card numbers stored in the card DB 39a by assigning them to each of the plurality of issued payment tools.
The creation unit 38 creates a wallet ID, a confidential ID stored in association with the card number assigned to each of the plurality of payment tools, information indicating the usage limit for each card, and information indicating availability for each card. A payment tool registration request message is created that includes the information and is addressed to the payment processing device 40. The creation unit 38 outputs the created payment tool registration request message to the communication unit 31.

The communication unit 31 receives the payment tool registration response message sent by the payment processing device 40 in response to the payment tool registration request message. The communication unit 31 outputs the received payment tool registration response message to the reception unit 32.
The reception unit 32 receives the payment tool registration response message output by the communication unit 31. The reception unit 32 acquires a plurality of pieces of information that associate the confidential ID and wallet ID included in the received payment tool registration response message. The reception unit 32 outputs a plurality of pieces of information in which the acquired confidential ID and wallet ID are associated with each other to the creation unit 38.
The creation unit 38 acquires a plurality of pieces of information that associate the confidential ID and wallet ID output by the reception unit 32. The creation unit 38 acquires a plurality of card numbers stored in association with each of the plurality of confidential IDs from the card DB 39a, based on a plurality of pieces of information in which the obtained confidential IDs and wallet IDs are associated with each other. The creation unit 38 creates a payment tool issue response message that includes a plurality of pieces of information that associate the card number and wallet ID, and that is addressed to the terminal device 10 . The creation unit 38 outputs the created payment tool issue response message to the communication unit 31.

The process when user U shops at a store will be described.
The communication unit 31 receives the debit request message sent by the store terminal 20. The communication unit 31 outputs the received debit request message to the reception unit 32.
The reception unit 32 receives the debit request message output by the communication unit 31. The reception unit 32 acquires the card number and information indicating the price P included in the received debit request message. The reception unit 32 outputs the acquired card number and information indicating the price P to the determination unit 37.

The determining unit 37 acquires the card number output by the accepting unit 32 and information indicating the price P. The determination unit 37 acquires the expiration date stored in association with the acquired card number from the card DB 39a. The determination unit 37 determines whether or not the card 5 is within its expiration date based on the acquired expiration date. If the determining unit 37 determines that the card 5 is within its expiration date, it outputs the card number to the converting unit 36.
The conversion unit 36 acquires the card number output by the determination unit 37. The conversion unit 36 acquires a confidential ID stored in association with the acquired card number, and converts the card number into the acquired confidential ID. The conversion unit 36 outputs the confidential ID obtained by the conversion to the determination unit 37.
The determining unit 37 acquires the confidential ID output by the converting unit 36. The determining unit 37 outputs the confidential ID and information indicating the price P to the creating unit 38.
The creation unit 38 acquires the confidential ID output by the determination unit 37 and information indicating the price P. The creation unit 38 creates a payment request message that includes the confidential ID and information indicating the price P and is addressed to the payment processing device 40 . The creation unit 38 outputs the created payment request message to the communication unit 31.

If the determination unit 37 determines that the card 5 is not within the expiration date, the determination unit 37 includes the card number and the determination result as to whether the card 5 is within the expiration date (information indicating that the card 5 is not within the expiration date). is output to the creation section 38.
The creation unit 38 acquires the card number output by the determination unit 37 and the determination result as to whether the card 5 is within its expiration date. The creation unit 38 creates a debit response message addressed to the terminal device 10, including the acquired card number and the determination result as to whether the card 5 is within its expiration date. The creation unit 38 outputs the created withdrawal response message to the communication unit 31.

The communication unit 31 receives the payment response message sent by the payment processing device 40 in response to the payment request message. The communication unit 31 outputs the received payment response message to the reception unit 32.
The reception unit 32 acquires the payment response message output by the communication unit 31. The reception unit 32 acquires the confidential ID included in the acquired payment response message and information indicating the payment result. The reception unit 32 outputs the acquired confidential ID and information indicating the payment result to the creation unit 38.
The creation unit 38 acquires the confidential ID output by the reception unit 32 and information indicating the payment result. The creation unit 38 acquires the card number stored in association with the acquired confidential ID from the card DB 39a. The management device 30 creates a debit response message addressed to the store terminal 20, including the acquired card number and information indicating the payment result. The creation unit 38 outputs the created withdrawal response message to the communication unit 31.

[Payment processing device 40]
The payment processing device 40 is realized by a device such as a personal computer, a server, or an industrial computer. The payment processing device 40 includes, for example, a communication unit 41, a reception unit 42, a processing unit 43, a determination unit 44, a payment unit 45, a determination unit 47, a creation unit 48, and a storage unit 49.
The communication unit 41 is realized by a communication module. Specifically, the communication unit 41 is configured by a device that performs wired communication. Further, the communication unit 41 may be configured by a wireless device that performs wireless communication using a wireless communication technology such as LTE or wireless LAN. The communication unit 41 communicates between the terminal device 10, the financial institution 15, and the management device 30 via the communication network NW. Specifically, the communication unit 41 receives the wallet registration request message sent by the management device 30 and sends the wallet registration response message output by the creation unit 48 to the management device 30. The communication unit 41 receives the payment tool registration request message sent by the management device 30 and sends the payment tool registration response message output by the creation unit 48 to the management device 30. The communication unit 41 receives the prepaid payment means (electronic money) deposit completion message sent by the financial institution 15 and transmits the prepaid payment means (electronic money) deposit response message output by the creation unit 48 to the terminal device 10. do. The communication unit 41 receives the payment request message sent by the management device 30 and sends the payment response message output by the creation unit 48 to the management device 30.

The storage unit 49 is realized by an HDD, flash memory, RAM, ROM, or the like. The storage unit 49 stores a user information DB 49a. The user information DB 49a may be stored on the cloud.
FIG. 4 is a diagram showing an example of the user information DB. The user information DB 49a is information having a plurality of table-format user information in which confidential IDs, card IDs, usage limits, availability, wallet IDs, and available amounts are associated with each other. In the example shown in FIG. 4, the user information DB 49a includes a confidential ID "confidential ID #1", a card ID "card ID #1", a usage limit "＊＊＊＊＊", and whether or not it can be used. The wallet ID "Wallet ID #1" and the available amount "Available amount #1" are stored in association with each other.
Furthermore, in the example shown in FIG. 4, the user information DB 49a includes the confidential ID "confidential ID #2", the card ID "card ID #2", the usage limit "*****", and the usage permission ""Notavailable", wallet ID "Wallet ID #2", and available amount "Available amount #2" are stored in association with each other. Furthermore, in the example shown in FIG. 4, the user information DB 49a includes the confidential ID "confidential ID #3", the card ID "card ID #3", the usage limit "*****", and the usage permission ""Acceptable", wallet ID "Wallet ID #3", and available amount "Available amount #3" are stored in association with each other.
In other words, in the example of the user information DB 49a shown in FIG. It is shown that wallets corresponding to “#1” are commonly used. Returning to FIG. 1, the explanation will be continued.

The receiving unit 42, the processing unit 43, the determining unit 44, the payment unit 45, the determining unit 47, and the creating unit 48 are configured such that, for example, a hardware processor such as a CPU executes a program (software) stored in a storage unit 49. This is realized by Further, some or all of these functional units may be realized by hardware (including circuits) such as LSI, ASIC, FPGA, or GPU, or may be realized by collaboration between software and hardware. May be realized. The program may be stored in advance in a storage device (a storage device equipped with a non-transitory storage medium) such as an HDD or a flash memory, or a removable storage medium (a non-transitory storage device) such as a DVD or CD-ROM. The software may be installed by attaching the storage medium to a drive device.

The reception unit 42, the processing unit 43, the determination unit 44, the payment unit 45, the determination unit 47, and the creation unit 48 perform processing and management when the administrator M requests the prepaid payment service system to create a wallet. The process when the person M requests the prepaid payment service system to issue a payment tool, the process when the administrator M requests the deposit/withdrawal account of the prepaid payment method, and the process when the user U requests the prepaid payment service system to issue a payment tool. This will be explained separately from the processing when shopping at a store.
The following describes the process when administrator M requests the prepaid payment service system to create a wallet.
The communication unit 41 receives the wallet registration request message sent by the management device 30. The communication unit 41 outputs the received wallet registration request message to the reception unit 42.
The reception unit 42 receives the wallet registration request message output by the communication unit 41. The receiving unit 42 obtains the wallet ID included in the received wallet registration request message. The reception unit 42 outputs the acquired wallet ID to the processing unit 43.

The processing unit 43 acquires the wallet ID output by the reception unit 42. The processing unit 43 creates user information including the acquired wallet ID. The processing unit 43 includes the created user information in the user information DB 49a.
The creation unit 48 creates a wallet registration response message that includes the wallet ID and is addressed to the management device 30. The creation unit 48 outputs the created wallet registration response message to the communication unit 41.

The following describes the process when the administrator M requests the prepaid payment service system to issue a payment tool.
The communication unit 41 receives the payment tool registration request message sent by the management device 30. The communication unit 41 outputs the received payment tool registration request message to the reception unit 42 .
The reception unit 42 receives the payment tool registration request message output by the communication unit 41. The reception unit 42 acquires a wallet ID, a plurality of confidential IDs, information indicating a usage limit for each card, and information indicating availability for each card included in the received payment tool registration request message. The reception unit 42 outputs the acquired wallet ID, a plurality of confidential IDs, information indicating the usage limit for each card, and information indicating availability for each card to the processing unit 43.

The processing unit 43 acquires the wallet ID output by the reception unit 42, a plurality of confidential IDs, information indicating the usage limit for each card, and information indicating availability for each card. The processing unit 43 creates a plurality of card IDs to be associated with each of the plurality of acquired confidential IDs.
The processing unit 43 acquires user information including the acquired wallet ID from the user information DB 49a. The processing unit 43 stores each of the plurality of confidential IDs, the created card ID, information indicating the usage limit, and information indicating availability of usage in association with the acquired user information.
The creation unit 48 creates a payment tool registration response message that includes a plurality of pieces of information that associate the confidential ID and the wallet ID, and that is addressed to the management device 30 . The creation unit 48 outputs the created payment tool registration response message to the communication unit 41.

The process when the manager M requests a deposit to the deposit/withdrawal account of the prepaid payment method will be explained.
The communication unit 41 receives the prepaid payment method (electronic money) deposit completion message sent by the financial institution 15. The communication unit 41 outputs the received prepaid payment method (electronic money) deposit completion message to the reception unit 42 .
The reception unit 42 acquires the prepaid payment method (electronic money) deposit completion message output by the communication unit 41. The reception unit 42 acquires the wallet ID included in the acquired prepaid payment means (electronic money) deposit completion message and information indicating the deposit amount. The reception unit 42 outputs the acquired wallet ID and information indicating the deposited amount to the determination unit 47.

The determination unit 47 acquires the wallet ID output by the reception unit 42 and information indicating the deposited amount. The determining unit 47 determines whether the amount corresponding to the information indicating the deposit amount has been deposited into the wallet corresponding to the wallet ID, based on the acquired wallet ID and the information indicating the deposit amount. Here, regarding a wallet ID, even if the total amount of the usage limit set in association with each of multiple card IDs is higher than the total amount deposited in the wallet corresponding to the wallet ID. good.
The determining unit 47 outputs the wallet ID and a determination result as to whether the amount corresponding to the information indicating the deposited amount has been deposited to the determining unit 44 and the creating unit 48.
The determining unit 44 acquires the wallet ID output by the determining unit 47 and the determination result as to whether or not the amount corresponding to the information indicating the deposited amount has been deposited. When the acquired determination result indicates that the amount corresponding to the information indicating the deposited amount has been deposited, the determining unit 44 determines whether each of the plurality of card IDs is used for the acquired wallet ID in the user information DB 49a. Determine the possible amount.
Specifically, regarding the wallet ID, if the usage limit set in association with each of the plurality of card IDs is higher than the amount deposited in the wallet corresponding to the wallet ID, The amount deposited in the wallet is determined and stored as the available amount. Regarding the wallet ID, if the usage limit set in association with each of the plurality of card IDs is less than or equal to the amount deposited in the wallet corresponding to the wallet ID, the determining unit 44 determines that the usage limit is the available usage amount. Determine and memorize the limit.
The creation unit 48 obtains the determination result of whether the deposited amount outputted by the determination unit 47 has been deposited. The creation unit 48 creates a prepaid payment method (electronic money) deposit response message that includes the acquired determination result and addresses the terminal device 10 . The creation unit 48 outputs the created prepaid payment means (electronic money) deposit response message to the communication unit 41.

The process when user U shops at a store will be described.
The communication unit 41 receives the payment request message sent by the management device 30. The communication unit 41 outputs the received payment request message to the reception unit 42.
The reception unit 42 acquires the payment request message output by the communication unit 41. The receiving unit 42 obtains the confidential ID and information indicating the price P included in the obtained payment request message. The reception unit 42 outputs the acquired confidential ID and information indicating the price P to the determination unit 47.
The processing unit 43 updates the usage limit based on an arbitrary period specified for the usage limit in the user information DB 49a. When updating the usage limit, the processing unit 43 updates the usage limit to the wallet corresponding to the wallet ID based on the usage limit set in association with each of the plurality of card IDs and the wallet ID. If the amount is higher than the deposited amount, the available amount is updated by setting the amount deposited in the wallet. Based on the usage limit set in association with each of the plurality of card IDs and the wallet ID, the processing unit 43 determines if the usage limit is less than the amount deposited in the wallet corresponding to the wallet ID. is updated by setting a usage limit on the available amount.
The determining unit 47 acquires information indicating the confidential ID and price P output by the receiving unit 42. The determination unit 47 acquires, from the user information DB 49a, information indicating a usage limit, information indicating availability, and information indicating an available amount stored in association with the acquired confidential ID. The determination unit 47 determines whether the acquired information indicating availability is set to be available. The determining unit 47 determines that payment is not possible when the information indicating availability is set to unavailable. When determining that the payment cannot be made, the determination unit 47 outputs the card ID and the payment result (information indicating that the payment cannot be made) to the creation unit 48. Hereinafter, a case will be continued in which the determination unit 47 determines that the information indicating availability is set to be available.
The determination unit 47 determines whether the price P is less than or equal to the available amount of money, based on the acquired information indicating the price P and the information indicating the available amount of money. If the determining unit 47 determines that the price P is less than or equal to the available amount, it creates a payment request that includes the card ID and information indicating the price P. The determination unit 47 outputs the created payment request to the payment unit 45. If the determining unit 47 determines that the price P is higher than the available amount, it determines that payment cannot be made. When determining that the payment cannot be made, the determination unit 47 outputs the card ID and the payment result (information indicating that the payment cannot be made) to the creation unit 48.

The payment unit 45 acquires the payment request output by the determination unit 47. The payment unit 45 obtains information indicating the card ID and price P included in the obtained payment request. The payment unit 45 performs payment processing based on the acquired card ID and information indicating the price P. The payment unit 45 reduces the price P of the user information DB 49a from the amount deposited in the wallet corresponding to the wallet ID associated with the card ID. The determining unit 44 updates the available amount associated with the card ID by decreasing the price P.
Further, regarding the wallet ID, if the usage limit set in association with each of the plurality of card IDs is higher than the amount deposited in the wallet corresponding to the wallet ID, the determining unit 44 determines that the available usage amount is , determine and remember the amount deposited in the wallet. Regarding the wallet ID, if the usage limit set in association with each of the plurality of card IDs is less than or equal to the amount deposited in the wallet corresponding to the wallet ID, the determining unit 44 determines that the usage limit is the available usage amount. Determine and memorize the limit. Here, as for the usage limit associated with the card ID included in the payment request, the one reduced by the price P is used. Furthermore, for the available amount associated with the card ID of the card used, the amount reduced by the price P is used. The payment unit 45 outputs the card ID and the payment result to the creation unit 48.
The creation unit 48 acquires the card ID and payment result output by the determination unit 47 or the payment unit 45. The creation unit 48 acquires a confidential ID stored in association with the acquired card ID from the user information DB 49a. The creation unit 48 creates a payment response message that includes the acquired confidential ID and the payment result and is addressed to the management device 30 . The creation unit 48 outputs the created payment response message to the communication unit 41.

[Terminal device 10]
The terminal device 10 is, for example, a personal computer, a smartphone, a tablet terminal, or the like. On the terminal device 10, an application program or a browser for using the prepaid payment service system 1 is activated to support the prepaid payment service. An example of the terminal device 10 is a personal computer, and it is assumed that an application program (prepaid payment service utilization application) is running. The prepaid payment service usage application communicates with the management device 30 in response to the operations of the administrator M, and performs push notifications based on responses received from the management device 30 and the payment processing device 40.

[Operation of prepaid payment service system]
[Operation when administrator M requests the prepaid payment service system to create a wallet]
FIG. 5 is a sequence chart showing an example 1 of the operation of the prepaid payment service system according to the present embodiment. FIG. 5 shows an example of processing when the administrator M requests the prepaid payment service system to create a wallet.
(Step S1-1)
The terminal device 10 acquires the user ID input by the administrator M and information indicating that a request is made to create a wallet. The terminal device 10 creates a wallet creation request message addressed to the management device 30, including the acquired user ID and information indicating that a wallet creation is requested.
(Step S2-1)
The terminal device 10 transmits the created wallet creation request message to the management device 30.
(Step S3-1)
In the management device 30, the communication unit 31 receives the wallet creation request message sent by the terminal device 10. The communication unit 31 outputs the received wallet creation request message to the reception unit 32. The reception unit 32 accepts the wallet creation request message received by the communication unit 31. The reception unit 32 acquires the user ID included in the received wallet creation request message and information indicating that the wallet creation is requested. The reception unit 32 outputs the acquired user ID and information indicating that a wallet creation is requested to the setting unit 35.
The setting unit 35 acquires the user ID output by the reception unit 32 and information indicating that a wallet creation is requested. The setting unit 35 creates a wallet based on the acquired information indicating that a wallet creation is to be requested. The setting unit 35 associates the wallet ID of the created wallet with the user ID and stores them in the storage unit 39.
(Step S4-1)
In the management device 30, the creation unit 38 creates a wallet registration request message that includes the wallet ID and is addressed to the payment processing device 40.
(Step S5-1)
In the management device 30, the creation unit 38 outputs the created wallet registration request message to the communication unit 31. The communication unit 31 acquires the wallet registration request message output by the creation unit 38 and transmits the acquired wallet registration request message to the payment processing device 40.

(Step S6-1)
In the payment processing device 40, the communication unit 41 receives the wallet registration request message sent by the management device 30. The communication unit 41 outputs the received wallet registration request message to the reception unit 42. The reception unit 42 receives the wallet registration request message output by the communication unit 41. The receiving unit 42 obtains the wallet ID included in the received wallet registration request message. The reception unit 42 outputs the acquired wallet ID to the processing unit 43.
The processing unit 43 acquires the wallet ID output by the reception unit 42. The processing unit 43 creates user information including the acquired wallet ID. The processing unit 43 includes the created user information in the user information DB 49a.
(Step S7-1)
In the payment processing device 40, the creation unit 48 creates a wallet registration response message that includes the wallet ID and is addressed to the management device 30.
(Step S8-1)
In the payment processing device 40, the creation unit 48 outputs the created wallet registration response message to the communication unit 41. The communication unit 41 acquires the wallet registration response message output by the creation unit 48 and transmits the acquired wallet registration response message to the management device 30.
(Step S9-1)
In the management device 30, the communication unit 31 receives the wallet registration response message sent by the payment processing device 40. The communication unit 31 outputs the received wallet registration response message to the reception unit 32.
The reception unit 32 receives the wallet registration response message output by the communication unit 31. The receiving unit 32 obtains the wallet ID included in the received wallet registration response message. The reception unit 32 outputs the acquired wallet ID to the creation unit 38.
The creation unit 38 acquires the wallet ID output by the reception unit 32. Based on the acquired wallet ID, the creation unit 38 acquires a user ID stored in association with the wallet ID. The creation unit 38 creates a wallet creation response message that includes the user ID and the wallet and is addressed to the terminal device 10 .
(Step S10-1)
In the management device 30, the creation unit 38 outputs the created wallet creation response message to the communication unit 31. The communication unit 31 acquires the wallet creation response message output by the creation unit 38 and transmits the acquired wallet creation response message to the terminal device 10.
(Step S11-1)
The terminal device 10 receives the wallet creation response message sent by the management device 30.
(Step S12-1)
The terminal device 10 acquires the user ID and wallet ID included in the received wallet creation response message. The terminal device 10 displays the user ID and wallet ID.
According to an example of processing when the administrator M requests the prepaid payment service system to create a wallet, the management device 30 can create the wallet based on the wallet creation request. Further, the payment processing device 40 can create user information including the wallet ID of the wallet created by the management device 30, and can include the created user information in the user information DB 49a.
Further, the payment processing device 40 can notify the management device 30 of the wallet ID, and the management device 30 can notify the terminal device 10 of the wallet ID. This allows the administrator M to be informed of the wallet ID of the created wallet.

[Operation when administrator M requests the prepaid payment service system to issue a payment tool]
FIG. 6 is a sequence chart showing a second example of the operation of the prepaid payment service system according to the present embodiment. FIG. 6 shows an example of a process when the administrator M requests issuance of a payment tool.
(Step S1-2)
The terminal device 10 acquires the wallet ID input by the administrator M, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used. The terminal device 10 includes the acquired wallet ID, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used, and has the management device 30 as the destination. Create a payment tool issue request message.
(Step S2-2)
The terminal device 10 transmits the created payment tool issue request message to the management device 30.
(Step S3-2)
In the management device 30, the communication unit 31 receives the payment tool issue request message sent by the terminal device 10. The communication unit 31 outputs the received payment tool issue request message to the reception unit 32 . The reception unit 32 accepts the payment tool issue request message received by the communication unit 31. The reception unit 32 acquires the wallet ID included in the received payment tool issue request message, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used. do. The reception unit 32 outputs the acquired wallet ID, information indicating the number of cards issued, information indicating the usage limit for each card, and information indicating whether each card can be used, to the setting unit 35.
The setting unit 35 acquires the wallet ID output by the receiving unit 32, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating whether each card can be used. The setting unit 35 sets a plurality of payment tools based on the acquired information indicating the number of issued cards. The setting unit 35 associates each of the plurality of payment tools with a card number stored in the card DB 39a.
(Step S4-2)
In the management device 30, the creation unit 38 generates a wallet ID, a confidential ID stored in association with each of a plurality of card numbers, information indicating a usage limit for each card, and information indicating availability for each card. A payment tool registration request message is created that includes the above information and is addressed to the payment processing device 40.
(Step S5-2)
In the management device 30 , the creation unit 38 outputs the created payment tool registration request message to the communication unit 31 . The communication unit 31 acquires the payment tool registration request message output by the creation unit 38 and transmits the acquired payment tool registration request message to the payment processing device 40 .

(Step S6-2)
In the payment processing device 40, the communication unit 41 receives the payment tool registration request message sent by the management device 30. The communication unit 41 outputs the received payment tool registration request message to the reception unit 42 . The reception unit 42 receives the payment tool registration request message output by the communication unit 41. The reception unit 42 acquires a wallet ID, a plurality of confidential IDs, information indicating a usage limit for each card, and information indicating availability for each card included in the received payment tool registration request message. The reception unit 42 outputs the acquired wallet ID, a plurality of confidential IDs, information indicating the usage limit for each card, and information indicating availability for each card to the processing unit 43.
The processing unit 43 acquires the wallet ID output by the reception unit 42, a plurality of confidential IDs, information indicating the usage limit for each card, and information indicating availability for each card. The processing unit 43 creates a plurality of card IDs to be associated with each of the plurality of acquired confidential IDs.
(Step S7-2)
In the payment processing device 40, the processing unit 43 links each of the plurality of card IDs to the wallet account (wallet ID) of the wallet.
(Step S8-2)
In the payment processing device 40, the processing unit 43 acquires user information including the wallet ID from the user information DB 49a. The processing unit 43 stores each of the plurality of confidential IDs, the created card ID, information indicating the usage limit, and information indicating availability of usage in association with the acquired user information.
(Step S9-2)
In the payment processing device 40, the creation unit 48 creates a payment tool registration response message that includes a plurality of pieces of information that associates a confidential ID and a wallet ID, and is addressed to the management device 30.

(Step S10-2)
In the payment processing device 40 , the creation unit 48 outputs the created payment tool registration response message to the communication unit 41 . The communication unit 41 acquires the payment tool registration response message output by the creation unit 48 and transmits the acquired payment tool registration response message to the management device 30.
(Step S11-2)
In the management device 30, the communication unit 31 receives the payment tool registration response message sent by the payment processing device 40. The communication unit 31 outputs the received payment tool registration response message to the reception unit 32.
The reception unit 32 receives the payment tool registration response message output by the communication unit 31. The receiving unit 32 obtains a plurality of pieces of information that associate the confidential ID and wallet ID included in the received payment tool registration response message. The reception unit 32 outputs a plurality of pieces of information in which the acquired confidential ID and wallet ID are associated with each other to the creation unit 38.
The creation unit 38 acquires a plurality of pieces of information that associate the confidential ID and wallet ID output by the reception unit 32. The creation unit 38 acquires a plurality of card numbers stored in association with each of the plurality of confidential IDs from the card DB 39a, based on a plurality of pieces of information in which the obtained confidential IDs and wallet IDs are associated with each other. The creation unit 38 creates a payment tool issue response message that includes a plurality of pieces of information that associate the card number and wallet ID, and that is addressed to the terminal device 10 .
(Step S12-2)
In the management device 30 , the creation unit 38 outputs the created payment tool issue response message to the communication unit 31 . The communication unit 31 acquires the payment tool issue response message output by the creation unit 38 and transmits the acquired payment tool issue response message to the terminal device 10 .
(Step S13-2)
The terminal device 10 receives the payment tool issue response message sent by the management device 30.
(Step S14-2)
The terminal device 10 acquires a plurality of pieces of information that associate the card number and wallet ID included in the received payment tool issue response message. The terminal device 10 displays a plurality of pieces of information in which card numbers and wallet IDs are associated with each other.
According to an example of the process when the administrator M requests the prepaid payment service system to issue a payment tool, the management device 30 can issue a plurality of payment tools based on the payment tool issuance request, and the management device 30 can issue a payment tool. The processing device 40 can link multiple payment tools and wallets.
Further, the payment processing device 40 can notify the management device 30 of a plurality of pieces of information associating a confidential ID and a wallet ID, and the management device 30 can notify the terminal device 10 of a plurality of pieces of information associating a card number with a wallet ID. information can be notified. This allows the administrator M to be informed of the card number of the issued card and the wallet ID used with that card.

[Operation when administrator M requests a deposit to the deposit/withdrawal account of a prepaid payment method]
FIG. 7 is a sequence chart showing a third example of the operation of the prepaid payment service system according to the present embodiment. FIG. 7 shows an example of processing when the administrator M requests a deposit/withdrawal account of a prepaid payment method.
(Step S21)
Based on the user's operation, the terminal device 10 creates a prepaid payment means (electronic money) deposit request message that includes information indicating the wallet ID and information indicating the deposit amount and is addressed to the financial institution 15.
(Step S22)
The terminal device 10 transmits the created prepaid payment method (electronic money) deposit request message to the financial institution 15.
(Step S23)
The financial institution 15 receives the prepaid payment method (electronic money) deposit request message sent by the terminal device 10 . The financial institution 15 deposits the amount corresponding to the deposit amount into the wallet corresponding to the wallet ID, based on the wallet ID included in the prepaid payment method (electronic money) deposit request message and the information indicating the deposit amount. Perform processing.
(Step S24)
The financial institution 15 creates a prepaid payment method (electronic money) deposit completion message that includes the wallet ID and information indicating the deposit amount and addresses the payment processing device 40 .
(Step S25)
The financial institution 15 transmits the created prepaid payment method (electronic money) deposit completion message to the payment processing device 40 .

(Step S26)
In the payment processing device 40, the communication unit 41 receives the prepaid payment means (electronic money) deposit completion message sent by the financial institution 15. The communication unit 41 outputs the received prepaid payment method (electronic money) deposit completion message to the reception unit 42 . The reception unit 42 acquires the prepaid payment method (electronic money) deposit completion message output by the communication unit 41. The reception unit 42 acquires the wallet ID included in the acquired prepaid payment means (electronic money) deposit completion message and information indicating the deposit amount.
The determination unit 47 determines whether or not the amount corresponding to the information indicating the deposit amount has been deposited into the wallet corresponding to the wallet ID, based on the wallet ID acquired by the reception unit 42 and the information indicating the deposit amount. judge. The determining unit 47 outputs the determination result of whether or not the amount corresponding to the information indicating the deposited amount has been deposited to the determining unit 44 .
(Step S27)
In the payment processing device 40, the determining unit 44 obtains a determination result as to whether or not the amount corresponding to the information indicating the deposited amount outputted by the determining unit 47 has been deposited. When the acquired determination result indicates that the amount corresponding to the information indicating the deposited amount has been deposited, the determining unit 44 determines whether each of the plurality of card IDs is used for the acquired wallet ID in the user information DB 49a. Determine the possible amount.
(Step S28)
In the payment processing device 40, the creation unit 48 obtains the determination result as to whether or not the amount corresponding to the information indicating the deposit amount output by the determination unit 47 has been deposited. The creation unit 48 creates a prepaid payment method (electronic money) deposit response message that includes the acquired determination result and addresses the terminal device 10 .
(Step S29)
In the payment processing device 40 , the creation unit 48 outputs the created prepaid payment means (electronic money) deposit response message to the communication unit 41 . The communication unit 41 acquires the prepaid payment means (electronic money) deposit response message output by the creation unit 48 . The communication unit 41 transmits the acquired prepaid payment means (electronic money) deposit response message to the terminal device 10 .
(Step S30)
The terminal device 10 receives the prepaid payment method (electronic money) deposit response message sent by the payment processing device 40.
(Step S31)
The terminal device 10 obtains a determination result as to whether the deposit amount included in the received prepaid payment means (electronic money) deposit response message has been deposited. The terminal device 10 displays the determination result as to whether or not the acquired deposit amount has been deposited.
According to an example of the process when the administrator M requests a deposit to the deposit/withdrawal account of a prepaid payment method, a prepaid payment method (electronic money) deposit request message is sent from the terminal device 10 to the financial institution 15. By doing so, it is possible to request the financial institution 15 to deposit money into the wallet corresponding to the wallet ID. In addition, by sending a prepaid payment method (electronic money) deposit request message from the terminal device 10 to the financial institution 15, each card can be used in the payment processing device 40 based on the amount deposited in the wallet. You can decide the amount.

[Operations when user U shops at a store]
FIG. 8 is a sequence chart showing a fourth example of the operation of the prepaid payment service system according to the present embodiment. FIG. 8 shows an example of a process when the user U uses the card 5 to shop at a store. Here, a case will be described in which the card 5 is set to be usable.
(Step S41)
The store terminal 20 uses an imaging device to image the information code attached to the product. The store terminal 20 acquires information indicating the price of the product based on the image captured by the imaging device. The store terminal 20 also acquires the card number represented on the card 5 presented by the user U.
(Step S42)
The store terminal 20 creates a debit request message addressed to the management device 30, including the acquired card number and information indicating the price P of the product.
(Step S43)
The store terminal 20 transmits the created withdrawal request message to the management device 30.
(Step S44)
In the management device 30, the communication unit 31 receives the debit request message sent from the store terminal 20. The communication unit 31 outputs the received debit request message to the reception unit 32.
The reception unit 32 receives the debit request message output by the communication unit 31. The receiving unit 32 obtains the card number and information indicating the price P included in the received debit request message. The reception unit 32 outputs the acquired card number and information indicating the price P to the determination unit 37.
The determining unit 37 acquires the card number output by the accepting unit 32 and information indicating the price P. The determination unit 37 acquires the expiration date stored in association with the acquired card number from the card DB 39a.
(Step S44)
In the management device 30, the determination unit 37 determines whether the card 5 is within its expiration date based on the acquired expiration date.
(Step S45)
In the management device 30, when determining that the card 5 is not within the expiration date, the determination unit 37 determines whether the card 5 is within the expiration date (here, it is determined that the card 5 is not within the expiration date). information indicating the card number) and information indicating the card number are output to the creation unit 38.
The creation unit 38 acquires the determination result of whether the card 5 outputted by the determination unit 37 is within the expiration date and information indicating the card number. The creation unit 38 creates a debit response message addressed to the terminal device 10, including a determination result as to whether the acquired card 5 is within its expiration date and information indicating the card number.

(Step S46)
In the management device 30 , the creation unit 38 outputs the created withdrawal response message to the communication unit 31 . The communication unit 31 transmits the withdrawal response message output by the creation unit 38 to the store terminal 20.
(Step S47)
The store terminal 20 receives the withdrawal response message sent by the management device 30.
(Step S48)
The store terminal 20 acquires the determination result of whether the card 5 included in the received withdrawal response message is within its expiration date and information indicating the card number. The store terminal 20 displays the determination result as to whether the acquired card 5 is within its expiration date and information indicating the card number. This allows the user U to be informed that the card 5 is not within its expiration date.
(Step S49)
In the management device 30 , when determining that the card 5 is within the expiration date, the determination unit 37 outputs the card number to the conversion unit 36 .
The conversion unit 36 acquires the card number output by the determination unit 37. The conversion unit 36 acquires a confidential ID stored in association with the acquired card number, and converts the card number into the acquired confidential ID. The conversion unit 36 outputs the confidential ID obtained by the conversion to the determination unit 37.
(Step S50)
In the management device 30, the determination unit 37 acquires the confidential ID output by the conversion unit 36. The determining unit 37 outputs the confidential ID and information indicating the price P to the creating unit 38.
The creation unit 38 acquires the confidential ID output by the determination unit 37 and information indicating the price P. The creation unit 38 creates a payment request message that includes the confidential ID and information indicating the price P and is addressed to the payment processing device 40 .

(Step S51)
In the management device 30 , the creation unit 38 outputs the created payment request message to the communication unit 31 . The communication unit 31 acquires the payment request message output by the creation unit 38. The communication unit 31 transmits the acquired payment request message to the payment processing device 40.
(Step S52)
In the payment processing device 40, the communication unit 41 receives the payment request message sent by the management device 30. The communication unit 41 outputs the received payment request message to the reception unit 42. The reception unit 42 acquires the payment request message output by the communication unit 41. The reception unit 42 acquires the confidential ID and information indicating the price P included in the acquired payment request message. The reception unit 42 outputs the acquired confidential ID and information indicating the price P to the determination unit 47.
(Step S53)
In the payment processing device 40, the determining unit 47 determines whether the price P is less than or equal to the available amount.

(Step S54)
In the payment processing device 40, when determining that the price P is not less than the available amount (price P is higher than the available amount), the determination unit 47 determines whether the price P is less than or equal to the available amount. The determination result (information indicating that the price P is not less than the available amount) and the confidential ID are output to the creation unit 48.
In the payment processing device 40, the creation unit 48 obtains the determination result as to whether the price P output by the determination unit 47 is less than or equal to the available amount, and the confidential ID. The creation unit 48 creates a payment response message addressed to the management device 30, including the determination result of whether the acquired price P is less than or equal to the available amount and the confidential ID.
(Step S55)
In the payment processing device 40, the creation unit 48 outputs the created payment response message to the communication unit 41. The communication unit 41 transmits the payment response message output by the creation unit 48 to the management device 30.
(Step S56)
In the management device 30, the communication unit 31 receives the payment response message sent by the payment processing device 40. The communication unit 31 outputs the received payment response message to the creation unit 38.
The creation unit 38 acquires the determination result of whether the price P included in the payment response message output by the communication unit 31 is less than or equal to the available amount, and the confidential ID. The creation unit 38 acquires a card number stored in association with the acquired confidential ID from the card DB 39a. The creation unit 38 creates a debit response message addressed to the store terminal 20, including the acquired card number and the determination result of whether the price P is less than or equal to the available amount.
(Step S57)
In the management device 30 , the creation unit 38 outputs the created withdrawal response message to the communication unit 31 . The communication unit 31 acquires the debit response message output by the creation unit 38. The communication unit 31 transmits the acquired debit response message to the store terminal 20.
(Step S58)
The store terminal 20 receives the withdrawal response message sent by the management device 30.

(Step S59)
The store terminal 20 acquires the card number included in the received debit response message and the determination result as to whether the price P is less than or equal to the available amount. The store terminal 20 displays the acquired card number and the determination result as to whether the price P is less than or equal to the available amount. This allows the user U to be informed that the price P is higher than the available amount.
(Step S60)
In the payment processing device 40, the determination unit 47 creates a payment request including a confidential ID and information indicating the price P when determining that the price P is less than or equal to the available amount. The determination unit 47 outputs the created payment request to the payment unit 45.
The payment unit 45 acquires the payment request output by the determination unit 47. The payment unit 45 obtains the confidential ID and information indicating the price P included in the obtained payment request. The payment unit 45 acquires the card ID and wallet ID associated with the confidential ID from the user information DB 49a. The payment unit 45 reduces the amount corresponding to the price P from the amount deposited in the wallet corresponding to the acquired wallet ID. The payment unit 45 executes a process of depositing the amount corresponding to the price P, which is reduced from the amount deposited in the wallet corresponding to the wallet ID, into the store's wallet. The payment unit 45 updates the user information DB 49a by reducing the amount corresponding to the price P from the available amount associated with the card ID.
Regarding the wallet ID, if the usage limit set in association with each of the plurality of card IDs is higher than the amount deposited in the wallet corresponding to the wallet ID, the determining unit 44 determines that the usage limit is set as the available usage amount. Determine and remember the amount deposited in your wallet. Regarding the wallet ID, if the usage limit set in association with each of the plurality of card IDs is less than or equal to the amount deposited in the wallet corresponding to the wallet ID, the determining unit 44 determines that the usage limit is the available usage amount. Determine and memorize the limit. Here, as for the usage limit associated with the card ID included in the payment request, the one reduced by the price P is used. Furthermore, for the available amount associated with the card ID of the card used, the amount reduced by the price P is used.
(Step S61)
In the payment processing device 40, the payment unit 45 outputs the card ID and the payment result to the creation unit 48.
The creation unit 48 acquires the card ID and payment result output by the payment unit 45. The creation unit 48 acquires a confidential ID stored in association with the acquired card ID from the user information DB 49a. The creation unit 48 creates a payment response message that includes the acquired confidential ID and the payment result and is addressed to the management device 30 .
(Step S62)
In the payment processing device 40, the creation unit 48 outputs the created payment response message to the communication unit 41. The communication unit 41 acquires the payment response message output by the creation unit 48. The communication unit 31 transmits the acquired payment response message to the management device 30.

(Step S63)
In the management device 30, the communication unit 31 receives the payment response message sent by the payment processing device 40. The communication unit 31 outputs the received payment response message to the creation unit 38.
The creation unit 38 acquires the confidential ID included in the payment response message output by the communication unit 31 and the payment result. The creation unit 38 acquires a card number stored in association with the acquired confidential ID from the card DB 39a. The creation unit 38 creates a debit response message containing the acquired card number and the payment result and addressed to the store terminal 20.
(Step S64)
In the management device 30 , the creation unit 38 outputs the created withdrawal response message to the communication unit 31 . The communication unit 31 acquires the debit response message output by the creation unit 38. The communication unit 31 transmits the acquired debit response message to the store terminal 20.
(Step S65)
The store terminal 20 receives the withdrawal response message sent by the management device 30.
(Step S66)
The store terminal 20 acquires the card number included in the received debit response message and the payment result. The store terminal 20 displays the acquired card number and payment result. This allows the user U to be informed that the payment has been completed.
According to the operation when the user U shops at a store, when the user U shops at the store using the card 5, the payment processing device 40 uses the information indicating the availability of the card. A process for determining whether the setting is possible and a process for determining whether the price P is less than or equal to the available amount are executed. The payment processing device 40 can perform payment based on the determination result.

In the embodiments described above, a prepaid card, a credit card, and a virtual card are used as examples of the payment tool, but the payment tool is not limited to this example. For example, it may be a display device that displays a card number.
In the embodiment described above, the case where the user U went shopping at a store was explained as an example, but the present invention is not limited to this example. For example, the present invention can also be applied to a case where user U purchases something on an EC (electronic commerce) site.
In the embodiment described above, the management device 30 and the payment processing device 40 were described as separate devices, but the present invention is not limited to this example. For example, the management device 30 and the payment processing device 40 may be realized as one device, or may be realized as three or more devices.
In the embodiment described above, a case has been described in which a card number is converted into a confidential ID in the management device 30, and a confidential ID is converted into a card ID in the payment processing device 40, but the present invention is not limited to this example. For example, processing may be performed using the card number without converting the card number into a confidential ID in the management device 30. Further, processing may be performed using the confidential ID without converting the confidential ID into a card ID in the payment processing device 40.
In the embodiment described above, an arbitrary period such as daily, weekly, monthly, quarterly, semi-annual, annual, semi-annual, etc. was explained as an example of the predetermined period regarding the usage limit for each card. The example is not limited to this example. For example, it may be a one-time payment amount or a total amount.

In the embodiment described above, the processing unit 43 sets the usage limit for each of the plurality of payment tools, and the determining unit 44 sets the total amount of prepayments paid to the deposit/withdrawal account of the prepaid payment method. Although a case has been described in which the usable amount of each of the plurality of payment tools is determined based on the usage limit of each of the plurality of payment tools set by the processing unit 43, the present invention is not limited to this example. For example, the determining unit 44 may determine the usable amount of each of the plurality of payment tools based on the total amount of prepayments paid into the deposit/withdrawal account of the prepaid payment means. For example, the determining unit 44 may determine the available amount of each of the plurality of payment tools to be the same as the total amount of prepayments paid into the deposit/withdrawal account of the prepaid payment method, or The amount may be set lower than the total amount of advance payments paid into the deposit/withdrawal account of the payment means. For example, the determining unit 44 sets the available amount of each of the plurality of payment tools to an amount obtained by subtracting a predetermined percentage from the total amount of prepayments paid into the deposit/withdrawal account of the prepaid payment method. Alternatively, the amount may be set to an amount obtained by subtracting a predetermined amount.
In this case, when the total amount of the advance payment is debited by using one of the plurality of payment tools, the determining unit 44 determines whether the total amount of the advance payment is debited based on the total amount after the debit By configuring in this way, the total amount of prepayments paid into the deposit/withdrawal account of the prepaid payment method and the multiple payments set by the processing unit 43 are updated. Since the process of determining the usable amount of each of the plurality of payment tools based on the usage limit of each of the tools can be omitted, the process can be simplified.
In the embodiment described above, the determination unit 47 of the payment processing device 40 acquires the confidential ID and the information indicating the price P included in the payment request message. The determining unit 47 determines whether the information indicating availability, which is stored in association with the acquired confidential ID, is set to be available. Thereafter, when the information indicating availability is set to be available, the determination unit 47 determines whether the price P is less than or equal to the available amount based on the information indicating the price P and the information indicating the available amount. Although the case where the determination is made has been described, the present invention is not limited to this example.
For example, the determining unit 47 performs a process of determining whether or not information indicating availability is set to be available, and determines whether the price P is the available amount based on the information indicating the price P and the information indicating the available amount. The process of determining whether or not the following is true may be executed in any order, or may be executed simultaneously.
In the embodiment described above, either or both of the card DB 39a and the user information DB 49a may be a relational database. In this case, one or both of the card DB 39a and the user information DB 49a are represented by a plurality of tables. For example, the card DB 39a can be represented by a table that associates card numbers and confidential IDs, and a table that associates card numbers and confidential IDs. For example, the user information DB 49a includes a table that associates confidential IDs with card IDs, a table that associates card IDs with usage limits and availability, and a table that associates card IDs with wallet IDs. It can be represented by a table and a table that associates wallet IDs and available amounts.

According to the prepaid payment service system 1 according to the present embodiment, the payment processing device 40 includes a processing unit 43 that sets usage limits for each of a plurality of payment tools, and a total amount of prepaid money paid into the wallet. The determining unit 44 determines the usable amount of each of the plurality of payment tools based on the amount and the usage limit of each of the plurality of payment tools set by the processing unit 43. The determining unit 44 updates the available amount of the used payment tool when the total amount of advance payment is debited by using any of the plurality of payment tools.
Since the available amount of each of the multiple payment tools is determined based on the total amount of the prepayment paid to the wallet and the usage limit of each of the multiple payment tools, usage higher than the prepayment amount You can set the possible amount. Therefore, it is possible to improve the convenience of the prepaid payment means.
Further, if the available amount of each of the plurality of payment tools set by the processing section 43 is higher than the total amount of the advance payment, the determining section 44 determines the amount of money available for each of the plurality of payment tools. If the available amount of each of the plurality of payment tools is less than or equal to the total amount of advance payment, the amount of money available for each of the plurality of payment tools is determined. With this configuration, the usable amount of each of the plurality of payment tools can be set so that it is less than or equal to the total amount of advance payment.
Further, when restricting the use of one payment tool among the plurality of payment tools, the processing unit 43 sets the usage limit of the one payment tool to zero. With this configuration, the use of one payment tool can be restricted without reducing the advance payment.
Further, the processing unit 43 can set the usage limit for each of the plurality of payment tools to an amount higher than the total amount of the advance payment. With this configuration, the usage limit for each of multiple payment tools can be set to a higher amount than the total amount of prepayments paid to the wallet, improving the convenience of prepaid payment methods. can be achieved.

Although the embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like may be made without departing from the gist of the present invention.
For example, a computer program for realizing the functions of each device described above may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed. Note that the "computer system" here may include hardware such as an OS and peripheral devices.
Furthermore, "computer-readable recording media" refers to flexible disks, magneto-optical disks, ROMs, writable non-volatile memories such as flash memory, portable media such as DVDs (Digital Versatile Discs), and media built into computer systems. A storage device such as a hard disk.
Furthermore, "computer-readable recording medium" refers to volatile memory (for example, DRAM (Dynamic It also includes those that retain programs for a certain period of time, such as Random Access Memory).
Further, the program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in a transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.
Moreover, the above program may be for realizing a part of the above-mentioned functions. Furthermore, it may be a so-called difference file (difference program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

DESCRIPTION OF SYMBOLS 1... Prepaid payment service system, 5... Card, 10... Terminal device, 15... Financial institution, 20... Store terminal, 30... Management device, 31... Communication department, 32... Reception department, 35... Setting section, 36... Conversion Section, 37... Judgment section, 38... Creation section, 39... Storage section, 39a... Card DB, 40... Payment processing device, 41... Communication section, 42... Reception section, 43... Processing section, 44... Determining section, 45... Payment section, 47... Judgment section, 48... Creation section, 49... Storage section, 49a... User information DB

Claims (8)

a determining unit that determines the available amount of each of the plurality of payment tools based on the total amount of prepayments paid into the deposit/withdrawal account of the prepaid payment means;
and a processing unit that sets a usage limit for each of the plurality of payment tools,
The processing unit sets the input limit amount as the usage limit amount when the input limit amount is higher than the total amount of the advance payment,
The determining unit updates the available amount of each of the plurality of payment tools based on the changed total amount when the total amount of the advance payment is changed. . When the total amount of the prepaid amount is changed due to the prepaid amount being paid into the deposit/withdrawal account of the prepaid payment method, the determining unit determines the amount of the prepaid amount based on the total amount after the change. , updating the available amount of each of the plurality of payment tools. The determining unit is based on the total amount of prepaid money paid into the deposit/withdrawal account of the prepaid payment means and the usage limit of each of the plurality of payment tools set by the processing unit. 3. The prepaid payment service system according to claim 1 or 2, wherein the available amount of each of the plurality of payment tools is determined. The determining unit updates the available amount of the used payment tool when the total amount of the advance payment is debited by using one of the plurality of payment tools. The prepaid payment service system according to claim 3. The determining unit determines the available amount of each of the plurality of payment tools as an advance payment if the usage limit of each of the plurality of payment tools set by the processing unit is higher than the total amount of the advance payment. and if the usage limit of each of the plurality of payment tools is less than or equal to the total amount of advance payment, the usage limit of each of the plurality of payment tools is determined. The prepaid payment service system according to claim 3 or 4. Any one of claims 3 to 5, wherein the processing unit sets a usage limit of one of the payment tools to zero when restricting the usage of one of the payment tools. The prepaid payment service system described in item (1) above. A prepaid payment processing method performed by a prepaid payment service system comprising a processor, the method comprising:
determining the amount available for each of the plurality of payment instruments based on the total amount of prepayments paid to the deposit/withdrawal account of the prepaid payment instrument;
setting a usage limit for each of the plurality of payment tools;
If the total amount of the advance payment is changed, updating the available amount of each of the plurality of payment tools based on the changed total amount,
If the input limit amount is higher than the total amount of the advance payment, the input limit amount is set as the usage limit amount. to the computer,
determining the amount available for each of the plurality of payment instruments based on the total amount of prepayments paid to the deposit/withdrawal account of the prepaid payment instrument;
setting a usage limit for each of the plurality of payment tools;
when the total amount of the advance payment is changed, updating the available amount of each of the plurality of payment tools based on the changed total amount;
A program for setting the input limit amount as the usage limit amount when the input limit amount is higher than the total amount of the advance payment.

Images