JP5236594B2 - Transaction support system, transaction support method, and transaction support program - Google Patents

Description

  The present invention relates to a transaction support system, a transaction support method, and a transaction support program that support accurate refund processing when a refund reason occurs in a transaction involving the transfer of funds.

  Today, in transactions between companies and customers, refunds may occur after payment. In such a case, the paid price is refunded from the company to the customer. When such a refund reason occurs, a technique for refunding while reducing an economic burden such as a transfer fee has been studied (for example, see Patent Document 1). In the technique described in this document, a refund agent request including a refund amount and customer specifying information for specifying a customer to be refunded is accepted. Then, an e-mail including the location of the site to be accessed to receive a refund is delivered with the customer's e-mail address as the destination. When the customer accesses the site, the electronic money entity that gives value to the electronic money is instructed to give the electronic money that the customer can use for payment of the commercial transaction to a value corresponding to the refund amount.

  In addition, when a user who has already paid for a mail-order item cancels the purchase of the mail-order item, a technique for offsetting the new payment amount and the scheduled refund amount is also being considered (for example, (See Patent Document 2). In the technology described in this document, when a user who has already paid for a mail-order item cancels the purchase, the refund amount is recorded in the refund information table. Furthermore, when a user accepts a mail-order item that he / she wishes to make a new purchase and records the payment amount, if the user's expected refund amount is recorded in the table, the payment amount will be refunded. The planned amount is automatically subtracted.

Japanese Patent Laying-Open No. 2003-108904 (first page, FIG. 1) Japanese Patent Laying-Open No. 2005-316753 (first page, FIG. 1)

  In Patent Document 1, a refund is made using electronic money. However, since this electronic money can be used only for a predetermined purpose commercial transaction, it may be inconvenient for the user. For this reason, there may be a case where a refund by a transfer to a user's deposit account or the like is desired.

  On the other hand, the cited document 2 discloses an offset process for refund. However, in the case of offsetting, new transactions are required. Here, when there is no plan of a new transaction, it cannot be refunded smoothly.

  In addition, when cash is refunded by transfer or the like, it is necessary for another person impersonating the person to receive the refund amount as the receiving side, or for the remittance side to suppress the transfer to the wrong account. Furthermore, there are cases where a company that has made a transaction wants to specify a refund method and a refund condition. Such refund methods and refund conditions differ depending on the company that performs the refund.

  The present invention has been made in order to solve the above problems, and its purpose is to provide a transaction support system for supporting an accurate refund process when a refund reason occurs in a transaction involving the transfer of funds, It is to provide a transaction support method and a transaction support program.

  In order to solve the above-mentioned problem, the invention according to claim 1 is paid from the second user to the first user for a transaction performed between the first user and the second user. Transaction information storage means for storing refund amount information for the second user, refund condition information storage means for recording a refund condition for each first user, and control means connected to the financial institution system A means for acquiring refund information for the second user from the first user when the control means receives an access from the client terminal of the second user; Means for obtaining a refund condition for the first user from the refund condition information storage means; means for obtaining information on a refund destination account from the client terminal of the second user; and the refund for the refund destination account. It determined whether to satisfy the matter, when satisfying the refund conditions are summarized as further comprising a means for transmitting a transfer execution instruction for the refund information to the financial institution system.

According to a second aspect of the present invention, in the transaction support system according to the first aspect, an evaluation value for evaluating a refund destination account is recorded in the refund condition information storage unit as a refund condition. A means for calculating a total value of evaluation values for a refund destination account acquired from the client terminal of the second user, and an error handling when the total value exceeds a preset reference value The gist of the present invention is that it further includes means for executing processing.

  The invention according to claim 3 is the transaction support system according to claim 1 or 2, wherein the refund condition recorded in the refund condition information storage means is composed of a plurality of items for the transfer, When an evaluation value for evaluating satisfaction of the refund condition is set, and the control means calculates the total value of the evaluation values of each item, and the total value exceeds a preset reference value The gist of the invention is that it further comprises means for executing an error handling process.

  According to a fourth aspect of the present invention, in the transaction support system according to any one of the first to third aspects, the refund condition information storage means evaluates when the existence of an account cannot be confirmed as the refund condition. If the value is recorded and the control means obtains the existence information of the refund destination account from the financial institution system and the existence of the account cannot be confirmed, the control means calculates a total value obtained by adding the evaluation value. The gist.

  The invention according to claim 5 is the transaction support system according to any one of claims 1 to 4, wherein the transaction support system is information on a destination financial institution having an account used for payment by the second user. The refund condition information storage means stores an evaluation value for evaluating a mismatch between the refund destination account and the destination financial institution information, as the refund condition. The gist of the invention is that the control means calculates a total value obtained by adding the evaluation values when the refund destination account and the destination financial institution information do not match.

  According to a sixth aspect of the present invention, in the transaction support system according to the fourth or fifth aspect, the refund condition information storage means includes, as the refund condition, the name of the holder of the refund destination account and the name of the second user. When the evaluation value for evaluating the inconsistency is recorded, the control means compares the name of the holder acquired in the account confirmation information with the name of the user of the second user. The gist is to calculate a total value obtained by adding the evaluation values.

  According to a seventh aspect of the invention, in the transaction support system according to any one of the first to sixth aspects, an evaluation value is recorded as the refund condition corresponding to a refund amount range in the refund condition information storage unit. The control means obtains an evaluation value corresponding to a refund amount range including a refund expected amount in the refund information for the second user from the first user, and adds the evaluation value to the total value The gist is to calculate.

  According to an eighth aspect of the present invention, the transaction information storage means further records information relating to a non-payment amount from the second user to the first user, and the control means uses the second usage information. The present invention further includes means for outputting a message for confirming whether or not there is a desire to cancel the billed amount and the refunded amount.

  The invention according to claim 9 is the transaction support system according to any one of claims 1 to 8, wherein the transaction information storage means further records information related to a refund due date allowing a refund, The gist of the invention is that the control means further comprises means for notifying the second user when the refund amount information that has passed the refund deadline remains.

  The invention according to claim 10 is the second use of the amount paid from the second user to the first user for the transaction performed between the first user and the second user. Using a transaction support system comprising transaction information storage means for accumulating refund amount information for a user, refund condition information storage means for recording a refund condition for each first user, and control means connected to a financial institution system A method of performing transaction support processing, wherein the control means obtains refund information for the second user from the first user when the control means receives an access from the client terminal of the second user. Obtaining a refund condition for the first user from the refund condition information storage means, obtaining information about a refund destination account from the client terminal of the second user, and Determining whether or not the refund condition is satisfied and, if the refund condition is satisfied, executing a step of transmitting a transfer execution instruction for the refund information to the financial institution system. .

  The invention according to claim 11 is the second use of the amount paid from the second user to the first user for the transaction performed between the first user and the second user. Using a transaction support system comprising transaction information storage means for accumulating refund amount information for a user, refund condition information storage means for recording a refund condition for each first user, and control means connected to a financial institution system A program for performing transaction support processing, wherein the control means obtains refund information for the second user from the first user when access from the client terminal of the second user is received. Means for acquiring the refund condition of the first user from the refund condition information storage means, means for acquiring information relating to the refund destination account from the client terminal of the second user, and the refund destination account. The determination whether to satisfy the refund conditions, when satisfying the refund conditions are summarized in that to function as means for transmitting a transfer execution instruction for the refund information to the financial institution system.

(Function)
According to the invention described in claim 1, 10 or 11, when the control means receives access from the client terminal of the second user, it obtains refund information for the second user from the first user. Next, the refund condition of the first user is acquired from the refund condition information storage means, and information on the refund destination account is acquired from the client terminal of the second user. Then, it is determined whether or not the refund condition is satisfied for the refund destination account. When the refund condition is satisfied, a transfer execution instruction for the refund information is transmitted to the financial institution system. Thereby, about the refund destination account set up by the 2nd user, refund can be performed according to the 1st user's refund conditions.

According to the invention described in claim 2, when the total value of the evaluation values for the refund destination account acquired from the second user's client terminal is calculated, and the total value exceeds a preset reference value, Execute error handling processing. Thereby, satisfaction of refund conditions can be determined using the total value of evaluation values.

According to the third aspect of the present invention, the control means calculates the total value of the evaluation values of each item, and executes the error handling process when the total value exceeds a preset reference value. This
Even when there are problems in a plurality of items, the evaluation can be performed in an integrated manner.

  According to the fourth aspect of the present invention, the control means acquires the presence information of the refund destination account from the financial institution system, and calculates the total value obtained by adding the evaluation values when the existence of the account cannot be confirmed. Thereby, a problem can be detected when the existence of an account cannot be confirmed.

  According to the fifth aspect of the present invention, when the refund destination account and the destination financial institution information do not match, the control means calculates a total value obtained by adding the evaluation values. Thereby, even when the transfer to the destination financial institution is a condition, satisfaction of the refund condition can be determined using the evaluation value.

  According to the invention described in claim 6, the control means compares the name of the holder acquired in the confirmation information of the existence of the account and the name of the user of the second user. Calculate the total sum. Thereby, even when the transfer to the account in the name of the person is a condition, satisfaction of the refund condition can be determined using the evaluation value.

  According to the seventh aspect of the present invention, the control means obtains an evaluation value corresponding to the refund amount range including the refund amount in the refund information from the first user to the second user, and adds the evaluation value. Calculate the total value. As a result, the error handling can be changed according to the scheduled refund amount.

  According to the invention described in claim 8, the control means outputs a message for confirming whether or not there is a desire to cancel the charge amount and the refund amount to the second user. As a result, a refund can be made by offsetting the billing amount.

  According to the ninth aspect of the present invention, the control means notifies the second user when the refund amount information that has passed the refund due date remains. Thereby, the state where refund remains over a long period of time can be suppressed.

  According to the present invention, when a refund reason occurs in a transaction involving the transfer of funds, it is possible to support an accurate refund process.

The system schematic of embodiment of this invention. It is explanatory drawing of the data used by this embodiment, Comprising: It records in (a) company management data storage part, (b) user management data storage part, (c) billing management data storage part, (d) refund management data storage part Explanatory drawing of made data. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment. Explanatory drawing of the process sequence of this embodiment.

Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, a description will be given of a transaction support system, a transaction support method, and a transaction support program used when a user and a company conduct a transaction and transfer funds related to the transaction. In this case, the company (first user) provides a transaction product to the user (second user) and makes a bill for this transaction. On the other hand, when the user returns the transaction product, the company gives a refund to the user.

  In the present embodiment, a transaction support server 20 shown in FIG. 1 is used to provide a service that supports transactions between a user and a company. This transaction support server 20 is connected to the client terminal 10, the company server 30, and the financial institution system 40 via the Internet.

  The client terminal 10 is a computer terminal used by a user who makes a transaction with a company. The client terminal 10 includes a display unit configured from a display or the like, and an input unit configured from a keyboard, a pointing device, or the like.

  The transaction support server 20 is a server computer for supporting transactions performed between a user and a company. This transaction support server 20 includes a control unit 21, a company management data storage unit 22, a user management data storage unit 23, a billing management data storage unit 24, a refund management data storage as a control means constituted by a CPU, a RAM, a ROM, and the like. The unit 25 is provided. Here, the company management data storage unit 22 functions as a refund condition information storage unit, and the user management data storage unit 23 functions as a user information storage unit. Further, the billing management data storage unit 24 and the refund management data storage unit 25 function as transaction information storage means.

  Here, the control unit 21 performs processes (each process such as a company management stage, a refund management stage, a transfer management stage, and a time limit management stage) described later. Then, as shown in FIG. 1, the control unit 21 uses a transaction support program to execute a company management unit 211, a transaction information management unit 212, a user authentication unit 213, a refund management unit 215, a transfer management unit 216, a term management unit 217, etc. Function as.

The company management unit 211 performs login authentication in response to an access from the company server 30 or a person-in-charge terminal of the company.
The transaction information management means 212 acquires transaction information from the company server 30 and records billing information and refund information. In addition, in response to a billing status inquiry or a refund status inquiry from a company's person in charge terminal, billing or refund status information is provided. Further, when receiving an instruction for unlocking the user management code from the person in charge at the company, the user management code is unlocked.

The user authentication unit 213 performs user authentication in response to access from the client terminal 10.
The refund management means 215 executes processing for acquiring refund information for the user from the company. Specifically, the refund management means 215 executes offset or transfer management processing according to the refund method designated by each company.

  The transfer manager 216 acquires information about the refund condition and the refund destination account, and executes a process of determining whether or not the refund destination account satisfies the refund condition. When the condition is satisfied, the transfer management unit 216 executes a transfer process for refund. In order to perform this processing, the transfer management means 216 holds data relating to an account confirmation service providing time zone in which the financial institution system 40 can be used, a transfer service providing time zone, and data relating to an account identifier of each company. The transfer management means 216 includes a total value memory, and stores a total value of evaluation values of errors generated in the refund transfer process.

  The term management means 217 manages a term that allows a refund to the user. Specifically, if the refund remains in an unpaid state even when this time limit has arrived, the time limit management means 217 notifies the company server 30 that makes this refund. In this case, the person in charge of the company confirms the situation and takes measures such as contacting the user as necessary.

  As shown in FIG. 2A, a company management record 220 for each company using this service is recorded in the company management data storage unit 22. This company management record 220 is registered when a company uses a transaction support service. The company management record 220 includes data related to a company management code, a password, a contact information, a refund method, a refund condition, and an error handling type.

In the company management code data area, data relating to an identifier for identifying a company that uses this service is recorded.
Data related to a password for authenticating the company is recorded in the password data area.

In the contact data area, data relating to a contact (here, a mail address) for sending a notification to this company is recorded.
In the refund method data area, a flag for specifying a refund method when a refund is given from the company to the user is recorded. In the present embodiment, a flag specifying “transfer” or “offset” is recorded. Here, when a plurality of refund method flags are recorded, the user can select a refund method.

  In the refund condition data area, data relating to conditions for allowing refund is recorded. For example, as a refund condition, if the account of the refund destination is limited to the account of the destination financial institution used for payment by the user, a destination financial institution restriction flag is recorded. In addition, when a match between the name of the transferee account and the user name is a refund condition, a transferee holder restriction flag is recorded.

  In addition, in the refund condition data area, a weighting value (refund destination account specified by the company) corresponding to a plurality of items (error types) for transfer such as inconsistency of the destination financial institution, account existence confirmation not possible, and name holder mismatch. Data relating to an evaluation value for evaluation) is recorded.

