JP2018160119A - Form transaction machine - Google Patents

Abstract

PROBLEM TO BE SOLVED: To read an input form and check a desired transaction in the past transaction history.SOLUTION: A form transaction apparatus that conducts a transaction using a form with a user includes: a form reading unit that reads an input form; and a control unit for outputting transaction information on a selected item of a transaction history to a display unit, based on an item selected by the user via an operation unit among items included in the input form and the past transaction history of the user.SELECTED DRAWING: Figure 8

Description

  The present invention relates to a history display method for a form transaction apparatus.

  In an automatic transaction apparatus (ATM) of a financial institution, it is possible to perform various transactions such as a withdrawal transaction and a deposit transaction, and a user can manage by entering these transaction histories in a passbook.

  However, if the user does not have a passbook, the transaction history cannot be entered, so the transaction history cannot be confirmed. In addition, all transaction histories are entered in the passbook in order of date, and if you want to confirm a specific transaction history, you have to look for it visually, which is troublesome. It is convenient for the user that the transaction history can be confirmed even when the bankbook is not held and the specific transaction history can be confirmed.

  For example, in an environment in which an automatic transaction apparatus and a financial institution server are connected via a network, an inquiry is made to the financial institution server that stores the user's transaction history information based on the user's cash card information. A method of displaying the transaction history information on the display of an automatic transaction apparatus has been proposed (see Patent Document 1).

JP 2004-234434 A

  In the prior art described in Patent Document 1, as described above, the user can confirm the latest transaction history information only with a cash card. Recently, however, the types of transaction services handled by automatic transaction devices are increasing, and some financial institutions have installed automatic transaction devices (hereinafter referred to as “form transaction devices”) that have devices for reading tax and utility bill payment forms. ing. In the case of a transaction performed using the payment form (hereinafter referred to as a payment transaction), depending on the user, a transaction may be performed periodically for a plurality of types of payment forms. In this case, there is a possibility that the transaction history information to be confirmed does not fall within the latest target range and cannot be confirmed. In addition, even if it is within the scope of the latest transaction history information, if you want to confirm specific transaction history information, for example, payment transaction information where the payment destination is a gas company, you need to search from a large number of transaction history information, Annoying for users.

  The present invention has been made in view of the above, and an object thereof is to provide a form transaction apparatus that can read an input form and confirm a desired transaction in a past transaction history.

  In order to solve the above-described problems and achieve the object, the form transaction apparatus according to the present invention is a form transaction apparatus that performs a transaction using a form with a user, and a form reading unit that reads an input form And the transaction for the selected item of the transaction history based on the item selected by the user from the operation unit among the items included in the input form and the transaction history of the user in the past. And a control unit that outputs information to the display unit.

  According to the present invention, a desired transaction can be confirmed in the past transaction history by reading the input form.

