JP6917202B2 - Payment support devices, payment support methods, and payment support programs - Google Patents

Description

The present invention relates to payment support devices, payment support methods, and payment support programs.

Conventionally, in stores and the like, users pay the price using various cards such as credit cards and debit cards. As a related prior art, when a transaction using a credit card is performed, the transaction details are sent to the management center, information that can recognize the transaction details is notified to the cardholder's terminal, and the cardholder is notified. If you do not recognize it, the payment management center will be notified immediately and it is disclosed that the use of the card will be suspended (see, for example, Patent Document 1 below).

Japanese Unexamined Patent Publication No. 2006-85446

However, in the conventional technology, for example, since only one card is issued in principle, the user cannot use the card when the user is not carrying or loses the card, and the card is used. There was something inconvenient for the person. Also, if the card is lost and reissued, the card number may change, so for example, if you are making various payments via a credit card, you will need to change the card number. It was bothersome and inconvenient for the user.

An object of the present invention is to provide a payment support device, a payment support method, and a payment support program that can improve the convenience of a card in order to solve the problems caused by the above-mentioned prior art.

In order to solve the above-mentioned problems and achieve the object, the payment support device according to the present invention provides a card number common to a plurality of cards possessed by the user and identification information corresponding to each of the plurality of cards. Indicates whether or not the acquisition unit for acquiring the including card information, the card number of the card owned by each user, a plurality of different identification information corresponding to each card number, and the card indicated by each of the plurality of identification information can be used. When the availability information and the predetermined storage unit for storing the card are referred to, and the availability information corresponding to the identification information included in the card information acquired by the acquisition unit indicates the availability of the card, the identification information is supported. It is characterized by having a permission unit that permits the use of the card with the card number.

Further, in the above invention, the payment support device according to the present invention exists in the predetermined range by the receiving unit and the receiving unit that receives the card information of the card existing in the predetermined range of the detection device possessed by the user. When the card information of the card to be used is received, a storage control unit that stores the availability information indicating that the card indicated by the identification information included in the card information is available in the predetermined storage unit is further added. It is characterized by being prepared.

Further, in the payment support device according to the present invention, in the above invention, when the storage control unit receives the card information of the card existing in the predetermined range by the receiving unit, the storage control unit is said to be said until the predetermined period elapses. It is characterized in that the possibility information indicating that the card indicated by the identification information included in the card information is available is stored in the predetermined storage unit.

Further, in the payment support device according to the present invention, in the above invention, the acquisition unit acquires card information including a card number common to the plurality of cards and card identification information desired by the user. It is characterized by further including a storage control unit that stores the availability information indicating that the card indicated by the identification information included in the card information acquired by the acquisition unit is available in the predetermined storage unit.

Further, in the payment support device according to the present invention, in the above invention, the predetermined storage unit stores the history of the availability information of each of the plurality of cards, and the permission unit refers to the predetermined storage unit. It is characterized in that the use of the card is permitted based on the history of the card indicated by the identification information included in the card information acquired by the acquisition unit.

Further, in the payment support device according to the present invention, in the above invention, the predetermined storage unit stores the usage history of each of the plurality of cards, and the permission unit refers to the predetermined storage unit. It is characterized in that the use of the card is permitted based on the usage history of the card indicated by the identification information included in the card information acquired by the acquisition unit.

Further, the payment support device according to the present invention is characterized in that, in the above invention, the usage history is a usage history of whether or not the card has been used within a certain period immediately before.

Further, in the payment support device according to the present invention, in the above invention, the predetermined storage unit stores the history of the availability information of each of the plurality of cards, refers to the predetermined storage unit, and refers to the predetermined storage unit for a certain period of time or longer. When the availability information indicating that the card cannot be used is stored, a notification unit for notifying the loss confirmation of the card is further provided.

Further, the payment support method according to the present invention acquires card information including a card number common to a plurality of cards owned by a user and identification information corresponding to each of the plurality of cards, and each user obtains card information. Refer to a predetermined storage unit that stores the card number of the card to be possessed, a plurality of different identification information corresponding to each card number, and the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information. When the availability information corresponding to the identification information included in the acquired card information indicates the availability of the card, the computer executes the process of permitting the use of the card with the card number corresponding to the identification information. And.

Further, the payment support program according to the present invention acquires card information including a card number common to a plurality of cards possessed by the user and identification information corresponding to each of the plurality of cards, and each user obtains card information. Refer to a predetermined storage unit that stores the card number of the card to be possessed, a plurality of different identification information corresponding to each card number, and the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information. , When the availability information corresponding to the identification information included in the acquired card information indicates the availability of the card, the computer is allowed to execute the process of permitting the use of the card with the card number corresponding to the identification information. And.

According to the payment support device, the payment support method, and the payment support program according to the present invention, the convenience of the card can be improved.

It is explanatory drawing which shows the system configuration example of the payment support system 100 which concerns on embodiment. It is a block diagram which shows an example of the hardware composition of the card company server 111. It is explanatory drawing which shows an example of the storage contents of the credit information DB 112. It is explanatory drawing which shows an example of the storage contents of the card information DB 113. It is explanatory drawing which shows an example of the storage content of the possibility information history DB 114. It is explanatory drawing which shows an example of the storage contents of the usage history DB 115. It is explanatory drawing which shows the card information of the credit card 122. It is explanatory drawing which shows the validity of the credit card 122a, 122b, 122e. It is explanatory drawing when the credit card 122a becomes available. It is explanatory drawing when the credit card 122e becomes unusable. It is explanatory drawing which shows the functional structure of the payment support system 100. It is a flowchart which shows an example of the card search processing procedure of a user terminal 121. It is a flowchart which shows an example of the approval / disapproval information update processing procedure of the target card by a card company server 111. It is a flowchart which shows an example of the purchase request processing procedure of a store terminal 131. It is a flowchart (the 1) which shows an example of the purchase request reception processing procedure of the card company server 111. It is a flowchart (No. 2) which shows an example of the purchase request reception processing procedure of the card company server 111. It is a flowchart which shows an example of the confirmation notification processing procedure of a card company server 111.

The payment support device, the payment support method, and the embodiment of the payment support program according to the present invention will be described in detail with reference to the drawings below.

(System configuration of payment support system)
First, a system configuration example of the payment support system 100 according to the embodiment will be described. FIG. 1 is an explanatory diagram showing a system configuration example of the payment support system 100 according to the embodiment. In FIG. 1, the payment support system 100 includes a card company server 111, a user terminal 121, and a store terminal 131.

The card company server 111 is a server of the card company 110. The card company server 111 is a general-purpose computer device such as a personal computer that manages credit card information for each owner and the amount of payment made by the credit card. The card company server 111 has a CPU (Central Processing Unit), a memory, an interface, and the like. Further, the card company server 111 has a credit information DB (Database) 112, a card information DB 113, a availability information history DB 114, and a usage history DB 115. The stored contents of the various DBs 112 to 115 will be described later with reference to FIGS. 3A to 3D.