Furthermore, in the refund condition data area, data relating to a reference value (management level value) for determining whether or not an error handling described later is necessary according to an error situation is recorded.
In the error handling type data area, a flag for specifying a handling method according to the total value of evaluation values of errors generated in the refund transfer process is recorded. In the present embodiment, a flag of “only notification to company” or “user management code lock” is recorded.

  In the user management data storage unit 23, as shown in FIG. 2B, a user management record 230 for each user who uses this service is recorded. This user management record 230 is registered when information about a user who uses the transaction support service is acquired. This user management record 230 includes a user management code, a password, a user name, contact information, destination financial institution information, and a transaction stop flag.

Data relating to an identifier for specifying each user is recorded in the user management code data area.
Data relating to a password for authenticating the user is recorded in the password data area.

In the user name data area, data relating to the name and name of the user is recorded.
In the contact data area, data relating to a contact (here, a mail address) for sending a notification to this user is recorded.

In the destination financial institution information data area, data related to the destination financial institution used when the user pays the billing amount is recorded. In the present embodiment, data related to the financial institution code of the destination financial institution and the head office code are recorded. This destination financial institution information is updated every time the user pays.

  In the transaction stop flag data area, a flag for determining whether or not a transaction with this user is possible is recorded. In this embodiment, when a transaction stop flag is recorded in this data area, refund for this user is stopped.

  As shown in FIG. 2 (c), the billing management data storage unit 24 records a billing management record 240 for billing made by a company to a user. This billing management record 240 is registered when billing information is acquired from the company server 30. The billing management record 240 includes data relating to a company management code, a user management code, a transaction management code, a billing amount, and a payment status.

