JP7109952B2 - card payment system - Google Patents

Description

The present invention relates to a card payment system capable of reducing system load.

In recent years, with the spread of virtual stores on the Internet (online shops), there are various ways such as holding special sales at virtual stores and accepting new product purchases at virtual stores before physical stores. Companies are making strategic use of virtual stores. Under such circumstances, a phenomenon occurs in which the use of credit cards at virtual shops concentrates during specific periods, such as the sales period and the acceptance period for purchasing new products. Therefore, the number of authorization processing (credit inquiry processing) increases rapidly during that specific period, so the number of authorization processing cases is reduced by temporarily raising the floor limit (the maximum amount of money that requires authorization processing). (see paragraph number 0005 of Patent Document 1).

Japanese Patent Application Laid-Open No. 2007-183978

However, if the floor limit is raised to reduce the number of authorization processes, a problem arises in that the credit card company's risk increases. In particular, in the case of a virtual store, there are more fraudulent uses of credit cards than in a real store, so it can be said that the risk is greater.

SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and its main object is to provide a credit card settlement system capable of reducing the number of authorization processes without increasing the floor limit.

In order to solve the above-described problems, a card payment system according to one aspect of the present invention includes usage condition setting means for setting usage conditions for a credit card at a virtual store in response to a request from a credit card user. a first determination means for determining whether or not a usage condition is set for the credit card when a credit card usage request is received; and a credit card related to the usage request when the usage condition is determined to be set. a second judgment means for judging whether or not the use of the card satisfies the conditions of use; and payment means for disallowing payment by the credit card when it is determined that the usage conditions are not satisfied.

The above aspect may further include second payment means for performing payment after performing credit card authorization processing when it is determined that the use condition is not set.

According to another aspect of the present invention, a credit card payment system includes a usage condition setting means for setting usage conditions for a credit card at a virtual store in response to a request from a credit card user; is received, a second determination means for determining whether or not the use of the credit card related to the use request satisfies the conditions of use of the credit card; settlement means for performing settlement without performing the authorization process of (1) and disallowing the credit card settlement when it is determined that the usage conditions are not satisfied.

In the above aspect, the usage condition setting means may be configured to set usage conditions including at least one of a credit card usage period, number of times, and amount of money.

In the above aspect, the usage condition setting means may be configured to set usage conditions including a virtual shop where credit cards are accepted.

In the above aspect, the usage condition setting means may be configured to set usage conditions including a communication terminal that can be used by the user of the credit card.

In the above aspect, the usage condition setting means is configured to set usage conditions including whether or not a specific program is to be executed in the communication terminal of the user of the credit card. Further comprising execution presence/absence information receiving means for receiving execution/non-execution information indicating whether or not a specific program is to be executed, the second determination means determining whether or not the usage conditions are satisfied based on the execution/non-execution information. may be configured to

Further, in the above aspect, the number recording means for recording the number of times the usage conditions are not satisfied for each virtual shop; It may further include identification means and warning output means for outputting a warning indicating that there is a possibility of unauthorized use of the identified virtual shop.

Further, in the above aspect, a user specifying means for specifying a user who has a usage history at the specified virtual shop, and for the specified user, setting conditions for using a credit card at the specified virtual shop. and setting prompting means for prompting the user to perform the setting.

Further, in the above aspect, a number recording means for recording the number of times the credit card is determined not to satisfy the usage conditions; It may further comprise identifying means and second warning output means for outputting a warning indicating that the identified credit card may be used illegally.

Further, the above aspect may further include providing means for providing each user with privilege information to be given to the user when the usage conditions are set.

According to the present invention, it is possible to reduce the number of authorization processes while ensuring safety.

1 is a block diagram showing the configuration of a card payment system and its communication destination according to an embodiment of the present invention; FIG. 1 is a block diagram showing the configuration of a prior notification system according to an embodiment of the present invention; FIG. FIG. 4 is a diagram showing an example of the layout of a usage rule database; 4 is a flowchart showing the procedure of a usage condition setting process; FIG. 4 is a diagram showing a display example of a usage condition setting screen; Flowchart (first half) showing the procedure of card payment processing. Flowchart (second half) showing the procedure of card payment processing. 4 is a flowchart showing the procedure of unauthorized use warning processing; 4 is a flowchart showing the procedure of advance report reminder processing; 4 is a flowchart showing the procedure of privilege information provision processing;

