JP2021043884A - Program, information processing apparatus, and information processing method - Google Patents

Abstract

To provide a program, or the like, configured to prevent unauthorized use of a credit card without complicating the configuration of the card.SOLUTION: A computer acquires card information on a credit card and an invisible-light image obtained by imaging the credit card irradiated with invisible light, whose information can be obtained by irradiation with invisible light. The computer requests a predetermined device for permission to use the credit card on the basis of the obtained card information and invisible-light image.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to programs, information processing devices and information processing methods.

In recent years, credit cards have been widely used when purchasing goods or services at stores or EC (Electronic Commerce) sites. When a credit card is used for purchasing on an EC site, for example, a user transmits card information such as a card number and an expiration date to the EC site via an input screen on the EC site. Then, when the EC site sends the card information to the authentication device of the card company to inquire whether or not to use the credit card, and receives the permission to use the credit card from the authentication device, payment with this credit card becomes possible. .. Therefore, since payment can be made only with the credit card information, there is a possibility that the credit card will be used illegally if the card information is leaked.

In Patent Document 1, recognition data such as a user's fingerprint, voice, retinal pattern, facial features, and DNA pattern are registered in the memory of the card body, and when the card is used, the user owns the recognition data. Is entered, and a technique has been proposed that enables the card to be used when the entered recognition data matches the registered recognition data. In the technique disclosed in Patent Document 1, the user's recognition data is input before the card is used, and if the input recognition data does not match the registered recognition data, the use of the card is not permitted. It is possible to prevent the card from being used illegally.

Japanese Unexamined Patent Publication No. 2003-67687

In the technique disclosed in Patent Document 1, it is necessary to provide an input unit or the like for inputting user recognition data (body pattern information) in the card body, and there is a problem that the card has a complicated configuration. Further, the technique disclosed in Patent Document 1 can prevent the card from being used by anyone other than a legitimate user (card owner) when the card is inserted into an external device such as an ATM machine and used. There is a problem that it is difficult to prevent unauthorized use of credit cards.

The present disclosure has been made in view of such circumstances, and the purpose of the present disclosure is to provide a program or the like capable of preventing unauthorized use of a credit card without complicating the card configuration. There is.

The program according to the present disclosure acquires card information related to a credit card, acquires an invisible light image taken by irradiating a credit card capable of acquiring information by irradiating invisible light with the invisible light, and acquires the card information. And, based on the invisible light image, the computer is made to perform a process of requesting the predetermined device for permission to use the credit card.

In the present disclosure, when a credit card is used, not only the card information but also the invisible light image taken by irradiating the credit card with invisible light is used to determine whether or not the credit card can be used. Therefore, the credit card may be configured so that information can be acquired by irradiating invisible light, and the configuration of the credit card is not complicated. Unauthorized use of credit cards can be prevented.

It is a schematic diagram which shows the configuration example of an information processing system. It is a schematic diagram which shows the appearance example of a credit card. It is a block diagram which shows the configuration example of the server for a card company and the server for an EC site. It is a schematic diagram which shows the configuration example of the DB stored in the server for a card company and the server for an EC site. It is a block diagram which shows the configuration example of a user terminal. It is a flowchart which shows an example of the credit card authentication processing procedure. It is a flowchart which shows an example of the credit card authentication processing procedure. It is a schematic diagram which shows the screen example in a user terminal. It is a flowchart which shows an example of the credit card authentication processing procedure in Embodiment 2. It is a schematic diagram which shows the structural example of the customer information DB of Embodiment 3. It is a flowchart which shows an example of the user registration processing procedure by the server for EC site. It is a flowchart which shows an example of the user registration processing procedure by the server for EC site. It is a schematic diagram which shows the screen example in a user terminal. It is a flowchart which shows an example of the settlement processing procedure on an EC site. It is a schematic diagram which shows the structural example of the information processing system of Embodiment 4. It is a block diagram which shows the configuration example of the server for a card company and the credit card processing terminal. It is a flowchart which shows an example of the credit card authentication processing procedure. It is a flowchart which shows an example of the payment processing procedure using a credit card. It is a schematic diagram which shows the appearance example of the card authentication device. It is a schematic diagram which shows the configuration example of the card authentication device. It is a schematic diagram which shows the configuration example of the contractor information DB stored in the server for card company of Embodiment 5. It is a flowchart which shows an example of the credit card authentication processing procedure in Embodiment 5.

Hereinafter, the program, the information processing apparatus, and the information processing method of the present disclosure will be described in detail with reference to the drawings showing the embodiments thereof. In each of the following embodiments, a system for determining whether or not to use a credit card on which a code, a pattern, a pattern, etc. are printed on an outer surface using an ultraviolet light emitting paint will be described as an example. However, the present disclosure is not limited to such a configuration, and can be applied to a system for determining whether or not to use a credit card that can acquire information by irradiating invisible light. For example, it can be applied to a system for determining the permission or disapproval of a credit card that can acquire information by irradiating infrared rays or X-rays.

(Embodiment 1)
FIG. 1 is a schematic diagram showing a configuration example of an information processing system. The information processing system of the present embodiment includes a card company server 10 managed by a credit card company, an EC site server 20 that operates an EC site (website), a user terminal 30 of a user who uses the EC site, and the like. The card company server 10, the EC site server 20, and the user terminal 30 are configured to be connectable to a network N such as the Internet. The card company server 10 and the EC site server 20 are information processing devices capable of transmitting and receiving various types of information processing and information, respectively, such as a server computer or a personal computer. One card company server 10 may be provided for each card company, or a plurality of card company servers 10 may be provided for each card company. One EC site server 20 may be provided for each EC site, or a plurality of EC site servers 20 may be provided for each EC site. Further, the card company server 10 and the EC site server 20 may be realized by a plurality of virtual machines provided in one server device, or may be realized by using a cloud server. The user terminal 30 is an information processing device capable of transmitting and receiving various types of information processing and information, and is, for example, a smartphone, a tablet terminal, a personal computer, or the like.

FIG. 2 is a schematic view showing an example of the appearance of a credit card. In the information processing system of the present embodiment, a credit card 40 as shown in FIG. 2 is used for credit card payment at an EC site that accepts purchase applications for goods or services. The upper side of FIG. 2 shows the front surface of the credit card 40, and the lower side shows the back surface of the credit card 40. The credit card 40 shown in FIG. 2 has an IC (Integrated Circuit) chip 44 in which a credit card name (ABC CARD) is printed on the surface and information on the credit card 40 and information on a user (contractor) are stored. It has been incorporated. The credit card name is the name of the card attached to the credit card 40 issued by the card company, and various information is stored in the IC chip 44 by the card company when the credit card 40 is issued. Further, the card number 41, the expiration date 42, and the contractor's name 43 are printed on the surface of the credit card 40. The card number 41 is the identification information assigned to the credit card 40, the expiration date 42 is the expiration date set on the credit card 40, and the contractor's name 43 is the contractor or usage authority of the credit card 40. It is the name of the user who has. The name 43 is written in Roman letters, for example, and is printed by embossing, for example. Further, in the credit card 40 of the present embodiment, a predetermined object is printed in a predetermined place (a plurality of areas) by using an ultraviolet light emitting paint. As the object, for example, a code, a pattern, a pattern, etc., which is a combination of alphabets and numbers, can be used. In the example shown in FIG. 2, an object 45a having a predetermined pattern is printed on one place on the front surface of the credit card 40, and an object 45b having a predetermined pattern and an object 45c having a predetermined code are printed on two places on the back surface. .. The number, printing position, and type of objects printed on the credit card 40 are not limited to the example shown in FIG. 2, and by making the objects different for each credit card 40, the credit card 40 on which different objects are printed for each contractor can be obtained. Can be created. By authenticating an individual based on credit card information and UV image information and permitting the use of the credit card for the holder of such a credit card 40, it is possible to prevent unauthorized use of the card. Can be done.

In the information processing system of the present embodiment, the user accesses the EC site server 20 using the user terminal 30 and requests the purchase of goods or services sold on the EC site. At that time, when the user specifies credit card payment, the user inputs the information (card information) of the credit card 40 using the user terminal 30, and the user terminal 30 transfers the acquired card information to the card company server 10. The credit card 40 is inquired about whether or not it can be used. The card company server 10 determines whether or not to use the credit card 40 in response to an inquiry from the user terminal 30, and transmits the determination result to the user terminal 30. At this time, if the determination result is the use permission of the credit card 40, the card company server 10 issues the permission information indicating the use permission, and the user terminal 30 (the device of the sender of the inquiry) together with the determination result of the use permission. ). Then, the user terminal 30 transmits the permission information received from the card company server 10 to the EC site server 20. When the EC site server 20 receives the permission information from the user terminal 30, the EC site server 20 asks the card company server 10 whether the received permission information is the permission information issued to this user (credit card 40), and the card is used. The inquiry result is acquired from the company server 10. If the permission information received from the EC site server 20 matches the appropriately issued permission information, the card company server 10 transmits an inquiry result indicating that the permission information is appropriate (authentication was successful). If they do not match, send an inquiry result indicating that it is not appropriate (cannot be authenticated). If the inquiry result obtained from the card company server 10 is authenticateable, the EC site server 20 determines that the use of the credit card 40 is permitted, and the payment procedure with the credit card 40 and the product Perform delivery procedures, etc.

