JP2019169033A - Card settlement system - Google Patents

Abstract

To provide a card settlement system which can reduce the number of authorization processing of credit cards.SOLUTION: A card settlement system 1 comprises: use condition setting means for setting a use condition of a credit card at a virtual shop in response to a request from a credit card user; first determining means for determining, when receiving the request for use of a credit card, whether or not there is any use condition relating the credit card; second determining means for determining, when it is determined that the use condition is set, whether or not use of the credit card relating to the use request satisfies the use condition; and settlement means for, when it is determined that the use condition is satisfied, carrying out settlement without carrying out authorization processing for the credit card and for, when it is determined that the use condition is not satisfied, preventing the settlement of the credit card from being carried out.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a card payment system that can reduce the load on the system.

  In recent years, with the spread of virtual stores (online shops) on the Internet, special sales have been conducted at virtual stores, and new product purchases have been accepted at virtual stores prior to actual stores. Companies are starting to use virtual stores strategically. Under such circumstances, there has been a phenomenon in which the use of credit cards at virtual stores is concentrated in specific periods such as the above-mentioned sale period and new product purchase acceptance period. As a result, the number of authorization processing (credit inquiry processing) increases rapidly during that specific period, so the number of authorization processing can be reduced by temporarily raising the floor limit (the upper limit amount that requires authorization processing). (See paragraph number 0005 of Patent Document 1).

JP 2007-183978 A

  However, when the number of authorization processes is reduced by raising the floor limit as described above, there is a problem that the risk of the credit card company increases. In particular, in the case of a virtual store, the risk is greater because unauthorized use of credit cards is more frequent than in a real store.

  The present invention has been made in view of such circumstances, and a main object thereof 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 problem, a card payment system according to an aspect of the present invention is a usage condition setting unit that sets usage conditions for a credit card in a virtual store in response to a request from a credit card user. When a credit card usage request is received, a first determination unit that determines whether or not usage conditions relating to the credit card are set, and a credit relating to the usage request when it is determined that usage conditions are set A second determination means for determining whether or not the use of the card satisfies the use condition; and when making a payment without performing an authorization process of the credit card when it is determined that the use condition is satisfied, Payment means for disabling payment of the credit card when it is determined that the use conditions are not satisfied.

  The said aspect WHEREIN: You may further provide the 2nd payment means to perform payment, after performing the authorization process of the said credit card, when it determines with the usage conditions not being set.

  In addition, the card payment system according to another aspect of the present invention includes a usage condition setting unit that sets usage conditions for a credit card in a virtual store in response to a request from a credit card user, and a credit card usage request. The second determination means for determining whether or not the use of the credit card according to the use request satisfies the use condition according to the credit card, and the credit card when it is determined that the use condition is satisfied. And a settlement means for disabling the credit card when it is determined that the use condition is not satisfied.

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

  Moreover, the said aspect WHEREIN: The said usage condition setting means may be comprised so that the usage condition including the virtual store where a credit card can be used is set.

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

  Further, in the above aspect, the use condition setting means is configured to set use conditions including presence / absence of execution of a specific program in a communication terminal on a user side of the credit card. Execution presence / absence information receiving means for receiving execution presence / absence information indicating the presence / absence of execution of a specific program is further provided, and the second determination means determines whether or not the use condition is satisfied based on the execution presence / absence information. It may be configured to.

  Moreover, in the said aspect, the virtual store which specifies the virtual store which has the possibility of unauthorized use based on the said frequency | count, and the frequency recording means which records the frequency | count determined that the said usage conditions are not satisfied for every virtual store You may further provide the specific | specification means and the warning output means which outputs the warning which shows that there exists possibility of unauthorized use about the specified virtual store.

  Further, in the above aspect, a user specifying means for specifying a user who has a usage history at the specified virtual store, and setting of credit card use conditions at the specified virtual store for the specified user And setting prompting means for prompting.

  Moreover, in the said aspect, the credit card which specifies the credit card with the possibility of unauthorized use based on the said frequency | count, and the frequency recording means which records the frequency | count determined that the said usage conditions are not satisfied for every credit card You may further provide the specific means and the 2nd warning output means which outputs the warning which shows that there exists possibility of unauthorized use about the specified credit card.

  Moreover, in the said aspect, you may further provide the provision means which provides the privilege information provided to a user with respect to each user when a use condition is set.

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

