JP2008176361A - Card settlement system, card settlement program, and card settlement method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To promote the use of a card by simplifying card payment in the common payment of a plurality of users. <P>SOLUTION: This card settlement system is provided with: a shared card use information acquisition part 301 for acquiring information relating to the use of a shared card 300; a user information acquisition part 302 for acquiring information relating to the plurality of users of the shared card 300 from a user information database 103a in which information about a plurality of users registered when issuing the shared card 300 is stored; a claim information generation part 303 for generating the claim information of each user acquired by the user information acquisition part 302 on the basis of the information acquired by the shared card use information acquisition part 301; and a claim processing part 304 for performing claim processing for each user on the basis of the generated claim information. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a card payment system that uses a card for payment for purchase of goods or services, a card payment program that is executed by the card payment system, and payment for purchase of goods or services using the card. It is related with the card settlement method performed using.

  Conventionally, a card such as a credit card or a debit card is issued for each individual, and in principle, card lending and borrowing is prohibited. Accordingly, those who do not own the card cannot purchase goods or services using the card. Currently, a card is not issued to a person who has not reached a predetermined age or does not obtain a predetermined income. Exceptionally, so-called family cards are issued to families with one household or one settlement account.

  Further, conventionally, when a group of a plurality of people act together (for example, travel), there is a cost that is incurred in common. For example, the cost of gasoline or highway when moving by car. The usual practice is so-called “split”, in which one of the members of the group changes it and splits it later. As the number of turnovers increases, the management becomes complicated, and it can be confusing by not knowing who changed what.

  Therefore, a predetermined amount of “cash” is collected from the members in advance, and the cash is shared with a member other than the personal wallet in a shared wallet, the so-called “mom wallet”. After the payment, the remaining balance in the mom wallet will be returned to each member in half. By doing so, the management of the advance payment is not complicated, and the above confusion can be easily avoided.

  Moreover, as a conventional technique, after a card user pays a card, there is a great need for a third party to pay part or all of the payment on behalf of the card user. In view of this, when making payments to the provider side, payment processing is performed on the representative's card, and then split payments are made to the payment splitting target person from the settlement company server including the credit card company via the network. Some of them present information for executing the payment process (see, for example, Patent Document 1 below).

JP 2004-280318 A

  However, the “mom wallet” that has been conventionally used is suitable for payment by cash, but cannot be applied to settlement using a card. Moreover, even in the prior art of the above-mentioned Patent Document 1, there is a problem that the payment procedure such as presenting all the users' cards is complicated and the use of the cards cannot be promoted.

  In particular, instead of cash payments, card payments have been increasing recently. Card payments are often more rewarding than cash payments. Cards are also used for common payments as described above. There are many requests to do. In addition, it is an important issue from the viewpoint of promoting the use of cards to give a privilege by card payment equally to use members.

  In order to solve the above-described problems caused by the prior art, the present invention provides a card settlement system and a card settlement that can facilitate the use of a card by facilitating the card payment in the common payment of a plurality of users. An object is to provide a program and a card payment method.

  In order to solve the above-described problems and achieve the object, a card payment system according to the present invention is a card payment system that uses a card to make a payment for the purchase of goods or services. Shared card usage information acquisition means for acquiring information related to usage of a card shared by the user (hereinafter referred to as “shared card”), and user information for storing information related to a plurality of users registered when the shared card is issued User information acquisition means for acquiring information on a plurality of users of the shared card from the database, and usage acquired by the user information acquisition means based on information acquired by the shared card usage information acquisition means Billing information generating means for generating billing information for each person, and the billing information generating means And billing means for performing a billing process for each user based on the billing information, characterized by comprising a.

  In the card payment system according to the present invention, in the above invention, the billing information generation means is a user acquired by the user information acquisition means based on information acquired by the shared card use information acquisition means. The billing information is generated so that the billing amount is equal to each other, or the billing amount is determined in proportion to each user.

  The card payment system according to the present invention is the card payment system according to the present invention, wherein the personal card use information acquisition means for acquiring information related to the use of the individual card owned by at least one of the users, and the personal card Usage limit determining means for determining the usage limit of the shared card based on the information acquired by the usage information acquiring means.

  Further, in the card payment system according to the present invention, in the above invention, the claim processing means, when the user owns the user's personal card, the user's personal card of the usage amount. If the user does not own the user's personal card, a billing process for the amount of usage for the user (based on the bill, the bank It is characterized in that it is a transfer process from a bank account or a withdrawal process from a bank account.

  In the card payment system according to the present invention, in the above-mentioned invention, the points given in correspondence with the use of the shared card based on the information acquired by the shared card use information acquiring means are assigned to the individual user. Point calculating means for calculating for each card, and point giving processing means for giving the points calculated by the point calculating means to the individual card of the user.

  A card payment program according to the present invention is a card payment program that causes a card payment system that uses a card to make a payment for purchase of goods or services, wherein the card payment system includes a plurality of the cards. Shared card usage information acquisition step for acquiring information related to use of a card shared by the user (hereinafter referred to as “shared card”), and user information for storing information related to a plurality of users registered when the shared card is issued A user information acquisition step for acquiring information on a plurality of users of the shared card from the database, and a usage acquired by the user information acquisition step based on the information acquired by the shared card usage information acquisition step. A billing information generation step for generating billing information for each person, and the billing information generation A billing step of executing billing processing for each user based on the billing information generated by the process, characterized in that for the execution.

  The card payment method according to the present invention is a card payment method in which payment for purchase of goods or services is performed using a card using a card payment system, and the card payment system includes a plurality of the cards. A shared card usage information acquisition step for acquiring information related to the use of a card shared by a user (hereinafter referred to as “shared card”), and a user for storing information related to a plurality of users registered when the shared card is issued Obtained from the information database based on the user information obtaining step for obtaining information on a plurality of users of the shared card and the information obtained by the shared card use information obtaining step. A billing information generation step for generating billing information for each user and the billing information generation step And billing process performed were performed billing for each user based on the billing information, characterized in that the run.

  According to the present invention, since a shared card of all users can be issued and paid using the shared card, the payment process is completed in exactly the same procedure as a normal personal card. Thereby, the card payment in the common payment of a plurality of users can be facilitated, and the use of the card can be promoted.

  Exemplary embodiments of a card payment system, a card payment program, and a card payment method according to the present invention will be explained below in detail with reference to the accompanying drawings.