FIG. 3 is a block diagram showing a configuration example of the card company server 10 and the EC site server 20. The card company server 10 includes a control unit 11, a storage unit 12, a communication unit 13, an input unit 14, a display unit 15, a reading unit 16, and the like, and each of these units is connected to each other via a bus. The control unit 11 includes one or a plurality of processors such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit). The control unit 11 appropriately executes the control program 12P stored in the storage unit 12 to execute various information processing and control processing to be performed by the card company server 10.

The storage unit 12 includes a RAM (Random Access Memory), a flash memory, a hard disk, an SSD (Solid State Drive), and the like. The storage unit 12 stores in advance various data and the like necessary for executing the control program 12P and the control program 12P executed by the control unit 11. Further, the storage unit 12 temporarily stores data or the like generated when the control unit 11 executes the control program 12P. Further, the storage unit 12 stores the contractor information DB 12a (database) and the EC site DB 12b, which will be described later. The contractor information DB 12a and the EC site DB 12b may be stored in an external storage device connected to the card company server 10, or may be stored in an external storage device capable of communicating with the card company server 10.

The communication unit 13 is an interface for connecting to the network N by wired communication or wireless communication, and transmits / receives information to / from an external device via the network N. The input unit 14 receives an operation input by the administrator who manages the card company server 10, and sends a control signal corresponding to the operation content to the control unit 11. The display unit 15 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 11. The input unit 14 and the display unit 15 may be a touch panel configured as an integral body.

The reading unit 16 reads information stored in a portable storage medium 1a including a CD (Compact Disc) -ROM, a DVD (Digital Versatile Disc) -ROM, a USB (Universal Serial Bus) memory, and the like. The control program 12P and various data stored in the storage unit 12 may be read by the control unit 11 from the portable storage medium 1a via the reading unit 16 and stored in the storage unit 12. Further, the control program 12P and various data stored in the storage unit 12 may be downloaded by the control unit 11 from an external device via the communication unit 13 and stored in the storage unit 12.

The EC site server 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, a display unit 25, and the like, and each of these units is connected to each other via a bus. Since each of these parts 21 to 25 has the same configuration as each part 11 to 15 of the card company server 10, detailed description thereof will be omitted. The storage unit 22 of the EC site server 20 stores the customer information DB 22a, which will be described later, in addition to the control program 22P executed by the control unit 21. The customer information DB 22a may be stored in an external storage device connected to the EC site server 20, or may be stored in an external storage device that the EC site server 20 can communicate with. Further, the EC site server 20 may include a reading unit in the same manner as the card company server 10.

FIG. 4 is a schematic diagram showing a configuration example of DB 12a to 12b, 22a stored in the card company server 10 and the EC site server 20. FIG. 4A shows the contractor information DB 12a, FIG. 4B shows the EC site DB 12b, and FIG. 4C shows the customer information DB 22a. The contractor information DB 12a stores information about a user (contractor) who has been issued a credit card 40 by a credit card company. The contractor information DB 12a shown in FIG. 4A includes a contractor ID column, a name column, a credit card information column, a UV image information column, an EC site information column, and the like, and is associated with the contractor ID, and the contractor name and credit card. Stores information, UV image information, EC site information, etc. The contractor ID column stores the identification information assigned to each user (contractor) who issued the credit card 40, and the name column stores the name of the contractor of the credit card 40 or the user who has the authority to use the credit card 40. To do. The credit card information column stores information such as a card number which is identification information assigned to each credit card 40, an expiration date set on the credit card 40, and a contractor's name printed on the credit card 40. The UV image information string stores information on an object printed on the credit card 40 using the ultraviolet light emitting paint. The object information stored in the UV image information string may be a UV image of the front surface and the back surface of the credit card 40, and is a print position and type (object image) of the object printed on each of the front surface and the back surface. You may. The UV image is an image taken in a state of being irradiated with ultraviolet rays. The EC site information column stores information on an EC site where the contractor has used the credit card 40 (credit card payment). The information on the EC site is, for example, the URL (Uniform Resource Locator) of the EC site. The contractor ID stored in the contractor information DB 12a is issued and stored by the control unit 11 when new contractor information is registered. The name, credit card information, and UV image information stored in the contractor information DB 12a are stored and controlled by the control unit 11 each time the control unit 11 acquires each information about a new contractor via, for example, the input unit 14. Each time the unit 11 acquires a change instruction for each information, the control unit 11 changes the information. The EC site information stored in the contractor information DB 12a is the control unit when the control unit 11 obtains an inquiry about whether or not to use the credit card 40 of each contractor from the EC site server 20 via, for example, the communication unit 13. It is memorized by 11. The stored contents of the contractor information DB 12a are not limited to the example shown in FIG. 4A, and various information related to the contractor and the credit card can be stored.

The EC site DB12b stores information about the EC site contracted with the card company so that the credit card 40 issued by the card company can be used (credit card payment). The EC site DB 12b shown in FIG. 4B includes a site ID column, a site name string, a site information column, and the like, and stores the site name, the site information, and the like of the EC site in association with the site ID. The site ID column stores identification information assigned to each of the EC sites contracted with the card company of the card company server 10. The site name column stores the name given to the EC site, and the site information column stores, for example, the URL of the EC site. The site ID stored in the EC site DB 12b is issued and stored by the control unit 11 when the information of the new EC site is registered. The site name and site information stored in the EC site DB 12b are stored by the control unit 11 each time the control unit 11 acquires each information of a new EC site via, for example, the input unit 14 or the communication unit 13. Each time the 11 acquires a change instruction for each information, the control unit 11 changes the information. The stored contents of the EC site DB 12b are not limited to the example shown in FIG. 4B, and various information related to the EC site can be stored. For example, information about the operator of the EC site may be stored.

The customer information DB 22a stores information about a user (customer) registered as a user on the EC site (EC site server 20). The customer information DB 22a shown in FIG. 4C includes a customer ID column, a name column, an age column, a gender column, an address column, a purchase history column, and the like, and is associated with the customer ID to include the customer's name, age, gender, address, and purchase. Store history etc. The customer ID column stores identification information assigned to each customer registered as a user on the EC site, and the name column, age column, gender column, and address column store the customer's name, age, gender, and address, respectively. The purchase history column stores information about products or services purchased by the customer on the EC site operated by the EC site server 20, the purchase date and time, and the like. The customer ID stored in the customer information DB 22a is issued and stored by the control unit 21 when new customer information is registered. The name, age, gender, and address stored in the customer information DB 22a are stored by the control unit 21 each time the control unit 21 acquires each information about a new customer via, for example, the communication unit 23, and the control unit 21 stores each information. Each time the information change instruction is acquired, the information is changed by the control unit 21. The purchase history stored in the customer information DB 22a is when the EC site server 20 completes processing related to the purchase of goods or services via the EC site (for example, payment processing) in response to a purchase request from the user terminal 30. Is stored by the control unit 11. The stored contents of the customer information DB 22a are not limited to the example shown in FIG. 4C, and various information related to the customer and the purchase history of the customer can be stored.

FIG. 5 is a block diagram showing a configuration example of the user terminal 30. The user terminal 30 includes a control unit 31, a storage unit 32, a communication unit 33, an input unit 34, a display unit 35, a camera 36, a visible light light 37, a UV (ultraviolet) light 38, a reading unit 39, and the like, and each of these units. Are interconnected via a bus. In the user terminal 30, each part 31 to 35 and 39 of the above-mentioned parts 31 to 39 has the same configuration as each part 11 to 16 of the card company server 10, so detailed description thereof will be omitted. The storage unit 32 of the user terminal 30 is an authentication application program (authentication) for the user terminal 30 to inquire the card company server 10 whether or not to use the credit card 40, in addition to the control program 32P executed by the control unit 31. Application) 32AP is stored.

The camera 36 (acquisition unit) is an image pickup unit (shooting unit) having a lens, an image sensor, and the like, and acquires image data of a subject image through the lens. The camera 36 shoots according to the instruction from the control unit 31, and sequentially sends the acquired image data (captured image) to the control unit 31. The visible light 37 has, for example, an LED (Light Emitting Diode) and irradiates visible light according to an instruction from the control unit 31. The UV light 38 (irradiation unit) is a black light that irradiates ultraviolet rays, and irradiates ultraviolet rays in accordance with instructions from the control unit 31. When acquiring a visible light image, the control unit 31 acquires a captured image with the camera 36 in a state where the visible light is irradiated to the subject by the visible light light 37. When acquiring a UV image (ultraviolet image), the control unit 31 acquires a photographed image with the camera 36 in a state of being irradiated with ultraviolet rays by the UV light 38. If the usage environment of the user terminal 30 is sufficiently bright, the visible light light 37 may not be provided on the user terminal 30, and even if the visible light light 37 is provided, the visible light light 37 may be provided. The photographed image (visible light image) may be acquired by the camera 36 without irradiating the visible light. Any or all of the camera 36, the visible light 37, and the UV light 38 may be built in the user terminal 30, or may be externally attached to the user terminal 30 via a cable or the like. Further, the UV light 38 may be configured by attaching a filter that transmits ultraviolet rays to a light irradiation portion of a light provided on a smartphone, a tablet terminal, or the like.

