Card reader and settlement method

Abstract

To provide a card reader that can be switched between a card reader mode and a settlement terminal mode.SOLUTION: There is provided a card reader that comprises a control unit 11 and a control unit 12. The control unit 11 performs processing to transmit information on a card 2 as a medium for settlement to a host device 3 at a request for settlement performed by the host device 3. Consequently, the card reader 1 itself is made to operate in a card reader mode in which the card reader is connected to the host device 3. The control unit 12 performs processing of a user interface for the settlement request. The control unit 12 performs the settlement with a settlement server 4 not through the host device 3 under specific conditions. Consequently, the control unit 12 makes the card reader 1 itself operate in a settlement terminal mode.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a card reader and a payment method. [Background technology]

[0002] Conventionally, there have been card readers that include multiple control units and are capable of communicating between a master device and a slave device. For example, Patent Document 1 describes a card reader in which a status notification line B and a line C for transmitting and receiving instructions and data are connected between a master device and a slave device. In this card reader, in response to a change in status, a status notification is sent to the master device via the status notification line B. When a status notification is detected, a status request command is sent via the line C. When this data is acquired, processing corresponding to the status is performed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-4206 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the card reader described in Patent Document 1 was only connected as a peripheral device to a host device (higher-level device) such as an ATM, and could not be operated as a payment terminal that could connect to a payment server and make payments on its own.

[0005] The present invention was made in consideration of this situation, and aims to solve the above-mentioned problems by providing a card reader that can be switched between a card reader mode as a peripheral device and a payment terminal mode that can be used for payments on its own. [Means for solving the problem]

[0006] A card reader according to one embodiment of the present invention is a card reader comprising a first control unit and a second control unit, wherein the first control unit operates the device in a card reader mode connected to the upper device by performing a process of sending information about a payment medium to the upper device in response to a payment request executed by the upper device, and the second control unit processes a user interface for payment requests, and under certain conditions, operates the device in a payment terminal mode by performing payment without going through the upper device. This configuration allows switching between card reader mode and payment terminal mode.

[0007] A card reader according to one embodiment of the present invention is characterized in that the first control unit and the second control unit are connected via serial communication, and when operating in the card reader mode, the first control unit becomes the master of the serial communication, and when operating in the payment terminal mode, the second control unit switches to become the master of the serial communication. By configuring in this way, it is possible to avoid communication collisions when switching between card reader mode and payment terminal mode.

[0008] A card reader according to one embodiment of the present invention is characterized in that, as the specific condition, it operates in the card reader mode when reading the payment medium that is supported by the upper device, and operates in the payment terminal mode when reading the payment medium that is not supported by the upper device but is supported by the card reader. By configuring it in this way, it is possible to dynamically switch between card reader mode and payment terminal mode depending on the type of card medium being read.

[0009] In one aspect of the card reader of the present invention, when the card reader is functioning in the payment terminal mode, the second control unit refuses a request from the higher-level device to switch to the card reader mode. This configuration can improve the reliability and certainty of payments.

[0010] A payment method according to one embodiment of the present invention is a payment method executed by a card reader, which, in card reader mode, performs processing to send information about a payment medium to a higher-level device in response to a payment request executed by the higher-level device, and in the card reader mode, performs processing of a user interface for the payment request, switches between the card reader mode and payment terminal mode in response to specific conditions, and in the payment terminal mode, performs payment without going through the higher-level device. This configuration allows switching between card reader mode and payment terminal mode. [Effects of the Invention]

[0011] According to the present invention, a card reader can be provided that can switch between card reader mode and payment terminal mode by having the second control unit, which processes the user interface, perform payment without going through a higher-level device under certain conditions, and operate the device in payment terminal mode. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a system configuration diagram of a payment system X according to an embodiment of the present invention. [Figure 2A] 10 is a flowchart of a card reader mode initialization process according to the embodiment of the present invention. [Figure 2B] 10 is a flowchart of a card reader mode payment process according to an embodiment of the present invention. [Figure 2C] 10 is a flowchart of a payment terminal mode switching process according to an embodiment of the present invention. [Figure 2D] 10 is a flowchart of a card reader mode switching process according to the embodiment of the present invention. [Figure 2E] 10 is a flowchart of a card reader mode switching refusal process according to the embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] <Embodiment> [System configuration of payment system X] The system configuration of a payment system X according to an embodiment of the present invention will be described with reference to Figure 1. In this embodiment, payment system X is a payment system including an ATM (Automated Teller Machine), a kiosk system, a ticket issuing system for transportation, a point card system for convenience stores or the like, a POS (Point Of Sales) system for retail stores, a membership card system, a card issuing / payment system for gaming machines, an entrance / exit management system, etc. (hereinafter simply referred to as "ATM, etc.").

[0014] The payment system X includes a card reader 1, a higher-level device 3, a payment server 4, and the payment server 4 reads a card 2 to perform payment. In this embodiment, the card reader 1 and the higher-level device 3 are connected by a USB (Universal Serial Bus) or the like. The higher-level device 3 and the payment server 4 are connected via a network such as the Internet or an intranet.

[0015] The card reader 1 is an example of a device that can read or write data from a card 2, which is an example of a payment medium. In this embodiment, the card reader 1 may include the functions of a magnetic card reader, a contact IC reader, and a contactless IC reader.