(System overview)
First, an overview of the entire system including the card payment system according to the present invention will be described. FIG. 1 is a block diagram showing an outline of the entire system according to the embodiment of the present invention. In FIG. 1, the entire system includes a card payment system 101, store terminals 102 (102a, 102b, 102c), various DBs (databases) 103, and user terminals 104, each of which includes a network 100. Connected by.

  The network 100 connects each of the component devices 101 to 104 described above. Specifically, the network 100 includes a wide range of devices capable of transmitting and receiving data, such as the Internet, a LAN, and a general public line.

  The card payment system 101 controls the entire system and manages payment processing using a card. Details regarding the payment processing by card will be described later.

  The store terminal 102 includes store terminals 102a, 102b, 102c,... Provided in a plurality of stores. Specifically, the store terminals 102a, 102b, and 102c realize their functions by a card reader or the like.

  Specifically, the various DBs 103 include DBs such as a user information DB 103a, a shared card information DB 103b, a personal card information DB 103c, and a sales information DB 103d shown in FIG. Each DB may be managed by the same server or may be managed by different servers.

  The user information DB 103a is a database that stores information related to card users. Specifically, for example, for each shared card 300, information on the registered member registered to use the shared card 300, whether or not the used member owns the personal card 350, and how to use it Information regarding the ownership of various types of cards (general cards, gold cards, family cards, etc.), information regarding payment methods for the shared card 300, other details regarding the items described in the card application form, shared card 300 Various types of information related to members in use, including information on other members registered at the time of issuance, are stored.

  The shared card information DB 103 b is a database that accumulates information related to the usage status of the shared card 300. Specifically, the usage status information is information necessary for settlement using the shared card 300, such as the date and time when the shared card 300 was used, the store, the usage amount, and the contents of the purchased product (service).

  The personal card information DB 103c is a database that accumulates information related to the usage status of the personal card 350. Specifically, the usage status information is information necessary for settlement by the personal card 350, such as the date and time when the personal card 350 was used, the store, the usage amount, and the contents of the purchased product (service).

  The sales information DB 103d is a database for accumulating information relating to sales of the card company shown in FIGS. The sales information is information relating to all card sales including the shared card 300 and the personal card 350.

  The user terminal 104 is an electronic device such as a personal computer, a mobile phone, or a PDA owned by the user, and is connected to the network 100. From the user terminal 104, it is possible to make an online application for the shared card 300, and it is also possible to perform online shopping using the issued shared card 300. Internet shopping can be used when all users purchase common products and services. For example, it is effective when all users purchase bouquets and gifts using online shopping.

