JP7116655B2 - System and program - Google Patents

Description

The present invention relates to systems and programs.

A system is known in which a card security center is provided on a website on the Internet, and the name, date of birth, and telephone number of the cardholder are notified to the card security center and notified to all card issuing companies. (See Patent Document 1, for example).
[Prior art documents]
[Patent Literature]
[Patent Document 1] JP-A-2006-216001

It is desired to be able to effectively suppress unauthorized use of cards.

In a first aspect of the invention, a system is provided. The above system includes, for example, a usage information receiving unit that receives card usage information including identification information of a card used for financial transactions and first code information. In the above system, for example, the first code information included in the card usage information received by the usage information receiving unit is the code information displayed on the card and is managed in association with the identification information. and a use suspension unit for suspending the use of the card when the code information matches the code information of the card.

In the above system, the first code information is code information different from the second code information and predetermined third code information for preventing unauthorized use of the card identified by the identification information. A judgment unit may be provided for judging that the card identified by the identification information is valid when they match.

In the above system, the third code information may be the security code of the card identified by the identification information.

In the above system, the third code information may contain multiple characters included in the second code information. In the above system, the order of the characters representing the third code information may be different from the order of the characters representing the second code information.

The above system receives restriction request information from a card holder terminal, which includes identification information of a card used for financial transactions and fourth code information for restricting the use of the card. You may have a part. In the above system, when the fourth code information matches the second code information managed in association with the identification information included in the card usage restriction request information, the identification information included in the card usage restriction request information. A usage restriction unit that restricts usage of the card identified by the information may be provided.

In the above system, when the fourth code information matches the second code information managed in association with the identification information included in the card usage restriction request information, the identification information included in the card usage restriction request information. A restriction release information transmission section may be provided for transmitting restriction release information for releasing restriction on use of the card identified by the information to the cardholder terminal.

The above system may include a restriction release information receiving unit that receives restriction release information for releasing restriction on use of the card from the cardholder terminal. In the above system, when the restriction release information received by the restriction release information receiving unit matches the restriction release information sent by the restriction release information transmission unit to the cardholder terminal, the identification information included in the card use restriction request information may be provided with a usage restriction release unit that releases usage restriction on the card identified by .

In the above system, when the use of the card identified by the identification information included in the card use restriction request information is restricted by the use restriction unit, the first code information included in the card use information is used to limit the use of the card. A report unit may be provided that reports to a predetermined report destination when the information matches the second code information managed in association with the identification information included in the information.

In a second aspect of the invention, a system is provided. The system includes a restriction request information receiving unit that receives card usage restriction request information including, for example, identification information of a card used for financial transactions and code information for restricting card usage. In the system, for example, the code information included in the card usage restriction request information received by the restriction request information receiving unit is code information displayed on the card and managed in association with the identification information. and a usage restriction unit that restricts the use of the card when For example, when the code information included in the card usage restriction request information matches the code information managed in association with the identification information, the above system provides restriction release information for releasing the usage restriction of the card. It has a restriction release information transmission unit that transmits it to the card holder terminal.

In a third aspect of the invention, a program is provided. The above program may be a program for causing a computer to function as the above system. The above program may be a program for causing a computer to execute information processing in the above system. A computer readable medium storing the above program may be provided. The computer-readable medium may be non-transitory computer-readable medium. The computer-readable medium may be a computer-readable recording medium.

It should be noted that the above summary of the invention does not list all the necessary features of the invention. Subcombinations of these feature groups can also be inventions.

1 schematically shows an example of the configuration of system 10 in one embodiment. It is an example of information displayed on the surface of the credit card 100. FIG. 3 is a block diagram showing the functional configuration of a management server 40; FIG. An example of information stored in the storage unit 44 is shown in a table format. An example of the registration screen 500 of the credit card 100 subject to usage restrictions is shown. An example of a screen when the usage restriction management application is started is shown. An example of a restriction release code display screen 700 displayed when the cardholder terminal 180 receives the restriction release code is shown. 8 shows an example of a restriction release screen 800 for releasing restrictions on the use of the credit card 100. FIG. 4 is a flow chart showing processing when the management server 40 receives a credit card usage restriction request. 4 is a flow chart showing processing when a management server 40 receives card usage information from a store server 50. FIG.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. Also, not all combinations of features described in the embodiments are essential for the solution of the invention. In addition, in the drawings, the same or similar parts may be denoted by the same reference numerals to omit redundant description.

FIG. 1 schematically shows an example configuration of a system 10 in one embodiment. In this embodiment, system 10 manages the use of credit card 100 . The system 10 comprises a management server 40 , a store server 50 and a cardholder terminal 180 . The management server 40 is a server operated by the issuing company of the credit card 100 .