Data relating to an identifier for identifying the billing company is recorded in the company management code data area.
In the user management code data area, data relating to an identifier for identifying the billing user is recorded.

Data relating to an identifier for identifying each transaction is recorded in the transaction management code data area.
In the billing amount data area, data relating to the amount billed from the company to the user is recorded.

  In the deposit status data area, a flag for specifying the payment status for this bill is recorded. In this embodiment, a flag for specifying “not paid”, “paid”, and “refund” is recorded in this data area.

  In the refund management data storage unit 25, as shown in FIG. 2D, a refund management record 250 for a refund paid from the company to the user is recorded. This refund management record 250 is registered when refund information is acquired from the company server 30. The refund management record 250 includes data relating to a company management code, a user management code, a scheduled refund amount, a time limit, a transfer account, and a refund status.

In the company management code data area, data relating to an identifier for specifying a requesting company to be refunded is recorded.
In the user management code data area, data relating to an identifier for specifying a user who receives a refund is recorded.

In the scheduled refund amount data area, data relating to the refund amount paid to the user is recorded.
In the time limit data area, data related to a time limit permitting refund is recorded. In this data area, the date after a predetermined period after the return is confirmed is set.

  In the transfer destination account data area, data related to a transfer destination account identifier (financial institution code, main branch code, deposit type, account number, etc.) for specifying a refund destination account and data on account holder information are recorded.

In the refund status data area, a flag for specifying the payment status for the refund is recorded. In the present embodiment, in this data area, a flag for identifying each status of “unrefunded”, “refunded”, and “refunded (error)” is recorded. The “non-refundable” flag indicates that it has not been refunded yet. The “refunded” flag indicates that a refund has been made without an error, and the “refunded (error)” flag indicates that a part of the error has occurred but has been refunded.

  The company server 30 is a server computer for managing transactions with users in the company. The company server 30 includes a customer management data storage unit, a product management data storage unit, and a transaction management data storage unit.

  The customer management data storage unit stores customer management records for managing users who conduct transactions with the company. The customer management record includes data related to a user management code and a password of a user who makes a transaction with the company.

In the user management code data area, data relating to an identifier for specifying each user who conducts business with this company is recorded.
Data relating to a password for authenticating the user is recorded in the password data area.

  The merchandise management data storage unit stores merchandise management records for managing the merchandise sold by the company. This merchandise management record includes data related to merchandise management codes and merchandise prices of merchandise to be traded.

Data relating to an identifier for specifying each product is recorded in the product management code data area.
In the product price data area, data relating to the sales price of this product is recorded.

  The transaction management data storage unit stores transaction management records for managing transactions between the company and customers. This transaction management record includes data relating to a transaction management code, a product management code, a user management code, a charge amount, and a transaction status.

Data relating to an identifier for identifying each transaction is recorded in the transaction management code data area.
In the product management code data area, data relating to an identifier for specifying a product to be traded in this transaction is recorded.

In the user management code data area, data relating to an identifier for specifying the user who has made this transaction is recorded.
In the billing amount data area, data relating to the amount billed to the user in this transaction is recorded.

  In the transaction status data area, a flag for specifying the status of the transaction is recorded. In the present embodiment, in this data area, flags for specifying “not yet received”, “paid”, “return receipt”, and “return confirmation” are recorded.

  The financial institution system 40 is a computer system of a financial institution that manages data related to the account holders and account balances of accounts opened in each financial institution. The financial institution system 40 includes a deposit account database. In this deposit account database, account data relating to a deposit account opened in a financial institution is recorded. This account data is registered when an account is opened in a financial institution. The account data includes data related to an account identifier, account holder information, account balance, and the like.

In the account identifier data area, data relating to an identifier (financial institution code, main branch code, deposit type, account number, etc.) for specifying the opened account is recorded.
In the account holder data area, data for specifying an account holder (account holder name, customer code, etc.) related to this account is recorded.
In the account balance data area, data for specifying the balance of the account is recorded.

  A processing procedure in the case of supporting the transfer of funds for a transaction performed between a user and a company using the system configured as described above will be described with reference to FIGS.

