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

Abstract

To provide a prepaid payment service system, a prepaid payment processing method, and a program capable of improving the convenience of prepaid payment means.SOLUTION: A prepaid payment service system comprises: a processing unit for setting a guarantee amount to guarantee payment for one or more bills that occur regularly by applying via each of a plurality of payment tools; and a determination unit for determining the available amount for each of the plurality of payment tools based on the amount obtained by subtracting the guarantee amount from the prepaid total amount paid to a deposit and withdrawal account for prepaid payment means.SELECTED DRAWING: Figure 1

Description

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

Prepaid payment methods such as prepaid cards are widely used. Some prepaid payment methods can be used at credit card merchants in the same way as credit cards.
Regarding prepaid payment methods that use the credit card mechanism, a technology is known in which a card company collects funds equivalent to the reimbursed shortfall from a user when a sales request for an amount exceeding the balance of a prepaid card is received. (See, for example, Patent Document 1).
This technology responds to the issuance application with data to identify the initial available amount set within the range of the prepaid amount paid in association with the issuance application for the prepaid payment instrument available at the merchant. A setting unit that stores the ID information of the prepaid payment instrument in the storage unit, a determination unit that determines the guarantee amount within the remaining amount of the available amount corresponding to the prepaid payment instrument, and a determined guarantee amount. Changes the data stored in the storage so that is not included in the balance of the available amount, and at least a part of the billing amount included in the sales information in the settlement process related to any prepaid payment method is in advance If a loss due to non-approval occurs, change the pool amount so that the pool amount indicating the accumulated amount of the deposit that will be the source of compensation for the loss includes the determined guarantee amount. It has a change part.

International Publication No. 2014/178121

When regular payments are made with a credit card, so-called authorization (credit approval) is performed to confirm whether or not payment can be made with the credit card. Authorization confirms the validity of your credit card. After authorization, sales are processed and settlement is completed.
Suppose you use a prepaid payment instrument to pay for recurring bills. Prepaid payment methods are different from credit transactions (deferred payments) performed by ordinary credit cards, so even if authorization is processed without problems, it is unclear whether or not there is a balance of prepaid payment methods on the due date. is there. For this reason, prepaid payment instruments cannot be used to pay for transactions that are due after authorization or for bills that occur on a regular basis.

The present invention has been made in consideration of such circumstances, and an object of the present invention is a prepaid payment service system, a prepaid payment processing method, and a program capable of improving the convenience of a prepaid payment means. Is to provide.

(1) One aspect of the present invention is a processing unit that sets a guarantee amount for guaranteeing payment for one or more claims that are periodically generated by applying for each of a plurality of payment tools, and advance payment. It includes a determination unit that determines the available amount of each of a plurality of payment tools based on the total amount of advance payments paid to the deposit / withdrawal account of the formal payment method minus the guarantee amount. It is a prepaid payment service system.
(2) One aspect of the present invention is the prepaid payment service system described in (1) above, which includes a reception unit that receives a periodic billing message that occurs periodically and a payment unit that performs payment processing. The unit associates each of one or more slip identification information with the slip identification information corresponding to the billing identification information included in the periodic billing message received by the reception unit from the storage unit that stores the guarantee amount information in association with each other. The payment unit setstles the billing amount included in the periodic billing message based on the guarantee amount corresponding to the guarantee amount information acquired by the processing unit. It is a type payment service system.
(3) In one aspect of the present invention, in the prepaid payment service system described in (2) above, the processing unit increases the available amount based on the guaranteed amount information, and the payment unit causes the payment unit to increase the available amount. It is a prepaid payment service system that settles the billing amount included in the periodic billing message based on the available amount increased by the processing unit.
(4) In one aspect of the present invention, in the prepaid payment service system described in (2) or (3) above, the determination unit determines the guarantee amount based on the billed amount, and the processing unit determines the guarantee amount. Updates the available amount of the payment tool used and the guaranteed amount information associated with the slip identification information stored in the storage unit based on the billing amount determined by the determination unit. It is a prepaid payment service system.
(5) One aspect of the present invention is the prepaid payment service system according to (4) above, wherein the processing unit determines the guaranteed amount determined by the determination unit from the available amount of the payment tool used. Is a prepaid payment service system that updates by subtracting and updates the guarantee amount information associated with the slip identification information stored in the storage unit with the guarantee amount determined by the determination unit. ..
(6) In one aspect of the present invention, in the prepaid payment service system according to (4), the processing unit uses the guaranteed amount associated with the slip identification information stored in the storage unit. It is a prepaid payment service system that restricts the use of each of the plurality of payment tools when the amount is higher than the available amount of the payment tool.
(7) One aspect of the present invention is a prepaid payment processing method executed by a prepaid payment service system including a processor, which is periodically generated by being applied for by each of a plurality of payment tools. Or, based on the step of setting the guarantee amount to guarantee payment for multiple claims and the total amount of the advance payment paid to the deposit / withdrawal account of the prepaid payment method minus the guarantee amount. , A prepaid payment processing method having a step of determining the available amount of each of a plurality of payment tools.
(8) One aspect of the present invention is a step of setting a guarantee amount for guaranteeing payment for one or more claims generated periodically by applying for each of a plurality of payment tools to a computer. , Perform steps to determine the available amount of each of multiple payment tools based on the total amount of advance payments paid to the deposit / withdrawal account of the prepaid payment instrument minus the guarantee amount. It is a program to let you.

According to the present invention, it is possible to improve the convenience of the prepaid payment means.

It is a block diagram which shows the configuration example of the prepaid payment service system which concerns on one Embodiment. It is a figure which shows the outline of the prepaid payment service system which concerns on this embodiment. It is a figure which shows an example of a card DB. It is a figure which shows an example of a user information DB. It is a figure which shows an example of the deposit DB. It is a figure which shows an example of the notification destination DB. It is a sequence chart which shows the example 1 of the operation of the prepaid payment service system which concerns on this embodiment. It is a sequence chart which shows the example 2 of the operation of the prepaid payment service system which concerns on this embodiment. It is a sequence chart which shows the example 3 of the operation of the prepaid payment service system which concerns on this embodiment. It is a sequence chart which shows the example 4 of the operation of the prepaid payment service system which concerns on this embodiment. It is a sequence chart which shows the example 5 of the operation of the prepaid payment service system which concerns on this embodiment.

Next, the prepaid payment service system, the prepaid payment processing method, and the program of the present embodiment will be described 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 all the drawings for explaining the embodiment, the same reference numerals are used for those having the same function, and the repeated description will be omitted.
Further, "based on XX" in the present application means "based on at least XX", and includes a case where it is based on another element in addition to XX. Further, "based on XX" is not limited to the case where XX is used directly, but also includes the case where XX is calculated or processed. "XX" is an arbitrary element (for example, arbitrary information).

(Embodiment)
Hereinafter, embodiments of the present invention will be described 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, the 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 member store terminal 20, the terminal device 25, 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, WAN (Wide Area Network), LAN (Local Area Network), public line, provider device, dedicated line, 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 a 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 settlement 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 "wallet") for prepaid payment means.
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 and 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 postpaid payment means possessed by the credit card. In the present embodiment, as an example, the case where the function of the payment tool is added to the credit card will be described. Hereinafter, credit cards to which the function of a payment tool is added may be collectively referred to as a card.
The payment processing device 40 sets the usage limit of each of the plurality of payment tools. Further, the payment processing device 40 is a plurality of payment processing devices 40 based on the total amount of the advance payment paid (deposited) to the deposit / withdrawal account of the prepaid payment means and the usage limit of each of the plurality of payment tools. Determine the amount of money available for each of your payment tools.

By operating the terminal device 10, the administrator M requests the prepaid payment service system to create a wallet. The administrator M inputs the user identifier (user ID) and the information indicating that the wallet creation is requested to the terminal device 10. Here, the user ID is information that can uniquely identify the administrator M, such as the e-mail address of the administrator M.
The terminal device 10 acquires a user ID and information indicating that the wallet is requested to be created. The terminal device 10 includes the acquired user ID and information indicating that the wallet is requested to be created, and creates a wallet creation request message addressed to the management device 30. 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 transmitted by the terminal device 10. The management device 30 acquires the user ID included in the received wallet creation request message and the information indicating that the wallet creation request is requested. The management device 30 creates (opens) a wallet based on the information indicating that the acquired wallet is requested to be created. The management device 30 stores the wallet ID of the created wallet in association with 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 includes the wallet ID of the created wallet and creates a wallet registration request message 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 the user information DB. The user information DB is user information in which a plurality of confidential IDs, a plurality of card IDs, a plurality of usage limits, a plurality of availability, a plurality of wallet IDs, and a plurality of available amounts are associated with each other. Is stored one or more.
The payment processing device 40 receives the wallet registration request message transmitted 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 including the wallet ID and destined for 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 transmitted 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 includes the acquired wallet ID and creates a wallet creation response message 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 transmitted 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 administrator M requests the prepaid payment service system to issue a payment tool. The administrator M inputs the wallet ID, the number of cards to be issued, the usage limit for each card, and the availability of each card to the terminal device 10.
Here, the number of cards issued is the number of cards issued in association with (associate with) 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, semiannual, yearly, and semiannual. By setting the usage limit to zero, the use of the card can be temporarily restricted. The availability of each card is information indicating whether or not each card can be used.
The terminal device 10 acquires a wallet ID, information indicating the number of cards issued, information indicating a usage limit for each card, and information indicating whether or not 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 the availability of each card, and issues a payment tool addressed to the management device 30. Create a request message. The terminal device 10 transmits the created payment tool issuance 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 the card issuing company, and registers each of the acquired plurality of card numbers in the card DB. The card DB stores the card number, the secret ID (hereinafter referred to as "confidential ID") used by the management device 30 and the payment processing device 40, and the expiration date in association with each other.
The management device 30 receives the payment tool issuance request message transmitted by the terminal device 10. The management device 30 acquires the wallet ID included in the received payment tool issuance request message, information indicating the number of cards issued, information indicating the usage limit for each card, and information indicating the availability of each card. To do. The management device 30 sets each of the plurality of payment tools based on the information indicating the number of issued cards acquired.

The management device 30 assigns and associates a plurality of card numbers with each of the plurality of payment tools from the card numbers registered in the card DB.
The management device 30 includes a wallet ID, a confidential ID stored in association with each of a plurality of card numbers assigned to each of the plurality of payment tools, information indicating a usage limit for each card, and usage for each card. A payment tool registration request message addressed to the payment processing device 40 is created, including information indicating whether or not the payment is possible. 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 transmitted by the management device 30. The payment processing device 40 acquires the wallet ID included in the received payment tool registration request message, a plurality of confidential IDs, information indicating the usage limit for each card, and information indicating the availability of each card. .. 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 thereof used to uniquely distinguish a specific card from a plurality of cards.
The payment processing device 40 associates a plurality of confidential IDs, a plurality of card IDs, information indicating a plurality of usage limits, information indicating a plurality of availability, and a wallet ID in the user information DB, respectively. And remember.
The payment processing device 40 includes a plurality of information associated with the confidential ID and the wallet ID, and creates a payment tool registration response message 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 transmitted by the payment processing device 40. The management device 30 acquires a plurality of information associated with the confidential ID and the 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 information associated with the acquired confidential ID and the wallet ID. The management device 30 includes a plurality of information associated with the card number and the wallet ID, and creates a payment tool issuance response message addressed to the terminal device 10. The management device 30 transmits the created payment tool issuance response message to the terminal device 10.

The terminal device 10 receives the payment tool issuance response message transmitted by the management device 30. The terminal device 10 acquires a plurality of information associated with the card number and the wallet ID included in the received payment tool issuance response message. The terminal device 10 displays the acquired information. The administrator M refers to a plurality of information associated with the card number and the wallet ID, and uses the card 5 with the card number as the corresponding plurality of users (messengers) (hereinafter referred to as "user U"). Issue to.