In this embodiment, cardholder 80 is the owner of credit card 100 . Cardholder terminal 180 is a terminal used by cardholder 80 . Cardholder terminal 180 is an information device such as a smart phone or a personal computer.

In this embodiment, the unauthorized user 90 is a person who attempts to use the credit card 100 illegally. Unauthorized user 90 is a person other than cardholder 80 . An unauthorized user 90 is, for example, a person who finds the credit card 100 lost by the cardholder 80 and tries to use the credit card 100 fraudulently. The unauthorized user terminal 190 is information equipment used by the unauthorized user 90 .

Store server 50 , management server 40 , cardholder terminal 180 , and unauthorized user terminal 190 are connected via network 12 . Network 12 may be any network. For example, the network 12 includes at least one of the Internet, mobile phone networks such as the so-called 3G (3rd Generation), LTE (Long Term Evolution), 4G (4th Generation) and 5G (5th Generation), public communication networks, and private networks. may include

The store server 50 is a server operated by a store that accepts payment by credit card. Store server 50 provides electronic commerce functions over network 12 . The functions of the store server 50 may be operated by, for example, an online shopping operating company. The shop server 50 provides consumers including the cardholder 80 and the unauthorized user 90 with a window for browsing, purchasing and paying for products.

When the card holder terminal 180 uses the shop server 50 to purchase a product by credit card payment, the shop server 50 provides input fields for the credit card number, expiration date, and security code of the credit card used for payment. is displayed on the card holder terminal 180. A sales authorization message based on the information input from the card holder terminal 180 is sent to the management server 40 directly through the store server 50 or through an intermediate device such as a settlement agency or CAFIS.

The management server 40 performs authorization processing to determine whether or not to approve the transaction based on the credit card number, expiration date, security code, sales amount, etc. included in the received authorization message. When the management server 40 approves the transaction by the authorization process, the management server 40 transmits an authorization OK message to the store server 50 .

FIG. 2 is an example of information displayed on the surface of the credit card 100. As shown in FIG. As shown in FIG. 2A, on the surface 101 of the credit card 100, a card number 110 and an expiration date 120 are displayed. For example, the card number 110 and expiration date 120 are displayed on the surface 101 of the credit card 100 by stamping or printing.

As shown in FIG. 2B, the back surface 102 of the credit card 100 is provided with a signature frame 210 and a magnetic stripe 290. As shown in FIG. A code is printed in the upper right corner of the signature frame 210 . This code is normally a verification code such as a security code that is entered to prove that the cardholder who actually has the credit card is a legitimate user. This is a code for capturing unauthorized use of cards acquired as goods. This code is hereinafter referred to as "fake verification code 220". Neither the value of the false confirmation code 220 nor the value of the security code are recorded on the magnetic stripe 290 .

The fake confirmation code 220 is a code different from the security code assigned to the credit card 100 . The fake verification code 220 may be composed of characters that form a string representing the security code assigned to the credit card 100 . For example, if the security code string assigned to the credit card 100 is "456", the fake verification code 220 may be "546", which is "4", "5", and "6" in a different order. .

The order of the characters forming the character string representing the false confirmation code 220 may be designated by the card issuer at the time of card issuance. For example, the card issuance requester may request card issuance by designating that the string of characters arranged in the order of the 2nd, 1st, and 3rd characters of the security code is to be used as the fake verification code. . The card issuing company generates a security code from the card number, expiration date and service code of the credit card 100 to be issued. The card issuer manages a character string in which the character strings of the generated security code are arranged in the order specified by the card issuer as the fake confirmation code 220 of the credit card 100.例文帳に追加Note that the character string representing the fake verification code 220 may be generated independently of the security code.

The security code for credit card 100 may be communicated to cardholder 80 by sending it to cardholder 80 along with credit card 100 . The security code need not be displayed on the credit card 100. Cardholder 80 knows that fake verification code 220 displayed in signature box 210 is not a security code. Therefore, when the cardholder 80 enters the security code on a payment screen for online shopping, etc., the security code sent with the credit card 100 is entered instead of the fake confirmation code 220 . Thereby, the management server 40 can determine that the credit card 100 used is valid in the authorization process. The security code is called, for example, CVV, CVV2, CVC, CVC2, CID, or the like, depending on the credit card issuer.

Next, the case where the unauthorized user 90 illegally uses the found credit card 100 and uses the unauthorized user terminal 190 to purchase a product at the store server 50 will be described. The unauthorized user 90 enters the credit card number and expiration date displayed on the front side 101 of the credit card 100 that he/she has found and the signature frame 210 displayed on the back side 102 of the credit card 100 on the payment screen of the product he/she intends to purchase. and the fake confirmation code 220 described in , are entered in the respective entry fields. The management server 40 extracts the code input as the security code code from the sales authorization message from the shop server 50 . The management server 40 suspends the use of the credit card 100 when the extracted code matches the fake confirmation code 220 .