[0016] Card 2 is an example of a payment medium according to this embodiment. Card 2 may be, for example, a rectangular card-shaped magnetic recording medium made of vinyl chloride and having a thickness of approximately 0.7 to 0.8 mm, a contact IC card, or a contactless IC card. In the case of a magnetic recording medium, a magnetic stripe for storing a magnetic signal is formed on one side of card 2. In the case of a contact IC card or a contactless IC card, card 2 may include, for example, contacts, an electromagnetic induction antenna, and an IC chip including a ROM (Read Only Memory) and an MPU (Micro Processing Unit).

[0017] Card 2 may be, for example, an IC credit card conforming to the EMV (Europay, MasterCard, VISA protocol) standard used for payments at banks, etc. In this case, card 2 has a built-in contactless IC that may also be used as a contact IC chip. That is, in card 2, the contact IC and contactless IC may be on the same IC chip or on separate IC chips. Furthermore, if card 2 is a contactless IC card, it may be a proximity-type contactless IC card, and in this case, it may be any of Type A, Type B, FeliCa (registered trademark), or a card of another standard.

[0018] The IC chip of card 2 stores various application software (hereinafter simply referred to as "apps") for performing credit card payments, debit card payments, other point payments, etc., as well as various data, in a recording medium such as flash memory or EEPROM (Electrically Erasable Programmable Read-Only Memory).The IC chip of card 2 may also include an MPU (Micro Processing Unit).

[0019] The card 2 may be a PET (polyethylene terephthalate) card having a thickness of about 0.18 to 0.36 mm, a paper card having a predetermined thickness, or the like. In addition, in this embodiment, in addition to card 2, other payment media and contactless media that can be used include smartphones, mobile phones, smart watches, RFID tags, etc. (hereinafter referred to as "smartphones, etc.").

[0020] Alternatively, a paper card or plastic card on which a one-dimensional barcode, a two-dimensional barcode such as a QR code (registered trademark), a color code, etc. (hereinafter referred to as "barcode, etc.") is printed can also be used as card 2. Furthermore, something like the display screen of a smartphone can also be used.

[0021] The higher-level device 3 is an information processing device connected to the card reader 1 and for realizing various functions of an ATM, etc. In this embodiment, the higher-level device 3 is, for example, a payment PC (Personal Computer), a cash register, a POS terminal, an ATM, a payment terminal in a hospital or the like, a store server, a terminal for other settlements (payments), a kiosk terminal, a payment terminal in a gas station, roadside equipment, an in-vehicle device in a taxi or the like, a terminal for a ticket issuing system in a transportation facility, a terminal for a point card payment system in a convenience store or the like, a terminal for a member card issuing system in a retail store, a terminal for a card issuing and payment system in a gaming machine, a terminal for an entrance and exit management system, etc.

[0022] In this embodiment, the higher-level device 3 executes, by means of a control unit, an application for realizing the functions of the payment system X stored in a storage (memory unit). For this reason, the higher-level device 3 is connected to a card reader 1 as a peripheral device for reading the card 2. In addition, the higher-level device 3 can also be connected to an IP network such as Ethernet (registered trademark), a mobile telephone network, other dedicated lines (hereinafter simply referred to as "networks"), various peripheral devices, etc.

[0023] The payment server 4 is a payment server that performs payment for ATMs and the like via the higher-level device 3. This payment includes, for example, the transfer of money using the card 2, transfer, money transfer, and payment by check. In this case, it is also possible to make a payment without going through the higher-level device 3 by using the payment server 4 to make the payment. The payment server 4 of this embodiment may be, for example, a server of a bank or card company on the so-called "cloud," or a deposit / withdrawal server on an intranet. The payment server 4 may also execute a dedicated payment app using a control unit.

[0024] In this embodiment, communication between the card reader 1 and the higher-level device 3 is achieved by connection via, for example, a Universal Serial Bus (USB), RS-232C, or other serial or parallel interfaces (hereinafter referred to as "USB, etc."). Information including various instructions (commands) and data can be sent and received via the USB, etc. In this case, the higher-level device 3 may recognize the card reader 1 as a device such as a smart card reader or a multifunction device. Furthermore, in this embodiment, the card reader 1 can also be connected to the payment server 4 via a network as an independent payment terminal. In this case, the card reader 1 may be connected to the network via a wired or wireless connection separately from the higher-level device 3, or may be connected to the network via a device driver of the higher-level device 3 via a USB or the like.

[0025] (Control configuration of card reader 1) Next, we will explain the control configuration of the card reader 1. The card reader 1 includes a control unit 11, a control unit 12, a PIN pad unit 13, and a reading unit . In addition, in this embodiment, the card reader 1 can be switched between a "card reader mode" in which it is connected to the higher-level device 3 as a peripheral device, and a "payment terminal mode" in which it performs payments with the payment server 4 without going through the higher-level device 3, either at the time of shipment from the factory or during operation (dynamically).

[0026] The control unit 11 is an example of a first control unit according to this embodiment, and is a control and calculation means such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), or an ASIC (Application Specific Integrated Circuit). The control unit 11 is configured as various circuits on a main (main) board that controls the entire card reader 1, for example.

[0027] In this embodiment, in the card reader mode, the control unit 11 performs a process of transmitting card information of the card 2, which is a magnetic card or a contact IC card, read by the reading unit 14 to the higher-level device 3 in response to a payment request executed by the higher-level device 3. Furthermore, the control unit 11 performs a process of switching from the card reader mode to the payment terminal mode under specific conditions. As a specific condition, the control unit 11 can switch the card reader 1 to operate in card reader mode when the higher-level device 3 reads a magnetic or contact IC medium, and to operate in payment terminal mode when reading a contactless IC.