Hereinafter, in the information processing system of the present embodiment, the processing performed by each device when the user makes a purchase at the EC site using the user terminal 30 will be described. 6 and 7 are flowcharts showing an example of the authentication processing procedure of the credit card 40, and FIG. 8 is a schematic view showing a screen example of the user terminal 30. 6 and 7 show the processing performed by the card company server 10 on the left side, the processing performed by the user terminal 30 in the center, and the processing performed by the EC site server 20 on the right side. The following processing is executed by the control unit 11 according to the control program 12P stored in the storage unit 12 of the card company server 10, and is executed by the control unit 31 according to the control program 32P stored in the storage unit 32 of the user terminal 30. It is executed and executed by the control unit 21 according to the control program 22P stored in the storage unit 22 of the EC site server 20. A part of the following processing may be realized by a dedicated hardware circuit.

In the information processing system of the present embodiment, the user of the user terminal 30 accesses the EC site (EC site server 20) using the user terminal 30 and makes a purchase at the EC site. The user terminal 30 accesses the EC site designated by the user via the input unit 34 (S11). The EC site server 20 transmits a web page in response to a request from the user terminal 30 to the user terminal 30 (S12), and the user terminal 30 receives the web page from the EC site server 20 and receives the web page. Is displayed on the display unit 35 (S13). As a result, the user of the user terminal 30 can browse the information of the product or service sold on the EC site.

When there is a product or service to be purchased, the user of the user terminal 30 performs a purchase procedure, and at that time, selects one of credit card payment, cash on delivery payment, convenience store payment, and the like as the payment method of the charge. When the user terminal 30 determines whether or not an instruction to perform credit card payment is received from the user via the input unit 34 (S14) and determines that the payment instruction is not accepted (S14: NO), The process returns to step S11. When receiving an instruction to make a payment by a method other than credit card payment, the user terminal 30 requests the EC site server 20 to make a payment procedure (purchasing procedure) by the instructed payment method. Omit.

When it is determined that the instruction to perform the credit card payment has been accepted (S14: YES), the user terminal 30 requests the EC site server 20 for the payment procedure (purchasing procedure) for the credit card payment (S15). When the EC site server 20 receives a request for a payment procedure for credit card payment, the EC site server 20 requests the user terminal 30 to execute the authentication process of the credit card 40 by the card company server 10 (S16). Specifically, the EC site server 20 transmits an authentication request screen as shown in FIG. 8A to the user terminal 30, and the user terminal 30 receives and receives the authentication request screen transmitted by the EC site server 20. The authentication request screen is displayed on the display unit 35. On the authentication request screen shown in FIG. 8A, a message requesting authentication of the credit card 40 is displayed. Further, the authentication request screen has an input field for inputting the permission information obtained as a result of the authentication process, and an OK button for instructing the transmission of the input permission information to the EC site server 20. The permission information is information that is issued and transmitted to the user terminal 30 when the usage permission (usability) of the credit card 40 is determined by the card company server 10.

The user who confirms the authentication request screen activates the authentication application 32AP using the user terminal 30 and requests the card company server 10 to authenticate the credit card 40. The user terminal 30 may be configured to automatically start the authentication application 32AP when receiving a credit card authentication request from the EC site server 20. The user terminal 30 automatically receives an authentication application 32AP when the user instructs the user to start the authentication application 32AP via the input unit 34, or when the EC site server 20 requests credit card authentication. Is started (S17). When the authentication application 32AP is activated, the user terminal 30 displays an authentication screen as shown in FIG. 8B on the display unit 35 (S18).

The authentication screen shown in FIG. 8B is a screen for accepting information on the credit card 40 to be used for credit card payment in order to inquire the card company server 10 whether or not to use the credit card 40 (whether or not it can be used). Specifically, the authentication screen has an input field for inputting the card number, expiration date, and contractor's name of the credit card 40. Instead of inputting the card number, expiration date, and name in the input field, a photographed image (visible light image) obtained by photographing the surface of the credit card 40 may be input (attached). Therefore, the authentication screen has a "credit card shooting" button for acquiring a captured image of the credit card 40. The authentication screen also has a "UV capture" button for acquiring a UV image of the credit card 40. The authentication screen has an authentication button for instructing the credit card 40 use permission inquiry (execution of authentication) with each input information, and a cancel button for ending the inquiry process.

The user terminal 30 accepts the card number, expiration date, and contractor name (card information) of the credit card 40 (S19). Specifically, when the user terminal 30 accepts the card number, expiration date and contractor's name via the input field on the authentication screen, or the "credit card shooting" button on the authentication screen is operated. Acquires a photographed image (visible light image) of the surface of the credit card 40 with the camera 36. If the shooting environment is not sufficiently bright, the user terminal 30 may acquire a shot image of the credit card 40 with the camera 36 in a state of irradiating the visible light with the visible light light 37. Further, the user terminal 30 acquires a UV image (ultraviolet image) of the area (photographing area) of the credit card 40 designated on the authentication screen by using the UV light 38 and the camera 36 (S20). Specifically, when the "UV shooting" button on the authentication screen is operated, the user terminal 30 shoots a predetermined area of the credit card 40 with the camera 36 in a state of being irradiated with ultraviolet rays by the UV light 38. .. The user terminal 30 determines whether or not the authentication of the credit card 40 is instructed according to whether or not the authentication button on the authentication screen is operated via the input unit 34 (S21). When it is determined that the authentication is not instructed (S21: NO), the user terminal 30 returns to the process of step S19.

When it is determined that the authentication of the credit card 40 is instructed (S21: YES), the user terminal 30 transmits the card information and the UV image acquired via the authentication screen from the communication unit 33 (transmitting unit) to the card company server 10 (S21: YES). It is transmitted to a predetermined device) (S22). As a result, the user terminal 30 inquires the card company server 10 whether or not to use the credit card 40, and requests the permission to use the credit card 40. When the photographed image (visible light image) of the credit card 40 is acquired as the card information of the credit card 40, the user terminal 30 performs image recognition processing on the photographed image, and the card number, the expiration date, and the contractor's name. May be extracted, and the extracted card number, expiration date, and contractor's name may be transmitted to the card company server 10 as card information. Further, the destination information of the destination card company server 10 is set in, for example, the authentication application 32AP.

When the card company server 10 receives the card information and the UV image transmitted by the user terminal 30 in the communication unit 13 (acquisition unit) and receives the card information and the UV image, the control unit 11 (determination unit) receives the card information and the UV image. Based on the received information, an authentication process for determining whether or not to use the credit card 40 is performed (S23). Specifically, the card company server 10 collates the received card information and the UV image with the stored contents of the contractor information DB 12a, and if the received card information and the UV image are stored in the contractor information DB 12a, It is determined that the credit card 40 is permitted to be used (authenticated). On the other hand, if the received card information or UV image is not stored in the contractor information DB 12a, the card company server 10 determines that the credit card 40 cannot be used (cannot be authenticated). When the photographed image (visible light image) of the credit card 40 is received from the user terminal 30 as the card information of the credit card 40, the card company server 10 performs image recognition processing on the received photographed image. , Card number, expiration date and contractor name may be extracted, and authentication may be performed based on the extracted card number, expiration date and contractor name.

The card company server 10 determines whether or not authentication has been performed (S24), and if it determines that authentication cannot be performed (S24: NO), notifies the user terminal 30 that authentication is not possible (credit card 40 cannot be used) (S25). ). When the card company server 10 notifies the user terminal 30 that authentication is not possible, the user terminal 30 displays an authentication failure (for example, a message indicating that authentication is not possible) on the display unit 35 (S26), returns to the process of step S18, and proceeds to FIG. The authentication screen as shown in 8B is displayed again. Then, when the user of the user terminal 30 confirms that the authentication is not possible, he / she re-enters the information (card information and UV image) of the different credit card 40 on the authentication screen, and asks the card company server 10 whether or not to use the credit card 40. Contact us again.

When the card company server 10 determines that the authentication has been successful (S24: YES), the card company server 10 issues the permission information indicating the permission to use the credit card 40 (S27), the authentication result indicating that the authentication has been performed, and the issued permission information. To the user terminal 30 (S28). The card company server 10 stores the issued permission information in association with the information of the credit card 40 or the information of the user (contractor). When the user terminal 30 receives the authentication result and the permission information from the card company server 10, the user terminal 30 displays the authentication result and the permission information on the display unit 35 (S29) and notifies the user. When the user of the user terminal 30 is notified of the use permission (authentication possible) of the credit card 40, the permission information notified together with the use permission is displayed in the input field on the screen shown in FIG. 8A displayed on the display unit 35. Input with the input unit 34 and operate the OK button. The user terminal 30 determines whether or not the permission information has been accepted through the input field in the authentication result input screen (S30), and if it determines that the permission information has not been accepted (S30: NO), waits until it is accepted.