The user terminal 121 is an example of a detection device, and is a computer device used by a user 120 having a credit card 122. The user terminal 121 can perform short-range wireless communication, and can read card information from an IC (Integrated Circuit) chip built in the credit card 122 (122a to 122e). For example, the user terminal 121 has an NFC (Near Field Communication) reader that reads card information from an IC chip built in a credit card 122 located within a predetermined range (for example, within 50 cm).

For the user terminal 121, for example, a smartphone, a tablet-type PC, a wearable terminal, or the like can be used. Wearable terminals include watch type, wristband type, clip type, goggles type and the like. However, the user terminal 121 is not limited to this, and may be, for example, a mobile phone, a PHS (Personal Handyphone System), or the like. One or more of the user terminals 121 are registered in the card company server 111 for each user 120. The user terminal 121 has a CPU, a memory, an interface, and the like.

The user 120 has a plurality of credit cards 122a to 122e having the same card number. The credit cards 122a to 122e have different identification information. The credit cards 122a to 122e have a built-in IC chip that stores card information. The card information includes a card number and identification information.

The store terminal 131 is a general-purpose computer device such as a personal computer used by the staff of the store 130. The store terminal 131 has a cash register function such as payment settlement, storage, and sales management. For the store terminal 131, for example, a desktop PC (Personal Computer), a tablet PC, a notebook PC, or the like can be used.

Further, the store terminal 131 is connected to the card reader 132. The card reader 132 reads the card information of the credit card 122 when the user 120 pays with the credit card 122. The card reader 132 may be a non-contact type or a contact type. The card information read by the card reader 132 is transmitted to the card company server 111 via the store terminal 131. As a result of the inquiry of the credit card 122 on the card company server 111, if available, the user can make a payment by a credit transaction using the credit card 122.

In the payment support system 100, the card company server 111, the user terminal 121, and the store terminal 131 are connected via a wired or wireless network 140. The network 140 includes, for example, the Internet, a mobile communication network, a LAN (Local Area Network), a WAN (Wide Area Network), and the like.

The payment support program according to the present invention is installed on the card company server 111. The card company server 111 performs processing according to various requests from the user terminal 121 and the store terminal 131, and outputs the processing result to the user terminal 121 and the store terminal 131.

(Example of hardware configuration of card company server 111)
Next, an example of a specific configuration of the card company server 111 will be described. Since the card company server 111, the user terminal 121, and the store terminal 131 have the same main configurations, the card company server 111 will be described below.

FIG. 2 is a block diagram showing an example of the hardware configuration of the card company server 111. In FIG. 2, the card company server 111 includes a CPU 201, a memory 202, an output unit 203, an input unit 204, and a communication IF (Interface) 205. Further, each unit 201 to 205 included in the card company server 111 is connected by a bus 210.

The CPU 201 is in charge of overall control of the card company server 111. The CPU 201 controls the entire card company server 111 by using various programs and data stored in the memory 202. The memory 202 can be realized by a hard disk, a flash memory, or the like.

The output unit 203 includes, for example, a display, a speaker, and an audio output terminal. The display can be realized, for example, mainly by a liquid crystal display, an organic EL (Electro-Luminescence) display, or the like.

In addition, the speaker outputs voice, alarm sound, and the like. The audio output terminal is a terminal for connecting headphones or the like, and outputs audio, alarm sounds, or the like to the connected headphones or the like in the same manner as a speaker.

The input unit 204 includes keys for inputting characters, numerical values, various instructions, and the like, and inputs data. The input unit 204 can be realized by, for example, a touch panel or a keyboard. The input unit 204 realized by a touch panel, a keyboard, or the like outputs a signal corresponding to an input operation to the input unit 204 to the CPU 201. Here, in the case of the store terminal 131, the input unit 204 has a function of inputting the card information read by the card reader 132 (see FIG. 1).

When the input unit 204 is realized by a touch panel, the touch panel is laminated on the display surface side of the display. When the touch panel detects that a writing member such as a finger or a pen has come into contact with the touch panel, the touch panel outputs an electric signal according to the contact position of the writing member with respect to the touch panel. As the touch panel, various known methods such as a resistance film method, a capacitance method, an acoustic pulse recognition method, an ultrasonic surface acoustic wave method, an infrared shading method, and an image recognition method can be used.

Further, the input unit 204 may include a camera. The camera is controlled by the CPU 201 to capture an image to be imaged to generate image data, or can convert characters captured by using an OCR (Optical Character Reader) function into data and input the characters.

Further, the input unit 204 may include a microphone. The microphone converts the speaker's voice input as analog data into analog / digital and generates audio data in digital format. By using a microphone, it is possible to input characters and the like instead of using a touch panel and a keyboard.

The communication IF 205 controls the interface between the inside of the card company server 111 and an external device such as a user terminal 121 or a store terminal 131. Further, in the case of the user terminal 121, the communication IF 205 has a function of reading card information from an IC chip built in the credit card 122 by short-range wireless communication.

(Memory contents of various DBs 112 to 114)
Next, the stored contents of various DBs 112 to 114 possessed by the card company server 111 shown in FIG. 1 will be described with reference to FIGS. 3A to 3D. The various DBs 112 to 114 are realized by, for example, a storage unit such as a memory.

FIG. 3A is an explanatory diagram showing an example of the stored contents of the credit information DB 112. In FIG. 3A, the credit information DB 112 has fields for a card number, a holder, an expiration date, a security code, a limit amount, and a usage amount up to now. By setting information in each field, a record of credit information (for example, credit information 300-1, 300-2) is stored.

The card number is, for example, a 16-digit number printed on a credit card. The holder indicates the holder of the credit card. The expiration date indicates the expiration date when the credit card can be used. The security code is, for example, a three-digit number printed on the back of the credit card. The limit amount indicates the maximum amount that can be purchased using a credit card within a certain period (for example, one month). The usage amount up to now indicates the total amount of credit card usage from the start of a certain period (for example, the beginning of the month) to the present.

For example, credit information 300-1 has a card number "1234 ...", a holder "Taro Soyama", an expiration date "September 2021", a security code "634", a limit of "¥ 300,000", and up to now. The usage amount "¥ 41520" is shown. If cash financing can be used, information about cashing (limit amount and usage amount up to now) is also stored in the credit information DB 112.

In the credit information DB 112, the card number, the holder, the expiration date, the security code, and the limit amount are set according to the examination of the card company 110 and the declaration of the user when a new credit card is created. The usage amount up to now is updated each time according to the usage amount. The credit information 300 may include the address, telephone number, date of birth, etc. of the holder in addition to the card number and the like.

FIG. 3B is an explanatory diagram showing an example of the stored contents of the card information DB 113. In FIG. 3B, the card information DB 113 has fields for card number, user terminal information, identification information, registration information, last update date and time, and availability information. By setting information in each field, a record of card information (for example, card information 310-1 to 10-n) is stored.

The card number corresponds to the card number in the credit information DB 112 (see FIG. 3A). The user terminal information is information for identifying the user terminal 121. The identification information is assigned to each of a plurality of cards having the same card number, and is different information. Specifically, there are five types of identification information, for example, symbols "A" to "E", but numbers such as "1" to "5" may be used.