Thus, according to the system 10, it is possible to suspend the use of the credit card 100 when the unauthorized user 90 tries to use the credit card 100 fraudulently. Therefore, even if the card holder 80 is not aware of the loss of the credit card 100, it is possible to suspend the use of the credit card 100 before the credit card 100 is illegally used. . In other words, it is possible to induce the unauthorized user 90 to perform the procedure for suspending the use of the credit card 100 instead of the cardholder 80 .

After the suspension of use of the credit card 100 is performed, the management server 40 returns authorization NG to the authorization message for the sales using the credit card 100 . That is, the management server 40 does not approve transactions using the credit card 100 . In this case, the card holder 80 asks the card issuer to reissue the credit card, and has a new credit card issued with a different credit card number and security code.

Also, the cardholder 80 can use the fake verification code 220 to restrict the use of the credit card 100 . For example, the cardholder 80 can put the credit card 100 into a restricted state by notifying the card issuer of the false verification code 220 . In this case, the management server 40 transmits to the cardholder terminal 180 a restriction release code for releasing the usage restriction. By notifying the card issuer of the received restriction release code, the cardholder 80 can release the restriction on the use of the credit card 100 and resume the use of the credit card 100. - 特許庁

When the credit card 100 is in the limited use state, the management server 40 returns authorization NG to the authorization message for sales using the credit card 100 . Therefore, even if it is unclear whether the credit card 100 is lost or not, the cardholder 80 can prevent unauthorized use by restricting the use of the credit card 100 using the false confirmation code 220. . When the credit card 100 is found, the usage restriction can be released with the restriction release code received from the management server 40 . Therefore, the cardholder 80 can quickly restrict the use of the credit card 100 even if it is not clear whether the credit card 100 has been lost.

In system 10, fake verification code 220 is a code different from the security code. Therefore, the cardholder 80 can easily write down the fake verification code 220 in a memorandum or the like. Therefore, even when the credit card 100 is not at hand, the card holder 80 can refer to the fake confirmation code 220 stamped in the memorandum and request usage restriction.

As described above, according to the system 10, it is possible to prevent unauthorized use of the credit card 100 by using the false confirmation code 220. FIG. Also, the cardholder 80 can use the fake verification code 220 to quickly restrict the use of the credit card 100 . Therefore, unauthorized use of the card can be effectively suppressed.

FIG. 3 is a block diagram showing the functional configuration of the management server 40. As shown in FIG. The management server 40 includes a processing unit 42 , a storage unit 48 and a storage unit 44 . The processing unit 42 is realized by a processing device including a processor. The storage unit 48 is realized by a volatile storage device. The storage unit 44 is realized by a nonvolatile storage device.

The processing unit 42 includes a usage information reception unit 410, a usage suspension unit 420, a determination unit 430, a restriction request information reception unit 440, a usage restriction unit 450, a restriction release information transmission unit 460, and a restriction release information reception unit. 470 , a usage restriction release unit 480 , and a notification unit 490 .

The usage information receiving unit 410 receives card usage information including the identification information of the credit card 100 and the first code information. The card usage information may be, for example, an authorization message for sales in transactions using the credit card 100 . The credit card identification information may be, for example, the credit card number of the credit card 100 . A credit card number is an example of PAN information. The first code information may be, for example, code information entered in the security code entry field when using the credit card 100 . The first code information may be a security code value included in the authorization message.

The usage suspension unit 420 manages the first code information included in the card usage information received by the usage information receiving unit 410 in association with the identification information displayed on the credit card 100. If it matches the second code information, use of the credit card 100 is stopped. The second code information may be, for example, the value of false verification code 220 . The value of the false confirmation code 220 and information indicating the status of the credit card 100 are stored in the storage unit 44 in association with the card ID that identifies the credit card 100 . The usage suspension unit 420 determines that the first code information included in the card usage information received by the usage information receiving unit 410 is a false confirmation code stored in the storage unit 44 in association with the card ID that identifies the credit card 100. 220, the state information of the credit card 100 stored in the storage unit 44 in association with the card ID is set to the "suspended" state.

The determination unit 430 determines that the first code information is code information different from the second code information and is a predetermined third code for preventing unauthorized use of the credit card 100 identified by the identification information. If the information matches, the credit card 100 identified by the identification information is determined to be valid. The third code information may be stored in the storage section 44 in association with the card ID that identifies the credit card 100 . The third code information does not have to be stored in the storage section 44 . In this case, determination section 430 may derive the third code information by calculation using the identification information included in the card usage information. For example, the determination unit 430 may derive the third code information by computation using the credit card number and expiration date included in the authorization message. The third code information may be, for example, the security code of the credit card 100 identified by the identification information included in the card usage information.

