JP2008305392A - Method for providing card settlement service, system for providing card settlement service, and computer program for causing computer system to execute card settlement service providing process - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enhance the security of cashless settlement by providing users with effective self-protective measures against information leakage. <P>SOLUTION: A method for providing users having accounts with a financial institution with a time-limited card settlement service comprises the processes of acquiring from a user terminal user information including account information, information on the expiration date of the card settlement service, and a part of a card number to receive an application for a service start (S4), performing authentication based on the acquired user information (S5), generating a unique card number including the acquired partial number (S6), storing card data including the generated card number and the expiration date in a card information storage part in association with the user information (S7), and sending the card data to the user terminal via a communication network to notify a use start of the card settlement service (S8). <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a server device managed by an issuer who issues a card having a settlement function to a user connected to a terminal device (user terminal) of a user who has an account with a financial institution via a communication network. The present invention relates to a method for providing a card payment service with an expiration date to the user, a system for providing a card payment service, and a computer program for causing a computer system to execute a card payment service providing process.

  Conventionally, debit card payment that immediately withdraws the price from the financial institution's account as one of the payment methods of the price (hereinafter collectively referred to as "product price") that the user purchased the product at the store and using the service Service is provided. In Japan, this debit card payment service is a service that enables cashless payment like a credit card by using a cash card issued by a financial institution and a personal identification number as they are. On the other hand, it is conceivable that the user may hesitate to debit card payment because there is a risk of information leakage if the same password as the bank account is input in an open space such as a store. Therefore, recently, it has been proposed and partially implemented to prevent information leakage by setting an expiration date on a debit card and inputting the expiration date instead of a password.

  In Europe and the United States, debit card payment services are often attached to credit cards so that users can choose between credit card payment (withdrawn at a later date) and debit card payment (with immediate debit) during payment. (Also called “check card”). Since this type is attached to the credit card, it can be said that an expiration date is also set for the debit card payment service. In Japan, some credit cards have a debit card function (such as regional bank cards).

  As described above, in the settlement by the debit card settlement service, the identity verification (authentication) is often performed by the number (credit card number or account number) written on the card and the expiration date (settlement information). The “debit card payment service” in this specification is a service that is provided with an existing card such as a cash card or a credit card, or is provided with a dedicated card and has an expiration date. Shall be pointed to.

  Such a debit card payment service is increasingly used for payment in online transactions using the Internet for the following reasons. That is, for the user, the procedure at the time of settlement is simple as with a credit card, and since it can be used only within the range of the account balance, overuse can be reliably prevented. In addition, for the business operator (virtual store operator), even when the business partner (user) is not visible, the payment can be quickly and reliably collected. Furthermore, for financial institutions and credit card companies (card issuers), it is expected that user services will be improved and usage fees will increase due to an increase in the number of member stores.

  For the settlement method using the debit card, for example, the following Patent Documents 1 to 3 are helpful.

JP 2002-288574 A JP 2003-157359 A JP 2004-5425 A

  However, in online transactions, payment information is transmitted and received over a network, so there is a risk of information leakage. Once information is leaked, it can only be dealt with by means such as reissuing cards or stopping services. This problem includes, for example, security information (several digits and symbols) written on the card medium and information that only the person knows (second PIN information: mother's oldness, pet name, etc.) as payment information Even so, it cannot be an effective solution. In addition, since the user often pays a part or all of the card reissue cost (several thousand yen), the user may hesitate to use it. In this regard, the present applicant distributes a token (one-time password generator) that issues a disposable password (OTP) at a period of about 60 seconds in synchronization with the host computer of the financial institution to the user. It has been put into practical use to verify the identity by using an account number. However, such a double authentication method using OTP is costly to distribute and manage tokens, and there are cases where tokens are lost or broken, so another measure to prevent fraud is desired.

  In particular, on the user side, in addition to general security measures such as physical management of card media and communication devices (PCs, mobile phones, etc.), monitoring of spyware, and checking against usage details, self- conduct of fraud due to information leakage There are no effective measures to defend.

  Such a problem is not unique to the debit card payment service, and the same can be said for credit cards, electronic money, and the like.

  The present invention has been made to solve such a problem, and provides an effective self-defense measure against information leakage when a user uses cashless payment by a debit card or the like. It is an object to provide a method, a system, and a program capable of promoting the use by improving security.

  According to the first main aspect of the present invention, a terminal device (user terminal) of a user having an account with a financial institution is connected via a communication network, and a card having a settlement function is issued to the user. A method of providing a card payment service with an expiration date to a user by a server device managed by an issuer, wherein the server device includes the account information from a user terminal via a communication network. Service start application acceptance process that receives information and information on the expiration date of the card payment service and accepts an application for service start, an authentication process that performs authentication based on the acquired user information, and when authentication is positive, Card data including a unique card number and the acquired expiration date are stored in the card information storage unit in association with the user information. A card data storage step, and a card data issuance step for sending the card data to a user terminal via a communication network to notify the start of use of the card payment service, and this method is preferably provided An executable system and a computer program for causing a computer system to execute the method are provided.

  According to the second main aspect of the present invention, a user terminal device (user terminal) having an account with a financial institution is connected via a communication network, and a card having a settlement function is provided to the user. A method for providing a card payment service with an expiration date to a user by a server device managed by an issuing issuer, wherein the server device receives the account information from a user terminal via a communication network. A service start application receiving process for receiving a service start application by acquiring an n-digit (n <N) number (user setting number) set by the user among the user information and the N-digit card number, and the acquired user An authentication process for performing authentication based on information, and an N-digit unique card number including the acquired user setting number and a predetermined expiration date if the authentication is positive Card data storage step of storing the card data including the card information in the card information storage unit in association with the user information, and transmitting the card data to the user terminal via the communication network to notify the start of use of the card payment service A card data issuing step, a system capable of suitably executing the method, and a computer program for causing a computer system to execute the method are provided.

  According to the present invention, a user who wishes to use a card payment service can freely set an expiration date of the service and a card number. Therefore, it is difficult to predict card information and the security can be improved as compared with the case where the card company sets a uniform expiration date and card number. Accordingly, when a user uses cashless payment using a debit card or the like, a method, system, and program that can provide effective self-defense measures against information leakage, improve security of cashless payment, and promote usage. Obtainable.

  In particular, by allowing the user to freely change the card information, for example, the expiration date can be changed when a possibility of leakage of information is found or at an arbitrary time. Thereby, even if the card information is leaked, the user himself / herself can disable the original card information. In addition, security can be improved by the user himself / herself by changing the card information regularly / irregularly.

  Further, the present invention is applicable not only to debit cards but also to card payment services that can be used for payment, such as credit cards and electronic money, with expiration dates set.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following, an example will be described in which the present invention is applied to a debit card payment service with an expiration date provided as part of a financial service to a customer (user) who has an account with a financial institution.

  The card payment service providing system denoted by reference numeral 1 in FIG. 1 is composed of one or more general-purpose or dedicated computer systems (server devices) provided in the financial institution 2, and is a well-known accounting system 3 or information system. 4 and a dedicated line in the row. A part of the functions of the system 1 can be provided in the accounting system 3 or the information system 4, or the system 1 can be configured by installing a later-described software program in the accounting system 3 or the information system 4. . Note that illustration and description of well-known system configurations such as a front-end server, a gateway server, a Web server, a firewall, and an ISP are omitted.

  The financial institution 2 is an online bank, a general bank having a real store, a post office, etc., and a card member store (virtual store / real store) 5 that provides online services such as online shopping on the Internet, and this member As a payment method with the user 6 who purchases a product at the store 5 or uses the service, the debit card payment service of this embodiment is provided to the user 6. In the following, an example will be described in which a user makes a debit card use application or various requests from a menu screen of net banking via the Internet.

  Therefore, the card payment service providing system 1 is a communication terminal 7 (PC, mobile phone, etc., hereinafter referred to as “user terminal”) of a user 6 who has an account in the financial institution 2 via a public line network such as the Internet. In addition to being connectable, it is possible to connect to the Web server and payment system of the member store 5 via a dedicated line or a public line.

  In the present embodiment, a dedicated card having a debit card settlement function and a credit card function is issued according to the desire of the user 6 who has an account at the financial institution 2. Generally, payment operations using a credit card or debit card are performed by a credit holder or a brand holder who owns an infrastructure for using a credit card, an issuer that issues a card to a user and manages card usage information (card issuer). ), Acquirers that acquire and supervise member stores (member store contractors and member store acquisition companies), and financial institutions that transfer funds between accounts (exchange business). Among these, the financial institution 2 of the present embodiment performs card issuing business in addition to the original exchange business.