The registration information indicates whether or not the card is registered among the plurality of cards, and is set based on, for example, a report from the user. It may be predetermined by. When the registration information is "Yes", the possibility information described later may be set to "Valid", while when the registration information is "None", "Invalid" is always held. Cards with "none" registration information are spare cards or lost cards that are not intended to be used by users. In the initial setting, for example, the predetermined number of registration information (for example, 3) is set to "Yes", and the remaining number (for example, 2) is set to "None".

The last update date and time indicates the last update date and time that is updated according to the reception result from the user terminal 121. Specifically, as the last update date and time, the card information of the card existing within the predetermined range of the user terminal 121 was last received from the user terminal 121 of each user indicated by the user terminal information registered in advance. The date and time.

The availability information is updated according to the reception result from the user terminal 121, and takes either "valid" in which the card can be used or "invalid" in which the card cannot be used. For example, the availability information is "valid" when the card is within a predetermined range of the user terminal 121. Further, when the availability information becomes "valid" at the last update date and time, the "validity" is maintained until a predetermined period elapses. On the other hand, the approval / disapproval information becomes "invalid" if the card information of the "valid" card is not received again by the elapse of the predetermined period.

For example, the card information 310-1 indicates the card number "1234 ...", the identification information "A", the registration information "Yes", the last update date and time "May 1, 9:00", and the availability information "Valid". Further, the card information 310-4 indicates the card number "1234 ...", the identification information "D", the registration information "none", the last update date and time "-", and the availability information "invalid".

In the card information DB 113, one user terminal information (user terminal 121) is registered for one user, but a plurality of user terminals for one user. Information may be registered. In this case, for example, if a card exists within a predetermined range of at least one user terminal 121 among a plurality of user terminals 121 and the last update date and time is updated, a predetermined period is set after the update is performed. The availability information may be "valid" until the elapse.

Further, in the present embodiment, the number of a plurality of cards having a common card number can be any number. Specifically, in the card information DB 113, the identification information can be an arbitrary number according to the number of cards according to the examination of the card company 110 and the declaration of the user.

FIG. 3C is an explanatory diagram showing an example of the stored contents of the availability information history DB 114. In FIG. 3C, the pass / fail information history DB 114 has fields for card number, identification information, update date / time, and pass / fail information. By setting information in each field, a record of history information (for example, history information 320-1 to 320-n + 1) is stored.

The card number corresponds to the card number in the credit information DB 112 (see FIG. 3A) and the card information DB 113 (see FIG. 3B). The identification information corresponds to the identification information in the card information DB 113. The update date and time indicates the date and time when the update date and time are updated according to the reception result from the user terminal 121. Specifically, the update date and time is the date and time when the identification information of the card existing in the predetermined range of the user terminal 121 is received from the user terminal 121, for example, at intervals of 10 minutes.

The availability information indicates a result according to the reception result from the user terminal 121, and takes either "valid" in which the card can be used or "invalid" in which the card cannot be used.

For example, the history information 320-1 indicates the card number “1234 ...”, the identification information “A”, the update date / time “9:00 on May 1”, and the availability information “valid”. As shown in the history information 320-1 to 320-4, the card indicated by the identification information "A" indicates that the availability information is "valid" at least after 8:30 on May 1.

On the other hand, the history information 320-m indicates the card number "1234 ...", the identification information "E", the update date and time "9:00 on May 1", and the availability information "invalid". In the availability information history DB 114, after the update date and time "March 25, 13:40" indicated by the history information 320-n + 1, and after the update date and time "March 25, 13:50" indicated by the history information 320-n, It is assumed that the availability information "invalid" continues until the update date and time "9:00 on May 1" indicated by the history information 320-m.

FIG. 3D is an explanatory diagram showing an example of the stored contents of the usage history DB 115. In FIG. 3D, the usage history DB 115 has fields for card number, identification information, date and time of use, location, and amount of money. By setting information in each field, a record of usage history information (for example, usage history information 330-1 to 330-n) is stored.

The card numbers correspond to the card numbers in various DBs 112 to 114 (see FIGS. 3A to 3C). The identification information corresponds to the identification information in the card information DB 113 and the availability information history DB 114. The date and time of use indicates the date and time when payment was made using a credit card. The location indicates a store using a credit card and includes store location information. The amount indicates the amount paid by using a credit card at the store.

For example, the usage history information 330-1 indicates the card number "1234 ...", the identification information "A", the update date and time "April 30, 15:20", the place "○○ department store", and the amount "¥ 7800". ..

(About credit card information)
FIG. 4A is an explanatory diagram showing card information of the credit card 122. In FIG. 4A, the credit card 122 stores the card number and the identification information. The credit cards 122a to 122e all have the same card number, and the identification information is different from each other.

Further, the credit cards 122a to 122e may be made so that the user can recognize the identification information, and for example, they may be colored differently or have symbols or numbers that can be visually recognized by the user. Further, by registering at the time of card creation, it is possible to register the credit cards 122a to 122e to be used and use the remaining cards as spare cards.

(About the validity of credit cards)
FIG. 4B is an explanatory diagram showing the validity of the credit cards 122a, 122b, 122e. FIG. 4B shows that there are three credit cards 122a, 122b, 122e. Since the credit cards 122a and 122b exist within a predetermined range from the user terminal 121 (user 120), they can be used.

On the other hand, the credit card 122e cannot be used because it does not exist within the predetermined range of the user terminal 121 (user 120). As described above, in the present embodiment, the validity of the credit card 122 differs depending on whether or not it exists within the predetermined range of the user terminal 121. The credit cards 122c and 122d (not shown) are, for example, cards that are not planned to be used, and specifically, the card information DB 113 (see FIG. 3A) registration information is registered as "None". ..

However, although the details will be described later, in the present embodiment, the credit cards 122a to 122e can be enabled or invalidated by the manual operation of the user. The credit cards 122a to 122e validated by the manual operation of the user can be used even if they do not exist in the predetermined range of the user terminal 121.

(When credit card 122a becomes available)
FIG. 4C is an explanatory diagram when the credit card 122a can be used. As shown in FIG. 4C, at the store 130, the user 120 possesses the user terminal 121 and the credit card 122a, and the payment procedure is performed by the credit card 122a. Since the credit card 122a is within the predetermined range of the user terminal 121, the credit card 122a is set to "valid" at the card company 110 (card company server 111) and can be used.

Specifically, when the user 120 presents the credit card 122a at the store 130, the card number and identification information of the credit card 122a are transmitted from the store 130 (store terminal 131) to the card company 110 (card company server 111). Is sent.

The credit card company 110 refers to the credit information DB 112 (see FIG. 3A) and the card information DB 113 (see FIG. 3B), and since the identification information of the credit card 122a received from the store 130 is “valid”, the credit card Allow the use of 122a. The result of whether or not the use of the card is permitted is transmitted from the card company 110 to the store 130.

If the use of the card is permitted, the user 120 can use the credit card 122a, that is, the payment can be made by the credit card 122a.

(When the credit card 122e becomes unusable)
FIG. 4D is an explanatory diagram when the credit card 122e becomes unusable. As shown in FIG. 4D, it is assumed that the user 120 possesses the user terminal 121 but does not possess the credit card 122e. Since the credit card 122e is not within the predetermined range of the user terminal 121, the credit card 122e is set to "invalid" at the card company 110 (card company server 111).