(Billing process)
First, referring to FIG. 3, a billing process for a product purchased by a user will be described.
Here, the client terminal 10 executes an access process for the company server 30 (step S1-1). Specifically, when purchasing a product, the user accesses the corporate server 30 using the client terminal 10.

  Next, the company server 30 executes user authentication processing (step S1-2). Specifically, the company server 30 provides a user authentication screen to the client terminal 10. This user authentication screen is provided with user management code and password input fields and a transmission execution icon. Here, the user sets the user management code and password in the input field, and selects a transmission execution icon. In this case, the client terminal 10 transmits a login request including the user management code and password to the company server 30.

  The company server 30 that has received the login request performs user authentication using the acquired user management code and password. When the user authentication is completed, the company server 30 searches the transaction management data storage unit for a transaction management record in which the user management code is recorded. Then, the presence / absence of a transaction management record in which “return confirmation” is recorded as the transaction status is determined. Here, when there is no transaction management record in which “return confirmation” is recorded, the company server 30 transmits a normal menu screen to the client terminal 10. On this menu screen, a product catalog icon and a return request icon are provided.

  Next, the client terminal 10 transmits a transaction request to the company server 30 (step S1-3). Here, when purchasing a product, a product purchase icon is selected. In this case, the client terminal 10 transmits a product catalog request to the company server 30.

  Next, the client terminal 10 and the company server 30 execute transaction processing. Specifically, the company server 30 that has received the product catalog request provides the client terminal 10 with a product catalog screen for products stored in the product management data storage unit. This product catalog screen is provided with a product icon in which a product management code is set in order to select each product. The user checks the product catalog screen displayed on the display of the client terminal 10 and selects the product icon of the desired product. In this case, the client terminal 10 transmits a product purchase transaction request to the company server 30. This transaction request includes a merchandise management code to be purchased.

  Next, the company server 30 executes transaction acceptance processing (step S1-4). Specifically, the company server 30 that has received the transaction request calculates a charge amount based on the product price associated with the product management code to be purchased. Then, the company server 30 assigns a transaction management code to the transaction request, and generates a transaction management record in which the transaction management code, the product management code, the user management code, and the billing amount are recorded.

  Furthermore, the company server 30 executes a billing information registration process (step S1-5). Specifically, the company server 30 provides billing information to the transaction support server 20. This billing information includes a company management code, a password, a user management code, a transaction management code, and data related to the billing amount. Furthermore, the company server 30 outputs a message about a payment request for a commodity price (billed amount) to the client terminal 10. This message includes a transaction management code used at the time of deposit.

  Next, the control unit 21 of the transaction support server 20 executes billing information accumulation processing (step S1-6). Specifically, the company management unit 211 of the control unit 21 performs login authentication using the acquired company management code and password. When the login authentication is completed, the transaction information management unit 212 generates a billing management record 240 including data on the company management code, the user management code, the transaction management code, and the billing amount included in the billing information, and stores the billing management data storage Register in the unit 24. At this stage, the transaction information management means 212 records the “not yet received” flag as the deposit status of the billing management record 240.

  Then, the user executes a payment process (step S1-7). In the present embodiment, the client terminal 10 is used to access the financial institution system 40, and the product price is transferred to the account of the company that has made the transaction. In this case, the transaction processing code acquired from the company server 30 is set and the transfer process is performed.

  Next, the company server 30 executes a payment confirmation process (step S1-8). Specifically, the company server 30 periodically accesses the financial institution system 40. Then, the company server 30 confirms payment to the company account. The company server 30 confirming the payment specifies a transaction management code included in the payment information. Then, the company server 30 records the “paid” flag in the transaction management record in which the acquired transaction management code is recorded. Next, the company server 30 outputs an instruction to ship the purchased product with the specified transaction management code to the user.

  Next, the company server 30 executes a payment information registration process (step S1-9). Specifically, the company server 30 provides payment information to the transaction support server 20. This payment information includes a company management code, a password, a specified transaction management code, and data relating to destination financial institution information used for payment.

  In this case, the transaction support server 20 executes a deposit information accumulation process (step S1-10). Specifically, the company management unit 211 of the control unit 21 executes login authentication using the acquired company management code and password and the company management data storage unit 22. When the login authentication is completed, the transaction information management unit 212 extracts the charge management record 240 in which the acquired transaction management code is recorded from the charge management data storage unit 24. Then, the transaction information management means 212 records a “paid” flag as the payment status of the billing management record 240. Further, the transaction information management means 212 records the destination financial institution information in the user management record 230 of this user.

(Refund procedure)
Next, the refund procedure when the user who acquired the purchased product returns the product will be described. In this case, the company refunds the product price acquired from the user.

  First, similarly to step S1-1, the client terminal 10 executes an access process for the company server 30 (step S2-1). Then, similarly to step S1-2, the company server 30 executes user authentication processing (step S2-2). When the user authentication is completed, the company server 30 transmits a menu screen to the client terminal 10. On this menu screen, a product catalog icon and a return request icon are provided.

  Next, a return request process is executed using the client terminal 10 (step S2-3). Here, when a return of goods is desired, a return request icon is selected. In this case, the client terminal 10 transmits a return procedure request to the company server 30.

  In this case, the company server 30 executes a return request acceptance process (step S2-4). Specifically, the company server 30 specifies a product that can be returned from among the products purchased by the user from the transaction management data storage unit. Then, the company server 30 provides the client terminal 10 with a return screen for products that can be returned. This return screen is provided with a product icon in which a transaction management code is set in order to select a transaction to be returned. The user confirms the return screen displayed on the display of the client terminal 10 and selects a product icon of a desired product. In this case, the client terminal 10 transmits the return specific information to the company server 30. This return specifying information includes a transaction management code to be returned.

  And a user returns goods (step S2-5). Specifically, the user returns the purchased product to the company. Then, the company confirms the returned merchandise (step S2-6). Specifically, the person in charge of the company who has confirmed the returned merchandise identifies the transaction management record recorded in the transaction management data storage unit of the company server 30 and sets “return confirmation” as the transaction status.

  In this case, the company server 30 executes a refund information registration process (step S2-7). Specifically, the company server 30 transmits refund information to the transaction support server 20. This refund information includes a company management code, a password, and data relating to a transaction management code for which a return has been made.

  Next, the control unit 21 of the transaction support server 20 executes a refund information accumulation process (step S2-8). Specifically, the company management unit 211 of the control unit 21 performs login authentication using the acquired company management code and password. When the login authentication is completed, the transaction information management unit 212 extracts the billing management record 240 in which the transaction management code is recorded from the billing management data storage unit 24. Then, the transaction information management unit 212 records a “refund” flag in the deposit status of the billing management record 240. Further, the transaction information management unit 212 generates a refund management record 250 including data on the company management code, the user management code, and the scheduled refund amount, and registers it in the refund management data storage unit 25. Further, the transaction information management means 212 calculates a time limit obtained by adding a predetermined refund period to the current date, and records it in the time limit data area of the refund management record 250. At this stage, an “unrefunded” flag is recorded in the refund status data area.

(Re-access processing)
Next, processing when the user accesses the corporate server 30 again will be described with reference to FIG.

  First, similarly to step S1-1, the client terminal 10 executes an access process for the company server 30 (step S3-1). Then, similarly to step S1-2, the company server 30 executes a user authentication process (step S3-2). When the user authentication is completed, the company server 30 searches the transaction management data storage unit for a transaction management record in which the user management code is recorded. Then, the presence / absence of a transaction management record in which “return confirmation” is recorded as the transaction status is determined. Here, when there is a transaction management record in which “return confirmation” is recorded, the company server 30 executes a refund information acquisition process (step S3-3). Specifically, the company server 30 acquires a transaction management code and a product management code from a transaction management record in which “return confirmation” is recorded.

  Then, the company server 30 executes a refund guidance screen output process (step S3-4). Specifically, the company server 30 generates a refund guidance screen including a message indicating that there is a refund on the menu screen transmitted to the client terminal 10. This message includes a transaction management code and a product management code acquired from the transaction management record, and also includes a link icon for accessing the transaction support server 20. Then, the company server 30 transmits a refund guidance screen to the display of the client terminal 10.