[0028] In addition, the control unit 11 performs general processing as the card reader 1, status monitoring, and control of sensors, LEDs, and drive mechanisms. In this embodiment, the control unit 11 may execute a general-purpose OS such as embedded Windows (registered trademark), Linux (registered trademark), or Android (registered trademark). In this embodiment, the control unit 11 controls the control unit 12 connected on lines A, B, and C through communication.

[0029] The control unit 12 is an example of a second control unit according to this embodiment, and is a control and calculation means such as a CPU, an MPU, a GPU, a DSP, an ASIC, etc. In addition, the control unit 12 may include an accelerator that exclusively executes hash calculations for various encryptions and decryptions using a method such as AES (Advanced Encryption Standard). The control unit 12 is configured as a sub-board connected to the control unit 11, or various circuits built in the same housing as the PIN pad unit 13 or in a separate housing.

[0030] In this embodiment, in both the card reader mode and the payment terminal mode, the control unit 12 controls the PIN pad unit 13 to process a user interface for payment requests, which in this embodiment is a GUI (Graphical User Interface). Under certain conditions, the control unit 12 can perform payment with the payment server 4 without going through the higher-level device 3, thereby causing the card reader 1 to operate in a payment terminal mode. Additionally, when functioning in the payment terminal mode, the control unit 12 can reject an instruction from the control unit 11 that has received an instruction from the higher-level device 3 to switch to the card reader mode, and can return only a negative response such as a NACK (Negative Acknowledgement). Here, in this embodiment, an example will be described in which the control unit 12 is functioning in the payment terminal mode when payment processing is being executed.

[0031] In addition, the control unit 12 also controls a security function for encrypting information or processing encrypted information, and mainly controls writing and reading of card information to and from the card 2, which is a contactless medium. In this embodiment, the control unit 12 may execute a general-purpose OS such as Android (registered trademark), embedded Windows (registered trademark), or Linux (registered trademark) to perform GUI processing, for example.

[0032] Additionally, the control units 11 and 12 include non-transitory storage media such as a RAM (Random Access Memory), a ROM (Read Only Memory), and a flash memory. Control programs including embedded software, firmware, etc. and various data are stored in the storage media of the control units 11 and 12. These control programs may include an OS, middleware, a device driver for connecting the higher-level device 3 to the card reader 1, a network-related module, and a program for monitoring sensors, controlling the drive mechanism of the card reader 1, switching between card reader mode and payment terminal mode, etc.

[0033] The recording medium of the control unit 12 may also store key data for encryption, a program for contactless communication, and the like. Furthermore, the recording medium of the control unit 12 may also store programs relating to a data encryption function, a decryption function, a function to detect tampering with the card reader 1, and the like, for preventing the fraudulent theft of data such as the ID, PIN, and password stored in the card 2. This allows the card reader 1 to be configured in compliance with PCI (Payment Card Industry) standards and to realize security functions.

[0034] The PIN pad unit 13 includes an input unit for inputting a personal identification number (PIN) and a display unit for a user interface.

[0035] The input section of the PIN pad unit 13 includes a numeric keypad, function keys for selecting a payment type, etc. In this embodiment, the numeric keypad may be covered with a fence to prevent others from seeing the keys being pressed.

[0036] The display unit of PIN pad unit 13 includes a liquid crystal display (LCD), an organic electroluminescence display (organic EL display, organic light emitting diode display), a vacuum fluorescent display, electronic paper, a light emitting diode (LED) for displaying status, etc. In this embodiment, the display unit can display the payment method, the payment status, a user selection screen, etc.

[0037] In this embodiment, the input section and display section of PIN pad section 13 may be configured as an integrated touch pad or touch panel.

[0038] The reading unit 14 is a component that includes a magnetic head that reads and writes to the card 2, an IC contact block, circuits for contactless communication, an RF (Radio Frequency) antenna, and other circuits related to these.

[0039] When reading or writing magnetic information from or to the card 2, the reader 14 reads and writes information from the magnetic stripe of the slid card 2. At this time, the signal to be read or written may be encrypted by an encryption magnetic head. Furthermore, when reading or writing information using a contact IC, the reading unit 14 makes contact with the terminals of the contact IC exposed on the surface of the card 2 with the IC contact block, thereby reading or writing card information stored in the contact IC. In addition, when performing contactless communication, the reading unit 14 performs short-range wireless contactless communication such as NFC (Near Field Communication) or BLE (Bluetooth (registered trademark) Low Energy), and reads and writes card information stored in the contactless IC. Alternatively, the reading unit 14 may be provided with a reader for reading barcodes or the like, a camera, or the like.

[0040] Furthermore, between the control unit 11 and the control unit 12, communication lines A and B and a line C for issuing a switching instruction, which will be described later, are connected. Lines A and B are signal lines such as a general-purpose bus, serial, parallel, etc. Information including various instructions (commands) and data can be transmitted and received between the control units 11 and 12 via lines A and B. In the following description of this embodiment, an example will be described in which lines A and B are signal lines of a UART (Universal Asynchronous Receiver Transmitter). UART is an example of serial communication according to this embodiment, and is an asynchronous serial communication method used by those skilled in the art.