The block diagram which shows the structure of the card payment system which concerns on embodiment of this invention, and its communication destination. The block diagram which shows the structure of the prior report system which concerns on embodiment of this invention. The figure which shows an example of the layout of a use condition database. The flowchart which shows the procedure of a use condition setting process. The figure which shows the example of a display of a use condition setting screen. The flowchart which shows the procedure of card payment processing (the first half). The flowchart which shows the procedure of a card payment process (second half). The flowchart which shows the procedure of an unauthorized use warning process. The flowchart which shows the procedure of a preliminary report reminding process. The flowchart which shows the procedure of a privilege information provision process.

  Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. In addition, each embodiment shown below illustrates the method and apparatus for actualizing the technical idea of this invention, Comprising: The technical idea of this invention is not necessarily limited to the following. Absent. The technical idea of the present invention can be variously modified within the technical scope described in the claims.

[Card authentication system configuration]
FIG. 1 is a block diagram showing a configuration of a card payment system and its communication destination according to an embodiment. As shown in FIG. 1, the card payment system 1 according to the present embodiment includes an authorization system 2 provided on the credit card issuing company side and a prior reporting system 3 provided in the same manner. The authorization system 2 is a computer system that performs an authorization process that is executed when a credit card is used. The prior declaration system 3 accepts a prior declaration of the usage conditions described later, and based on the usage conditions, It is a computer system that determines whether or not it can be used.

  The authorization system 2 and the prior declaration system 3 are connected so that they can communicate with each other. Further, the authorization system 2 and the prior declaration system 3 are connected to the Internet 101 so as to be communicable. The authorization system 2 is a user terminal 4, 4,... Provided on the credit card user side, and the prior declaration system 3 is a store server that operates the user terminals 4, 4,. 5, 5,... And various data are transmitted / received via the Internet 101. Here, the user terminal 4 is configured by, for example, a personal computer, a mobile phone such as a smartphone, or a tablet terminal.

[Authorization system configuration]
The authorization system 2 is composed of one or a plurality of computers, and executes a predetermined authorization process. When a credit card is used in a virtual store, it also has a role of mediating between the store server 5 of the virtual store and the prior reporting system 3.

[Preliminary report system configuration]
The prior declaration system 3 is composed of one computer. Hereinafter, the detailed structure of this prior report system 3 is demonstrated.
FIG. 2 is a block diagram showing the configuration of the prior reporting system 3. As shown in FIG. 2, the prior 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 F35 is connected by a bus 36.

  The CPU 31 executes various computer programs loaded in the RAM 33. Thereby, the computer 3 functions as the prior reporting system 3 of the present embodiment.

  The ROM 32 is configured by a mask ROM, a PROM (Programmable ROM), an EPROM (Erasable PROM), an EEPROM (Electrically Erasable PROM) or the like, and a computer program executed by the CPU 31 and data used for the execution. Is remembered.

  The RAM 33 is configured by SRAM, DRAM, or the like. The RAM 33 is used for reading various computer programs stored in the hard disk 34. Further, it is also used as a work area for the CPU 31 when the CPU 31 executes various computer programs.

  In the hard disk 34, various computer programs to be executed by the CPU 31, data used for executing the computer programs, and the like are installed in advance. The hard disk 34 also includes 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 in advance by each user. (DB) 34B, a store database (DB) 34C in which store information about each virtual store is stored, an unconditional history database (DB) 34D in which a history of transactions determined to be out of the range of use conditions is stored, An unauthorized use database (DB) 34E that stores unauthorized use information related to virtual stores and credit cards that may be used illegally, and a usage history database (DB) 34F that stores credit card usage history are provided. Yes. Details of these databases will be described later.

  In addition, a multitask operating system such as Windows (registered trademark) manufactured and sold by US Microsoft Co. is installed in the hard disk 34. In the following description, it is assumed that various computer programs operate on the operating system.

  The communication I / F 35 is an interface device for the advance reporting system 3 to communicate with an external device via the Internet 101. The prior reporting system 3 transmits / receives various data to / from the user terminals 4, 4,... And the store 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 a terminal ID for identifying the user terminal 4 used by the user, in addition to the user name, contact information, and card number of the credit card. This terminal ID is stored in the user DB 34A only when provided by each user.