The administrator M uses the terminal device 10 to specify the wallet ID and the deposit amount to perform an operation of depositing money into the wallet corresponding to the wallet ID. Based on the operation of the administrator M, the terminal device 10 includes information indicating the wallet ID and information indicating the deposit amount, and creates a prepaid payment means (electronic money) deposit request message addressed to the financial institution 15. To do. The terminal device 10 transmits the created prepaid payment means (electronic money) payment request message to the financial institution 15.

The financial institution 15 receives the prepaid payment means (electronic money) payment request message transmitted 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 means (electronic money) deposit request message and the information indicating the deposit amount. Perform processing. The financial institution 15 includes a wallet ID and information indicating a deposit amount, and creates a prepaid payment means (electronic money) deposit completion message addressed to the payment processing device 40. The financial institution 15 transmits the created prepaid payment means (electronic money) payment completion message to the payment processing device 40.

The payment processing device 40 receives the prepaid payment means (electronic money) payment completion message transmitted by the financial institution 15. Based on the wallet ID included in the received prepaid payment means (electronic money) deposit completion message and the information indicating the deposit amount, the payment processing device 40 adds the information indicating the deposit amount to the wallet corresponding to the wallet ID. Make sure that the applicable amount has been deposited.
The payment processing device 40 is associated with each of the plurality of card IDs associated with the wallet ID after confirming that the amount corresponding to the deposit amount has been deposited in the wallet corresponding to the wallet ID. Determine the available amount and store the determined available amount.

FIG. 2 is a diagram showing an outline of a prepaid payment service system according to the present embodiment.
In FIG. 2, the financial institution 15, the wallet W received from the financial institution, the payment tool PT-1, the payment tool PT-2, ..., The payment tool PT- associated with the wallet ID of the wallet W are shown. N (N is an integer of N> 1) is shown.
The wallet W is a deposit / withdrawal account of a prepaid payment instrument and has a balance. One wallet W is associated with the payment tool PT-1, the payment tool PT-2, ..., The payment tool PT-N.
Each of the payment tool PT-1, the payment tool PT-2, ..., And the payment tool PT-N is associated (linked) with the wallet account (wallet ID) of the wallet W. Each of the payment tool PT-1, the payment tool PT-2, ..., The payment tool PT-N has no balance.
The deposit amount from the financial institution 15 to the wallet W corresponding to the wallet ID based on the wallet ID included in the prepaid payment means (electronic money) deposit request message transmitted by the terminal device 10 and the information indicating the deposit amount. The amount corresponding to is deposited. The payment processing device 40 confirms that the amount corresponding to the deposit amount has been deposited in the wallet W corresponding to the wallet ID, and then the payment tool PT-1 and the payment tool PT-2 associated with the wallet ID. , ..., Determine the available amount of payment tool PT-N and store the determined available amount. A usage limit is set for each of the payment tool PT-2, ..., And the payment tool PT-N, but the usable amount is set to be equal to or less than the balance of the wallet W. In other words, the usage limit of each of the payment tool PT-2, ..., And the payment tool PT-N can be set to an amount higher than the balance of the wallet W. As a result, it is not possible to settle an amount exceeding the balance of the wallet W. The explanation will be continued by returning to FIG.
The payment processing device 40 includes information indicating that the payment has been made to the wallet, and creates a prepaid payment means (electronic money) payment response message addressed to the terminal device 10. The payment processing device 40 transmits the created prepaid payment means (electronic money) payment response message to the terminal device 10.
The terminal device 10 receives the prepaid payment means (electronic money) payment response message transmitted by the payment processing device 40. The terminal device 10 acquires information indicating that the payment has been made to the wallet included in the received prepaid payment means (electronic money) payment response message. The terminal device 10 notifies the administrator M that the payment has been made by displaying the information indicating that the payment has been made to the acquired wallet.

One user U who has received the issuance of the card 5 accesses the member store terminal 20 and visits the shopping site by operating the terminal device 25. User U purchases products that are billed on a regular basis at the shipping site. Examples of products that are billed on a regular basis include payment of utilities such as electricity, gas, and water, subscription to magazines, and payment of telephone charges. The user U inputs the card number of the card 5 used for payment and the expiration date of the card 5 on the shopping site when subscribing to a product for which billing occurs on a regular basis. The terminal device 25 includes the card number input by the user U and the information indicating the expiration date of the card 5, and creates a periodic payment application message addressed to the member store terminal 20. The terminal device 25 transmits the created periodic payment application message to the member store terminal 20.
The member store terminal 20 receives the periodic payment application message transmitted by the terminal device 25. The member store terminal 20 acquires the card number included in the received periodic payment application message and the information indicating the expiration date of the card 5. The member store terminal 20 includes the acquired card number and information indicating the expiration date of the card 5, and creates a periodic payment request message addressed to the management device 30. The member store terminal 20 transmits the created periodic payment request message to the management device 30.

The management device 30 receives the periodic payment request message transmitted by the member store terminal 20. The management device 30 acquires the card number included in the received periodic payment request message and the information indicating the expiration date of the card 5. The management device 30 acquires the information indicating the expiration date stored in association with the acquired card number from the card DB, the information indicating the acquired expiration date, and the information indicating the expiration date acquired from the periodic payment request message. Judges whether or not matches. When the management device 30 determines that the information indicating the expiration date acquired from the card DB and the information indicating the expiration date acquired from the periodic payment request message match, the management device 30 provides information indicating that the periodic payment application is possible. Create a recurring payment request response message addressed to the member store terminal 20, including the card number and the information indicating that the created recurring payment application is possible. When the management device 30 determines that the information indicating the expiration date acquired from the card DB and the information indicating the expiration date acquired from the periodic payment request message do not match, the management device 30 indicates that the periodic payment application is impossible. The information is created, and a periodic payment request response message addressed to the member store terminal 20 is created, including the card number and the information indicating that the created periodic payment application is not possible. The management device 30 transmits the created periodic payment request response message to the member store terminal 20.
The member store terminal 20 receives the periodic payment request response message transmitted by the management device 30, the card number included in the received periodic payment request response message, information indicating that the periodic payment application is possible, and the periodic payment application. Acquires either information or information indicating that is impossible. The member store terminal 20 stores the periodic billing DB. The periodic billing DB stores one or a plurality of periodic billing information in which a plurality of card numbers, a plurality of billing identification information, and a plurality of billing dates and times are associated with each other. Here, the billing identification information is information for identifying bills that occur periodically. The billing identification information may be the same as the slip identification information described later. When the member store terminal 20 acquires the information indicating that the periodic payment application is possible, the member store terminal 20 creates the billing identification information, and associates the card number, the created billing identification information, and the billing date and time with the periodic billing DB. Remember in. The member store terminal 20 includes information on either one of the acquired information indicating that the periodic payment application is possible and the information indicating that the periodic payment application is not possible, and the periodic payment addressed to the terminal device 25 is the destination. Create a payment request response message. The member store terminal 20 transmits the created periodic payment application response message to the terminal device 25.

The terminal device 25 receives the periodic payment application response message transmitted by the member store terminal 20. The terminal device 25 acquires either information indicating that the periodic payment application is possible or information indicating that the periodic payment application is not possible, which is included in the received periodic payment application response message. .. The terminal device 25 displays information on either one of the acquired information indicating that the periodic payment application is possible and the information indicating that the periodic payment application is not possible.
The member store terminal 20 refers to the periodic billing DB, and when there is a bill whose billing date and time has arrived, the member store terminal 20 includes a card number corresponding to the billing date and time, information indicating the billing amount, and billing identification information, and is a management device. Create a periodic billing message addressed to 30. The member store terminal 20 transmits the created periodic billing message to the management device 30.
The management device 30 receives the periodic billing message transmitted by the member store terminal 20. The management device 30 acquires the card number included in the received periodic billing message, the information indicating the billing amount, and the billing identification information. 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 the expiration date based on the acquired expiration date. After confirming that the card 5 is within the expiration date, the management device 30 acquires the Confidential ID stored in association with the acquired card number. The management device 30 includes the acquired confidential ID, information indicating the billing amount, and billing identification information, and creates a payment request message 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 transmitted by the management device 30. The payment processing device 40 acquires the confidential ID included in the received payment request message, the information indicating the billing amount, and the billing identification information. The payment processing device 40 obtains the card ID stored in association with the acquired confidential ID, the information indicating the usage limit amount, the information indicating the availability, and the information indicating the available amount from the user information DB. get. The payment processing device 40 stores the deposit DB. The deposit DB stores one or more guarantee amount information in which one or more confidential IDs, one or more slip identification information, and information indicating one or more guarantee amounts are associated with each wallet ID. To do. The slip identification information is information for identifying the payment corresponding to the billing identification information that occurs regularly. The payment processing device 40 acquires the slip identification information stored in association with the acquired confidential ID from the deposit DB.
The payment processing device 40 determines whether or not it is available based on the acquired information indicating whether or not it can be used. When it is determined that the payment processing device 40 can be used, the payment processing device 40 determines whether or not the slip identification information acquired from the deposit DB includes (associated) the billing identification information. When the payment processing device 40 determines that the slip identification information acquired from the deposit DB does not include the billing identification information, the payment processing device 40 is based on the information indicating the billing amount and the information indicating the available amount. , Determine if the billed amount is less than or equal to the available amount. The payment processing device 40 performs payment processing when it is determined that the billed amount is equal to or less than the available amount.
When the settlement processing device 40 determines that the slip identification information acquired from the security deposit DB includes the information corresponding to the billing identification information, the payment processing device 40 corresponds to the billing identification information among the slip identification information acquired from the security deposit DB. The guarantee amount stored in association with is acquired from the deposit DB. The payment processing device 40 is updated by adding the acquired guarantee amount to the available amount. The payment processing device 40 determines whether or not the billed amount is equal to or less than the updated available amount based on the information indicating the billed amount and the information indicating the updated available amount. The payment processing device 40 performs payment processing when it is determined that the billed amount is equal to or less than the updated available amount.
When the payment processing device 40 determines that the billed amount is less than the updated available amount, the payment processing device 40 identifies the wallet ID stored in association with the acquired card ID. The payment processing device 40 limits the use of the wallet by disabling the availability associated with the specified wallet ID. As a result, the use of each of the multiple payment tools associated with the restricted wallet is restricted.
The payment processing device 40 includes a confidential ID and information indicating a payment result, and creates a payment response message addressed to the management device 30. The settlement result is either that the settlement has been completed or that the settlement has not been completed. If the payment is not completed, the reason may be added. The payment processing device 40 transmits the created payment response message to the management device 30.
Further, the payment processing device 40 creates the slip identification information corresponding to the billing identification information when it is determined that the slip identification information does not include the billing identification information. The payment processing device 40 determines the guarantee amount corresponding to the created slip identification information by deriving the guarantee amount based on the billed amount. The payment processing device 40 determines whether or not the derived guarantee amount is equal to or less than the available amount. When the settlement processing device 40 determines that the derived guarantee amount is less than or equal to the available amount, the payment processing device 40 subtracts the derived guarantee amount from the available amount. The payment processing device 40 updates the guarantee amount corresponding to the slip identification information with the derived guarantee amount.
When the payment processing device 40 determines that the derived guaranteed amount is higher than the available amount, the payment processing device 40 specifies the wallet ID stored in association with the acquired card ID in the user information DB. The payment processing device 40 changes the availability associated with the specified wallet ID to be unusable. This freezes the wallet and limits its use. As a result, the use of each of the multiple payment tools associated with the restricted wallet is restricted. The payment processing device 40 stores the notification destination DB. The notification destination DB stores one or a plurality of notification destination information in which one or a plurality of confidential IDs and information indicating one or a plurality of notification destinations are associated with each wallet ID. An example of a notification destination is an IP address. The payment processing device 40 acquires information indicating the notification destination stored in association with the confidential ID from the notification destination information corresponding to the wallet ID of the wallet whose use is restricted from the notification destination DB. The payment processing device 40 includes information indicating that the wallet has been frozen, and creates a payment request message addressed to the acquired notification destination. The payment processing device 40 transmits the created payment request message to the notification destination.
The management device 30 receives the payment response message transmitted by the payment processing device 40. The management device 30 acquires information indicating the payment result included in the received payment response message. The management device 30 includes information indicating the acquired payment result, and creates a periodic billing response message addressed to the member store terminal 20. The management device 30 transmits the created periodic billing response message to the member store terminal 20.
The member store terminal 20 receives the periodic billing response message transmitted by the management device 30. The member store terminal 20 acquires information indicating a payment result included in the received periodic billing response message. The member store terminal 20 displays information indicating the acquired payment result.
Hereinafter, details of the management device 30, the payment processing device 40, the member store terminal 20, and the terminal device 10 included in the prepaid payment service system will be sequentially described.