(Hardware configuration of card payment system)
FIG. 2 is a block diagram showing a hardware configuration of the card settlement system according to the embodiment of the present invention. In FIG. 2, the card payment system 101 includes, for example, a CPU 201, a RAM 202, a ROM 203, an HDD (hard disk drive) 204, an HD (hard disk) 205, an FDD (flexible disk drive) 206, and a removable recording. An FD (flexible disk) 207 as an example of a medium, a display 208, an I / F (interface) 209, a keyboard 210, a mouse 211, a scanner 212, and a printer 213 are provided. The components 201 to 213 are connected by a bus 200.

  The CPU 201 governs overall control of the card payment system 101. The RAM 202 is used as a work area for the CPU 201. The ROM 203 stores a program such as a boot program. The HDD 204 controls data read / write with respect to the HD 205 according to the control of the CPU 201. The HD 205 stores data written under the control of the HDD 204.

  The FDD 206 controls reading / writing of data with respect to the FD 207 according to the control of the CPU 201. The FD 207 stores data written under the control of the FDD 206 or causes the information processing apparatus to read data recorded on the FD 207. In addition to the FD 207, the removable recording medium may be a CD-ROM (CD-R, CD-RW), MO, DVD (Digital Versatile Disk), memory card, or the like. A display 208 displays data such as documents, images, and function information. For example, in addition to a TFT liquid crystal display, a CRT or a plasma display may be used.

  The I / F (interface) 209 is connected to the network 100 through a communication line, and is connected to the store terminal 102, various DBs 103, the user terminal 104, and the like via the network 100. The I / F 209 controls an interface between the network 100 and the inside of the apparatus, and controls data input / output from the store terminal 102, various DBs 103, the user terminal 104, and the like. The I / F 209 is, for example, a modem or a LAN adapter. The I / F 209 can also be used as an external input / output such as a USB.

  A pointing device such as a keyboard 210 and a mouse 211 is used for inputting / setting various data. The scanner 212 optically reads image information. It also has a function to read barcodes, digital watermarks, and the like. In addition to the scanner device, the scanner 212 may be a digital still camera, a digital video camera, or the like that can optically read an image. The printer 213 prints image information and other information. For example, a laser beam printer, an ink jet printer, a thermal printer, an impact printer, or the like.

(Functional configuration of card payment system)
Next, a functional configuration of the card settlement system will be described. FIG. 3 is a block diagram showing an example of a functional configuration of the card settlement system according to the embodiment of the present invention. In FIG. 3, 300 is a shared card (mom wallet card), and 350 is a personal card. The personal card 350 is a general card owned by the individual member.

  Also, the card payment system 101 according to the present embodiment includes a shared card usage information acquisition unit 301, a user information acquisition unit 302, a billing information generation unit 303, a billing processing unit 304, a point calculation unit 305, The configuration includes a point information DB (database) 306, a point grant processing unit 307, a personal card usage information acquisition unit 308, and a usage limit determining unit 309.

  The shared card usage information acquisition unit 301 acquires, from the shared card information DB 103b, information related to the usage of the shared card 300, which is a card shared by a plurality of usage members, and stores the predetermined information in the card payment system (computer) 101. The data is stored in an area (specifically, for example, RAM 202, ROM 203, HD 205, FD 207, etc. shown in FIG. 2). Specifically, the shared card usage information acquisition unit 301 functions by the CPU 201 executing a program stored in the RAM 202, the ROM 203, the HD 205, the FD 207, or the like, for example, by the I / F 209 illustrated in FIG. Realize.

  The user information acquisition unit 302 stores a plurality of usage members of the shared card 300 (specifically, a diagram to be described later) from the user information database 103a that stores information related to the plurality of usage members registered when the shared card 300 is issued. 9, information about each member (Mr. A, M, B) of the user group 901 shown in FIG. 10 is acquired, and a predetermined storage area (specifically, for example, FIG. RAM 202, ROM 203, HD 205, FD 207, etc. shown in FIG. Specifically, the user information acquisition unit 302 realizes its function by the CPU 201 executing a program stored in the RAM 202, ROM 203, HD 205, FD 207, or the like, for example, by the I / F 209 shown in FIG. To do.

  The billing information generation unit 303 reads the shared card usage information acquired by the shared card usage information acquisition unit 301 and stored in a predetermined storage area. Similarly, user information acquired by the user information acquisition unit 302 and stored in a predetermined storage area is read. Similarly, the billing information for each utilization member in the user information read out (that is, each member (Mr. A, Mr. B, Mr. C) of the user group 901 shown in FIGS. 9 and 10 in the above example)). And generated based on the read shared card usage information. The generated billing information is stored in a predetermined storage area of the card payment system (computer) 101 (specifically, for example, the RAM 202, ROM 203, HD 205, FD 207, etc. shown in FIG. 2). Specifically, the billing information generation unit 303 realizes its function when the CPU 201 executes a program stored in the RAM 202, the ROM 203, the HD 205, the FD 207, or the like shown in FIG.

  At that time, based on the information acquired by the shared card usage information acquisition unit 301 and stored in the predetermined storage area, the usage information acquired by the user information acquisition unit 302 and stored in the predetermined storage area (that is, In the above example, Mr. A, Mr. B, and Mr. C) are charged equally (specifically, refer to FIG. 9 and FIG. 10), or a predetermined proportion of charges for each member of use. Billing information can also be generated for each forehead.

  The billing processing unit 304 reads billing information generated by the billing information generating unit 303 and stored in a predetermined storage area. Based on the read billing information, billing processing is performed for each use member. Specifically, the billing processing unit 304 realizes its function by the CPU 201 executing a program stored in the RAM 202, the ROM 203, the HD 205, the FD 207, or the like shown in FIG.

  The billing processing unit 304 includes functional units such as a withdrawal processing unit 304a and a bill creation processing unit 304b. Specifically, the withdrawal processing unit 304a and the bill creation processing unit 304b realize their functions by causing the CPU 201 to execute programs stored in the RAM 202, the ROM 203, the HD 205, the FD 207, and the like shown in FIG.

  Specifically, the withdrawal processing unit 304a performs the billing process by rewriting the personal card information of the personal card 350 of each applicable member. That is, the same procedure (data rewriting process) as when the usage amount was settled by the individual member's personal card 350 is executed. Further, the bill creation processing unit 304b performs processing for creating (issuing) a bill for the usage amount with reference to address information of each corresponding usage member. Invoicing is preferably performed every predetermined period (for example, for one month). The creation of the bill in the bill creation processing unit 304b may be executed only when the member using the shared card 300 does not own the personal card 350. Alternatively, either one may be executed based on each user's request (withdrawal from the personal card 350 or payment by bill).

  The billing processing unit 304 is a process of withdrawing the usage amount from the personal card 350 of the usage member when the usage member owns the personal card 350 of the usage member. In the case of not owning, it is possible to create a bill for the usage amount for the member or to withdraw from the bank account. By creating an invoice, the use member can be transferred to a predetermined bank account. Whether or not the user member owns the personal card 350 is owned by the user information acquisition unit 302 is acquired from the user information DB 103a. A bank account is not limited to a bank, but means an account of a financial institution such as a post office or a credit union. Then, the billing processing unit 304 determines which one to select based on the acquired information regarding whether or not the user member owns the personal card 350.

