JP2016200939A - Management system, management method, and program for prepaid card - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a prepaid card management system, management method, and program for issuing a prepaid card to a recipient of public payment such as livelihood protection expenses, and for managing the information.SOLUTION: A prepaid card management system 100 includes: a card company system 105; and a card management center system 107. The card company system 105 include: means for receiving one or more recipient files including recipient information of public payment; and means for creating a card batch issue request file on the basis of one or more recipient files, and for uploading the card batch issue request file to the card management center system 107. The card management center system 107 includes means for registering the prepaid cards of recipients in a batch on the basis of the card batch issue request file.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a prepaid card management system, management method, and program. More specifically, for example, a prepaid card is issued to a beneficiary of public benefits such as welfare expenses and the information is managed. The present invention relates to a prepaid card management system, a management method, and a program.

  The welfare system is to protect people who are still in need of life even if they use all their assets and abilities, according to their degree of need, and to guarantee a healthy and cultural minimum life, It is a system that promotes that independence. In view of the purpose of the system, the government (directly local governments) pays welfare costs according to the requirements for welfare and the content of welfare.

  There are eight types of welfare expenses (life assistance, housing assistance, educational assistance, medical assistance, nursing assistance, childbirth assistance, livelihood assistance, funeral service assistance). It is intended. As for the composition of the recipients, a single elderly person occupies the majority, and the number of protected persons who need various life support services is increasing. In addition, the Livelihood Protection Law has been revised (enacted in December 2013), and it is the responsibility of the recipient to properly grasp the status of income, expenditure and other livelihoods.

  However, in the past, public benefits such as welfare costs have been provided by bank transfer or cash delivery, and the beneficiary can withdraw cash from the account or perform a receipt procedure at the counter for each monthly benefit. I had to do it. Such work has also been a burden for the public benefit payer.

  Furthermore, the beneficiary is responsible for properly understanding the status of livelihood, such as income and expenditure, but currently the recipient has no choice but to create a household account book, etc. The local government that is the supplier was not able to grasp the actual usage of living assistance expenses.

  The present invention has been made in view of such problems. The purpose of the present invention is to issue a prepaid card in a lump sum to a beneficiary of public benefits such as welfare expenses and pay monthly benefits. It is an object to provide a prepaid card management system, a management method, and a program for charging and paying at least a part (for example, a part of life assistance expenses) to a prepaid card in a lump.

  In order to achieve such an object, a prepaid card management system according to an embodiment of the present invention includes a card company system and a card management center system. In the card company system, information on recipients of public benefits is provided. Means for receiving one or more recipient files, means for creating a card batch issuance request file based on the one or more recipient files, and uploading it to the card management center system; and card management center system And a means for collectively registering the prepaid card of the recipient based on the card batch issue request file.

  The prepaid card management system according to an embodiment of the present invention is a card company system that creates a balance batch charge request file based on a means for receiving a deposit data file for a prepaid card of a recipient and a deposit data file. And a means for uploading to the card management center system, and a means for collectively registering the balance of the prepaid card of the recipient based on the balance batch charge request file in the card management center system.

  Further, the prepaid card management system according to an embodiment of the present invention creates a member information batch update request file based on the attribute change file and the means for receiving the attribute change file of the recipient in the card company system, It further comprises means for uploading to the card management center system, and means for collectively updating the recipient's member information based on the member information batch update request file in the card management center.

  The prepaid card management system according to an embodiment of the present invention creates a partner return file based on the membership information of the recipient or the transaction history information of the recipient in the card management center system, and transmits the file to the card company system. And means for downloading the partner return file and transmitting it to the local government system.

  As described above, according to the present invention, it is possible to reduce the burden on both the recipient and the recipient when paying welfare expenses. In addition, it becomes possible for the supply person to grasp the usage record such as welfare expenses.