When the user terminal 30 determines that the permission information has been accepted (S30: YES), the user terminal 30 transmits the accepted permission information to the EC site server 20 (S31). When the EC site server 20 receives the permission information from the user terminal 30, the EC site server 20 transmits the received permission information to the card company server 10 (S32), and determines whether or not the permission information is appropriate for the card company server. Contact 10. The EC site server 20 transmits the permission information to the card company server 10 together with the contractor (user) information or the credit card 40 information. When the card company server 10 receives the permission information and the credit card 40 information or the contractor (user) information from the EC site server 20, the card company server 10 uses the credit card 40 information or the contractor (user) information. The permission information stored in association with each other is read from the storage unit 12, and it is determined whether or not the read permission information matches the permission information received from the EC site server 20 (S33). If it is determined that they do not match (S33: NO), the card company server 10 tells the EC site server 20 that the permission information sent from the EC site server 20 is not appropriate information and cannot be authenticated (authentication is not possible). Notify (S34). When the EC site server 20 is notified by the card company server 10 that authentication is not possible, the EC site server 20 notifies the user terminal 30 that authentication is not possible (S35), and the user terminal 30 is notified by the EC site server 20 that authentication is not possible. (For example, a message indicating that authentication cannot be performed) is displayed on the display unit 35 (S36). When the card company server 10 notifies the EC site server 20 that authentication is not possible, the EC site server 20 may send an input screen requesting input of permission information to the user terminal 30 again, and is shown in FIG. 8A. The authentication request screen may be transmitted to the user terminal 30 again.

When the card company server 10 determines that the permission information read from the storage unit 12 and the permission information received from the EC site server 20 match (S33: YES), the credit card 40 can be authenticated (credit). (Permission to use the card 40) is notified to the EC site server 20 (S37). When the EC site server 20 is notified by the card company server 10 that the authentication has been completed, the payment completion screen for notifying that the payment has been completed by performing the payment procedure requested by the user terminal 30 in step S15. Is transmitted to the user terminal 30 (S38). The user terminal 30 receives the payment completion screen transmitted by the EC site server 20, displays the received payment completion screen on the display unit 35 (S39), and ends the process.

By the above-mentioned processing, when the credit card 40 is used for shopping on the EC site, not only the verification (authentication) by the card number, the expiration date, the contractor's name, etc., but also the verification by the UV image of the predetermined area of the credit card 40 is used. (Authentication) is performed to determine whether or not the credit card 40 can be used. Therefore, in the present embodiment, the use of the credit card 40 can be restricted only to the user who has the credit card 40 at hand when using the credit card 40, and the unauthorized use of the credit card 40 on the EC site can be prevented. It should be noted that the printing position and type of the object printed on each credit card 40 may be managed by the card company server 10 by printing the object on the outer surface of the credit card 40 using the ultraviolet light emitting paint. The configuration of the card 40 is not complicated, and the server 10 for the card company may perform the collation based on the UV image in addition to the collation based on the card information, so that the processing related to the authentication does not increase.