That is, the card payment service providing system 1 of the present embodiment has the following functions.
(1) Issuance of cards (virtual and real)
(2) Management of cardholder (user with account) information (authentication, etc.)
(3) Card information management (update)
(4) Management of member store information (5) Settlement support

  Here, (4) the management of the member store information is an information management operation independently performed by the financial institution 2 in order to protect the customer information, unlike the member store management performed by the acquirer. Brand holders and acquirer operations, sales exchange fees paid by acquirers to card issuers, merchant fees paid by merchants to card issuers, royalties paid by card issuers to brand holders, and brands Various services provided by holders and card issuers to cardholders (enhancement: preferential discount services at member stores, provision of various information, overseas travel accident insurance, etc.) are well known in the art, and are illustrated and described in detail. Is omitted.

  In order to exhibit the above-described functions, the card settlement service providing system 1 of the present embodiment has a configuration as shown in the functional block diagram of FIG.

  In this system 1, as shown in FIG. 2A, a RAM 13, a ROM 14, an HDD 15, and an input / output interface (I / F) 16 are connected to a CPU 11 built in a computer system of a financial institution 2 via a system bus 12. Has been. The input / output I / F 16 is connected to an output device 19 such as an LED display 17 and a card writer 18, an input device 20 such as a keyboard and a mouse, and a communication device 21 such as a NIC. The external storage device such as the ROM 14 or the HDD 15 includes a data storage unit 23 and a program storage unit 24 as shown in FIG. Each of these storage units 23 and 24 is a fixed storage area secured in the external storage device (14, 15), information input / generated / calculated by each function of a software program described later, and the communication device The information acquired from the user terminal 7, the member store system, the brand holder management system, the information system 4, etc. via 21 is described and updated as needed.

  As shown in FIG. 2B, the data storage unit 23 includes a customer database (DB) 25, a member store information table 26, a card information storage unit 27, and a change history table 28.

  The customer DB 25 acquires a part of user information managed by the financial institution 2 from the information system 4 and stores it. Specifically, the account information (the book) of the user who holds an account at the financial institution 2 and who applied for an online payment service (hereinafter referred to as “the service”) using a debit card provided by the system 1. Branch information, account number, password, etc.) and login information (user ID and password) for the user terminal 7 to log in to the WEB server of the financial institution 2 are periodically acquired from the information system 4; It is stored in association with the customer code. The customer DB 25 can also use the existing customer DB in the information system 4 as it is.

  As shown in FIG. 3, the member store information table 26 stores information 29 of businesses that operate the member stores 5 in association with member company IDs 30 uniquely assigned by the financial institution 2. The company information 29 specifically includes the company name 29a, the industry 29b, the URL 29c of the virtual store that provides products and services on the WEB, the date 29d when the company information is registered in the system 1, and the examination. A flag 29e is included.

  Here, among the companies that can make online payments for merchandise, public institutions such as government agencies and local governments, public service providers such as electricity and gas, other general companies, small and medium enterprises, and individual business owners It seems that the information management system varies greatly depending on the factors. Therefore, the financial institution 2 providing this service, when registering a member store in the system 1, in order to prevent information leakage of the user 6, masks the company size, rating, encryption level of communication information, and card number. Judgment is made based on criteria such as the number of digits. This examination is preferably conducted by a systematic examination based on a fixed standard such as a company size, and then a second examination by the person in charge of the financial institution 2 individually. Then, “1” indicating that screening has been completed is registered in the column of the screening flag 29e for the business operator that has passed such preliminary screening. In the illustrated example, since the examination flag 29e is unregistered (examination has not been completed or registration is not permitted), the user of the member company ID: C222 has to register this company as a continuous use destination described later. I can't.

  As shown in FIG. 4, the card information storage unit 27 stores the debit card data 33 including the unique debit card number 34, the expiration date 35, and the member company ID 30 registered as the continuous use destination, the customer code 31 and the user The terminal 7 is stored in association with login information (user ID and password) 32 for connecting to the system 1. Here, in this embodiment, account information (main branch code + 10-digit number of account number) is set as the customer code 31, but the system 1 uniquely assigns it when opening an account or issuing debit card data. A unique ID (such as a credit card membership number) may be used.