Here, it is assumed that a third party 401 different from the user 120 who is the holder performs the payment procedure at the store 130 by using the credit card 122e. Specifically, when the third party 401 presents the credit card 122e in the payment at the store 130, the card number of the credit card 122e is sent from the store 130 (store terminal 131) to the card company 110 (card company server 111). And the identification information are sent.

The card company 110 refers to the credit information DB 112 (see FIG. 3A) and the card information DB 113 (see FIG. 3B), and since the identification information of the credit card 122e received from the store 130 is "invalid", the credit card Do not allow the use of 122e.

If the use of the card is not permitted, the user 120 cannot use the credit card 122e, that is, cannot make a payment with the credit card 122e. As a result, when the credit card 122e is lost, it is possible to prevent the credit card 122e from being illegally used by the third party 401.

(Functional configuration of payment support system 100)
FIG. 5 is an explanatory diagram showing a functional configuration of the payment support system 100. In FIG. 5, the payment support system 100 includes a card company server 111, a user terminal 121, and a store terminal 131. The card company server 111 includes an acquisition unit 501, a permission unit 502, a reception unit 503, a storage control unit 504, a notification unit 505, and a storage unit 510.

The acquisition unit 501, the permission unit 502, the reception unit 503, and the storage control unit 504 realize their functions by, for example, causing the CPU to execute a program stored in the memory of the card company server 111. The processing result of each functional unit is stored in a storage device such as a memory of the card company server 111, for example. Further, the storage unit 510 is realized by a storage device such as a memory of the card company server 111.

In the present embodiment, the user has a plurality of cards having a common card number. The card is, for example, a credit card, but may be a debit card. Each of the plurality of cards is assigned different identification information corresponding to each card number. In addition, whether or not each of the plurality of cards can be used is set.

Specifically, the storage unit 510 stores the card number, the identification information, and the availability information. The card number is the number of the card used by each user. The identification information is information for identifying a plurality of different types (for example, 5 types) corresponding to each card number. The identification information is information different from the card number, but can be, for example, information represented by any digit added to the card number.

The availability information is information indicating whether or not the card can be used (valid or invalid) indicated by each of the plurality of identification information. The availability information will be described in detail later, but is "valid" when it is within a predetermined range of the user terminal 121 or when there is a request from the user. In the present embodiment, the storage unit 510 is included in the card company server 111, but is not limited to this, and may be included in other devices.

The acquisition unit 501 acquires card information including the card numbers of a plurality of cards owned by the user and the identification information corresponding to each of the plurality of cards. For example, the card information is read from the card by the card reader 132 (see FIG. 1) and acquired by the receiving unit 503 receiving from the store terminal 131.

The permission unit 502 refers to the storage unit 510, and when the availability information corresponding to the identification information included in the card information acquired by the acquisition unit 501 indicates the availability of the card, the permission unit 502 of the card number corresponding to the identification information. Allow the use of the card. Specifically, when the approval / disapproval information of the card information DB 113 (see FIG. 3B) indicates "valid", the permission unit 502 permits the use of the card with the card number corresponding to the approval / disapproval information. When the use of the card is permitted by the permission unit 502, the card company server 111 makes an authority reservation to secure the payment amount according to the usage limit amount and the like.

Further, in the present embodiment, the receiving unit 503 receives the card information of the card existing in the predetermined range of the user terminal 121 possessed by the user. For example, the user terminal 121 has a function of reading short-range wireless communication such as an NFC reader, and reads card information from an IC chip built in a credit card. The predetermined range is, for example, a range of 50 cm, 1 m, 2 m.

The user terminal 121 transmits card information existing within a predetermined range of the user terminal 121 to the card company server 111 at a predetermined timing. The predetermined timing is, for example, the timing of making a payment by credit card or the timing of elapse of a predetermined period.

Specifically, the card company server 111 transmits card information existing within the predetermined range of the user terminal 121 to the user terminal 121 at a predetermined timing (timing of payment or timing of elapse of a predetermined period). Make a request. The user terminal 121 receives the transmission request and transmits the card information to the card company server 111.

As a result, the acquisition unit 501 can acquire the card information existing in the predetermined range of the user terminal 121 at a predetermined timing. Further, without making a transmission request from the card company server 111 to the user terminal 121, the user terminal 121 clocks a predetermined period, and at the timing when the predetermined period elapses, the card company presents the card information existing within the predetermined range. It is also possible to send to the server 111.

The predetermined period corresponds to the update period of the availability information, specifically, the period in which the user is recognized as having a credit card, for example, a period of several minutes, several hours, several days, etc. It is possible to set to. The predetermined period is, for example, 10 minutes. The shorter the predetermined period, the more accurately the card company server 111 can grasp whether or not the card exists near the user. On the other hand, the longer the predetermined period is, the more the card company server 111 can reduce the update frequency of the last update date and time and the availability information of the card information DB 113 (see FIG. 3B), thereby simplifying the management of each card. be able to.

When the receiving unit 503 receives the card information of the cards existing within the predetermined range, the storage control unit 504 stores the availability information indicating that the card indicated by the identification information included in the card information can be used. It is stored in the part 510.

Further, the user terminal 121 may transmit the identification information of the card that does not exist within the predetermined range of the user terminal 121 among the registered cards to the card company server 111. In this case, when the storage control unit 504 receives the identification information of the card that does not exist within the predetermined range by the receiving unit 503, the availability information (invalid) indicating that the card indicated by the identification information cannot be used. May be stored in the storage unit 510.

In the present embodiment, the storage unit 510 stores the history of the availability information of each of the plurality of cards. The history of the availability information is, for example, the history indicated by the history information 320 of the availability information history DB 114 (see FIG. 3C). The permission unit 502 refers to the storage unit 510 and permits the use of the card based on the history of the card indicated by the identification information included in the card information acquired by the acquisition unit 501. This will be described in detail.

For example, in a department store, the accounting place (the place where payment procedures are performed) and the delivery place of goods may be different. In such a case, when the staff of the department store performs the procedure by credit card at the checkout place, the credit card does not exist within the predetermined range of the user terminal 121, and the availability information indicates that it cannot be used (invalid). Is expected to be.

Therefore, when the credit card does not exist within the predetermined range of the user terminal 121 in the payment procedure at a specific payment place such as a department store, the permission unit 502 refers to the history of approval / disapproval information, for example. If the credit card is within the predetermined range of the user terminal 121 by immediately before the payment procedure (for example, 10 minutes before), the use of the credit card is permitted.

Specifically, the permission unit 502 uses the card even when the availability information indicates that it is not available at a specific payment place, but when the availability information immediately before the payment procedure is performed indicates that it is available. to approve. As a result, even if the accounting place and the delivery place of the product are different and the credit card does not exist within the predetermined range of the user terminal 121 at the timing of the payment procedure, the use of the credit card can be permitted.

