JP2006285444A - Settlement/charge-collection proxy system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform settlement/charge-collection on behalf of a service providing firm and settlement/charge-collection firm without imposing large load on the firms. <P>SOLUTION: A settlement/charge-collection proxy program is stored in a settlement/charge-collection proxy system 24 in a proxy firm system 2. Then, a service providing system 3 requests the transmission of the settlement/charge collection proxy program to the settlement/charge-collection proxy system 24. Then, the settlement/charge-collection proxy system 24 transmits the settlement/charge-collection proxy program which it stores to the service providing system 3 in response to the transmission request. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a settlement / fee collection agency system that performs settlement / fee collection on behalf of a service provider.

  With the spread of computer networks such as the Internet, for example, consumers access computer terminals to electronic shopping malls (electronic shopping streets) on the Internet, and buy and sell products, tickets (entrance tickets, tickets) Electronic commerce, in which electronic contents such as reservations and purchases of boarding passes, etc., and electronic contents such as still images, moving images, and software programs are electronically purchased.

  In such electronic commerce, another operator may perform settlement or fee collection that occurs when a consumer receives a service from a service provider that provides the service on behalf of the service provider. Often there is. In addition, as a business operator that performs payment and fee collection (hereinafter referred to as payment and fee collection agent), for example, a credit sales company that handles credit cards, an Internet service provider that provides Internet connection services, and communication services including telephones Telecommunications companies that provide services.