[0041] In this embodiment, when operating in card reader mode, control unit 11 becomes the master of UART and control unit 12 becomes the slave. In this case, the connection side of line A to control unit 11 may be the transmitting side (TX), and the connection side of line A to control unit 12 may be the receiving side (RX). The connection side of line B to control unit 11 may be the receiving side (RX), and the connection side of line B to control unit 12 may be the transmitting side (TX). On the other hand, when operating in payment terminal mode, it is possible to switch so that control unit 12 becomes the UART master and control unit 11 becomes the slave. In this case, the side of line A connected to control unit 11 may be the receiving side (RX) and the side connected to control unit 12 may be the transmitting side (TX). The side of line B connected to control unit 11 may be the transmitting side (TX) and the side connected to control unit 12 may be the receiving side (RX).

[0042] Line C is a signal line for transmitting a switching instruction for switching between the card reader mode and the payment terminal mode. Line C may be provided as, for example, one of the GPIO (General-purpose input / output) pins. In this case, the line C notifies the state from the control unit 12 to the control unit 11 by inverting the logic. In this embodiment, this change in logic of the line C can be detected, for example, by using an interrupt function of the control unit 12. Furthermore, it is also possible to set an interrupt from the control unit 12 to the control unit 11 for monitoring this change in logic.

[0043] Here, the control unit 11 performs the operation of each of the above-mentioned functions by executing a control program stored in a built-in recording medium, and the control unit 12 performs the operation of each of the above-mentioned functions by executing a control program stored in a built-in recording medium. Furthermore, each part of the card reader 1 described above serves as a hardware resource for executing the information processing method of the present invention. Note that a part or any combination of the above-described functional configurations may be configured in terms of hardware or circuits using ICs, programmable logic, FPGAs (Field-Programmable Gate Arrays), or the like.

[0044] [Card reader mode initialization process by payment system X] Next, the card reader mode initialization process executed by the card reader 1 of the payment system X according to the embodiment of the present invention will be described with reference to FIG. 2A. The card reader mode initialization process according to this embodiment is a process for performing initialization in a state where the card reader is connected to the higher-level device 3 as a peripheral device.

[0045] The card reader mode initialization process according to this embodiment is executed mainly by the control units 11 and 12 executing a control program stored in an internal storage medium, in cooperation with each unit, and using hardware resources. The card reader mode initialization process will be described in detail below for each step with reference to the flowchart in FIG. 2A.

[0046] (Step S100) First, the control unit 11 performs an initialization request process. In this embodiment, whether the card reader 1 starts up in card reader mode or payment terminal mode is set in the storage medium of the control unit 11, for example, in the factory default state or at the time of setup. Here, an example of starting up in card reader mode will be described. The control unit 11 is connected to the control unit 12 via UART and transmits an initialization request command via lines A and B.

[0047] (Step S200) Here, the control unit 12 performs an initialization process. Upon receiving the initialization request, the control unit 12 performs initialization processing in the card reader mode. The control unit 12 initializes the display unit and input unit of the PIN pad unit 13, and initializes the GUI. The control unit 12 may cause the display unit of the PIN pad unit 13 to display a message regarding reading of the card 2, such as "Please insert or swipe card 2." Additionally, control unit 12 may allow the user making the payment to select the type of payment (payment method) using the input unit of PIN pad unit 13. In this case, control unit 12 may cause the display unit or function keys of PIN pad unit 13 to display an image that allows the user to select the payment method from magnetic card, contact IC card, contactless IC card or contactless medium, barcode, etc.

[0048] (Step S201) Next, the control unit 12 performs a response process. The control unit 12 transmits to the control unit 11 a response such as an ACK (ACKnowledgement) indicating that the initialization has been successful. After this, the control unit 12 enters a state of waiting for a command from the control unit 11. This completes the card reader mode initialization process according to the embodiment of the present invention.

[0049] [Card reader mode payment processing by payment system X] Next, the card reader mode payment process executed by the card reader 1 of the payment system X according to the embodiment of the present invention will be described with reference to FIG. 2B. The card reader mode payment process according to this embodiment is a process in which, while connected to the higher-level device 3, the device operates as a card reader, which is a peripheral device, and executes commands from the higher-level device 3. Here, an example will be described in which the higher-level device 3 is an ATM or the like that only supports magnetic cards or contact IC cards, and the user has instructed payment with a magnetic card or contact IC card.

[0050] The card reader mode payment processing of this embodiment is mainly carried out by the control unit of the upper device 3, and the control units 11 and 12 of the card reader 1, in cooperation with each unit and using hardware resources by executing a control program stored in a connected storage or an internal storage medium. The details of the card reader mode payment process will be explained below step by step with reference to the flowchart in FIG. 2B.

[0051] (Step S310) First, the higher-level device 3 performs card reader command processing. The control unit of the higher-level device 3 sends a payment request command to start reading the card 2 for payment from the payment app via a device driver via a USB or the like. Here, the higher-level device 3 performs payment using a magnetic card or contact IC.

[0052] (Step S110) Here, the control unit 11 performs card reader processing. The control unit 11 receives a command from the higher-level device 3 and executes a process corresponding to the command. Here, in the card reader mode, the control unit 11 reads the card information of the card 2 using the magnetic head or IC contact block of the reading unit 14. As a result, when the higher-level device 3 reads the magnetic or contact IC card 2 under certain conditions, it becomes possible to operate the card reader 1 in the card reader mode. At this time, the control unit 11 may cause the display unit of the PIN pad unit 13, via the control unit 12, to display a message indicating that the card 2 is being read and payment is being made.