In the present embodiment, prior to the permission of use by the permission unit 502, the notification unit 505 notifies the store terminal 131 of an alarm when the availability information indicates that it is not available at a specific payment place. .. The alarm notification timing by the notification unit 505 is, for example, the timing before the authority reservation is made. As a result, the sales staff and the card company 110 can directly contact each other to confirm the identity of the user.

Then, if there is no problem as a result of the identity verification, the permission unit 502 also permits the use of the card indicating that the availability information cannot be used at the specific payment place. Therefore, it is possible to confirm whether or not the card is illegally used before making an authority reservation, and it is possible to prevent the illegal use of the credit card.

As described above, in the present embodiment, the permission unit 502 refers to the storage unit 510 and uses the card based on the card history indicated by the identification information included in the card information acquired by the acquisition unit 501. to approve.

Further, in the present embodiment, when the storage control unit 504 receives the identification information of the card existing in the predetermined range by the receiving unit 503, the card corresponding to the identification information is used until the predetermined period elapses. The storage unit 510 stores the availability information indicating that it is possible. The predetermined period referred to here is the same period (10 minutes) as the above-mentioned predetermined period (period in which the availability information is updated), but may be longer than that. When the identification information of the card existing in the predetermined range is received again by the receiving unit 503 before the predetermined period elapses, the storage control unit 504 can use the card corresponding to the identification information. Update the availability information (valid) indicating that.

On the other hand, if the receiving unit 503 does not receive the identification information of the cards existing within the predetermined range before the predetermined period elapses, the storage control unit 504 cannot use the card corresponding to the identification information. The storage unit 510 stores the availability information (invalidity) indicating that the information exists. Further, the determination as to whether or not the predetermined period has passed is made at a uniform timing for each card, such as at regular time intervals, but may be determined according to the timing at which the approval / disapproval information is enabled for each card, for example. You may do it with.

Here, in the present embodiment, the availability information can be set to "valid" or "invalid" according to the request from the user, and this point will be specifically described. The acquisition unit 501 acquires card information including a card number common to a plurality of cards and card identification information desired by the user. The card desired by the user is a card that the user plans to use among a plurality of cards, and is a card that the user manually selects.

The card information may be received from the user terminal 121 by being input to the user terminal 121 by the user, or may be received from another terminal different from the user terminal 121 that can be input by the user. It may be input directly to the card company server 111 by the operator of the card company 110.

The storage control unit 504 stores in the storage unit 510 the availability information indicating that the card indicated by the identification information included in the card information acquired by the acquisition unit 501 is available. As described above, in the present embodiment, the availability information can be set to "valid" or "invalid" according to the request from the user.

Further, when the approval / disapproval information of the predetermined card is set to "valid" in response to the request from the user, the permission unit 502 determines whether or not the card exists within the predetermined range of the user terminal 121. Allows the use of cards. As a result, the user can use the card regardless of whether or not the card is near the user terminal 121.

In addition, when the availability information of a predetermined card is set to "valid" in response to a request from the user, it is always set to "valid", or the card is within the predetermined range of the user terminal 121 when paying with the card. If it does not exist, the user may be able to select whether to make it "invalid".

Further, the notification unit 505 does not have the card in the predetermined range of the user terminal 121 for a predetermined period (for example, for several days) even when the availability information is "valid" in response to the request from the user. In that case, a confirmation notice indicating that the user terminal may have been lost may be given to the user terminal 121. As a result, it is possible to prompt confirmation of the loss of the card that has been "valid" by the user's manual operation, prevent the card from being lost, and suppress unauthorized use of the card.

Further, the storage control unit 504 can change the registration information of the card information DB 113 (see FIG. 3B). As for the registration information, "None" is registered for the card that is not planned to be used, and specifically, the approval / disapproval information is always "invalid" for the card. On the other hand, "Yes" is registered for the card to be used, and the possibility information is set to "Valid" for the card when it exists within the predetermined range of the user terminal 121.

Specifically, if the user loses one of the multiple cards or does not plan to use it for a while, the registration information corresponding to the identification information of the card should be set to "None". Is possible. A card whose registration information indicates "none" may not be detected by the user terminal 121, or even if the card information exists within a predetermined range of the user terminal 121 and the card information is received, it is acquired. It suffices that the unit 501 does not make the approval / disapproval information "valid".

Further, for example, when a lost card is found or when the card is planned to be used, the card can be used again by setting the registration information to "Yes". The registration information may be changed manually by the user or by the operator of the card company 110.

Further, in the present embodiment, the storage unit 510 stores the usage history of each of the plurality of cards. The usage history is, for example, the history indicated by the usage history information 330 of the usage history DB 115 (see FIG. 3D). The permission unit 502 refers to the storage unit 510 and permits the use of the card based on the card usage history indicated by the identification information included in the card information acquired by the acquisition unit 501. This will be described in detail.

For example, the usage history is a usage history of whether or not the card was used within a certain period immediately before. For example, when the card to be used is a card used within a certain period immediately before (when the identification information is the same), the permission unit 502 permits the use of the card. The fixed period referred to here is an arbitrary period such as several hours or several days, and can be arbitrarily set.

On the other hand, the permission unit 502 does not permit the use of the card when the identification information is different from the card used within a certain period immediately before. As a result, for example, if the card used for the purchase procedure has different identification information from the card used one hour ago, the card used for the purchase procedure may be illegally used. It can be impossible.

In addition to the fact that the card used is a card used within a certain period immediately before, the permission unit 502 considers the location information of the store used within a certain period immediately before the card. You may allow the use of. Specifically, the permission unit 502 is located around a store (predetermined area) where the card used is a card used within a certain period immediately before and the store making payment is used within a certain period immediately before. ), The use of the card is permitted.

On the other hand, the permission unit 502 does not permit the use when the store where the payment is made is not in the predetermined area. As a result, for example, if the card used for the purchase procedure has different identification information from the card used at a distance one hour ago, the card used for the purchase procedure may be misused. It can be disabled.

Further, in this case, the notification unit 505 notifies the store terminal 131 of the alarm. As a result, the store staff or the operator of the card company 110 can confirm whether or not the card has been lost (confirmation of whether or not the card has been used illegally). As a result of the identity verification, if there is no problem, the receiving unit 503 permits the use even if the card used is not the card used immediately before.

Further, the permission unit 502 may permit the use of cards having different identification information and whose frequency of use is equal to or higher than a predetermined value in a certain period. On the other hand, the permission unit 502 may not permit the use of a card whose frequency of use is less than a predetermined value. Further, in this case, the notification unit 505 may notify the store terminal 131 of the alarm. As a result, the store staff or the operator of the card company 110 can confirm whether or not the card has been lost (confirmation of whether or not the card has been used illegally). If there is no problem as a result of the identity verification, the permission unit 502 may permit the use of the card whose usage frequency is less than the predetermined value.

As described above, in the present embodiment, the permission unit 502 refers to the storage unit 510 and uses the card based on the card usage history indicated by the identification information included in the card information acquired by the acquisition unit 501. Allow.

Further, for example, it is possible to register the card used by the user for each day of the week. Specifically, the card company server 111 may register the card for each day of the week used by the user in advance. good. In this case, when the day of the week when the user actually uses the card is not the day of the week corresponding to the card, the store terminal 131 may be notified of the alarm. As a result, the store staff or the operator of the card company 110 can confirm whether or not the card is lost.