It is a block diagram of the prepaid card management system which concerns on one Embodiment of this invention. It is a functional block diagram of the prepaid card management system concerning one embodiment of the present invention. It is a flowchart of the card issue process which concerns on one Embodiment of this invention. It is a flowchart of the balance charge process which concerns on one Embodiment of this invention. It is a flowchart of the card reissue process which concerns on one Embodiment of this invention. It is a flowchart of the attribute change process which concerns on one Embodiment of this invention. It is a flowchart of the attribute batch change process which concerns on one Embodiment of this invention. It is a flowchart of the withdrawal process which concerns on one Embodiment of this invention. It is a flowchart of the partner return file download process which concerns on one Embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In addition, the same code | symbol represents the same thing in several drawing, and the repeated description is abbreviate | omitted.

  FIG. 1 shows an overall configuration of a prepaid card management system 100 according to an embodiment of the present invention. The prepaid card management system 100 includes a local government system 101, a card company system 105, a card management center system 107, and a printing company system 109. The local government system 101, the card company system 105, the card management center system 107, and the printing company system 109 are generally composed of a plurality of operation terminals and servers.

  The local government system 101 is a system on the local government side that operates the welfare system. Specifically, the local government system 101 accepts applications for public benefits such as welfare expenses and registers the applicant as a recipient of public benefits. For the local government computer system. Information of the recipient registered in the local government system 101 is transmitted to the card company system 105 via the network 103 such as the Internet or a dedicated network. In addition to the recipient registration, information such as prepaid card balance charge, prepaid card reissue, change of recipient attribute information, prepaid card cancellation, etc. is also transmitted from the municipality system 101 to the card company system 105. .

  The card company system 105 transmits / receives a data file to / from the card management center system 107 based on the information received from the local government system 101. In addition to file transmission / reception, the card management center system 107 may be directly accessed via the administrator web screen so that data can be registered and referenced. When the card company system 105 receives transaction information such as authorization data and sales data when using the prepaid card from the partner store terminal 111 or the shopping website 112, the card company system 105 transmits it to the card management center system 107.

  The card management center system 107 stores prepaid card member information and charge balance information. Further, the card management center system 107 transmits card issuance information and reissue information to the printing company system 109. Further, when a prepaid card is used in the partner store terminal 111 or the shopping website 112, the card management center system 107 receives transaction information via the card company system 105, updates the balance information DB 232, The history is stored in the transaction information DB 233. As described above, the prepaid card according to the present invention is a server-managed prepaid card, and information such as a charge balance is managed not by the prepaid card itself but by the server of the card management center system 107. Information stored in the card itself in the server-managed prepaid card basically needs only the identification information (ID) of the card itself. In order to use the server-managed prepaid card at a store or shopping site, it is necessary to communicate with the card management center system 107.

  When the printing company system 109 receives card issuance information and reissue information from the card management center system 107, the printing company creates a prepaid card in which the card information is recorded and delivers it to the local government. The created prepaid card is distributed to the recipient at the local government office.

  The partner store terminal 111 is a terminal installed in a partner store where a recipient can use a prepaid card, and exchanges transaction information with the card company system 105. A prepaid card can also be used at a shopping website 112 operated by a partner store or the like. In general, the prepaid card is authenticated by the card number, expiration date, security code, etc. of the prepaid card entered on the shopping website by the recipient, and transaction information is exchanged with the card company system 105.

  The operation terminal and server of the system described above can be configured by one or a plurality of computers, and are not limited to a specific hardware configuration or software program. Further, the operation terminal can be a workstation, a personal computer, a mobile phone, a smartphone, a tablet terminal, or the like.

  The overall configuration of the prepaid card management system 100 according to the embodiment of the present invention has been described above, but the system configuration capable of implementing the present invention is not limited to this.

  Next, a functional configuration of the prepaid card management system according to the embodiment of the present invention will be described with reference to FIG. Each function described below is realized by a computer processing device (CPU) reading and executing a computer program stored in a storage device or memory of a computer constituting the prepaid card management system.

  The local government system 101 includes a registration unit 201, a file generation unit 203, a file transmission unit 205, and a file reception unit 207. The registration unit 201 is input by the person in charge of the local government, information on the recipient who newly issues the prepaid card, payment data to be charged to the prepaid card, reissue request for prepaid, member attribute change, cancellation of prepaid card, etc. Is registered and stored in the local government system 101. The file generation unit 203 generates various files based on the contents registered in the local government system 101. The file transmission unit 205 transmits various files generated by the file generation unit 203 to the card company system 105. The file receiving unit 207 receives the file transmitted from the card company system 105 and stores it in the local government system 101. The local government system 101 can check the data held in the card management center by referring to the file received from the card company system 105.

  The card company system 105 includes a file reception unit 211, a file generation unit 212, a file upload unit 213, a file download unit 214, a file transmission unit 215, a file inquiry unit 216, a registration unit 217, and a refund processing unit 218.

  The file receiving unit 211 receives and stores various files transmitted from the local government system 101. The file generation unit 212 generates various corresponding files based on the stored various files. The file upload unit 213 uploads various files generated to the card management center system 107. The file download unit 214 downloads a file from the card management center system 107 and stores it in the card company system 105. The file transmission unit 215 transmits the file received from the card management center system 107 to the local government system 101. The file inquiry unit 216 makes it possible to refer to data stored in the card management center system 107. The registration unit 217 registers data input by a card company representative in the card management center system 107. For example, the file generated by the file generation unit 212 is generated in order to register a large amount of data received from the local government system 101 and uploaded to the card management center system 107 by the file upload unit 213. The unit 217 is used for individually registering data with a low occurrence frequency in the card management center system 107. Access to the card management center system 107 may be performed via an administrator web screen. The refund processing unit 218 performs a refund process for those who have left the prepaid card balance.

  The card management center system 107 includes a file fetch unit 221, a card batch issue processor 222, a balance batch charge processor 223, a member information update processor 224, a member information batch update processor 225, a withdrawal processor 226, and a partner return A file creation processing unit 227, a member website providing unit 228, a member information database (DB) 231, a balance information DB 232, and a transaction history DB 233 are provided.

  The file capturing unit 221 captures and stores various files uploaded from the card company system 105. The card collect issuance processing unit 222 registers in the member information DB 231 based on the received card collect issuance request file. The balance batch charge processing unit 223 registers the charge balance for each prepaid card in the balance information DB 232 based on the received balance batch charge request file. The member information update processing unit 224 updates the member information DB 231 based on individual member attribute change data registered from the card company system 105. The member information batch update processing unit 225 updates the member information DB 231 based on the received member information batch update request file. The withdrawal processing unit 226 updates the member information DB 231 based on withdrawal data registered from the card company system 105. The partner return file processing unit 227 creates various data files based on data registered in various databases of the card management center system. The website providing unit 228 for members allows a member of a prepaid card to display his / her usage status and registration information based on data stored in the member information DB 231, balance information DB 232, and transaction history DB 233. I will provide a.

  The functional configuration of the prepaid card management system according to one embodiment of the present invention has been described above, but the functional configuration of the prepaid card system is not limited to this, and may include other functional components.

  Next, with reference to FIG. 3, the prepaid card issuance process according to an embodiment of the present invention will be described. The processing flow shown in FIG. 3 is executed by the local government system 101, the card company system 105, the card management center system 107, and the printing company system 109.

  First, in step 301, upon accepting an application for assistance for welfare at a local government office, the person in charge examines the welfare requirements and the contents of welfare, and inputs the examination result to the operation terminal. In step 302, the local government system 101 registers the information of the recipients who satisfy the requirements and the contents of the welfare, and creates a recipient file from the registered recipient information. In step 303, the created recipient file is transmitted to the card company system 105. Creation and transmission of the recipient file may be performed every time the recipient is registered, or may be periodically performed on a predetermined date.

  In step 304, the card company system 105 receives and stores one or more beneficiary files. Next, in step 305, the card company system 105 generates a card batch issue request file including the recipient information based on the stored recipient file. The card collect issuance request file includes a plurality of recipient information and is a file for requesting issuance of a plurality of prepaid cards in a lump. By issuing a plurality of prepaid card issuance requests in a lump, the processing load can be reduced as compared with individual recipient information exchange. In step 306, the generated card batch issue request file is uploaded to the card management center system 107.

  In step 307, the card management center system 107 takes in the card batch issue request file uploaded from the card company system 105. Next, in step 308, the card management center system 107 performs a card batch issuance process and registers the payee's prepaid cards in a batch. Here, member information for newly issuing a prepaid card is registered in the member information DB 231. The card batch issuing process is performed, for example, in a night batch process and batch processed at a time. The registered member information is transmitted to the printing company system 109, and a new prepaid card is created in step 309. When a printing company creates a new prepaid card, it sends it to the local government, and it is paid to the recipient at the local office.

  Next, in step 310, a result file of the card batch issue process is generated. The card collective issue result file is downloaded by the card company system 105 in step 311 and is transmitted from the card company system 105 to the local government system 101 in step 312. In step 313, the local government system 101 receives and stores the card batch issue result file. The person in charge of the local government can verify the batch registration result of the prepaid card by matching the beneficiary file and the card batch issue result file.

  Next, with reference to FIG. 4, a prepaid card balance charge process according to an embodiment of the present invention will be described. The processing flow shown in FIG. 4 is executed by the local government system 101, the card company system 105, and the card management center system 107.

  First, in step 401, the local government system 101 creates a payment data file from the payment data for the prepaid card inputted by the person in charge of the local government, and transmits it to the card company system 105 in step 402. The deposit data is data of benefits such as welfare expenses performed every month, and the amount charged to the prepaid card is transmitted to the card company system 105 as a deposit data file. Payment of benefits is made to many beneficiaries at once. In addition, the local government deposits the charge equivalent amount to the designated account of the card company according to the deposit data.

  Next, when the card company system 105 receives and stores the deposit data file in step 403, it creates a balance batch charge request file in step 404. The balance batch charge request file is a file for requesting a lot of beneficiary's prepaid cards that are generated regularly every month to charge the balance in a batch. By performing the collective balance charge, the processing load can be reduced as compared with the case where the balance charge for each recipient is individually exchanged. In step 405, the created balance batch charge request file is uploaded to the card management center system 107.

  In step 406, the card management center system 107 takes in the balance batch charge request file uploaded from the card company system 105. Next, in step 407, the card management center system 107 performs a balance batch charge process. Here, the balance of each recipient's prepaid card is collectively registered in the balance information DB 232. The balance batch charge process is also performed, for example, in a night batch process and batch processed at a time. In the balance batch charge process, a balance batch charge result file is generated. In step 408, the card company system 105 can refer to the file of the generated balance batch charge result and check the result of the balance batch charge process.

  Next, a prepaid card reissue process according to an embodiment of the present invention will be described with reference to FIG. The processing flow shown in FIG. 5 is executed by the local government system 101, the card company system 105, the card management center system 107, and the printing company system 109.

  First, in step 501, upon receiving a prepaid card reissue request at a local government office, the person in charge inputs a prepaid reissue request using the operation terminal. In step 502, the local government system 101 creates a reissue information file based on the prepaid card reissue information input by the person in charge and transmits it to the card company system 105.

  In step 503, the card company system 105 receives and stores the reissue information file. In step 504, a reissue request is registered in the card management center system 107 based on the stored reissue information file.

  In step 505, the card management center system 107 performs card batch issue processing, and a card reissue request is transmitted to the printing company system 109. In step 506, a prepaid card reissued at the printing company is created and sent to the municipality. The prepaid card reissue process is usually processed individually, but it can also be processed by a card issuance process in the same way as a new card issue process. Information indicating that the card has been reissued may be recorded in the reissued prepaid card.

  Next, with reference to FIG. 6, the attribute change process (individual) of the member information of the prepaid card according to the embodiment of the present invention will be described. The member attribute information may include information useful for grasping the recipient's situation in addition to the address and age. The processing flow shown in FIG. 6 is executed by the local government system 101, the card company system 105, and the card management center system 107.

  First, in step 601, when a member information change request is received at a local government office, the person in charge inputs a member attribute change using the operation terminal. In step 602, the local government system 101 creates an attribute change file based on the attribute information input by the person in charge, and in step 603, transmits the created attribute change file to the card company system 105.

  In step 604, the card company system 105 receives and stores the attribute change file. In step 605, attribute change registration is performed with respect to the card management center system 107 based on the stored attribute change file.

  In step 606, the card management center system 107 performs member information update processing based on the registered attribute information, and updates the member information DB 231. In this way, individual attribute change processing is performed.

  Next, with reference to FIG. 7, a description will be given of attribute pre-payment card attribute change processing for a prepaid card according to an embodiment of the present invention. The processing flow shown in FIG. 7 is executed by the local government system 101, the card company system 105, and the card management center system 107.

  First, in step 701 to step 703, an attribute change request is received, an attribute change file is created, and transmitted to the card company system 105. In step 704, the card company system 105 receives and stores the attribute change file. The processing so far is the same as the processing shown in FIG.

  Next, in step 705, the card company system 105 creates a member information batch update request file. Here, not a member-specific attribute change file, but a file that requests a plurality of attribute changes at once is created. By doing so, it is possible to reduce the processing load rather than exchanging attribute change information individually. For example, when the welfare system is revised and the recipient classification is changed, such information can be changed in a batch.

  Next, in step 706, the card company system 105 uploads the created member information batch change request file to the card management center system 107.

  In step 707, the card management center system 107 takes in the uploaded member information batch change request file, and in step 708, performs member information batch update processing. Here, based on the member information batch update request file, the member information DB 231 is batch updated and a member information batch update result file is created. In step 709, the card company system 105 can refer to the created member information batch update result file, and can confirm the result of the member information batch update process.

  Next, a withdrawal process for a prepaid card according to an embodiment of the present invention will be described with reference to FIG. Withdrawal occurs when the beneficiary stops receiving benefits such as welfare expenses using prepaid cards or is not eligible for welfare. The processing flow shown in FIG. 8 is executed by the local government system 101, the card company system 105, and the card management center system 107.

  First, in step 801, when the cancellation of the prepaid card is accepted at the local government office, the person in charge inputs the cancellation of the prepaid card using the operation terminal. In step 802, the local government system 101 creates a termination file based on the termination information input by the person in charge, and in step 803 transmits the created termination file to the card company system 105.

  In step 804, the card company system 105 receives and stores the cancellation file. In step 805, withdrawal registration is made to the card management center system 107 based on the stored cancellation file.

  In step 806, the card management center system 107 performs withdrawal processing based on the registered withdrawal information, and updates the member information DB 231. Next, in step 807, the card company system 105 performs a refund process. Here, for those who left the balance of the prepaid card, a refund process is performed to a financial institution designated by the local government. In this way, the withdrawal process is performed individually.

  Next, with reference to FIG. 9, a partner return file download process according to an embodiment of the present invention will be described. Here, the partner return file refers to a member information list file and a transaction history information file stored in the card management center system 107. The processing flow shown in FIG. 9 is executed by the local government system 101, the card company system 105, and the card management center system 107.

  First, in step 901, the card management center system 107 performs a partner return file creation process. Here, predetermined information is extracted from the member information DB 231 and the transaction history DB 233 of the card management center system 107, and a partner return file is created.

  In step 902, the partner company return file created by the card company system 105 is downloaded and stored. In step 903, the card company system 105 encrypts the partner return file and transmits it to the local government system 101. In step 904, the local government system 101 combines and stores the received partner return file. In this way, the information stored in the card management center system 107 is provided to the local government system 101.

  The prepaid card management system and management method according to an embodiment of the present invention have been described above. According to the present invention, prepaid card issuance, collective balance charge, and collective attribute change can be performed, and the prepaid card can be managed more easily by the supplier. Accordingly, public benefits such as welfare expenses can be provided using a prepaid card.

  Further, according to the present invention, the beneficiary can pay the balance of the prepaid card charged as a welfare cost, particularly as a living assistance cost, without carrying out cash withdrawal from the account or receiving procedure at the window. You can purchase the necessary goods. Also, the usage status and charge balance of a prepaid card can be confirmed on a member website provided by the card management center system, and a daily usage limit may be set.

  Moreover, even if it is a supply person, a case worker etc. can refer to a utilization condition as needed, and it can utilize for the household support with respect to a receiver, and can also be connected with the economical exploitation prevention by a malicious provider. Also, for the payer, cash delivery and receipt procedures can be reduced, payment to the target person can be speeded up, and administrative efficiency can be improved.