[0053] (Step S111) Next, the control unit 11 performs a screen switching process. The control unit 11 instructs the control unit 12 to input a PIN via lines A and B as necessary. For this reason, the control unit 11 transmits to the control unit 12 a command such as a request to switch the screen for PIN input.

[0054] (Step S210) Here, the control unit 12 performs display input processing. Control unit 12 causes the display unit of PIN pad unit 13 to display a screen instructing the user to enter a PIN, a numeric keypad, and the like.

[0055] (Step S211) Next, the control unit 12 performs a response process. If the PIN input is successful, the control unit 12 transmits a response to the control unit 11 via lines A and B to the effect that the PIN input is successful. The control unit 12 can also transmit encrypted PIN information, PCI standard encryption keys, and the like to the control unit 11. At this time, the control unit 12 can also perform GUI processing for the payment request.

[0056] (Step S113) Here, the control unit 11 performs a response process. The control unit 11 responds to the higher-level device 3 via a USB or the like to the effect that reading of the card 2 has been completed and, if necessary, that the PIN has been successfully entered. At this time, the control unit 11 may encrypt the card information and PIN of the read card 2 in accordance with PCI standards or the like, and transmit them to the higher-level device 3. By performing such processing, the control unit 11 can operate the card reader 1 itself in a card reader mode connected to the higher-level device 3. This completes the card reader mode payment process according to the embodiment of the present invention.

[0057] [Payment terminal mode switching process by payment system X] Next, the payment terminal mode switching process executed by the card reader 1 of the payment system X according to the embodiment of the present invention will be described with reference to FIG. 2C. In this process, the card reader 1 operating in card reader mode is switched to payment terminal mode. In this embodiment, for example, if the higher-level device 3 does not support payments using contactless IC cards such as contactless EMV, payments using barcodes, etc., and the user instructs this, this switching is performed. In other words, in this embodiment, it is possible to switch between card reader mode and payment terminal mode depending on the payment method.

[0058] The payment terminal mode switching process according to this embodiment is performed by the control unit of the payment server 4 and the control units 11 and 12 of the card reader 1 executing a control program stored in storage or in an internal storage medium, in cooperation with each unit including the PIN pad unit 13, using hardware resources. The following describes the details of the payment terminal mode switching process step by step using the flowchart in FIG. 2C.

[0059] (Step S130) First, the control unit 11 performs a payment terminal initialization request process. Here, the control unit 11 switches to the payment terminal mode and sends a command to the control unit 12 via lines A and B requesting initialization.

[0060] (Step S230) Here, the control unit 12 performs the master switching process. In this embodiment, as described above, an example will be described in which the master and slave are interchanged when the control units 11 and 12 use UART for communication between the CPUs. Here, in UART communication, it is necessary to clearly identify the master as the main device and the slave as the sub-device.

[0061] In this embodiment, control unit 11 is the master in the card reader mode, but control unit 12 is the master in the payment terminal mode. Therefore, control units 11 and 12 change their master and slave roles when switching between the card reader mode and the payment terminal mode. Specifically, in this process, the control unit 12 switches between master and slave by switching between TX and RX on lines A and B, causing the device to operate as a master. At that time, the control unit 11 also switches between TX and RX on lines A and B, causing the device to operate as a slave.

[0062] As a result, when operating in the payment terminal mode, the control unit 12 and the control unit 11 are switched to be the masters of the UART, and it becomes possible to change the subject of the payment process to the control unit 12.

[0063] (Step S231) Next, the control unit 12 performs a response process. Control unit 12 transmits a response to control unit 11, indicating that the change to the payment terminal mode and the initialization have been successful, via lines A and B, which have been switched between master and slave.

[0064] (Step S330) Here, the PIN pad unit 13 and the control unit 12 perform a transaction start process. The control unit 12 performs initialization processing for the payment method selected by the user, and display switching processing for displaying a display for the selected payment method on the display unit of the PIN pad unit 13.

[0065] Thereafter, the control unit 12 starts the payment transaction and reads the card information for the payment method selected by the user from the card 2. At this time, the control unit 12 can obtain the card information from the card 2 via the reading unit 14 using a contactless IC card, contactless medium, barcode, etc.

[0066] In this way, when specific conditions are met to read card information such as a contactless IC card, contactless medium (contactless IC), or barcode, it is possible to switch between card reader mode and payment terminal mode accordingly. Then, depending on the specific conditions, it is possible to operate the card reader 1 in the payment terminal mode.

[0067] (Step S131) Here, the control unit 11 performs card reader command processing. The control unit 11 transmits a command to the control unit 12 via lines A and B to instruct the control unit 12 to transmit the card information of the card 2 .

[0068] (Step S232) Here, the control unit 12 performs a response process. If the control unit 12 has successfully read the card information of the card 2, it transmits a response to that effect to the control unit 11 via lines A and B.

[0069] (Step S233) Next, the control unit 12 performs a PIN input request process. Control unit 12 causes PIN pad unit 13 to display a screen instructing the user to enter a PIN, a numeric keypad, etc. This process is performed in the same manner as in step S210 described above.

[0070] (Step S331) Here, PIN pad unit 13 and control unit 12 perform the PIN input process. The control unit 12 acquires the PIN information input by the user through the input unit of the PIN pad unit 13 . In this way, the control unit 12 can perform GUI processing for the payment request.