[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 unit 31, a reception unit 32, a setting unit 35, a conversion unit 36, a determination unit 37, a creation unit 38, and a storage unit 39.
The communication unit 31 is realized by a communication module. Specifically, the communication unit 31 is composed of a device that performs wired communication. Further, the communication unit 31 may be configured by a wireless device that performs wireless communication by wireless communication technology such as LTE or wireless LAN. The communication unit 31 communicates between the terminal device 10, the member store terminal 20, the terminal device 25, 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 output by the creation unit 38 to the terminal device 10. The communication unit 31 transmits the wallet registration request 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 issuance request message transmitted by the terminal device 10, and transmits the payment tool issuance 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 periodic payment request message transmitted by the member store terminal 20, and transmits the periodic payment request response message output by the creation unit 38 to the member store terminal 20. The communication unit 31 receives the periodic billing message transmitted by the member store terminal 20, and transmits the periodic billing response message output by the creation unit 38 to the member 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 transmitted 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 the card DB 39a. The card DB39a may be stored in the cloud.
FIG. 3 is a diagram showing an example of a card DB. The card DB39a is tabular information in which the card number, the confidential ID, and the expiration date are associated with each other. 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 with each other, and the card number "card number # 3", the confidential ID "confidential ID # 3", and the expiration date ". 2022/03 "is associated and stored. This information is registered when the management device 30 acquires a plurality of card numbers issued by the card issuing company. Returning to FIG. 1, the explanation will be continued.

The reception unit 32, the setting unit 35, the conversion unit 36, the determination unit 37, and the creation unit 38 execute, for example, a program (software) stored in the storage unit 39 by a hardware processor such as a CPU (Central Processing Unit). It is realized by. In addition, some or all of these functional units are hardware (circuits) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit). It may be realized by the part; including circuitry), or it may be realized by the cooperation of software and hardware. The program may be stored in advance in a storage device (a storage device including a non-transient storage medium) such as an HDD (Hard Disk Drive) or a flash memory, or a removable storage device such as a DVD or a CD-ROM. It is stored in a medium (non-transient storage medium) and may be installed by mounting the storage medium in a drive device.

Regarding the reception unit 32, the setting unit 35, the conversion unit 36, the judgment unit 37, and the creation unit 38, the processing when the administrator M requests the prepaid payment service system to create the wallet, and the administrator M Issuance of payment tools is divided into processing when requesting a prepaid payment service system and processing when user U purchases a product that is billed regularly at a shopping site provided by a member store. I will explain.
The process when the administrator M requests the prepaid payment service system to create the wallet will be described.
The communication unit 31 receives the wallet creation request message transmitted 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 the information indicating that the wallet is requested to be created. The reception unit 32 outputs the acquired user ID and information indicating that the wallet creation is requested to the setting unit 35.

The setting unit 35 acquires the user ID output by the reception unit 32 and the information indicating that the wallet creation is requested. The setting unit 35 creates (opens) a wallet based on the information indicating that the acquired wallet is requested to be created. The setting unit 35 associates the wallet ID of the created wallet with the user ID and stores it in the storage unit 39.
The creation unit 38 creates a wallet registration request message including the wallet ID and destined for 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 transmitted 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 reception unit 32 acquires 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 the user ID stored in association with the wallet ID from the storage unit 39. The creation unit 38 creates a wallet creation response message that includes the user ID and the wallet ID and is destined for the terminal device 10. The creation unit 38 outputs the created wallet creation response message to the communication unit 31.

The process when the administrator M requests the issuance of the payment tool to the prepaid payment service system will be described.
The communication unit 31 receives the payment tool issuance request message transmitted by the terminal device 10. The communication unit 31 outputs the received payment tool issuance request message to the reception unit 32.
The reception unit 32 receives the payment tool issuance request message output by the communication unit 31. The reception unit 32 acquires the wallet ID included in the received payment tool issuance request message, information indicating the number of cards issued, information indicating the usage limit for each card, and information indicating the availability of each card. To do. The reception unit 32 outputs the acquired wallet ID, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating availability for each card to the setting unit 35.

The setting unit 35 acquires the wallet ID output by the reception unit 32, information indicating the number of cards issued, information indicating the usage limit for each card, and information indicating whether or not the card can be used. The setting unit 35 issues a plurality of payment tools based on the information indicating the number of issued cards acquired. The setting unit 35 sets by assigning a plurality of card numbers stored in the card DB 39a to each of the plurality of issued payment tools.
The creation unit 38 indicates a wallet ID, a confidential ID stored in association with a card number assigned to each of a plurality of payment tools, information indicating a usage limit for each card, and availability for each card. Create a payment tool registration request message that includes information and is destined for 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 transmitted 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 information associated with the confidential ID and the wallet ID included in the received payment tool registration response message. The reception unit 32 outputs a plurality of information associated with the acquired confidential ID and the wallet ID to the creation unit 38.
The creation unit 38 acquires a plurality of information in which the confidential ID output by the reception unit 32 and the wallet ID are associated with each other. 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 the plurality of information associated with the acquired confidential ID and the wallet ID. The creation unit 38 creates a payment tool issuance response message addressed to the terminal device 10, including a plurality of information associated with the card number and the wallet ID. The creation unit 38 outputs the created payment tool issuance response message to the communication unit 31.

The process when the user U purchases a product for which a bill is regularly generated on a shopping site provided by a member store will be described.
The communication unit 31 receives the periodic payment request message transmitted by the member store terminal 20. The communication unit 31 outputs the received periodic payment request message to the reception unit 32.
The reception unit 32 receives the periodic payment request message output by the communication unit 31. The reception unit 32 acquires the card number included in the received periodic payment request message and the information indicating the expiration date of the card 5. The reception unit 32 outputs the acquired card number and information indicating the expiration date of the card 5 to the determination unit 37.

The determination unit 37 acquires the card number output by the reception unit 32 and the information indicating the expiration date of the card 5. 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 the expiration date based on the acquired expiration date. When the determination unit 37 determines that the card 5 is not within the expiration date, the determination unit 37 outputs a determination result of whether or not the card 5 is within the expiration date to the creation unit 48.
The creation unit 48 acquires a determination result of whether or not the card 5 output by the determination unit 37 is within the expiration date. The creation unit 48 creates a periodic payment request response message addressed to the member store terminal 20, including a determination result of whether or not the card 5 is within the expiration date. The creation unit 48 outputs the created periodic payment request response message to the communication unit 31.
A case where a request that occurs regularly occurs will be described.
The communication unit 31 receives the periodic billing message transmitted by the member store terminal 20. The communication unit 31 outputs the received periodic billing message to the reception unit 32.
The reception unit 32 receives the periodic billing message output by the communication unit 31. The reception unit 32 acquires the card number included in the received periodic billing message, the information indicating the billing amount, and the billing identification information. The reception unit 32 outputs the acquired card number, information indicating the billing amount, and billing identification information to the determination unit 37.

The determination unit 37 acquires the card number output by the reception unit 32, the information indicating the billing amount, and the billing identification information. 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 the expiration date based on the acquired expiration date. When the determination unit 37 determines 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 the 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 determination unit 37 acquires the confidential ID output by the conversion unit 36. The determination unit 37 outputs the confidential ID, the information indicating the billing amount, and the billing identification information to the creation unit 38.
The creation unit 38 acquires the confidential ID output by the determination unit 37, the information indicating the billing amount, and the billing identification information. The creation unit 38 creates a payment request message addressed to the payment processing device 40, including the confidential ID, information indicating the billing amount, and billing identification information. The creation unit 38 outputs the created payment request message to the communication unit 31.
When 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 of whether or not 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 unit 38.
The creation unit 38 acquires the card number output by the determination unit 37 and the determination result of whether or not the card 5 is within the expiration date. The creation unit 38 creates a periodic billing response message addressed to the member store terminal 20, including the acquired card number and the determination result of whether or not the card 5 is within the expiration date. The creation unit 38 outputs the created periodic request response message to the communication unit 31.

The communication unit 31 receives the payment response message transmitted 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 receives the payment response message output by the communication unit 31. The reception unit 32 acquires the confidential ID included in the received payment response message and the 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 the 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 includes the acquired card number and information indicating the payment result, and creates a withdrawal response message addressed to the member store terminal 20. 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 composed of a device that performs wired communication. Further, the communication unit 41 may be configured by a wireless device that performs wireless communication by 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 transmitted by the management device 30, and transmits 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 transmitted by the management device 30, and transmits 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) payment completion message transmitted by the financial institution 15, and transmits the prepaid payment means (electronic money) payment response message output by the creation unit 48 to the terminal device 10. To do. The communication unit 41 receives the payment request message transmitted by the management device 30, and transmits the payment response message output by the creation unit 48 to the management device 30.

The storage unit 49 is realized by an HDD, a flash memory, a RAM, a ROM, or the like. The storage unit 49 stores the user information DB 49a, the deposit DB 49b, and the notification destination DB 49c. The user information DB 49a, the deposit DB 49b, and the notification destination DB 49c may be stored in the cloud.
FIG. 4 is a diagram showing an example of a user information DB. The user information DB 49a is information having a plurality of table-format user information in which a confidential ID, a card ID, a usage limit, availability, a wallet ID, and a usable amount are associated with each other. In the example shown in FIG. 4, the user information DB 49a has a confidential ID "confidential ID # 1", a card ID "card ID # 1", a usage limit "*****", and availability "possible". And the wallet ID "wallet ID # 1" and the available amount "usable amount # 1" are stored in association with each other.
Further, 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 availability ". "Not possible", the wallet ID "wallet ID # 2", and the available amount "usable amount # 2" are stored in association with each other. Further, 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 availability ". "Yes", the wallet ID "Wallet ID # 3", and the available amount "Available amount # 3" are stored in association with each other.
That is, in the example of the user information DB49a shown in FIG. 4, the confidential IDs “confidential ID # 1”, “confidential ID # 2”, and “confidential ID # 3” are the wallet ID “wallet ID”. It is shown that the wallet corresponding to "# 1" is commonly used.
FIG. 5 is a diagram showing an example of a deposit DB. The deposit DB49b is information having a plurality of table-type deposit information in which the confidential ID, the slip identification information, and the deposit amount are associated with each wallet ID. Here, the slip identification information is information for identifying a transaction regarding the purchase of goods, and is associated with the billing identification information. The guarantee amount is the amount of the balance that is allocated separately from the available amount in order to guarantee payment for bills that occur on a regular basis.
In the example shown in FIG. 5, the deposit DB49b stores the confidential ID “confidential ID # 1”, the slip identification information “slip identification information # 1”, and the guarantee amount “*****” in association with each other. Has been done. Further, in the example shown in FIG. 5, the security deposit DB49b stores the confidential ID "confidential ID # 2", the slip identification information "slip identification information # 2", and the guarantee amount "++++" in association with each other. There is. Further, in the example shown in FIG. 5, the deposit DB49b is associated with the confidential ID "confidential ID # 3", the slip identification information "slip identification information # 2", and the guarantee amount "*++++". Is remembered.
That is, in the example of the deposit DB49b shown in FIG. 5, the confidential IDs “confidential ID # 1”, “confidential ID # 2”, and “confidential ID # 3” are the wallet ID “wallet ID #”. It is shown that the wallet corresponding to "1" is commonly used.
FIG. 6 is a diagram showing an example of the notification destination DB. The notification destination DB 49c is information having a plurality of table-format notification destination information in which the confidential ID and the notification destination are associated with each wallet.
In the example shown in FIG. 6, the notification destination DB 49c stores the confidential ID “confidential ID # 1” and the notification destination “*****” in association with each other. Further, in the example shown in FIG. 6, the notification destination DB 49c stores the confidential ID “confidential ID # 2” and the notification destination “++++++” in association with each other. Further, in the example shown in FIG. 6, the notification destination DB 49c stores the confidential ID "confidential ID # 3" and the notification destination "*++++" in association with each other.
That is, in the example of the notification destination DB49c shown in FIG. 6, the confidential IDs “confidential ID # 1”, “confidential ID # 2”, and “confidential ID # 3” are the wallet ID “wallet ID”. It is shown that the wallet corresponding to "# 1" is commonly used. The explanation will be continued by returning to FIG.