The third code information may contain multiple characters included in the second code information. The order of the characters representing the third code information may be different from the order of the characters representing the second code information. For example, as described above, if the security code string assigned to the credit card 100 is "456", the fake verification code 220 is "546", which is "4", "5", and "6" in different order. ' may be

Restriction request information receiving unit 440 receives card use restriction request information including identification information of credit card 100 and fourth code information for restricting use of credit card 100 . For example, the restriction request information receiving unit 440 receives card usage restriction request information from the cardholder 80 . The restriction request information receiving section 440 may receive card usage restriction request information from the cardholder terminal 180 . The restriction request information receiving unit 440 may receive card usage restriction request information including the fourth code information input by the cardholder 80 through the application of the cardholder terminal 180 . Cardholder 80 may send card restriction request information by calling the card issuer. When the card usage restriction request information is transmitted by telephone, the restriction request information receiving unit 440 confirms the identity of the cardholder 80 using the telephone number of the caller, and then confirms the number entered by the cardholder 80 by key operation of the telephone. 4 code information may be received.

The usage restriction unit 450 is included in the card usage restriction request information when the fourth code information matches the second code information managed in association with the identification information included in the card usage restriction request information. Use of the credit card 100 identified by identification information is restricted. For example, the usage restriction unit 450 sets the status information of the credit card 100 stored in the storage unit 44 in association with the card ID specifying the credit card 100 to the "restricted" status.

If the fourth code information matches the second code information managed in association with the identification information included in the card usage restriction request information, the restriction release information transmitting unit 460 removes it from the card usage restriction request information. Limit release information for releasing the use limit of the credit card 100 identified by the included identification information is sent to the cardholder 80 . For example, the restriction release information transmission unit 460 transmits restriction release information to the cardholder terminal 180 .

The restriction release information receiving unit 470 receives restriction release information for releasing the usage restriction of the credit card 100 . For example, the restriction release information receiving unit 470 receives restriction release information from the cardholder 80 . For example, the restriction release information receiving unit 470 may receive restriction release information from the cardholder terminal 180 .

If the restriction release information received by the restriction release information reception unit 470 matches the restriction release information transmitted to the cardholder 80 by the restriction release information transmission unit 460, the usage restriction release unit 480 adds the restriction release information to the card usage restriction request information. Release the restriction on the use of the credit card 100 identified by the included identification information. As a result, the restriction on the use of the credit card 100 can be released later, so that the cardholder 80 can easily restrict the use of the credit card 100 even at the stage when it is not clear whether the credit card 100 is lost or not. be able to.

When the usage restriction unit 450 restricts the use of the credit card 100 identified by the identification information included in the card usage restriction request information, the notification unit 490 receives the first code included in the card usage information described above. When the information matches the second code information managed in association with the identification information included in the card usage information, a report is sent to a predetermined report destination. For example, the reporting unit 490 may report not only to the cardholder 80 but also to a reporting destination other than the cardholder 80, such as a credit information agency, an insurance company, a store that operates the store server 50, and the like.

FIG. 4 shows an example of information stored in the storage unit 44 in a table format. FIG. 4A is an example of an authorization information table used for credit card authorization processing. The approval information table stores information in which card IDs, security codes, credit card statuses, credit card expiration dates, and personal identification numbers are associated with each other. The card ID is information that identifies the credit card issued by the card issuing company. A card ID is information corresponding to a credit card issued by a card issuer on a one-to-one basis. The card ID may be arbitrary ID information assigned to the credit card on a one-to-one basis, key information such as a hash value derived from the credit card number, or the credit card number itself. .

"Security code" stores the value of the security code assigned by the card issuing company when the credit card is issued. "Status" stores a value indicating the current status of the credit card. "Status" includes a value indicating "available" indicating that the credit card 100 can be used, a value indicating "restricted" indicating that the use of the credit card 100 is restricted, and a value indicating that the credit card 100 is not used. One of the values indicating "stopped" indicating the stopped state is stored. "Expiration date" stores a value indicating the expiration date of the credit card. "PIN code" stores a value indicating the PIN code of the credit card. The personal identification number may be information notified to the card issuer when the card issuer requests the issuance of the credit card.

(B) of FIG. 4 shows a card usage management table stored in the storage unit 44 . The card usage management table stores information in which card IDs, fake confirmation codes, restriction release codes, restriction release code expiration dates, and tokens are associated with each other.

"Fake confirmation code" stores a value indicating the fake confirmation code displayed on the credit card. As noted above, the fake verification code may be a string generated by permuting the characters of the security code string.