Next, the client terminal 10 executes link processing (step S3-5). Specifically, when the user receives a refund, the link icon included in the refund guidance screen displayed on the display of the client terminal 10 is selected. In this case, the client terminal 10 transmits a refund request to the transaction support server 20.
And the transaction assistance server 20 performs the refund process mentioned later (step S3-6).

(Refund processing)
Next, refund processing in the transaction support server 20 will be described with reference to FIG.

  The control unit 21 of the transaction support server 20 executes user authentication processing (step S4-1). Specifically, the user authentication unit 213 of the control unit 21 provides a user authentication screen to the client terminal 10. This user authentication screen includes an input field for a user management code. When the user management code is set in this input field, the client terminal 10 transmits the user management code to the transaction support server 20.

  In this case, the user authentication unit 213 determines whether or not the acquired user management code and password are recorded in the user management data storage unit. When the user management record 230 in which the acquired user management code and password are recorded can be extracted, the user authentication unit 213 checks whether or not a transaction stop flag is recorded in the user management record 230. If a transaction stop flag is recorded, the user's access is denied.

  Next, the control unit 21 of the transaction support server 20 executes refund information extraction processing (step S4-2). Specifically, the refund management means 215 of the control unit 21 is a refund management record 250 in which the acquired user management code is recorded from the refund management data storage unit 25, and an “unrefunded” flag is displayed in the refund status data area. Get the record where is recorded.

  Next, the control unit 21 of the transaction support server 20 executes processing for specifying a company-specified refund method (step S4-3). Specifically, the refund management means 215 of the control unit 21 specifies the company management code recorded in the refund management record 250, and the company management record 220 in which the company management code is recorded is stored in the company management data storage unit 22. get. And it specifies based on the flag recorded on the refund method data area recorded on the company management record 220.

  Next, the control part 21 of the transaction assistance server 20 performs the determination process about whether the refund method can be selected (step S4-4). Specifically, the refund management means 215 of the control unit 21 determines whether or not a plurality of refund method flags are recorded in the refund method data area. Further, the refund management means 215 extracts the billing management record 240 in which the company management code and the user management code are recorded from the billing management data storage unit 24. Then, the refund management means 215 determines whether or not there is a billing management record 240 in which the “non-payment” flag is recorded.

When a plurality of refund method flags are recorded in the company management record 220, and the non-paid bill management record 240 is extracted for this user, it is possible to select cancellation or transfer. On the other hand, when the only refund method is defined in the company management record 220, or when the non-paid bill management record 240 to be offset cannot be extracted, the refund method cannot be selected. If there is no non-paid billing management record 240, only refund by transfer is made.

  When the refund method can be selected (in the case of “YES” in step S4-4), the control unit 21 of the transaction support server 20 executes the output process of the refund method selection screen (step S4-5). Specifically, the refund management means 215 of the control unit 21 outputs a refund method selection screen on the display of the client terminal 10. In this selection screen, a radio button for selecting cancellation or transfer is provided. And the refund management means 215 acquires the refund method selected on this selection screen.

  On the other hand, when the refund method cannot be selected (in the case of “NO” in step S4-4), the control unit 21 of the transaction support server 20 executes a refund method specifying process (step S4-6). Specifically, the refund management means 215 of the control unit 21 outputs a message indicating that a refund will be performed by the refund method specified on the display of the client terminal 10.

  Next, the control part 21 of the transaction support server 20 performs the transfer or cancellation determination process (step S4-7). Specifically, the refund management means 215 of the control unit 21 specifies the refund method selected or specified in the previous step.

  When refund by transfer is selected or specified (in the case of “transfer” in step S4-7), the control unit 21 of the transaction support server 20 executes a refund transfer process described later (step S4-8).

  On the other hand, when the refund by cancellation is selected or specified (in the case of “offset” in step S4-7), the control unit 21 of the transaction support server 20 performs a determination process as to whether or not the charged amount is equal to or more than the scheduled refund amount. Execute (Step S4-9). Specifically, the refund management means 215 of the control unit 21 compares the billing amount recorded in the billing management record 240 with the scheduled refund amount recorded in the refund management record 250.

  When the charged amount is equal to or more than the scheduled refund amount (in the case of “YES” in step S4-9), the control unit 21 of the transaction support server 20 executes a calculation process of the charged amount after offset (step S4-10). Specifically, the refund management means 215 of the control unit 21 calculates the remaining amount obtained by subtracting the scheduled refund amount from the charged amount. Then, the refund management means 215 updates the billing amount of the billing management record 240 using the remaining amount. Further, the refund management means 215 records a “refunded” flag in the refund status data area of the refund management record 250.

  Next, the control part 21 of the transaction assistance server 20 performs the output process of the after-offset amount (step S4-11). Specifically, the refund management means 215 of the control unit 21 outputs a content confirmation screen on the display of the client terminal 10. This content confirmation screen includes information on the billed amount after offset.

  On the other hand, when the scheduled refund amount is less than the billed amount (in the case of “NO” in step S4-9), the control unit 21 of the transaction support server 20 executes a process for updating the scheduled refund amount (step S4-12). Specifically, the refund management means 215 of the control unit 21 updates the scheduled refund amount of the refund management record 250 using the remaining amount obtained by subtracting the charged amount from the scheduled refund amount.

Next, the control part 21 of the transaction support server 20 performs the confirmation process of the offset content (step S4-13). Specifically, the refund management means 215 of the control unit 21 outputs a scheduled refund amount information screen to the display of the client terminal 10. This refund scheduled amount information screen includes information on the remaining scheduled refund amount. And the process after step S4-4 is repeated about the remaining refund amount of money.