Further, for example, it is possible to register a card used by the user for each area. Specifically, the card company server 111 may register a card for each area used by the user in advance. good. In this case, when the area when the user actually uses the card is not the area corresponding to the card, the store terminal 131 may be notified of the alarm. As a result, the store staff or the operator of the card company 110 can confirm whether or not the card is lost.

Further, in the present embodiment, the notification unit 505 sends a notification prompting the user terminal 121 to confirm the loss of the card when the availability information indicating that the card cannot be used is stored for a certain period of time or longer. To do. The fixed period referred to here is, for example, a period in which there is a risk of loss, and can be arbitrarily set such as one month and one year. The notification prompting the user to confirm the loss is a confirmation notification that may have been lost and prompts the user to confirm. As a result, when the card is lost, the lost card can be identified at an early stage, and unauthorized use of the card can be suppressed.

Further, in the present embodiment, the design of the face of the plurality of cards may be the same or different from each other. If the face design of multiple cards is the same, the user can select the card without wondering which card to bring. On the other hand, if the design of the face of the plurality of cards is different, the user can select the card (design) to carry according to the usage scene. In the present embodiment, the card selected by the user can be valid regardless of whether the design of the face of the card is the same or different.

(Card search processing procedure of user terminal 121)
FIG. 6 is a flowchart showing an example of the card search processing procedure of the user terminal 121. In the flowchart of FIG. 6, the user terminal 121 determines whether or not the timing is predetermined (step S601). The predetermined timing is, for example, the timing of making an authority reservation in the purchase procedure or the timing of each time a predetermined period (for example, 10 minutes) elapses.

Specifically, the timing of making an authority reservation is such that a request for an authority reservation is made from the store terminal 131 to the card company server 111 (see step S802 in FIG. 8), and the card company server 111 sends the user terminal 121 to the user terminal 121. This is the timing at which the transmission request for the card information of the cards existing within the predetermined range is made.

The user terminal 121 waits until a predetermined timing is reached (step S601: No). Then, when the predetermined timing is reached (step S601: Yes), the user terminal 121 determines whether or not there is a credit card within the predetermined range (step S602). The determination of whether or not the credit card is within the predetermined range is specifically determined as to whether or not the card information of the IC chip built in the credit card can be read within the predetermined range by using short-range wireless communication. Is. When the user terminal 121 does not have a credit card within the predetermined range (step S602: No), the user terminal 121 ends a series of processes according to this flowchart.

On the other hand, when the credit card is within the predetermined range (step S602: Yes), the user terminal 121 transmits the card information including the credit card identification information read by the short-range wireless communication to the card company server 111. (Step S603), a series of processes according to this flowchart is completed.

(Procedure for updating the availability information of the target card by the card company server 111)
FIG. 7 is a flowchart showing an example of the procedure for updating the availability information of the target card by the card company server 111. In the flowchart of FIG. 7, the card company server 111 sets the availability information (see the card information DB 113 of FIG. 3B) of the target card (hereinafter referred to as “target card”) to “valid” by the user (manual operation). It is determined whether or not it has been performed (step S701). The card company server 111 proceeds to step S706 when the availability information of the target card is set to "valid" by the user (step S701: Yes).

When the card company server 111 does not set the availability information of the target card to "valid" by the user (step S701: No), the card company server 111 receives the card information of the target card existing within the predetermined range of the user terminal 121. Whether or not it is determined (step S702). When the card company server 111 does not receive the card information of the target card existing within the predetermined range of the user terminal 121 (step S702: No), the process proceeds to step S704.

When the card company server 111 receives the card information of the target card existing within the predetermined range of the user terminal 121 (step S702: Yes), the card information DB 113 (see FIG. 3B) and the availability information history DB 114 (see FIG. 3C). ) Is set to "valid" (step S703).

If the pass / fail information is already set to "valid" in the card information DB 113, the card company server 111 holds (updates) "valid". Then, the card company server 111 determines whether or not a predetermined period (for example, 10 minutes) has elapsed (step S704). The predetermined period is an interval (for example, 10 minutes) for receiving the card information of the cards existing within the predetermined range from the user terminal 121, but it may be a longer period.

Then, the card company server 111 proceeds to step S706 when a predetermined period has not elapsed since the possibility information was set to "valid" (step S704: No). On the other hand, when the predetermined period has elapsed since the card company server 111 sets the pass / fail information to "valid" (step S704: Yes), the card company server 111 sets the pass / fail information corresponding to the identification information of the target card to "invalid". (Step S705).

After that, the card company server 111 determines whether or not the change to set the registration information of the target card (see the card information DB 113 in FIG. 3B) to “none” has been accepted (step S706). The change to "None" of the registration information may be accepted by the user's operation from the user terminal 121, for example, when the user loses the credit card, or the user may be the operator of the card company 110. It may be declared and accepted by the operation of the operator.

When the card company server 111 does not accept the change to set the registration information of the target card to "None" (step S706: No), the process returns to step S701. On the other hand, when the card company server 111 accepts the change to set the registration information to "None" (step S706: Yes), the card company server 111 changes the registration information of the card information DB 113 (see FIG. 3B) to "None" (step S707). ), Ends a series of processes according to this flowchart.

(Purchase request processing procedure of store terminal 131)
FIG. 8 is a flowchart showing an example of the purchase request processing procedure of the store terminal 131. In the flowchart of FIG. 8, the store terminal 131 determines whether or not the purchase request by the credit card has been accepted (step S801). Accepting a purchase request by a credit card means, for example, that the card information of the credit card presented by the user is read by the card reader 132, and a predetermined operation of paying the payment amount is performed.

The store terminal 131 waits until it receives a purchase request by credit card (step S801: No). When the store terminal 131 receives the purchase request by the credit card (step S801: Yes), the store terminal 131 requests the card company server 111 to make an authorization reservation (step S802), and ends the series of processes according to this flowchart. In the request for authorization reservation, card information including credit card identification information is transmitted from the store terminal 131 to the card company server 111.

(Procedure for receiving purchase request of card company server 111)
FIG. 9A is a flowchart (No. 1) showing an example of the purchase request reception processing procedure of the card company server 111. FIG. 9B is a flowchart (No. 2) showing an example of the purchase request reception processing procedure of the card company server 111.

In the flowcharts of FIGS. 9A and 9B, the card company server 111 determines whether or not the request for authorization reservation has been received from the store terminal 131 (step S901). The card company server 111 waits until it receives the request for authorization reservation from the store terminal 131 (step S901: No).

When the card company server 111 receives the request for authorization reservation from the store terminal 131 (step S901: Yes), the card company server 111 refers to the credit information DB 112 (see FIG. 3A) and determines whether or not the card number can be used. (Step S902). If the card company server 111 does not have a usable card number (step S902: No), it notifies the store terminal 131 that the credit card cannot be used (step S903), and ends a series of processes according to this flowchart.

When the card company server 111 has a usable card number (step S902: Yes), the card company server 111 refers to the card information DB 113 (see FIG. 3B) and determines whether or not the availability information is set to "valid" (see FIG. 3B). Step S904). When the pass / fail information is set to "valid" (step S904: Yes), the card company server 111 proceeds to step S908.