The "restriction release code" stores a value indicating the restriction release information transmitted from the restriction release information transmitting unit 460 to the cardholder in response to the card use restriction request information from the cardholder. "Restriction release code expiration date" is the expiration date of the restriction release information sent to the cardholder. The restriction release information becomes invalid after the expiration date. After the expiration date of the restriction release code expires, the status of the credit card may be changed from the usage restricted status to the usage suspended status. A “token” is information assigned to the cardholder terminal 180 by the management server 40 . A token is an example of information identifying a cardholder 80 or cardholder terminal 180 . Tokens will be described later.

FIG. 5 shows an example of the registration screen 500 of the credit card 100 subject to usage restrictions. Registration screen 500 is displayed on cardholder terminal 180 by application software installed on cardholder terminal 180 . This application software is software having a function for managing the use restriction state of the credit card 100 . In this embodiment, this application software is abbreviated as a usage restriction management application.

A usage restriction management application is provided by, for example, a card issuing company. The registration screen 500 includes a card number entry field 510 for entering a credit card number, an expiration date entry field 520 for entering an expiration date, a personal identification number entry field 530 for entering a personal identification number, and a usage restriction. and a button 540 for registering the credit card for which the

The cardholder 80 enters the credit card number and expiration date of the credit card 100 in the card number entry field 510 and the expiration date entry field 520, respectively. In addition, the cardholder 80 enters the personal identification number of the credit card 100 set when the cardholder 80 requested the issuance of the credit card 100 into the personal identification number input field 530 . When the button 540 is pressed in this state, the cardholder terminal 180 transmits the registration information including the information entered in each entry field to the management server 40 .

When the management server 40 receives the registration information, the processing section 42 of the management server 40 identifies the card ID associated with the received information based on the information stored in the storage section 44 . The processing unit 42 generates a token for the card holder terminal 180, associates it with the card ID, and stores it in the card usage management table of the storage unit 44. FIG. The processing unit 42 also transmits the generated token to the cardholder terminal 180 . The cardholder terminal 180 stores the token received from the management server 40 as an operation parameter of the usage restriction management application. Thereafter, when the usage restriction management application is activated, the cardholder terminal 180 accesses the management server 40 using the token stored in the usage restriction management application.

FIG. 6 shows an example of a screen when the usage restriction management application is activated. When the token received from the management server 40 is stored, the usage restriction management application displays a usage restriction screen 600 shown in FIG. Usage restriction screen 600 includes a code input field 610 for inputting false confirmation code 220 and a button 620 for instructing usage restriction.

Cardholder 80 enters fake verification code 220 in code entry field 610 and presses button 620. Cardholder terminal 180 issues a card usage restriction request containing the information and token entered in code entry field 610. Information is sent to the management server 40 .

In the management server 40 , when the restriction request information receiving unit 440 receives the card usage restriction request information, the usage restriction unit 450 adds the token and the false confirmation code included in the card usage restriction request information to the card usage management table in the storage unit 44 . If stored in correspondence, the card ID associated with the token and the false confirmation code is identified. The usage restriction unit 450 stores a value indicating “restriction” in the status information of the approval information table in the storage unit 44 in association with the identified card ID. The usage restriction unit 450 also generates a restriction release code, stores the generated restriction release code in the card usage management table of the storage unit 44 in association with the token confirmation and fake confirmation codes included in the card usage restriction request information. Store. Also, the restriction release information transmission unit 460 transmits the restriction release code generated by the usage restriction unit 450 to the cardholder terminal 180 .

As described above, if the cardholder 80 first registers the information of the credit card 100 with the usage restriction management application, the usage restriction management application can be activated and the fake confirmation code 220 can be obtained without complicated authentication. By inputting, the use of the credit card 100 can be restricted. In this way, the cardholder 80 can contact the card issuing company to prevent the credit card 100 from being used when the credit card 100 is stolen or when the credit card 100 may be lost. No need to look ahead. Therefore, the restriction on use of the credit card 100 can be quickly completed. For example, when the credit card 100 is stolen by snatching, after immediately reporting to the police, the use restriction of the credit card 100 can be completed before the police arrive. According to the system 10, the time lag until use is restricted can be significantly shortened, so the psychological burden on the cardholder 80 can be reduced.

FIG. 7 shows an example of a restriction release code display screen 700 displayed when the cardholder terminal 180 receives a restriction release code. The restriction release code display screen 700 includes a restriction release code display field 710 indicating the restriction release code, a time limit display field 720 indicating the expiration date of the restriction release code, and a button 730 for instructing to end the restriction release code display. including. Cardholder terminal 180 closes restriction release code display screen 700 when button 730 is pressed.