External view of form transaction device System configuration diagram and control block diagram of form transaction device Host server customer account information data table Host server customer transaction information data table Payment server data table of content server Sample payment form Flow chart showing the process up to payment history inquiry process in the form transaction device Detailed flow chart of form history inquiry in form transaction device Payment history inquiry selection screen display example in a form transaction device Payment destination selection screen display example in a form transaction device Example of the transaction history list screen display in the form transaction device Example of payment list selection screen display in form transaction device Payment form image screen display example in form transaction device

  Hereinafter, with reference to FIGS. 1-13, the form transaction apparatus employ | adopted for financial institution systems, such as a bank system, in this embodiment is demonstrated. In the following, the case where the history inquiry system and the history inquiry method are applied to a form transaction apparatus is illustrated, but the present invention can be applied to various apparatuses having similar functions.

  FIG. 1 is an external view of a form transaction apparatus (hereinafter referred to as STM (Store Tellers Machine)) 1 according to this embodiment, and FIG. 2 is a diagram in which STM1, a host server, and a content server are connected via a communication network. It is a system configuration diagram and a control block diagram.

  The STM 1 is an apparatus that is installed in a financial institution or the like and automatically executes transactions such as a withdrawal transaction, a deposit transaction, and a payment transaction by a user operation. As shown in FIGS. 1 and 2, the STM 1 has an operation unit 2 that allows a user to display transaction contents and operation procedures and perform operations. It comprises a deposit / withdrawal mechanism unit 6, a coin deposit / withdrawal mechanism unit 7, a form reading mechanism unit 8, a receipt output mechanism unit 9, and a control unit 3 for controlling these units.

  The control unit 3 includes a hardware configuration such as a CPU and a memory, and a software configuration such as a program and data, and controls various processes and transactions. Since the card / detail slip mechanism unit 4, the passbook mechanism unit 5, the banknote deposit / withdrawal mechanism unit 6, and the coin deposit / withdrawal mechanism unit 7 have a conventionally known general configuration, description thereof is omitted here. The form reading mechanism unit 8 includes a scanner unit, reads information on the payment form inserted from the insertion slot, and generates and stores an image file of the payment form. The receipt output mechanism unit 9 prints and outputs the image file of the previous payment form and transaction information on the receipt. In the communication unit 10, the STM 1 is connected to each of the host server 11 and the content server 17 via a network, and communicates customer transaction information, payment form information, and the like.

  The host server 11 includes a control unit 12, a communication unit 13, and a storage unit 14. The control unit 12 includes a CPU, a memory, and the like, and controls processing of the host server. The communication unit 13 communicates STM1 with customer transaction information and the like. The storage unit 14 stores customer account information 15 and customer transaction information 16.

  The content server 17 includes a control unit 18, a communication unit 19, and a storage unit 20. The control unit 18 includes a CPU, a memory, and the like, and controls processing of the content server. The communication unit 19 communicates the STM 1 with payment form information and the like. The storage unit 20 stores payment form information 21 and a payment form image 22 of the read payment form.

  3 is a data table of customer account information 15 stored in the storage unit 14 of the host server 11, and FIG. 4 is a data table of customer transaction information 16 stored in the storage unit 14 of the host server 11. is there. As shown in FIG. 3, the customer account information 15 stores information such as account number, subject, balance, name, date of birth, address, and telephone number. The customer transaction information stores information such as transaction date / time, account number, subject, transaction type, transaction amount, and payment destination.

  In FIG. 3, for example, an account number 321 -89865 of the savings account is an account of Hanako Tanaka who lives in Tokyo, and indicates that the balance is 1,234,567 yen. In addition, Hanako Tanaka's date of birth is September 9, 1990, indicating that the contact information is 03-4567-8901. Thus, the customer account information 15 stores information related to the STM1 user account.

  In addition, in FIG. 4, at 8:46:10 on October 25, 2016, from the account number 321-89865 (account of Hanako Tanaka) of the savings account, 10,000 yen as a gas fee for XX gas Indicates that the payment has been made. As described above, the customer transaction information 16 stores information related to transactions of users of the STM1.

  FIG. 5 shows the payment form data 21 stored in the storage unit 20 of the content server 17. As shown in FIG. 5, the payment form data 21 stores information such as transaction date, payment deadline, payment destination / transfer destination account number, payment destination, name, transaction amount, form type, form image file name, and the like. . As will be described later, the payment form data is actually stored in association with these pieces of information in association with the form image file name.

  In FIG. 5, the payment deadline for the payment form addressed to XX Gas that Hanako Tanaka traded with the payment form at 8:46:10 am on October 25, 2016 is November 14, 2016 The account number of the payee is 3170-3-225, and the transaction amount is 10,000 yen. Also, the image of the payment form at this time is 02.02. It is stored as Jpeg. As described above, the payment form data 21 stores information related to the form when the transaction is made by the user of the STM1.

  FIG. 6 is a sample payment form. As shown in FIG. 6, the payment form includes items such as payment destination 1, payment destination / transfer destination account number 2, transaction amount 3, payment deadline 4, name 5, and the like. Is read and stored as the payment form data 21 shown in FIG. Since these items are the same as those shown in FIG. 5, the description thereof is omitted here, but in FIG. 6, Hanako Tanaka was at 8:46:10 on October 25, 2016. It can be seen that the payment form at the time of the transaction is stored as the payment form data 21.

  Next, the payment transaction history inquiry processing flow performed by STM1 will be described with reference to FIGS. The process shown in FIG. 7 is a flow from when the user inserts the payment form into the insertion slot of STM1 until the payment history inquiry process is performed.

  When the user starts a transaction, first, the control unit 3 displays a form insertion screen on the operation unit 2 of the STM 1 (S701). On the form insertion screen, for example, a message prompting insertion of a form such as “Please insert your form” is displayed. When the user inserts a payment form into the form reading mechanism unit 8 of STM1, the form reading mechanism unit 8 detects the inserted payment form (S702) and reads the information of the payment form (S703).

  Next, the control unit 3 temporarily stores the read payment form data and the payment form image file in a memory (not shown) in the control unit 3 (S704). The control unit 3 transmits the stored payment form data and the payment form image file to the content server 17 via the communication unit 10 (S705), and the content server 17 sends the received data to the payment form information 21 of the storage unit 20 and The payment form image 22 is stored.

  Next, the control unit 3 displays a payment transaction selection screen as shown in FIG. 9 on the operation unit 2 of the STM 1 (S706). On the payment transaction selection screen, a button 901 for performing a payment transaction and a button 902 for performing a history inquiry of the payment transaction are displayed (FIG. 9). When the operation unit 2 detects that a button for performing a payment transaction is pressed (S707; No), a payment transaction process is performed by notifying the control unit 3 (S708). Since the contents of the payment transaction process are not related to the present embodiment, the description thereof is omitted here. When the operation unit 2 detects that a button for making a transaction transaction history inquiry is pressed (S707; Yes), a payment history inquiry process is performed by notifying the control unit 3 (S709).