The point calculation unit 305 reads the shared card usage information acquired by the shared card usage information acquisition unit 301 and stored in the predetermined storage area. Then, based on information regarding the usage amount of the shared card 300 among the read shared card usage information, the points given in accordance with the usage of the shared card 300 are obtained using the point information DB (database) 306. Calculated for each member member's personal card 350.

  In addition, the point calculation unit 305 may read the sales information stored in the sales information DB 103d and calculate points based on the read sales information. Specifically, the point calculation unit 305 realizes its function when the CPU 201 executes a program stored in the RAM 202, the ROM 203, the HD 205, the FD 207, or the like shown in FIG.

  The point information DB 306 stores information related to points to be given according to the usage amount of the shared card 300 and the personal card 350. In addition, even if the amount used is the same, points may be given differently depending on the card owner, purchased product, purchased store, time of purchase, etc., and information about each point in that case is also accumulated Has been. Specifically, the point information DB 306 realizes its function by, for example, the RAM 202, ROM 203, HD 205, FD 207, etc. shown in FIG.

  The point calculation unit 305 acquires the number of points (total number of points) corresponding to the usage amount of the shared card 300 by transmitting those conditions to the point information DB 306 and acquiring information about the corresponding points, Store in the storage area. Thereafter, the point calculation unit 305 divides the total number of points stored in a predetermined storage area according to the use member, and calculates the number of points of each member. At that time, the number of points is equal for each member stored in the predetermined storage area (that is, Mr. A, Mr. B, Mr. C in the above example) (specifically, refer to FIGS. 9 and 10). ), Or billing information can be generated so that the number of points is predetermined for each user.

  The point giving processing unit 307 gives each point calculated by the point calculating unit 305 to the personal card 350 of the using member. Specifically, points can be given to each member by updating the information related to the points of the member's personal card 350 (rewriting processing of point data) to the personal card information DB 103c. Specifically, for example, the CPU 201 executes a program stored in the RAM 202, the ROM 203, the HD 205, the FD 207, or the like shown in FIG.

  The personal card usage information acquisition unit 308 acquires, from the personal card information DB 103c, information related to the usage of the personal card 350 of all the usage members, or at least one of the usage members, and possesses a predetermined storage area (specifically, Is stored in, for example, the RAM 202, the ROM 203, the HD 205, the FD 207, and the like shown in FIG. Specifically, the personal card usage information acquisition unit 308 functions by the CPU 201 executing a program stored in the RAM 202, ROM 203, HD 205, FD 207, or the like, for example, by the I / F 209 shown in FIG. Realize.

  The usage limit determining unit 309 reads information on the usage of the personal card 350 of the usage member acquired by the personal card usage information acquisition unit 308 and stored in a predetermined storage area. Then, the usage limit amount of the shared card 300 is determined based on the read information. Specifically, the usage limit determining unit 309 realizes its function by the CPU 201 executing a program stored in, for example, the RAM 202, the ROM 203, the HD 205, the FD 207, or the like shown in FIG.

  The usage limit of the shared card 300 is determined by the usage limit of the personal card 350 owned by each usage member when the shared card 300 is issued. Specifically, for example, the usage limit of each member (Mr. A, Mr. B, Mr. C) is A's personal card 350a: 3 million yen, B's personal card 350b: 2 million yen, C If the personal card 350c is 1 million yen, the usage limit of the shared card 300 is 6 million, which is the total amount of the personal cards 350 for three people.

  In this case, if any one of the usage members (Mr. A, Mr. B, Ms. C) uses the personal card 350 and the individual usage limit is changed, By using 10,000 yen with the personal card 350b, if Mr. B's personal usage limit reaches 1.9 million yen, the above 100,000 yen is subtracted from the 6 million yen usage limit of the shared card 300 to 5.9 million yen To.

  Alternatively, the use limit amount of the shared card 300 may be 3 million yen, which is the use limit amount of the personal card 350a of the highest member (Mr. A) among the use members. In this case, even if Mr. B and Mr. C use the personal cards 350b and 350c, respectively, the usage limit of 3 million yen of the shared card 300 is not changed, but when Mr. A uses the personal card 350a, The amount obtained by subtracting the usage amount is set as the usage amount of the shared card 300.

  The use limit amount of the shared card 300 may be the one million yen of the use limit amount of the personal card 350c of the minimum member (Mr. C) among the use members. In this case, even if Mr. A and Mr. B use the personal cards 350a and 350b, respectively, the usage limit of 1,000,000 yen of the shared card 300 is not changed, but when Mr. C uses the personal card 350c, The amount obtained by subtracting the usage amount is set as the usage amount of the shared card 300.

  Further, an average amount of 2 million yen of the usage limit amount of three people may be used as the usage limit amount of the shared card 300. In this case, if any one of the members (Mr. A, Ms. B, Ms. C) uses the personal card 350 and the personal usage limit is changed, specifically, Mr. B is 100,000 By using the yen with the personal card 350b, when Mr. B's individual usage limit amounted to 1.9 million yen, the above 100,000 yen was divided into 330,000 from the usage limit of 2 million yen for the shared card 300. The yen is subtracted to 296.7 million yen.

(Card payment processing procedure)
Next, the contents of the card payment processing procedure will be described. FIG. 4 is a flowchart showing the contents of the processing procedure in the card settlement system according to the embodiment of the present invention. In the flowchart of FIG. 4, the card payment system 101 first determines whether or not the shared card 300 has been used (step S401).

  Specifically, for example, when the shared card 300 is used, the information is stored in the shared card information DB 103b. The shared card usage information acquisition unit 301 of the card payment system 101 determines whether or not the shared card 300 has been used by acquiring information related to the usage of the shared card 300 from the shared card information DB 103b. The use of the shared card 300 may be determined for each individual use, and it may be determined whether or not the card has been used for a predetermined period (usually one month) on a predetermined settlement date. Also good.

  If the shared card 300 is used after waiting for the shared card 300 to be used in step S401 (step S401: Yes), the usage information is acquired from the shared card information DB 103b and stored in a predetermined storage area. Store (step S402). Further, the user information is acquired from the user information DB 103a and stored in a predetermined storage area (step S403).

  The billing information generation unit 303 reads the usage information of the shared card 300 acquired and stored in step S402 and the user information acquired and stored in step S403, respectively, and the read usage information and user information are read out. The billing information is generated based on the information and stored in a predetermined storage area (step S404). Details of the billing information generation processing procedure will be described later. Thereafter, the billing processing unit 304 reads the billing information generated and stored in step S404, and executes billing processing for each member based on the billing information read (step S405). Details of the billing procedure will be described later.

  Furthermore, as necessary, the point calculation unit 305 reads the usage information of the shared card 300 acquired and stored in step S402 and the user information acquired and stored in step S403, respectively, and the read usage information and Based on the user information, using the information accumulated in the point information DB 306, the number of points to be given to each usage member according to the usage of the shared card 300 is calculated and stored in a predetermined storage area (step S406). . Then, the point grant processing unit 307 gives points by updating the personal card information DB 103c of each user based on the number of points calculated and stored in step S406 (step S407). Details of the point calculation / assignment processing procedure will be described later.

(Billing information generation process (step S404 in FIG. 4))
FIG. 5 is a flowchart showing the contents of the billing information generation process in the processing procedure in the card settlement system according to the embodiment of the present invention. In the flowchart of FIG. 5, first, the usage information obtained and stored from the shared card information DB 103b is read, and information on the usage amount by the shared card 300 is extracted from the read usage information and stored in a predetermined storage area. (Step S501). Further, the user information obtained and stored from the user information DB 103a is read out, information on the number of users, that is, the number of members in use is extracted from the read user information and stored in a predetermined storage area (step S502).

  Next, the information on the usage amount extracted and stored in step S501 and the information on the number of users extracted and stored in step S502 are respectively read, and the usage amount is divided by the number of users based on the read information. Thus, the usage amount per person is calculated and stored in a predetermined storage area (step S503). Next, it is determined whether or not there is a fraction in the calculation result (step S504). Here, when there is no fraction (step S504: No), a series of processing is ended without doing anything. On the other hand, when there is a fraction (step S504: Yes), the fraction is added to one or more predetermined representatives, and the information is also stored (step S505), and a series of processes Exit.

(Billing process (step S405 in FIG. 4))
FIG. 6 is a flowchart showing the contents of the billing process in the processing procedure in the card settlement system according to the embodiment of the present invention. In the flowchart of FIG. 6, the user information acquired from the user information DB 103a and stored is read out, information on the personal card 350 of each user is extracted from the read user information, and stored in a predetermined storage area. Store (step S601).

  Next, the extracted and stored information about the personal card 350 is read out, and it is determined whether or not there is a user who does not own the personal card 350 among the usage members (step S602). Here, when all the using members possess the personal card 350 (step S602: No), the process proceeds to step S604. On the other hand, when there is a user who does not own the personal card 350 (step S602: Yes), the above-described bill creation processing is executed for the user who does not own the personal card 350 (step S603). ), The process proceeds to step S604.

  In step S604, the above-described withdrawal process from the personal card 350 is executed for the member who owns the personal card 350 (step S604). As a result, a series of processing is completed.