Preferred embodiments of the present invention will be described below with reference to the drawings. It should be noted that each of the embodiments shown below exemplifies a method and apparatus for embodying the technical idea of the present invention, and the technical idea of the present invention is not limited to the following. do not have. Various modifications can be made to the technical idea of the present invention within the technical scope described in the claims.

[Configuration of card authentication system]
FIG. 1 is a block diagram showing the configuration of a card payment system and its communication destinations according to an embodiment. As shown in FIG. 1, the card settlement system 1 of the present embodiment includes an authorization system 2 provided on the side of a credit card issuing company, and an advance declaration system 3 similarly provided. The authorization system 2 is a computer system that performs authorization processing that is executed when a credit card is used. It is a computer system for determining availability.

The authorization system 2 and the advance declaration system 3 are connected so as to be able to communicate with each other. Also, the authorization system 2 and the advance declaration system 3 are communicably connected to the Internet 101 . The authorization system 2 consists of user terminals 4, 4, . 5, 5, . Here, the user terminal 4 is configured by, for example, a personal computer, a mobile phone such as a smart phone, a tablet terminal, or the like.

[Authorization system configuration]
The authorization system 2 is composed of one or more computers, and executes predetermined authorization processing. When a credit card is used in a virtual shop, it also has a role of intermediary between the shop server 5 of the virtual shop and the pre-report system 3 .

[Configuration of advance declaration system]
The advance notification system 3 is composed of one computer. The detailed configuration of this prior notification system 3 will be described below.
FIG. 2 is a block diagram showing the configuration of the advance notification system 3. As shown in FIG. As shown in FIG. 2, the advance declaration system 3 includes a CPU 31, a ROM 32, a RAM 33, a hard disk 34, and a communication interface (I/F) 35. These CPU 31, ROM 32, RAM 33, hard disk 34, and communication I/F F 35 are connected by bus 36 .

The CPU 31 executes various computer programs loaded on the RAM 33 . As a result, the computer 3 functions as the prior notification system 3 of this embodiment.

The ROM 32 is composed of a mask ROM, a PROM (Programmable ROM), an EPROM (Erasable PROM), an EEPROM (Electrically Erasable PROM), or the like, and stores computer programs executed by the CPU 31 and data used during the execution thereof. is stored.

The RAM 33 is composed of an SRAM, a DRAM, or the like. This RAM 33 is used for reading out various computer programs stored in the hard disk 34 . It is also used as a work area for the CPU 31 when the CPU 31 executes various computer programs.

Various computer programs to be executed by the CPU 31 and data used for executing the computer programs are pre-installed in the hard disk 34 . The hard disk 34 also has a user database (DB) 34A that stores user information about users, and a use condition database that stores use condition information related to use conditions set by prior declaration by each user. (DB) 34B, a store database (DB) 34C storing store information related to each virtual store, and an out-of-conditions history database (DB) 34D storing the history of transactions determined to be outside the range of usage conditions, A fraudulent use database (DB) 34E that stores fraudulent use information about virtual shops and credit cards that may be fraudulently used, and a usage history database (DB) 34F that stores credit card usage histories are provided. there is Details of each of these databases will be described later.

Further, the hard disk 34 is installed with a multitasking operating system such as Windows (registered trademark) manufactured and sold by Microsoft Corporation. In the following description, it is assumed that various computer programs run on the operating system.

Communication I/F 35 is an interface device for communication between prior notification system 3 and an external device via Internet 101 . Via this communication I/F 35, the advance report system 3 transmits and receives various data to and from the user terminals 4, 4, . . . and the shop servers 5, 5, .

Details of each database provided in the hard disk 34 will be described below.
(A) User DB 34A
The user DB 34A stores user information including the user's name, contact information, credit card number, and terminal ID for identifying the user terminal 4 used by the user. This terminal ID is stored in the user DB 34A only when it is provided by each user.