The process shown in FIG. 8 is the details of the payment history inquiry process shown in S709 of FIG.
First, the control unit 3 inputs a telephone number to the operation unit 3 of the STM 1 in order to specify a user (S801). For example, a message prompting the user to enter a telephone number is displayed on the operation unit 3 such as “Please enter your telephone number”. Here, although inputting a telephone number is illustrated, it is not restricted to this, For example, it can also consider inputting a birth date, an address, etc.

  Next, the control unit 3 displays a payment destination selection screen as shown in FIG. 10 on the operation unit 2 of the STM 1 (S802). In the payment destination selection screen, in order to make a history inquiry from the same payment destination button 1001 for making a history inquiry to the same payment destination as the inserted payment form and the payment destination to be displayed from the payment destination that has made a payment transaction so far. A payment destination selection button 1002 is displayed (FIG. 10).

  When the control unit 3 detects that the same payment destination button 1001 for making a history inquiry to the same payment destination as the payment form inserted by the user is selected (S803; Yes), the STM1 temporarily causes the control unit 3 to The stored payment form data (payment destination, name) and information such as the telephone number entered by the user are transmitted to the host server 11, and the history data of the payment transaction performed by the user for the same payment destination as the payment form Request (S804). The host server 11 searches the data table of the customer account information 15 in the storage unit 14 based on information such as the user's name and telephone number received from the STM 1 and identifies the user's account number.

  For example, when the name is “Hanako Tanaka” and the telephone number is “03-4567-8901”, it can be specified from the customer account information data table shown in FIG. 3 that the account number is “321-89865”. Next, the host server 11 searches the data table of the customer transaction information 16 in the storage unit 14 based on the information on the payment destination and the specified account number received from STM1, extracts the payment transaction history data of the same payment destination, STM1 (S804). In FIG. 4, transaction history information such as “October 25, 2016, 08:46:10” and transaction amount “10,000 yen” can be acquired. A plurality of records may be acquired as the transaction history information.

  Next, the control unit 3 displays a payment transaction history list screen for each account number as shown in FIG. 11 on the operation unit 2 of the STM 1 and displays the received payment transaction history data (S806).

  On the other hand, when the control unit 3 detects that the user has selected a payment destination selection button (1002) for performing a history inquiry to a payment destination to be displayed from a payment destination that has previously made a payment transaction (S803; No), STM1 sends the payment form data (payment destination, name) temporarily stored in the control unit 3 and information such as the telephone number entered by the user to the host server 11, and the user has performed so far In the payment transaction, a request is made for data of a payment destination list that has been in a payment transaction so far (S807).

  The host server 11 searches the data table (FIG. 3) of the customer account information 15 in the storage unit 14 based on information such as the user's name and telephone number received from the STM 1 and identifies the user's account number. Next, the host server 11 searches the data table (FIG. 4) of the customer transaction information 16 in the storage unit 14 based on the specified account number information, and transmits all payment destination list data of the payment transaction to the STM 1 ( S808). Next, the control unit 3 displays a payment destination list selection screen as shown in FIG. 12 on the operation unit 2 of the STM 1 and displays the received payment destination list data (S809). It can be seen that a plurality of payment destination buttons 1201 for selecting a payment destination are displayed on the payment destination list selection screen shown in FIG.

  Next, when the control unit 3 detects that the payment destination button 1201 on the payment destination list selection screen has been pressed (S810), the control unit 3 transmits the payment destination of the pressed button to the host server 11 and designated by the user. The history data of the payment transaction performed for the payment destination is requested (S811). The processing from S812 to S806 can be considered in the same way as the above-described S805 to S806, and therefore the description thereof is omitted here.

  The payment transaction history list screen is provided with a button for ending payment transaction history inquiry (hereinafter referred to as an end button) 1101 and a button for displaying a payment form image (hereinafter referred to as a form image display button) 1102. When the control unit 3 confirms that the operation unit 2 has received a press of the end button 1101 from the user (S813; No), the payment transaction history inquiry is terminated.

  On the other hand, when the control unit 3 confirms that the operation unit 2 has received a press of the form image display button 1102 from the user (S813; Yes), the specified payment transaction information (transaction date, payment destination / transfer account) The number, payment destination, name, transaction amount) are transmitted to the content server 17 and a form image file of the designated payment transaction is requested (S814). The content server 17 searches the data table (FIG. 5) of the payment form data 21 in the storage unit 20 based on the previous payment information received from the STM 1 and identifies the form image file name of the designated payment transaction.

  For example, the transaction date is “October 24, 2016 18:16:48”, the payee / transfer account number is “1694-0-123”, the name is “Hanako Akagi”, and the transaction amount is “5400 yen” In some cases, the form image file name can be specified as “01.jpeg” from the payment form data table shown in FIG. Next, the content server 17 retrieves a form image file from the payment form image 22 in the storage unit 20 and transmits it to the STM 1 (S815). Next, the control unit 3 displays a payment form image screen as shown in FIG. 13 on the operation unit 2 of the STM 1 and displays the received payment form image file (S816).

  In the payment form image screen, a button for printing the contents displayed on the screen (hereinafter referred to as a print button) 1301 and a confirmation button 1302 and a payment for displaying image data of the form used for the payment transaction. A form image data display field 1303 is provided. When the control unit 3 confirms that the operation unit 2 has received a press of the print button 1301 from the user (S817; Yes), the receipt output mechanism unit 9 A request is made to print the screen display content of the payment form image data display field 1303 on paper, and the receipt output mechanism unit 9 prints the screen display content on paper and discharges it (S818).

  On the other hand, when the control unit 3 confirms that the operation unit 2 has received a press of the confirmation button 1302 from the user (S817; No), the control unit 3 displays a payment transaction history list screen on the operation unit 2 of the STM1 (S806).

  As described above, by executing the processing in this embodiment, not only the latest transaction history information is uniformly displayed, but also the payment transaction is limited by allowing the user to insert a payment form, and a specific payment destination Transaction history information can be easily confirmed. For example, the user can easily confirm the payment transaction history information of the same payment destination as the inserted payment form by inserting the payment form. In addition, the user can confirm payment transaction history information of a payment destination different from the inserted payment form by selecting a payment destination.

  The present invention is not limited to the above-described embodiments. In the above-described embodiment, when making a history inquiry of a payment destination different from the inserted payment form, the payment destination list data is first received from the host server 11, and then the payment destination selected by the user from the host server 11 is paid. Transaction history data is received, but payment destination list data and payment transaction history data for each payment destination are received at the same time, and payment is performed without transmission / reception with the host server 11 after the user selects a payment destination. Transaction history data may be displayed.

  In the above-described embodiment, transaction history information is acquired from the host server 11 using the payment destination as a keyword and displayed on the operation unit 2. However, not only the payment destination but also an arbitrary keyword is selected by the user. The transaction history information corresponding to the keyword may be displayed on the operation unit 2. Specifically, the control unit 3 includes all items included in the input form read by the form reading mechanism unit 8 (for example, the payment destination / transfer destination account number 2 shown in FIG. Item 3 such as amount 3, payment due date 4, name 5, etc.) is output to the operation unit 2, and transaction information about the item selected by the user by the operation unit 2 is output to the operation unit 2. Also good. By such processing, the user can grasp his / her past transaction history at a glance by using a desired item as a starting point.