In the information processing system of the present embodiment, the card information (card number, expiration date, contractor's name, etc.) input by the user terminal 30 is transmitted to the card company server 10 for authentication processing by the card company server 10. Used. That is, in the present embodiment, the card information does not need to be transmitted from the user terminal 30 to the EC site server 20, and information that can identify the user (purchaser of the product or service) is transmitted to the EC site server 20. Just do it. Therefore, since the card information of the credit card 40 is not transmitted to the EC site server 20, it is possible to prevent the card information (personal information) from leaking from the EC site server 20. Further, since the card information is not transmitted to the EC site server 20, it is possible to avoid a loss of purchasing opportunity by a purchaser who is reluctant to transmit the card information to the EC site server 20.

In the present embodiment, the card company server 10 associates the credit card information of the user (contractor) with the credit card information and the UV image information of the user (contractor) as the usage history of the credit card 40 in the contractor information DB 12a (history storage unit). It stores information on EC sites (EC site information, store information) that have used the card 40. Therefore, in the present embodiment, the card company server 10 receives an authentication request based on card information (for example, a card number) from the user terminal 30 in order to use the credit card 40 at a certain EC site. It is determined whether or not the card 40 will be used for the first time on this EC site, and when the card 40 is used for the first time, the card information (card number, expiration date, contractor name, etc.) of the credit card 40 and the UV image are requested from the user terminal 30. It may be configured to be used. Specifically, when the authentication application 32AP is activated, the user terminal 30 displays an authentication screen for inputting only the card number of the credit card 40, for example, and the card number and the credit card 40 input via the authentication screen. Send the information of the EC site you want to use to the server 10 for the card company and inquire whether the credit card can be used (authentication). The control unit 11 (judgment unit) of the card company server 10 determines whether or not the credit card 40 with the received card number is used for the first time on this EC site in response to an inquiry from the user terminal 30. .. When it is determined that the credit card is used for the first time on the EC site, the control unit 11 (request unit) of the server 10 for the card company sends the card information of the credit card 40 (in addition to the card number, the expiration date and the contractor's name). Etc.) and UV images are requested from the user terminal 30. Then, the card company server 10 acquires the card information and the UV image from the user terminal 30, and performs permission / rejection (authentication) of the credit card based on the acquired card information and the UV image. With such a configuration, when purchasing a product for the first time on each EC site, authentication based on the UV image of the credit card 40 is performed, and from the next time, only authentication based on the card information of the credit card 40 is required for the credit card 40. It is convenient because it can be used.

The credit card 40 in the above-described embodiment is a credit card in which an object is printed on the outer surface using an ultraviolet light emitting paint. However, in the system of the present disclosure, it is possible to use a credit card configured so that information can be acquired by irradiating with invisible light. For example, the outer surface or internal structure of a credit card may be configured so that a predetermined shape (object) is included in an X-ray image taken by irradiating X-rays. In this case, it is possible to determine whether or not the credit card can be used based on the object extracted from the X-ray image taken by irradiating the credit card with X-rays. Further, the credit card may be configured so that the infrared image taken by irradiating infrared rays includes a predetermined shape (object). For example, a credit card on which an object is printed using a paint whose temperature changes with infrared irradiation may be used. In this case, it is possible to determine whether or not the credit card can be used based on the object extracted from the infrared image taken by irradiating the credit card with infrared rays.

(Embodiment 2)
When the card company server 10 receives credit card information (card information and UV image) from the user terminal 30 for credit card authentication, the received UV image is printed on the credit card with ultraviolet light emitting paint. An information processing system having a configuration for recognizing (extracting) the existing object will be described. Since the information processing system of the present embodiment can be realized by the same device as the information processing system of the first embodiment, the description of the configuration will be omitted.

FIG. 9 is a flowchart showing an example of the authentication processing procedure of the credit card 40 in the second embodiment. The process shown in FIG. 9 is a process in which step S41 is added before step S23 in the processes shown in FIGS. 6 and 7. The same steps as in FIGS. 6 and 7 will be omitted. Further, in FIG. 9, the illustrations of steps S11 to S14 in FIG. 6 and each step in FIG. 7 are omitted.

In the information processing system of the present embodiment, when the card company server 10 receives the card information and the UV image transmitted by the user terminal 30 in step S22, the control unit 11 (recognition unit) receives the card information and the UV image from the received UV image. Recognize (extract) an object printed with UV-emitting paint on the subject's credit card. For example, an image (template) of an object printed on a credit card 40 is stored in the storage unit 12 in association with an object type or an object ID, and an object existing in the UV image is searched by, for example, a template matching technique. To do. When the card company server 10 can search for an object in the UV image, the card company server 10 specifies the type of the searched object or the object ID. Then, the card company server 10 performs an authentication process for determining whether or not to use the credit card 40 based on the card information received from the user terminal 30 and the specified object type (or object ID) (S23). ). Here, the card company server 10 collates the received card information and the specified object type (object ID) with the stored contents of the contractor information DB 12a, and if it is stored in the contractor information DB 12a, this credit card. It is determined that 40 usage permits (authentication was successful). In the present embodiment, the UV image information stored in the contractor information DB 12a can be the print position and type (object ID) of the object printed on the front surface and the back surface of the credit card 40, respectively. After that, the card company server 10 performs the processes after step S24.

By the above-mentioned treatment, the same effect as that of the first embodiment can be obtained in the present embodiment as well. Further, in the present embodiment, the card company server 10 identifies and identifies the types (object IDs) of the objects 45a to 45c printed on the subject credit card 40 from the UV image taken by the user terminal 30. It is determined (authenticated) whether or not the credit card 40 can be used based on the type of object (object ID). Therefore, the storage unit 12 of the card company server 10 may store the print positions and types (object IDs) of the objects 45a to 45c printed on the credit card 40 as information for collating the UV image. , The amount of UV image information stored in the storage unit 12 (contractor information DB 12a) can be reduced.

(Embodiment 3)
An information processing system in which user information (customer information) is registered in the EC site server 20 will be described. Since the information processing system of the present embodiment can be realized by the same device as the information processing system of the first embodiment, the description of the configuration will be omitted. In the information processing system of the present embodiment, the configuration of the customer information DB 22a stored in the storage unit 22 of the EC site server 20 is slightly different from that of the first embodiment.

FIG. 10 is a schematic view showing a configuration example of the customer information DB 22a of the third embodiment. Similar to the customer information DB 22a shown in FIG. 4C, the customer information DB 22a shown in FIG. 10 includes a customer ID column, a name column, an age column, a gender column, an address column, and a purchase history column, and further includes a card company information column and a card identification. Includes information string, authentication availability information string, etc. The card company information column stores information about the card company that issued the customer's credit card. The card identification information column is information for identifying a credit card, and stores, for example, identification information issued by the EC site server 20 for each credit card. The authentication availability information column stores the card information of the credit card 40 and information indicating whether or not the use of the credit card 40 is permitted (whether or not it is authenticated) by the authentication process based on the UV image. If it is authenticated, "authenticated" is stored, and if it is not authenticated, "authentication not possible" is stored. The card company information stored in the customer information DB 22a is stored by the control unit 21 when the control unit 21 acquires the card company information of the credit card 40 via, for example, the communication unit 23. The card identification information stored in the customer information DB 22a is issued and stored by the control unit 21 when the control unit 21 acquires information about a new customer via, for example, the communication unit 23. The authentication availability information stored in the customer information DB 22a is stored as "authenticated" by the control unit 21 when the card company server 10 notifies that the customer's credit card 40 has been authenticated.

Hereinafter, in the information processing system of the present embodiment, the processing performed by each device when the user of the user terminal 30 registers his / her own information (customer information) in the EC site server 20 will be described. 11 and 12 are flowcharts showing an example of a user registration processing procedure by the EC site server 20, and FIG. 13 is a schematic view showing a screen example of the user terminal 30. In FIGS. 11 and 12, the processing performed by the card company server 10 is shown on the left side, the processing performed by the user terminal 30 in the center, and the processing performed by the EC site server 20 on the right side. A part of the following processing may be realized by a dedicated hardware circuit.

In the information processing system of the present embodiment, the user terminal 30 accesses the EC site designated by the user via the input unit 34 (S51). The EC site server 20 transmits a web page in response to a request from the user terminal 30 to the user terminal 30 (S52), and the user terminal 30 displays the web page received from the EC site server 20 on the display unit 35. (S53).

Since the purchasing procedure (settlement procedure) can be simplified by registering the user's customer information on the EC site, the user of the user terminal 30 can register the user on the EC site via the web page. Instruct to execute. The user terminal 30 determines whether or not the user registration execution instruction has been accepted from the user via the input unit 34 (S54), and if it determines that the user registration execution instruction has not been accepted (S54: NO), the process of step S51 is performed. go back.

When it is determined that the user registration execution instruction has been accepted (S54: YES), the user terminal 30 requests the EC site server 20 for the registration procedure (S55). When the EC site server 20 receives the request for the registration procedure, the EC site server 20 transmits a registration screen as shown in FIG. 13A to the user terminal 30 (S56). The user terminal 30 receives the registration screen transmitted by the EC site server 20, and displays the received registration screen on the display unit 35 (S57).

The registration screen shown in FIG. 13A has an input field for inputting the name, age, gender, address, credit card company, and the like of the user (customer of the EC site) of the user terminal 30. A pull-down menu may be set in the input field of the card company so that one of the pre-registered card companies can be selected. Further, the registration screen has a registration button for instructing the execution of user registration with each input information, and a cancel button for ending the user registration process. The user terminal 30 receives customer information such as a user's name, age, gender, address, and credit card company through an input field on the registration screen (S58). The user terminal 30 determines whether or not the registration of the user's customer information is instructed according to whether or not the registration button on the registration screen is operated via the input unit 34 (S59). If it is determined that registration has not been instructed (S59: NO), the user terminal 30 continues the process of step S58.

When it is determined that the registration of the customer information is instructed (S59: YES), the user terminal 30 transmits the customer information acquired via the registration screen to the EC site server 20 (S60). When the EC site server 20 receives the customer information transmitted by the user terminal 30, it issues a customer ID, associates it with the customer ID, and stores the received customer information in the customer information DB 22a (S61). Then, the EC site server 20 issues card identification information in response to the received customer information (card company information) (S62). The EC site server 20 stores the issued card identification information in the customer information DB 22a. Then, the EC site server 20 requests the user terminal 30 to authenticate the credit card 40 by the card company server 10 (S63). Here, the EC site server 20 transmits an authentication request screen as shown in FIG. 13B to the user terminal 30, and the user terminal 30 displays the authentication request screen received from the EC site server 20 on the display unit 35. .. The EC site server 20 transmits the card identification information issued in step S62 to the user terminal 30 when requesting the user terminal 30 to authenticate the credit card 40.

The user who confirms the authentication request screen activates the authentication application 32AP using the user terminal 30 and requests the card company server 10 to authenticate the credit card 40, as in the first embodiment. Therefore, the user terminal 30 performs the same processing as steps S17 to S21 in FIG. 6 described in the first embodiment (S64 to S68). That is, the user terminal 30 activates the authentication application 32AP (S64) and displays the authentication screen as shown in FIG. 8B on the display unit 35 (S65). Further, the user terminal 30 receives card information such as the card number, expiration date, and contractor's name of the credit card 40 (S66), and acquires a UV image of a predetermined area (designated area) of the credit card 40 (S67). .. The user terminal 30 may acquire a photographed image (visible light image) obtained by photographing the surface of the credit card 40 with the camera 36 instead of the card information. The user terminal 30 determines whether or not the authentication of the credit card 40 is instructed according to whether or not the authentication button on the authentication screen is operated via the input unit 34 (S68). When it is determined that the authentication is not instructed (S68: NO), the user terminal 30 returns to the process of step S66.

When it is determined that the authentication of the credit card 40 is instructed (S68: YES), the user terminal 30 uses the card information and the UV image acquired through the authentication screen, the site information related to the EC site to be registered as a user, and the EC site. The card identification information issued by the server 20 is transmitted to the server 10 for the card company (S69). The site information is information for identifying an EC site, and for example, destination information for accessing the EC site can be used. When the photographed image (visible light image) of the credit card 40 is acquired as the card information of the credit card 40, the user terminal 30 performs image recognition processing on the photographed image, and the card number, the expiration date, and the contractor's name. May be extracted and the extracted information may be transmitted to the card company server 10 as card information.

When the card company server 10 receives the card information, the UV image, the site information, and the card identification information transmitted by the user terminal 30, the card company server 10 collates the received card information and the UV image with the stored contents of the contractor information DB 12a, and this An authentication process for determining whether or not to use the credit card 40 is performed (S70). The card company server 10 determines whether or not authentication has been performed (S71), and if it determines that authentication cannot be performed (S71: NO), notifies the user terminal 30 that authentication is not possible (credit card 40 cannot be used) (S72). ). When the card company server 10 notifies the user terminal 30 that the authentication is not possible, the user terminal 30 displays the authentication failure (for example, a message indicating that the authentication cannot be performed) (S73), returns to the process of step S65, and returns to the process of step S65, and the authentication shown in FIG. 8B. Display the screen again.

When the card company server 10 determines that the authentication has been performed (S71: YES), the authentication result indicating that the authentication has been performed and the card identification information received from the user terminal 30 are combined with the site information received from the user terminal 30. Based on this, it is transmitted to the EC site server 20 (S74). When the EC site server 20 receives the authentication result and the card identification information from the card company server 10, it stores "authenticated" in the customer information DB 22a as the authentication availability information corresponding to the received card identification information (S75). .. The EC site server 20 completes the registration process requested by the user terminal 30 in step 55, and transmits a registration completion screen notifying that the registration process is completed to the user terminal 30 (S76). The user terminal 30 receives the registration completion screen transmitted by the EC site server 20, displays the received registration completion screen on the display unit 35 (S77), and ends the process.

When the customer information of the EC site customer (user of the user terminal 30) is registered in the EC site server 20 by the above-mentioned process, the card information (card number, expiration date and contractor name) is registered in the card company server 10. ), But also the verification (authentication) by the UV image of the predetermined area of the credit card 40 is performed to determine whether or not the credit card 40 can be used. Therefore, in the present embodiment, the use of the credit card 40 is permitted and the usable credit card 40 can be registered only when the user who has the credit card 40 at hand registers the user on the EC site. In the present embodiment, the customer information registered in the EC site server 20 does not include card information such as a card number, an expiration date, and a contractor's name, and a UV image of the credit card 40. Therefore, it is possible to prevent various information of the credit card 40 from being leaked from the EC site server 20.

FIG. 14 is a flowchart showing an example of a payment processing procedure on an EC site. In FIG. 14, the processing performed by the user terminal 30 is shown on the left side, and the processing performed by the EC site server 20 is shown on the right side. A part of the following processing may be realized by a dedicated hardware circuit. The user terminal 30 accesses the EC site designated by the user via the input unit 34 (S81), and the EC site server 20 transmits a web page in response to the request from the user terminal 30 to the user terminal 30. (S82), the user terminal 30 displays the web page received from the EC site server 20 (S83).

When the user terminal 30 determines whether or not an instruction to perform credit card payment is received from the user via the input unit 34 (S84) and determines that the payment instruction is not accepted (S84: NO), The process returns to the process of step S81. Again, when receiving a payment instruction by a payment method other than credit card payment, the user terminal 30 requests the EC site server 20 to perform the payment procedure by the instructed method. When it is determined that the instruction to perform the credit card payment has been accepted (S84: YES), the user terminal 30 requests the EC site server 20 to perform the payment procedure for the credit card payment (S85). Specifically, the user terminal 30 transmits a payment procedure request including user identification information (for example, a customer ID assigned by the EC site server 20) to the EC site server 20.

When the EC site server 20 receives a request for payment procedure by credit card payment, the credit card of this user (customer) has been authenticated based on the user's identification information (customer ID) received from the user terminal 30. It is determined whether or not it is (S86). Specifically, the EC site server 20 determines whether or not "authenticated" is stored in the customer information DB 22a as authentication availability information corresponding to the customer ID received from the user terminal 30. The EC site server 20 determines that the credit card has been authenticated when "authenticated" is stored as the authentication availability information, and when "authenticated" is not stored, the credit card is not authenticated. Judge. When it is determined that the credit card has been authenticated (S86: YES), the EC site server 20 performs the payment procedure and transmits a payment completion screen notifying that the payment has been completed to the user terminal 30 (S87). .. The user terminal 30 receives the payment completion screen transmitted by the EC site server 20 and displays the received payment completion screen (S88).