(Refund transfer process)
Next, refund transfer processing (step S4-8) will be described with reference to FIG.
Here, the control part 21 of the transaction support server 20 performs the acquisition process of company management data (step S5-1). Specifically, the transfer management means 216 of the control unit 21 acquires data relating to the refund condition and the error handling type recorded in the company management data storage unit 22.

  Next, the control part 21 of the transaction assistance server 20 performs the output process of a transfer destination setting screen (step S5-2). Specifically, the transfer management unit 216 of the control unit 21 outputs a transfer destination setting screen on the display of the client terminal 10. This transfer destination setting screen is provided with an input field and a transmission execution icon for setting a deposit account as a transfer destination of the refund amount.

  Next, the control part 21 of the transaction assistance server 20 performs the transfer destination information acquisition process (step S5-3). Specifically, the user sets deposit account information of the deposit destination and selects a transmission icon. In this case, the client terminal 10 transmits the set deposit account information to the transaction support server 20. Then, the transfer management unit 216 of the control unit 21 acquires the deposit account information of the transfer destination from the client terminal 10.

  Next, the control part 21 of the transaction support server 20 performs the determination process about whether there is a restriction | limiting of a financial institution (step S5-4). Specifically, the transfer management means 216 of the control unit 21 determines whether or not the transfer to the destination financial institution is a refund condition in the company management record 220.

  When the destination financial institution restriction flag is recorded in the company management record 220 and the transfer destination is restricted to the destination financial institution (“YES” in step S5-4), the control unit 21 of the transaction support server 20 The destination financial institution information is acquired (step S5-5). Specifically, the transfer management unit 216 of the control unit 21 acquires the destination financial institution information recorded in the user management record 230.

  And the control part 21 of the transaction assistance server 20 performs the determination process about whether the transfer destination corresponds with the destination financial institution (step S5-6). Specifically, the transfer management means 216 of the control unit 21 compares the account information of the transfer destination account with the destination financial institution information. In the present embodiment, a match between the financial institution code and the main branch code is confirmed.

  If the transfer account information and the destination financial institution information do not match (in the case of “NO” in step S5-6), the control unit 21 of the transaction support server 20 executes an evaluation value addition process (step S5). -7). Specifically, the transfer management means 216 of the control unit 21 acquires an evaluation value corresponding to “destination financial institution mismatch” from the company management record 220 of this company. Then, the transfer management means 216 adds this evaluation value to the total value memory.

  On the other hand, when there is no restriction for the destination financial institution (in the case of “NO” in step S5-4), or when the transfer destination account information and the destination financial institution information match (in the case of “YES” in step S5-6) ), The process of step S5-7 is skipped.

Next, the control part 21 of the transaction support server 20 performs the determination process about whether it is within account confirmation service provision time (step S5-8). Specifically, the transfer management means 216 of the control unit 21 acquires the current date and time from the system timer. Then, the date and time are compared with the account confirmation service provision time zone provided in the financial institution system 40.

If it is not within the account confirmation service provision time (in the case of “NO” in step S5-8), a reception mail transmission process (step S6-15) described later is executed.
On the other hand, when it is within the account confirmation service provision time (in the case of “YES” in step S5-8), the control unit 21 of the transaction support server 20 executes an account existence check process (step S5-9). Specifically, the transfer management means 216 of the control unit 21 accesses the financial institution system 40. Then, the transfer management unit 216 transmits an account existence confirmation request to the financial institution system 40. This confirmation request includes the bank account information acquired from the client terminal 10.

  Next, as illustrated in FIG. 7, the control unit 21 of the transaction support server 20 executes a determination process as to whether there is an error (step S <b> 6-1). Specifically, the transfer management means 216 of the control unit 21 determines whether or not this account exists based on the account existence confirmation result acquired from the financial institution system 40.

  When it is not possible to confirm the existence of the account in the account existence confirmation result and an error occurs (in the case of “YES” in step S6-1), the control unit 21 of the transaction support server 20 executes an addition process of the evaluation value ( Step S6-2). Specifically, the transfer management means 216 of the control unit 21 acquires an evaluation value corresponding to “account existence confirmation impossible” from the company management record 220 of this company. Then, the transfer management means 216 adds this evaluation value to the total value memory.

  If the account existence confirmation result confirms the existence of the account and no error occurs (in the case of “NO” in step S6-1), the control unit 21 of the transaction support server 20 executes a name check process (step S61). S6-3). Specifically, the transfer management means 216 of the control unit 21 specifies the name of the name of the transfer destination account acquired in the account existence confirmation result.

  Next, the control part 21 of the transaction assistance server 20 performs the determination process about whether a nominee name corresponds (step S6-4). Specifically, the transfer management unit 216 of the control unit 21 compares the name of the transfer destination account acquired in the account existence confirmation result with the user name recorded in the user management record 230.

  When the name of the transfer account and the user name do not match (in the case of “NO” in step S6-4), the control unit 21 of the transaction support server 20 executes a determination process as to whether or not the transaction is handled (step S6-4). S6-5). Specifically, the transfer management means 216 of the control unit 21 makes a determination based on whether or not a transfer holder name restriction flag is recorded in the remittance conditions of the company management record 220.

  When the transfer holder name restriction flag is recorded and it is handled as an error (in the case of “YES” in step S6-5), the control unit 21 of the transaction support server 20 executes an evaluation value addition process. (Step S6-2). Here, specifically, the transfer management means 216 of the control unit 21 acquires an evaluation value corresponding to “name holder mismatch” from the company management record 220 of this company. Then, the transfer management means 216 adds this evaluation value to the total value memory.