As described above, the cardholder 80 can know the restriction release code for releasing the usage restriction of the credit card 100 and the expiration date in response to the card usage restriction request operation for the credit card 100 .

FIG. 8 shows an example of a restriction release screen 800 for releasing restrictions on the use of the credit card 100. As shown in FIG. Restriction release screen 800 includes a restriction release code entry field 810 for entering a restriction release code, and a button 820 for instructing release of usage restrictions.

The cardholder 80 enters the restriction release code displayed on the restriction release code display screen 700 of FIG. The information input in the input field 810 and the restriction release information including the token are transmitted to the management server 40 .

In the management server 40 , when the restriction release information receiving section 470 receives the restriction release information, the usage restriction release section 480 associates the token and the restriction release code included in the restriction release information with the card usage management table in the storage section 44 . and the current time is before the expiration date of the restriction release code, the card ID associated with the token and the restriction release code is specified in the card usage management table of the storage unit 44 . The use restriction release unit 480 stores a value indicating “usable” in association with the identified card ID as status information in the approval information table of the storage unit 44 . As a result, the cardholder 80 can restore the credit card 100 to a usable state without requesting reissuance of the credit card.

As described above, the card holder 80 can cancel the usage restriction of the credit card 100 when the credit card 100 thought to be lost is found. Therefore, it is possible to easily restrict the use of the credit card 100. - 特許庁

FIG. 9 is a flow chart showing processing when the management server 40 receives a credit card 100 usage restriction request. This flowchart is started when the restriction request information receiving unit 440 receives the card use restriction request information from the card holder terminal 180 .

In S902, the usage restriction unit 450 determines whether or not there is a credit card associated with the fake confirmation code included in the card usage restriction request information received by the restriction request information reception unit 440. As described above, the card usage restriction request information includes the false confirmation code and the token notified to cardholder terminal 180 . The usage restriction unit 450 determines whether or not there is a card ID associated with the token and the false confirmation code included in the received card usage restriction request information in the card usage management table.

If there is a credit card associated with the fake confirmation code included in the card usage restriction request information, the usage restriction unit 450 restricts the usage of the credit card 100 in S904. Specifically, usage restriction unit 450 stores a value indicating “restricted” in the status information of the corresponding card ID in the approval information table of storage unit 44 .

In S<b>906 , the usage restriction unit 450 generates a restriction release code and stores the generated restriction release code in the card usage management table of the storage unit 44 . In S908, the restriction release information transmission unit 460 transmits the restriction release code generated by the usage restriction unit 450 to the cardholder terminal 180 as response information to the card usage restriction request information, and the processing of this flowchart ends.

In S902, if there is no credit card associated with the counterfeit confirmation code included in the card usage restriction request information, in S910, the processing unit 42 sends information to the effect that the restriction cannot be canceled as response information to the card usage restriction request information. It is transmitted to the card holder terminal 180, and the processing of this flowchart ends.

FIG. 10 is a flow chart showing processing when the management server 40 receives card usage information from the store server 50 . This flowchart is started, for example, when the usage information receiving unit 410 receives an authorization message for sales in transactions using the credit card 100 .

In S1002, the determination unit 430 refers to the authorization information table in the storage unit 44, identifies the card ID based on the credit card number in the card usage information, and determines the expiration date and expiration date of the credit card 100 corresponding to the identified card ID. Acquire the status of the credit card 100. In S1004, the determination unit 430 determines whether the credit card 100 has expired or the status of the credit card 100 is "suspended" based on the information acquired in S1002. If the expiration date of the credit card 100 has expired or the status of the credit card 100 is "suspended", authorization NG information indicating that the transaction is not approved is returned in S1014.

If the credit card 100 has not expired in S1004 and the status of the credit card 100 is not "suspended" in S1006, the security code included in the card usage information does not correspond to the card ID specified in S1002. It is determined whether or not it matches the false confirmation code stored in the card usage management table of the storage unit 44 in correspondence. If the security code matches the fake confirmation code, the usage suspension unit 420 suspends the usage of the credit card 100 in S1008. Specifically, the usage suspension unit 420 stores a value indicating “suspended” in the status information corresponding to the card ID identified in S1002 in the approval information table of the storage unit 44 .

At S1010, reporting unit 490 determines the state of credit card 100 identified at S1002. If the status of the credit card 100 specified in S1002 is "can be used", in S1016, the card holder 80 is notified that the use of the card has been suspended. If the status of the credit card 100 specified in S1002 is "restricted", in S1012, the fact that the credit card 100 is being used illegally is reported. In addition to the card holder 80, the destination of the report in S1012 can be a credit information agency, an insurance company, a store that provides the product for which the credit card 100 is used for payment, and the like. Subsequently, in S1014, the processing unit 42 returns authorization NG.