The reception unit 42, the processing unit 43, the determination unit 44, the settlement unit 45, the determination unit 47, and the creation unit 48, for example, execute a program (software) stored in the storage unit 49 by a hardware processor such as a CPU. Is realized by. Further, a part or all of these functional parts may be realized by hardware (including circuit part; circuitry) such as LSI, ASIC, FPGA, GPU, or by cooperation between software and hardware. It may be realized. The program may be stored in advance in a storage device such as an HDD or a flash memory (a storage device including a non-transient storage medium), or a removable storage medium such as a DVD or a CD-ROM (non-transient). It is stored in a sex storage medium) and may be installed by attaching the storage medium to a drive device.

Regarding the reception unit 42, the processing unit 43, the decision unit 44, the settlement unit 45, the judgment unit 47, and the creation unit 48, the processing and management when the administrator M requests the prepaid payment service system to create a wallet. The processing when the person M requests the issuance of the payment tool to the prepaid payment service system, the processing when the administrator M requests the deposit / withdrawal account of the prepaid payment method, and the user U , The processing when purchasing a product that is billed regularly on the shopping site provided by the member store will be explained separately.
The process when the administrator M requests the prepaid payment service system to create the wallet will be described.
The communication unit 41 receives the wallet registration request message transmitted 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 reception unit 42 acquires 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 including the wallet ID and destined for the management device 30. The creation unit 48 outputs the created wallet registration response message to the communication unit 41.

The process when the administrator M requests the issuance of the payment tool to the prepaid payment service system will be described.
The communication unit 41 receives the payment tool registration request message transmitted 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 the wallet ID included in the received payment tool registration request message, a plurality of confidential IDs, information indicating the usage limit for each card, and information indicating the availability of each card. 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 the availability of 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 whether or not the card can be used. The processing unit 43 creates a plurality of card IDs associated with each of the acquired plurality of 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 the acquired user information in association with each of the plurality of confidential IDs, the created card ID, the information indicating the usage limit amount, and the information indicating the availability.
The creation unit 48 creates a payment tool registration response message destined for the management device 30, which includes a plurality of pieces of information associated with the confidential ID and the wallet ID. The creation unit 48 outputs the created payment tool registration response message to the communication unit 41.

The process when the administrator M requests the deposit / withdrawal account of the prepaid payment method will be described.
The communication unit 41 receives the prepaid payment means (electronic money) payment completion message transmitted by the financial institution 15. The communication unit 41 outputs the received prepaid payment means (electronic money) payment completion message to the reception unit 42.
The reception unit 42 acquires the prepaid payment means (electronic money) payment 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 deposit amount to the determination unit 47.

The determination unit 47 acquires the wallet ID output by the reception unit 42 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 in the wallet corresponding to the wallet ID based on the acquired wallet ID and the information indicating the deposit amount. Here, for the wallet ID, even if the total amount of the usage limit set in association with each of the plurality of card IDs is higher than the total amount of money deposited in the wallet corresponding to the wallet ID. Good.
The determination unit 47 outputs the wallet ID and the determination result of whether or not the amount corresponding to the information indicating the deposit amount has been deposited to the determination unit 44 and the creation unit 48.
The determination unit 44 acquires the wallet ID output by the determination unit 47 and the determination result of whether or not the amount corresponding to the information indicating the deposit amount has been deposited. When the acquired determination result indicates that the amount corresponding to the information indicating the deposit amount has been deposited, the determination unit 44 uses each of the plurality of card IDs for the acquired wallet ID in the user information DB 49a. Determine the possible amount.
Specifically, when the usage limit set for the wallet ID 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 determination unit 44 determines. As the available amount, determine and store the amount deposited in the wallet. When the usage limit set for 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 determination unit 44 uses the wallet ID as the available amount. Determine and memorize limits.
The creation unit 48 acquires a determination result of whether or not the deposit amount output by the determination unit 47 has been deposited. The creation unit 48 creates a prepaid payment means (electronic money) payment response message to the terminal device 10 including the acquired determination result. The creation unit 48 outputs the created prepaid payment means (electronic money) payment response message to the communication unit 41.

The process when the user U purchases a product for which a bill is regularly generated on a shopping site provided by a member store will be described.
The communication unit 41 receives the payment request message transmitted 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 included in the acquired payment request message, the information indicating the billing amount, and the billing identification information. The reception unit 42 outputs the acquired confidential ID, information indicating the billing amount, and billing identification information to the determination unit 47.
The processing unit 43 updates the usage limit amount based on an arbitrary period specified for the usage limit amount in the user information DB 49a. When updating the usage limit, the processing unit 43 sets 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 it is higher than the amount deposited, it will be updated by setting the available amount to the amount deposited in the wallet. The processing unit 43 is in the case where the usage limit is equal to or less than the amount deposited in 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. Is updated by setting a usage limit on the available amount.
The determination unit 47 acquires the confidential ID output by the reception unit 42, the information indicating the billing amount, and the billing identification information. The determination unit 47 acquires the card ID stored in association with the acquired confidential ID, the information indicating the usage limit amount, the information indicating the availability, and the information indicating the available amount from the user information DB 49a. To do. The determination unit 47 acquires the slip identification information stored in association with the acquired confidential ID from the deposit DB 49b. The determination unit 47 determines whether or not the acquired information indicating availability is set to be available. The determination unit 47 determines that payment cannot be made when the information indicating availability is set to unavailable. When it is determined that payment cannot be made, the determination unit 47 outputs the acquired card ID and the payment result (information indicating that payment cannot be made) to the creation unit 48.
The creation unit 48 acquires the card ID output by the determination unit 47 and the payment result. The creation unit 48 acquires the 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 to the management device 30 including the acquired confidential ID and the payment result. The creation unit 48 outputs the created payment response message to the communication unit 41.
Hereinafter, the case where the determination unit 47 is set to enable the information indicating availability will be described.

The determination unit 47 determines whether or not the slip identification information acquired from the deposit DB 49b includes the bill identification information. Hereinafter, the case where the slip identification information includes the billing identification information and the case where the slip identification information does not include the billing identification information will be described separately.
(When the slip identification information includes the billing identification information)
When the determination unit 47 determines that the slip identification information acquired from the security deposit DB 49b includes the information corresponding to the billing identification information, the information indicating the guarantee amount stored in association with the information corresponding to the billing identification information. Is obtained from the deposit DB49b. The determination unit 47 outputs the card ID, the information indicating the billing amount, and the information indicating the acquired guarantee amount to the processing unit 43.
The processing unit 43 acquires the card ID output by the determination unit 47, the information indicating the billing amount, and the information indicating the guaranteed amount. The processing unit 43 updates the available amount by adding the acquired guarantee amount to the available amount stored in association with the acquired card ID in the user information DB 49a. After updating the available amount, the processing unit 43 outputs information indicating that the available amount has been updated to the determination unit 47.
The determination unit 47 acquires information indicating that the available amount output by the processing unit 43 has been updated. When the determination unit 47 acquires the information indicating that the available amount output by the processing unit 43 has been updated, the billing amount can be used based on the information indicating the billing amount and the information indicating the available amount. Determine if it is less than or equal to the amount. Hereinafter, the case where the determination unit 47 determines that the billed amount is less than or equal to the available amount and the case where the billed amount is determined to be higher than the available amount will be described separately.

(When it is determined that the billed amount is less than or equal to the available amount)
When the determination unit 47 determines that the invoice amount is less than or equal to the available amount, the determination unit 47 creates a settlement request including the card ID, the invoice identification information, and the information indicating the invoice amount. The determination unit 47 outputs the created settlement request to the settlement unit 45.
The settlement unit 45 acquires the settlement request output by the determination unit 47. The settlement unit 45 acquires the card ID included in the acquired settlement request, the billing identification information, and the information indicating the billing amount. The settlement unit 45 performs settlement processing based on the acquired card ID and information indicating the billing amount. The settlement unit 45 reduces the billing amount of the user information DB 49a from the amount deposited in the wallet corresponding to the wallet ID associated with the card ID. The determination unit 44 updates the available amount associated with the card ID by reducing the billed amount.
Further, the determination unit 44 determines the usable amount of the wallet ID when 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. As, determine and memorize the amount deposited in the wallet. When the usage limit set for 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 determination unit 44 uses the wallet ID as the available amount. Determine and memorize limits. Here, as for the usage limit associated with the card ID included in the payment request, the billed amount is reduced. Further, as for the available amount associated with the card ID of the used card, the amount in which the billing amount is reduced is used. The settlement unit 45 outputs the card ID and the settlement result to the creation unit 48.
The creation unit 48 acquires the card ID output by the payment unit 45 and the payment result. The creation unit 48 acquires the 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 to the management device 30 including the acquired confidential ID and the payment result. The creation unit 48 outputs the created payment response message to the communication unit 41.

Further, the settlement unit 45 outputs the card ID, the billing identification information, and the information indicating the billing amount to the determination unit 44.
The determination unit 44 acquires the card ID output by the settlement unit 45, the billing identification information, and the information indicating the billing amount. The determination unit 44 determines by deriving the guarantee amount based on the information indicating the acquired billing amount. For example, the determination unit 44 may use the same amount as the billed amount as the guaranteed amount or an amount obtained by increasing or decreasing a predetermined amount from the billed amount as the guaranteed amount based on the information indicating the billed amount. The determination unit 44 outputs the card ID, the billing identification information, and the information indicating the determined guarantee amount to the processing unit 43.
The processing unit 43 acquires the card ID output by the determination unit 44, the billing identification information, and the information indicating the guaranteed amount. The processing unit 43 acquires information indicating the available amount of money stored in association with the card ID from the user information DB 49a. The processing unit 43 determines whether or not the guaranteed amount is equal to or less than the available amount based on the acquired information indicating the guaranteed amount and the information indicating the available amount. When the processing unit 43 determines that the guaranteed amount is less than or equal to the available amount, the processing unit 43 updates the available amount by subtracting the guaranteed amount from the available amount. The processing unit 43 acquires the confidential ID stored in association with the card ID from the user information DB 49a. The processing unit 43 updates the guarantee amount stored in association with the combination of the acquired confidential ID and the slip identification information corresponding to the billing identification information with the information indicating the guarantee amount acquired from the determination unit 44.
When the processing unit 43 determines that the guaranteed amount is higher than the available amount, the processing unit 43 identifies the wallet ID stored in association with the acquired card ID in the user information DB 49a. The processing unit 43 freezes by restricting the use of the wallet by disabling the availability associated with the specified wallet ID. The processing unit 43 outputs the card ID and information indicating that the wallet has been frozen to the creation unit 48.
The creation unit 48 acquires the card ID output by the processing unit 43 and the information indicating that the wallet has been frozen. The creation unit 48 acquires the notification destination stored in association with the acquired card ID from the notification destination information DB 49c. The creation unit 48 creates a deposit request message to the notification destination, including information indicating that the wallet has been frozen, based on the information indicating that the acquired wallet has been frozen and the information indicating the notification destination. .. The creation unit 48 transmits the created payment request message to the communication unit 41.