(B) Terms of use DB 34B
FIG. 3 is a diagram showing an example of the layout of the usage rule DB 34B. As shown in FIG. 3, the usage condition DB 34B has at least a card number field 301, a period field 302, a number of times field 303, an amount field 304, a store field 305, a terminal field 306, an activation field 307, and an effective field 308. there is

The card number field 301 stores the card number of each user's credit card. Also, the term field 302, the number of times field 303, and the amount field 304 store the period during which the credit card can be used, the maximum number of times, and the maximum amount, respectively. The store field 305 stores store IDs that identify virtual stores that accept credit cards.

The terminal field 306 stores information indicating whether or not the user has identified an available user terminal 4 . In this embodiment, "1" is stored in the terminal field 306 if specified, and "0" if not specified. When the user makes this specification, the credit card can be used only when the specified user terminal 4 is used.

The activation field 307 stores information indicating whether or not the user associates the activation of a specific program (dedicated application) with the use of a credit card. In this embodiment, "1" is stored in the activation field 307 when the association is established, and "0" is stored when the association is not established. When the user makes this association, the credit card can be used only when the dedicated application is activated.

The validity field 308 stores information indicating whether or not the set usage conditions are valid. In this embodiment, the valid field 308 stores "1" if valid and "0" if invalid. If a credit card is used that satisfies the conditions of use, or if a set period of time has passed, the conditions of use are determined to be invalid, and "0" is stored in the valid field 308. Become.

(C) Store DB34C
The store DB 34C stores various types of information such as names and contact information of virtual stores in association with store IDs for identifying each virtual store.

(D) Unconditional history DB 34D
The non-conditional history DB 34D stores the non-conditional history, which is the history of transactions that do not satisfy the terms of use, ie, transactions determined to be out of the scope of the terms of use. This unconditional history includes the card number of the credit card and the store ID of the virtual store related to the transaction.

(E) Unauthorized use DB 34E
The fraudulent use DB 34E stores fraudulent use information related to virtual shops and credit cards determined to have the possibility of fraudulent use, as will be described later. This unauthorized use information includes the shop ID of the virtual shop and the card number of the credit card.

(F) Usage history DB 34F
The usage history DB 34F stores the credit card usage history of each user. This usage history includes the card number of the credit card and the store ID of the virtual store.

As described above, in the present embodiment, the pre-report system 3 is composed of one computer, but it is not limited to this, and the pre-report system 3 is composed of a distributed system composed of a plurality of computers. may have been

[Operation of card payment system]
Next, the operation of the card settlement system of the present embodiment configured as described above will be described with reference to flowcharts and the like. In the following, (1) usage condition setting processing for setting usage conditions based on advance declaration by the user, (2) credit card payment processing executed when using a credit card, and (3) possibility of unauthorized use. Unauthorized use warning processing to warn about, (4) Pre-report reminder processing to prompt the user to pre-report the terms of use, and (5) Benefits given to each user according to the setting of terms of use Each processing of privilege information providing processing for providing privilege information will be described.

(1) Usage condition setting processing Each user who uses a credit card at a virtual store can set usage conditions before using the credit card. The usage condition setting process that is executed when the setting is performed will be described below.

FIG. 4 is a flow chart showing the procedure of the usage condition setting process. As shown in FIG. 4, first, the user terminal 4 transmits a usage condition setting request to the advance notification system 3 according to the instruction received from the user (S101). This setting request includes information that can identify the user's credit card (card number, user's identification ID, etc.).

When the advance declaration system 3 receives a setting request from the user terminal 4 (S201), it refers to the usage condition DB 34B (S202), and then displays a usage condition setting screen related to the usage condition setting screen for accepting the setting of the usage condition. Information is generated (S203). Here, the advance declaration system 3 identifies the card number of the credit card based on the information included in the received setting request, and confirms whether or not the usage condition information related to the card number exists in the usage condition DB 34B. . If the usage condition information exists, usage condition setting screen information including the usage condition information is generated in step S203. The advance notification system 3 transmits the generated usage condition setting screen information to the user terminal 4 (S204).

When the user terminal 4 receives the use condition setting screen information from the advance declaration system 3 (S102), the use condition setting screen information is used to display the use condition setting screen on the display unit (S103).