Currently, there are various systems in which payment / charge collection agents perform collection services (see, for example, Patent Documents 1 to 5). For example, paying attention to the fact that most consumers receive public services from public service providers such as electric power companies and have established a utility charge debit account to pay utility charges. And collection using a utility bill withdrawal account.
JP 2001-283131 A JP 2002-325136 A JP 2000-353194 A JP 2003-141433 A JP 2003-233766 A

  The service provider, for example, makes a payment for exchanging a payment or billing message with a system provided by the payment / charge collection agency in order to make a payment or collection agency. It is necessary to have a function and a billing function. For this reason, the service provider needs to create a program for the payment function and a program for the billing function, and install and use them in the system on the service provider side. Alternatively, it is necessary for the settlement / fee collection agent to construct its own system so as to be compatible with the system on the service provider side.

  General users who receive services that require payment and fee collection are requesting various payment and fee collection methods. For this reason, in order for a service provider to provide services to a larger number of users, it is necessary for the service provider to connect its own system to the systems of many payment / charge collection agents. . For this reason, it becomes necessary for the service provider to create a program for a settlement function or a program for a billing function for each system of a settlement / fee collection agent to be connected, which increases the burden. Alternatively, the settlement / fee collection agent must construct its own system so as to be compatible with the systems of many service providers, which is a heavy burden. Furthermore, if the service provider is forced to use the hosting system provided by the payment / charge collection agency, the system flexibility on the service provider side will be reduced, preventing the provision of more advanced services. .

  Accordingly, the present invention provides a settlement without imposing a heavy burden on the service provider and the settlement / fee collection agency even when the service provider requests a settlement / fee collection agency from many settlement / fee collection agencies. The purpose is to provide a settlement / fee collection agency system that enables agency of fee collection.

  The settlement / fee collection agency system of the present invention is an agency that performs settlement and fee collection agency, which is connected to a provider company system provided on the provider company side who requests settlement and fee collection agency so that data communication is possible. A settlement / fee collection agency system provided on the contractor side, wherein the provider side system describes a processing procedure to be performed when the settlement / fee collection agency system requests the settlement / fee collection agency Payment / charge collection agency program storage means for storing a collection agency program, and upon receipt of a request for a settlement / charge collection agency program from the provider side system, the settlement stored in the settlement / charge collection agency program storage means -Settlement / fee collection agency program transmission to send the fee collection agency program to the requesting provider's system Characterized by comprising a means.

  In the settlement / fee collection agency system, data to be transmitted when data is transmitted from the provider side system to the settlement / fee collection agency system according to the settlement / fee collection agency program is the settlement / fee collection agency program When receiving a request for an operation check program from the provider side system, an operation check program storage means for storing an operation check program for causing the provider side system to check whether the data structure is defined in the above, It further comprises an operation confirmation program transmitting means for transmitting the operation confirmation program stored in the confirmation program storage means to the provider side system as a request source.

  In the settlement / fee collection agency system, a system for performing processing performed by the settlement / fee collection agency system in the settlement / fee collection agency is constructed in a pseudo manner in the provider side system. A pseudo-settlement system program storage unit that stores a pseudo-settlement system program for causing the system to perform processing performed by the settlement / fee collection agency system; and when receiving a request for the pseudo-settlement system program from the provider side system, It further comprises an operation confirmation program transmission means for transmitting the pseudo payment system program stored in the payment system program storage means to the provider side system as a request source.

  According to the present invention, a settlement / fee collection agency program is stored in advance in the settlement / fee collection agency system, and the settlement / fee collection agency system receives a request for the settlement / fee collection agency program from the provider side system. When you receive it, you will be sent a settlement / fee collection agency program. For this reason, the service provider does not need to create a settlement / fee collection agency program on its own, and the settlement / fee collection agency only needs to create one settlement / fee collection agency program. The burden on the agent will be small.

Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings.
First, a system including a settlement / fee collection agency system according to an embodiment of the present invention will be described with reference to FIG. FIG. 1 is a system configuration diagram of an entire system including a settlement / fee collection agency system according to the present embodiment.

  1 is used by a service provider system 2 constructed by a settlement / fee collection agent, a service provision system 3 constructed by a service provider, and a service user who receives the service. A user terminal 4 is included. The agent system 2, the service providing system 3, and the user terminal 4 are each connected to a computer network such as the Internet, and can exchange data with each other. As the user terminal 4, for example, a terminal device (computer terminal, mobile phone, fixed phone, IP video phone, etc.) provided with an input device (button, keyboard, etc.) connectable to a computer network such as the Internet and an output device (display) Is mentioned.

  The agency system 2 includes a subscriber database 21, a statement issuing system 22, a settlement system 23, and a settlement / fee collection agency system 24. The subscriber database 21 is a database that stores information associated with subscribers who have subscribed to a settlement / fee collection agent. The subscriber information includes an ID (user ID) for identifying the subscriber, a subscriber password, a name, a telephone number, an address, and the like. The statement issuing system 22 is a system for issuing a bill.

  The payment system 23 includes an authentication database (authentication DB) 23a, a payment function (authentication function) unit 23b, and a charging function (charge collection) function unit 23c. The authentication DB 23 a stores an ID (user ID) for identifying a user and a password of the user in association with each other, and is created using the stored contents of the subscriber database 21. The settlement function unit 23b performs user authentication with reference to the stored contents of the authentication DB 23a. The charging function unit 23c charges the service fee to the user.

  As shown in FIG. 2, the settlement / fee collection agency system 24 includes a program storage unit 24a, an electronic certificate storage unit 24b, a settlement / billing management table 24c, a program providing unit 24d, a settlement function unit 24e, and a billing function unit 24f. have. The program storage unit 24a stores a settlement / fee collection agency program, an operation check program (operation check program), and a pseudo payment system program. The settlement / fee collection agent program is a program describing a processing procedure performed when the service providing system 3 requests the settlement / fee collection agency system for settlement (authentication) and billing (fee collection). The operation check program is a data structure (data) that the data to be transmitted when the service providing system 3 transmits data to the settlement / fee collection agency system 24 in accordance with the settlement / fee collection agency program is defined in the settlement / fee collection agency program. This is a program for confirming that the number of digits and the character code are correct. The pseudo payment system program simulates the payment / charge collection agency system and the payment system so that the service provision system 3 can confirm a series of operations of the payment / charge collection agency program and the operation check program. A payment / charge collection agency system and a payment system constructed in a pseudo manner by describing processing procedures executed when the payment / charge collection agency system 24 and the payment system 23 perform settlement and charge collection agency It is a program for executing the processing procedure.

  The electronic certificate storage unit 24b is a storage device that stores an electronic certificate issued to the service provider system 3 of the service provider in association with the business code of the issued service provider.

  The settlement / billing management table 24c is a table for storing settlement and billing information, and an example is shown in FIG. As shown in FIG. 3, the table includes “enterprise code”, “settlement serial number”, “settlement request Token”, “settlement result”, “settlement Token”, and “settlement result Token”.

  The program providing unit 24d transmits the program requested by the service providing system 3 (settlement / fee collection agency program, operation check program, pseudo-settlement system program) to the requesting service providing system 3. The settlement function unit 24e is a function unit that performs processing related to settlement (authentication), and the billing function unit 24f is a function unit that performs processing related to fee collection (billing).

  The service providing system 3 includes a service database (service DB) 31, a service program storage unit 32, a payment function unit 33, a charging function unit 34, an operation confirmation unit 35, and a pseudo payment system unit 36. The service providing system 3 is provided with an electronic certificate storage unit (not shown) that stores the electronic certificate in association with the provider code of the settlement / fee collection agency of the electronic certificate issuer. .

  The service DB 31 includes a service ID for identifying a service for each service, a service charge of the service ID (information indicating that the service is free in the case of a free service), a type (charged each time, flat rate system), and the service ID. Information indicating the location where the program is stored is stored in association. The service program storage unit 32 stores a program (service program) in which contents for transmitting a service to the user terminal 4 are described.

  The settlement function unit 33 is a function unit that performs processing procedures related to settlement (authentication) described in the settlement / fee collection agency program. The charging function unit 34 is a functional unit that performs processing procedures related to fee collection (billing) described in the settlement / fee collection agent program. The operation confirmation unit 35 has a data structure in which data to be transmitted when transmitting data to the settlement / fee collection agency system 24 is defined in the settlement / fee collection agency program according to the contents described in the operation check program (operation confirmation program). This is a functional unit that confirms that the number of digits of data and the character code are set. The pseudo-payment system unit 36 is a part in which a settlement / fee collection agency system and a settlement system are built in the service providing system 3 by a pseudo-payment system program. This is a part for simulating a series of operations of the check program in conjunction with a part in the service providing system 3 and confirming the operation.

  In the following, the flow of settlement / fee collection processing performed in the system shown in FIG. 1 will be described with reference to FIG. FIG. 4 is a sequence diagram showing the flow of processing for payment / fee collection agency in the present embodiment. However, the agency system 2 calls a program (settlement / fee collection agency program, operation check program, pseudo-settlement system program) described in WDSL (Web Services Description Language) in advance to the service providing system 3 (program) Read procedure) and the program read procedure is stored in a storage unit (not shown) of the service providing system 3. In addition, HTTPS (Hypertext Transfer Protocol Security) is used for transmission / reception of programs and payment / billing data between the settlement / charge collection agency system 24 and the service providing system 3 of the settlement / charge collection agency system 2. SSL (Secure Socket Layer) v3 is used so that mutual authentication can be performed.

  The user uses his / her user terminal 4 to access the home page of the service provider and selects the service he / she wants to receive, and the user terminal 4 transmits the service ID of the service to the service providing system 3 (step S101). ). The service providing system 3 refers to the stored contents of the service DB 31 to determine whether or not the service with the service ID is charged, and in this sequence, determines that it is a charged service. Then, the service providing system 3 transmits to the user terminal 4 an explanation screen including a message for explaining to the user that settlement / billing (fee collection) will occur when receiving the provision of the selected service (step) S102). When an explanation screen is displayed on the user terminal 4 and the user accepts that payment / billing occurs, a pointing device such as a mouse provided on the user terminal 4 is provided with a “purchase” button provided in the explanation screen. Based on the pressed signal, the user terminal 4 transmits information (approval) indicating that the user has consented to payment / billing to the service providing system 3 (step S103).

  When the service providing system 3 receives the consent from the user terminal 4, the service providing system 3 transmits a request for a settlement / fee collection agency program (program call request) to the settlement / fee collection agency system 24 (step S104). Then, mutual authentication (key exchange of transmission path encryption based on an electronic certificate) is performed between the service providing system 3 and the settlement / fee collection agency system 24 (step S105). In step S105, the operator codes are exchanged, and the message certificate stored in the electronic certificate storage unit in association with the partner operator code is used.

  After mutual authentication, the program providing unit 24d of the settlement / fee collection agency system 24 transmits the settlement / fee collection agency program stored in the program storage unit 24a to the service provision system 3 (step S106). The service providing system 3 receives the settlement / fee collection agency program from the settlement / fee collection agency system 24, and the service provision system 3 operates the settlement / fee collection agency program on the platform of its own system (step S107). Note that SOAP is used to operate the settlement / fee collection agency program on the platform of the service providing system 3.

  The payment function unit 33 of the service providing system 3 creates a payment serial number by adding 1 to the previous payment serial number as a number for identifying the current payment (step S108). Then, the settlement function unit 33 of the service providing system 3 settles the information (settlement request) for requesting settlement (authentication) including the settlement serial number created in step S107 and the operator code assigned to the service provider. It transmits to the fee collection agency system 24 (step S109).

  The settlement function unit 24e of the settlement / fee collection agency system 24 receives the settlement request from the service providing system 3, creates a hash value from the settlement serial number and the company code included in the settlement request, and sets it as the settlement request Token ( Step S110). At this time, the settlement function unit 24e newly adds the received business operator code and settlement sequence number to the settlement / billing management table 24c, and stores the settlement request Token created at the corresponding location of the added record. The payment request Token is information for confirming the validity of the user terminal 4 that transmits the payment serial number.

  The settlement function unit 24e of the settlement / fee collection agency system 24 sends the settlement sequence number transmitted in step S109, the settlement request Token created in step S110, and the URL of the authentication screen (authentication screen URL) to the service providing system 3. Transmit (step S111). Then, the payment function unit 33 of the service providing system 3 receives the payment sequence number, the payment request token, and the authentication screen URL received from the payment / fee collection agency system 24, and the post-payment completion screen URL stored in the own system. It transmits with respect to the user terminal 4 (step S112). However, the authentication screen is a screen for the user to input a user ID (user ID) and a password used for user authentication by the payment system 23. The screen after completion of payment is a screen for notifying the user that payment (authentication) is completed.

  When the user terminal 4 receives each piece of information transmitted by the service providing system 3 in step S112, the user terminal 4 transmits the received settlement serial number, settlement request Token, and authentication screen URL to the settlement / fee collection agency system 24. (Step S113). Then, the payment function unit 24e of the payment / charge collection agency system 24 receives each piece of information transmitted by the user terminal 4 in step S113, and the combination of the payment serial number and the payment request Token is stored in the payment / charge management table 24c. (Step S114). After the confirmation, the payment function unit 24e of the payment / fee collection agency system 24 transmits an authentication screen URL to the payment system 23 to request an authentication screen (step S115). If the confirmation cannot be made, the settlement function unit 24e of the settlement / fee collection agency system 24 does not request an authentication screen from the settlement system 23.

  The payment function unit 23b of the payment system 23 transmits an authentication screen to the payment / charge collection agency system 24 (step S116), and the payment function unit 24e of the payment / charge collection agency system 24 sends an authentication screen to the user terminal 4. Is transferred (step S117).

  An authentication screen is displayed on the display unit of the user terminal 4, and the user inputs his / her ID (user ID) and password using an input device provided in the user terminal 4, and is provided in the authentication screen after input. The “send” button is pressed using a pointing device such as a mouse provided in the user terminal 4. The user terminal 4 transmits an ID (user ID) and a password to the settlement system 23 based on the press signal. Upon receiving the ID (user ID) and password, the payment function unit 23b of the payment system 23 confirms that the combination of the received ID and password is stored in the authentication DB 23b, and performs user authentication (step S118). The settlement function unit 23b of the settlement system 23 transmits an authentication completion indicating that the authentication including the settlement (authentication) result (authentication OK, authentication NG) is completed to the settlement / fee collection agency system 24 (step S119).

  The settlement function unit 24e of the settlement / fee collection agency system 24 receives the completion of authentication from the settlement system 23, and the settlement function unit 24e responds to the settlement sequence number and settlement request Token transmitted and received by the service providing system 3 in step S111. In addition, the settlement result (authentication OK, authentication NG) is associated with each other and stored in the corresponding part of the settlement / billing management table 24c. The settlement function unit 24e of the settlement / fee collection agency system 24 creates a settlement token (information for identifying a settlement result) from the carrier code and settlement serial number of the record storing the settlement result, and associates it with the settlement result. And stored in the corresponding part of the settlement / billing management table 24c. Then, the settlement function unit 24e of the settlement / fee collection agency system 24 transmits the created settlement Token to the user terminal 4 (step S120). At this time, the user terminal 4 obtains the screen after completion of payment from the service providing system 3 based on the screen URL after completion of payment and displays it on the display unit, thereby confirming that the user has been authenticated by the payment system 3. I can know.

  When the user terminal 4 receives the payment Token from the payment / fee collection agency system 24, the user terminal 4 receives the payment serial number (the payment serial number transmitted in step S112 and received by the user terminal 4) and the payment Token (transmitted in step S120). The payment token received by the user terminal 4 is transmitted to the service providing system 3 (step S121). When the payment function unit 33 of the service providing system 3 receives the payment sequence number and the payment token from the user terminal 4, the payment function request 33 requests the payment result to the payment / fee collection agency system 24 (the received payment sequence number and The payment token and the business code of the service provider stored in its own system are transmitted (step S122).

  When receiving the settlement result request from the service providing system 3, the settlement function unit 24e of the settlement / fee collection agency system 24 performs settlement / billing management in association with the business code, settlement serial number, and settlement token included in the settlement result request. The settlement result (authentication OK, authentication NG) stored in the table 24c is taken out. Then, the settlement function unit 24e of the settlement / fee collection agency system 24 creates a settlement result Token (information for judging the validity of the billing request) from the carrier code and the settlement serial number of the record from which the settlement result is extracted. The created settlement result Token is stored in the corresponding part of the settlement / billing management table 24c in association with the business code, settlement serial number, and settlement Token included in the settlement result request. Then, the settlement function unit 24e of the settlement / fee collection agency system 24 transmits the settlement result, the user management number, and the settlement result Token to the service providing system 3, and the settlement function unit 33 of the service providing system 3 sends these pieces of information. Receive (step S123). However, the user management number is a number different from the user ID stored in the subscriber database 21 or the authentication DB 23a of the agency system 2, and the user management number is checked at a later date while preventing the service provider from impersonating the service user. The service provider can inquire about the billing status of the service user. The agency system 2 stores the user ID associated with the user ID.

  Thereby, the settlement (authentication) is performed by the settlement system 23 constructed by the settlement / charge collection agent, the service providing system 3 receives the result of the settlement (authentication) performed by the settlement system 23, and the service providing system 3 A settlement (authentication) result can be obtained.

  The charging function unit 34 of the service providing system 3 determines whether or not to charge the content, and determines that charging is performed in this sequence. Then, the billing function unit 34 creates a billing request sequence number by adding 1 to the previous billing request sequence number as a number for identifying the current billing (step S124). Then, the billing function unit 34 of the service providing system 3 sends a billing request (provider code, settlement serial number, settlement result token, billing request sequence number, service name, service name) The fee and type (including billing each time, monthly billing, etc.) are transmitted (step S125).

  Upon receiving a billing request from the service providing system 3, the billing function unit 24f of the settlement / charge collection agent system 24 stores the billing request in association with the business code and the settlement serial number included in the billing request and is stored in the settlement / billing management table 24c. The settlement result Token is taken out, and the retrieved settlement result Token is compared with the settlement result Token included in the billing request (step S126). If the payment results Token match, the charging function unit 24f of the payment / fee collection agency system 24 transmits the service name and the charge (step S127). Then, the billing processing unit 23c of the payment system 23 performs billing by associating the received service name with the user ID acquired from the user terminal 4 at the time of user authentication and storing it in a storage unit (not shown), The charging result, the charging reception date, and the reception number are transmitted to the settlement / fee collection system 24 (step S128). Upon receiving each piece of information from the settlement system 23, the billing function unit 24f of the settlement / fee collection agency system 24 transmits the received billing result, billing reception date / time, and receipt number to the service providing system 3 (step S129). The charging function unit 34 of the service providing system 3 receives each piece of information from the settlement / fee collection agency system 24, and the service providing receiving unit 3 transmits the service desired by the user to the user terminal 4 (step S130). ).

  As a result, fee collection (billing) is performed by the payment system 23 constructed by the payment / charge collection agent, the service providing system 3 receives the result of the billing performed by the payment system 23, and the service providing system 3 charges. The result can be obtained.

  As described above, the settlement / fee collection agency program creates a payment / fee collection agency program and stores it in the settlement / fee collection agency system 24, and requests the settlement / fee collection agency to perform the settlement / fee collection agency Since the service provider that calls and uses the settlement / fee collection agency program, it is possible to prevent the burden on both parties from increasing. In addition, since communication is performed using HTTPS and SSLv3 is used for the communication, it is not necessary to newly provide an entrance / exit in the firewall installed on the service providing system side.

  In the above embodiment, the service providing system 3 requests the settlement / fee collection agency system 24 to transmit an operation check program (operation confirmation program), and the program provision unit 24d of the settlement / fee collection agency system 24 Transmits an operation check program to the service providing system 3. Then, the service providing system 3 operates according to the operation check program, and checks whether or not it conforms to the data structure defined in the settlement / fee collection agency program when transmitting data to the settlement / fee collection agency system 24. You may make it confirm.

  Further, the service providing system 3 requests the settlement / fee collection agency system 24 to transmit a pseudo-settlement system program, and the program provision unit 24d of the settlement / fee collection agency system 24 sends a pseudo-settlement to the service provision system 3. Send the system program. The service providing system 3 operates according to the operation check program, and constructs the payment / fee collection agency system 24 and the payment system 23 in a pseudo manner (pseudo payment system unit 35), and the service providing system 3 includes a user. Connect a terminal instead of a terminal. Then, the simulated settlement / fee collection agency system and settlement system are operated as the settlement / fee collection agency system 24 and settlement system 23 in FIG. 4 to simulate the settlement / fee collection agency program and the operation program. Make sure to check.

  The preferred embodiments of the present invention have been described above, but the present invention is not limited to the above-described embodiments, and various design changes can be made as long as they are described in the claims. Yes.