If it is determined in S1006 that the security code does not match the false confirmation code, determination unit 430 determines in S1020 whether the security code included in the card usage information is valid. The determination unit 430 determines whether the security code included in the card usage information matches the security code stored in the authorization information table of the storage unit 44 in association with the card ID specified in S1002. If the security code is not valid, the processing unit 42 returns authorization NG in S1014.

In S1020, if the security code included in the card usage information is valid, in S1022, determination unit 430 performs another authorization determination to determine whether or not to approve the transaction. For example, the determination unit 430 determines whether to approve the transaction based on the sales amount included in the card usage information and the current balance and credit limit of the credit card 100 or card holder 80 . If it is determined in S1022 that the transaction is not approved, in S1014 the processing unit 42 returns authorization NG. If it is determined in S1022 that the transaction is to be approved, in S1024 the processing unit 42 returns authorization OK indicating that the transaction is to be approved.

As explained above, according to the system 10, unauthorized use of the credit card 100 can be effectively suppressed. In the credit card 100, a fake confirmation code is printed at a position where a security code is printed on a credit card issued by another card issuer to prevent unauthorized use. Therefore, instead of the card holder 80 who does not know that the credit card 100 has been lost or stolen, the unauthorized user 90 can be guided to suspend the use of the credit card 100. - 特許庁As a result, credit card users can greatly reduce their anxiety about fraudulent use due to the loss of their credit cards. In addition, it is possible to reduce the damage as compared with the case of cash theft. Therefore, it can contribute to promoting the use of credit cards.

Even if an unauthorized user finds out that some credit cards with a code other than a security code printed near the signature frame 210 like the credit card 100 are in circulation, the unauthorized user Since it becomes impossible to reliably determine that the code in the signature frame 210 of the credit card to be used illegally is the security code, the illegal use of the credit card may be stopped. Therefore, it can contribute not only to credit card 100 but also to suppression of unauthorized use of other credit cards. It should be noted that whether the code printed in the signature frame 210 is used as a "confirmation code" for personal authentication such as a security code or as a "fake confirmation code 220" for catching unauthorized use of a credit card. may be configurable for each cardholder. By enabling the setting for each cardholder, it is possible to discourage unauthorized credit card acquirers from using the card.

In the system 10 described above, it is possible for the cardholder 80 to cancel the usage restrictions on the credit card 100 . However, it may be possible for the cardholder 80 to set whether or not to permit the release of the usage restriction of the credit card 100 . For example, when the management server 40 receives, through the card holder terminal 180, a notification indicating that the usage restriction of the credit card 100 is not permitted, the usage restriction of the credit card 100 is canceled in the card usage management table of the storage unit 44. may store information to the effect that is not permitted. When it is set that the release of the credit card 100 usage restriction is not permitted, the restriction release information transmitting unit 460 does not transmit the restriction release code to the card holder terminal 180 when receiving the card usage restriction request information. . In addition, even when the restriction release code is received from the card holder terminal 180, the usage restriction release unit 480 does not release the usage restriction of the credit card 100. FIG. As a result, the card holder 80 can prohibit the release of the credit card 100 use restriction when it is certain that the credit card 100 has been lost.

In addition, in this embodiment described above, the credit card 100 is an example of a card used for financial transactions. Cards used for financial transactions include credit cards, debit cards, account cards of financial institutions such as banks and securities companies, and the like. Also, the credit card number mentioned above is a so-called membership number. A credit card number is an example of a PAN (Primary Account Number).

Note that each unit of the management server 40 may be implemented by hardware, software, or both hardware and software. At least part of each part of the management server 40 may be realized by a single server, or may be realized by a plurality of servers. At least part of each part of the management server 40 may be implemented on a virtual machine or a cloud system. At least part of each part of the management server 40 may be realized by a personal computer or a mobile terminal. Examples of mobile terminals include mobile phones, smart phones, PDAs, tablets, notebook computers or laptop computers, wearable computers, and the like. The management server 40 may store information using a distributed ledger technology such as blockchain or a distributed network.

When at least part of the components that make up the management server 40 are implemented by software, the components implemented by the software define the operations of the components in an information processing device with a general configuration. It may be implemented by activating software or a program. The information processing device having the above general configuration includes (i) a data processing device having a processor such as a CPU and GPU, a ROM, a RAM, a communication interface, and the like; Input devices such as devices, gesture input devices, various sensors, and GPS receivers, (iii) output devices such as display devices, audio output devices, and vibration devices, and (iv) storage devices such as memories, HDDs, and SSDs (external including a storage device).