100 Prepaid Card Management System 101 Local Government System 103 Network 105 Card Company System 107 Card Management Center System 109 Printing Company System 111 Partner Store Terminal 112 Shopping Website

Claims (10)

A prepaid card management system comprising a card company system and a card management center system,
Means for receiving one or more beneficiary files including information on beneficiaries of public benefits in the card company system;
In the card company system, based on the one or more recipient files, a card batch issue request file is created and uploaded to the card management center system;
A prepaid card management system comprising: means for collectively registering the payee's prepaid card based on the card batch issue request file in the card management center system. Means for receiving a deposit data file for the prepaid card of the recipient in the card company system;
In the card company system, creating a balance batch charge request file based on the deposit data file, and uploading to the card management center system;
2. The prepaid card management according to claim 1, further comprising means for collectively registering a balance of the payee's prepaid card based on the balance batch charge request file in the card management center system. system. In the card company system, means for receiving the attribute change file of the beneficiary;
In the card company system, based on the attribute change file, a member information batch update request file is created and uploaded to the card management center system;
3. The prepaid card management according to claim 1, further comprising: means for collectively updating member information of the recipient based on the member information batch update request file in the card management center. 4. system. In the card management center system, a means for creating a partner return file based on the member information of the recipient or the transaction history information of the recipient;
The prepaid card management system according to any one of claims 1 to 3, further comprising means for downloading the partner return file and transmitting it to the local government system in the card company system.   5. The card company system according to any one of claims 1 to 4, further comprising a member website providing means for providing member information, balance information, and transaction information of the recipient. The prepaid card management system described.   A program for causing a computer to function as the prepaid card management system according to any one of claims 1 to 5. A method for managing a prepaid card in a prepaid card management system comprising a card company system and a card management center system,
Said card company system receiving one or more beneficiary files containing information on beneficiaries of public benefits;
The card company system creates a card batch issue request file based on the one or more recipient files and uploads it to the card management center system;
The card management center system comprises a step of collectively registering the recipient's prepaid card based on the card batch issue request file. The card company system receiving a deposit data file for the beneficiary's prepaid card;
The card company system creates a balance batch charge request file based on the deposit data file and uploads it to the card management center system;
The method according to claim 7, further comprising the step of: collectively registering a balance of the payee's prepaid card based on the balance batch charge request file. The card company system receiving the beneficiary attribute change file;
The card company system creates a member information batch update request file based on the attribute change file and uploads it to the card management center system;
The method according to claim 7 or 8, further comprising the step of: the card management center collectively updating member information of the recipient based on the member information batch update request file. The card management center system creating a partner return file based on the receiver's member information or the receiver's transaction history information;
The method according to any one of claims 7 to 9, further comprising the step of the card company system downloading the partner return file and transmitting the file to the local government system.

Images