FIG. 5 is a diagram showing a display example of a usage condition setting screen. As shown in FIG. 5, a usage condition setting screen 1001 includes a display column 1002 for displaying the name of the user and the credit card number, a display column 1003 for displaying the setting history of the usage condition, and each usage condition. An input field 1004 for input and a setting button 1005 for instructing setting are displayed. The setting history is displayed in the display column 1003 only when there is a usage condition setting history, that is, when usage condition information related to the card number exists in the usage condition DB 34B.

The user uses the input unit provided in the user terminal 4 to input desired usage conditions in the input field 1004 . For example, if the user can only use it for a specific period, the period (any period such as a day unit or an hour unit), if setting the upper limit of the number of times / amount, the upper limit When specifying a store, enter the name of the store, when specifying a terminal that can be used, enter that fact, and when making it available only when the dedicated application is started, enter that fact.

When inputting the usage conditions as described above, the user can refer to the setting history displayed in the display field 1003 . This facilitates the input of usage conditions. Note that even if each setting history is displayed in a selectable manner and when a specific setting history is selected by the user, the same terms of use as that setting history are automatically entered in the input field 1004. good.

After the usage conditions have been entered in this manner, the user clicks the setting button 1005 . This completes the reception of the input of the terms of use.

When the user terminal 4 accepts the input of the terms of use as described above (S104), the user terminal 4 transmits the terms of use input information including the terms of use to the advance notification system 3 (S105). When the advance notification system 3 receives the use condition input information from the user terminal 4 (S205), each use condition included in the use condition input information is registered in the use condition DB 34B (S206), and the process ends. .

After that, the pre-reporting system 3 transmits to the authorization system 2 pre-reported information indicating that the pre-reporting of the terms of use has been made. This pre-declared information includes the card number of the credit card for which the pre-declaration of the terms of use has been made. The authorization system 2 stores this pre-declared information in a storage device.

In the above description, the authorization system 2 does not judge whether or not the usage conditions can be set, but such a judgment may be made. Specifically, when the pre-declared information is received from the pre-declaration system 3, the authorization system 2 confirms the details of the pre-declared terms of use, and the credit card is used within the scope of the terms of use. It is determined whether or not the balance of the credit limit is insufficient. As a result, when it is determined that the usage limit is insufficient, the authorization system 2 determines that the usage conditions are not appropriate, and notifies the prior notification system 3 of that fact. Upon receiving this notification, the advance notification system 3 deletes the terms of use from the terms of use DB 34B. This can prevent inappropriate usage conditions from being set.

Further, as described above, instead of the authorization system 2 judging whether or not the conditions of use are appropriate after the conditions of use are set by the pre-notification system 3, the judgment may be made before the conditions of use are set. Specifically, when the advance declaration system 3 receives the use condition input information (S206), each use condition included in the use condition input information is transmitted to the authorization system 2, and the authorization system 2 receives the use conditions. may determine whether each usage condition is appropriate in the same manner as described above.

(2) Card payment processing When each user uses a credit card at the virtual shop, the following card payment processing is executed.
6A and 6B are flowcharts showing the procedure of card payment processing. A user accesses the store server 5 of a specific virtual store using the user terminal 4 and performs purchase procedures for products sold at the virtual store. As a result, the user terminal 4 transmits to the store server 5 purchase request information specifying the product to be purchased (S301). This purchase request information includes the terminal ID of the user terminal 4 and information indicating that access is made using a dedicated application.

When the store server 5 receives the purchase request information from the user terminal 4 (S401), it checks whether a credit card can be used to pay for the product specified by the purchase request information. A request for whether or not the card can be used is transmitted to the authorization system 2 (S402). This use permission/prohibition request includes the credit card number and the payment amount.

When the authorization system 2 receives the request for approval/disapproval of use from the store server 5 (S501), it refers to the pre-declared information stored in the storage device and determines the conditions of use for the card number included in the request for approval/disapproval of use. By confirming whether or not a prior report has been made, it is determined whether or not the usage conditions have been reported in advance (S502).