The debit card number 34 is a card basic number 32a (n ₂ = 11) consisting of 1st to 8th digits + 13th to 15th digits, and 9 to 9 set by the user at the time of card payment service registration or change application. A 12-digit 4-digit user setting number 32b (n ₁ = 4) and a 16-digit check digit 32c are registered as a 16-digit number (N = 16). In this embodiment, since the 11-digit card basic number 32a is uniquely set, any number set by the user as the user setting number 32b or any number can be changed to a debit card. The uniqueness of number 34 is maintained.

  The card expiration date 35 can be freely set and changed by the user 6 on a monthly basis within a predetermined period such as 3 years or 5 years. In this embodiment, the card expiration date 35 is set to one year by default (for 12 months from the month following the date the card data registration date belongs), and the expiration date is registered as one year unless otherwise specified by the user 6. The

  In the present embodiment, as will be described later, a one-time card (second payment service: hereinafter referred to as “OTC”) that can be temporarily used only for transactions of a specific company is provided. For the card data registered as the OTC, the expiration date 36 and the available number of times 37 are also registered. In the OTC, for example, the available number of times may be set to 1 and the usage time limit may be fixed to 1 hour, or may be set by the user 6 within a predetermined range such as 3 times or 5 hours. In the former case, a symbol indicating OTC may be registered instead of the usage time limit or the number of times of use. In addition, when the number of available times is set to a plurality of times or when the user 6 is set, the available remaining number is registered and updated by subtracting the available remaining number one by one every time the card settlement is completed. .

  When the usage time limit of the OTC has passed or when the usage count has been reached, the usage time limit 36 and the usage count 37 are deleted and the card can be used as a normal debit card. Therefore, it is necessary to continuously manage the expiration date 35 of the card data for the card registered as the OTC. This OTC usage application can be made at any time other than when a debit card is newly issued or additionally issued. Further, it is preferable that the OTC is not used as a normal debit card within the usage period.

  The member company ID 30 is a member company of this service that has been subjected to member examination by the financial institution 2, that is, among the companies whose examination flag “1” is registered in the member company table 26 (FIG. 3). This is identification information of a business operator that the user 6 wishes to use this service as a means for continuous payment of the price (see FIGS. 10 and 11). With regard to the settlement of the commodity price charged to the user 6 every month from the company in which the member company ID 30 is registered, the transfer process is executed from the user's account even if there is no individual instruction from the user 6.

  The card medium issued flag 39 is registered in order to avoid duplicate issuance when the user 6 wishes to issue a dedicated debit card medium (real card) separately from the cash card or credit card. . The present invention provides a debit card payment service (virtual debit card) by issuing (notifying) the user 6 debit card data 33 associated with account information (customer code 30). In consideration of the characteristics, it is possible to issue a card medium similar to the conventional one.

  Here, in the present embodiment, the debit card data 33 (the user setting number 34b of the debit card number 34, the card expiration date 35 and the member company ID 30) can be changed in accordance with an instruction from the user 6, and therefore any one of the card data The number 40 of times the item is changed is also registered in the card information storage unit 27. The change data itself, the change date and time, etc. are stored in the change history table 28. Therefore, when authentication or card data is changed at the time of debit card payment, the card information storage unit 27 is first accessed to determine whether the number of changes 40 is 1 or more. If the number of changes 40 is 0, the process is executed according to the registered items at the time of initial setting in the card information storage unit 27. If the number of changes 40 is 1 or more, the change history table 28 is accessed to change the card data. The process is executed while referring to both the history and the registered items at the initial setting.

  As will be described later, in order to ensure security, the expiration date 35 is not allowed to be changed (returned) to “year / month” that has been set in the past. If it is a year, the possible number of changes is 60 times. On the other hand, there is no such limitation on the change of the card number 34, but in consideration of the burden of paperwork and the inability to settle due to the time lag between the change process and the payment process, the expiration date 35 and the total number of 60 times, It is preferable to provide a restriction such that the change condition is that one month or more has passed since the previous change date. Although the OTC expiration date 36 and the usable count 37 cannot be changed, the card data 33 can be changed before and after the OTC application, so the change count 40 is also registered as the total count before and after the OTC application. Is done.

  In the present embodiment, a plurality of debit card data 33 can be issued in association with one account information 30 (see serial Nos. 1 and 2 in FIG. 4). Thereby, for example, a plurality of debit cards such as a family card, a use purpose card, and a corporate card can be created and responded to a user's request to use them properly. As described above, in the present embodiment, since the 11-digit card basic number 34a is unique, a plurality of unique card numbers can be easily registered by changing the 4-digit user setting number 34b. In this embodiment, the number of card data 33 issued is limited to five in order to prevent card data management load and unauthorized use.

  As described above, when a plurality of debit card data are registered, the card data (expiration date, card number and member company ID) can be changed for each card data. Therefore, the card information storage unit 27 stores the debit card data 33 in association with not only the customer code (account information) 31 but also the login information 32 of the user 6. In the following description, the second and subsequent cards issued in association with the first issued debit card (first card) are collectively referred to as “second cards”.

  The change history table 28 stores the change history of the debit card data 33 in association with the login information 32 (identification information) of the user 6 who has accepted the change. Specifically, as shown in FIG. 5, for each debit card (login information 32), one record of the change data 41 such as the card number 34 'after the change and the expiration date 35', and the change date and time 42 thereof. Will be recorded sequentially. In the drawing, the change of the member company ID included in the change data 41 is omitted.

  As described above, in the present embodiment, a unique card basic number 34a is set for each customer code 31, and therefore, among the changed card numbers 34 ', the user 6 can change only the card basic number 34b'. With this change, the check digit 34c ′ is also changed.

  The number of records (changeable number of times) of such change history is set to about 60 at maximum per account (customer code 31) as described above. The change history record indicates that when the debit card data 33 is newly issued or changed, the issued / changed card number or expiration date is “card number after change” 34 ′ or “expiration date after change”. Those recorded in the item “35 ′” are generated. At this time, the change date and time field 42 of this record is blank, and the number of changes 40 in the card information storage unit 27 is zero. When the first change request is received from the user 6 at a later date, the change data 41 is overwritten, and the change date 42 and the change count 40 are recorded / updated. In the case of the second and subsequent change requests, a change history record is added. Note that a change history record may be added even when the first change request is received.

  Returning to FIG. 2, the program storage unit 26 is installed with a software program for realizing each function of the present invention. Each functional unit described later is an independent software program, its module, subroutine, component, and the like. When an external input from the user terminal 7 or the member store system is accepted or an operator of the financial institution 2 operates the input device 20 to input various commands (commands), the CPU 11 causes the software program to be stored in the work area of the RAM 13. It is loaded and executed, and performs the functions of the present invention in cooperation with the hardware and OS (operation system) described above.

  The software program includes service start application accepting means 45 (second card use application accepting means, use restriction information storing means, business registration application accepting means), authentication means 46, card data registering means 47 (card data storing means, Second card data storage means), card number generating means 48, card data issuing means 49, card data changing means 50 (card data change accepting means, card data updating means, discriminating means, uniqueness judging means, second card Data change accepting means, second card data updating means, login information updating means), change history registration means 51, and settlement processing means 52.

  The service start application accepting means 45 provides a transaction menu screen or the like (input interface: see FIG. 7 etc.) to the user terminal 7 via the communication network when login authentication is performed based on user information or the like. This input interface has a function of accepting various requests shown below.