(Point calculation / grant process (steps S406 and 407 in FIG. 4))
FIG. 7 is a flowchart showing the contents of the point calculation / granting process in the processing procedure in the card settlement system according to the embodiment of the present invention. In the flowchart of FIG. 7, first, the usage information obtained and stored from the shared card information DB 103b is read, and information relating to the usage amount by the shared card 300 is extracted from the read usage information and stored in a predetermined storage area. (Step S701). Further, the user information obtained and stored from the user information DB 103a is read out, information on the personal card 350 of each user member is extracted from the read out user information, and stored in a predetermined storage area (step) S702).

  Next, the granted point information for the usage amount is acquired from the point information DB 306 and stored in a predetermined storage area (step S703). Then, information relating to the usage amount extracted and stored in step S701 and information relating to the personal card 350 extracted and stored in step S702 are respectively read, and based on the read information, the read point information is similarly read out. Is used to divide the number of granted points by the number of owners of the personal card 350 among the members in use, thereby calculating the granted points per person and storing them in a predetermined storage area (step S704).

  Next, it is determined whether or not the calculation result has a fraction (step S705). If there is no fraction (step S705: No), the process proceeds to step S707 without doing anything. On the other hand, when there is a fraction (step S705: Yes), the fraction is added to one or more representatives determined in advance, and the information is also stored (step S706), and the process goes to step S707. Transition.

  In step S707, the number of points calculated and stored in step S704 is read, and points are given only to the user (user) who owns the personal card 350 (step S707). Specifically, by updating the information regarding the number of points for each personal card 350 stored in the personal card information DB 103c, it is possible to give points to each use member. As a result, a series of processing is completed.