(If it is determined that the billed amount is higher than the available amount)
When the determination unit 47 determines that the billed amount is higher than the available amount, it determines that the settlement cannot be made. When it is determined that payment cannot be made, the determination unit 47 outputs the acquired card ID and the payment result (information indicating that payment cannot be made) to the processing unit 43.
The processing unit 43 acquires the card ID output by the determination unit 47 and the payment result (information indicating that payment cannot be made). The processing unit 43 identifies the wallet ID stored in association with the acquired card ID in the user information DB 49a based on the acquired card ID and the payment result. The processing unit 43 freezes by restricting the use of the wallet by disabling the availability associated with the specified wallet ID. The processing unit 43 outputs the card ID and information indicating that the wallet has been frozen to the creation unit 48.
The creation unit 48 acquires the card ID output by the processing unit 43 and the information indicating that the wallet has been frozen. The creation unit 48 acquires the notification destination stored in association with the acquired card ID from the notification destination information DB 49c. The creation unit 48 creates a deposit request message to the notification destination, including information indicating that the wallet has been frozen, based on the information indicating that the acquired wallet has been frozen and the information indicating the notification destination. .. The creation unit 48 transmits the created payment request message to the communication unit 41.

(When the billing identification information is not included in the slip identification information)
When the determination unit 47 determines that the slip identification information acquired from the deposit DB49b does not include the billing identification information, the determination unit 47 is based on the information indicating the billing amount and the information indicating the available amount. Determine if the billed amount is less than or equal to the available amount. Hereinafter, the case where the determination unit 47 determines that the billed amount is less than or equal to the available amount and the case where the billed amount is determined to be higher than the available amount will be described separately.
(When it is determined that the billed amount is less than or equal to the available amount)
When the determination unit 47 determines that the invoice amount is less than or equal to the available amount, the determination unit 47 creates a settlement request including the card ID, the invoice identification information, and the information indicating the invoice amount. The determination unit 47 outputs the created settlement request to the settlement unit 45.
The settlement unit 45 acquires the settlement request output by the determination unit 47. The settlement unit 45 acquires the card ID included in the acquired settlement request, the billing identification information, and the information indicating the billing amount. The settlement unit 45 performs settlement processing based on the acquired card ID and information indicating the billing amount. The settlement unit 45 reduces the billing amount of the user information DB 49a from the amount deposited in the wallet corresponding to the wallet ID associated with the card ID. The determination unit 44 updates the available amount associated with the card ID by reducing the billed amount.
Further, the determination unit 44 determines the usable amount of the wallet ID when 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. As, determine and memorize the amount deposited in the wallet. When the usage limit set for 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 determination unit 44 uses the wallet ID as the available amount. Determine and memorize limits. Here, the determination unit 44 uses a usage limit amount associated with the card ID included in the payment request with the billing amount reduced. Further, the determination unit 44 uses the amount of the available amount associated with the card ID of the card used, which is the amount reduced. The settlement unit 45 outputs the card ID and the settlement result to the creation unit 48.
The creation unit 48 acquires the card ID output by the payment unit 45 and the payment result. The creation unit 48 acquires the 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 to the management device 30 including the acquired confidential ID and the payment result. The creation unit 48 outputs the created payment response message to the communication unit 41. In addition, the creation unit 48 creates the slip identification information, and associates (associates) the created slip identification information with the acquired confidential ID and the billing identification information. The creation unit 48 associates the confidential ID with the created slip identification information and stores it in the deposit DB 49b.

Further, the settlement unit 45 outputs the card ID, the billing identification information, and the information indicating the billing amount to the determination unit 44.
The determination unit 44 acquires the card ID output by the settlement unit 45, the billing identification information, and the information indicating the billing amount. The determination unit 44 determines the guarantee amount based on the information indicating the acquired billing amount. For example, the determination unit 44 may use the same amount as the billed amount as the guaranteed amount or an amount obtained by increasing or decreasing a predetermined amount from the billed amount as the guaranteed amount based on the information indicating the billed amount. The determination unit 44 outputs the card ID, the billing identification information, and the information indicating the determined guarantee amount to the processing unit 43.
The processing unit 43 acquires the card ID output by the determination unit 44, the billing identification information, and the information indicating the guaranteed amount. The processing unit 43 acquires information indicating the available amount of money stored in association with the card ID from the user information DB 49a. The processing unit 43 determines whether or not the guaranteed amount is equal to or less than the available amount based on the acquired information indicating the guaranteed amount and the information indicating the available amount. When the processing unit 43 determines that the guaranteed amount is less than or equal to the available amount, the processing unit 43 updates the available amount by subtracting the guaranteed amount from the available amount. The processing unit 43 acquires the confidential ID stored in association with the card ID from the user information DB 49a. The processing unit 43 acquires the confidential ID stored in association with the card ID from the user information DB 49a. The processing unit 43 associates the acquired confidential ID, the created slip identification information, and the information indicating the guarantee amount acquired from the determination unit 44, and stores it in the deposit DB 49b.
When the processing unit 43 determines that the guaranteed amount is higher than the available amount, the processing unit 43 identifies the wallet ID stored in association with the acquired card ID in the user information DB 49a. The processing unit 43 freezes the wallet by disabling the availability associated with the specified wallet ID. The processing unit 43 outputs the card ID and information indicating that the wallet has been frozen to the creation unit 48.
The creation unit 48 acquires the card ID output by the processing unit 43 and the information indicating that the wallet has been frozen. The creation unit 48 acquires the stored notification destination associated with the acquired card ID from the notification destination information DB 49c. The creation unit 48 creates a deposit request message to the notification destination, including information indicating that the wallet has been frozen, based on the information indicating that the acquired wallet has been frozen and the information indicating the notification destination. .. The creation unit 48 transmits the created payment request message to the communication unit 41.

(If it is determined that the billed amount is higher than the available amount)
When the determination unit 47 determines that the billed amount is higher than the available amount, it determines that the settlement cannot be made. When it is determined that payment cannot be made, the determination unit 47 outputs the acquired card ID and the payment result (information indicating that payment cannot be made) to the processing unit 43.
The processing unit 43 acquires the card ID output by the determination unit 47 and the payment result (information indicating that payment cannot be made). The processing unit 43 identifies the wallet ID stored in association with the acquired card ID in the user information DB 49a based on the acquired card ID and the payment result. The processing unit 43 freezes by restricting the use of the wallet by disabling the availability associated with the specified wallet ID. The processing unit 43 outputs the card ID and information indicating that the wallet has been frozen to the creation unit 48.
The creation unit 48 acquires the card ID output by the processing unit 43 and the information indicating that the wallet has been frozen. The creation unit 48 acquires the notification destination stored in association with the acquired card ID from the notification destination information DB 49c. The creation unit 48 creates a deposit request message to the notification destination, including information indicating that the wallet has been frozen, based on the information indicating that the acquired wallet has been frozen and the information indicating the notification destination. .. The creation unit 48 transmits the created payment request message to the communication unit 41.

[Merchant terminal 20]
The member store terminal 20 is, for example, a personal computer, a smartphone, a tablet terminal, or the like. At the member store terminal 20, an application program for using the prepaid payment service system 1, a browser, or the like is activated to support the prepaid payment service. An example of the member store terminal 20 is a personal computer, and it is assumed that an application program (prepaid payment service use application) is running. The prepaid payment service use application communicates with the management device 30 in response to the access from the terminal device 25, and transmits the response received from the management device 30 to the terminal device 25. The member store terminal 20 stores the periodic billing DB. The member store terminal 20 refers to the periodic billing DB, and when there is a bill whose billing date and time has arrived, the member store terminal 20 includes a card number corresponding to the billing date and time, information indicating the billing amount, and billing identification information, and is a management device. Create a periodic billing message addressed to 30. The member store terminal 20 transmits the created periodic billing message to the management device 30.

[Terminal device 10]
The terminal device 10 is, for example, a personal computer, a smartphone, a tablet terminal, or the like. In the terminal device 10, an application program for using the prepaid payment service system 1, a browser, or the like 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 use application) is running. The prepaid payment service use application communicates with the management device 30 in response to the operation of the administrator M, and performs a push notification based on the response received from the management device 30 and the payment processing device 40.
[Terminal device 25]
The terminal device 25 is, for example, a personal computer, a smartphone, a tablet terminal, or the like. The terminal device 25 activates an application program, a browser, or the like for using a shopping site provided by a member store. An example of the terminal device 25 is a personal computer, and it is assumed that an application program (shopping application) is running. The shopping application communicates with the member store terminal 20 in response to the operation of the user U, and performs a push notification based on the response received from the member store terminal 20.