(1) Debit Card Payment Service Start Application Accepting Function Obtaining the customer code 31 (user information), card payment service expiration date information 35, and a 4-digit user setting number 34b, and applying for service start It is a function to accept. In the present embodiment, a function of accepting an OTC in which the number of use times or a use time limit is limited is also provided.

(2) Function for accepting card medium issuance request This function accepts an issuance application for a dedicated card medium for a debit card settlement service, which is different from a cash card or a credit card, according to a user's request. You may make it issue as a dual-purpose card which embossed and printed the number of the debit card on the credit card or the cash card.

(3) Second Card Usage Application Reception Function The first card number 34 registered in the card information storage unit 27, the expiration date information 35 of the second card settlement service, and the card of the first card This is a function for acquiring the second user setting number 34b having a different number 34 and the user setting number 34b from the user terminal 7 and accepting the use application for the second card.

(4) Card usage restriction acceptance function For either the first or second card, the card data change authority, the second card issuance application authority, or the card usage limit within a predetermined period from a specific user terminal 7 This is a function for acquiring usage restriction information such as the amount, number of usages, usage limit per usage, etc., and storing it in the card information storage unit 27.

(5) Accepting function of member affiliated company The user terminal 6 obtains card data and customer code 31 (user information) and the ID of the affiliated company that the user wants to continuously use for the payment of the product price, This function accepts applications for member store continuation destination registration. As described above, stores (businesses) that can be registered as continuous use destinations are examined according to a predetermined standard.

  The authenticating means 46 confirms the identity of the user 6 and the authority when the service start application accepting means 45 accepts various requests from the user terminal 7. In this embodiment, the financial institution 2 performs user authentication using a device (token) distributed in advance to the user 6 when an account is opened. This token is a device that continuously generates a password (one-time password: OTP) with a predetermined algorithm in a short cycle such as one minute in synchronization with the host computer of the financial institution 2. When the authentication unit 46 receives a request to start a debit card payment service, the authentication unit 46 acquires the OTP displayed on the token from the user terminal 7 as user information, and the host computer (information system 4 or the like) generates it. Acquire OTP and verify both to authenticate. The authentication unit 46 may perform authentication at the time of login to the Web server or the like, and conversely, the Web server or the like may execute the authentication function of the present invention.

  In addition, when the authentication means 46 accepts an application for changing the validity period, a second card issuance / card information change application, etc., in addition to confirming the identity of the user 6 who applied for the change (OTP authentication) The card information storage unit 27 is also referred to to determine whether or not there is a change authority such as an expiration date. For example, in a family card or a corporate card, the right to change the card data for the second card may be granted only to a specific user (such as a householder or a senior employee). It is determined whether such change authority exists.

  The card data registration unit 47 stores the debit card number 34 including the first and second user setting numbers 34b acquired from the user terminal 7 and the debit card data 33 including the expiration date 35 as the customer code 31 (user information) and the login. The information is stored in the card information storage unit 27 in association with the information 32 (see FIG. 4). When the second card usage application is accepted, the second card data including the 11-digit unique second card number including the acquired second user setting number and a predetermined expiration date is stored in the second card data. 1 is stored in the card information storage unit 27 in association with the card number or user information. The second card data may be registered in association with the first card data so that the authority authentication or the like can be performed instantaneously.

  In addition, when receiving an application for the OTC from the user, the card information storage unit 27 has a function of storing the expiration date 36 and the available number of times 37 as card data. Further, when the service start application accepting means 45 accepts a member company registration application from the user terminal 7, the member company ID 30 is registered for the target card data 33.

  When the authentication by OTP is positive, the card number generation means 48 first generates a unique 11-digit card basic number 34a, and this card basic number 34a and the 4-digit user setting acquired from the user terminal 7 The number 34 b and the one-digit check digit 34 c are combined to generate a unique 16-digit card number 34 and register it in the card information storage unit 27. Note that an automatic setting button for the user setting number 34b may be prepared in the input interface for starting service use, and when this button is pressed, the card number generating means 48 may randomly generate the user setting number 34b. Further, when the user 6 can set only the expiration date and cannot set a card number (including a user setting number), the card number generation means 48 generates a 16-digit unique card number.

  The card data issuing means 49 transmits the card data to the user terminal 7 via a communication network to notify the start of use of the card payment service. Specifically, as shown in FIG. 7C, a WEB page including registered card data is generated and transmitted to the user terminal 7 and displayed on the display of the user terminal 7. Other communication means such as a user-dedicated page or electronic mail may be used, or registration information may be printed and mailed to the user's home. The card data issuing means 49 outputs the generated card data to the card writer 18 when the service start application accepting means 45 accepts a request for issuance of a card medium from the user 6. Has a function of recording card data. The card medium on which the card data is recorded is delivered to the user 6 by means such as mailing. Further, after outputting the card data to the card writer 18, “1” is recorded in the card medium issued flag 39 of the card information storage unit 27.

  The card data changing means 50 obtains change data (card number, expiration date, usable store ID, etc.) from the user terminal 7 for the card data (card number and expiration date) of the first and second cards, and applies for the change. A card data change application acceptance function for accepting changes in login information (login ID and password), and a card data update function for updating registered items in the card information storage unit 27 and customer DB 25 in accordance with the obtained change data. I have.

  Here, when changing the card data, only when the card number or the expiration date change data acquired from the user terminal 7 does not match any of the past card data registered in the change history table 28, The card data is updated based on the changed data (discriminating function). Thereby, illegal use based on past data leakage can be effectively prevented, and the user does not need to store past card data.

  Here, when the card number is changed, the user setting number 34b (4 digits) after the change is acquired. However, in this embodiment, the 11-digit card basic number 34a is unique. There is no need to determine the uniqueness of the card number (16 digits). In addition, when the number of changes reaches a predetermined number (for example, 60 times) or when a predetermined period (for example, one month) or more has not elapsed since the previous change, the update may not be permitted. If the card basic number 34a is not set and the automatic setting of the card number can be selected at the time of the application for changing the card data, the data changing means 50 provides 16 to the card number generating means 48. Instructs the generation of a unique card number of digits. In this case, it is preferable to update the card information storage unit 27 with the generated card number and register a changed flag in the card data.

  When the card data changing means 50 updates the card data for any of the first / second card data, the change history registration means 51 indicates the change date / time 42 and the change data 41 of the user 6 who applied for the change. The debit card data is recorded in the change history table 28 in association with the customer code 31 (account information), and 1 is added to the number of changes 40 (see FIG. 4) in the card information storage unit 27 for this debit card data. Here, when the second card data is updated, in addition to the customer code, the change history of the second card data is stored in association with the first card data. Thereby, the 1st card holder (a guardian, a manager employee, a manager, etc.) can know change history of the 2nd card data easily.

  The settlement processing means 52 transmits the amount information, the card data, and the information on the payment destination (member store code, etc.) (hereinafter collectively referred to as “settlement information”) transmitted from the member store system (communication device). When acquired, the account information of the user 6 associated with the card data is specified from the card information storage unit 27, and a message including the account information and the settlement information is generated to generate the account system 3 of the financial institution 2. Is to be transmitted. Since the payment information is created by a file transfer software for a credit card message such as HULFT (Host Unix Linkage File Transfer), for example, the payment processing means 52 has a function of reading a transmitted payment information file, The payment information and the account information are combined to generate a new credit card message. If the account system 3 that received the message can confirm whether the account balance of the user 6 is equal to or more than the price included in the message, as in ordinary debit card payment, the account is immediately debited from the user's account and the member store Notify the system of payment completion. In addition, a predetermined fee is deducted from the debited money and transferred to the member store account. This transfer process is not performed immediately but is executed at a predetermined cycle such as daily or monthly. When payment is made as a credit card, the payment processing means 52 immediately notifies the completion of payment if the account information of the user 6 can be confirmed based on the payment information file transmitted from the member store system. Settlement information including product price and user account information are transferred to acquirers and brand holders.