In the information processing apparatus having the general configuration described above, the data processing apparatus or storage device may store the software or program described above. The software or program is executed by the processor to cause the information processing device to perform operations defined by the software or program. The above software or program may be stored in a non-transitory computer-readable recording medium. The software or program described above may be a program for causing a computer to function as the management server 40 or a part thereof. The above software or program may be a program for causing a computer to execute information processing in the management server 40 or part thereof.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It is obvious to those skilled in the art that various modifications and improvements can be made to the above embodiments. In addition, matters described with respect to a specific embodiment can be applied to other embodiments as long as they are not technically inconsistent. It is clear from the description of the scope of claims that forms with such modifications or improvements can also be included in the technical scope of the present invention.

The execution order of each process such as actions, procedures, steps, and stages in the devices, systems, programs, and methods shown in the claims, the specification, and the drawings is particularly "before", "before" etc., and it should be noted that they can be implemented in any order unless the output of the previous process is used in the subsequent process. Regarding the operation flow in the claims, the specification, and the drawings, even if the description is made using “first,” “next,” etc. for convenience, it means that it is essential to carry out in this order. not a thing

10 System 12 Network 40 Management server 42 Processing unit 44 Storage unit 48 Storage unit 50 Store server 80 Card holder 90 Unauthorized user 100 Credit card 101 Front surface 102 Back surface 110 Card number 120 Expiration date 180 Card holder terminal 190 Unauthorized user terminal 210 signature frame 220 fake confirmation code 290 magnetic stripe 410 usage information receiving unit 420 usage suspension unit 430 judging unit 440 restriction request information receiving unit 450 usage restriction unit 460 restriction cancellation information transmission unit 470 restriction cancellation information reception unit 480 usage restriction cancellation unit 490 Reporting section 500 Registration screen 510 Card number input field 520 Validity period input field 530 PIN input field 540 Button 600 Usage restriction screen 610 Code input field 620 Button 700 Restriction release code display screen 710 Restriction release code display field 720 Expiration date display field 730 Button 800 Restriction release screen 810 Restriction release code entry field 820 Button

Claims (10)

a usage information receiving unit that receives card usage information including identification information of a card used for financial transactions and first code information;
The first code information included in the card usage information received by the usage information receiving unit is code information displayed on the card and is a second code managed in association with the identification information. A system comprising a suspension unit for suspending the use of the card when the information matches the information. The first code information is different from the second code information and matches predetermined third code information for preventing unauthorized use of the card identified by the identification information. 2. The system according to claim 1, further comprising a judging unit for judging that the card identified by the identification information is valid when the card is issued. 3. The system of claim 2, wherein said third code information is a security code of said card identified by said identification information. The third code information includes a plurality of characters included in the second code information,
4. The system of claim 2 or 3, wherein the order of the characters representing the third code information is different from the order of the characters representing the second code information. a restriction request information receiving unit that receives card usage restriction request information including identification information of a card used for financial transactions and fourth code information for restricting the use of the card from a card holder terminal;
When the fourth code information matches the second code information managed in association with the identification information included in the card usage restriction request information, the card usage restriction request information includes the 5. The system according to any one of claims 1 to 4, further comprising a usage restriction unit that restricts usage of the card identified by the identification information. When the fourth code information matches the second code information managed in association with the identification information included in the card usage restriction request information, the card usage restriction request information includes the 6. The system according to claim 5, further comprising a restriction release information transmitting unit that transmits restriction release information for releasing restriction on use of the card identified by the identification information to the cardholder terminal. a restriction release information receiving unit that receives restriction release information for releasing restriction on use of the card from the card holder terminal;
When the restriction release information received by the restriction release information receiving unit matches the restriction release information transmitted to the cardholder terminal by the restriction release information transmission unit, the card use restriction request information includes the 7. The system according to claim 6, further comprising a usage restriction release unit that releases usage restriction of the card identified by the identification information. When the use restriction unit restricts the use of the card identified by the identification information included in the card usage restriction request information, the first code information included in the card usage information 8. The method according to any one of claims 5 to 7, further comprising a reporting unit that reports to a predetermined reporting destination when the code matches the second code information managed in association with the identification information included in the card usage information. or the system according to item 1. a restriction request information receiving unit for receiving card usage restriction request information including identification information of a card used for financial transactions and code information for restricting the use of the card;
The code information included in the card use restriction request information received by the restriction request information receiving unit matches code information displayed on the card and managed in association with the identification information. a usage restriction unit that restricts the use of the card when
If the code information included in the card usage restriction request information matches the code information managed in association with the identification information, the card possessing restriction release information for releasing the usage restriction of the card. and a restriction release information transmitting unit that transmits to the user terminal. A program for causing a computer to function as the system according to any one of claims 1 to 9.

Images