[Operation of prepaid payment service system]
[Operation when administrator M requests the prepaid payment service system to create a wallet]
FIG. 7 is a sequence chart showing Example 1 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 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 the information indicating that the wallet creation is requested. The terminal device 10 includes the acquired user ID and information indicating that the wallet is requested to be created, and creates a wallet creation request message addressed to the management device 30.
(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 transmitted 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 received by the communication unit 31. The reception unit 32 acquires the user ID included in the received wallet creation request message and the information indicating that the wallet is requested to be created. The reception unit 32 outputs the acquired user ID and information indicating that the wallet creation is requested to the setting unit 35.
The setting unit 35 acquires the user ID output by the reception unit 32 and the information indicating that the wallet creation is requested. The setting unit 35 creates a wallet based on the information indicating that the acquired wallet is requested to be created. The setting unit 35 associates the wallet ID of the created wallet with the user ID and stores it in the storage unit 39.
(Step S4-1)
In the management device 30, the creation unit 38 creates a wallet registration request message including the wallet ID and destined for 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 transmitted 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 reception unit 42 acquires 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 including the wallet ID and destined for 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 transmitted 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 reception unit 32 acquires 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. The creation unit 38 acquires a user ID stored in association with the wallet ID based on the acquired wallet ID. The creation unit 38 creates a wallet creation response message that includes the user ID and the wallet and is destined for 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 transmitted by the management device 30.
(Step S12-1)
The terminal device 10 acquires the user ID and the wallet ID included in the received wallet creation response message. The terminal device 10 displays the user ID and the 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 a 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 the created user information can be included 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. As a result, the wallet ID of the created wallet can be notified to the administrator M.

[Operation when administrator M requests the prepaid payment service system to issue a payment tool]
FIG. 8 is a sequence chart showing Example 2 of the operation of the prepaid payment service system according to the present embodiment. FIG. 8 shows an example of processing when the administrator M requests the issuance of a payment tool.
(Step S1-2)
The terminal device 10 acquires the wallet ID input by the administrator M, the information indicating the number of cards issued, the information indicating the usage limit for each card, and the information indicating the availability of each card. 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 or not the card can be used, and is destined for the management device 30. Create a payment tool issue request message.
(Step S2-2)
The terminal device 10 transmits the created payment tool issuance request message to the management device 30.
(Step S3-2)
In the management device 30, the communication unit 31 receives the payment tool issuance request message transmitted by the terminal device 10. The communication unit 31 outputs the received payment tool issuance request message to the reception unit 32. The reception unit 32 receives the payment tool issuance request message received by the communication unit 31. The reception unit 32 acquires the wallet ID included in the received payment tool issuance request message, information indicating the number of cards issued, information indicating the usage limit for each card, and information indicating the availability of each card. To do. The reception unit 32 outputs the acquired wallet ID, information indicating the number of issued cards, information indicating the usage limit for each card, and information indicating availability for each card to the setting unit 35.
The setting unit 35 acquires the wallet ID output by the reception unit 32, information indicating the number of cards issued, information indicating the usage limit for each card, and information indicating whether or not the card can be used. The setting unit 35 sets a plurality of payment tools based on the information indicating the number of issued cards acquired. The setting unit 35 associates each of the plurality of payment tools with the card number stored in the card DB 39a.
(Step S4-2)
In the management device 30, the creation unit 38 indicates 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 availability for each card. Create a payment tool registration request message that includes information and is destined for 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 transmitted 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 the wallet ID included in the received payment tool registration request message, a plurality of confidential IDs, information indicating the usage limit for each card, and information indicating the availability of each card. 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 the availability of 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 whether or not the card can be used. The processing unit 43 creates a plurality of card IDs associated with each of the acquired plurality of confidential IDs.
(Step S7-2)
In the payment processing device 40, the processing unit 43 associates each of the plurality of card IDs with 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 a wallet ID from the user information DB 49a. The processing unit 43 stores the acquired user information in association with each of the plurality of confidential IDs, the created card ID, the information indicating the usage limit amount, and the information indicating the availability.
(Step S9-2)
In the payment processing device 40, the creation unit 48 creates a payment tool registration response message addressed to the management device 30 including a plurality of information associated with the confidential ID and the wallet ID.

(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 transmitted 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 reception unit 32 acquires a plurality of information associated with the confidential ID and the wallet ID included in the received payment tool registration response message. The reception unit 32 outputs a plurality of information associated with the acquired confidential ID and the wallet ID to the creation unit 38.
The creation unit 38 acquires a plurality of information associated with the confidential ID and the 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 the plurality of information associated with the acquired confidential ID and the wallet ID. The creation unit 38 creates a payment tool issuance response message addressed to the terminal device 10, including a plurality of information associated with the card number and the wallet ID.
(Step S12-2)
In the management device 30, the creation unit 38 outputs the created payment tool issuance response message to the communication unit 31. The communication unit 31 acquires the payment tool issuance response message output by the creation unit 38, and transmits the acquired payment tool issuance response message to the terminal device 10.
(Step S13-2)
The terminal device 10 receives the payment tool issuance response message transmitted by the management device 30.
(Step S14-2)
The terminal device 10 acquires a plurality of information associated with the card number and the wallet ID included in the received payment tool issuance response message. The terminal device 10 displays a plurality of information associated with the card number and the wallet ID.
According to an example of processing when the administrator M requests the issuance of the payment tool to the prepaid payment service system, the management device 30 can issue a plurality of payment tools based on the issuance request of the payment tool. Further, the payment processing device 40 can associate a plurality of payment tools with a wallet. Further, the payment processing device 40 can notify the management device 30 of a plurality of information relating the confidential ID and the wallet ID, and the management device 30 can notify the terminal device 10 of a plurality of information relating the card number and the wallet ID. Information can be notified. As a result, the card number of the issued card and the wallet ID used by the card can be notified to the administrator M.

[Operation when administrator M requests deposit to the deposit / withdrawal account of the prepaid payment method]
FIG. 9 is a sequence chart showing Example 3 of the operation of the prepaid payment service system according to the present embodiment. FIG. 9 shows an example of processing when the administrator M requests deposit to the deposit / withdrawal account of the prepaid payment means.
(Step S1-3)
Based on the operation of the administrator M, the terminal device 10 includes information indicating the wallet ID and information indicating the deposit amount, and creates a prepaid payment means (electronic money) deposit request message addressed to the financial institution 15. To do.
(Step S2-3)
The terminal device 10 transmits the created prepaid payment means (electronic money) payment request message to the financial institution 15.
(Step S3-3)
The financial institution 15 receives the prepaid payment means (electronic money) payment request message transmitted 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 means (electronic money) deposit request message and the information indicating the deposit amount. Perform processing.
(Step S4-3)
The financial institution 15 includes a wallet ID and information indicating a deposit amount, and creates a prepaid payment means (electronic money) deposit completion message addressed to the payment processing device 40.
(Step S5-3)
The financial institution 15 transmits the created prepaid payment means (electronic money) payment completion message to the payment processing device 40.

(Step S6-3)
In the payment processing device 40, the communication unit 41 receives the prepaid payment means (electronic money) payment completion message transmitted by the financial institution 15. The communication unit 41 outputs the received prepaid payment means (electronic money) payment completion message to the reception unit 42. The reception unit 42 acquires the prepaid payment means (electronic money) payment 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.
Based on the wallet ID acquired by the reception unit 42 and the 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 in the wallet corresponding to the wallet ID. judge. The determination unit 47 outputs to the determination unit 44 a determination result of whether or not an amount corresponding to the information indicating the deposit amount has been deposited.
(Step S7-3)
In the payment processing device 40, the determination unit 44 acquires a determination result of whether or not an amount corresponding to the information indicating the deposit amount output by the determination unit 47 has been deposited. When the acquired determination result indicates that the amount corresponding to the information indicating the deposit amount has been deposited, the determination unit 44 uses each of the plurality of card IDs for the acquired wallet ID in the user information DB 49a. Determine the possible amount.
(Step S8-3)
In the payment processing device 40, the creation unit 48 acquires a determination result of whether or not an 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 means (electronic money) payment response message to the terminal device 10 including the acquired determination result.
(Step S9-3)
In the payment processing device 40, the creation unit 48 outputs the created prepaid payment means (electronic money) payment response message to the communication unit 41. The communication unit 41 acquires the prepaid payment means (electronic money) payment response message output by the creation unit 48. The communication unit 41 transmits the acquired prepaid payment means (electronic money) payment response message to the terminal device 10.
(Step S10-3)
The terminal device 10 receives the prepaid payment means (electronic money) payment response message transmitted by the payment processing device 40.
(Step S11-3)
The terminal device 10 acquires a determination result of whether or not the deposit amount included in the received prepaid payment means (electronic money) deposit response message has been deposited. The terminal device 10 displays a determination result of whether or not the acquired deposit amount has been deposited.
According to an example of processing when the administrator M requests a deposit / withdrawal account of a prepaid payment means, a prepaid payment means (electronic money) deposit request message is transmitted 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. Further, by transmitting a prepaid payment means (electronic money) payment 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 of money deposited in the wallet. You can let the amount be decided.

[Operation when user U purchases a product that is billed regularly on a shopping site provided by a member store]
FIG. 10 is a sequence chart showing Example 4 of the operation of the prepaid payment service system according to the present embodiment. FIG. 10 shows Example 1 of processing when the user U purchases a product for which a bill is regularly generated at a shopping site provided by a member store using the card 5.
(Step S1-4)
The terminal device 25 accesses the member store terminal 20 by the operation of one user U who has been issued the card 5. Connection processing is performed between the terminal device 25 and the member store terminal 20.
(Step S2-4)
The terminal device 25 visits the shopping site by the operation of one user U who has been issued the card 5. The user U purchases a product for which a bill is generated on a regular basis. The user U inputs the card number of the card 5 used for payment and the expiration date of the card 5 on the shopping site. The terminal device 25 includes the card number input by the user U and the information indicating the expiration date of the card 5, and creates a periodic payment application message addressed to the member store terminal 20.
(Step S3-4)
The terminal device 25 transmits the created periodic payment application message to the member store terminal 20.
(Step S4-4)
The member store terminal 20 receives the periodic payment application message transmitted by the terminal device 25. The member store terminal 20 acquires the card number included in the received periodic payment application message and the information indicating the expiration date of the card 5. The member store terminal 20 includes the acquired card number and information indicating the expiration date of the card 5, and creates a periodic payment request message addressed to the management device 30.
(Step S5-4)
The member store terminal 20 transmits the created periodic payment request message to the management device 30.
(Step S6-4)
In the management device 30, the communication unit 31 receives the periodic payment request message transmitted by the member store terminal 20. The communication unit 31 outputs the received periodic payment request message to the reception unit 32. The reception unit 32 receives the periodic payment request message output by the communication unit 31. The reception unit 32 acquires the card number included in the received periodic payment request message and the information indicating the expiration date of the card 5. The reception unit 32 outputs the acquired card number and information indicating the expiration date of the card 5 to the determination unit 37.
The determination unit 37 acquires the card number output by the reception unit 32 and the information indicating the expiration date of the card 5. 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 the expiration date based on the acquired expiration date.
(Step S7-4)
In the management device 30, the determination unit 37 outputs the card number and the determination result of whether or not the card 5 is within the expiration date to the creation unit 48. The creation unit 48 acquires the card number output by the determination unit 37 and the determination result of whether or not the card 5 is within the expiration date. The creation unit 48 creates a periodic payment request response message addressed to the member store terminal 20, including the card number and the determination result of whether or not the card 5 is within the expiration date.

(Step S8-4)
In the management device 30, the creation unit 48 outputs the created periodic payment request response message to the communication unit 31. The communication unit 31 acquires the periodic payment request response message output by the creation unit 48. The communication unit 31 transmits the acquired periodic payment request response message to the member store terminal 20.
(Step S9-4)
The member store terminal 20 receives the periodic payment request response message transmitted by the management device 30. The member store terminal 20 acquires the card number included in the received periodic payment request response message and the determination result of whether or not the card 5 is within the expiration date. When the member store terminal 20 acquires information indicating that the card 5 is within the expiration date, the member store terminal 20 creates billing identification information, and the user U purchases the created billing identification information on a regular basis. Associate (link) with the product to be used. The member store terminal 20 stores the product identification information, the card number, the created billing identification information, and the billing date and time in association with each other in the periodic billing DB.
(Step S10-4)
The member store terminal 20 includes information indicating that the acquired periodic payment application is possible and information indicating that the periodic payment application is not possible, and destinations the terminal device 25. Create a recurring payment application response message.
(Step S11-4)
The member store terminal 20 transmits the created periodic payment application response message to the terminal device 25.
(Step S12-4)
The terminal device 25 receives the periodic payment application response message transmitted by the member store terminal 20.
(Step S13-4)
The terminal device 25 acquires either information indicating that the periodic payment application is possible or information indicating that the periodic payment application is not possible, which is included in the received periodic payment application response message. .. The terminal device 25 displays information on either one of the acquired information indicating that the periodic payment application is possible and the information indicating that the periodic payment application is not possible.
According to Example 1 of processing when the user U uses the card 5 to purchase a product for which a bill is periodically generated at a shopping site provided by a member store, the member store terminal is displayed from the terminal device 10. By sending the regular payment application message to 20, it is possible to apply for regular payment to the member store terminal 20 when purchasing a product for which billing occurs on a regular basis.
The member store terminal 20 inquires the management device 30 whether or not the card 5 is valid based on the application for regular payment from the user U. Based on the result of the inquiry, the member store terminal 20 creates billing identification information when the card 5 is within the expiration date, and the user U purchases the created billing identification information on a regular basis. Associate (link) with the product to be used. The member store terminal 20 stores the product identification information, the card number, the created billing identification information, and the billing date and time in association with each other in the periodic billing DB. With this configuration, the member store terminal 20 can make a periodic bill when the billing date and time arrives.

FIG. 11 is a sequence chart showing Example 5 of the operation of the prepaid payment service system according to the present embodiment. FIG. 11 shows Example 2 of processing when the user U uses the card 5 to purchase a product for which a regular bill is generated at a shopping site provided by a member store. Here, the case where the card 5 is set to be usable will be described.
(Step S1-5)
The member store terminal 20 refers to the periodic billing DB, and when the billing date and time arrives, the member store terminal 20 includes a card number stored in association with the billing date and time, information indicating the billing amount, and billing identification information, and manages the billing identification information. Create a periodic billing message addressed to the device 30.
(Step S2-5)
The member store terminal 20 transmits the created periodic billing message to the management device 30.
(Step S3-5)
In the management device 30, the communication unit 31 receives the periodic billing message transmitted by the member store terminal 20. The communication unit 31 outputs the received periodic billing message to the reception unit 32. The reception unit 32 receives the periodic billing message output by the communication unit 31. The reception unit 32 acquires the card number included in the received periodic billing message, the information indicating the billing amount, and the billing identification information. The reception unit 32 outputs the acquired card number, information indicating the billing amount, and billing identification information to the determination unit 37. The determination unit 37 acquires the card number output by the reception unit 32, the information indicating the billing amount, and the billing identification information. 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 the expiration date based on the acquired expiration date.
(Step S4-5)
In the management device 30, when the determination unit 37 determines that the card 5 is not within the expiration date, the determination result of whether or not the card 5 is within the expiration date (here, the card 5 is not within the expiration date). Information indicating) and information indicating the card number are output to the creating unit 38.
The creation unit 38 acquires the determination result of whether or not the card 5 output by the determination unit 37 is within the expiration date, and the information indicating the card number. The creation unit 38 creates a periodic billing response message addressed to the member store terminal 20, including a determination result of whether or not the acquired card 5 is within the expiration date and information indicating the card number.
(Step S5-5)
In the management device 30, the creation unit 38 outputs the created periodic request response message to the communication unit 31. The communication unit 31 transmits the periodic request response message output by the creation unit 38 to the member store terminal 20.

(Step S6-5)
The member store terminal 20 receives the periodic billing response message transmitted by the management device 30.
(Step S7-5)
The member store terminal 20 acquires the determination result of whether or not the card 5 included in the received periodic billing response message is within the expiration date, and the information indicating the card number. The member store terminal 20 displays a determination result of whether or not the acquired card 5 is within the expiration date, and information indicating the card number. As a result, the member store can be made to take action when the card 5 is not within the expiration date.
(Step S8-5)
In the management device 30, when the determination unit 37 determines 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 the 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 S9-5)
In the management device 30, the determination unit 37 acquires the confidential ID output by the conversion unit 36. The determination unit 37 outputs the confidential ID, the information indicating the billing amount, and the billing identification information to the creation unit 38.
The creation unit 38 acquires the confidential ID output by the determination unit 37, the information indicating the billing amount, and the billing identification information. The creation unit 38 creates a payment request message addressed to the payment processing device 40, including the confidential ID, information indicating the billing amount, and billing identification information.
(Step S10-5)
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 S11-5)
In the payment processing device 40, the communication unit 41 receives the payment request message transmitted 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 included in the acquired payment request message, the information indicating the billing amount, and the billing identification information.
(Step S12-5)
In the payment processing device 40, the reception unit 42 outputs the acquired confidential ID, information indicating the billing amount, and billing identification information to the determination unit 47. The determination unit 47 acquires the confidential ID output by the reception unit 42, the information indicating the billing amount, and the billing identification information. The determination unit 47 acquires the card ID stored in association with the acquired confidential ID, the information indicating the usage limit amount, the information indicating the availability, and the information indicating the available amount from the user information DB 49a. To do. The determination unit 47 acquires the slip identification information stored in association with the acquired confidential ID from the deposit DB 49b. The determination unit 47 determines whether or not the acquired information indicating availability is set to be available. Here, the case where the information indicating availability is set to be available will be described. The determination unit 47 determines whether or not the slip identification information acquired from the deposit DB 49b includes the bill identification information (corresponding to the bill identification information).
(Step S13-5)
In the settlement processing device 40, when the determination unit 47 determines that the slip identification information acquired from the deposit DB 49b includes the information corresponding to the billing identification information, the determination unit 47 associates the information corresponding to the billing identification information with the slip identification information. Information indicating the deposit amount stored in the deposit DB49b is acquired from the deposit DB49b. The determination unit 47 outputs the card ID, the information indicating the billed amount, and the information indicating the guaranteed amount to the processing unit 43.
The processing unit 43 acquires the card ID output by the determination unit 47, the information indicating the billing amount, and the information indicating the guaranteed amount. The processing unit 43 updates the available amount by adding the acquired guarantee amount to the available amount stored in association with the acquired card ID in the user information DB 49a.
(Step S14-5)
In the payment processing device 40, the processing unit 43 outputs the information indicating that the available amount has been updated to the determination unit 47 after updating the available amount.
The determination unit 47 acquires information indicating that the available amount output by the processing unit 43 has been updated. When the determination unit 47 acquires the information indicating that the available amount output by the processing unit 43 has been updated, the billing amount can be used based on the information indicating the billing amount and the information indicating the available amount. Determine if it is less than or equal to the amount. Here, the case where the determination unit 47 determines that the billed amount is equal to or less than the available amount will be described.
When the determination unit 47 determines that the invoice amount is less than or equal to the available amount, the determination unit 47 creates a settlement request including the card ID, the invoice identification information, and the information indicating the invoice amount. The determination unit 47 outputs the created settlement request to the settlement unit 45.
The settlement unit 45 acquires the settlement request output by the determination unit 47. The settlement unit 45 acquires the card ID included in the acquired settlement request, the billing identification information, and the information indicating the billing amount. The settlement unit 45 performs settlement processing based on the acquired card ID and information indicating the billing amount. The settlement unit 45 reduces the billing amount of the user information DB 49a from the amount deposited in the wallet corresponding to the wallet ID associated with the card ID. The determination unit 44 updates the available amount associated with the card ID by reducing the billed amount.
Further, the determination unit 44 determines the usable amount of the wallet ID when 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. As, determine and memorize the amount deposited in the wallet. When the usage limit set for 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 determination unit 44 uses the wallet ID as the available amount. Determine and memorize limits. Here, as for the usage limit associated with the card ID included in the payment request, the billed amount is reduced. Further, as for the available amount associated with the card ID of the used card, the amount in which the billing amount is reduced is used.

