JP3987758B2 - Billing / settlement system that can have multiple merchant codes for one service provider - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a system for charging / settlement of paid services on the Internet, other networks, or in the real world, and in particular, between a credit card company or a settlement agency company where a service provider providing the service performs settlement. The present invention relates to a method for efficiently managing a member store code when a plurality of member store contracts are concluded, and a method for managing this when a service provider manages a service user as a member.
[0002]
[Prior art]
When a service provider uses credit card payment, it is necessary to make a contract with a credit card company or a payment agent company. (Here, the service provider includes both a service provider having a physical store and a service provider having a virtual store deployed online.)
In this contract, whether the service provider sells only to members, sells to the general public, the price range of the products handled by the service provider, whether or not a regular charge occurs like a monthly fee, etc. Differences in merchant contracts with credit card companies or payment agent companies will arise due to restrictions on products and sales targets.
Thus, when there is a difference between member store contracts, a difference also occurs in the handling and processing flow of billing / sales data.
On the other hand, when one service provider sells a variety of products, for example, when one service provider sells both mail-order merchandise sales and monthly digital contents, the processing flow pattern of these charges and sales A virtual business operator that enters into a franchise contract with a credit card company or payment agency for each different product and sells different types of products when viewed from the credit card company or payment agency. It is common to handle as follows.
[0003]
Conventional billing systems and payment systems are created on the assumption that one service provider can manage one credit card company or one payment agent company as one member store code. It was not envisaged that one service provider would handle multiple types of merchant codes.
For this reason, in order to provide both products with different member store codes to the member when the service provider manages the membership, the billing / settlement system uses data between multiple virtual service providers. It is necessary to synchronize the member data in the application, and the application using the billing / settlement system registers the same data in two virtual operators (substances are one service operator) with different member store codes, or It was necessary to synchronize member data between two virtual operators by some method on the billing / settlement system side.
[0004]
[Problems to be solved by the invention]
When a service provider that manages users as a member has signed multiple merchant contracts with a credit card company or a payment agency in order to provide users with multiple services, the merchant code If you want to provide all members with different services, you must register the member information in the member database corresponding to each member store contract, and the member information will change. Similarly, it is necessary to update the member database corresponding to each member store contract.
The reason for this is that even in the conventional billing / settlement system, even if the service provider can manage the members, the service provider and the member store have a one-to-one correspondence. This is because only one member store code can be managed for one service provider, and members can be managed only for each member store.
An object of the present invention is to provide a billing / settlement system that can manage a member without waste when one service provider that manages users as described above has a plurality of member store contracts. is there.
[0005]
[Means for Solving the Problems]
To solve the above problem,
According to the first aspect of the present invention, there is provided a merchandise type product information table for identifying a pattern of a billing or sales processing flow different from service provider identification information and merchandise information including a sales amount, and one service corresponding to a plurality of merchandise types. A means for receiving a user identification information and purchase product information from a user, comprising a business information table of a plurality of member store codes of the business, a member information table of user identification information and a credit card number, and a user purchase product The sales amount and product type are extracted using the product information table based on the information, the member store code is extracted using the business information table based on the extracted product type, and the member information table is used based on the user identification information. The means to retrieve the user's credit card number, and payment / settlement information consisting of the user's credit card number, member store code and sales amount is settled Characterized by comprising means for transmitting to the company, the.
[0006]
The invention of claim 2 is a product type product information table for identifying a pattern of a processing flow of billing or sales different from service provider identification information and product information including a sales amount, and a member of user identification information and a credit card number. It has an information table and an operator information table for a plurality of member store codes of one service operator corresponding to a plurality of product types, and the sales amount and product type are determined using the product information table based on the user purchase product information. One service business that takes out the member store code using the operator information table based on the extracted product type and the means for extracting the user's credit card number using the member information table based on the user identification information A method for creating billing / settlement information for each service provider by collecting billing / settlement information for merchant codes corresponding to the service provider, and service business And means for transmitting the billing and settlement information consisting of the credit card number of the user of each sales to the settlement company, and further comprising a.
[0008]
DETAILED DESCRIPTION OF THE INVENTION
The billing / settlement system of the present invention comprises a purchase front-end subsystem, a billing subsystem, and a settlement subsystem. The purchase front-end subsystem is responsible for the interface portion for the user to make purchases. The charging subsystem performs a charging process for each user based on information passed from the purchase front-end subsystem. The payment subsystem distributes sales information to an appropriate payment organization based on information passed from the charging subsystem.
[0009]
Example 1
FIG. 1 shows the configuration of the charging / settlement system of the first embodiment.
The purchase front-end subsystem 10 includes a purchase control unit 11, a product management unit 12, and a product information table 13. Product information table 13 identifies service provider identification (identification given to each service provider), product identification (identification given to product), product name, product type (different billing and sales processing flow patterns Type), unit price, etc. are held as a table.
The case where a user (member identification: M1) applies for the use of a monthly fixed-price digital content distribution service (product identification: G1) will be described.
[0010]
Purchase front-end subsystem 10
(1) The user transmits the member identification (M1) and the product identification (G1) of the product to be purchased to the billing / settlement system.
(2) Based on the product identification number (G1) received by the purchase control unit 11, the product management unit 12 searches the product information table 13, and identifies the business entity identification (S1) and product corresponding to the product identification number (G1). The name (monthly fee), product type (T1), and unit price (300 yen) are extracted and transmitted to the purchase control unit 11.
(3) The purchase control unit 11 includes user purchase information (member identification (M1), business operator identification (S1), product identification (G1), product name (monthly fee), product type (T1), unit price (300 yen) ), Quantity (1)), and (4) output to the charging subsystem 20.
Further, as the purchase front-end subsystem, a purchase front-end subsystem may be provided for each service provider, and the user may access the purchase front-end subsystem of the service provider that sells the purchased product.
[0011]
Billing subsystem 20
The charging subsystem 20 uses the member store codes 1, 2,... (For example, in the case of the product type T1, in the case of the member store code 1 and the product type T2, for each business entity identification (S1, S2,...). Uses a member store code 2.) and a member information table 22 in which member identification is associated with a credit card number.
(5) The event control unit 23 refers to the company information table 26 based on the product type (T1) of the user purchase information and retrieves the member store code (A11111001). Also, (6) the member management unit 21 receives the member identification (M1) of the user purchase information from the event control unit 23, refers to the member information table 22, and takes out the credit card number (CN1111) of the member (M1).
(7) The event control unit 23 performs processing based on the product type of the user purchase information. In this case, since the product type is T1 (monthly fee), this information (that is, monthly fee deduction information) is held in the periodic charging event table 24. Next, create user billing information (business type (S1), user credit card number (CN1111), merchant code (A11111001), product sales date (2000.5.5), sales amount (300 yen)) Are stored in the internal billing information storage unit 25, and this information is stored for a certain period (for example, one month) by the period closing processing unit 27.
(9) The user billing information stored in the internal billing information storage unit 25 is output to the settlement subsystem 30.
[0012]
Settlement subsystem 30
(10) (11) The settlement company distribution unit 31 receives the user billing information and bills and settles the specified settlement company based on the user's credit card number (card number (CN1111), member store code (A11111001) , Product sales date (2000.5.5), sales amount (300 yen)).
It is assumed that the charging subsystem can manage the provider identification and a plurality of member store codes as information for each service provider, and can correspond to the product type information of the purchase front-end subsystem. As the service provider information, other necessary data such as the provider name and address may be managed.
In addition, the billing subsystem can manage the members of the user, and manages information such as member identification, credit card number required for settlement, and credit card expiration date as member information. Information such as a member name and address may be managed as member information if necessary.
The payment subsystem performs processing for distributing sales data to an appropriate payment period in accordance with the carrier identification of the information for each service carrier possessed by the billing subsystem, but the detailed method is not defined in the present invention.
[0013]
(Example 2)
FIG. 2 shows the configuration of the charging / settlement system of the second embodiment.
The difference from the billing / settlement system in FIG. 1 is that the merchant code is not managed by the billing subsystem, but by the settlement subsystem, and payment is made at any settlement organization (credit company, etc.) for each service provider. Distribute billing / settlement information so that
A case where the user purchases two ballpoint pens will be described.
(1) The user transmits member identification (M1), product identification (G2), and quantity (2) to the billing / settlement system.
(2) to (4) As in the first embodiment, the purchase control unit 11 and the product management unit 12 use the product information table 13 to obtain user purchase information (member identification (M1), business operator identification (S1), product identification). (G2), product name (ballpoint pen), product type (T2), unit price (120 yen), quantity (2)) are created and output to the charging subsystem 20.
(6) to (9) The charging subsystem 20 is similar to the first embodiment in the user charging information (credit card number (CN1111), business type (S1), product type (T2), sales date (2002.5.5)) , A sales amount (240 yen)) is generated and output to the settlement subsystem 30. In this case, the periodic billing event table 24 is not used because it is not a monthly fee (that is, automatic deduction).
[0014]
Settlement subsystem 30
The settlement subsystem 30 includes a member store code conversion table 33 composed of member store codes 1, 2,.
(10) The member store code management unit 32 receives the user billing information and (11) retrieves the member store code 2 (A11111002) with reference to the member store code conversion table 33 based on the product type (T2). Then, billing / settlement information (card number (CN1111), member store code (A11111002), sales date (2002.5.5), sales amount (240 yen)) is created, and the settlement company distribution unit 31 provides the credit card number. Originally sent to the settlement company. At this time, the member store code management unit 32 collects the billing / settlement information of the member store codes of one service provider and creates billing / settlement information for each service provider.
[0015]
(Example 3)
FIG. 3 shows the configuration of the charging / settlement system of the third embodiment.
The difference from the first embodiment is that the member store code is not managed by the charging subsystem, but the member store code is handled as part of the product information of the purchase front-end subsystem.
The purchase front-end subsystem 10 includes a product information table 13 for product identification, product name, member store code, and unit price.
A case where the user purchases two ballpoint pens will be described.
(1) The user transmits member identification (M1), product identification (G2), and quantity (2) to the billing / settlement system.
(2) The purchase control unit 11 receives this, and the product management unit 12 refers to the product information table 13 based on the product identification (G2), identifies the product identification (G2), the product name (ballpoint pen), the member store code (A11111002 ), The unit price (120 yen) is taken out and transmitted to the purchase control unit 11. (3) The purchase control unit 11 provides user purchase information (member identification (M1), member store code (A11111002), product identification (G2), product name (ballpoint pen), unit price (120 yen), quantity (2)). Create and send to billing subsystem (4).
[0016]
(5) to (8) The event control unit 23 receives the user purchase information, and the member management unit 21 extracts the credit card number (CN1111) based on the member type (M1) from the member information table 22, and controls the event. Department 23 creates billing / settlement information (card number (CN1111), member store code (A11111002), sales date (2000.5.5), sales amount (240 yen)) based on user purchase information The billing information storage unit 25 and the term closing processing unit 27 output user billing information for a certain period (for example, one month) to the payment subsystem 30.
(9), (10) The payment subsystem 30 sends the user billing information (card number (CN1111), merchant code (A11111002), sales date (2002.5.5), Send the sales amount (240 yen).
[0017]
【The invention's effect】
The first effect is that a single service provider can provide a variety of products and services such that there are a plurality of member store codes at the time of card settlement. The reason is that, by using the present invention, a plurality of member store codes can be used properly depending on the type of product.
The second effect is that when a single service provider manages various members of a service user while providing various products and services that result in multiple member store codes at the time of card payment, It is to be able to unify management. The reason is that, conventionally, it was necessary to manage the membership for each member store code, but by using the present invention, the service provider can use a plurality of member store codes and perform member management separately. This is because it is not necessary.
[Brief description of the drawings]
FIG. 1 is a functional configuration diagram of a billing / settlement system according to a first embodiment.
FIG. 2 is a functional configuration diagram of a charging / settlement system according to a second embodiment.
FIG. 3 is a functional configuration diagram of a charging / settlement system according to a third embodiment.
[Explanation of symbols]
10 ... Purchase front-end subsystem
11 ... Purchase control unit, 12 ... Product management unit, 13 ... Product information table
20 ... Billing subsystem
21 ... Member management unit, 22 ... Member information table, 23 ... Event control unit,
24: Periodic charge event table, 25: Internal charge information storage unit
26 ... Business information table, 27 ... Period closing processing section
30 ・ ・ ・ Payment subsystem
31 ... Settlement company distribution department, 32 ... Merchant code management department, 33 ... Merchant code conversion table

Claims (2)

A billing / settlement system for paid services provided by a service provider to their members after a service provider has signed multiple merchant contracts with a credit card company or a settlement agency.
Product identification for the service provider (hereinafter referred to as operator identification), unit price, product name, product identification attached to the product, and product type that identifies different billing and sales processing flow patterns An information table, a company information table of a plurality of member store codes of one service company corresponding to a plurality of product types, a member information table of member identification and credit card number,
Means for receiving user identification information and product identification information from a user;
Based on the received product identification information, the sales information, product type, and business operator identification are extracted using the product information table, and include the received user identification information, the extracted sales price, product type, and business operator identification. A means of creating user purchase information;
The member store code is extracted using the business operator information table based on the product type included in the user purchase information, and the member information table is used based on the user identification information included in the user purchase information. Means for taking out the user's credit card number and creating user billing information consisting of the taken out user's credit card number, member store code and sales amount;
Means for transmitting billing / settlement information consisting of the user's credit card number, member store code and sales amount extracted from the user billing information to a settlement company;
A billing / settlement system capable of having a plurality of member store codes for a single service provider. A billing / settlement system for paid services provided by a service provider to their members after a service provider has signed multiple merchant contracts with a credit card company or a settlement agency.
Service provider identification (hereinafter referred to as operator identification), unit price, product name, product identification attached to the product, and different billing and sales processing flow patterns corresponding to the product identification A product information table of product types for identifying a user, a member information table of user identification information and a credit card number, and a business information table of a plurality of member store codes of one service business corresponding to a plurality of product types Prepared,
Means for receiving user identification information, product identification information and quantity from the user;
Means for extracting a sales amount and a product type using the product information table based on the received product identification information, and creating user purchase information including the received user identification information, the extracted sales amount and the product type; ,
The credit card number of the user is extracted using the member information table based on the user identification information included in the user purchase information, and is included in the extracted user credit card number and the user purchase information. Means for creating user billing information including business entity identification, product type and sales amount;
Based on the product type extracted from the user billing information, a merchant code is retrieved using the business information table, and the bill includes the retrieved merchant code, the credit card number retrieved from the user billing information, and the sales amount.・ Means to create payment information;
Means for creating billing / settlement information for each service provider by collecting the billing / settlement information of member store codes corresponding to one service provider;
Means for transmitting billing / settlement information consisting of the user's credit card number and sales amount for each service provider to a settlement company;
A billing / settlement system capable of having a plurality of member store codes for a single service provider.

Images