If it is determined in step S502 that the terms of use have not been declared in advance (NO in S502), the authorization system 2 performs authorization processing in the same manner as in normal transactions (S503). As a result, if the use of the credit card is approved (YES in S504), the authorization system 2 executes a predetermined settlement process such as processing as provisional sales (S505), and the credit card can be used. Use permission/prohibition information indicating that there is, is transmitted to the store server 5 (S506). On the other hand, if the use of the credit card has not been approved (NO in S504), the authorization system 2 transmits to the store server 5 usage permission/prohibition information indicating that the credit card cannot be used (S506).

When the shop server 5 receives the availability information from the authorization system 2 (S403), it transmits the availability information to the user terminal 4 (S404). When the user terminal 4 receives this availability information (S302), it displays the availability result indicated in the availability information on the display unit (S303).

If it is determined in step S502 that a prior declaration has been made (YES in S502), the authorization system 2 requests confirmation of whether or not the usage satisfies the set usage conditions. A confirmation request is transmitted to the advance declaration system 3 (S507).

When the advance declaration system 3 receives a condition confirmation request from the authorization system 2 (S601), it refers to the usage condition DB 34B (S602) and determines whether or not the current credit card usage satisfies the usage conditions ( S603). This determination differs depending on the usage conditions that have been set. For example, if usage conditions are set for the period, number of times, amount, and virtual store, whether the usage is within the period, does not exceed the upper limit of the number of times and amount, and is the same as the specified virtual store Whether or not the usage conditions are satisfied is determined by confirming whether or not there is. In addition, if the terminal is specified by the terms of use, the terminal ID of the user terminal 4 is specified based on the purchase request information transmitted from the terminal of the user terminal 4, and the terminal ID and the user By confirming whether or not the terminal ID stored in the DB 34A matches, it is determined whether or not the usage conditions are satisfied. Furthermore, if the use condition is set to allow use only when the dedicated application is activated, it determines whether or not the dedicated application is to be executed based on the purchase request information sent from the user terminal 4, and according to the result. It is determined whether or not the usage conditions are satisfied.

If it is determined in step S603 that the usage conditions are satisfied (YES in S603), the advance declaration system 3 executes a predetermined settlement process such as processing as provisional sales (S604), and credit card usage is possible. is sent to the authorization system 2 (S606). On the other hand, if it is determined that the usage conditions are not satisfied (NO in S603), the pre-reporting system 3 registers the non-conditional history in the non-conditional history DB 34D (S605). The approval/denial information is transmitted to the authorization system 2 (S606).

When the authorization system 2 receives the availability information from the advance declaration system 3 (S508), it transmits the availability information to the shop server 5 (S509). Similarly, the shop server 5 receives the usage availability information (S405) and transmits it to the user terminal 4 (S406). When the user terminal 4 receives this availability information (S304), it displays the availability result indicated in the availability information on the display unit (S305).

As described above, if there is no pre-declaration of terms of use, authorization processing can be performed as usual, while if there is a pre-declaration of terms of use, settlement can be performed without executing authorization processing. As a result, it is possible to reduce the number of authorization processes.

In addition, if there is a prior declaration of usage conditions, settlement processing is performed only when the usage conditions are satisfied, and the credit card cannot be used if the usage conditions are not satisfied. Since a third party other than the user who has made a prior declaration of the terms of use usually does not know the terms of use, it can be said that it is difficult to conduct a transaction that satisfies the terms of use. Therefore, it becomes possible to prevent unauthorized use by a third party.

(3) Unauthorized Use Warning Processing As described above, when there is a transaction that does not satisfy the terms of use, an unconditional history is registered in the unconditional history DB 34D. The advance notification system 3 executes the following unauthorized use warning process based on the unconditional history registered in the unconditional history DB 34D.

FIG. 7 is a flow chart showing the procedure of unauthorized use warning processing. As shown in FIG. 7, the pre-reporting system 3 first refers to the unconditional history DB 34D (S701), and identifies a virtual store or credit card with a predetermined number or more of transactions that do not satisfy the usage conditions (S702). .

Since it is rare for genuine users to repeat transactions that do not satisfy the terms of use, it is possible that credit cards with more than a predetermined number of transactions that do not satisfy the terms of use may be used fraudulently. It is considered to be of high quality. In addition, it can be said that there is a high possibility of fraudulent use of a virtual shop where transactions that do not satisfy the terms of use are repeated. Therefore, the advance reporting system 3 determines that the virtual shop or credit card identified in step S702 has a high possibility of being used illegally, and reports the illegal use information including the shop ID of the virtual shop or the credit card number. Register in the unauthorized use DB 34E (S703).