[0071] (Step S234) Here, the control unit 12 performs a payment request process. If the PIN is successfully entered, the control unit 12 connects to the payment server 4 via the network and makes a payment request. The control unit 12 encrypts the acquired card information using an encryption key or the like conforming to the PCI standard, and transmits it together with similarly encrypted PIN information to the payment server 4, thereby carrying out the payment.

[0072] (Step S430) Here, the payment server 4 performs the payment process. The control unit of the payment server 4 receives the encrypted card information and PIN information via a network or the like, decrypts them, and performs payment processing.

[0073] (Step S431) Next, the settlement server 4 performs a result notification process. The control unit of the payment server 4 notifies the control unit 12 of the result of the payment.

[0074] (Step S235) Here, the control unit 12 performs a payment notification process. The control unit 12 acquires the result of the payment from the payment server 4 and stores it in a recording medium. The result of this payment is then displayed on the display of PIN pad unit 13 to notify the user. Alternatively, control unit 12 can also cause a printer (not shown) to print the result of this payment on a receipt or the like.

[0075] (Step S332) Here, PIN pad unit 13 and control unit 12 perform transaction completion processing. The control unit 12 displays on the display unit of the PIN pad unit 13 that the transaction has been completed. At this time, it is also possible to instruct the user to remove the card 2, receipt, etc. This completes the payment terminal mode switching process according to the embodiment of the present invention.

[0076] [Card reader mode switching process by payment system X] Next, the card reader mode switching process executed by the card reader 1 of the payment system X according to the embodiment of the present invention will be described with reference to FIG. 2D. In this process, the card reader 1 operating in the payment terminal mode is switched to the card reader mode. Here, we will explain the process when the higher-level device 3 instructs the card reader 1 to perform payment in the card reader mode and the card reader 1 is able to execute the instruction.

[0077] The card reader mode switching process in this embodiment is mainly performed by the control unit of the higher-level device 3 and the control units 11 and 12 of the card reader 1, in cooperation with each unit, by executing a control program stored in a connected storage or an internal storage medium, using hardware resources. The card reader mode switching process will be described in detail below for each step with reference to the flowchart in FIG. 2D.

[0078] (Step S340) First, the higher-level device 3 performs a payment request process. The higher-level device 3 issues an instruction to switch to the card reader mode. When making a payment using a magnetic card or a contact IC card as described above, the control unit of the higher-level device 3 transmits a payment request command via a USB or the like.

[0079] (Step S140) Here, the control unit 11 performs a card reader switching request process. Upon receiving the instruction to switch to the card reader mode, the control unit 11 instructs the control unit 12 to switch to the card reader mode. In this embodiment, the control unit 11 can notify the switching timing through line C, which is a signal line (interrupt line) for notifying the switching timing.

[0080] (Step S240) Here, the control unit 12 performs a switching determination process. The control unit 12 determines whether or not the state is such that switching is possible. In this embodiment, when the control unit 12 receives a notification from line C, it determines whether a payment is being made in the payment terminal mode or whether there is an uninterruptible process, as an interrupt process. Here, if these processes are not performed, the control unit 12 determines that switching is possible.

[0081] (Step S241) Next, the control unit 12 performs possible response processing. Here, the control unit 12 notifies that switching of ACK etc. is possible.

[0082] (Step S141) Here, the control unit 11 performs a switching response process. The control unit 11 switches to the card reader mode and sends a response notification to switch the master and slave of the UART. Thereafter, the control unit 11 switches TX and RX on lines A and B, thereby changing the mode to become the master, just like the original card reader mode.

[0083] (Step S242) The control unit 12 performs the slave switching process. In this process, the control unit 12 switches between the master and slave of the UART. This process is the opposite of step S230 described above, and changes to the slave by switching TX and RX of lines A and B. In this way, when the device is operated in the card reader mode again, the control unit 11 becomes the master of the UART and the control unit 12 becomes the slave, so that the main body of the payment process can be changed to the control unit 11.

[0084] (Step S142) Next, the control unit 11 performs an initialization request process. The control unit 11 transmits an initialization request command in the card reader mode to the control unit 12 . This process is performed in the same manner as in step S100 described above.

[0085] (Step S243) Here, the control unit 12 performs an initialization process. This process is also performed in the same manner as in step S200 described above.

[0086] (Step S244) Here, the control unit 12 performs a success response process. If the initialization is successful, the control unit 12 transmits a response to the control unit 11 indicating that the initialization is successful. This process is also performed in the same manner as in step S201 described above. This completes the card reader mode switching process according to the embodiment of the present invention.

[0087] [Card reader mode switching refusal processing by payment system X] Next, the card reader mode switching refusal process executed by the card reader 1 of the payment system X according to the embodiment of the present invention will be described with reference to FIG. 2E. This process is performed when the switching from the payment terminal mode to the card reader mode by the card reader mode switching process in FIG. 2D described above fails for a reason such as during a payment.

[0088] The card reader mode switching rejection process in this embodiment is mainly performed by the control unit of the higher-level device 3 and the control units 11 and 12 of the card reader 1, in cooperation with each unit, by executing a control program stored in a connected storage or an internal storage medium, using hardware resources. The card reader mode switching refusal process will be described in detail below for each step with reference to the flowchart in FIG. 2E.

[0089] (Step S350) First, the higher-level device 3 performs a payment request process. When performing payment in card reader mode, the higher-level device 3 transmits a payment request command. This process is performed in the same manner as in step S340 described above. Here, when the user tries to insert the card 2 into the reading unit 14, the higher-level device 3 may send this command regardless of the timing.