On the other hand, the card company server 111 has a pass / fail information history DB 114 (FIG. 3C) when the pass / fail information is not set to "valid" (step S904: No), that is, when the pass / fail information is set to "invalid". Refer to), and determine whether or not the immediately preceding availability information was “valid” (step S905).

When the immediately preceding availability information is "valid" (step S905: Yes), the card company server 111 proceeds to step S908. The card company server 111 has a card at the time of payment procedure when the immediately preceding availability information is not "valid" (step S905: No), that is, because the accounting place and the delivery place of the product are different, such as in a department store. Does not exist within the predetermined range of the user terminal 121, and when the availability information becomes "invalid", for example, the possibility of unauthorized use by a third party cannot be denied, so an alarm is notified to the store terminal 131. (Step S906).

When this alarm is notified to the store terminal 131, the sales staff and the card company 110 can directly contact each other to confirm the identity of the user and prevent unauthorized use of the credit card. can.

Then, the card company server 111 determines whether or not the store terminal 131 has received the fact that the identity verification has been obtained within a predetermined period after the alarm is notified (step S907). If the card company server 111 does not receive the fact that the identity verification has been obtained from the store terminal 131 within the predetermined period (step S907: No), the process proceeds to step S903.

When the card company server 111 receives the fact that the identity verification has been obtained from the store terminal 131 within the predetermined period (step S907: Yes), the card company server 111 refers to the usage history DB 115 (see FIG. 3D), and immediately before in the predetermined area. It is determined whether or not the card has been used within a certain period of time (step S908). When the card company server 111 is a card used within a predetermined area within a certain period immediately before (step S908: Yes), the card company server 111 proceeds to step S912.

When the card company server 111 is not a card used within a predetermined area within a certain period immediately before (step S908: No), for example, the possibility of unauthorized use by a third party cannot be denied, so that the store terminal 131 Notifies the alarm (step S909). When this alarm is notified to the store terminal 131, the sales staff and the card company 110 can directly contact each other to confirm the identity of the user and prevent unauthorized use of the credit card. can.

Then, the card company server 111 determines whether or not the store terminal 131 has received the fact that the identity verification has been obtained within a predetermined period after the alarm is notified (step S910). If the card company server 111 does not receive the fact that the identity verification has been obtained from the store terminal 131 within the predetermined period (step S910: No), the process proceeds to step S903.

When the card company server 111 receives the fact that the identity verification has been obtained from the store terminal 131 within the predetermined period (step S910: Yes), the card company server 111 determines whether or not the authorization reservation is possible (step S911). If the card company server 111 cannot make an authorization reservation (step S9111: No), the card company server 111 proceeds to step S903. When the card company server 111 can make an authority reservation (step S911: Yes), the card company server 111 makes an authority reservation (step S912). Then, the card company server 111 notifies the store terminal 131 of the completion of the authorization reservation (step S913), and ends a series of processes according to this flowchart.

(Confirmation notification processing procedure of card company server 111)
FIG. 10 is a flowchart showing an example of the confirmation notification processing procedure of the card company server 111. In the flowchart of FIG. 10, the card company server 111 refers to the availability information history DB 114 (see FIG. 3C) and determines whether or not there is a card whose approval / disapproval information is “invalid” for a certain period of time (step S1001).

The card company server 111 waits until there is a card whose approval / disapproval information is "invalid" for a certain period of time (step S1001: No). When the card company server 111 has a card whose pass / fail information is "invalid" for a certain period of time (step S1001: Yes), the card company server 111 extracts the user terminal information corresponding to the card number of the card from the card information DB 113 (see FIG. 3B). (Step S1002).

Then, the card company server 111 notifies the user terminal 121 indicated by the extracted user terminal information to confirm the loss (step S1003), and ends a series of processes according to this flowchart.

As described above, the card company server 111 according to the present embodiment assigns a plurality of identification information corresponding to a common card number, and uses the card when the card indicated by each identification information is valid. Was decided to be permitted. As a result, since the card company server 111 uses the card number of the card used conventionally as it is, it is possible to manage a plurality of different cards having the same card number while using the inquiry system using the conventional card number as it is. Can be done. As a result, the user can use a plurality of valid cards having a common card number.

Therefore, the user can store each card in a different place, for example, a wallet, a regular case, a bag, a drawer at home, a drawer at a company, or in a car. This allows the user to use another card without having to carry one particular card, for example, if the wallet is forgotten at home or lost, another location. You can use other cards stored in your wallet.

Also, for example, if the user decides to carry different wallets for business (weekdays) and non-business (holidays), put one card in each wallet. Therefore, each card can be used even if the wallet carried on weekdays and holidays is different. Therefore, according to the present embodiment, it is possible to eliminate the trouble of reinserting the card every time the wallet to be carried is changed as in the conventional case. In addition, the storage location of the card is not limited to the wallet, and can be any location such as a pocket of clothes, a bag, or a car. Therefore, the user can use the card in the predetermined storage location according to the situation and situation of use.

Further, according to the present embodiment, even if one of the cards is lost, the user does not have to reissue a new card because there are a plurality of valid cards, so that the card number is changed. You don't have to. As a result, even if the user makes various payments using the lost card, he / she can continue to make various payments without performing complicated procedures such as changing the card number. Therefore, according to the present embodiment, the convenience of the card can be improved.

Further, the card company server 111 according to the present embodiment is determined to validate a card existing within a predetermined range of the user terminal 121. As a result, the card company server 111 can validate the card that is found to be near the user, and can invalidate the card that is found not to be near the user.

Therefore, the user can use a card that exists near himself / herself among a plurality of cards. In addition, since the card company server 111 can invalidate a card that does not exist near the user, even if the user loses one of the cards, an unauthorized use of the card by a third party can be performed. Can be prevented.

Further, when the card company server 111 according to the present embodiment receives the card information of the card existing within the predetermined range of the user terminal 121, the card indicated by the identification information is valid until the predetermined period elapses. It was decided to. As a result, the card company server 111 can invalidate the card for which the card information is not received until the predetermined period elapses. Therefore, the card company server 111 can prevent a third party from illegally using a card for which card information is not received until a predetermined period elapses.

Further, the card company server 111 according to the present embodiment can enable or invalidate each card in response to a request (manual operation) from the user. As a result, the user can use the card regardless of whether or not the card is near the user terminal 121. As a result, when there is no plan to carry the user terminal 121 or when various wireless functions of the user terminal 121 cannot be used due to a failure or the like, the user activates the card by manual input and uses the card. can do.

Further, the card company server 111 according to the present embodiment permits the use of the card based on the history of the availability information. As a result, even if the card does not exist within the predetermined range of the user terminal 121 in the payment procedure at a specific payment place such as a department store, the user terminal 121 can be reached by immediately before the payment procedure (for example, 10 minutes before). If it exists within the predetermined range, the card can be used.

Further, the card company server 111 according to the present embodiment permits the use of the card based on the usage history of each card having different identification information. As a result, for example, it is possible to make it impossible to use a card that is rarely used, assuming that there is a risk of unauthorized use due to loss because the use itself is rare. This makes it possible to prevent unauthorized use of the card.

