JP6660223B2 - Transaction management device and transaction management method - Google Patents

Description

  The present invention relates to a transaction management device and a transaction management method.

  2. Description of the Related Art Systems for supporting the work of public relations officers such as financial institutions have become widespread. For example, there is a system including a server in a business office and a portable terminal carried by a person in charge of public relations. Then, in this system, information on business can be transmitted and received between the server and the mobile terminal, and a schedule can be referenced and transaction details can be input via the mobile terminal.

  Patent Literature 1 describes, in a business support system having a business support server and a mobile terminal, transmitting a visit plan list and personal information of a customer from the server to the mobile terminal.

JP 2013-69216 A

  In the above technology, it is described that distribution of plan information to support transactions and complete erasure of personal information after transactions to improve security, etc., are different from agents who are scheduled to be transactions It does not improve the credibility of the transaction itself, such as preventing the agent from proceeding, that is, preventing spoofing.

  An object of the present invention is to provide a technique capable of improving the convenience of a transaction while improving the reliability of the transaction.

The present application includes a plurality of means for solving at least a part of the above-described problems, and examples thereof are as follows. The transaction management device according to one aspect of the present invention, a storage unit that stores a predetermined transaction permission condition for a predetermined transaction, and accepts a reservation together with information that specifies a situation at the time of the predetermined transaction , said by determining the transaction reservation reception section you stored in the storage unit, receiving information identifying the situation in time of the transaction, the agreement between the information specifying the status stored in the storage unit at the time of the booking A normal transaction determination processing unit that determines whether or not the situation is satisfied, a transaction processing unit that processes the transaction when the situation is satisfied, and a signature processing unit that receives input of a handwritten signature by a trader in the process of processing the transaction. , equipped with, the transaction permission condition is, for each of the transaction, der ones to determine the maximum amount to be handled in the above transaction as a condition for permitting depending on the relationship between the account holder according to the above transactions The normal transaction determination processing unit, when not satisfy the conditions, whether the transaction is approved condition is satisfied, and determines to accept the relationship between the account holder relating to transactions of the trader, the transaction authorization if they meet the conditions to process the transaction in the transaction processing unit, does not meet the above situation, if you do not meet the above transactions permit conditions, it accepts a transaction approval of the account holder according to the transaction and the transaction processing unit the above transactions Ru is processing, it is characterized in.

Further, in the above transaction management device, a storage unit for storing a predetermined transaction permission condition for a predetermined transaction, and information for specifying a situation at the time of the predetermined transaction for a predetermined transaction, accepting a reservation, and The transaction reservation accepting unit stored in the unit and the information for specifying the situation at the time of the transaction are received, and the situation is satisfied by determining a match with the information for identifying the situation stored in the storage unit at the time of the reservation. A normal transaction determination processing unit that determines whether the transaction is completed, a transaction processing unit that processes the transaction when the above condition is satisfied, and a signature processing unit that receives input of a handwritten signature by a trader in the process of processing the transaction. The above-mentioned transaction licensing conditions, for each of the above-mentioned transactions, define the maximum amount of money to be handled in the above-mentioned transaction as a condition to be permitted according to the relationship with the account holder of the above-mentioned transaction. The normal transaction determination processing unit, when not satisfy the conditions, whether the transaction is approved condition is satisfied, and determines to accept the relationship between the account holder relating to transactions of the trader, the transaction authorization If the condition is satisfied, the transaction processing unit processes the transaction.If the condition is not satisfied and the transaction permission condition is not satisfied, a change in the amount handled in the transaction by the account holder of the transaction is involved. When the transaction approval is received, the transaction processing unit is made to process the transaction with the amount related to the change.

Further, in a transaction management method using a transaction management device according to another aspect of the present invention, the transaction management device includes a control unit and a storage unit, and the storage unit stores a predetermined transaction in advance. defined transaction permission condition is stored, the control unit receives a reservation together information for specifying a state at the time of the transaction for a given transaction, the transaction reservation accepting step of storing in the storage unit, at the time of the transaction A normal transaction determination step of receiving information specifying the situation and determining whether the situation is satisfied by determining a match with the information specifying the situation stored in the storage unit at the time of the reservation; and transaction processing step of processing the transaction if they meet, running, and signature processing step of accepting an input of a handwritten signature by traders in the process of the above transactions, taken the Permission condition, for each of the transactions, which defines the maximum amount to be handled in the transaction as a condition for permitting according to relationship between the account holder in accordance with the above transactions, the above normal transaction determination processing step, satisfy the conditions If no, whether the transaction is approved condition is satisfied, and determines to accept the relationship between the account holder relating to transactions of the trader, the transaction by the transaction processing steps in the case of satisfying the above transactions permission condition is processing, not satisfy the above conditions, if not met the transaction authorization condition, characterized in that to process the transaction by the transaction process step when receiving a transaction approval of the account holder in accordance with the transaction.

  ADVANTAGE OF THE INVENTION According to this invention, the convenience regarding a transaction can be improved, improving the reliability of a transaction.

  Problems, configurations, and effects other than those described above will be apparent from the following description of the embodiments.