(Step S15-5)
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 output by the payment unit 45 and the payment result. The creation unit 48 acquires the 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 to the management device 30 including the acquired confidential ID and the payment result.
(Step S16-5)
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 S17-5)
In the management device 30, the communication unit 31 receives the payment response message transmitted 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 the card number stored in association with the acquired confidential ID from the card DB 39a. The creation unit 38 creates a periodic billing response message addressed to the member store terminal 20 including the acquired card number and the payment result.
(Step S18-5)
In the management device 30, the creation unit 38 outputs the created periodic request response message to the communication unit 31. The communication unit 31 acquires the periodic request response message output by the creation unit 38. The communication unit 31 transmits the acquired periodic billing response message to the member store terminal 20.
(Step S19-5)
The member store terminal 20 receives the periodic billing response message transmitted by the management device 30.
(Step S20-5)
The member store terminal 20 acquires the card number included in the received withdrawal periodic billing response message and the payment result. The member store terminal 20 displays the acquired card number and the payment result. This allows the merchant to be informed that the payment was successful.
(Step S21-5)
In the settlement processing device 40, when the determination unit 47 determines that the slip identification information acquired from the deposit DB 49b does not include the bill identification information, the determination unit 47 indicates the information indicating the billing amount and the available amount. Based on the information, it is determined whether the billed amount is less than or equal to the available amount. Hereinafter, the determination unit 47 will continue to explain the case where the billed amount is equal to or less than the available amount. When the determination unit 47 determines that the invoice amount is less than or equal to the available amount, the determination unit 47 creates a settlement request including the card ID, the invoice identification information, and the information indicating the invoice amount. The determination unit 47 outputs the created settlement request to the settlement unit 45.
The settlement unit 45 acquires the settlement request output by the determination unit 47. The settlement unit 45 acquires the card ID included in the acquired settlement request, the billing identification information, and the information indicating the billing amount. The settlement unit 45 performs settlement processing based on the acquired card ID and information indicating the billing amount. The settlement unit 45 reduces the billing amount of the user information DB 49a from the amount deposited in the wallet corresponding to the wallet ID associated with the card ID. The determination unit 44 updates the available amount associated with the card ID by reducing the billed amount.
Further, the determination unit 44 determines the usable amount of the wallet ID when 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. As, determine and memorize the amount deposited in the wallet. When the usage limit set for 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 determination unit 44 uses the wallet ID as the available amount. Determine and memorize limits. Here, as for the usage limit associated with the card ID included in the payment request, the billed amount is reduced. Further, as for the available amount associated with the card ID of the used card, the amount in which the billing amount is reduced is used. After that, the processing of steps S15-5 to S16-5 and the processing of steps S22-5 are performed.

(Step S22-5)
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 output by the payment unit 45 and the payment result. The creation unit 48 acquires the confidential ID stored in association with the acquired card ID from the user information DB 49a. The creation unit 48 creates the slip identification information, and associates the created slip identification information with the acquired confidential ID and the billing identification information. The creation unit 48 associates the confidential ID with the created slip identification information and stores it in the deposit DB 49b.
(Step S23-5)
In the payment processing device 40, the payment unit 45 outputs the card ID, the billing identification information, and the information indicating the billing amount to the determination unit 44.
The determination unit 44 acquires the card ID output by the settlement unit 45, the billing identification information, and the information indicating the billing amount. The determination unit 44 determines by deriving the guarantee amount based on the information indicating the acquired billing amount.
(Step S24-5)
In the payment processing device 40, the determination unit 44 outputs the card ID, the billing identification information, and the information indicating the determined guarantee amount to the processing unit 43.
The processing unit 43 acquires the card ID output by the determination unit 44, the billing identification information, and the information indicating the guaranteed amount. The processing unit 43 acquires information indicating the available amount of money stored in association with the card ID from the user information DB 49a. The processing unit 43 determines whether or not the guaranteed amount is equal to or less than the available amount based on the acquired information indicating the guaranteed amount and the information indicating the available amount.
(Step S25-5)
In the payment processing device 40, when the guaranteed amount is less than or equal to the available amount, the processing unit 43 updates the available amount by subtracting the guaranteed amount from the available amount.
(Step S26-5)
In the payment processing device 40, the processing unit 43 acquires the confidential ID stored in association with the card ID from the user information DB 49a. The processing unit 43 acquires the confidential ID stored in association with the card ID from the user information DB 49a. The processing unit 43 associates the acquired confidential ID, the created slip identification information, and the information indicating the guarantee amount acquired from the determination unit 44, and stores it in the deposit DB 49b.
(Step S27-5)
In the payment processing device 40, when the guaranteed amount is higher than the available amount, the processing unit 43 identifies the wallet ID stored in association with the acquired card ID in the user information DB 49a. The processing unit 43 freezes the wallet by disabling the availability associated with the specified wallet ID.

(Step S28-5)
In the payment processing device 40, the processing unit 43 outputs the card ID and the information indicating that the wallet has been frozen to the creating unit 48. The creation unit 48 acquires the card ID output by the processing unit 43 and the information indicating that the wallet has been frozen. The creation unit 48 acquires the notification destination stored in association with the acquired card ID from the notification destination information DB 49c. The creation unit 48 creates a deposit request message to the notification destination, including information indicating that the wallet has been frozen, based on the information indicating that the acquired wallet has been frozen and the information indicating the notification destination. ..
(Step S29-5)
In the payment processing device 40, the creation unit 48 transmits the created payment request message to the communication unit 41.
The communication unit 41 acquires the payment request message output by the creation unit 48. The communication unit 41 transmits the acquired payment request message to the notification destination.
According to Example 2 of processing when the user U uses the card 5 to purchase a product for which a bill is regularly generated at a shopping site provided by the member store, the member store terminal 20 has a billing date and time. Can be billed on a regular basis when
The payment processing device 40 determines a guarantee amount for each user U of the plurality of cards to guarantee payment for a bill generated periodically by applying for a product with the card. The payment processing device 40 determines the available amount of each user U of the plurality of cards based on the result of subtracting the determined guarantee amount from the balance of the wallet commonly used by each of the plurality of cards. decide. When the available amount cannot be secured, the payment processing device 40 freezes by restricting the use of the wallet. With this configuration, when a claim is incurred, the deposit included in the balance of the prepaid payment instrument can be used to pay for the claim, so that the prepaid payment instrument can be used to pay for claims that occur on a regular basis. Can be used. Therefore, the convenience of the payment type payment means can be improved.