Further, the card company server 111 according to the present embodiment permits the use of the card based on the usage history of whether or not the card was used within a certain period immediately before. As a result, for example, it is rare that the identification information of the card used for the purchase procedure and the card used one hour ago are different, so that the card used for the purchase procedure may be misused. Therefore, it is possible to make the card unusable and prevent unauthorized use.

In addition, the card company server 111 according to the present embodiment decides to give a notification prompting the confirmation of loss of the card for the card that has been invalid for a certain period of time or longer. This makes it possible for the user to confirm whether or not the product has been lost. Therefore, when the card is lost, the lost card can be identified at an early stage and the unauthorized use of the card can be suppressed.

The payment support method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. Payment support programs include hard disks, flexible disks, CD (Compact Disk) -ROM (Read Only Memory), MO (Magnet-Optical disk), DVD (Digital Versailles Disk), USB (Universal Personal Computer Bus), etc. It is stored on a possible storage medium and executed by being read from the storage medium by a computer. In addition, the payment support program may be distributed via a network such as the Internet.

As described above, the payment support device, the payment support method, and the payment support program according to the present invention are useful for the payment support device, the payment support method, and the payment support program for making payments, and are particularly possessed by the user. Suitable for payment support devices, payment support methods, and payment support programs that make payments with a card.

100 Payment support system 111 Card company server 112 Credit information DB
113 Card information DB
114 Yes / No Information History DB
115 Usage history DB
121 User terminal 122 Credit card 131 Store terminal 132 Card reader 201 CPU
202 Memory 203 Output section 204 Input section 205 Communication IF
210 Bus 501 Acquisition unit 502 Permit unit 503 Reception unit 504 Storage control unit 505 Notification unit 510 Storage unit

Claims (11)

An acquisition unit that acquires card information including a card number common to a plurality of cards owned by a user and identification information corresponding to each of the plurality of cards.
The card number of the card possessed by each user, a plurality of different identification information corresponding to each card number, the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information, and each of the plurality of cards. When the availability information corresponding to the identification information included in the card information acquired by the acquisition unit indicates the availability of the card by referring to the history of the availability information and the predetermined storage unit for storing the identification information. The permission department that permits the use of cards with the card number corresponding to
Equipped with a,
The permission unit refers to the predetermined storage unit and permits the use of the card based on the history of the card indicated by the identification information included in the card information acquired by the acquisition unit.
A payment support device characterized by that. An acquisition unit that acquires card information including a card number common to a plurality of cards owned by a user and identification information corresponding to each of the plurality of cards.
The card number of the card possessed by each user, a plurality of different identification information corresponding to each card number, the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information, and each of the plurality of cards. When the availability information corresponding to the identification information included in the card information acquired by the acquisition unit indicates the availability of the card by referring to the history of the availability information and the predetermined storage unit for storing the identification information. The permission department that permits the use of cards with the card number corresponding to
When the possibility information indicating that the card cannot be used is stored for a certain period of time or more by referring to the predetermined storage unit, the notification unit that gives a notification prompting the loss confirmation of the card, and the notification unit.
A payment support device characterized by being equipped with. A receiver that receives card information of cards existing within a predetermined range of the detection device possessed by the user, and a receiver.
When the card information of a card existing within the predetermined range is received by the receiving unit, the predetermined storage unit stores information on whether or not the card indicated by the identification information included in the card information can be used. A memory control unit that stores information in
The payment support device according to claim 1 or 2, further comprising. When the receiving unit receives the card information of a card existing within the predetermined range, the storage control unit can use the card indicated by the identification information included in the card information until a predetermined period elapses. The payment support device according to claim 3 , wherein the availability information indicating that the information is stored in the predetermined storage unit. The acquisition unit acquires card information including a card number common to the plurality of cards and card identification information desired by the user.
A claim including a storage control unit that stores in the predetermined storage unit the availability information indicating that the card indicated by the identification information included in the card information acquired by the acquisition unit is available. The payment support device according to any one of Items 1 to 4. The predetermined storage unit stores the usage history of each of the plurality of cards, and stores the usage history of each of the plurality of cards.
The permission unit refers to the predetermined storage unit and permits the use of the card based on the usage history of the card indicated by the identification information included in the card information acquired by the acquisition unit.
The payment support device according to any one of claims 1 to 5, wherein the payment support device is characterized. The payment support device according to claim 6, wherein the usage history is a usage history of whether or not the card was used within a certain period immediately before. Acquires card information including a card number common to a plurality of cards owned by a user and identification information corresponding to each of the plurality of cards.
The card number of the card possessed by each user, a plurality of different identification information corresponding to each card number, the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information, and each of the plurality of cards. When the availability information corresponding to the identification information included in the acquired card information indicates the availability of the card by referring to the history of the availability information and the predetermined storage unit for storing the identification information, the card number corresponding to the identification information. Allow the use of the card,
The computer executes the process ,
The process of permitting the use of the card is characterized in that the use of the card is permitted based on the history of the card indicated by the identification information included in the acquired card information by referring to the predetermined storage unit. Payment support method. Acquires card information including a card number common to a plurality of cards owned by a user and identification information corresponding to each of the plurality of cards.
The card number of the card possessed by each user, a plurality of different identification information corresponding to each card number, the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information, and each of the plurality of cards. When the availability information corresponding to the identification information included in the acquired card information indicates the availability of the card by referring to the history of the availability information and the predetermined storage unit for storing the identification information, the card corresponding to the identification information is used. allow the use of the number of the card,
When the possibility information indicating that the card cannot be used is stored for a certain period of time or more by referring to the predetermined storage unit, a notification prompting the loss confirmation of the card is given.
A payment assistance method characterized by a computer performing processing. Acquires card information including a card number common to a plurality of cards owned by a user and identification information corresponding to each of the plurality of cards.
The card number of the card possessed by each user, a plurality of different identification information corresponding to each card number, the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information, and each of the plurality of cards. When the availability information corresponding to the identification information included in the acquired card information indicates the availability of the card by referring to the history of the availability information and the predetermined storage unit for storing the identification information, the card number corresponding to the identification information. Allow the use of the card,
Let the computer perform the process
Process to allow use of the card, the reference to the predetermined storage unit, based on the history of the card shown the identification information included in the acquired card information, and characterized that you permitted the use of the card Payment support program. Acquires card information including a card number common to a plurality of cards owned by a user and identification information corresponding to each of the plurality of cards.
The card number of the card possessed by each user, a plurality of different identification information corresponding to each card number, the availability information indicating whether or not the card can be used indicated by each of the plurality of identification information, and each of the plurality of cards. When the availability information corresponding to the identification information included in the acquired card information indicates the availability of the card by referring to the history of the availability information and the predetermined storage unit for storing the identification information, the card corresponding to the identification information is used. allow the use of the number of the card,
When the possibility information indicating that the card cannot be used is stored for a certain period of time or more by referring to the predetermined storage unit, a notification prompting the loss confirmation of the card is given.
A payment support program characterized by having a computer perform processing.

Images