And the control part 21 of the transaction support server 20 performs the determination process about whether the total value of the evaluation value exceeded the management level value (step S6-6). Specifically, the transfer management means 216 of the control unit 21 acquires the management level value recorded in the company management record 220. Then, the transfer management unit 216 compares the value recorded in the total value memory with the management level value recorded in the company management record 220.

  When the total value is less than or equal to the management level value (in the case of “NO” in step S6-6), the control unit 21 of the transaction support server 20 repeats the output process of the transfer destination setting screen (step S5-2). On the other hand, when the total value exceeds the management level value (in the case of “YES” in step S6-6), the control unit 21 of the transaction support server 20 executes an error handling type acquisition process (step S6-7). . Specifically, the transfer management unit 216 of the control unit 21 acquires the error handling type recorded in the company management record 220.

  Next, the control part 21 of the transaction assistance server 20 performs the determination process about whether it is a transaction stop (step S6-8). Specifically, the transfer management means 216 of the control unit 21 determines based on whether or not the “transaction stop” flag is recorded in the acquired error handling type.

  When the “transaction stop” flag is recorded as the error handling type and it is necessary to stop the transaction (in the case of “YES” in step S6-8), the control unit 21 of the transaction support server 20 locks the user management code. Processing is executed (step S6-9). Specifically, the transfer management means 216 of the control unit 21 records a transaction stop flag in the user management record 230. Then, the person in charge of the company accesses the transaction support server 20 and checks the transaction stop flag of the refund management record 250 accumulated in the refund management data storage unit 25 to grasp the transaction stop state for this user. be able to.

  Next, the control unit 21 of the transaction support server 20 executes a lock management process for the user management code (step S6-10). Specifically, the transfer management means 216 of the control unit 21 acquires the user's mail address from the user management data storage unit 23. Then, the transfer management unit 216 notifies the mail address that the user management code has been locked.

  When the “transaction stop” flag is not recorded as the error handling type and it is not necessary to stop the transaction (in the case of “NO” in step S6-8), the control unit 21 of the transaction support server 20 executes the error recording process. (Step S6-11). Specifically, the transfer management means 216 of the control unit 21 records a “refunded (error)” flag in the refund status data area of the refund management record 250. Then, the person in charge of the company checks the “refunded (error)” flag of the refund management record 250 stored in the refund management data storage unit 25 by the transaction support server 20, thereby indicating the error status for this user. I can grasp it.

  Next, the control part 21 of the transaction assistance server 20 performs the output process of a confirmation screen (step S6-12). Specifically, the transfer management means 216 of the control unit 21 outputs a message notifying the client terminal 10 that transfer is to be performed. In addition, when the holder name of the transfer account and the user name match (in the case of “YES” in step S6-4), the transfer holder name restriction flag is not recorded and is not handled as an error ( Also in the case of “NO” in step S6-5, this confirmation screen output process is executed.

  And the control part 21 of the transaction assistance server 20 performs the determination process about whether it is in the transfer service provision time (step S6-13). Specifically, the transfer management means 216 of the control unit 21 compares the current date and time with the transfer service providing time zone.

When the current date and time is within the transfer service providing time (in the case of “YES” in step S6-13), the control unit 21 of the transaction support server 20 executes a transfer request process (step S6-14). Specifically, the transfer management means 216 of the control unit 21 transmits a transfer request to the financial institution system 40. This transfer request includes an instruction to deposit the refund amount from the company account to the transfer destination account. Further, the transfer management means 216 records a “refunded” flag in the refund status data area of the refund management record 250.

  On the other hand, when the current date and time is not within the transfer service providing time (in the case of “NO” in step S6-13), the control unit 21 of the transaction support server 20 executes a reception mail transmission process (step S6-15). Specifically, the transfer management means 216 of the control unit 21 transmits to the client terminal 10 an email indicating that the transfer is to be performed during the transfer service provision time.

Next, the control part 21 of the transaction assistance server 20 performs a transfer request process, when it is within the transfer service provision time (step S6-16). This process will be described with reference to FIG.
The transfer management means 216 of the control unit 21 executes an account existence check process as in step S5-9 (step S7-1). If the account existence confirmation result confirms the existence of the account and no error occurs (in the case of “NO” in step S7-2), the control unit 21 of the transaction support server 20 performs the same as in step S6-3. A right holder name check process is executed (step S7-3). When the name of the transferee account and the user name match (in the case of “YES” in step S7-4), the transfer management means 216 executes the transfer request process in the same manner as in step S6-14. (Step S7-5). On the other hand, if the name of the transfer account and the user name do not match (in the case of “NO” in step S7-4), the transfer management means 216 determines whether or not to handle an error as in step S6-5. The determination process is executed (step S7-6). Even when it is not handled as an error (in the case of “NO” in step S7-6), the transfer request process is executed (step S7-5).

  On the other hand, when it is treated as an error (in the case of “YES” in step S7-6), the control unit 21 of the transaction support server 20 evaluates the evaluation value corresponding to “name holder mismatch” from the company management record 220. The acquisition process is executed (step S7-7). Further, similarly to step S6-7, an error handling type acquisition process corresponding to this evaluation value is executed (step S7-8). Here, when the “transaction stop” flag is not recorded as the error handling type and it is not necessary to stop the transaction (in the case of “NO” in step S7-9), the transfer management unit 216 executes step S6-11. , S6-14, an error recording process (step S7-10) and a transfer request process (step S7-5) are executed. When the transfer request is transmitted, the transfer management unit 216 records a “refunded” flag in the refund status data area of the refund management record 250.

  On the other hand, when it is not possible to confirm the presence of the account in the account existence confirmation result and an error occurs (in the case of “YES” in step S7-2), the control unit 21 of the transaction support server 20 executes the transfer impossible notification process. (Step S7-11). Specifically, the transfer management means 216 of the control unit 21 acquires the user's mail address from the user management data storage unit 23, and notifies the mail address that the transfer was not possible. In addition, when the “transaction stop” flag is recorded as the error handling type and the transaction stop is necessary (in the case of “YES” in step S7-9), the transfer management unit 216 performs the transfer impossible notification process. Execute (Step S7-11).

According to this embodiment, the following effects can be obtained.
(1) In this embodiment, a company management record 220 for each company that uses this service is recorded in the company management data storage unit 22. The company management record 220 includes data related to a company management code, a password, a contact information, a refund method, a refund condition, and an error handling type. And the control part 21 of the transaction assistance server 20 performs the specific process of the refund method designated by a company (step S4-3). When the refund method can be selected (in the case of “YES” in step S4-4), the control unit 21 of the transaction support server 20 executes the output process of the refund method selection screen (step S4-5). Thereby, the refund method and refund conditions can be set according to a company.

  (2) In this embodiment, the control part 21 of the transaction assistance server 20 performs the transfer destination information acquisition process (step S5-3). And the control part 21 of the transaction assistance server 20 performs the determination process about whether there is a restriction | limiting of a financial institution (step S5-4). When the destination financial institution restriction flag is recorded in the company management record 220 and the transfer destination is restricted to the destination financial institution (“YES” in step S5-4), the control unit 21 of the transaction support server 20 The destination financial institution information is acquired (step S5-5). If the transfer account information and the destination financial institution information do not match (in the case of “NO” in step S5-6), the control unit 21 of the transaction support server 20 executes an evaluation value addition process (step S5). -7). As a result, the transfer to the financial institution where the account used for payment by the user is established is used as a refund condition, and this condition can be evaluated based on the evaluation value, and an accurate refund can be performed.

  (3) In this embodiment, the control part 21 of the transaction assistance server 20 performs an account presence check process (step S5-9). When it is not possible to confirm the existence of the account in the account existence confirmation result and an error occurs (in the case of “YES” in step S6-1), the control unit 21 of the transaction support server 20 executes an addition process of the evaluation value ( Step S6-2). Thereby, since the evaluation value is repeatedly added for each error, the total value of the evaluation values becomes large. Accordingly, if an error repeatedly occurs in the transfer account confirmation or the name holder check (“YES” in steps S6-1 and S6-5), an error handling process can be executed.

  (4) In this embodiment, when the existence of the account can be confirmed in the account existence confirmation result (in the case of “NO” in step S6-1), the control unit 21 of the transaction support server 20 performs the name check process. Execute (Step S6-3). When the name of the transfer account and the user name do not match (in the case of “NO” in step S6-4), the control unit 21 of the transaction support server 20 executes a determination process as to whether or not the transaction is handled (step S6-4). S6-5). As a result, a refund to the same person as the payer can be used as a refund condition, and this condition can be evaluated based on the evaluation value, and an accurate refund can be performed.

  When the transfer holder name restriction flag is recorded (in the case of “YES” in step S6-5), the control unit 21 of the transaction support server 20 executes an evaluation value addition process (step S6-2). Thereby, when a holder is different, attention can be drawn by addition of an evaluation value.

  (5) In this embodiment, the control part 21 of the transaction support server 20 performs the determination process about whether the total value of the evaluation value exceeded the management level value (step S6-6). When the total value exceeds the management level value (in the case of “YES” in Step S6-6), the control unit 21 of the transaction support server 20 executes an error handling type acquisition process (Step S6-7). As a result, various types of error handling can be implemented by companies.

  Furthermore, when the “transaction stop” flag is recorded as the error handling type (in the case of “YES” in step S6-8), the control unit 21 of the transaction support server 20 executes the lock process of the user management code ( Step S6-9). Thereby, refund for this user can be stopped.