On the other hand, when it is determined that the credit card has not been authenticated (S86: NO), the EC site server 20 performs the process of step S63 in FIG. 11 and displays the authentication request screen as shown in FIG. 13B to the user terminal 30. It sends and requests the credit card authentication process (S63). After that, the user terminal 30, the EC site server 20, and the card company server 10 perform the processes of steps S64 to S77 shown in FIGS. 11 and 12, and the card company server 10 authenticates the credit card 40. Note that in FIG. 14, the illustrations of steps S65 to S77 in FIG. 12 are omitted.

By the above-mentioned treatment, the same effect as that of the first embodiment can be obtained in the present embodiment as well. Further, in the present embodiment, by registering the customer information in the EC site server 20, it is possible to shop at the EC site using the credit card 40 once authenticated. Further, in the present embodiment, the customer information of the user is registered in the server 20 for the EC site, but the card information of the user's credit card 40 and the UV images (objects 45a to 45c) are not registered. Therefore, it is possible to prevent the card information of the credit card 40, the UV image, or the information of the object printed on the credit card 40 from being leaked from the EC site server 20. Further, in the present embodiment, the authentication process of the credit card 40 by the UV image of the credit card 40 only needs to be performed once when the customer information is registered in the EC site server 20, so that the operation burden on the user does not increase.

In the present embodiment, the EC site server 20 issues card identification information to each credit card 40, and each credit card 40 is identified using the card identification information. Therefore, in this case, the transmission and reception of personal information such as a card number can be minimized. In addition, each credit card 40 may be identified by using the card number written on the credit card 40 instead of the card identification information.

In the present embodiment, the card company server 10 stores the information of the EC site in which each contractor has used the credit card 40 in the contractor information DB 12a. Therefore, the card company server 10 can grasp the EC site registered as a user by each contractor (user). Therefore, for example, when customer information is leaked from one of the EC sites (EC site server 20), there is a possibility that the customer information registered on the EC site is leaked from the card company to each contractor. It is possible to call attention to this, and it is possible to prevent the use of the credit card 40, which may have leaked customer information. This embodiment can be applied to the information processing system of the second embodiment, and the same effect can be obtained even when the information processing system of the second embodiment is applied.

(Embodiment 4)
An information processing system in which an authentication process based on a UV image of a credit card is performed when a credit card is used in a physical store will be described. FIG. 15 is a schematic diagram showing a configuration example of the information processing system of the fourth embodiment. The information processing system of the present embodiment includes a credit card processing terminal 50 installed in an actual store instead of the EC site server 20 in the information processing system of the first embodiment. The credit card processing terminal 50 is configured to be connectable to the network N. One credit card processing terminal 50 may be provided in each physical store, or a plurality of credit card processing terminals 50 may be provided in each physical store. In the present embodiment, the card company server 10, the user terminal 30, and the credit card 40 have the same configurations as those in the first embodiment, and thus detailed description thereof will be omitted. The card company server 10 of the present embodiment does not need to store the EC site DB 12b in the storage unit 12, but may store it.

In the information processing system of the present embodiment, when the user uses the credit card 40 for shopping at a physical store, the user terminal 30 is used to acquire the information (card information and UV image) of the credit card 40, and the acquired information is obtained. It is transmitted to the card company server 10 to inquire about the permission or disapproval of the credit card 40, and the usage permission is obtained. The card company server 10 determines whether or not the credit card 40 can be used in response to an inquiry from the user terminal 30, and when it is determined that the credit card 40 can be used (usable), the predetermined time (for example, 1 hour to 1 hour) from the time of the determination is determined. Within a few hours), I will allow the use of this credit card 40. Specifically, when an inquiry about whether or not to use the credit card 40 is received from any of the credit card processing terminals 50 within a predetermined time after determining the permission to use, the card company server 10 receives the credit. The permission to use the card 40 is output to the credit card processing terminal 50.

FIG. 16 is a block diagram showing a configuration example of the card company server 10 and the credit card processing terminal 50. The card company server 10 is the same as the first embodiment except that the EC site DB 12b is not stored in the storage unit 12, and thus the description thereof will be omitted. The credit card processing terminal 50 includes a storage unit 51, a card information reading unit 52, a communication unit 53, an input unit 54, a display unit 55, and the like, and each of these units is connected to each other via a bus. The storage unit 51 includes, for example, a flash memory, and stores the terminal ID 51a, which is identification information assigned to each of the credit card processing terminals 50. The card information reading unit 52 reads the information (card information) stored in the IC chip 44 provided on the credit card 40. When the credit card 40 has a magnetic stripe in which the card information is stored, the card information reading unit 52 may read the card information from the magnetic stripe. The communication unit 53 is an interface for connecting to the network N by wired communication or wireless communication, and for example, the card information read by the card information reading unit 52 is transmitted to a predetermined card company server 10. The input unit 54 receives an operation input by an operator who operates the credit card processing terminal 50, and the display unit 55 displays various information to be notified to the operator.

Hereinafter, in the information processing system of the present embodiment, the processing performed by each device when the user uses the credit card 40 for shopping at the actual store will be described. FIG. 17 is a flowchart showing an example of the authentication processing procedure of the credit card 40. In FIG. 17, the processing performed by the user terminal 30 is shown on the left side, and the processing performed by the card company server 10 is shown on the right side. A part of the following processing may be realized by a dedicated hardware circuit.

In the information processing system of the present embodiment, a user who wants to use the credit card 40 for shopping at a physical store activates the authentication application 32AP using the user terminal 30 and credits before performing the purchasing procedure (settlement procedure). Request the card company server 10 for permission to use the card 40. When the user instructs the user to start the authentication application 32AP via the input unit 34, the user terminal 30 starts the authentication application 32AP (S91). When the authentication application 32AP is activated, the user terminal 30 displays an authentication screen as shown in FIG. 8B on the display unit 35 (S92). Then, the user terminal 30 accepts the card information (card number, expiration date and contractor's name) via the input field on the authentication screen, or acquires a photographed image of the surface of the credit card 40 with the camera 36. Accepts the card information of the credit card 40 (S93). Further, the user terminal 30 acquires a UV image of a predetermined area of the credit card 40 by using the UV light 38 and the camera 36 (S94). When the user terminal 30 determines whether or not the credit card 40 is instructed to authenticate according to whether or not the authentication button on the authentication screen is operated (S95), and determines that the authentication is not instructed (S95). S95: NO), the process returns to step S93.

When it is determined that the credit card 40 is instructed to be authenticated (S95: YES), the user terminal 30 transmits the card information and the UV image acquired via the authentication screen from the communication unit 33 to the card company server 10 (S96). ). When the card company server 10 receives the card information and the UV image from the user terminal 30, the card company server 10 performs an authentication process for determining whether or not to use the credit card 40 based on the received information (S97). The card company server 10 determines whether or not authentication has been performed (S98), and if it determines that authentication cannot be performed (S98: NO), notifies the user terminal 30 that authentication is not possible (credit card 40 cannot be used) (S99). ). When the card company server 10 notifies the user terminal 30 that authentication is not possible, the user terminal 30 displays an authentication failure (for example, a message indicating that authentication is not possible) on the display unit 35 (S100), returns to the process of step S92, and proceeds to FIG. The authentication screen shown in 8B is displayed again.

When the card company server 10 determines that the authentication has been successful (S98: YES), the card company server 10 issues the permission information indicating the permission to use the credit card 40 (S101), the authentication result indicating that the authentication has been performed, and the issued permission information. To the user terminal 30 (S102). The card company server 10 stores the issued permission information in the storage unit 12 in association with the information of the credit card 40 or the information of the user (contractor) (S103). When the user terminal 30 receives the authentication result and the permission information from the card company server 10, the user terminal 30 displays the authentication result and the permission information on the display unit 35 (S104) and notifies the user. When the user of the user terminal 30 is notified of the permission to use the credit card 40, the purchase procedure (the permission information notified together with the usage permission is displayed on the user terminal 30 or the permission information is memorized (memorized)). Settlement procedure).

FIG. 18 is a flowchart showing an example of a payment processing procedure using the credit card 40. In FIG. 18, the processing performed by the credit card processing terminal 50 is shown on the left side, and the processing performed by the card company server 10 is shown on the right side. A part of the following processing may be realized by a dedicated hardware circuit. The user who has obtained the permission to use the credit card 40 takes the desired product to the cashier counter of the actual store and performs the purchase procedure with the credit card 40. The clerk of the actual store reads the card information of the credit card 40 by the card information reading unit 52 of the credit card processing terminal 50 (S111), and transmits the read card information to the card company server 10 (S112). The card information read from the credit card 40 includes the information of the card company server 10 corresponding to the credit card 40, and the credit card processing terminal 50 is the card company based on the information included in the card information. The card information is transmitted to the server 10.