(B) Usage condition DB 34B
FIG. 3 is a diagram illustrating an example of the layout of the use condition DB 34B. As shown in FIG. 3, the use condition DB 34B has at least a card number field 301, a period field 302, a frequency field 303, an amount field 304, a store field 305, a terminal field 306, an activation field 307, and a valid field 308. Yes.

  The card number field 301 stores the card number of each user's credit card. The period field 302, the number of times field 303, and the amount of money field 304 store a period during which the credit card can be used, an upper limit of the number of times, and an upper limit of the amount of money. The store field 305 stores a store ID for identifying a virtual store where a credit card can be used.

  The terminal field 306 stores information indicating whether or not the user terminal 4 that can be used by the user has been specified. In the present embodiment, “1” is stored in the terminal field 306 if it is specified, and “0” is stored if it is not specified. When the user performs 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 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 made, and “0” is stored in the activation field 307 when the association is not made. When the user performs this association, the credit card can be used only when the dedicated application is activated.

  The valid field 308 stores information indicating whether or not the set use conditions are valid. In this embodiment, “1” is stored in the valid field 308 when it is valid, and “0” is stored when it is invalid. When a credit card that satisfies the usage conditions is used, or when a set period has elapsed, the usage conditions are determined to be invalid, and “0” is stored in the valid field 308. Become.

(C) Store DB34C
In the store DB 34C, various information such as the name and contact information of the virtual store is stored in association with the store ID for identifying each virtual store.

(D) Unconditional history DB 34D
The unconditional history DB 34D stores an unconditional history that is a history of transactions that do not satisfy the use conditions, that is, transactions that are determined to be out of the range of use conditions. This out-of-condition history includes the card number of the credit card related to the transaction and the store ID of the virtual store.

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

(F) Usage history DB 34F
The usage history DB 34F stores usage history of credit cards by 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 prior declaration system 3 is configured by one computer. However, the present invention is not limited to this, and the prior declaration system 3 is configured by a distributed system including a plurality of computers. May be.

[Card payment system operation]
Next, the operation of the card payment system of the present embodiment configured as described above will be described with reference to a flowchart and the like. In the following, (1) Usage condition setting processing for setting usage conditions by user's advance declaration, (2) Card payment processing executed when credit card is used, (3) Possibility of unauthorized use Unauthorized use warning process to warn about, (4) Preliminary notice prompting process to encourage users to pre-declare usage conditions, and (5) Benefits given to each user when setting usage conditions Each process of the privilege information provision process for providing privilege information is demonstrated.

(1) Usage condition setting process Each user who uses a credit card in a virtual store can set usage conditions before using the credit card. Hereinafter, the use condition setting process executed when the setting is performed will be described.

  FIG. 4 is a flowchart showing the procedure of the use condition setting process. As shown in FIG. 4, first, the user terminal 4 transmits a use condition setting request to the advance reporting system 3 in accordance with an instruction received from the user (S101). This setting request includes information (such as a card number or a user identification ID) that can identify the user's credit card.

  When receiving a setting request from the user terminal 4 (S201), the prior declaration system 3 refers to the use condition DB 34B (S202), and uses the use condition setting screen related to the use condition setting screen for accepting the use condition setting. Information is generated (S203). Here, the prior declaration system 3 specifies the card number of the credit card based on the information included in the received setting request, and confirms whether or not the usage rule information relating to the card number exists in the usage rule DB 34B. . If the usage condition information exists, usage condition setting screen information including the usage condition information is generated in step S203. The prior declaration system 3 transmits the generated use 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 reporting system 3 (S102), the user terminal 4 displays the use condition setting screen on the display unit using the use condition setting screen information (S103).

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

  The user inputs a desired usage condition in the input field 1004 using the input unit provided in the user terminal 4. For example, when a user can use only a specific period, the period (any period such as daily unit or hour unit) can be used. When specifying a store, the store name is input, when specifying a usable terminal, that fact is input, and when making available only when the dedicated application is activated, that fact is input.

  When inputting the use 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. Each setting history is displayed in a selectable manner, and when a specific setting history is selected by the user, the same usage conditions as the setting history may be automatically input in the input field 1004. Good.

  After the usage conditions are input in this way, the user clicks a setting button 1005. Thereby, reception of the input of usage conditions is completed.

  When the user terminal 4 receives the input of the use condition as described above (S104), the user terminal 4 transmits the use condition input information including the use condition to the advance reporting system 3 (S105). When receiving the usage condition input information from the user terminal 4 (S205), the prior reporting system 3 registers each usage condition included in the usage condition input information in the usage condition DB 34B (S206), and ends the process. .

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

  In the above description, the authorization system 2 does not determine whether or not the usage conditions can be set, but such a determination may be made. Specifically, when pre-declared information is received from the pre-declaration system 3, the authorization system 2 confirms the contents of the pre-declared use conditions and the credit card is used within the range of the use conditions It is determined whether there is a shortage of usage limit balance. As a result, when it is determined that the usage limit amount is insufficient, the authorization system 2 determines that the usage conditions are not appropriate, and notifies the prior declaration system 3 to that effect. Upon receiving this notification, the prior reporting system 3 deletes the use condition from the use condition DB 34B. Thereby, it is possible to prevent an inappropriate usage condition from being set.

  Further, as described above, the authorization system 2 may determine whether or not the usage conditions are appropriate after setting the usage conditions by the prior filing system 3, but may make the determination before setting the usage conditions. Specifically, when the prior 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 that has received this is received. In the same manner as described above, the suitability of each use condition may be determined.