It is a block diagram of a transaction management system concerning an embodiment. It is a figure showing the data structure stored in a transaction reservation storage part. FIG. 4 is a diagram illustrating a data structure stored in a schedule storage unit. FIG. 4 is a diagram illustrating a data structure stored in a signature storage unit. FIG. 4 is a diagram illustrating a data structure stored in a transaction history storage unit. It is a figure showing the data structure stored in a transaction permission condition storage part. It is a figure showing the example of hardware constitutions of a transaction management device. It is a figure showing the example of hardware constitutions of a liaison support terminal. It is a figure showing the flow of transaction application processing. It is a figure showing the flow of transaction processing. It is a figure showing an example of an output screen of transaction application processing. It is a figure showing another example of an output screen of transaction application processing. It is a figure showing the example of the output screen of transaction processing. It is a figure showing another example of an output screen of transaction processing. It is a figure showing still another example of an output screen of transaction processing. It is a figure showing still another example of an output screen of transaction processing.

  Hereinafter, an embodiment using a transaction management system 1 to which an embodiment according to the present invention is applied will be described with reference to the drawings.

  In general, there are a number of systems that require identity verification and / or approval.However, even with digital signatures based on handwriting input, there is a risk that the ability to prove evidence is relatively low, and this is a barrier to incorporating digital signatures into various systems. It has become.

  Previous efforts included increasing the amount of information related to digital signatures and improving the reliability of electronic signature data by improving the algorithm for determining the similarity of handwriting, and indirectly increasing the reliability of transactions. .

  By using the transaction management system 1 according to the present embodiment, the reliability of the transaction can be directly increased.

  FIG. 1 is a block diagram of a transaction management system 1 according to the present embodiment. The transaction management system 1 includes a transaction management device 100, a liaison support terminal 200 communicably connected to the transaction management device 100 via a network 50, and an account holder terminal 300 of an account holder such as a bank. Including. Note that the account holder terminal may be a terminal such as a smartphone that the account holder holds and uses regardless of the account.

  The network 50 is a communication network such as a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, and a mobile phone network. The network 50 may be a VPN (Virtual Private Network) or the like on a wireless communication network such as a mobile phone communication network.

  Transaction management device 100 is a so-called server device. However, the transaction management apparatus 100 is not limited thereto, and may be various types of information processing apparatuses such as a personal computer, a smartphone, a workstation, a PDA (Personal Data Assistant), and a tablet device.

  The transaction management device 100 receives a transaction reservation request from the account holder terminal 300 for a transaction relating to an account via the network 50. Further, transaction management apparatus 100 allocates a person in charge of external affairs based on a reservation for a transaction on a predetermined basis, and records schedule information of the person in charge of external affairs. Further, the transaction management device 100 determines whether or not the transaction is a reserved transaction at the place of the transaction, and if the transaction is a reserved transaction, establishes the transaction. In this process, if the account holder is not the account holder but the agent is participating as a business partner, the transaction management device 100 will use the agent's own handwriting input if the agent is a planned agent. Record the signature data.

  The public relations support terminal 200 is a terminal carried by a public relations officer, and is a so-called tablet device. However, the present invention is not limited to this, and the liaison support terminal 200 may be various information processing devices such as a personal computer, a smartphone, a workstation, and a PDA.

  Upon receiving an instruction to display and output a predetermined screen from the transaction management device 100 via the network 50, the liaison support terminal 200 performs output processing. Further, input information received from the input device and various sensors described below is transmitted to the transaction management device 100 via the network 50.

  The account holder terminal 300 is a terminal used by an account holder performing a transaction, and is a so-called smartphone device. However, the present invention is not limited to this, and the account holder terminal 300 may be various information processing devices such as a personal computer, a workstation, a PDA, and a tablet terminal.

  The account holder terminal 300 performs output processing when receiving an instruction to display and output a predetermined screen from the transaction management device 100 via the network 50. Also, the input information received from the input device is transmitted to the transaction management device 100 via the network 50.

  Transaction management device 100 includes a control unit 110, a storage unit 120, and a communication unit 130. The control unit 110 includes a transaction reservation receiving unit 111, a schedule interlocking processing unit 112, a normal transaction determination unit 113, a transaction processing unit 114, and a signature processing unit 115.

  The transaction reservation receiving unit 111 receives the transaction reservation information from the account holder terminal 300 via the network 50 and stores the transaction reservation information in the transaction reservation storage unit 121. That is, the transaction reservation receiving unit 111 receives a reservation for a predetermined transaction together with information for specifying the situation at the time of the transaction. Further, at this time, the transaction reservation receiving unit 111 receives information for specifying the agent of the account holder pertaining to the transaction as a transactor performing the transaction at the time of the transaction. In addition, the transaction reservation receiving unit 111 presents, as a proxy, a person who belongs to the eaves of the account holder as a candidate.

  The schedule interlocking processing unit 112 generates schedule information according to the transaction reservation, and causes the schedule storage unit 122 to store the schedule information. In addition, the schedule link processing unit 112 causes the schedule storage unit 122 to store the schedule so that it can be shared by the superior or manager of the person in charge of liaison related to the transaction reservation. Further, when accepting a reservation for a transaction, the schedule linkage processing unit 112 generates predetermined schedule information by designating a date and time related to the reservation. In addition, the schedule link processing unit 112 allocates a staff member who is in charge of the transaction, and shares the schedule information with the manager of the staff member.

  The normal transaction determination unit 113 determines whether or not the transaction is a normal transaction at the start of the transaction according to the transaction reservation received by the transaction reservation receiving unit 111. Note that a normal transaction is a transaction that is not different from the transaction content related to the reservation. More specifically, the normal transaction determination unit 113 determines whether the transaction satisfies a predetermined situation when determining whether the transaction is normal. In the processing, for example, as information for specifying the situation at the time of the transaction, it is confirmed whether or not the agent is a scheduled agent, or information on the position where the transaction is performed or information on the optical image of the transaction Is used to determine whether the situation is satisfied. This is to reduce the risk that a transaction is made in an unscheduled place or that a trader is impersonated by another person.

  Transaction processing unit 114 executes a predetermined business logic for each predetermined transaction. For example, the transaction processing unit 114 controls the start and end of programs related to various transactions such as payment, withdrawal, notification, and repayment.

  The signature processing unit 115 creates signature data using the input handwriting information. In addition, the signature processing unit 115 stores the signature data in the signature storage unit 123 for each signer who is a trader.

  The storage unit 120 includes a transaction reservation storage unit 121, a schedule storage unit 122, a signature storage unit 123, a transaction history storage unit 124, and a transaction permission condition storage unit 125.

  FIG. 2 is a diagram illustrating a data structure stored in the transaction reservation storage unit 121. The transaction reservation storage unit 121 includes a reservation identifier 121A, a subscriber identifier 121B, a customer name 121C, a desired transaction date and time 121D, a transaction execution place 121E, a transaction type 121F, a transaction 121G, a relationship 121H, The transaction amount 121J and the clothing 121K are stored in association with each other.

  The reservation identifier 121A is information for specifying a transaction reservation. The reservation person identifier 121B is information for specifying the person who made the reservation specified by the reservation identifier 121A. The customer name 121C is information for specifying the holder of the account to be traded. The desired transaction date and time 121D is a date and time when the transaction to be reserved specified by the reservation identifier 121A is performed. The transaction execution place 121E is a place where a transaction to be reserved specified by the reservation identifier 121A is performed.

  The transaction type 121F is information for specifying the type of transaction to be reserved specified by the reservation identifier 121A. The trader 121G is a person who performs a procedure in a transaction to be reserved specified by the reservation identifier 121A. Usually, it is assumed that the trader is the account holder, but the agent becomes the trader, for example, the account holder will not be present due to various circumstances, or it will be customarily performed by a related party. There is also.

  The relationship 121H is information for specifying a relationship with the account holder who is a customer for the trader specified by the trader 121G. The handling amount 121J is an amount handled in the transaction to be reserved specified by the reservation identifier 121A. The clothing 121K is information that specifies the color of the clothing of the agent when the person performing the procedure in the transaction to be reserved specified by the reservation identifier 121A is an agent. The information on the clothes 121K is not essential information for the transaction, but is auxiliary information that can be used when the reliability of the transaction is further increased.

  FIG. 3 is a diagram illustrating a data structure stored in the schedule storage unit 122. The schedule storage unit 122 stores schedule information of a public relations officer and other staff members. The schedule storage unit 122 includes a staff identifier 122A, a reservation identifier 122B, a date and time 122C, and a content 122D.

  The staff identifier 122A is information for identifying a staff including a person in charge of public relations. The reservation identifier 122B is information for identifying a schedule (event). The date and time 122C is information for specifying the date and time when the schedule identified by the reservation identifier 122B is performed. The content 122D is information for specifying the content to be identified by the reservation identifier 122B.

  FIG. 4 is a diagram illustrating a data structure stored in the signature storage unit 123. In the signature storage unit 123, a signer identifier 123A, signature data 123B, and a signature date and time 123C are stored in association with each other.

  The signer identifier 123A is information for identifying the signer. The signature data 123B is information of an electronic signature generated by a predetermined algorithm based on handwriting information input at the time of signature by the signer identified by the signer identifier 123A. The signature date and time 123C is information for specifying the date and time when the signer identified by the signer identifier 123A signed.

  FIG. 5 is a diagram showing a data structure stored in the transaction history storage unit 124. The transaction history storage unit 124 includes a transaction identifier 124A, a customer name 124B, a transaction end date and time 124C, a transaction execution place 124D, a transaction type 124E, a trader 124F, a transaction amount 124G, a handling staff 124H, Are stored in association with each other.

  The transaction identifier 124A is information for specifying a transaction. The customer name 124B is information for specifying the holder of the account to be traded. The transaction end date and time 124C is the date and time when the transaction specified by the transaction identifier 124A was performed. The transaction execution place 124D is a place where the transaction specified by the transaction identifier 124A is performed.

  The transaction type 124E is information that specifies the type of transaction specified by the transaction identifier 124A. The trader 124F has performed a procedure in the trade specified by the trade identifier 124A.

  The transaction amount 124G is the amount treated in the transaction specified by the transaction identifier 124A. The handling staff 124H is information for specifying the person in charge of external affairs in charge of the transaction specified by the transaction identifier 124A.

  FIG. 6 is a diagram showing a data structure stored in the transaction permission condition storage unit 125. The transaction permission condition storage unit 125 stores a trader 125A and a transaction type such as a report 125B, a deposit 125C, a repayment 125D, an account transfer 125E, a remittance in the organization 125F, and a remittance 125G outside the organization. . In the transaction permission condition storage unit 125, information having the above-described data structure is stored for each account holder so as to be editable from the account holder.

  The trader 125A is a person who is present at the place of the trade. The trader 125A in the present embodiment specifies the social relationship (person, spouse, first-degree family, housemate, employee, temporary agent, etc.) with the account holder, together with the information specifying the individual. Stored as possible. Transaction types such as a report 125B, a deposit 125C, a repayment 125D, an account transfer 125E, an internal remittance 125F, and an external remittance 125G are provided for each type of transaction. Is stored.

  The communication unit 130 performs communication with the external support terminal 200 and the account holder terminal 300, which are other devices, via the network 50.

  The liaison support terminal 200 includes a display unit 210, an input reception unit 220, a communication unit 230, a position acquisition unit 240, and an imaging unit 250. When the display unit 210 receives, from the communication unit 230, screen information in a predetermined format instructed to be displayed by the transaction management device 100, the display unit 210 draws the screen information on the display device. The input receiving unit 220 receives an input instruction from an operator of the liaison support terminal 200, for example, a liaison person, and transmits the instruction to the transaction management apparatus 100. The communication unit 230 communicates with the transaction management device 100, which is another device, via the network 50. When the display unit 210, the input receiving unit 220, and the communication unit 230 are combined, a so-called Internet browser function for controlling display of a Web page can be realized. The position obtaining unit 240 obtains information for specifying the position of the liaison support terminal 200. Specifically, the position obtaining unit 240 obtains coordinate information by surveying using a satellite radio wave such as a global positioning system (GPS) or a global navigation satellite system (GLONASS). Upon receiving the instruction, the imaging unit 250 senses a predetermined range of wavelengths using an imaging device such as a solid-state imaging device using CMOS (complementary metal oxide semiconductor) to generate image information.

  The account holder terminal 300 includes a display unit 310, an input receiving unit 320, and a communication unit 330. When receiving the screen information of a predetermined format instructed to be displayed by the transaction management device 100 from the communication unit 330, the display unit 310 draws the screen information on the display device. The input receiving unit 320 receives an input instruction from an operator of the account holder terminal 300, for example, an account holder, and transmits the instruction to the transaction management device 100. The communication unit 330 communicates with the transaction management device 100, which is another device, via the network 50. When the display unit 310, the input receiving unit 320, and the communication unit 330 are combined, a so-called Internet browser function for controlling display of a Web page can be realized.

  FIG. 7 is a diagram illustrating an example of a hardware configuration of the transaction management device 100. The transaction management device 100 includes an arithmetic device 102, an external storage device 103, a main storage device 104, an output device 105, a communication device 106, and a bus 107 connecting each device. In addition, the transaction management device 100 includes an input device 101.

  The arithmetic device 102 is an arithmetic device such as a CPU (Central Processing Unit).

  The external storage device 103 is a nonvolatile storage device that can store digital information, such as a so-called hard disk (Hard Disk Drive), an SSD (Solid State Drive), or a flash memory.

  The main storage device 104 is a memory device such as a RAM (Random Access Memory).

  The output device 105 is a display device such as a liquid crystal display and an organic EL (Electro Luminescence) display.

  The communication device 106 is a device such as a network card that establishes a communication path with other devices such as the liaison support terminal 200 and the account holder terminal 300 via the network 50 and transmits and receives information.

  The input device 101 is various input devices such as a keyboard, a mouse, and a touch panel.

  The input device 101, the arithmetic device 102, the external storage device 103, the main storage device 104, the output device 105, and the communication device 106 are connected to each other by a connection lead such as a bus 107.

  The transaction reservation receiving unit 111, the schedule link processing unit 112, the normal transaction determining unit 113, the transaction processing unit 114, and the signature processing unit 115 of the above-described transaction management device 100 are programs that cause the arithmetic device 102 to perform processing. It is realized by. This program is stored in the main storage device 104, the external storage device 103, or a ROM device (not shown), loaded on the main storage device 104 for execution, and executed by the arithmetic device 102.

  The storage unit 120 of the transaction management device 100 is realized by the main storage device 104 and the external storage device 103. The communication unit 130 of the transaction management device 100 is realized by the communication device 106. The hardware configuration example of the transaction management device 100 has been described above. Note that the account holder terminal 300 also has substantially the same configuration as the hardware configuration example shown in FIG.

  Each configuration of the transaction management device 100 and the account holder terminal 300 can be classified into more components according to the processing content. In addition, classification can be made such that one component executes more processing.

  In addition, each control unit may be configured by hardware (ASIC, GPU, or the like). Further, the processing of each control unit may be executed by one piece of hardware, or may be executed by a plurality of pieces of hardware.

  FIG. 8 is a diagram illustrating a hardware configuration example of the liaison support terminal 200. The communication support terminal 200 includes an arithmetic device 202, an external storage device 203, a main storage device 204, an output device 205, a communication device 206, a bus 207 connecting the devices, a position information acquisition device 208, an imaging device 209 at least. In addition, the liaison support terminal 200 includes an input device 201.

  The arithmetic device 202 is, for example, an arithmetic device such as a CPU. The external storage device 203 is a nonvolatile storage device such as a so-called hard disk, SSD, or flash memory that can store digital information. The main storage device 204 is a memory device such as a RAM, for example. The output device 205 is a display device such as a liquid crystal display and an organic EL display. The communication device 206 is a device such as a network card that establishes a communication path with other devices such as the transaction management device 100 and the account holder terminal 300 via the network 50 and transmits and receives information.

  The input device 101 is various input devices such as a keyboard, a mouse, and a touch panel.

  The input device 201, the arithmetic device 202, the external storage device 203, the main storage device 204, the output device 205, the communication device 206, the position information acquisition device 208, and the imaging device 209 are connected to a bus 207 or the like. The wires are connected to each other.

  The display unit 210, the input receiving unit 220, and the communication unit 230 of the above-described liaison support terminal 200 are realized by a program that causes the arithmetic device 202 to perform processing. This program is stored in the main storage device 204, the external storage device 203, or a ROM device (not shown), loaded on the main storage device 204 for execution, and executed by the arithmetic device 202.

  The communication unit 230 of the liaison support terminal 200 is realized by the communication device 206. The position acquisition unit 240 of the liaison support terminal 200 is realized by the position information acquisition device 208. The imaging unit 250 of the liaison support terminal 200 is realized by the imaging device 209. The hardware configuration example of the liaison support terminal 200 has been described above.

  The configuration of the liaison support terminal 200 can be classified into more components according to the processing content. In addition, classification can be made such that one component executes more processing.

  In addition, each control unit may be configured by hardware (ASIC, GPU, or the like). Further, the processing of each control unit may be executed by one piece of hardware, or may be executed by a plurality of pieces of hardware.

  [Description of Operation] Next, the operation of the transaction management system 1 in the present embodiment will be described.

  FIG. 9 is a diagram showing a flow of the transaction application processing. The transaction application process is started when a user such as an account holder obtains a transaction reservation instruction from the account holder terminal 300. The transaction application process is started not only in the case where an instruction for transaction reservation is obtained from the account holder terminal 300 but also in the case where an instruction is obtained from the liaison support terminal 200 or other various terminals (not shown).

  First, the transaction reservation receiving unit 111 of the transaction management device 100 receives a request for a transaction reservation (Step S001). Specifically, the transaction reservation receiving unit 111 receives information on transaction reservation.

  The information related to the reservation of the transaction includes the name of the customer (name holder of the account to be transacted), information specifying the desired date and time of the transaction, information specifying the place where the transaction is performed, and specifying the type of the transaction. Information, information on the trader who attends the transaction, transaction clothing color information that specifies the color of the trader's clothing at the time of the transaction, and information that specifies the transaction amount. However, the present invention is not limited to this, and it suffices if information that specifies the details of the transaction and the attendees is included. For example, information on the place of exchange or clothes may not be included.

  Then, the transaction reservation receiving unit 111 determines whether or not the trader is a temporary agent (Step S002). Specifically, the transaction reservation accepting unit 111 is a temporary agent when the transaction is not the account holder and is not a member of the eaves for the transaction accepted in step S001. Is determined. The eave is a unit corresponding to an address and treating a family living at the address as one group. If the agent is not a temporary agent, the transaction reservation accepting unit 111 proceeds to step S005 described below.

  If the trader is a temporary agent (“Yes” in step S002), the transaction reservation accepting unit 111 transmits a temporary agent setting screen (step S003). Specifically, the transaction reservation receiving unit 111 generates a temporary agent setting screen according to a predetermined layout as shown in FIG. 12 described later, and transmits it to the account holder terminal 300.

  Then, the transaction reservation receiving unit 111 receives the temporary agent information (Step S004). Specifically, the transaction reservation receiving unit 111 receives a relationship between the name of the temporary agent and the account holder of the temporary agent.

  Next, the transaction reservation receiving unit 111 assigns a handling staff (step S005). Specifically, the transaction reservation receiving unit 111 assigns staff members in charge of negotiation of the transaction by using an algorithm such as a predetermined priority.

  Then, the transaction reservation receiving unit 111 records the transaction reservation, and the schedule link processing unit 112 records the staff schedule (step S006). Specifically, the transaction reservation receiving unit 111 causes the transaction reservation storage unit 121 to store the information on the transaction reservation and the information of the temporary agent. Further, the schedule link processing unit 112 generates and stores schedule information related to the transaction in the schedule storage unit 122 of the handling staff. The schedule information is also stored in the schedule storage unit 122 of the manager of the handling staff or the manager, so that the schedule information can be shared.

  The above is the flow of the transaction application processing. According to the transaction application process, it is possible to reserve a transaction using the terminal of the account holder, so that it can be said that convenience is improved.

  FIG. 10 is a diagram showing a flow of the transaction processing. The transaction processing is started when a request for starting processing relating to the transaction is received from the liaison support terminal 200.

  First, the transaction processing unit 114 receives date and time or customer information (step S101). Specifically, the transaction processing unit 114 receives, from the liaison support terminal 200, the date and time of the transaction or the customer information of the account holder performing the transaction.

  Then, the transaction processing unit 114 specifies one or more transactions of the eaves using the date or the customer information (step S102). Specifically, the transaction processing unit 114 searches the transaction reservation storage unit 121 using the date and time or the customer information received in step S101 as a search key, and specifies one or a plurality of transactions of the eaves to which the corresponding customer belongs. I do.

  Then, the normal transaction determination unit 113 determines whether the transaction environment (date and time, place, clothes, etc.) is as planned or the transaction is within the permitted conditions (step S103). Specifically, the normal transaction determination unit 113 determines whether or not the transaction environment satisfies the content applied for in the transaction application process. It is determined whether or not the transaction is within the upper limit. For example, the normal transaction determination unit 113 receives the input of the customer name, the trader, the transaction type, the transaction amount, and the like in step S103 and compares the input with the transaction schedule. Whether the transaction is fulfilled, whether the transaction location satisfies the transaction location, whether the transaction to be performed is included in the transaction type, whether the transaction is on schedule, whether the transaction amount is within the transaction amount, It is determined whether the base color of the person's clothes is as expected.

  To specify the transaction location, the normal transaction determination unit 113 receives the position information acquired by the position acquisition unit 240 of the liaison support terminal 200. Then, the normal transaction determination unit 113 determines whether or not the coordinates specified by the position information are included in the range of the planned place.

  In addition, in specifying the color that is the base color of the clothes of the trader, the normal transaction determination unit 113 converts the color in a predetermined range in the video information related to the figure of the trader acquired by the imaging unit 250 of the liaison support terminal 200. Identify using

  Then, if the transaction environment is not as scheduled, the normal transaction determination unit 113 determines whether or not there is an input in step S103 according to the transaction and the type of transaction, otherwise, the normal transaction determination unit 113 determines whether the transaction is According to the type of transaction, the transaction amount as the upper limit of the transaction permission condition storage unit 125 is read, and if the transaction falls within the transaction amount, it is determined that the transaction is within the permission condition.

  If the transaction environment is not as planned and the transaction is not within the permission conditions (“No” in step S103), the normal transaction determination unit 113 performs the process of step S109 described below. If the transaction execution is not approved, the control proceeds to step S108 described below. If the transaction execution has been approved, the control proceeds to step S104.

  When the transaction environment is as planned or the transaction is within the permission conditions (“Yes” in step S103), or when the transaction execution is approved (“Yes” in step S109) The transaction processing unit 114 performs a transaction process (step S104). Then, the transaction processing unit 114 determines whether or not all transaction processing for the eaves has been completed (step S105). If all the transactions for the eaves specified in step S102 have not been completed ("No" in step S105), the transaction processing unit 114 returns the control to step S104.

  If all transaction processing for the eaves has been completed ("Yes" in step S105), the signature processing unit 115 starts accepting a signature input (step S106). Then, the signature processing unit 115 generates signature data based on the received signature input by using a predetermined algorithm, and also generates screen display information in which the past signature of the signer is described (step S107). In order to add the past signature, the signature processing unit 115 reads a record with a new signature date and time for the signer from the signature storage unit 123 and uses the signature data.

  Then, the signature processing unit 115 updates the signature, and the transaction processing unit 114 records the details of the transaction in the transaction history (step S108). Specifically, the signature processing unit 115 adds the signature data received in step S106 to the signature storage unit 123, and the transaction processing unit 114 adds the details of the transaction to the transaction history storage unit 124.

  If the transaction environment is not as planned and the transaction is not within the permission conditions (“No” in step S103), the normal transaction determination unit 113 sets the transaction information (transaction type, The transaction information (including the handling amount) and the agent information (transactioner information) are transmitted to the account holder terminal 300, and an inquiry is made as to whether or not to approve the transaction (step S109). Specifically, the normal transaction determination unit 113 transmits the transaction information and the agent information to the account holder terminal 300, and approves the transaction execution, changes the amount, approves the transaction, or denies the transaction. , Get one of the answers. Note that, when obtaining an answer that the amount is changed and approved, the normal transaction determination unit 113 also receives the changed amount, and corrects and transfers the amount to the transaction processing unit 114.

  The above is the flow of the transaction processing. According to the transaction processing, the transaction matching with the schedule or the transaction processing in a predetermined range can be performed using the liaison support terminal 200, so that the transaction with higher reliability can be executed.

  FIG. 11 is a diagram illustrating an example of an output screen of the transaction application process. An example of an output screen of the transaction application process is a transaction application screen 400. The transaction application screen 400 is a screen for generating data of a request accepted in step S001 of the transaction application process. In the transaction application screen 400 according to the present embodiment, the Internet browser of the account holder terminal 300 performs event control, but the present invention is not limited to this. What is necessary is just to perform.

  On the transaction application screen 400, a customer name 401, a desired transaction date 402, a transaction time 403, a transaction place selection 404, a transaction type selection 405, a transaction selection 406, a transaction clothing color selection 407, a transaction amount, 408). Further, transaction application screen 400 displays an application instruction reception button 409, a transaction application addition instruction reception button 410, and a return button 411.

  When the application instruction reception button 409 receives an input, the browser creates transaction request data using the information input in the input reception area and transmits the data to the transaction management device 100. When the transaction application addition instruction reception button 410 receives an input, the browser creates the transaction application request data using the information input in the input reception area, and displays a new input reception area to display an additional transaction application. Accept. When the return button 411 receives the input, the browser returns the process to the screen before the transaction application screen 400 is displayed.

  FIG. 12 is a diagram illustrating another output screen example of the transaction application process. Another output screen example of the transaction application process is a temporary proxy setting screen 450. The temporary agent setting screen 450 is a screen for receiving the temporary agent setting transmitted in step S003 of the transaction application process. In the temporary agent setting screen 450 in the present embodiment, it is assumed that the Internet browser of the account holder terminal 300 performs event control. However, the present invention is not limited to this. Can be used as long as it performs control.

  On the temporary agent setting screen 450, an input receiving area for the customer name 451, the temporary agent name 452, the relationship with the customer 453, and whether or not to register in the template of the transaction permission condition storage unit 125 are selected. And a template addition instruction input area 454 for inputting. Further, on temporary agent setting screen 450, an application instruction reception button 459, a transaction application addition instruction reception button 460, a template edit button 461, and a return button 462 are displayed.

  When the template addition instruction input area 454 accepts an input, the browser alternatively accepts as an input to select whether or not to register the template. When the application instruction reception button 459 receives an input, the browser creates request data for the transaction application using the information input in the input reception area and transmits the data to the transaction management device 100. When the transaction application addition instruction reception button 460 receives an input, the browser creates the transaction application request data using the information input in the input reception area and displays a new input reception area to display an additional transaction application. Accept. Here, in the case where an input to be registered in the template is received in the template addition instruction input area 454, the transaction reservation receiving unit 111 uses the information input in the input receiving area to store in the transaction permission condition storage unit 125. Store information as a new trader. When the button 461 for editing the template receives an input, the browser calls a screen that realizes a function of displaying, modifying, and deleting data stored in the transaction permission condition storage unit 125. When the return button 462 receives the input, the browser returns the processing to the screen before the temporary agent setting screen 450 is displayed.

  FIG. 13 is a diagram illustrating an example of an output screen of the transaction processing. An example of an output screen of the transaction processing is a signature input screen 500. The signature input screen 500 is a screen for transmitting the input information of the handwriting accepted in step S106 of the transaction processing to the transaction management apparatus 100. In the signature input screen 500 in the present embodiment, it is assumed that the Internet browser of the liaison support terminal 200 performs event control, but the present invention is not limited to this, and the liaison support terminal 200 performs control according to the implementation format. Anything should do.

  The signature input screen 500 includes a transaction content display area 501 for displaying information including a customer name, a signer, a transaction, and a transaction amount, and a signature field 502 for receiving handwriting input data. The signer displays the name of the person who has been set in advance in the transaction reservation as the signer or, if input in step S103, the name of the trader. Further, on the signature input screen 500, a return button 503 and a signature confirmation instruction acceptance button 504 are displayed.

  When the signature field 502 receives a handwritten input, the browser starts a process of receiving the input as handwriting data. When the signature confirmation instruction reception button 504 receives an input, the browser transmits the handwriting data input in the signature field 502 to the transaction management device 100. When the return button 503 receives the input, the browser returns the process to the screen before the signature input screen 500 is displayed.

  FIG. 14 is a diagram illustrating another output screen example of the transaction processing. Another output screen example of the transaction processing is a multiple transaction signature screen 600. The multiple transaction signature screen 600 is a screen for transmitting the input information of the handwriting accepted in step S <b> 106 of the transaction processing to the transaction management apparatus 100 when performing multiple transactions collectively. In the multiple transaction signature screen 600 in the present embodiment, it is assumed that the Internet browser of the liaison support terminal 200 performs event control. However, the present invention is not limited to this. Anything can be performed.

  The multiple transaction signature screen 600 includes a transaction content display area 601 for displaying information including a customer name, a transaction, a transaction amount, and a signer for a plurality of transactions, and a signature field 602 for receiving handwriting input data. Prepare. The signer displays the name of the person who has been set in advance in the transaction reservation as the signer or, if input in step S103, the name of the trader. Further, on the multiple transaction signature screen 600, a return button 603 and a signature confirmation instruction acceptance button 604 are displayed.

  When the signature field 602 receives a handwritten input, the browser starts a process of receiving the input as handwriting data. When the signature confirmation instruction reception button 604 receives an input, the browser transmits the handwriting data input in the signature field 602 to the transaction management device 100. When the return button 603 receives the input, the browser returns the process to the screen before the multiple transaction signature screen 600 is displayed.

  FIG. 15 is a diagram showing still another output screen example of the transaction processing. Another output example of the transaction processing is a transaction approval / rejection screen 700. The transaction approval / rejection screen 700 displays the transaction management device 100 in step S109 of the transaction processing when the content is different from the reserved transaction or when a transaction that does not satisfy the predetermined condition is going to be performed. This is a screen to be transmitted to the server 300. In the transaction denial screen 700 according to the present embodiment, the Internet browser of the account holder terminal 300 controls the event, but the present invention is not limited to this. What is necessary is just to perform.

  The transaction approval / rejection screen 700 includes a transaction content display area for displaying information including a customer name 701, a trader 702, transaction details 703, a transaction amount 704, and a description 705 for prompting a predetermined approval / denial operation input. A transaction approval button 706 for receiving an instruction input for approving the transaction, a change amount setting instruction reception button 707 for receiving an instruction input for approving the transaction under the condition for changing the amount, and a transaction rejection instruction reception button 708 for receiving an instruction input for denying the transaction. And an input reception area of

  When the browser of account holder terminal 300 receives the instruction input on transaction approval button 706, it transmits the transaction approval information to transaction management apparatus 100. When the browser receives an instruction input on transaction rejection instruction reception button 708, the browser transmits transaction rejection information to transaction management device 100. When the browser receives an instruction input to change amount setting instruction reception button 707, the browser transmits a request for display information of amount change approval screen 750 to transaction management device 100.

  FIG. 16 is a diagram showing still another output screen example of the transaction processing. Yet another output screen example of the transaction processing is an amount change approval screen 750. The amount change approval screen 750 displays the transaction management device 100 in step S109 of the transaction process when the content is different from the reserved transaction or when a transaction that does not satisfy the predetermined condition is going to be performed. 4 is a screen transmitted to the terminal 300. Note that, in the amount change approval screen 750 in the present embodiment, the Internet browser of the account holder terminal 300 performs event control. However, the present invention is not limited to this. What is necessary is just to perform control.

  On the amount change approval screen 750, a transaction content display area for displaying the customer name 751, the trader 752, and the transaction content 753 for the transaction, a change amount input area 754 where the browser accepts the input of the change in the transaction amount, and The browser displays an amount change approval button 755 for accepting an instruction input for the browser to transmit the transaction approval information to the transaction management device 100 together with the transaction amount input to the change amount input area 754, and the browser displays an amount change approval screen 750. A return instruction reception button 756 for receiving an instruction input for returning to the immediately preceding screen is provided.

  The transaction management system 1 to which the embodiment according to the present invention is applied has been described above. According to this embodiment, the convenience of the transaction can be improved while improving the reliability of the transaction.

  The present invention is not limited to the above embodiment. The above embodiment can be variously modified within the scope of the technical idea of the present invention. For example, in the above embodiment, in order to confirm the legitimacy of the transaction, the contents of the transaction, the trader, and the transaction place are set in advance, but the present invention is not limited to this. For example, in addition to the above, an oral password including whether or not a trader's voiceprint is similar to a preregistered voiceprint, a trader's retina authentication, a physical IC card or memory reading authentication, a fingerprint authentication, etc. The legitimacy of the agent may be confirmed in association with various security confirmation elements.

  Further, for example, the legitimacy of a staff member in charge of public affairs may be confirmed. For example, it may be determined in advance whether or not an IC card (such as an identifiable certificate) possessed by a staff member corresponds to that of a staff member who is to be in charge of the transaction. The transaction processing may be started only when a notice is given to the user and the approval is obtained. By doing so, it is possible to prevent impersonation, fictitious transactions, and moral hazard of staff.

  Further, for example, the liaison support terminal 200 is not limited to the one that communicates with the transaction management device 100 in real time. For example, a part of the transaction is performed on the terminal without communication, and the transaction management is performed on the unprocessed part. It may be executed when communicating with the device 100. In this case, the past signature data by the trader is also taken in when taking the transaction schedule into the liaison support terminal. In the case of a custody operation, the liaison support terminal 200 can output form data, such as a custody slip, for certifying that the custody has been taken from a printer or the like connected to the liaison support terminal 200.

  Further, the technical elements of the above-described embodiments may be applied independently, or may be applied by being divided into a plurality of parts such as a program component and a hardware component.

  As described above, the present invention has been described centering on the embodiments.