[0090] (Step S150) Here, the control unit 11 performs a card reader switching request process. This process is performed in the same manner as in step S140 described above.

[0091] (Step S250) Here, the control unit 12 performs a switching determination process. In this process, the control unit 12 determines whether a payment is being made in the payment terminal mode or whether there is an uninterruptible process, similar to step S240 described above. Here, the control unit 12 determines that switching is not possible if the device is functioning in the payment terminal mode. Specifically, the control unit 12 determines that switching is not possible if, for example, a payment is being made with the payment server 4 or there is other processing that cannot be interrupted.

[0092] (Step S251) Next, the control unit 12 performs an impossible response process. Here, the control unit 12 returns a response to the effect that switching is not possible to the control unit 11. This enables the control unit 12 to refuse switching to the card reader mode from the higher-level device 3 while functioning in the payment terminal mode. That is, the control unit 12 rejects the payment from the control unit 11 side because it is an unexpected illegal state. At this time, the control unit 12 can display a screen such as "Settlement in progress" on the display unit of the PIN pad unit 13.

[0093] (Step S151) Here, the control unit 11 performs an acknowledgement response process. The control unit 11 transmits a response to the control unit 12 acknowledging that the switching is not possible. In this state, the control unit 11 may notify the higher-level device 3 via USB or the like that the mode could not be changed to the card reader mode.

[0094] (Step S152) Here, the control unit 11 performs initialization request processing. In this embodiment, even if an acceptance response has been sent, the control unit 11 may make an initialization request if a specific time has elapsed, or if a payment request command is received again from the higher-level device 3, etc. In these cases, the control unit 11 may transmit an initialization request command in the card reader mode, similar to step S142 described above.

[0095] (Step S252) Here, the control unit 12 performs NACK processing. In this embodiment, if an initialization request command is received from the control unit 11 even though switching from the payment terminal mode is not possible, the control unit 12 rejects the instruction from the control unit 11 and returns only a negative response such as NACK. This allows the control unit 12 to refuse a request from the higher-level device 3 to switch to the card reader mode. This completes the card reader mode switching refusal process according to the embodiment of the present invention.

[0096] [Major Effects of the Present Embodiment] The above configuration can provide the following effects. Conventional card readers equipped with two control units, a master device and a slave device, are simply connected to a higher-level device as peripheral devices and cannot perform payments by themselves.

[0097] In contrast, (a) the card reader 1 according to an embodiment of the present invention is a card reader comprising a control unit 11 and a control unit 12, and the control unit 11 performs a process of transmitting information about a card 2, which is an example of a payment medium, to the upper device 3 in response to a payment request executed by the upper device 3, thereby causing the card reader 1 itself to operate in a card reader mode connected to the upper device 3, and the control unit 12 processes the user interface for the payment request, and under certain conditions, performs payment with the payment server 4 without going through the upper device 3, causing the card reader 1 itself to operate in a payment terminal mode.

[0098] This configuration makes it possible to switch between card reader mode as a peripheral device and payment terminal mode, which allows for standalone payment. This allows dynamic switching between card reader mode and payment terminal mode through host control from the higher-level device 3. Alternatively, it is possible to sell a model with the same hardware as either a card reader or a payment terminal, as separate products. This also reduces product development costs.

[0099] Furthermore, in the conventional technology of Patent Document 1, communication was requested via an interrupt line, and commands had to be transmitted from the master side.

[0100] In contrast, (b) in the card reader 1 according to the embodiment of the present invention, the control unit 11 and the control unit 12 are connected via UART, and when operating in card reader mode, the control unit 11 becomes the master of UART, and when operating in payment terminal mode, the control unit 12 switches to become the master of UART, which is the card reader described in (a).

[0101] This configuration makes it possible to avoid communication collisions when switching between card reader mode and payment terminal mode. That is, communication can be performed by dynamically switching between UART master and slave depending on whether the mode is card reader mode or payment terminal mode. This allows the control unit 12 to send commands when it operates as the master. This eliminates the need to always send commands from the control unit 11, improving communication efficiency. Increasing communication efficiency in this way can also improve the performance, response, etc. of the entire payment system X. Furthermore, by detecting an interruption on line C with the control unit 12, it is possible to reliably switch to card reader mode even when operating in payment terminal mode.

[0102] (c) The card reader 1 according to the embodiment of the present invention is characterized in that it is a card reader as described in (a) or (b) that operates in card reader mode when reading a card 2 that is supported by the higher-level device 3, and operates in payment terminal mode when reading a card 2 that is not supported by the higher-level device 3 but is supported by the card reader, as a specific condition.

[0103] This configuration makes it possible to dynamically switch between card reader mode and payment terminal mode depending on the type of card 2 to be read as a specific condition. This makes it possible, for example, for the upper device 3 to operate in card reader mode when it only reads magnetic or contact IC media, and to operate in payment terminal mode when it reads contactless ICs. In this way, even if the upper device 3 does not support contactless IC cards or contactless media, payments can be made by connecting the card reader 1. This improves convenience.

[0104] (d) The card reader 1 according to an embodiment of the present invention is characterized in that, when functioning in payment terminal mode, the control unit 12 is a card reader as described in any one of (a) to (c), which refuses switching to card reader mode from the higher-level device 3.