In the above-described embodiment, the case of a prepaid card, a credit card, and a virtual card has been described as an example of the payment tool, but the present invention is not limited to this example. For example, it may be a display device that displays a card number.
In the above-described embodiment, as an example, a case where the user U makes a purchase at an EC (electronic transaction) site has been described, but the present invention is not limited to this example. For example, it can be applied to the case where the user U makes a purchase at a member store.
In the above-described embodiment, the management device 30 and the payment processing device 40 have been 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 above-described embodiment, the case where the card number is converted into the confidential ID by the management device 30 and the confidential ID is converted into the card ID by the payment processing device 40 has been described, but the present invention is not limited to this example. For example, the management device 30 may perform processing with the card number without converting the card number into a confidential ID. Further, the payment processing device 40 may perform the processing with the confidential ID without converting the confidential ID into the card ID.
In the above-described embodiment, regarding the usage limit for each card, as an example of a predetermined period, an arbitrary period such as daily, weekly, monthly, quarterly, semiannual, yearly, semiannual, etc. has been described. Not limited to this example. For example, it may be the amount of payment per payment or the total amount.

In the above-described embodiment, the processing unit 43 sets the usage limit of each of the plurality of payment tools, and the determination unit 44 sets the total amount of the advance payment paid to the deposit / withdrawal account of the prepaid payment means. Although the case where 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 has been described, the present invention is not limited to this example. For example, the determination unit 44 may determine the available amount of each of the plurality of payment tools based on the total amount of advance payments paid to the deposit / withdrawal account of the prepaid payment instrument.
For example, the determination unit 44 may determine the available amount of each of the plurality of payment tools to be the same as the total amount of the advance payments paid to the deposit / withdrawal account of the advance payment means, or the advance payment type. It may be set to be lower than the total amount of advance payments paid to the deposit / withdrawal account of the payment method. For example, the determination 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 the advance payments paid to the deposit / withdrawal account of the prepaid payment means. Alternatively, the amount may be set by subtracting a predetermined amount.
In this case, if any of the plurality of payment tools is used to withdraw from the total amount of the advance payment, the determination unit 44 may use a plurality of determination units 44 based on the total amount after the withdrawal. Update the available amount of each of the payment tools of, by configuring in this way, the total amount of advance payments paid to the deposit / withdrawal account of the prepaid payment instrument and multiple payments set by the processing unit 43. Since the process of determining the available amount of each of the plurality of payment tools based on the usage limit of each tool can be omitted, the process can be simplified.
In the above-described embodiment, the determination unit 47 of the payment processing device 40 acquires the confidential ID included in the payment request message, the billing identification information, and the information indicating the billing amount. The determination unit 47 determines whether or not the information indicating availability, which is stored in association with the acquired confidential ID, is set to be available. After that, when the information indicating availability is set to be available, the determination unit 47 acquires the guarantee amount stored in association with the slip identification information corresponding to the billing identification information, and obtains the acquired guarantee amount. Update by adding to the available amount. The determination unit 47 has described a case where it is determined whether or not the invoiced amount is less than or equal to the available amount based on the information indicating the invoiced amount and the updated information indicating the available amount, but this is limited to this example. Absent.
For example, the determination unit 47 determines whether or not the information indicating availability is set to be available, and the information indicating the available amount updated by adding the acquired guarantee amount to the available amount. Based on the above, the process of determining whether or not the billed amount is less than or equal to the available amount may be executed in any order, or may be executed at the same time.
In the above-described embodiment, the guarantee amount stored in association with the slip identification information corresponding to the billing identification information is acquired, updated by adding the acquired guarantee amount to the available amount, and the information indicating the billing amount is obtained. The case of determining whether or not the billed amount is less than or equal to the available amount based on the updated information indicating the available amount has been described, but the present invention is not limited to this example. For example, it may be determined whether or not the billed amount is equal to or less than the guaranteed amount. In this case, if the billed amount is higher than the guaranteed amount, the difference may be paid from the available amount.
In the above-described embodiment, the case where the guarantee amount is updated based on the previous billing amount has been described, but the present invention is not limited to this example. For example, the guarantee amount may be updated based on a plurality of past billed amounts. For example, it may be the average of a plurality of past billed amounts, the maximum amount, or an intermediate value.
In the above-described embodiment, either one or both of the card DB 39a and the user information DB 49a may be a relational database. In this case, either one or both of the card DB 39a and the user information DB 49a is represented by a plurality of tables. For example, as an example, the card DB39a can be represented by a table in which the card number and the confidential ID are associated with each other and a table in which the card number and the confidential ID are associated with each other. Further, for example, in the user information DB 49a, a table in which the confidential ID and the card ID are associated, a table in which the card ID, the usage limit, and availability are associated, and the card ID and the wallet ID are associated with each other. It can be represented by a table and a table in which the wallet ID and the available amount are associated with each other.

According to the prepaid payment service system 1 according to the present embodiment, the payment processing device 40 guarantees payment for one or more bills that are periodically generated by being applied for by each of the plurality of payment tools. Based on the amount obtained by subtracting the guarantee amount from the total amount of the advance payment paid to the deposit / withdrawal account of the prepaid payment method and the processing unit 43 that sets the guarantee amount of the above, each of the plurality of payment tools. It is provided with a determination unit 44 that determines the available amount.
Multiple prepaid payment instruments based on the total amount of down payments paid to the deposit / withdrawal account minus the guaranteed amount to guarantee payment for one or more bills that occur on a regular basis. The amount available for each payment tool is determined. If one of the multiple payment tools is used and the total amount of the advance payment is deducted, the available amount will decrease, but the guarantee amount will not decrease, so it will occur regularly. You can secure the amount to be paid for the bill you make. Therefore, the convenience of the prepaid payment means can be improved.
Further, a reception unit 42 for receiving a periodic billing message generated periodically and a settlement unit 45 for performing settlement processing are provided, and the processing unit 43 associates each of one or a plurality of slip identification information with the guarantee amount information. From the storage unit to be stored, the guarantee amount information stored in association with the slip identification information corresponding to the billing identification information included in the periodic billing message received by the reception unit 42 is acquired, and the settlement unit 45 is the processing unit 43. Settle the billing amount included in the periodic billing message based on the guarantee amount corresponding to the acquired guarantee amount information. By configuring in this way, the billing amount included in the periodic billing message is based on the guarantee amount corresponding to the guarantee amount information stored in association with the slip identification information corresponding to the billing identification information included in the periodic billing message. Can be settled.
Further, the processing unit 43 increases the available amount based on the guarantee amount information, and the settlement unit 45 setstles the billing amount included in the periodic billing message based on the available amount increased by the processing unit 43. To do. With this configuration, the billing amount included in the periodic billing message can be settled based on the available amount updated by adding the guarantee amount to the available amount.
Further, the determination unit 44 determines the guarantee amount based on the billing amount, and the processing unit 43 determines the available amount of the payment tool used and the storage unit 49 based on the billing amount determined by the determination unit 44. Update the guarantee amount information associated with the slip identification information stored in. With this configuration, the guarantee amount can be updated based on the past billed amount.
Further, the processing unit 43 updates by subtracting the guarantee amount determined by the determination unit 44 from the available amount of the used payment tool, and is associated with the slip identification information stored in the storage unit 49. The guarantee amount information is updated with the guarantee amount determined by the determination unit 44. With this configuration, the available amount of the payment tool used and the guarantee amount information associated with the slip identification information can be updated with the determined guarantee amount.
Further, when the guarantee amount associated with the slip identification information stored in the storage unit 49 is higher than the available amount of the payment tool used, the processing unit 43 uses each of the plurality of payment tools. Restrict. With such a configuration, it is possible to urge the administrator M to respond to payment and the like.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included.
For example, a computer program for realizing the functions of the above-described devices may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by the computer system and executed. The "computer system" referred to here may include hardware such as an OS and peripheral devices.
The "computer-readable recording medium" is a writable non-volatile memory such as a flexible disk, a magneto-optical disk, a ROM, or a flash memory, a portable medium such as a DVD (Digital Versatile Disc), or a built-in computer system. A storage device such as a hard disk.
Furthermore, the "computer-readable recording medium" is a volatile memory inside a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line (for example, DRAM (Dynamic)). It also includes those that hold the program for a certain period of time, such as Random Access Memory)).
Further, the program may be transmitted from a computer system in which this program is stored in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting a program refers to a medium having 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.
Further, the above program may be for realizing a part of the above-mentioned functions.
Further, a so-called difference file (difference program) may be used, which can realize the above-mentioned functions in combination with a program already recorded in the computer system.

1 ... Prepaid payment service system, 5 ... Card, 10 ... Terminal device, 15 ... Financial institution, 20 ... Merchant terminal, 25 ... Terminal device, 30 ... Management device, 31 ... Communication department, 32 ... Reception department, 35 ... Setting unit, 36 ... Conversion unit, 37 ... Judgment unit, 38 ... Creation unit, 39 ... Storage unit, 39a ... Card DB, 40 ... Payment processing device, 41 ... Communication unit, 42 ... Reception unit, 43 ... Processing unit, 44 ... decision unit, 45 ... settlement unit, 47 ... judgment unit, 48 ... creation unit, 49 ... storage unit, 49a ... user information DB, 49b ... deposit DB, 49c ... notification destination DB

Claims (8)

A processing unit that sets a guarantee amount to guarantee payment for one or more bills that occur regularly by applying for each of multiple payment tools,
It is provided with a determination unit that determines the available amount of each of the plurality of payment tools based on the amount obtained by subtracting the guarantee amount from the total amount of the advance payment paid to the deposit / withdrawal account of the prepaid payment method. , Prepaid payment service system. The reception department that accepts regular billing messages that occur regularly,
Equipped with a payment department that handles payment processing
The processing unit stores the voucher identification information corresponding to the billing identification information included in the periodic billing message received by the reception unit from the storage unit that stores each of the one or a plurality of slip identification information in association with the guarantee amount information. Get the guaranteed amount information stored in association with
The prepaid settlement service system according to claim 1, wherein the settlement unit settles the billing amount included in the periodic billing message based on the guarantee amount corresponding to the guarantee amount information acquired by the processing unit. The processing unit increases the available amount based on the guarantee amount information.
The prepaid settlement service system according to claim 2, wherein the settlement unit settles the billing amount included in the periodic billing message based on the available amount increased by the processing unit. The determination unit determines the guarantee amount based on the invoiced amount.
The processing unit has the available amount of the payment tool used and the guaranteed amount information associated with the slip identification information stored in the storage unit based on the billing amount determined by the determination unit. The prepaid payment service system according to claim 2 or 3, which updates and. The processing unit is updated by subtracting the guaranteed amount determined by the determination unit from the available amount of the payment tool used, and is associated with the slip identification information stored in the storage unit. The prepaid payment service system according to claim 4, wherein the guarantee amount information is updated with the guarantee amount determined by the determination unit. The processing unit uses each of the plurality of payment tools when the guarantee amount associated with the slip identification information stored in the storage unit is higher than the available amount of the payment tool used. The prepaid payment service system according to claim 4, which limits the number of payments. A prepaid payment processing method performed by a prepaid payment service system equipped with a processor.
Steps to set a guarantee amount to guarantee payment for one or more bills that occur on a regular basis by applying for each of multiple payment tools,
A prepayment with the step of determining the available amount of each of the multiple payment tools based on the total amount of prepayments paid to the deposit / withdrawal account of the prepayment payment instrument minus the guarantee amount. Formula payment processing method. On the computer
Steps to set a guarantee amount to guarantee payment for one or more bills that occur on a regular basis by applying for each of multiple payment tools,
Perform the steps of determining the available amount of each of the multiple payment tools based on the total amount of advance payments paid to the deposit / withdrawal account of the prepaid payment instrument minus the guarantee amount. ,program.

Images