When the card company server 10 receives the card information from the credit card processing terminal 50, the card company server 10 requests the credit card processing terminal 50 for the permission information issued to the credit card 40 of the received card information (S113). .. In step S103 during the process shown in FIG. 17, when the card company server 10 issues the permission information to the credit card 40, the permission information is associated with the information of the credit card 40 or the contractor. It is stored in the storage unit 12. Therefore, when the card information received from the credit card processing terminal 50 is stored in the storage unit 12, the card company server 10 corresponds to the received card information within a predetermined time from the issue date and time of the permission information. Request the permission information from the credit card processing terminal 50.

When the credit card processing terminal 50 requests the permission information from the card company server 10, the credit card processing terminal 50 displays a request for inputting the permission information (S114). For example, the credit card processing terminal 50 displays a message requesting input of permission information on the display unit 55. The credit card processing terminal 50 may be configured to include a notification light for notifying a request for input of permission information instead of the display unit 55. In this case, the permission information is turned on or blinked by turning on or blinking the notification light. You may request the input of. The credit card processing terminal 50 determines whether or not the permission information has been accepted via the input unit 54 (S115), and if it determines that the permission information has not been accepted (S115: NO), waits until it is accepted.

When it is determined that the permission information has been accepted (S115: YES), the credit card processing terminal 50 transmits the accepted permission information to the card company server 10 (S116). When the card company server 10 receives the permission information from the credit card processing terminal 50, whether or not the received permission information matches the permission information stored in the storage unit 12 in step S103 during processing shown in FIG. Is determined (S117). If it is determined that they do not match (S117: NO), the card company server 10 informs the credit card processing terminal 50 that the permission information transmitted from the credit card processing terminal 50 is not appropriate information and cannot be authenticated (authentication is not possible). Notify (S118). When the credit card processing terminal 50 is notified by the card company server 10 that the authentication is not possible, the credit card processing terminal 50 displays an authentication failure (for example, a message indicating that the authentication cannot be performed) (S119), returns to the process of step S114, and returns to the processing of the permission information The input request is displayed again (S114).

When it is determined that the permission information matches (S117: YES), the card company server 10 performs a payment procedure and notifies the credit card processing terminal 50 that the payment has been completed (S120). That is, the control unit 11 (permission unit) of the card company server 10 permits the use of the credit card 40, which has been inquired about whether or not to use the credit card 40 from the credit card processing terminal 50, and performs a payment procedure using the credit card 40. When the credit card processing terminal 50 is notified by the card company server 10 that the payment has been completed, the credit card processing terminal 50 displays that the payment has been completed (S121), and ends the processing. The credit card processing terminal 50 may display a message indicating that the payment has been completed on the display unit 55 to notify the completion of the payment, or when the credit card processing terminal 50 is provided with a notification light for notifying the completion of the payment. You may notify the completion of payment by turning on or blinking the notification light.

By the above processing, even when the credit card 40 is used for shopping at a physical store, not only the authentication by the card information such as the card number, the expiration date and the contractor's name, but also the UV image of the predetermined area of the credit card 40 is used. Authentication is done. Therefore, the use of the credit card 40 can be restricted only to the user who has the credit card 40 at hand, and the unauthorized use of the credit card 40 can be prevented.

In the present embodiment, when the credit card 40 is authenticated by the card company server 10, that is, when the permission to use the credit card 40 is obtained, only the authentication by the card information of the credit card 40 is performed within a predetermined time. Allows the use of the credit card 40. Therefore, unauthorized use of the credit card 40 can be prevented by performing authentication using the UV image of the credit card 40, and within a predetermined time after being authenticated by the UV image of the credit card 40, the UV image of the credit card 40 is used. By eliminating the need for authentication, it is possible to save the trouble of taking a UV image of the credit card 40, and the convenience is improved. Further, in the present embodiment, the UV image of the credit card 40 acquired by using the user terminal 30 is transmitted only to the server 10 for the card company, and the credit card processing terminal 50 in the store cannot acquire the UV image. Therefore, it is possible to prevent the UV image of the credit card 40 from leaking from the credit card processing terminal 50.

In the present embodiment, if it is within a predetermined time after the permission to use the credit card 40 is obtained by the authentication by the UV image of the credit card 40, not only the credit card 40 is used in the actual store but also the credit on the EC site. Regarding the use of the card 40, it is also possible to eliminate the need for authentication by the UV image of the credit card 40. In this case, even a user who uses the EC site can save the trouble of taking a UV image of the credit card 40, and the convenience is improved.

This embodiment can be applied to the information processing system of the second to third embodiments, and the same effect can be obtained even when the information processing system of the second to third embodiments is applied. When applied to the information processing system of the third embodiment, the use permission is obtained by registering the user on the EC site within a predetermined time after the use permission of the credit card 40 is obtained by the authentication by the UV image of the credit card 40. It is possible to register as a user with the obtained credit card 40.

(Embodiment 5)
An information processing system that acquires (photographs) a UV image and a visible light image of a credit card 40 with a dedicated device (card authentication device) will be described. The information processing system of the present embodiment includes a card authentication device 60 in addition to each device in the information processing system of the first embodiment. In the present embodiment, the card company server 10, the EC site server 20, the user terminal 30, and the credit card 40 have the same configurations as those in the first embodiment, and thus detailed description thereof will be omitted. The user terminal 30 of the present embodiment does not have to include the camera 36, the visible light light 37, and the UV light 38. The card authentication device 60 may be distributed to each contractor together with the credit card 40 when the credit card 40 is issued, or may be provided in a physical store.

FIG. 19 is a schematic diagram showing an external example of the card authentication device 60, and FIG. 20 is a schematic diagram showing a configuration example of the card authentication device 60. The card authentication device 60 shown in FIG. 19 has an elliptical pillar-shaped housing, and light (visible light or ultraviolet light) is incident on one end surface of an ultraviolet irradiation window 64a emitted from a UV light 64 and a camera 63. An incident window 63a is provided for this purpose. Further, on the side surface of the housing of the card authentication device 60, a visible light shooting button 62a for instructing the shooting of a visible light image (first shooting process) and a UV image shooting (second shooting process) are instructed. The UV photographing button 62b and the transmitting button 62c for instructing the transmission of the photographed image to the external device are provided.

The card authentication device 60 includes a storage unit 61, an input unit 62, a camera 63, a UV light 64, a communication unit 65, a display unit 66, and the like, and each of these units is connected to each other via a bus. The storage unit 61 stores, for example, a flash memory and stores the device ID 61a, which is identification information assigned to each of the card authentication devices 60. The input unit 62 includes a visible light photographing button 62a, a UV photographing button 62b, and a transmission button 62c, and receives an operation input by an operator who operates the card authentication device 60. The camera 63 and the UV light 64 are the same as the camera 36 and the UV light 38 provided in the user terminal 30 of the first embodiment. Further, similarly to the user terminal 30 of the first embodiment, the card authentication device 60 may be provided with a visible light light. The communication unit 65 is an interface for connecting to the network N by wired communication or wireless communication, and transmits, for example, a visible light image and a UV image taken by the camera 63 to a predetermined device. The display unit 66 displays various information to be notified to the operator. The display unit 66 may be configured to include a notification light 66a for notifying the operating state of the card authentication device 60. For example, a notification light for notifying that the shooting of a visible light image is completed, a notification light for notifying that the shooting of a UV image is completed, and a notification light for notifying that the transmission of the shot image is completed. A notification light or the like may be provided on the display unit 66.

The card authentication device 60 having the above-described configuration may be used in place of the user terminal 30 when capturing a visible light image and a UV image of the credit card 40 in the information processing system of the first to fourth embodiments. In this case, for example, the card authentication device 60 and the user terminal 30 are configured to be able to communicate directly via the network N. Then, the card authentication device 60 transmits the visible light image and the UV image taken by the camera 63 to the user terminal 30, so that the user terminal 30 acquires the visible light image and the UV image of the credit card 40. Can be configured. In this case, the user terminal 30 does not need to take a visible light image and a UV image using the camera 36, and the user terminal 30 does not need to include the camera 36 and the UV light 38. Even in such a configuration, the same effect as that of the first to fourth embodiments can be obtained.

In the following, the card authentication device 60 does not transmit the visible light image and the UV image taken by the camera 63 to the user terminal 30, but transmits them to the card company server 10 to inquire whether or not to use the credit card 40. The configuration to be performed will be described. In the information processing system of the present embodiment, when the user wants to authenticate the credit card 40, the card authentication device 60 is used to take a visible light image and a UV image of the credit card 40, and the server 10 for the card company is used. Inquire about the permission or disapproval of the credit card 40 by sending. The case where the credit card 40 is desired to be authenticated is, for example, when the user terminal 30 acquires the authentication request screen shown in FIG. 8A from the EC site server 20 in the first and second embodiments, the EC site in the third embodiment. There is a case where the user is registered for the user, or there is a case where the user wants to obtain the permission to use the credit card 40 from the card company server 10 in the fourth embodiment.