(2) Card payment processing When each user uses a credit card at a virtual store, 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 a purchase procedure for a product sold at the virtual store. Thereby, the user terminal 4 transmits the purchase request information specifying the product scheduled for purchase to the store server 5 (S301). This purchase request information includes the terminal ID of the user terminal 4 and information indicating that the access is made using a dedicated application.

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

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

  When it is determined in step S502 that the advance declaration of the use conditions has not been made (NO in S502), the authorization system 2 executes the authorization process in the same manner as a normal transaction (S503). As a result, when the use of the credit card is approved (YES in S504), the authorization system 2 can use the credit card after executing a predetermined settlement process such as processing as provisional sales (S505). The availability information indicating the presence is transmitted to the store server 5 (S506). On the other hand, when the use of the credit card is not approved (NO in S504), the authorization system 2 transmits the availability information indicating that the credit card cannot be used to the store server 5 (S506).

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

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

  When receiving the condition confirmation request from the authorization system 2 (S601), the prior declaration system 3 refers to the use condition DB 34B (S602), and determines whether or not the current use of the credit card satisfies the use condition (S602). S603). This determination differs depending on the set use conditions. For example, if the usage conditions are set for the period, number of times, amount of money, and virtual store, it is the same as the specified virtual store whether it is used within that period, or the upper limit of the number of times and amount is exceeded By confirming whether or not there is, it is determined whether or not the use condition is satisfied. If the terminal is specified according to the usage conditions, 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 are identified. By checking whether or not the terminal ID stored in the DB 34A matches, it is determined whether or not the use condition is satisfied. Furthermore, if the usage conditions are set to be available only when the dedicated application is activated, it is determined whether or not the dedicated application is executed from the purchase request information transmitted from the user terminal 4, and according to the result. It is determined whether or not the use conditions are satisfied.

  If it is determined in step S603 that the usage conditions are satisfied (YES in S603), the prior declaration system 3 can use a credit card after executing a predetermined settlement process such as processing as provisional sales (S604). Is transmitted 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 prior declaration system 3 registers the non-condition history in the non-condition history DB 34D (S605) and indicates that the credit card cannot be used. The permission information is transmitted to the authorization system 2 (S606).

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

  As described above, when there is no prior declaration of the use conditions, the authorization process is performed as usual, while when there is the prior declaration of the use conditions, the settlement can be performed without executing the authorization process. As a result, the number of authorization processes can be reduced.

  In addition, when there is a prior declaration of usage conditions, payment processing is performed only when the usage conditions are satisfied, and credit cards cannot be used when the usage conditions are not satisfied. It can be said that it is difficult for a third party other than the user who has made a prior declaration of the usage conditions to know that the usage conditions are normal, and therefore to make a transaction that satisfies the usage conditions. Therefore, unauthorized use by a third party can be prevented.