Next, based on the unauthorized use information registered in the unauthorized use DB 34E, the pre-reporting system 3 generates warning information identifying virtual shops or credit cards with a high possibility of unauthorized use (S704). Send (S705). This transmission destination is the person in charge of monitoring unauthorized use, and the warning information is transmitted to the person in charge using means such as e-mail, for example. This allows the person in charge to grasp virtual shops or credit cards that are highly likely to be used fraudulently.

(4) Pre-report reminder processing Users who have used credit cards at virtual shops with a high possibility of fraudulent use are likely to be involved in fraudulent use. In order to avoid being involved in such fraudulent use, it is preferable to declare the terms of use in advance. The pre-report system 3 can prompt such users to pre-report usage conditions by executing the following pre-report prompting process.

FIG. 8 is a flow chart showing the procedure of the pre-report prompting process. As shown in FIG. 8, the pre-reporting system 3 first refers to the unauthorized use DB 34E to identify virtual shops with a high possibility of unauthorized use (S801). Next, the pre-reporting system 3 refers to the usage history DB 34F to identify credit cards that have been used at the virtual shop identified in step S801 (S802).

Next, the pre-report system 3 refers to the usage condition DB 34B to identify a credit card for which a pre-report of the usage condition has not yet been made, that is, a card to be reminded, among the credit cards identified in step S802. (S803). Then, the advance declaration system 3 generates advance declaration reminder information for demanding advance declaration of terms of use (S804), and sends the advance declaration reminder information to the credit card user identified in step S803. Send (S805). This transmission is performed using e-mail or the like, for example.

A user who receives the above-mentioned advance notice notification information can know that he or she may be involved in unauthorized use, and that it is possible to make a prior notice of usage conditions as a countermeasure. Advance notification of usage conditions is made in accordance with this advance notification reminder information, thereby promoting advance notification.

(5) Privilege Information Provision Processing As described above, in the case of the present embodiment, there is no need to perform authorization processing for the use of credit cards for which usage conditions have been set, so the number of authorization processing cases can be reduced. can be done. Reducing the number of authorization processes reduces the load on the system, which is a great advantage for the credit card company that operates the system, but not for the credit card user. Therefore, in the present embodiment, when the usage conditions are reported in advance, the user is given a predetermined privilege such as an increase in usage points. As a result, users are also benefited, so advance declaration of terms of use will be promoted. The privilege information providing process described below is a process for notifying the user that the privilege will be given as such.

FIG. 9 is a flow chart showing the procedure of privilege information provision processing. As shown in FIG. 9, the pre-report system 3 first refers to the user DB 34A and the terms of use DB 34B (S901), and selects credit cards for which terms of use have not been pre-declared, that is, credit cards for which terms of use have not been set. Identify the card (S902).

Next, the advance declaration system 3 generates privilege information indicating the content of the privilege to be granted when the advance declaration of the usage conditions is made (S903), and converts the privilege information into the credit specified in step S902. It is sent to the card user (S904). This transmission is performed using e-mail or the like, for example.

A user who receives the privilege information can know that the privilege can be obtained if the usage conditions are declared in advance. Advance notification of usage conditions is made in accordance with this privilege information, thereby promoting advance notification.

In addition, for example, when a special sale is held at a virtual store, the pre-reporting system 3 acquires the schedule of the sale from the virtual store in advance, and uses a credit card that has been used at the virtual store. You may make it transmit privilege information addressed|directed to the user of. By pre-declaring the terms of use according to this privilege information, it is possible to prevent the number of authorization processes from increasing rapidly during the sale period, and as a result, it is possible to reduce the load on the system.