FIG. 21 is a schematic diagram showing a configuration example of the contractor information DB 12a stored in the card company server 10 of the fifth embodiment. The contractor information DB 12a of the present embodiment includes a device ID string and an authentication availability information string in addition to the configuration of the contractor information DB 12a shown in FIG. 4A. The device ID column stores identification information assigned to each of the card authentication devices 60 distributed when issuing the credit card 40 to the contractor of the credit card 40. The authentication availability information column stores information indicating whether or not the use of the credit card 40 is permitted (whether or not it is authenticated) by the authentication process based on the visible light image and the UV image of the credit card 40. If it is authenticated, "authenticated" is stored, and if it is not authenticated, "authentication not possible" is stored. The authentication permission / rejection information column may store the authentication result in association with the date / time (authentication date / time) when the use permission / rejection (authentication availability) of each credit card 40 is determined. The device ID stored in the contractor information DB 12a is stored by the control unit 11 when new contractor information is registered. The device ID of the card authentication device 60 distributed to the contractor is stored. The authentication result is stored in the contractor information DB 12a by the control unit 11 when the control unit 11 performs the authentication process based on the visible light image and the UV image received from the card authentication device 60. To. The stored contents of the contractor information DB 12a are not limited to the example shown in FIG.

FIG. 22 is a flowchart showing an example of the authentication processing procedure of the credit card 40 in the fifth embodiment. In FIG. 22, the processing performed by the card authentication device 60 is shown on the left side, and the processing performed by the card company server 10 is shown on the right side. A part of the following processing may be realized by a dedicated hardware circuit. In the information processing system of the present embodiment, the card authentication device 60 determines whether or not the visible light photographing button 62a of the input unit 62 has been operated (S131), and when it is determined that the operation has been performed (S131: YES). ), A visible light image is acquired by taking a picture using the camera 63 (S132). When it is determined that the visible light photographing button 62a is not operated (S131: NO), the card authentication device 60 skips the process of step S132. The area to be captured as a visible light image is the entire area on the surface of the credit card 40. For example, it is described in the instruction manual of the card authentication device 60, and the user can see it according to the description in the instruction manual. Acquire an optical image. In addition, the card authentication device 60 is configured to determine whether or not the captured visible light image includes the card number, expiration date, and contractor's name. If it is determined that the image is not included, re-imaging is requested. A configuration or the like may be provided.

Next, the card authentication device 60 determines whether or not the UV shooting button 62b of the input unit 62 has been operated (S133), and if it determines that the UV shooting button 62b has been operated (S133: YES), the UV light 64 and the camera 63 are used. And take a picture to acquire a UV image (S134). When it is determined that the UV photographing button 62b is not operated (S133: NO), the card authentication device 60 skips the process of step S134. The area to be captured as a UV image is described in, for example, the instruction manual of the card authentication device 60, or if the EC site is being browsed, the user is notified via the EC site, and the user describes the instruction manual or Acquire UV images according to the notification from the EC site.

The card authentication device 60 determines whether or not the transmission button 62c of the input unit 62 has been operated (S135), and if it determines that the transmission button 62c has been operated (S135: YES), two images, a visible light image and a UV image, are displayed. It is determined whether or not the image has been taken (S136). When it is determined that the transmission button 62c is not operated (S135: NO), or when it is determined that two images, a visible light image and a UV image, have not been captured (S136: NO), the card authentication device 60 Returns to the process of step S131. When it is determined that two images have been taken (S136: YES), the card authentication device 60 communicates the acquired visible light image and UV image with the device ID 61a stored in the storage unit 61. To the card company server 10 (S137).

When the card company server 10 receives a visible light image, a UV image, and a device ID 61a from the card authentication device 60, the card company server 10 authenticates to determine whether or not to use the credit card 40 based on the received visible light image and UV image. The process is performed (S138). The card company server 10 performs image recognition processing on the received visible light image, and extracts the card number, expiration date, and contractor name (card information) of the subject credit card 40. Further, the card company server 10 performs, for example, template matching processing on the received UV image, and identifies the object (UV image information) of the credit card 40 appearing in the UV image. Then, the card company server 10 collates the card information extracted from the visible light image and the object specified from the UV image with the stored contents of the contractor information DB 12a, and if stored in the contractor information DB 12a, the credit card 40 Judge that the usage permission (authentication was successful).

When the card company server 10 determines whether or not it has been authenticated (S139) and determines that it has been authenticated (S139: YES), in the contractor information DB 12a, "authentication" is performed as authentication availability information corresponding to the received device ID. "Done" is memorized (S140). Further, when the card company server 10 determines that the authentication cannot be performed (S139: NO), the card company server 10 stores "authentication not possible" as the authentication possibility information corresponding to the received device ID (S141). By the above-described processing, the card company server 10 determines whether or not the credit card 40 can be used based on the visible light image and the UV image transmitted from the card authentication device 60, and determines the determination result (authentication result) as the contractor information. Store in DB12a. The authentication result may be stored in association with the date and time of authentication.

In the present embodiment, the license / disapproval (authentication result) of each contractor's credit card 40 is registered in the contractor information DB 12a stored in the card company server 10. Therefore, the card company server 10 is used based on the authentication result stored in the contractor information DB 12a when the EC site server 20 or the credit card processing terminal 50 inquires about the permission to use the credit card 40. Whether or not it can be used can be determined. Further, when the authentication date and time are stored in the contractor information DB 12a together with the authentication result of the credit card 40, the card company server 10 can use the credit card 40 within a predetermined time after the use of the credit card 40 is authenticated. It can be configured to allow the use of the credit card 40 without performing UV image authentication. Further, in the present embodiment, since the visible light image and the UV image of the credit card 40 are captured by using the card authentication device 60, the card authentication device 60 does not interrupt the browsing of the EC site using the user terminal 30. Can be used to authenticate the credit card 40. Further, since the visible light image and the UV image taken by the card authentication device 60 are transmitted only to the card company server 10, the EC site server 20, the user terminal 30, and the credit card processing terminal 50 do not leak.

The present embodiment can be applied to the information processing system of the second to fourth embodiments, and the same effect can be obtained even when the information processing system of the second to fourth embodiments is applied. When applied to the information processing system of the second to fourth embodiments, the card of the present embodiment is used when acquiring the card information (visible light image) and the UV image of the credit card 40 and transmitting them to the card company server 10. It can be configured to use the authentication device 60. Further, when applied to the information processing system of the fourth embodiment, the card authentication device 60 is provided in the actual store, and when the credit card 40 is used in the actual store, the credit card 40 is used by using the card authentication device 60. The visible light image and the UV image of the above may be acquired and transmitted to the card company server 10 for authentication.

The embodiments disclosed this time should be considered as exemplary in all respects and not restrictive. The scope of the present invention is indicated by the scope of claims, not the above-mentioned meaning, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

10 Card company server 11 Control unit 12 Storage unit 13 Communication unit 20 EC site server 30 User terminal 31 Control unit 32 Storage unit 33 Communication unit 36 Camera 37 Visible light light 38 UV light 40 Credit card 12a Contractor information DB
22a Customer information DB
32AP authentication app 45a-45c object

Claims (10)

Get card information about your credit card,
An invisible light image taken by irradiating the invisible light to a credit card whose information can be acquired by irradiating the invisible light is acquired.
A program that causes a computer to execute a process of requesting a predetermined device for permission to use a credit card based on the card information and the invisible light image. Accepts an execution instruction for either the first shooting process for acquiring a visible light image or the second shooting process for acquiring a non-visible light image.
When the execution instruction of the first shooting process is received, the visible light image obtained by shooting the credit card is acquired.
The program according to claim 1, wherein the computer executes a process of extracting the card information from the acquired visible light image. Obtain the designation of the shooting area for the credit card and
The program according to claim 1 or 2, wherein the computer executes a process of acquiring the invisible light image obtained by photographing the designated photographing area. When an instruction to obtain a credit card use permission is obtained from a website that accepts a purchase application for a product, the above-mentioned on the website is based on the card information, the invisible light image, and the site information about the website. The program according to any one of claims 1 to 3, which causes the computer to execute a process of requesting a predetermined device for permission to use a credit card. With the shooting department
Irradiation part that irradiates invisible light and
Acquisition of a visible light image in which a credit card is photographed by the photographing unit without irradiating invisible light and an invisible light image in which the credit card is photographed by the photographing unit by irradiating invisible light. Department and
An information processing device including a transmission unit that transmits the acquired visible light image and non-visible light image to a predetermined device. A credit card-related card information, an acquisition unit that acquires an invisible light image taken by irradiating the credit card with invisible light, and an acquisition unit.
A recognition unit that recognizes an object whose information can be acquired by irradiating the credit card with invisible light from the acquired invisible light image.
An information processing device including a determination unit that determines whether or not to use the credit card based on the acquired card information and the recognized object. A storage unit that stores the card information and the information of the object corresponding to the credit card in association with each other is provided.
The determination unit collates the acquired card information and the recognized object with the card information and the object information stored in association with the storage unit, and uses the credit card based on the collation result. The information processing apparatus according to claim 6, which determines whether or not the information is permitted. When the determination unit acquires the inquiry information on whether or not the credit card can be used within a predetermined time after the determination unit determines the permission to use the credit card, the use of the credit card is permitted and the information indicating the permission to use is input to the inquiry source. The information processing apparatus according to claim 6 or 7, further comprising a permitting unit for transmitting to the apparatus. 6. Claim 6 including a transmission unit that transmits the permission information indicating the permission to use the credit card to the device that transmits the card information and the invisible light image when the determination unit determines the permission to use the credit card. The information processing device according to any one of 1 to 8. Get card information about your credit card,
An invisible light image taken by irradiating the invisible light to a credit card whose information can be acquired by irradiating the invisible light is acquired.
An information processing method in which a computer executes a process of requesting a predetermined device for permission to use a credit card based on the card information and the invisible light image.

Images