(flowchart)
Next, with reference to the flowcharts of FIGS. 6, 8, 10, and 13 and examples of screen transitions of FIGS. 7, 9, 11, 12, and 14, detailed functions of the system 1 will be described. This will be described together with the actual operation. Each processing step is executed when the login authentication of the user 6 is performed based on the login information 32 (S1) and the user's transaction selection is accepted from the transaction menu of the service in FIG. 7A (S2). ). Hereinafter, it demonstrates for every transaction classification.

(Processing process at the start of new use)
First, processing steps at the start of new use will be described with reference to FIGS. In the transaction menu of FIG. 7A displayed on the user terminal 7, when the user 6 clicks “start new use” (S3), the screen changes to a new registration screen of FIG. 7B. The service start application accepting means 45 acquires the 4-digit user setting number 34b (card number), expiration date information, and usage limit entered in each entry field on this screen to obtain the debit card payment service. An application for starting use is accepted (S4). At this time, a card medium issue application button (not shown) may be prepared to accept the application.

  Further, the authentication means 46 is activated, the token owned by the user 6 is specified from the customer DB 25 in accordance with the login information acquired from the user terminal 7 at the time of login, and the OTP input from the user terminal 7 and the host computer generate it. The validity of the request is confirmed by collating with OTP (S5). If the authentication is positive, the card data generation means 48 generates an 11-digit unique card basic number 34a, and the card basic number 34a, the user setting number 34b acquired from the user terminal 7 and the check digit 34c. The unique debit card number 34 is generated by synthesizing (S6). Then, a confirmation screen shown in FIG. 7C including the debit card number 34 and information such as the expiration date 35 and usage limit acquired from the user is generated and displayed on the user terminal 7. By pressing, these pieces of information are associated with the customer code 31 and stored in the card information storage unit 27 (S7). At the time of new issuance, the settable range of the expiration date (the range that can be selected by the user) is, for example, about 6 to 60 months.

  When the card data 33 is registered, the card data issuing means 49 displays a registration completion screen similar to that shown in FIG. 7C on the user terminal 7 (S8). Thereby, the user 6 can perform online shopping using the debit card data (virtual debit).

  Next, the change history registration means 51 newly generates an update history record for the card data in the change history table 28, and registers the card number 34 'and the expiration date 35' (S9). As described with reference to FIG. 5, the “change date / time” item 42 of the update history record remains blank until a card data change request is received at a later date.

  Here, in the transaction selection receiving step (S3), when the card medium issuance request is also received from the user terminal 7 (Yes in S10), the card data issuing means 49 sends the card data to the card writer 18. The data is output and recorded on the card medium (S11). The card medium on which the card data is recorded is sent to the registered address of the user registered in the information system 4 by a method such as registered mail (S12). Further, “1” is recorded in the card medium issued flag column 39 of the card information storage section 27 (S13).

(Processing process when changing card data)
Next, processing steps when changing card data will be described with reference to FIGS.
When the user 6 clicks “change card data” in the transaction menu of FIG. 7A displayed on the user terminal 7 (S14), the screen changes to the registered card list screen of FIG. 9A. This screen is common with “add card (application for use of second card)” described later.

  When the user 6 checks the card whose card data is to be changed on the screen of FIG. 9A and presses the “select” button (S15), the screen changes to the change data input screen of FIG. 9B. When the user inputs change data in each entry field on this screen and presses the “change” button, the card data change means 50 acquires the input change data (S16), and authentication by OTP is performed in the same manner as described above. (S17).

  If the authentication is positive, the card data changing means 50 accesses the change history table 28 to determine whether the change information related to the request matches the card data in the change history of the card data. (S18). If they do not match (No in S18), the card data changing means 50 updates the card information storage unit 27 with the changed card data (S19). When the card data is updated, the change history registration unit 51 updates the card information storage unit 27 by adding 1 to the number of changes 40 (S20), and changes to the change date / time column 42 of the change history table 28. The date and time are recorded (S21).

  Also, a new update history record is generated in the change history table 28 based on the updated card data 33 ', and the changed card number 34' and expiration date 35 'are registered (S22). The “change date / time” column 42 of this added record is blank.