(3) Unauthorized use warning process As described above, when there is a transaction that does not satisfy the use conditions, the unconditional history is registered in the unconditional history DB 34D. The prior reporting 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 flowchart showing the procedure of unauthorized use warning processing. As shown in FIG. 7, the prior filing system 3 first refers to the unconditional history DB 34D (S701), and specifies a virtual store or a credit card in which the number of transactions not satisfying the use conditions is equal to or greater than a predetermined number (S702). .

  If it is used by a genuine user, it is rare to repeat transactions that do not satisfy the usage conditions, so it is possible to illegally use a credit card that has more than a predetermined number of transactions that do not satisfy the usage conditions It is considered that the nature is high. In addition, it can be said that there is a high possibility of unauthorized use in a virtual store where transactions that do not satisfy the use conditions are repeatedly performed. Therefore, the prior reporting system 3 determines that the virtual store or credit card specified in step S702 has a high possibility of unauthorized use, and uses the unauthorized use information including the store ID of the virtual store or the card number of the credit card. Registration in the unauthorized use DB 34E (S703).

  Next, the prior reporting system 3 generates warning information specifying a virtual store or a credit card with a high possibility of unauthorized use based on the unauthorized use information registered in the unauthorized use DB 34E (S704). Transmit (S705). This transmission destination is a person in charge who monitors unauthorized use, and warning information is transmitted to the person in charge using means such as e-mail. Thereby, this person in charge can grasp a virtual store or a credit card with high possibility of unauthorized use.

(4) Advance filing prompting process A user who has used a credit card in a virtual store with a high possibility of unauthorized use is likely to be involved in unauthorized use. In order not to be involved in such unauthorized use, it is preferable to declare the use conditions in advance. The prior declaration system 3 can prompt such a user to preliminarily declare the use conditions by executing the following preliminary declaration prompting process.

  FIG. 8 is a flowchart showing the procedure of the preliminary report prompting process. As shown in FIG. 8, the prior reporting system 3 first refers to the unauthorized use DB 34E and identifies a virtual store with a high possibility of unauthorized use (S801). Next, the prior declaration system 3 refers to the use history DB 34F, and specifies a credit card having a use record in the virtual store specified in step S801 (S802).

  Next, the prior declaration system 3 refers to the use condition DB 34B, and identifies, from among the credit cards identified in step S802, a credit card that has not been preliminarily declared for use conditions, that is, a card to be urged. (S803). Then, the advance declaration system 3 generates advance declaration prompting information for prompting advance declaration of use conditions (S804), and sends the advance declaration prompting information to the credit card user specified in step S803. Transmit (S805). This transmission is performed using e-mail or the like, for example.

  The user who has received the above advance report notification information can know that he / she may be involved in unauthorized use and that it is possible to make a prior declaration of the use conditions as a countermeasure. Advance declaration is promoted by pre-declaring the use conditions according to the preliminary declaration prompting information.

(5) Bonus information provision processing As described above, in the case of the present embodiment, it is not necessary to execute the authorization processing for the use of the credit card for which the usage conditions are set, so the number of authorization processing is reduced. Can do. Reducing the number of authorization processing leads to a reduction in system load, which is a great advantage for card companies operating the system, but not for credit card users. For this reason, in this embodiment, when advance reporting of usage conditions is made, a predetermined privilege such as an increase in usage points is given to the user. As a result, there is a merit for the user, so that advance declaration of the use condition is promoted. The following privilege information provision process is a process for notifying the user that a privilege is granted in that way.

  FIG. 9 is a flowchart showing a procedure of privilege information provision processing. As shown in FIG. 9, the prior declaration system 3 first refers to the user DB 34A and the usage condition DB 34B (S901), and is a credit card for which the usage conditions are not pre-declared, that is, a credit for which usage conditions are not set. A card is specified (S902).

  Next, the prior declaration system 3 generates privilege information indicating the content of the privilege given when the prior declaration of the use conditions is performed (S903), and the privilege information is identified in step S902. The data is transmitted to the card user (S904). This transmission is performed using e-mail or the like, for example.

  The user who has received the privilege information can know that the privilege can be obtained when the usage condition is reported in advance. Advance declaration is promoted by making a prior declaration of the use conditions in accordance with the privilege information.

  In addition, for example, when a special sale is carried out at a virtual store, the advance reporting system 3 obtains the schedule of the sale in advance from the virtual store side, and a credit card that has been used in the virtual store. The privilege information may be transmitted to the user. By making a prior declaration of the use conditions in accordance with this privilege information, it is possible to prevent the number of authorization processes from rapidly increasing during the sale period, and as a result, the load on the system can be reduced.

