JPWO2013186930A1 - Deposit system - Google Patents

Abstract

[PROBLEMS] To remit money using a conventional bank account or the like, it is difficult to accept remittance for 24 hours, but other remittance methods have a problem that it is difficult to remit safely. In addition, it is difficult to change the usage limit for a conventional credit card, etc. On the other hand, if it is possible to accept deposits and changes to the usage limit on the card freely, there is a problem that the safety of the card is lowered. is there. In order to solve the above problems, the present application enables safe payment by separately having a receipt ID that can be used only for receipt and a consumption use ID that can be used for consumption. Use a card. Furthermore, for the card with the two IDs of the above receipt and consumption use after correctly authenticating the sender so that the remittance for the receipt can be performed safely at a store other than the financial institution. To provide a deposit system capable of depositing and raising the usage limit. [Selection] Figure 2

Description

  The present invention accepts payment after correctly authenticating the depositor at a normal store other than a financial institution, and according to the deposit, safely uses the card usage limit for payment at the time of product purchase. The present invention relates to a technique for enabling appropriate changes.

  Conventionally, in order to change the maximum amount that a withdrawal person can withdraw from, for example, a bank account, it is conceivable to deposit money and increase the balance in the account. If the deposit is for a third party, the sender obtains the recipient's bank account number and sends it to his / her bank account from his / her bank account, Or the method of depositing cash directly to the bank account of the said beneficiary directly to store terminals, such as a cash dispenser, is common.

  On the other hand, even if there is no such deposit, a “credit card” that can be withdrawn freely as long as it is within the limit amount can also be used. For this credit card, an amount that can be used within a predetermined period (usage limit) is set at the time of contract with a credit sales company according to the user's ability to pay, for example. Can be purchased freely by presenting the card at the store or entering the card number at the online shop.

  However, the above-mentioned conventional credit card has a problem that the usage limit amount is fixed to some extent at the time of the contract, so that it is difficult to change the increase of the limit amount or complicated procedures are required. Therefore, Patent Document 1 below discloses a technique for calculating and changing the credit card usage limit amount according to the usage record.

JP 2006-059193 A

  Remittance using a bank account here is difficult due to the operational status of the bank network system, etc., and it is difficult to perform 24 hour remittance reception and immediate reflection of remittance processing (immediate receipt after remittance acceptance). However, there is a problem that it is difficult to transfer money safely.

  Moreover, the change of the usage limit in the credit card is calculated and changed according to the usage record within the predetermined usage limit, and there is a problem that the following cases cannot be handled. In other words, even if the user's money has increased beyond the average income at the time of the credit card contract by receiving remittance from another person, it will be It is not reflected in the usage limit. Therefore, it is difficult to use a credit card that reflects the increase, but on the other hand, if such a card can be received freely and the usage limit can be changed, the card's safety will be reduced. There is.

  In order to solve the above problems, the present application uses a card that enables safe payment by first having a receipt ID that can be used only for receipt and a consumption use ID that can be used for consumption. To do. In addition, for example, the deposit to the card having the two IDs of receipt and consumption after the authentication of the sender is correctly performed so that the deposit can be safely performed at a store other than the financial institution, for example, and To provide a deposit system capable of raising the usage limit.

  Specifically, it is possible to raise the usage limit amount according to the deposit amount associated with the card, and a receipt ID that can be used only for receipt and a consumption use ID that can be used for consumption use. A payment system for a card having a type of ID, and a remittance request information acquisition unit for acquiring remittance request information including information of a remittance ID of one or more cards and a remittance source terminal ID, and the acquired remittance A remittance request information transmitting unit for transmitting request information, an authentication information receiving unit for receiving authentication information for depositor authentication returned in response to the transmission, and an authentication information for outputting the acquired authentication information A remittance source terminal having an output unit, a receiving unit for receiving remittance request information transmitted from the transmitting unit of the remittance source terminal, and generating and holding unique authentication information corresponding to the received remittance request information Authentication information A generating unit, a reply unit that returns the generated authentication information to the remittance source terminal, a transfer receiving unit that receives the transfer of the authentication information output from the authentication information output unit of the remittance source terminal, and transfer reception An authentication unit that obtains an authentication result based on the authentication information and the authentication information that is uniquely associated with the remittance request information of the remittance source terminal, and the authentication result is transferred to the authentication information transfer source A transfer reply unit that replies to the server, an authentication information acquisition unit that acquires authentication information output from the authentication information output unit of the remittance source terminal, and the acquired authentication information to the server A deposit side storefront terminal device having a transfer unit for transferring to the device, an authentication result receiving unit for receiving an authentication result returned in response to the transfer, and an authentication result display unit for displaying the received authentication result; For cards with To provide a payment system.

  Further, in addition to the above-mentioned configuration, the deposit side confirmation information receiving unit that receives the deposit confirmation information that is the confirmation of the deposit made in response to the display of the authentication result in the authentication result display unit, A payment confirmation information transmitting unit that transmits the payment confirmation information received by the payment confirmation information receiving unit to the server device, and the server device transmits the payment confirmation information from the deposit-side in-store terminal device. There is also provided a deposit system for a card having a deposit confirmation information receiving unit for receiving information and a receipt ID transmitting unit for transmitting the received receipt confirmation information in association with the receipt ID of the card.

  Further, in addition to the above configuration, a linking table holding unit that holds a linking table in which a consumption use ID and a payment ID are linked, and a reception ID that is received in association with payment confirmation information from the server device. A card ID management device having a gold ID receiving unit, a consumption usage ID transmitting unit that acquires and transmits a consumption usage ID linked to the received payment ID from the linkage table, and receives the consumption usage ID According to the consumption usage ID receiving unit, the usage limit table holding unit that holds the usage limit amount table that is a table in which the consumption usage ID and the usage limit amount are associated, and the payment confirmation information associated with the received consumption usage ID A card limit management server device having a usage limit change unit for changing the usage limit associated with the consumption usage ID in the usage limit table. Payment system is also provided for.

  With the present invention having the above-described configuration, it is possible to safely send money from others using a card having a receipt ID that can only be used for receipt and a consumption / use ID that can be used for consumption. You can receive money and raise the limit. Further, the remittance to the card can be executed after correctly authenticating the sender.