Here, the expiration date that can be set by the user when the card data is changed needs to satisfy all of the following conditions, for example.
Condition 1: Must be a month after the month to which the change acceptance date belongs Condition 2: Must be 5 years or less from the initial setting date of the card Condition 3: The same date is not registered in the past change history This will be specifically described as follows.
・ Expiration date: January 5th, 2005. First card issued as December 2008. ・ Expiration date is 5 years maximum (until December 2010)
-After that, the expiration date is changed to October 2008, and then changed again to March 2010. In this case, when requesting the change of the expiration date in January 2007, from February 2007 to 2010 Of the years up to the month (Conditions 1 and 2), changes are allowed only for the months (Condition 3) excluding “October 2008” and “March 2010”.

  Finally, the card data issuing means 49 generates the screen of FIG. 9C including the updated debit card data (card number and expiration date) and transmits it to the user terminal 7 related to the request (S23). As a result, the user 6 can use the debit card after the change for online shopping and the debit card data before the change becomes invalid, so even if the card data is leaked, illegal use is effectively prevented. it can. In addition, since the card data can be changed at the user's intention regularly / irregularly, security can be further enhanced by the user's own information management.

  On the other hand, if it is determined in S18 that the card data matches with any of the card data in the change history (Yes in S18), an alarm is transmitted to the user terminal 7 to prompt re-input of the change data (S24).

(Processing process at the time of continuous use registration)
Next, with reference to FIG.10 and FIG.11, the process process at the time of continuous use destination registration is demonstrated.
When the user 6 clicks “continuous use destination registration” in the transaction menu of FIG. 7A displayed on the user terminal 7 (S24), the screen transitions to the registration card list screen of FIG. On this screen, for each card data, the ID of an already registered member store (operator) is displayed.

  When the user 6 checks 1 card data from this list and presses the “select” button (S25), the screen changes to the usage destination selection screen of FIG. On this screen, select one or more member companies that you want to register as continuous use destinations with the check box (S26), enter OTP and press the “Enter” button, and then go through the same OTP authentication as above ( In S27, the selected usage destination is registered in the card information storage unit 27 (S28). The user terminal 7 displays a registration completion screen shown in FIG.

(Processing process when adding a card)
Next, processing steps when adding a card will be described with reference to FIGS.
When the user 6 clicks “add card” in the transaction menu of FIG. 7A displayed on the user terminal 7 (S29), the service start application accepting means 45 is registered in the card information storage unit 27. It is determined whether the card data has reached the maximum value (whether it is less than 5) (S30). If the card data has not reached the maximum value (Yes in S30), the registration card list screen of FIG. Display. This screen is the same as that shown in FIG.

  When the user presses the “Add” button on this screen, the screen transitions to the screen of FIG. Even if any registered card is selected, the “add” button is preferentially processed. In the screen of FIG. 12 (B), the card information input by the service start application accepting means 45 is acquired (S31), and after the authentication by OTP (S32), the card data is additionally registered in the same way as at the start of new use. (S33). When the card data is added, the registration completion screen shown in FIG. 12C is displayed on the user terminal 7 (S34), and a record is added to the change history table 28 (S35).

  On the other hand, if it is determined in S30 that the registered number of card data has reached the maximum value (No in S30), a predetermined alarm message is output to the user terminal 7 and this process is terminated (S36). ).

(Processing process when issuing a one-time card)
Finally, the processing steps when issuing a one-time card will be described with reference to FIGS. In the following, an example in which card data for setting OTC is selected from already registered card data will be described. In addition to this, an OTC issuance application can be made at the start of the new use, when the card data is changed, or when the card is added.

  In the transaction menu of FIG. 7A displayed on the user terminal 7, when the user 6 clicks “issue one time card” (S37), the screen of the registered card list of FIG. 14A is displayed. On this screen, all card data associated with the user information 30 is displayed. When the user 6 checks the card data of 1 for which the OTC is to be set, inputs the OTP and presses the “apply” button (S38), the OTP authentication is performed by the authentication means 46 as described above (S39). If the authentication is positive, the service use start application accepting means 45 registers the use time limit 36 and the usable number of times 37 in the card information storage unit 27 (S40), and the OTC registration completion screen in FIG. Is generated and displayed on the user terminal 7.

  In the present embodiment, since the number of times of use and the use time limit are both fixedly set without accepting the user's setting, the OTC setting is completed only by the user 6's intention confirmation and OTP authentication. The user 6 inputs the OTC card data in the payment information input field of an arbitrary WEB site while displaying the registration completion screen of FIG. 14B or referring to the hard / soft copy of this screen. Since the usage time limit of OTC is a short time of about 1 hour, even if the card data is entered on the WEB site of a business operator with an insufficient information management system, there is no possibility of being misused by a third party.

  According to the above-described configuration, the user can freely select whether to start the debit card payment service, whether to issue the card medium, and the expiration date, so that the user can independently manage the card data and the expiration date is Compared with the conventional card payment service set uniformly, the risk of unauthorized use due to leakage of card data can be reduced.

  In addition, this invention is not limited to said embodiment, A various deformation | transformation is possible in the range which does not change the summary of invention.

  For example, in the above embodiment, an example of issuing debit card data (virtual debit) associated with an account of a financial institution has been described, but debit card data associated with a credit card, electronic money, prepaid card, or the like is issued. You can also Further, the virtual debit card according to the present invention can be used not only in the virtual store described above but also in an actual store. For example, you can enter your debit card number and expiration date on the numeric keypad for entering your PIN, and enter your identification data such as your PIN or login information as required, so that you can pay for it even if you do not have a card. Settlement is possible.

  Also, the card payment history information is stored in association with the debit card data (virtual debit) and the credit card number, respectively, and the card used to make the payment is specified in the monthly transaction details. Also good. Thereby, the user can grasp the timing when the price is withdrawn from the account, and can selectively use the two types of cards depending on the purpose, balance, and the like.

  Furthermore, in the above embodiment, the uniqueness is ensured by the 11-digit card basic number 34a. However, the card basic number is not set, and the number of digits of the card number (1 to (N-1) digits) is set by the user. Can be freely set, the card information storage unit 37 is referred to determine the uniqueness of the acquired card number. In this case, it is necessary to determine uniqueness when changing the card number.