(Other embodiments)
In the above embodiment, the pre-notification system 3 has the usage condition DB, but the user terminal 4 that made the pre-notification may have a similar database. In this case, when using a credit card, that is, in card payment processing, the user terminal 4 transmits the terms of use stored in the database to the pre-declaration system 3 via the store server 5 and the authorization system 2 . The advance notification system 3 uses the usage conditions thus transmitted to determine whether or not the usage conditions are satisfied in the same manner as in step S603 above, and continues subsequent processing. With this, as in the case of the above-described embodiment, if there is a prior declaration of terms of use, settlement can be made without executing authorization processing, so the number of cases of authorization processing can be reduced. can. As in the case of the above embodiment, the authorization system 2 judges whether or not the usage conditions can be set. Conditions may be stored.

In addition, in the above embodiment, the authorization system 2 and the advance declaration system 3 are composed of separate computer systems that are communicably connected to each other, but are not limited to this. The authorization system 2 and the advance declaration system 3 may be realized by a computer system.

1 Card payment system 2 Authorization system 3 Pre-report system 31 CPU
32 ROMs
33 RAM
34 hard disk 35 communication interface 36 bus 34A user database 34B usage condition database 34C store database 34D unconditional history database 34E unauthorized use database 34F usage history database 4 user terminal 5 store server 101 Internet

Claims (11)

usage condition setting means for setting usage conditions of the credit card at the virtual store in response to a request from the credit card user;
a first determination means for determining, when a credit card usage request is received, whether or not usage conditions related to the credit card are set;
a second determination means for determining whether or not the use of the credit card related to the usage request satisfies the usage conditions when it is determined that the usage conditions are set;
settlement means for performing settlement without performing credit card authorization processing when it is determined that the usage conditions are satisfied, and disallowing the credit card settlement when it is determined that the usage conditions are not satisfied ;
a frequency recording means for recording the number of times it is determined that the usage conditions are not satisfied for each virtual shop;
virtual shop identifying means for identifying a virtual shop with a possibility of unauthorized use based on the number of times;
card payment system. Further comprising a second payment means for performing payment after performing authorization processing of the credit card when it is determined that the usage conditions are not set,
The card payment system according to claim 1. usage condition setting means for setting usage conditions of the credit card at the virtual store in response to a request from the credit card user;
a second determination means for determining, when a request for use of a credit card is received, whether the use of the credit card according to the request for use satisfies the conditions for use of the credit card;
settlement means for performing settlement without performing credit card authorization processing when it is determined that the usage conditions are satisfied, and disallowing the credit card settlement when it is determined that the usage conditions are not satisfied ;
a frequency recording means for recording the number of times it is determined that the usage conditions are not satisfied for each virtual shop;
virtual shop identifying means for identifying a virtual shop with a possibility of unauthorized use based on the number of times;
card payment system. The usage condition setting means is configured to set usage conditions including at least one of a credit card usage period, number of times, and amount.
The card settlement system according to any one of claims 1 to 3. The usage condition setting means is configured to set usage conditions including a virtual shop where credit cards can be used.
The card settlement system according to any one of claims 1 to 4. The usage condition setting means is configured to set usage conditions including a communication terminal that can be used by the user of the credit card.
The card payment system according to any one of claims 1 to 5. The usage condition setting means is configured to set usage conditions including whether or not a specific program is to be executed in a communication terminal on the user side of the credit card,
further comprising execution presence/absence information receiving means for receiving execution presence/absence information indicating whether or not the specific program is executed from the communication terminal;
The second determination means is configured to determine whether or not the usage condition is satisfied based on the execution presence/absence information.
The card settlement system according to any one of claims 1 to 6. warning output means for outputting a warning indicating that there is a possibility of unauthorized use of the identified virtual shop;
The card settlement system according to any one of claims 1 to 7. user identification means for identifying a user who has a usage history at the identified virtual shop and has not requested the setting of the usage conditions ;
9. The card payment system according to any one of claims 1 to 8, further comprising setting prompting means for prompting the specified user to set conditions for using the credit card at the specified virtual shop. a frequency recording means for recording the number of times the credit card is determined not to satisfy the usage conditions;
Credit card identification means for identifying a credit card that may be used illegally based on the number of times;
a second warning output means for outputting a warning indicating the possibility of unauthorized use of the specified credit card;
The card payment system according to any one of claims 1 to 9. further comprising providing means for providing each user with privilege information given to the user when the usage conditions are set;
The card settlement system according to any one of claims 1 to 10.

Images