[0105] This configuration can improve the reliability and certainty of payments. That is, even if the control unit 11 issues an instruction such as inserting the card 2 while the control unit 12 is functioning in payment terminal mode, it is possible to reduce the possibility of an error in the payment. This can improve convenience.

[0106] (e) A payment method according to an embodiment of the present invention is a payment method executed by a card reader 1, which, in card reader mode, performs processing to send information on a card 2, which is a payment medium, to a higher-level device 3 in response to a payment request executed by the higher-level device 3, and, in card reader mode or payment terminal mode, performs processing of a user interface for the payment request, switches between card reader mode and payment terminal mode in response to specific conditions, and, in payment terminal mode, performs payment without going through the higher-level device 3.

[0107] By configuring it in this way, it is possible to switch between a card reader mode as a peripheral device and a payment terminal mode in which payments can be made on its own.

[0108] Other Embodiments In the above embodiment, an example has been described in which the higher-level device 3 and the card reader 1 are directly connected via a USB or the like. However, the higher-level device 3 may also be connected via a network.

[0109] In addition, in the above-mentioned embodiment, an example was described in which, as a specific condition, depending on the payment method, the device operates in card reader mode for magnetic cards and contact IC cards, and in payment terminal mode for contactless ICs, barcodes, etc. However, this may be reversed, and a separate card reader or the like may be prepared for each payment method.

[0110] Furthermore, in the above embodiment, an example has been described in which, in the case of a payment method that is not supported by the higher-level device 3, for example, in the case of a contactless IC, payment is made by switching to the payment terminal mode. However, even if the higher-level device 3 is compatible with contactless ICs or the like, it may be possible to select either the card reader mode or the payment terminal mode for payment. In this case, depending on the payment method, it may be possible to select between card reader mode and payment terminal mode depending on conditions such as whether it is better to process on the higher-level device 3 with a faster line speed, or on the card reader 1 side with higher security.

[0111] As a specific condition, the card reader 1 may be configured to change to card reader mode if it is connected to the higher-level device 3 via USB or the like, and to change to payment terminal mode if it is not connected to the higher-level device 3 via USB or the like but is connected to a network.

[0112] Furthermore, as specific conditions, it is also possible to set conditions such as when an instruction is given from the higher-level device 3, when reading of a point card or other card medium is completed, when magnetic reading is completed, when encryption processing is completed, and the like.

[0113] By configuring it in this way, it becomes possible to make appropriate payments in either card reader mode or payment terminal mode depending on various environments.

[0114] In the above embodiment, the lines A, B, and C are described as examples in which physical conductors are used. However, instead of using physical conductors, lines A, B, and C may be configured to communicate and notify status using wireless communication such as Bluetooth (registered trademark), a pair of light-emitting and light-receiving parts of an optical sensor, a capacitance sensor, etc. Even when physical conductors are used, other types of synchronous or asynchronous serial communication besides UART may be used as the communication method for lines A and B. Alternatively, lines A and B may use other types of signal communication, such as I2C, SPI, CAN, PCI Express, USB, or other interconnects.

[0115] Furthermore, in the above embodiment, it has been described that the control unit 12 detects an interruption of line C, but this may be configured to be switched between the card reader mode and the payment terminal mode. That is, in the card reader mode, the control unit 12 may detect an interruption of line C, but in the payment terminal mode, the control unit 11 may detect an interruption of line C.

[0116] By configuring in this way, it becomes possible to accommodate a flexible configuration.

[0117] In the above-described embodiment, an example has been described in which control units 11 and 12 are built into card reader 1. However, the processing of the above-described embodiment may be executed by payment system X in which the control unit of higher-level device 3 is control unit 11 and the control unit of card reader 1 is control unit 12. In this case, a status notification line may be connected to card reader 1 and higher-level device 3, and commands may be sent and received using a network or the like.

[0118] It goes without saying that the configurations and operations of the above-described embodiments are merely examples, and can be modified as appropriate within the scope of the present invention. [Explanation of symbols]

[0119] 1 card reader 2 Cards 3 Upper device 4. Payment Server 11, 12 Control section 13 PIN pad section 14 Reading unit A, B, C lines X Payment System

Claims

1. A card reader including a first control unit and a second control unit, the first control unit operates the device in a card reader mode connected to the higher-level device by performing a process of transmitting information about a payment medium to the higher-level device in response to a payment request executed by the higher-level device; The second control unit processes a user interface for a payment request, and, under specific conditions, performs payment without going through the higher-level device, thereby operating the device in a payment terminal mode. A card reader characterized by:

2. The first control unit and the second control unit are connected via serial communication, When the device is operated in the card reader mode, the first control unit becomes a master of the serial communication, When the device is operated in the payment terminal mode, the second control unit is switched to become the master of the serial communication.

2. The card reader according to claim 1.

3. As the specific condition, when reading the payment medium that is supported by the host device, the device is operated in the card reader mode, and when reading the payment medium that is not supported by the host device but is supported by the card reader, the device is operated in the payment terminal mode.

2. The card reader according to claim 1.

4. When functioning in the payment terminal mode, The second control unit rejects a request from the host device to switch to the card reader mode.

2. The card reader according to claim 1.

5. A payment method executed by a card reader, comprising: In the card reader mode, the device performs a process of transmitting information about a medium for payment to the host device in response to a request for payment executed by the host device; In the case of the card reader mode, a user interface for a payment request is processed; Switching between the card reader mode and the payment terminal mode according to specific conditions; In the payment terminal mode, payment is made without going through the higher-level device. A payment method characterized by:

Images