FIG. 1 is a network configuration diagram of an embodiment of the present invention. FIG. 2 is a functional block diagram showing a schematic configuration of the card payment service providing system. FIG. 3 is a diagram illustrating a data configuration of the member store information table. FIG. 4 is a diagram illustrating a data configuration of the card information storage unit. FIG. 5 is a diagram illustrating a data configuration of the change history table. FIG. 6 is a flowchart showing processing steps when issuing card data. FIG. 7 is a diagram schematically showing an example of screen transition when issuing card data. FIG. 8 is a flowchart showing processing steps when updating card data. FIG. 9 is a diagram schematically illustrating an example of screen transition when card data is updated. FIG. 10 is a flowchart showing processing steps at the time of continuous use destination registration and card data additional registration. FIG. 11 is a diagram schematically illustrating an example of screen transition at the time of continuous use destination registration. FIG. 12 is a diagram schematically illustrating an example of screen transition at the time of card data additional registration. FIG. 13 is a flowchart showing processing steps during one-time card registration. FIG. 14 is a diagram schematically illustrating an example of screen transition at the time of one-time card registration.

Explanation of symbols

1 ... Card payment service provision system 2 ... Financial institution 3 ... Account system 4 ... Information system 5 ... Card member store (operator)
6 ... User 7 ... User terminal 11 ... CPU
12 ... System bus 13 ... RAM
14 ... ROM
15 ... HDD
16 ... I / O interface (I / F)
DESCRIPTION OF SYMBOLS 17 ... Display 18 ... Card writer 19 ... Output device 20 ... Input device 21 ... Communication device 23 ... Data storage part 24 ... Program storage part 25 ... Customer database (DB)
26 ... Member store information table 27 ... Card information storage unit 28 ... Change history table 29 ... Company information 30 ... Member company ID
31 ... Account information (customer code)
32 ... Login information 33 ... Card data 34 ... Debit card number 34a ... Card basic number 34b ... User setting number 34c ... Check digit 35 ... Expiration date 36 ... Expiration date 37 ... Usable count 39 ... Card medium issued flag 40 ... Card Number of data changes 42 ... Date and time of change 45 ... Service start application acceptance means 46 ... Authentication means 47 ... Card data registration means 48 ... Card number generation means 49 ... Card data issue means 50 ... Card data change means 51 ... Change history registration means 52 ... Payment processing means

Claims (23)