(Usage limit determination process)
FIG. 8 is a flowchart showing the contents of the processing procedure (determination processing of the limit amount) in the card payment system according to the embodiment of the present invention. In the flowchart of FIG. 8, the usage limit is first reset (step S801). That is, the usage limit registered and accumulated in the shared card information DB 103b is changed so as to be the usage limit determined when the shared card 300 is issued (“6 million yen” in the above example). .

  Next, it is determined whether or not the shared card 300 has been used (step S802). Specifically, for example, when the shared card 300 is used, the information is stored in the shared card information DB 103b. The shared card usage information acquisition unit 301 of the card payment system 101 determines whether or not the shared card 300 has been used by acquiring information related to the usage of the shared card 300 from the shared card information DB 103b. Use of the shared card 300 is determined for each individual use.

  If the shared card 300 is not used in step S802 (step S802: No), the process proceeds to step S805 without doing anything. On the other hand, if the shared card 300 is used (step S802: Yes), information on the usage amount and information on the current usage limit (“6 million yen if reset” is extracted) from the shared card information DB 103b. Then, it is stored in a predetermined storage area (step S803). Next, in step S803, the information on the usage amount extracted and stored and the information on the current usage limit amount are read out. Based on the read information, a new usage limit is calculated by subtracting the current usage amount from the current usage limit, and the calculated new usage limit is shared as the current usage limit. Data in the card information DB 103b is updated (step S804).

  Next, in step S805, it is determined whether or not each user (user member) personal card 350 has been used. Here, when the personal cards 350 of all the users are not used (step S805: No), the process proceeds to step S808. On the other hand, when the personal card 350 of any one of the users is used (step S805: Yes), information on the usage amount of the personal card 350 and the current usage limit amount of the personal card 350 from the personal card information DB 103c. The information regarding is extracted and stored in a predetermined storage area (step S806).

  Next, in step S806, information on the usage amount extracted and stored and information on the current usage limit amount are read out. In step S804, information on the updated usage limit amount of the shared card 300 is read out. Then, based on the read information, a new usage limit is calculated by subtracting the usage amount of the current personal card 350 from the current usage limit amount, and the calculated new usage limit amount is used as the current usage limit amount. The data in the shared card information DB 103b is updated as the limit amount (step S807). In this way, each time the shared card 300 or the personal card 350 of each user is used, the usage limit of the shared card 300 decreases.

  Thereafter, it is determined whether or not a predetermined time (period) has elapsed (step S808). Specifically, for example, the predetermined time (period) is, for example, one month, and it is determined whether or not the closing date for one month has passed. Here, if the predetermined time has not elapsed (step S808: No), the process returns to step S802, and thereafter, the processes of steps S802 to 808 are repeated. On the other hand, if the predetermined time has elapsed (step S808: Yes), the process returns to step S801, the usage limit is reset (step S801), and the following steps are repeated thereafter.