The conceptual diagram showing an example of the remittance reception by the deposit system of Example 1 The figure showing an example of the functional block in the money_receiving | payment system of Example 1. The conceptual diagram showing an example of the GUI screen in the remittance request information acquisition part of the payment system of Example 1. The conceptual diagram showing an example of the data table for management of the information for authentication in the payment system of Example 1 The figure showing an example of the hardware constitutions in the remittance origin terminal of the payment system of Example 1. The figure showing an example of the hardware constitutions in the server apparatus of the payment system of Example 1. The figure showing an example of the hardware constitutions in the payment side storefront terminal device of the payment system of Example 1. The flowchart showing an example of the flow of processing in the payment system according to the first embodiment. The figure showing an example of the functional block in the money_receiving | payment system of Example 2. The conceptual diagram showing an example of the data table for management of the payment confirmation information in the payment system of Example 2. The flowchart showing an example of the flow of a process in the money_receiving | payment system of Example 2. The figure showing an example of the functional block in the money_receiving | payment system of Example 3. The figure for demonstrating an example of the change process of the usage limit in the payment system of Example 3. FIG. The figure showing an example of the hardware constitutions in the card ID management apparatus of the payment system of Example 3. The figure showing an example of the hardware constitutions in the card limit management server apparatus of the payment system of Example 3. The flowchart showing an example of the flow of a process in the money_receiving | payment system of Example 3.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the present invention is not limited to these embodiments, and can be implemented in various modes without departing from the spirit of the present invention.

  Example 1

    <Overview>

  FIG. 1 is a conceptual diagram illustrating an example of deposit acceptance by a deposit system for a card according to the present embodiment. For example, the user α considered to deposit 10,000 yen to the “card” used by the user β. Therefore, as shown in FIG. 1A, the user α uses his own mobile terminal (remittance source terminal) or the like to access a remittance service registration website by the present system. Then, the receipt ID of the card of the user β as the remittance destination is input on the displayed GUI screen. Then, the server device that manages the Web site stores and holds the input information and information such as the unique ID of the accessed terminal in the database. Also, for example, a barcode for authentication is generated based on the information, and it is returned to the mobile terminal of the user α.

  And as shown in FIG.1 (b), the user (alpha) visits a convenience store etc. and performs the procedure for depositing there. Specifically, the user α causes the terminal device (payment side storefront terminal device) at the store to read the barcode or the like previously returned to the mobile terminal. Then, as shown in FIG. 1 (c), the store terminal device transfers the authentication information indicated by the barcode acquired by reading or the like to the server device described above and makes an authentication request. Then, the server device matches the transferred authentication information with the information stored in its own database, and if matching information is registered, the authentication result indicating the authentication OK is sent to the store terminal device. Send back.

  Then, in the terminal device at the store, as shown in FIG. 1 (d), for example, information indicating that the authentication is OK is displayed on the display for the store clerk, and the store clerk confirming this displays the deposit from the user α or the like. And so on.

    <Functional configuration>

  FIG. 2 is a diagram illustrating an example of functional blocks in the deposit system according to the present embodiment. Note that the functional blocks of each device constituting the system described below can be realized as hardware, software, or both hardware and software. Specifically, if a computer is used, a CPU, a main memory, a bus, or a secondary storage device (a hard disk, a non-volatile memory, a storage medium such as a CD or a DVD, a read drive for the medium, etc.), information Input devices used for input, printing equipment, display devices, other hardware components such as external peripheral devices, interfaces for external peripheral devices, communication interfaces, driver programs for controlling these hardware, Other examples include application programs and user interface applications.

  Then, by CPU processing according to the program developed on the main memory, the data input from the input device or other interface and held in the memory or hard disk is processed and stored, An instruction for controlling the software is generated. The present invention can be realized not only as a system but also as a method. A part of the invention can be configured as software. Further, a software product used to cause a computer to execute such software and a recording medium on which the product is fixed are naturally included in the technical scope of the present invention (the same applies throughout the present specification). .

  As shown in FIG. 2, the deposit system for the card of this embodiment includes a “remittance source terminal” (0200), a “server device” (0210), and a “payment side storefront terminal device” (0220). Become. Note that the “card” can increase the usage limit according to the deposit amount, and two types of IDs, a receipt ID that can only be used for receipt and a consumption use ID that can be used for consumption. A card with Further, the “payment ID” refers to an ID that can be used only for receiving money. However, “available only for receiving money” means that it is used only for receiving money in relation to the card and not used for consumption. IDs that can be used in various situations not related to the card are also used. included. Therefore, for example, in addition to a dedicated ID issued for receiving money, a mobile / fixed telephone number, an e-mail address, a basic resident register number, and the like are included.

    (Configuration requirements for remittance source terminal)

  First, the configuration requirements of the “remittance source terminal” will be described. This remittance source terminal refers to a terminal used by a remittance person, for example, a mobile phone, a PHS (Personal Handyphone System), a PDA (Personal Digital Assistance), a smartphone, a portable game machine with a communication function, a netbook, A portable terminal device such as a notebook PC may be mentioned. If the remittance source terminal is a portable terminal in this way, authentication information to be described later can be easily output to a deposit side storefront terminal device installed at a convenience store or the like that actually deposits money.

  Alternatively, it may be a stationary terminal device such as a desktop PC or a stationary game machine with a communication function. In that case, by printing out the authentication information on paper or transferring it to another portable terminal, It is good to output with respect to the deposit side storefront terminal device installed in the storefront.

  As shown in FIG. 2, the “remittance source terminal” (0200) includes a “remittance request information acquisition unit” (0201), a “remittance request information transmission unit” (0202), and an “authentication information reception unit” ( 0203) and “authentication information output unit” (0204).

  The “remittance request information acquisition unit” (0201) has a function of acquiring remittance request information including, as information, a remittance ID of one or more cards and a remittance source terminal ID. As described above, the “card receipt ID” refers to an ID linked to a card and usable only for receipt. However, “available only for receiving money” means that it is used only for receiving money in relation to the card and not used for consumption. IDs that can be used in various situations not related to the card are also used. included. Therefore, for example, in addition to a dedicated ID issued for receiving money, a mobile / fixed telephone number, an e-mail address, a basic resident register number, and the like are included.

  “Remittance source terminal ID” refers to information for specifying a terminal that is a remittance source. For example, a unique ID (manufacturing ID) of a terminal device that is the remittance source, or a MAC address assigned to the network communication device. Alternatively, like the remittance destination terminal ID, a telephone number or an e-mail address that can be used at the terminal, or an identification number assigned exclusively for this service can be used. In addition, this remittance source terminal ID is managed in association with an e-mail address or the like and a unique ID (remittance source terminal ID) of a terminal identified by the e-mail address in a server device described later, and can be converted by the e-mail address. It may be configured.

  The remittance request information acquisition unit in the remittance request information acquisition unit is configured to display a GUI screen as shown in FIG. 3, for example, and to input a remittance ID of a card as a remittance destination in the input field. The acquisition method is mentioned. Further, the remittance source terminal ID can be automatically acquired without any input by the user if it is a unique ID or MAC address. Moreover, if it is a telephone number, an e-mail address, etc., it is good also as a structure acquired by making a user input via a GUI screen etc. similarly to receipt ID.

  In addition, as shown in FIG. 3, a remittance (planned) amount or the like may be acquired as remittance request information. In that case, it is preferable to perform a process of determining whether or not the actual deposit amount and the scheduled remittance amount input here match with a deposit side storefront terminal device to be described later.

  Further, the remittance request information acquisition unit may be configured to acquire a plurality of receipt IDs at once. And, by processing a plurality of received IDs collectively acquired as described later, a manager (employer) such as a company, for example, uses this system for a plurality of employees. A single piece of authentication information can be used to pay a salary. When remittance is performed for a plurality of cards in this way, it is preferable that the remittance amount information is acquired for each individual receipt ID. As described above, by acquiring the remittance amount information for each receivable ID, it is possible to divide and collect the remittance amount for each remittance destination.

  The “remittance request information transmission unit” (0202) has a function of transmitting the acquired remittance request information and can be realized by, for example, an Internet communication function. Specifically, for example, the service web page in the server device described later is accessed at the remittance source terminal. Then, using the Web page as an input GUI for remittance request information, remittance request information such as a remittance card ID and remittance source terminal ID is input, and the input information is transmitted as an HTTP request to the server device. , And so on. Of course, the transmission of the remittance request information is not limited to this, and may be various, such as e-mail transmission.

  The “authentication information receiving unit” (0203) has a function of receiving authentication information returned in response to the transmission. “Authentication information” is information for depositor authentication generated by the server device in response to transmission of the remittance request information. For example, a bar code generated by transcoding remittance request information or 2 For example, a dimension code or information obtained by encrypting remittance request information may be used. The details of the generation of the authentication information will be described in a server device described later.

  The “authentication information output unit” (0204) has a function of outputting the acquired authentication information. Here, the output form of the authentication information may be various according to the acquisition form of the authentication information in the deposit side storefront terminal device described later. For example, if the deposit side storefront terminal device includes a barcode (or two-dimensional code) reader, the authentication information output unit displays and outputs the authentication information as a barcode or two-dimensional code on a display or the like. Can be mentioned. In addition, if the deposit-side storefront terminal device has a short-range wireless communication function, the authentication information is modulated into a communication signal for the short-range wireless communication and output.

  Further, if the remittance source terminal is a stationary desktop PC or the like, as described above, a barcode or two-dimensional code indicating authentication information is printed on paper and output using a printing device or the like. And a form of transferring and outputting to other portable terminals.

  In the remittance source terminal, the remittance including its own authentication is performed by, for example, outputting and reading the information for authentication to a deposit side storefront terminal device installed in a convenience store or the like. The procedure for can be done easily.

    (Configuration requirements for server equipment)

  Next, returning to FIG. 2, the configuration requirements of the “server device” will be described. As shown in FIG. 2, the “server device” (0210) includes a “reception unit” (0211), an “authentication information generation unit” (0212), a “reply unit” (0213), and a “transfer reception”. Section ”(0214),“ authentication section ”(0215), and“ forwarding reply section ”(0216).

  The “reception unit” (0211) has a function of receiving remittance request information transmitted from the remittance request information transmitting unit of the remittance source terminal. In this receiving unit, for example, remittance request information is received from a remittance source terminal via a network or the like.

  The “authentication information generation unit” (0212) has a function of generating and holding unique authentication information corresponding to the received remittance request information. For example, a CPU, a main memory, a recording medium such as an HDD, and an authentication It can be realized by an information generation program. Specifically, for example, a unique character string is randomly generated or regularly generated according to a predetermined rule, and converted into a barcode or the like to generate authentication information. An arbitrary character string before code conversion may be used as authentication information. Moreover, you may comprise so that the money_receiving | payment ID and money_remittance_source terminal ID contained in remittance request information in that case may be added to the said random character string. Further, if the remittance request information includes the scheduled remittance amount, the amount information may be added.

  When generating authentication information by barcode conversion, two-dimensional code conversion, etc., it is not preferable to generate authentication information by code conversion only with information included in the remittance request information. Because these code conversion methods are generally disclosed, if the information that is the conversion source is only the information included in the remittance request information, a barcode or the like, which is authentication information, can be easily given to general users. This is because it can be generated. Therefore, when generating this authentication information, it is desirable to generate it by adding some character string in this server device, or by performing code conversion using a private conversion method.

  The data format of the authentication information is not particularly limited. For example, the above-described barcode, two-dimensional code, data format indicating an arbitrary character string before code conversion, or specific information is embedded so that it can be read. For example, a data format indicating image data, audio data, and the like. Then, a reading device such as a barcode reader corresponding to them may be provided in the deposit side storefront terminal device described later.

  The authentication information generated as described above and various information used to generate the authentication information are recorded on a recording medium such as an HDD in the authentication information generation unit, and a remittance source terminal to be described later It is used for the authentication of. If the authentication information is generated without including the receipt ID or the remittance source terminal ID, as shown in FIG. 4A, the receipt ID or the remittance included in the remittance request information for the above authentication. The authentication information may be recorded in association with the destination terminal. Further, if these IDs are included in the authentication information, it is preferable to record the information directly on the recording medium as shown in FIG. 4B and to read the information from the authentication information at the time of authentication.

  The “reply unit” (0213) has a function of returning the generated authentication information to the remittance source terminal, for example, receiving remittance request information from the remittance source terminal via a network or the like. . As described above, for example, when the employer remits the salary to the employee, the server apparatus may perform the following processing when a plurality of cards are used as the remittance destination. That is, the authentication information is first generated individually corresponding to each of the plurality of payment IDs included in the remittance request information. Then, one piece of collective authentication information associated with the plurality of pieces of individually generated authentication information is generated, and the association is managed. Then, only the authentication information is returned to the remittance source terminal.

  In this way, the authentication information sent back to the sender is combined into one, so that the sender does not need to make a separate payment for each destination, and only a deposit process using one authentication information is required. Remittance procedures can be performed. And when actually receiving money, as will be described later, the server device uses a plurality of individual authentication information and the collective authentication information managed in association with each other, and the server device accepts a plurality of receiving destination cards. And so on.

  The “transfer receiving unit” (0214) has a function of receiving the transfer of authentication information output from the authentication information output unit of the remittance source terminal. Note that “transfer of authentication information” refers to the following information flow. That is, the authentication information transmitted to the remittance source terminal by the above-described reply unit is read by a terminal of a store that actually accepts payment for remittance (a deposit side storefront terminal device described later). Then, the read authentication information is transmitted from the deposit side storefront terminal device together with the authentication request to the server device, and is received by the transfer receiving unit.

  That is, the transfer receiving unit receives authentication information as an authentication request made by the storefront terminal for sender authentication when the depositing side storefront terminal device to be described later actually receives the deposit process, and the authentication is performed with the following configuration. Processing will be executed. The generation of the authentication request in the deposit side storefront terminal device will be described later.

  The “authentication unit” (0215) has a function of acquiring an authentication result based on the transferred authentication information and the authentication information that is uniquely associated with the remittance request information of the remittance source terminal. Have. Specifically, if the remittance source terminal ID is included in the received authentication information, a data table as shown in FIG. 4 is referred to using the remittance source terminal ID as a key, and the held authentication information is changed. Identify. Alternatively, when the remittance source terminal ID is not included in the authentication information, as will be described later, the remittance source terminal ID transmitted from the deposit side storefront terminal device in association with the authentication information is used as a key in the same manner. Referring to the data table as shown in Fig. 4, the held authentication information is specified.

  Then, a process of determining whether the identified authentication information matches, for example, a random character string or other information indicated by the acquired authentication information is executed by a logical operation process such as a CPU. If they match, authentication OK or mismatch If so, an authentication result with the authentication NG is obtained.

  The “transfer reply unit” (0216) has a function of returning the authentication result to the transfer source of the authentication information. For example, the authentication is performed for the transfer source (payment side storefront terminal device) via a network or the like. The result is transmitted.

  Then, in the next depositing storefront terminal device, processing is performed by distinguishing whether or not to perform the procedure for remittance using the authentication result returned as described above according to the authentication information transferred and transmitted as the authentication request. be able to.

    (Construction requirements for deposit side storefront terminal device)

  Next, returning to FIG. 2, the configuration requirements of the “payment side storefront terminal device” will be described. As shown in FIG. 2, the “payment side storefront terminal device” (0220) includes an “authentication information acquisition unit” (0221), a “transfer unit” (0222), and an “authentication result reception unit” (0223). And “authentication result display section” (0224). This deposit side storefront terminal device has the following configuration requirements, and refers to a device that inputs / outputs information to / from the server device and other devices via a network and other communication means by wired, wireless, or infrastructure connection, For example, it can be realized by being incorporated in terminals installed in convenience stores, service stations, travel agencies, and other various stores.

  The “authentication information acquisition unit” (0221) has a function of acquiring authentication information output from the authentication information output unit of the remittance source terminal. For example, if the authentication information is a barcode or a two-dimensional code, It can be realized by a code reading device corresponding to it. Specifically, the user who performed the remittance registration process using the remittance source terminal as described above has the remittance source terminal in which the authentication information returned in response is recorded, and actually pays in. In order to do this, they visit certain stores such as convenience stores. And the bar code etc. which are the information for authentication memorize | stored in the remittance origin terminal are displayed on a terminal display, and it is made to read by the bar code reader etc. of this deposit side storefront terminal device installed in the store. .

  If the authentication information is an arbitrary character string or the like, the authentication information acquisition unit can be realized by an input device such as a keyboard, a touch panel, or a GUI screen for inputting the authentication information. If the authentication information is image data, it can be realized by an image reading device such as a camera. If the authentication information is audio data, it can be realized by a voice input device such as a microphone. If the authentication information is code-converted or embedded in an image or sound, the information input from such various input devices is interpreted according to the conversion / embedding rules to obtain the authentication information. It is a state of doing. Further, there is a form in which the authentication information transmitted from the remittance source terminal by near field communication is received, demodulated and acquired.

  Further, as described above, when the remittance source terminal ID is not included in the authentication information, the remittance source terminal ID may be acquired in association with the authentication information acquisition source terminal.

  The “transfer unit” (0222) has a function of transferring the acquired authentication information to the server device. For example, the authentication information acquired as described above is transmitted to the server device via a network or the like. For example, it is transmitted as an authentication request. In addition, when the remittance source terminal ID is not included in the authentication information, the remittance source terminal ID acquired as described above may be associated and transmitted.

  The “authentication result receiving unit” (0223) has a function of receiving an authentication result returned in response to transfer. For example, the authentication information acquired and returned as described above in the server device via a network or the like Is received. Note that the response of the authentication result corresponding to the transfer is as described in connection with the configuration requirements of the server device.

  The “authentication result display unit” (0224) has a function of displaying the received authentication result, and can be realized by, for example, a display device including a display or a VRAM, and an authentication result display program. And the store clerk etc. confirms the authentication result displayed here, and if it is OK, a payment will be accepted.

  Of course, the deposit side storefront terminal device is configured as a device that automatically performs all payments. If the authentication result is authentication OK, the payment is automatically displayed to the sender by displaying that fact on the display and opening the deposit slot. You may make it encourage. The authentication result may be output by voice output instead of display on a display or the like.

  Further, if the authentication information includes information such as the scheduled remittance amount, the authentication result may be returned including the amount information and the amount displayed on a display or the like. Then, it may be configured such that the displayed amount is confirmed, the store clerk or the computing device of the computer determines whether or not the deposit amount matches the planned amount, and the result information is input / generated.

  In this manner, the remittance person can perform remittance processing by a simple procedure such as reading the authentication information at a store or the like by registering in advance with his / her mobile terminal or the like.

  In addition, although the information transmission / reception between the apparatuses in the system in the above-described embodiment has been described by taking an example in which the apparatuses directly perform each other, the transmission / reception may be performed via another apparatus. . In addition, the entities that manage each device including the devices in the second and subsequent embodiments may be various, may be managed by completely different entities, or a plurality of devices may be managed by the same entity. In addition, as for the apparatus itself, what is described as one apparatus may be physically realized by a plurality of apparatuses, or what is described as a plurality of apparatuses may be physically incorporated into one apparatus and realized. .

    <Hardware configuration>

  An example of the hardware configuration of each device of this system will be described with reference to FIGS.

    (Hardware configuration of remittance source terminal)

  FIG. 5 is a diagram illustrating an example of a hardware configuration of the remittance source terminal of the system. As shown in this figure, the remittance source terminal of this system includes a “CPU (central processing unit)” (0501) for executing various arithmetic processes and a “main memory” (0502). In addition, an “input device” (0503) for inputting remittance request information, an “internet communication circuit” (0504) which is an information output unit for remittance request information, an authentication information receiving unit, and an authentication information output unit, A “flash memory” (0505) for recording programs and the like is also provided. They are connected to each other via a data communication path such as a “system bus” to transmit / receive information and process information.

  A program is read out to the “main memory”, and the “CPU” refers to the read out program and executes various arithmetic processes according to the procedure indicated by the program. In addition, a plurality of addresses are assigned to each of the “main memory” and “flash memory”, and in the calculation processing of the “CPU”, the addresses are specified and accessed to store the data. It is possible to perform arithmetic processing using.

  The remittance source terminal will be described by taking a mobile phone as an example, but it is not limited to that as described above.

  Here, the user operates the “input device” to access the Web page for remittance request registration. Then, in response to the access, a registration Web page is acquired via the “Internet communication circuit” and displayed on a “display” (not shown). The user operates the “input device” to input the receipt ID of the partner card as the destination in the entry field of the receipt ID of the displayed registration Web page. At that time, the scheduled remittance amount may be input.

  Then, upon accepting the “determined transmission” input by operating the “input device”, the “CPU” interprets the transmission program, and first acquires its own terminal ID (for example, a mobile phone number or a device-specific ID). And stored in the main memory as the remittance source terminal ID. Alternatively, the remittance source terminal ID may be configured to be input and acquired together with the remittance destination terminal ID by providing an input field on the registration Web page. Then, the remittance source terminal ID is transmitted to the server device from the “Internet communication circuit” as remittance request information together with the input ID of the received card.

  Then, as a response to the transmission of the remittance request information, when the authentication information generated and returned by the server device is acquired by the “Internet communication circuit” as described later, the acquired authentication information is “flash memory”. Record in etc. After that, when the user visits a store such as a convenience store to actually deposit money, the “CPU” interprets the authentication information output program according to the operation from the user, and the authentication is displayed on the “display” of the remittance source terminal. Information such as a barcode is output and displayed. Then, the authentication information is read by the reading device of the deposit-side storefront terminal device installed at the storefront. Alternatively, the authentication information may be output to the deposit-side storefront terminal device using short-range wireless communication or the like. Then, using the authentication information output in this way, the deposit side storefront terminal device authenticates the depositor as will be described later.

    (Hardware configuration of server device)

  FIG. 6 is a diagram illustrating an example of a hardware configuration of the server apparatus of the present system. As shown in this figure, the server device of this system executes various arithmetic processes, and also includes “CPU” (0601) which is an authentication information generation unit and authentication unit, and “main memory” (0602). I have. Also, an “Internet communication circuit” (0603) that is a receiving unit, a reply unit, a transfer receiving unit, and a transfer reply unit, and an “HDD” (0604) that records various information and programs are provided. They are connected to each other via a data communication path such as a “system bus” to transmit / receive information and process information.

  Here, when the remittance request information from the remittance source terminal described above is received by the “Internet communication circuit”, the “CPU” interprets the reception program and stores the remittance request information received accordingly in the “main memory”.

  Subsequently, the “CPU” interprets the authentication information generation program, and combines the remittance request information stored in, for example, the “main memory” with the randomly generated authentication character string accordingly, and converts it into a code. To generate authentication information. Of course, the authentication information may be generated by other methods. Then, the “CPU” interprets the reply program and outputs authentication information from the “Internet communication circuit” to the remittance source terminal accordingly.

  At the same time, the authentication information is recorded in the record of the data table in the “HDD” as shown in FIG. 4 in association with the remittance source terminal ID included in the transmission request information and the receipt ID of the card as the transmission destination. To do.

  After that, when the authentication information sent back to the remittance source terminal is read to the deposit side storefront terminal device and transferred as an authentication request, the “CPU” displays the authentication information indicated by the authentication request in accordance with the authentication program in the “main memory”. To store. Then, using the remittance source terminal ID included in or associated with the authentication information as a key, the data table search process in “HDD” is performed by the logical operation process of “CPU”.

  Then, the authentication information in the data table specified as a result of the search processing is compared with the authentication information stored in the “main memory”, and a comparison result that matches is output from the “CPU”. Then, an authentication result indicating authentication OK is generated and stored in the “main memory”. If there is no record in the matching data table as a result of the search, or if a result indicating that the comparison does not match is output, an authentication result indicating authentication NG is generated and stored in the “main memory”. Then, the “CPU” interprets the transfer reply program, outputs the authentication result from the “Internet communication circuit” to the deposit side storefront terminal device that is the transmission source of the authentication request, and sends it back.

    (Hardware configuration of deposit side storefront terminal device)

  FIG. 7 is a diagram illustrating an example of a hardware configuration of the deposit-side storefront terminal device of the present system. As shown in this figure, the deposit-side storefront terminal device of this system includes a “CPU” (0701) that executes various arithmetic processes and a “main memory” (0702). In addition, for example, a “reading device” (0703) such as a barcode reader that is an authentication information acquisition unit, an “Internet communication circuit” (0704) that is a transfer unit and an authentication result receiving unit, and a “display” that is an authentication result display unit. (0705) is also provided. They are connected to each other via a data communication path such as a “system bus” to transmit / receive information and process information.

  Here, the bar code displayed on the display of the remittance source terminal of the user who visited the store is read by the “reading device”, and the acquired authentication information is stored in the “main memory”. Alternatively, the deposit-side storefront terminal device may include a “short-range wireless communication circuit” instead of the “reading device”, and acquire authentication information transmitted from the remittance source terminal by short-range wireless communication. Then, the “CPU” interprets the transfer program and outputs the authentication information acquired according to the transfer program from the “Internet communication circuit” to the server device as an authentication request.

  When the authentication result generated and returned by the server device is acquired as a response to the authentication request by the “Internet communication circuit”, the acquired authentication result is stored in the “main memory”. Then, according to the interpretation result of the “CPU” authentication result display program, the authentication result indicated by the authentication result is displayed on the “display” or the like of this deposit side storefront terminal device.

  Then, for example, by confirming the authentication result by a store clerk or a computer, it is possible to determine whether to accept / reject the payment from the user.

    <Process flow>

  FIG. 8 is a flowchart showing an example of the processing flow in the deposit system of the present embodiment. The steps shown below may be steps executed by each hardware configuration of the computer as described above, or may be processing steps that constitute a program for controlling the computer recorded on a medium. I do not care.

  As shown in this figure, first, at a remittance source terminal used by a remittance user, for example, by accessing a registration web page and entering according to the registration screen, the receipt ID of one or more cards, Remittance request information including the remittance source terminal ID as information is acquired (step S0801). Then, the remittance request information thus acquired is transmitted (step S0802).

  Then, the server device receives the remittance request information transmitted from the remittance source terminal (step S0811), and generates and holds unique authentication information for depositor authentication corresponding to the received remittance request information ( Step S0812). Then, the generated authentication information is returned to the remittance source terminal (step S0813).

  When the remittance source terminal receives the authentication information returned from the server device as described above (step S0803), the received authentication information is held in, for example, a flash memory inside the terminal. After that, when visiting a store that actually makes the deposit, the authentication information is output to the deposit-side storefront terminal device installed in the store by, for example, a display display output or a short-range wireless communication output ( Step S0804).

  The deposit-side storefront terminal device acquires authentication information output from the remittance source terminal, such as display output or short-range wireless output (step S0821), and transfers the acquired authentication information to the server device (step S0821). S0822).

  When the server device receives the authentication information transferred from the deposit side storefront terminal device (step S0814), the server device is unique with respect to the received authentication information and the remittance request information of the remittance source terminal in step S0812. Is compared with the authentication information held in association with the authentication result to obtain an authentication result (step S0815). Then, the authentication result is returned to the deposit-side storefront terminal device that is the transfer source of the authentication information (step S0816).

  Then, the deposit side storefront terminal device receives the authentication result returned in response to the transfer (step S0823), and displays the received authentication result on, for example, a display for shop assistants (step S0824). Then, the displayed authentication result can be confirmed, and it can be determined whether or not to accept or reject the payment from the user.

    <Simple explanation of effect>

  With the deposit system of the present embodiment, the remittance person can perform remittance processing by a simple procedure such as reading the authentication information at the store etc. by registering in advance with his / her portable terminal or the like.

  << Example 2 >>

    <Overview>

  This embodiment is based on the above embodiment, and further has a function of confirming at the deposit side storefront terminal device that payment has actually been actually made at the store and transmitting a receipt ID from the server device accordingly. It is a deposit system. Thus, by sending the receipt ID in response to the fact that the actual deposit has been made, it is possible to reliably increase the card usage limit indicated by the receipt ID according to the deposit.

    <Functional configuration>

  FIG. 9 is a diagram illustrating an example of functional blocks in the deposit system according to the present embodiment. As shown in this figure, the deposit system of the present embodiment is based on the first embodiment, and is based on the “remittance source terminal” (0900), “server device” (0910), and “payment side storefront terminal device” (0920). ). In addition, since the structural requirements etc. in the remittance source terminal have already been described in the above embodiment, description thereof is omitted.

  And the deposit system of a present Example has the point that the "payment side storefront terminal device" further has a "payment confirmation information reception part" (0921) and a "payment confirmation information transmission part" (0922), The “server device” further includes a “payment confirmation information receiving unit” (0911) and a “payment ID transmission unit” (0912). In addition, about the component requirement already described in Example 1 about this payment side storefront terminal device and server apparatus, illustration and its description are abbreviate | omitted.

    (Functional configuration of the deposit side storefront terminal device)

  The “payment confirmation information receiving unit” (0921) has a function of receiving payment confirmation information, which is information on confirmation of payment made in accordance with the display of the authentication result on the authentication result display unit. For example, an input device or a communication circuit , CPU, main memory, payment confirmation information reception program, etc.

  Specifically, for example, when the authentication result is received at a POS cash register (payment side in-store terminal device) installed in the store as in the first embodiment, and the fact is displayed on the display, the POS cash register is waiting for payment. Migrate to Then, when the user who is the remittance requester pays, for example, actual money or securities to be replaced with other money to the clerk, the clerk presses the “payment confirmed button” in the POS cash register. Then, the payment confirmation information is generated and accepted at the POS cash register.

  In addition, there is also a configuration in which payment confirmation information is generated and received by receiving electronic money from the user or electronic money information that can be used in other systems from a remittance source terminal, electronic money card, or other system. It is done.

  Then, by accepting information that can confirm that the money for remittance has actually been received in this way, when the user of the remittance destination actually tries to receive money in this system, the deposit for that purpose Can be determined.

  The “payment confirmation information transmitting unit” (0922) has a function of transmitting the payment confirmation information received by the payment confirmation information receiving unit to the server device. The payment confirmation information acquired as described above is transmitted. In addition, when the payment confirmation information is registered in the server device described later, the payment confirmation information is registered in association with the remittance source terminal ID and the receipt ID of the card as the remittance destination. Therefore, the payment confirmation information transmission unit may extract the remittance source terminal ID and the receipt ID from the authentication information that is the basis of the received authentication result, and transmit them in association with the payment confirmation information. good.

  Alternatively, if the server device is configured to manage the authentication result in association with the remittance source terminal ID and the money receiving ID, for example, it may be configured to transmit the payment confirmation information to the server device in association with the authentication result (identification information thereof). good.

    (Functional configuration of server device)

  The “payment confirmation information receiving unit” (0911) has a function of receiving payment confirmation information transmitted from the deposit side storefront terminal device. For example, the payment confirmation information from the deposit side storefront terminal device via a network or the like For example, information is received.

  The “receipt ID transmission unit” (0912) has a function of transmitting the received receipt confirmation information in association with the receipt ID of the card. For example, as shown in FIG. 10, the receipt ID associated with the receipt flag and With reference to a data table or the like of the server device indicating the remittance source terminal ID, the payment confirmation information associated with the receipt ID is transmitted with respect to the item for which the deposit flag is ○ (deposited).

  In addition, when a plurality of payment IDs are specified in one remittance request information as described above, the received payment confirmation information is used to associate with the above-described summary authentication information that is the basis of the payment confirmation. It is preferable that a payment confirmation flag is set and processed for all of the plurality of receipt IDs associated with the plurality of individual authentication information.

  In response to this transmission, a usage limit raising process for the card is executed as described later in the third embodiment.

  In addition, as an item in the table shown in FIG. 10, an expiration date (for example, two weeks after receipt of payment confirmation information) is set in association with each record, and after that, the remittance destination user is sent to the remittance source terminal. It may be configured to notify that the payment is not performed.

    <Process flow>

  FIG. 11 is a flowchart showing an example of the flow of processing in the deposit system of the present embodiment. The steps shown below may be steps executed by each hardware configuration of the computer as described above, or may be processing steps that constitute a program for controlling the computer recorded on a medium. I do not care.

  Note that the processing up to reception and display of the authentication result at the deposit side storefront terminal device has already been described with reference to FIG.

  Then, when the deposit side storefront terminal device receives the authentication result indicating that the authentication of the sender is OK (step S1121), the deposit side is in a waiting state for deposit. Then, for example, when payment is made by actual money payment and the receipt confirmation information indicating it is received in association with the authentication information (step S1122), the receipt confirmation information is associated with the remittance terminal ID and receipt ID, for example. To the server device (step S1123).

    The server device receives the received payment confirmation information (step S1111), associates the received payment confirmation information with the receipt ID of the card as the remittance destination, and increases the card usage limit amount related to the receipt ID. For transmission (step S1112).

    <Simple explanation of effect>

  As described above, the receipt ID of the card is transmitted by receiving the receipt confirmation information indicating that the deposit of the money for remittance was actually made by the deposit system of the present embodiment. Processing (processing for raising the usage limit) can be performed.

  Example 3

    <Overview>

  The present embodiment is a deposit system characterized in that, as described above, using the receipt ID of the card transmitted in accordance with the actual deposit confirmation, a process for raising the card usage limit is performed. In particular, this card has its receipt ID and consumption / use ID managed as separate IDs, so that it is possible to safely carry out the deposit and use limit increase with different IDs. And

  <Functional configuration>

  FIG. 12 is a diagram illustrating an example of functional blocks in the deposit system according to the present embodiment. The deposit system of the present embodiment has a “remittance source terminal”, a “server device”, and a “payment side storefront terminal device” based on the first embodiment (illustration and description omitted), and further, “card ID management”. The apparatus further includes a “device” (1200) and a “card limit management server device” (1210).

    (Card ID management device)

  First, the configuration requirements of the “card ID management device” will be described. As shown in FIG. 12, the “card ID management device” (1200) includes a “correlation table holding unit” (1201), a “payment ID reception unit” (1202), and a “consumption use ID transmission unit” (1203). And).

  The “correlation table holding unit” (1201) has a function of retaining a correlation table in which a consumption use ID and a receipt ID are linked, and can be realized by various storage media such as a hard disk drive. Specifically, for example, the consumption use ID “0123” is associated with the unique receipt ID “Ctl-001-123-xxx”. Alternatively, the mobile phone number “090-xxx-xxxx” is used as the receipt ID, and the consumption use ID “9876” is associated therewith. Alternatively, the consumption use ID “1234” is associated with the electronic mail address “α@yyy.ne.jp” which is the receipt ID.

  By managing the card ID and consumption ID as separate IDs in this way, it is possible to safely receive money by designating a mobile phone number, etc. without informing the sender of the consumption ID. You can raise the card usage limit.

  In addition, the consumption / use ID held in the association table is managed by combining two types of fixed ID (card ID used for actual consumption) and variable ID (one-time use-up ID). It is possible to improve the security.

  The “receipt ID receiving unit” (1202) has a function of receiving the receipt ID transmitted in association with the receipt confirmation information from the server device, and is received via, for example, a network.

  The “consumption usage ID transmission unit” (1203) has a function of acquiring and transmitting a consumption usage ID linked to the received receipt ID from the linkage table. For example, the above table is obtained by a logical operation process such as a CPU. And the corresponding consumption use ID is transmitted via a network or the like.

    (Card limit management server device)

  Next, returning to FIG. 12, the configuration requirements of the card limit management server device will be described. As shown in FIG. 12, the “card limit management server device” includes a “consumption use ID receiving unit” (1211), a “use limit table holding unit” (1212), and a “use limit changing unit”. (1213).

  The “consumed use ID receiving unit” (1211) has a function of receiving the consumed use ID transmitted from the card ID management device, and obtains the consumed use ID via, for example, the Internet network. It is.

  The “use limit table holding unit” (1212) has a function of holding the use limit table, and can be realized by various storage media such as an HDD. The “use limit table” refers to a table in which the consumption use ID and the use limit are associated with each other. For example, when a card is actually presented at a store or the like, the use limit amount is referred to. That is, it is determined whether or not it can be used. In this embodiment, the use limit is configured to be changeable according to the amount of money received by the following configuration.

  The “use limit change unit” (1213) has a function of changing the use limit associated with the consumption use ID in the use limit table in accordance with the payment confirmation information associated with the received consumption use ID.

  FIG. 13 is a diagram for explaining an example of the change process of the usage limit amount. As shown in FIG. 13A, the limit of use associated with the consumption use ID “0123” is “100,000 yen”. Here, if the deposit confirmation information indicates that 10,000 yen has been deposited on the card of ID: 0123 (receipt ID: 090-xxx-xxxx), as shown in FIG. In addition, the usage limit associated with the consumption usage ID “0123” is updated to “110,000 yen”.

  The card limit management server device may be configured to receive information indicating that the payment within the usage limit has been executed and raise the usage limit by the amount of payment. By doing so, it becomes possible to appropriately change and manage the use limit amount according to the receipt and use of the card.

  In addition, with regard to the payment confirmation information used for determining the withdrawal amount, the payment confirmation information may be obtained directly, or when the card ID management device transmits the consumption use ID, the withdrawal is based on the payment confirmation information. As long as the information indicating the amount is separately generated and transmitted in association with the consumption use ID, the amount to be raised may be determined with reference to the generated information. Also, the amount itself may be the same as the amount received, or may be the amount deducted from the fee or the amount increased by some kind of privilege.

  As described above, it is possible to safely raise the usage limit by the receipt ID managed as an ID different from the consumption use ID.

    <Hardware configuration>

  An example of the hardware configuration of each device of this system will be described with reference to FIGS.

    (Hardware configuration of card ID management device)

  FIG. 14 is a diagram illustrating an example of a hardware configuration of the card ID management apparatus of the present system. As shown in this figure, the card ID management device of this system includes a “CPU (central processing unit)” (1401) that executes various arithmetic processes and a “main memory” (1402). In addition, an “HDD” (1403) that is a linking table holding unit and an “Internet communication circuit” (1404) that is a receipt ID receiving unit and a consumption / use ID transmitting unit are provided. They are connected to each other via a data communication path such as a “system bus” to transmit / receive information and process information.

  Here, the “CPU” interprets the receipt ID reception program, and stores the receipt ID and the deposit amount received at the predetermined address in the “main memory”.

  Subsequently, the “CPU” interprets the consumption / use ID transmission program and searches the consumption / use ID using the received ID stored in the address 1 of the “main memory” as a key. Logical operation processing is performed with reference to the associated table. As a result, the consumption use ID associated with the receipt ID is specified in the association table and stored in the address 3 of “main memory”.

  Then, the “CPU” further transmits the consumption use ID stored in the predetermined address of the “main memory” and the deposit amount via the “Internet communication line” according to the interpretation result of the consumption use ID transmission program. is there.

    (Hardware configuration of card limit management server device)

  FIG. 15 is a diagram illustrating an example of a hardware configuration of the card limit management server device of the present system. As shown in this figure, the card limit management server device of this system executes various arithmetic processes and uses a “CPU (central processing unit)” (1511) which is a usage limit changing unit, and “main memory”. (1512). In addition, “HDD” (1513) which is a usage limit table holding unit and “Internet communication circuit” (1514) which is a consumption usage ID receiving unit are also provided. They are connected to each other via a data communication path such as a “system bus” to transmit / receive information and process information.

  Here, when the consumption use ID is received by the “Internet communication circuit”, the “CPU” interprets the consumption use ID receiving program, and the received consumption use ID and the amount received according to the interpretation are received according to the address 1 of the “main memory”. 2 respectively.

  Subsequently, “CPU” interprets the usage limit change program and refers to the usage limit table held in “HDD” using the consumption usage ID stored at address 1 of “main memory” as a key. Perform logical operation processing. As a result, the usage limit amount associated with the consumption usage ID is specified in the usage limit table and stored in address 3 of “main memory”.

  Then, the “CPU” performs a calculation process to add the deposit amount stored at the address 2 of the “main memory” to the usage limit amount stored at the address 3, and calculates the usage limit amount with the face value raised. To do. Then, the new usage limit amount is written in the corresponding record of the usage limit amount table held in “HDD”.

    <Process flow>

  FIG. 16 is a flowchart showing an example of a processing flow in the deposit system of the present embodiment. The steps shown below may be steps executed by each hardware configuration of the computer as described above, or may be processing steps that constitute a program for controlling the computer recorded on a medium. I do not care.

  In addition, since it has already described in the said Example about the process until it transmits receipt ID in a server apparatus, the description is abbreviate | omitted.

  Then, when the card ID management device receives the receipt ID transmitted in association with the payment confirmation information from the server device (step S1601), the card ID management device associates a consumption use ID with the receipt ID in advance and holds the association table. The consumption use ID linked to the received receipt ID is acquired (step S1602), and the acquired consumption use ID is transmitted together with the deposit amount indicated by the payment confirmation information (step S1603). .

  Then, in the card limit management server device, the transmitted consumption use ID is received (step S1614), and the received consumption use ID in the table that holds the consumption use ID and the limit amount in advance in association with each other. The associated usage limit is acquired (step S1615), and the usage limit is changed according to the deposit amount (step S1616).

    <Simple explanation of effect>

  As described above, according to the deposit system of the present embodiment, it is possible to safely accept a card with a receipt ID managed as an ID different from the consumption use ID, and to execute a process of raising the limit of use. .