A terminal device (user terminal) of a user who has an account at a financial institution is connected to the user by a server device managed by an issuer that issues a card having a settlement function to the user. Providing a card payment service with an expiration date,
The server device is
From a user terminal, via a communication network, a service start application accepting step of obtaining user information including the account information and information on the expiration date of the card payment service and accepting an application for service start;
An authentication step of performing authentication based on the acquired user information;
A card data storage step of storing card data including a unique card number and the acquired expiration date in the card information storage unit in association with the user information when authentication is positive;
A card data issuing step of transmitting the card data to a user terminal via a communication network and notifying the start of use of a card payment service. A terminal device (user terminal) of a user who has an account at a financial institution is connected to the user by a server device managed by an issuer that issues a card having a settlement function to the user. Providing a card payment service with an expiration date,
The server device is
From the user terminal, the user information including the account information and the n-digit (n <N) number (user setting number) set by the user out of the N-digit card number are acquired via the communication network and the service is started. A service start application acceptance process for accepting applications,
An authentication step of performing authentication based on the acquired user information;
Card data storage for storing card data including an N-digit unique card number including the acquired user setting number and a predetermined expiration date in the card information storage unit in association with the user information when authentication is positive Process,
A card data issuing step of transmitting the card data to a user terminal via a communication network and notifying the start of use of a card payment service. The method of claim 2, wherein
Further, the server device includes a card number generation step of generating a unique N-digit card number by combining a unique Nn-digit card basic number and the user setting number,
The card data storing step stores the generated N-digit card number in a card information storage unit. The method of claim 1 or 2,
Furthermore, the server device
From the user terminal, through the communication network, the user information, the changed n ₁ (n ₁ <N) digit number and / or the changed expiration date (hereinafter collectively referred to as “change data”). A card data change acceptance process for obtaining and accepting card data changes;
A card data updating step of updating the card data in the card information storage unit based on the received change data. The method of claim 4, wherein
The card data change accepting step receives the changed user setting number as an n ₁ digit number after the change (n = n ₁ ) and accepts the change of the card number. The method of claim 4, wherein
Furthermore, the server device
A change history storage step of storing the change history of the card data updated in the card data update step in a card information storage unit;
A determination step of determining whether the change data received in the card data change reception step matches the card data at the time of initial registration stored in the change history storage unit or the card data in the change history. ,
The card data update step updates the card data based on the received change data when it is determined in the determination step that the card data does not match the past card data. The method of claim 6 wherein:
The customer DB stores a plurality of user identification information as user information in association with account information,
The card data change acceptance step is to acquire any user identification information among a plurality of user identification information,
The card information storage unit stores a change history of card data in association with the acquired user identification information. The method of claim 4, wherein
The card data change receiving step, determining when receiving a change card number, by referring to the card information storage section, whether or N-digit card number is unique including the acquired n ₁ digit card number Comprising the steps of:
The card data updating step updates the card number in the card information storage unit when the card number after the change is unique and registers a changed flag in the card data. The method of claim 1, wherein
Furthermore, the server device
Obtaining the user information and / or the card number registered in the card information storage unit (first card number) and the expiration date of the second card settlement service from the user terminal via the communication network A second card use application acceptance process for accepting a second card use application;
When the authentication in the authentication step is affirmative, the second card data including a unique card number and the acquired expiration date is stored in the card information in association with the first card number and / or user information. And a second card data storing step for storing in the card. The method of claim 2, wherein
Furthermore, the server device
The card number (first card number) registered in the user information and / or card information storage unit from the user terminal via the communication network, and the card number of the first card and n ₂ (n ₂ <N ) A second card use application receiving step of acquiring a second user setting number with a different digit number and receiving a second card use application;
If authentication in the authentication step is positive, second card data including an N-digit unique second card number including the acquired second user setting number and a predetermined expiration date is stored in the first card data. A second card data storage step of storing in the card information storage unit in association with the card number and / or user information of
The said authentication process performs authentication based on the said acquired user information or card number. The method of claim 9 or 10, wherein
Further, the server device has the right to change the card data, the right to apply for the use of a new card, the card usage limit amount and the number of times of use, once for either the first card data or the second card data. A method comprising a use restriction information storing step of storing use restriction information such as a per capita use limit in a card information storage unit. The method of claim 9 or 10, wherein
Furthermore, the server device
For the second card data registered in the card information storage unit from the user terminal via the communication network, the second user setting number after change and / or the expiration date after change (hereinafter referred to as “change data”). And a second card data change accepting step of accepting a change of the second card data,
A second card data update step of updating the second card data in the card information storage unit based on the received change data;
A change history storing step of storing the updated change history of the second card data in association with the first card data in the card information storage unit. The method of claim 1 or 2,
The service start application acceptance step is to accept a card medium issuance request from the user terminal in addition to the issuance of card data,
The card data issuing step outputs the generated card data to a card writer connected to the server device and records the card data on the card medium when a card medium issuance request is received. A method characterized by. The method of claim 1 or 2,
The customer DB stores, as user information, login information for a user terminal to log in to a WEB server of a financial institution in association with account information,
In the card data storage step, the generated card data is associated with login information and stored in a card information storage unit,
The method further comprises a login information update step in which the server device receives a login information change application from a user terminal and updates the customer DB. The method of claim 1 or 2,
The card data is debit card data in which the price of the product purchased by the user or the usage fee of the service used by the user (hereinafter collectively referred to as “price”) is immediately debited and settled from the user's account,
In this method, the server device further acquires the price information, the card data, and the payment destination information (hereinafter collectively referred to as “settlement information”) transmitted from the communication device of the card member company. In this case, the account information of the user associated with the card data is specified from the card information storage unit, and a message including the account information and the payment information is generated and transmitted to the account host of the financial institution. A method comprising a processing step. The method of claim 1 or 2,
The service start application accepting step selectively accepts, from a user terminal, a use application for a first card settlement service with a limited number of uses and a second card settlement service with a limited number of uses,
In the card data storage step, when the selection of the first card payment service is received, information for identifying the service type of the first card payment service and / or the number of times of use as the card data is stored in the card information storage unit. The method characterized by storing in. The method of claim 16, wherein
The service start application accepting step is for obtaining information on the number of times of use as card data from the user terminal and accepting a use application for the first card payment service,
The card data storing step stores the acquired number of uses in the card information storage unit. The method of claim 16, wherein
The service start application accepting step obtains card data registered in the card information storage unit from the user terminal and information on member companies that the user wants to use for payment, and applies for use of the first card payment service. Is to accept,
The card data storage step stores, in the card information storage unit, information for identifying the service type of the first card payment service and / or the number of times of use and member company information for the acquired card data. A method characterized by. The method of claim 1 or 2,
Furthermore, the server device receives card data and / or user information from the user terminal and information on member companies that the user wants to use for payment, and accepts a company registration application. With a process,
The card data storage step stores the acquired member company information as card data in the card information storage unit. A terminal device (user terminal) of a user who has an account with a financial institution is connected via a communication network, and includes a server device managed by an issuer that issues a card having a settlement function to the user. A system for providing a card payment service with an expiration date,
A customer database (DB) for storing user information including information on the account;
A service start application receiving means for providing an input interface to the user terminal via the communication network, acquiring user information and service expiration information, and receiving a service start application;
An authentication means for performing authentication based on the acquired user information;
Card information storage means for storing card data including a unique card number and the acquired expiration date in a storage device of a server device in association with the user information when authentication is positive;
A card data issuing means for transmitting the card data to a user terminal via a communication network and notifying the start of use of the card payment service. A terminal device (user terminal) of a user who has an account with a financial institution is connected via a communication network, and includes a server device managed by an issuer that issues a card having a settlement function to the user. A system for providing a card payment service with an expiration date,
A customer database (DB) for storing user information including information on the account;
Provides an input interface to the user terminal via the communication network, and obtains user information and an n-digit (n <N) number (user setting number) set by the user from the N-digit card number and starts the service. A service start application acceptance means for accepting an application,
An authentication means for performing authentication based on the acquired user information;
Card information for storing card data including an N-digit unique card number including the acquired user setting number and a predetermined expiration date in a storage device of the server device in association with the user information when authentication is positive Storage means;
A card data issuing means for transmitting the card data to a user terminal via a communication network and notifying the start of use of the card payment service. A terminal device (user terminal) of a user who has an account with a financial institution is connected via a communication network, and a computer system managed by an issuer that issues a card having a settlement function to the user is connected to the user. And a computer program for executing a process for providing a card payment service with an expiration date,
In the computer system,
From a user terminal, via a communication network, a service start application accepting step of obtaining user information including the account information and information on the expiration date of the card payment service and accepting an application for service start;
An authentication step of performing authentication based on the acquired user information;
A card data storage step of storing card data including a unique card number and the acquired expiration date in the card information storage unit in association with the user information when authentication is positive;
A computer program for executing a card data issuing step of transmitting the card data to a user terminal via a communication network and notifying the start of use of a card payment service. A terminal device (user terminal) of a user who has an account with a financial institution is connected via a communication network, and a computer system managed by an issuer that issues a card having a settlement function to the user is connected to the user. And a computer program for executing a process for providing a card payment service with an expiration date,
In the computer system,
From the user terminal, the user information including the account information and the n-digit (n <N) number (user setting number) set by the user out of the N-digit card number are acquired via the communication network and the service is started. A service start application acceptance process for accepting applications,
An authentication step of performing authentication based on the acquired user information;
Card data storage for storing card data including an N-digit unique card number including the acquired user setting number and a predetermined expiration date in the card information storage unit in association with the user information when authentication is positive Process,
A computer program for executing a card data issuing step of transmitting the card data to a user terminal via a communication network and notifying the start of use of a card payment service.

Images