DESCRIPTION OF SYMBOLS 1 ... Transaction management system, 50 ... Network, 100 ... Transaction management apparatus, 110 ... Control part, 111 ... Transaction reservation reception part, 112 ... Schedule interlocking processing part, 113 ...・ Normal transaction determination unit, 114 ・ ・ ・ Transaction processing unit, 115 ・ ・ ・ Signature processing unit, 120 ・ ・ ・ Storage unit, 121 ・ ・ ・ Transaction reservation storage unit, 122 ・ ・ ・ Schedule storage unit, 123 ・ ・ ・Signature storage unit, 124: Transaction history storage unit, 125: Transaction permission condition storage unit, 130: Communication unit, 200: External support terminal, 210: Display unit, 220: Input Reception unit, 230: communication unit, 240: position acquisition unit, 250: imaging unit, 300: account holder terminal, 310: display unit, 320: input reception unit, 330: ..Communication section

Claims (4)

A storage unit for storing a predetermined transaction permission condition for a predetermined transaction,
A transaction reservation receiving unit for receiving a reservation together with information for specifying a situation at the time of the predetermined transaction, and storing the reservation in the storage unit;
A normal transaction determination processing unit that receives information specifying the situation at the time of the transaction, and determines whether the situation is satisfied by determining a match with the information specifying the situation stored in the storage unit at the time of the reservation. When,
A transaction processing unit that processes the transaction when the situation is satisfied;
A signature processing unit that receives an input of a handwritten signature by a trader in the processing process of the transaction;
With
The transaction permission condition is, for each transaction, an upper limit amount to be handled in the transaction as a condition permitted according to a relationship with an account holder related to the transaction,
The normal transaction determination processing unit, when the situation is not satisfied, determines whether or not the transaction permission condition is satisfied, by receiving a relationship with an account holder related to the transaction of the trader, and determines the transaction permission condition. When satisfying, let the transaction processing unit process the transaction,
If the condition is not satisfied and the transaction permission condition is not satisfied, the transaction processing unit causes the transaction processing unit to process the transaction when accepting the transaction approval of the account holder related to the transaction.
A transaction management device, characterized in that: A storage unit for storing a predetermined transaction permission condition for a predetermined transaction,
A transaction reservation receiving unit for receiving a reservation together with information for specifying a situation at the time of the predetermined transaction, and storing the reservation in the storage unit;
A normal transaction determination processing unit that receives information specifying the situation at the time of the transaction, and determines whether the situation is satisfied by determining a match with the information specifying the situation stored in the storage unit at the time of the reservation. When,
A transaction processing unit that processes the transaction when the situation is satisfied;
A signature processing unit that receives an input of a handwritten signature by a trader in the processing process of the transaction;
With
The transaction permission condition is, for each transaction, an upper limit amount to be handled in the transaction as a condition permitted according to a relationship with an account holder related to the transaction,
The normal transaction determination processing unit, when the condition is not satisfied, determines whether the transaction permission condition is satisfied, by receiving a relationship with an account holder related to the transaction of the trader, and determines the transaction permission condition. When satisfying, let the transaction processing unit process the transaction,
If the condition is not satisfied and the transaction permission condition is not satisfied, the transaction processing unit pertains to the transaction by accepting a transaction approval involving a change in the amount handled in the transaction by the account holder pertaining to the transaction. To be processed by the amount,
A transaction management device, characterized in that: A transaction management method using a transaction management device,
The transaction management device includes a control unit and a storage unit,
The storage unit stores predetermined transaction permission conditions for a predetermined transaction,
The control unit includes:
Accepting the reservation together information for specifying a state at the time of the transaction for a given transaction, the transaction reservation accepting step of storing in the storage unit,
A normal transaction determination step of receiving information identifying the situation at the time of the transaction and determining whether the situation is satisfied by determining a match with the information identifying the situation stored in the storage unit at the time of the reservation ; ,
A transaction processing step of processing the transaction when the situation is satisfied;
A signature processing step of receiving an input of a handwritten signature by a trader in the processing of the transaction;
Run
The transaction permission condition is, for each transaction, an upper limit amount to be handled in the transaction as a condition permitted according to a relationship with an account holder related to the transaction,
In the normal transaction determination step, when the condition is not satisfied, whether or not the transaction permission condition is satisfied is determined by receiving a relationship with an account holder related to the transaction of the trader, and the transaction permission condition is determined. If satisfied, the transaction is processed by the transaction processing step ,
If the condition is not satisfied and the transaction permission condition is not satisfied, the transaction processing step causes the transaction to be processed by receiving the transaction approval of the account holder related to the transaction.
A transaction management method comprising:   A transaction management method using a transaction management device,
  The transaction management device includes a control unit and a storage unit,
  The storage unit stores predetermined transaction permission conditions for a predetermined transaction,
  The control unit includes:
  A transaction reservation receiving step of receiving a reservation together with information specifying a situation at the time of the predetermined transaction, and storing the reservation in the storage unit;
  A normal transaction determination processing step of receiving information identifying the situation at the time of the transaction and determining whether the situation is satisfied by determining a match with the information identifying the situation stored in the storage unit at the time of the reservation When,
  A transaction processing step of processing the transaction when the situation is satisfied;
  A signature processing step of receiving an input of a handwritten signature by a trader in the processing of the transaction;
  Run
  The transaction permission condition is, for each transaction, an upper limit amount to be handled in the transaction as a condition permitted according to a relationship with an account holder related to the transaction,
  In the normal transaction determination processing step, when the condition is not satisfied, whether or not the transaction permission condition is satisfied is determined by receiving a relationship with an account holder related to the transaction of the trader, and the transaction permission condition is determined. If the condition is satisfied, the transaction is processed by the transaction processing step,
  If the condition is not satisfied and the transaction permission condition is not satisfied, the transaction processing step relates to the transaction by the transaction processing step when accepting a transaction approval involving a change in the amount handled in the transaction by the account holder pertaining to the transaction. To be processed by the amount,
  A transaction management method characterized in that:

Images