1 ... form transaction device 2 ... operation part (input and display part)
DESCRIPTION OF SYMBOLS 3 ... Control part 4 ... Card mechanism part / statement slip mechanism part 5 ... Passbook mechanism part 6 ... Banknote depositing / withdrawing mechanism part 7 ... Coin depositing / withdrawing mechanism part 8 ... Form reading mechanism part 9 ... Receipt output mechanism part 10 ... Communication part ( (Form transaction device)
11: Host server 12: Control unit (host server)
13. Communication unit (host server)
14: Storage unit (host server)
15 ... Customer account information 16 ... Customer transaction information 17 ... Content server 18 ... Control unit (content server)
19 ... Communication part (content server)
20: Storage unit (content server)
21 ... Payment form data 22 ... Payment form image

Claims (7)

A form transaction device that performs transactions using forms with users,
A form reading unit that reads input forms;
Based on the item selected by the user from the operation unit among the items included in the input form and the transaction history of the user in the past, transaction information on the selected item of the transaction history is obtained. A control unit for outputting to the display unit;
A form transaction apparatus comprising: The form reading unit reads an input form inserted from an insertion slot,
The control unit outputs transaction information about the selected item to a display unit based on the selected item in the inserted input form and the transaction history of the user.
The form transaction device according to claim 1. The form reading unit reads a payment form as the input form,
The control unit extracts the transaction history including the same payment destination as the payment destination item included in the payment form, and outputs the transaction history to the display unit.
The form transaction device according to claim 1. The form reading unit reads a payment form as the input form,
The control unit outputs a list of payment destinations indicating past business partners by the user included in the transaction history to the display unit, and the payment unit selected from the list of payment destinations by the operation unit Extract transaction history and output to the display unit,
The form transaction device according to claim 1. The control unit outputs an item included in the input form read by the form reading unit to the display unit, and transaction information regarding an item selected by the operation unit among the output items is displayed on the display unit. Output to
The form transaction device according to claim 1. The form reading unit outputs an image of the form used in the past transaction of the user,
The control unit outputs to the display unit an image of a form used in the transaction of the user together with transaction information about the selected item.
The form transaction device according to claim 1. The control unit prints the transaction information including the image of the form from a printing unit based on a print instruction of the transaction information including the image of the form received from the operation unit.
The form transaction apparatus according to claim 6.

Images