0200 Remittance source terminal 0201 Remittance request information acquisition unit 0202 Remittance request information transmission unit 0203 Authentication information reception unit 0204 Authentication information output unit 0210 Server device 0211 Reception unit 0212 Authentication information generation unit 0213 Reply unit 0214 Transfer reception unit 0215 Authentication unit 0216 Transfer reply unit 0220 Deposit side store terminal device 0221 Authentication information acquisition unit 0222 Transfer unit 0223 Authentication result reception unit 0224 Authentication result display unit

Claims (10)

It is possible to raise the usage limit according to the deposit amount associated with the card, and has two types of IDs, a receipt ID that can be used only for receipt and a consumption use ID that can be used for consumption A deposit system for cards,
A remittance request information acquisition unit for acquiring remittance request information including information of a receivable ID of one or more of the cards and a remittance source terminal ID;
A remittance request information transmitting unit for transmitting the acquired remittance request information;
An authentication information receiving section for receiving authentication information for depositor authentication returned in response to the transmission;
An authentication information output unit for outputting the acquired authentication information;
A remittance source terminal having
A receiving unit for receiving remittance request information transmitted from the transmitting unit of the remittance source terminal;
An authentication information generating unit that generates and holds unique authentication information corresponding to the received remittance request information;
A reply unit that returns the generated authentication information to the remittance source terminal;
A transfer receiving unit that receives the transfer of the authentication information output from the authentication information output unit of the remittance source terminal;
An authentication unit that acquires an authentication result based on the authentication information that is transferred and received, and the authentication information that is uniquely associated with the remittance request information of the remittance source terminal;
A transfer reply unit that returns the authentication result to the transfer source of the authentication information;
A server device having
An authentication information acquisition unit for acquiring authentication information output from the authentication information output unit of the remittance source terminal;
A transfer unit that transfers the acquired authentication information to the server device;
An authentication result receiver for receiving an authentication result returned in response to the transfer;
An authentication result display section for displaying the received authentication result;
A deposit-side storefront terminal device having
Payment system for cards with The deposit side storefront terminal device is:
A payment confirmation information receiving unit for receiving payment confirmation information, which is information of payment confirmation made in accordance with the display of the authentication result in the authentication result display unit;
A payment confirmation information transmitting unit that transmits the payment confirmation information received by the payment confirmation information receiving unit to the server device;
The server device
A receipt confirmation information receiving unit for receiving receipt confirmation information transmitted from the receipt-side in-store terminal device;
A receipt ID transmission unit that transmits the received receipt confirmation information in association with the receipt ID of the card;
The payment system with respect to the card | curd of Claim 1 which has these. A tied table holding unit for holding a tied table in which a consumption use ID and a receipt ID are linked;
A receipt ID receiving unit for receiving a receipt ID transmitted in association with the payment confirmation information from the server device;
A consumption use ID transmitting unit that acquires and transmits a consumption use ID associated with the received receipt ID from the association table;
A card ID management device having
A consumption use ID receiving unit for receiving the consumption use ID;
A usage limit amount table holding unit that holds a usage limit amount table that is a table in which a consumption usage ID and a usage limit amount are associated;
A usage limit change unit that changes the usage limit associated with the consumption usage ID in the usage limit table according to the payment confirmation information associated with the received consumption usage ID;
A card limit management server device having:
The payment system with respect to the card | curd of Claim 2 which has these.   The server device according to claim 1 or 2.   The deposit side storefront terminal device according to claim 1 or 2.   The card ID management device according to claim 3.   The card limit management server device according to claim 3. It is possible to raise the usage limit according to the deposit amount associated with the card, and has two types of IDs, a receipt ID that can be used only for receipt and a consumption use ID that can be used for consumption A method of operating a deposit system for a card,
A remittance request information acquisition step of acquiring remittance request information including information of a remittance ID of one or more of the cards and a remittance source terminal ID;
Remittance request information transmission step for transmitting the acquired remittance request information;
An authentication information receiving step for receiving authentication information for depositor authentication returned in response to the transmission;
An authentication information output step for outputting the acquired authentication information;
On the remittance source terminal,
A receiving step of receiving remittance request information transmitted in the transmitting step of the remittance source terminal;
An authentication information generation step for generating and maintaining unique authentication information corresponding to the received remittance request information;
A reply step of returning the generated authentication information to the remittance source terminal;
A transfer receiving step for receiving the transfer of the authentication information output in the authentication information output step of the remittance source terminal;
An authentication step of acquiring an authentication result based on the authentication information transferred and received, and the authentication information that is uniquely associated with the remittance request information of the remittance source terminal;
A transfer reply step for returning the authentication result to the transfer source of the authentication information;
On the server device,
An authentication information acquisition step for acquiring the authentication information output in the authentication information output step of the remittance source terminal;
A transfer step of transferring the acquired authentication information to the server device;
An authentication result receiving step for receiving an authentication result returned in response to the transfer;
An authentication result display step for displaying the received authentication result;
Is executed at the deposit side storefront terminal device,
How the deposit system works for cards. At the deposit side storefront terminal device,
A receipt confirmation information receiving step for accepting receipt confirmation information, which is confirmation information of receipt made according to the display of the authentication result in the authentication result display step;
A deposit confirmation information transmission step of transmitting the receipt confirmation information received in the receipt confirmation information reception step to the server device; and
In the server device,
A receipt confirmation information receiving step for receiving receipt confirmation information transmitted from the deposit side storefront terminal device;
A receipt ID sending step of sending the received receipt confirmation information in association with the receipt ID of the card;
The method of operating a deposit system for a card according to claim 8, further comprising: It has in advance a tied table holding unit for holding a tied table in which the consumption use ID and the receipt ID are linked,
A receipt ID receiving step for receiving a receipt ID transmitted in association with the payment confirmation information from the server device;
A consumption use ID transmission step of acquiring and transmitting a consumption use ID linked to the received receipt ID from the linkage table;
Is executed by the card ID management device,
A usage limit amount table holding unit for holding a usage limit amount table that is a table in which the consumption usage ID and the usage limit amount are associated;
A consumption use ID receiving step for receiving a consumption use ID;
A usage limit change step for changing the usage limit associated with the consumption usage ID in the usage limit table according to the payment confirmation information associated with the received consumption usage ID;
On the card limit management server device,
The operation | movement method of the payment system with respect to the card | curd of Claim 9.

Images