In addition, you may change each said embodiment as follows.
In the above embodiment, the transaction support server 20 includes the billing management data storage unit 24 and the refund management data storage unit 25. The billing management data storage unit 24 records a billing management record 240 for billing made from a company to a user. In the refund management data storage unit 25, a refund management record 250 for a refund paid from the company to the user is recorded. In the refund process, the transaction support server 20 uses the billing management record 240 and the refund management record 250. In this case, the billing management record 240 and the refund management record 250 may be acquired individually by accessing the company server 30.

  In the above embodiment, the company server 30 executes a billing information registration process (step S1-5), a payment information registration process (step S1-9), and a refund information registration process (step S2-7). Then, the company server 30 provides billing information, payment information, and refund information to the transaction support server 20. Instead, the person in charge of the company may use the client terminal 10 to provide the transaction support server 20 with billing information, payment information, and refund information.

  -In above-mentioned embodiment, the company server 30 performs a payment confirmation process (step S1-8). Instead of this, the transaction support server 20 may periodically access the financial institution system 40 to confirm payment to the company account. Then, the control unit 21 of the transaction support server 20 confirming the payment specifies the transaction management code included in the payment information, and extracts the billing management record 240 in which the transaction management code is recorded from the billing management data storage unit 24. . Thereby, the processing load of the company server 30 can be reduced.

  In the above embodiment, data related to the management level value for determining whether or not to perform error handling is recorded in the refund condition data area according to the error status. This management level value may be changed according to the range of the refund scheduled amount (return amount range). Specifically, a table or function for calculating the management level value is stored in the refund condition data area using the scheduled refund amount as a variable. Thereby, it is possible to determine whether or not error handling is necessary according to the scheduled refund amount. For example, careful refund processing can be executed when the scheduled refund amount is high, and simple refund processing can be performed when the scheduled refund amount is low.

  DESCRIPTION OF SYMBOLS 10 ... Client terminal, 20 ... Transaction support server, 21 ... Control part, 211 ... Company management means, 212 ... Transaction information management means, 213 ... User authentication means, 215 ... Refund management means, 216 ... Transfer management means, 217 ... Time limit Management means, 22 ... company management data storage unit, 23 ... user management data storage unit, 24 ... billing management data storage unit, 25 ... refund management data storage unit, 30 ... company server, 40 ... financial institution system.

Claims (11)

Regarding transactions between the first user and the second user,
Transaction information storage means for accumulating refund amount information for the second user out of the amount paid to the first user from the second user,
Refund condition information storage means for recording a refund condition for each first user;
A transaction support system having a control means connected to a financial institution system,
The control means is
Means for obtaining refund information for the second user from the first user when receiving an access from the client terminal of the second user;
Means for obtaining the refund condition of the first user from the refund condition information storage means;
Means for obtaining information relating to a refund destination account from the client terminal of the second user;
A means for determining whether or not the refund condition is satisfied for the refund destination account, and when the refund condition is satisfied, a means for transmitting a transfer execution instruction for the refund information to the financial institution system. A transaction support system characterized by In the refund condition information storage means, an evaluation value for evaluating a refund destination account is recorded as a refund condition.
The control means is
Means for calculating a total value of evaluation values for a refund destination account acquired from the client terminal of the second user;
The transaction support system according to claim 1, further comprising means for executing an error handling process when the total value exceeds a preset reference value. The refund condition recorded in the refund condition information storage means is composed of a plurality of items for the transfer,
Each item has an evaluation value to evaluate the satisfaction of the refund condition,
The control means further comprises means for calculating a total value of evaluation values of each item and executing an error handling process when the total value exceeds a preset reference value. The transaction support system according to claim 1 or 2. In the refund condition information storage means, as the refund condition, an evaluation value when the existence of an account cannot be confirmed is recorded,
The said control means acquires the presence information of the said refund destination account from a financial institution system, and when the presence of an account cannot be confirmed, the total value which added the said evaluation value is calculated. 4. The transaction support system according to any one of 3. The transaction support system further includes user information storage means for recording information on a destination financial institution with an account used for payment by the second user,
In the refund condition information storage means, an evaluation value for evaluating a mismatch between the refund destination account and the destination financial institution information is recorded as the refund condition.
The said control means calculates the total value which added the said evaluation value, when the said refund destination account and destination financial institution information do not correspond. Transaction support system. In the refund condition information storage means, an evaluation value for evaluating a mismatch between the name of the holder of the refund destination account and the name of the second user is recorded as the refund condition.
The control means compares the name of the holder acquired in the account existence confirmation information and the name of the user of the second user, and if they do not match, calculates the total value obtained by adding the evaluation values. The transaction support system according to claim 4 or 5, characterized by the above. In the refund condition information storage means, an evaluation value is recorded corresponding to a refund amount range as the refund condition,
The control means obtains an evaluation value corresponding to a refund amount range including a scheduled refund amount in the refund information for the second user from the first user, and calculates a total value obtained by adding the evaluation values. The transaction support system according to claim 1, wherein the transaction support system is characterized in that: In the transaction information storage means, information related to the non-paid bill amount from the second user to the first user is further recorded,
The said control means is further provided with the means to output the message for confirming the presence or absence of the cancellation hope of the said charge amount and refund amount with respect to the said 2nd user. The transaction support system according to any one of the above. In the transaction information storage means, information on a refund due date allowing refund is further recorded,
9. The control unit according to claim 1, further comprising means for notifying the second user when there is remaining refund amount information after the refund deadline. The transaction support system according to one. Regarding transactions between the first user and the second user,
Transaction information storage means for accumulating refund amount information for the second user out of the amount paid to the first user from the second user,
Refund condition information storage means for recording a refund condition for each first user;
A method of performing transaction support processing using a transaction support system having a control means connected to a financial institution system,
The control means is
When receiving access from the client terminal of the second user, obtaining refund information for the second user from the first user;
Obtaining a refund condition of the first user from the refund condition information storage means;
Obtaining information about a refund destination account from the client terminal of the second user;
Determining whether the refund condition is satisfied for the refund destination account, and if the refund condition is satisfied, executing a step of transmitting a transfer execution instruction for the refund information to the financial institution system. A transaction support method characterized by Regarding transactions between the first user and the second user,
Transaction information storage means for accumulating refund amount information for the second user out of the amount paid to the first user from the second user,
Refund condition information storage means for recording a refund condition for each first user;
A program for performing transaction support processing using a transaction support system having a control means connected to a financial institution system,
The control means;
Means for obtaining refund information for the second user from the first user when receiving an access from the client terminal of the second user;
Means for obtaining the refund condition of the first user from the refund condition information storage means;
Means for obtaining information relating to a refund destination account from the client terminal of the second user;
It is determined whether or not the refund condition is satisfied for the refund destination account. A featured transaction support program.