1 is a system configuration diagram of an entire system including a settlement / fee collection agency system according to an embodiment of the present invention. The functional block diagram which shows the function structure of the payment and fee collection agency system of FIG. FIG. 3 is an explanatory diagram for explaining the settlement / billing management table of FIG. 2. The sequence diagram which shows the flow of the process of the payment and fee collection agent of FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 System 2 Agency system 3 Service provision system 23 Settlement system 24 Settlement / fee collection agency system

Claims (3)

Settlement and fee collection agency provided on behalf of the provider and agency of payment and fee collection connected to the provider side system provided on the provider side requesting settlement and fee collection agency A system,
A settlement / fee collection agency program storage means for storing a settlement / fee collection agency program describing a processing procedure performed when the provider side system requests the settlement / fee collection agency system for settlement and fee collection agency;
Upon receiving a request for the settlement / fee collection agency program from the provider side system, the settlement / fee collection agency program stored in the settlement / fee collection agency program storage means is transmitted to the provider side system that is the request source. A settlement / fee collection agency program transmission means to transmit,
A payment / fee collection agency system characterized by Whether the data to be transmitted when transmitting data from the provider side system to the payment / charge collection agency system according to the payment / charge collection agency program has a data structure defined in the payment / charge collection agency program Operation confirmation program storage means for storing an operation confirmation program for causing the provider side system to confirm
An operation confirmation program transmitting means for transmitting the operation confirmation program stored in the operation confirmation program storage means to the requesting provider side system upon receiving an operation confirmation program request from the provider side system; ,
The payment / charge collection agent system according to claim 1, further comprising: A system that performs processing performed by the settlement / fee collection agency system in the settlement / fee collection agency is constructed in a pseudo manner in the provider side system, and the settlement / fee collection agency is included in the pseudo-built system. Pseudo payment system program storage means for storing a pseudo payment system program for performing processing performed by the system;
When receiving a request for a pseudo payment system program from the provider side system, an operation confirmation program for transmitting the pseudo payment system program stored in the pseudo payment system program storage means to the requesting provider side system A transmission means;
The payment / fee collection agency system according to claim 1 or 2, further comprising:

Images