(An example of how to use the card payment system)
FIG. 9 is an explanatory diagram showing an example of a usage pattern of the card payment system according to the embodiment of the present invention. In FIG. 9, the members A, B, and C of the user group 901 of the shared card (mom wallet card) 300 own personal cards 350a, 350b, and 350c, respectively. When these three members are used as members (representing Mr. A) to apply for the membership of the mama wallet card to the card company 902, the maturity wallet card 300 is issued after the examination by the examination organization 903 and passing the examination.

  The admission screening may be conducted for all three members or only the representative A. Further, the expiration date of the mom wallet card 300 can be determined by applying at the time of applying for the card.

  And when three people in the usage group travel together, etc., and the total amount paid is 10,000 yen due to food procurement 904a, gasoline refueling 904b, and highway usage 904c, each usage is 10,000 yen Request and give points to members. Specifically, dividing 10,000 yen equally into three equals a fraction of 1 yen. Therefore, 1 yen of the fraction is added to Mr. A, the usage amount (withdrawal amount) of Mr. A's personal card 350a is 3,334 yen, and the usage amounts of Mr. B and C are both 3,333 yen. .

  In addition, regarding the point grant, the total points given for the use of 10,000 yen is 10 points, and when it is divided into three, the fraction becomes 1 point, and this 1 point is given to Mr. A. Therefore, Mr. A will be given 4 points, and Mr. B and Mr. C will be given 3 points each.

  FIG. 10 is an explanatory diagram showing another example of the usage pattern of the card payment system according to the embodiment of the present invention. The difference from FIG. 9 is that neither user B nor Mr. C owns the personal card 350. For example, this is the case where Mr. B and Mr. C cannot own a card for reasons such as minors.

  Mr. A, the owner of the personal card 350a, will be the representative, and when these three members are used as members, they apply to the card company 902 for membership in the mama wallet card. A card 300 is issued. In this case, the admission examination should be conducted only by the representative A. Further, the expiration date of the mom wallet card 300 can be determined by applying at the time of applying for the card. In addition, the usage limit is the usage limit for Mr. A's personal card 350a.

  Similarly to FIG. 9, when three people in the usage group travel together, etc., and the total payment is 10,000 yen due to food procurement 904a, gasoline refueling 904b, and highway use 904c, 10,000 yen Charge and give points to each member for use. Specifically, dividing 10,000 yen equally into three equals a fraction of 1 yen. Therefore, 1 yen of the fraction is added to Mr. A, the usage amount (withdrawal amount) of Mr. A's personal card 350a is 3,334 yen, and the usage amounts of Mr. B and C are both 3,333 yen. .

  Here, since Mr. B makes 3,333 yen by transfer, he sends an invoice with transfer sheets to Mr. B. On the other hand, Mr. C wants to withdraw a bank account, and since the automatic transfer procedure has been carried out in advance, 3,333 yen will be withdrawn from Mr. C's bank account on a predetermined date.

  In addition, regarding the point grant, the total points given for the use of 10,000 yen is 10 points, but since neither Mr. B nor Mr. C own the personal card 350, no points are granted ( (0 points), all procedures are given to Mr. A (10 points). In this example, since one person owns the personal card 350, all points are given to one person. However, when multiple persons own the personal card 350, all points are given to the representative. May be given, and the points may be equally divided by a plurality of persons who own the personal card 350.

  As described above, according to this embodiment of the present invention, the shared card usage information acquisition unit 301 that acquires information related to the usage of the shared card 300 and the plurality of users registered when the shared card 300 is issued. User information acquisition unit 302 that acquires information related to a plurality of users of shared card 300 from user information DB 103a that stores information, and user information based on information acquired by shared card usage information acquisition unit 301 A billing information generation unit 303 that generates billing information for each user acquired by the acquisition unit 302, and a billing processing unit 304 that performs billing processing for each user based on the billing information generated by the billing information generation unit 303 Since it can be paid using the shared card 300, it is completely different from a normal personal card. It is possible to complete the payment process in the like of the procedure.

  Further, according to the present embodiment of the present invention, the billing information generation unit 303 is based on the information acquired by the shared card usage information acquisition unit 301 for each user acquired by the user information acquisition unit 302. Since the billing information is generated so that the billing amount is equal, or the billing amount is predetermined for each user, it is possible to reduce the work for reimbursement of the advance later.

  Further, according to this embodiment of the present invention, the personal card usage information acquisition unit 308 that acquires information related to the usage of the personal card 350 of the user owned by at least one of the users, and the personal card usage information And a usage limit determining unit 309 that determines the usage limit of the shared card 300 based on the information acquired by the acquisition unit 308. Therefore, it is possible to prevent the card from being used beyond the usage limit. it can.

  Further, according to the present embodiment of the present invention, when the user has the personal card 350 of the user, the billing processing unit 304 determines the usage amount from the personal card 350 of the user. If the user does not own the user's personal card 350, this is a process of creating an invoice for the usage amount for the user or a withdrawal process from a bank account. Even if it is not, it can become a utilization member and the utilization of the shared card 300 can be further promoted.

  Further, according to the present embodiment of the present invention, points given in accordance with the use of the shared card 300 based on the information acquired by the shared card use information acquiring unit 301 are assigned to the user's personal card 350. A point calculation unit 305 to be calculated every time, and a point grant processing unit 307 to give the points calculated by the point calculation unit 305 to the personal card 350 of the user. Can share equally.

  Note that the card settlement system 101 described in the present embodiment can be realized by causing a program prepared in advance to be executed by a computer such as a personal computer or a workstation. This program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. The program may be a transmission medium that can be distributed via a network such as the Internet.

  As described above, the present invention can be used in a card payment system, and is particularly suitable for using a card shared by a plurality of users for payment for purchase of goods or services.

It is a block diagram which shows the outline | summary of the whole system concerning embodiment of this invention. It is a block diagram which shows the hardware constitutions of the card payment system concerning embodiment of this invention. It is a block diagram which shows an example of a functional structure of the card payment system concerning embodiment of this invention. It is a flowchart which shows the content of the process sequence in the card payment system concerning embodiment of this invention. It is a flowchart which shows the content of the charge information generation process of the process procedures in the card payment system concerning embodiment of this invention. It is a flowchart which shows the content of the billing process in the process sequence in the card payment system concerning embodiment of this invention. It is a flowchart which shows the content of the point calculation and provision process of the process procedures in the card payment system concerning embodiment of this invention. It is a flowchart which shows the content of the processing procedure (determination processing of a limit amount) in the card payment system concerning embodiment of this invention. It is explanatory drawing which shows an example of the utilization form of the card payment system concerning embodiment of this invention. It is explanatory drawing which shows another example of the utilization form of the card payment system concerning embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Network 101 Card payment system 102 (102a, 102b, 102c) Store terminal 103 Various DB (database)
103a User information DB (database)
103b Shared card information DB (database)
103c Personal card information DB (database)
300 Shared card (mom wallet card)
301 Shared Card Usage Information Acquisition Unit 302 User Information Acquisition Unit 303 Billing Information Generation Unit 304 Billing Processing Unit 304a Withdrawal Processing Unit 304b Invoice Creation Processing Unit 305 Point Calculation Unit 306 Point Information DB (Database)
307 Point grant processing unit 308 Personal card usage information acquisition unit 309 Usage limit determination unit 350 (350a, 350b, 350c) Personal card

Claims (7)

A card payment system that uses a card to make payments for purchases of goods or services,
Among the cards, a shared card usage information acquisition unit that acquires information related to usage of a card shared by a plurality of users (hereinafter referred to as “shared card”);
User information acquisition means for acquiring information on a plurality of users of the shared card from a user information database storing information on a plurality of users registered at the time of issuing the shared card;
Billing information generating means for generating billing information for each user acquired by the user information acquiring means based on the information acquired by the shared card usage information acquiring means;
Billing processing means for performing billing processing for each user based on the billing information generated by the billing information generating means;
A card payment system characterized by comprising:   The billing information generation unit is configured to obtain an equal bill amount for each user acquired by the user information acquisition unit based on the information acquired by the shared card usage information acquisition unit, or the user 2. The card settlement system according to claim 1, wherein billing information is generated so that a billing amount at a predetermined rate is generated for each billing information. Personal card use information acquisition means for acquiring information related to the use of the individual card of the user owned by at least one of the users;
Usage limit determination means for determining the usage limit of the shared card based on the information acquired by the personal card usage information acquisition means;
The card payment system according to claim 1 or 2, further comprising:   When the user owns the user's personal card, the claim processing means is a process of withdrawing the usage amount from the user's personal card, and the user is the user personal If the card is not owned, it is a billing process for the usage amount for the user or a debiting process from a bank account. Card payment system. Based on the information acquired by the shared card usage information acquisition means, point calculation means for calculating points given in correspondence with the usage of the shared card for each individual card of the user;
Point grant processing means for granting the points calculated by the point calculation means to the user's personal card;
The card payment system according to claim 4, further comprising: A card payment program that causes a card payment system to use a card to make payments for purchases of goods or services,
In card payment system,
Among the cards, a shared card use information acquisition step for acquiring information related to use of a card shared by a plurality of users (hereinafter referred to as “shared card”);
A user information acquisition step of acquiring information on a plurality of users of the shared card from a user information database storing information on a plurality of users registered at the time of issuing the shared card;
A billing information generation step for generating billing information for each user acquired by the user information acquisition step based on the information acquired by the shared card usage information acquisition step;
A billing process for billing each user based on the billing information generated by the billing information generating process;
Card payment program characterized by causing A card payment method that uses a card to make a payment for the purchase of goods or services using a card payment system,
Card payment system
Among the cards, a shared card use information acquisition step for acquiring information related to use of a card shared by a plurality of users (hereinafter referred to as “shared card”);
A user information acquisition step of acquiring information on a plurality of users of the shared card from a user information database storing information on a plurality of users registered at the time of issuing the shared card;
A billing information generation step for generating billing information for each user acquired by the user information acquisition step based on the information acquired by the shared card usage information acquisition step;
A billing process for billing each user based on the billing information generated by the billing information generating process;
The card payment method characterized by performing.

Images