(Other embodiments)
In the above embodiment, the advance reporting system 3 has the usage condition DB, but the user terminal 4 that has made the preliminary reporting may have a similar database. In this case, when the credit card is used, that is, in the card payment process, the user terminal 4 transmits the usage conditions stored in the database to the advance reporting system 3 via the store server 5 and the authorization system 2. The prior declaration system 3 determines whether or not the use condition is satisfied in the same manner as in step S603 using the use condition transmitted in this way, and the subsequent processing is continued. Even in this case, as in the case of the above embodiment, if there is a prior declaration of the use conditions, it is possible to make a settlement without executing the authorization process, so that the number of authorization processes can be reduced. it can. As in the case of the above-described embodiment, the authorization system 2 determines whether or not usage conditions can be set, and is used for the database of the user terminal 4 only when it is determined that the usage conditions are appropriate. Conditions may be stored.

  In the above-described embodiment, the authorization system 2 and the prior declaration system 3 are configured as separate computer systems that are communicably connected to each other. However, the present invention is not limited to this. The authorization system 2 and the prior declaration system 3 may be realized by a computer system.

1 Card payment system 2 Authorization system 3 Prior declaration system 31 CPU
32 ROM
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)

In response to a request from a credit card user, usage condition setting means for setting usage conditions of the credit card in the virtual store,
A first determination means for determining whether or not a usage condition relating to the credit card is set when a credit card usage request is received;
Second determination means for determining whether or not the use of the credit card according to the use request satisfies the use condition when it is determined that the use condition is set;
Payment means for making payment without performing the credit card authorization process when it is determined that the use condition is satisfied, and disabling payment of the credit card when it is determined that the use condition is not satisfied; A card payment system. When it is determined that usage conditions are not set, the credit card authorization process is further performed, and a second settlement unit that performs settlement is further provided.
The card payment system according to claim 1. In response to a request from a credit card user, usage condition setting means for setting usage conditions of the credit card in the virtual store,
A second determination unit that determines whether or not the use of the credit card according to the use request satisfies the use condition according to the credit card when receiving the use request of the credit card;
Payment means for making payment without performing the credit card authorization process when it is determined that the use condition is satisfied, and disabling payment of the credit card when it is determined that the use condition is not satisfied; A card payment system. The usage condition setting means is configured to set a usage condition including at least one of a period, the number of times, and an amount of money that the credit card can be used.
The card payment system according to any one of claims 1 to 3. The use condition setting means is configured to set use conditions including a virtual store where a credit card can be used.
The card payment system according to any one of claims 1 to 4. The use condition setting means is configured to set a use condition including a communication terminal that can be used on a user side 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 a usage condition including presence or absence of execution of a specific program in a communication terminal on a user side of the credit card,
An 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 use condition is satisfied based on the execution presence / absence information.
The card payment system according to any one of claims 1 to 6. Number of times recording means for recording the number of times determined to not satisfy the use conditions for each virtual store,
Based on the number of times, a virtual store specifying means for specifying a virtual store that may be illegally used;
A warning output means for outputting a warning indicating that the identified virtual store may be illegally used;
The card payment system according to any one of claims 1 to 7. A user specifying means for specifying a user who has a use history in the specified virtual store;
A setting prompting means for urging the specified user to set credit card usage conditions at the specified virtual store;
The card payment system according to claim 8. For each credit card, a number recording means for recording the number of times determined not to satisfy the use conditions;
A credit card identifying means for identifying a credit card that may be illegally used based on the number of times;
A second warning output means for outputting a warning indicating that the identified credit card may be illegally used;
The card payment system according to any one of claims 1 to 9. Providing provision means for providing each user with privilege information given to the user when the use condition is set;
The card payment system according to any one of claims 1 to 10.

Images