Method for Supporting Payment between Payer and Recipient through Card Payment and Management Server Used Therefor

Abstract

A method for supporting cost settlement between a payer and a recipient via card payment and a management server used therein are disclosed. The present invention is implemented through a process in which a management server receives a card payment request from a payer terminal containing information necessary for card payment regarding costs to be paid to a recipient, receives an approval message for the card payment request from a payment server, and calculates an amount to be remitted to the recipient based on fee information agreed upon by the recipient to bear in the card payment. According to the present invention, since the recipient bears the fees incurred in card payment intended to replace cash payment, the payer can utilize the card payment service while bearing only the same amount as the original amount to be paid. Furthermore, according to the present invention, it is possible to prevent the payer's payment amount from changing arbitrarily depending on the payment method, such as cash or card, for the same transaction.

Description

Technology Field

[0001] The present invention relates to a method for supporting cost settlement between a payer and a recipient through card payment and a management server used therein. More specifically, the invention relates to a method for supporting cost settlement between a payer and a recipient through card payment and a management server used therein, wherein the recipient bears the fees incurred in card payment to replace cash payment, thereby allowing the payer to use the card payment service while bearing only the amount that is originally to be paid, and preventing the payer's payment amount from changing arbitrarily depending on the payment method, such as cash or card, for the same transaction. Background Technology

[0002] In the past, regarding payment settlements between franchise stores and headquarters, headquarters often required payment for supplies and other items only in cash or via bank transfer; however, recently, there is a growing trend of franchise headquarters introducing card payments to secure cash liquidity and enhance convenience for franchisees.

[0003] In addition, while real estate tenants often requested rent from landlords only in cash or via bank transfer, recently, services that allow tenants to pay rent using credit cards without immediate cash expenditure and to take advantage of payment deferral benefits are becoming increasingly widespread.

[0004] However, when payments are switched from cash to card payments in this manner, card fees are inevitably incurred. Since the recipients of the payments, such as franchise headquarters and landlords, do not want to suffer losses resulting from the switch in payment methods, the payers, such as franchisees and tenants, end up bearing the card fees.

[0005] For example, if the amount to be paid to the recipient is 1 million won and the card fee rate is 2%, the payer must make a card payment of approximately 1.02 million won, and consequently, there is a problem that the payer actually has to spend more than in the case of cash payment.

[0006] The foregoing description is provided merely as related art to aid in understanding the present invention, and does not imply that the foregoing description can be applied as prior art related to the present invention. The problem to be solved

[0007] Accordingly, the objective of the present invention is to provide a method for supporting cost settlement between a payer and a recipient through card payment and a management server used therein, wherein the recipient bears the fees incurred in card payment to replace cash payment, thereby allowing the payer to use the card payment service while bearing only the same amount as the original amount to be paid, and preventing the payer's payment amount from changing arbitrarily depending on the payment method, such as cash or card, for the same transaction.

[0008] The problems to be solved by the present invention are not limited to the problems mentioned, and include other technical problems that can be clearly understood by those skilled in the art to which the present invention belongs from the description below. means of solving the problem

[0009] A method for supporting cost settlement between a payer and a recipient through card payment according to the present invention for achieving the above objective comprises: (a) a step in which a management server receives a card payment request from a payer terminal that includes information necessary for card payment regarding costs to be paid to a recipient; (b) a step in which the management server receives an approval message for the card payment request from a payment server; and (c) a step in which the management server calculates an amount to be remitted to the recipient based on fee information agreed upon by the recipient in the card payment.

[0010] Preferably, the management server calculates the amount to be remitted to the recipient by deducting the fee agreed to be borne by the recipient from the payment approval amount in the card payment.

[0011] Meanwhile, the management server according to the present invention includes: a receiving unit that receives a card payment request from a payer terminal containing information necessary for card payment regarding costs to be paid to a recipient, and receives an approval message for said card payment request from a payment server; and a calculation unit that calculates an amount to be remitted to said recipient based on fee information agreed upon by the recipient in said card payment.

[0012] Preferably, the above-mentioned operation unit is characterized by calculating the amount to be remitted to the recipient by subtracting the fee agreed to be borne by the recipient from the payment approval amount in the above-mentioned card payment.

[0013] Meanwhile, the management server according to the present invention is characterized by having a program installed that executes the above method. Effects of the invention

[0014] According to the present invention, the recipient bears the fees incurred in card payments to replace cash payments, thereby enabling the payer to utilize the card payment service while bearing only the same amount as the original amount to be paid.

[0015] In addition, according to the present invention, it is possible to prevent the payer's payment amount from changing arbitrarily depending on the payment method, such as cash or card, for the same transaction.

[0016] The effects of the present invention are not limited to the effects mentioned, and include other effects that can be clearly understood by those skilled in the art from the description below. Brief explanation of the drawing

[0017] FIG. 1 is a configuration diagram of a cost settlement support system between a payer and a recipient through card payment according to an embodiment of the present invention. FIG. 2 is a functional block diagram showing the structure of a management server that executes a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention. FIG. 3 is a signal flowchart illustrating the execution process of a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention. FIGS. 4 and 5 are drawings showing the screen state of a merchant terminal during the execution process of a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention, and FIG. 6 is a flowchart illustrating the process of calculating the remittance amount in a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention. Specific details for implementing the invention

[0018] The present invention will be described in more detail below with reference to the drawings. It should be noted that identical components in the drawings are denoted by the same reference numerals wherever possible. Furthermore, detailed descriptions of known functions and configurations that could unnecessarily obscure the essence of the invention are omitted.

[0019] FIG. 1 is a configuration diagram of a cost payment support system between a payer and a recipient through card payment according to an embodiment of the present invention. Referring to FIG. 1, the cost payment support system between a payer and a recipient through card payment according to an embodiment of the present invention includes a recipient terminal (100), a management server (200), and a payer terminal (300).

[0020] The recipient terminal (100) is a communication terminal such as a PC or smartphone used by a person in charge of franchise management at a headquarters operating a franchise business, a building lessor, etc., and the payer terminal (300) is a wireless communication terminal such as a smartphone or PC used by a franchisee who has signed a franchise agreement with the franchise headquarters, a building lessee, etc.

[0021] Meanwhile, in implementing the present invention, the recipient terminal (100) and the payer terminal (300) may each be equipped with a main application program and a merchant application program for using the cost settlement support service between the payer and the recipient through card payment according to the present invention.

[0022] The management server (200) is a server installed and operated by a business operator that provides a cost payment support service between a payer and a recipient through card payment according to an embodiment of the present invention. The management server (200) receives a card payment request from a payer terminal (300) that includes various information necessary for card payment regarding costs to be paid to the recipient, receives an approval message for the card payment request from a payment server of a credit card company, and calculates an amount to be remitted to the recipient based on information regarding fees agreed to be borne by the recipient in card payment, and calculates the amount to be remitted to the recipient by subtracting the fees agreed to be borne by the recipient from the card payment approval amount.

[0023] The management server (200) is configured to communicate with the recipient terminal (100) and the payer terminal (300) through a communication network, and the communication network provides a connection path so that the management server (200), the recipient terminal (100), and the payer terminal (300) can transmit and receive packet data after connecting to each other.

[0024] Communication networks may include wired networks such as LANs (Local Area Networks), WANs (Wide Area Networks), MANs (Metropolitan Area Networks), and ISDNs (Integrated Service Digital Networks), as well as wireless networks such as wireless LANs, CDMA, Bluetooth, and satellite communication, but the scope of the present invention is not limited thereto.

[0025] FIG. 2 is a functional block diagram showing the structure of a management server (200) that executes a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention. Referring to FIG. 2, the management server (200) that executes a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention includes a receiving unit (210), a storage unit (230), a calculation unit (250), and a transmitting unit (270).

[0026] The receiving unit (210) of the management server (200) may receive partner information from the recipient terminal (100) and receive a merchant registration request and a card payment request from the payer terminal (300).

[0027] The computation unit (250) of the management server (200) generates card payment history information of the payer based on a card payment request, and calculates the amount to be transferred to the recipient based on fee information agreed upon by the recipient in the card payment.

[0028] The transmitting unit (270) of the management server (200) transmits the payer's payment history information to the recipient terminal (100).

[0029] Meanwhile, various receiving information from the receiving unit (210), various generation and output information from the calculation unit (250), and various transmission information from the transmission unit (270) may be accumulated and stored in the storage unit (230) of the management server (200).

[0030] FIG. 3 is a signal flowchart illustrating the execution process of a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention. Hereinafter, with reference to FIGS. 1 to 3, the execution process of a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention will be described.

[0031] Although the following explanation assumes that the recipient is a franchise headquarters, the same configuration applicable by an ordinary skilled technician according to the purpose of the transaction can be applied even if the recipient falls under other types, such as a building lessor.

[0032] First, as a representative of a franchise headquarters that has entered into an agreement with a service operator according to the present invention regarding support for franchise management tasks inputs information of partner companies such as interior companies, sign companies, logistics companies, and equipment companies that do business with the headquarters through a recipient terminal (100) (e.g., names of partner companies and business registration numbers, etc.), the management server (200) may receive and store information of each partner company from the recipient terminal (100) (S410).

[0033] Meanwhile, when a franchisee who has signed a franchise agreement with the franchise headquarters completes service member registration by entering a franchisee ID (e.g., the franchisee's mobile phone number) through the payer terminal (300), the franchisee can view a service usage guide screen as shown in FIG. 4 through the payer terminal (300).

[0034] Accordingly, when a franchisee selects the franchisee registration item (Please register a franchisee) in FIG. 4 to register the franchisee's service, and then enters franchisee information such as a business registration number, franchisee name, and franchisee address through an input screen like FIG. 5, the management server (200) receives a franchisee registration request containing the input information from the payer terminal (300) (S420).

[0035] Accordingly, the transmitting unit (270) of the management server (200) transmits the merchant registration request to the recipient terminal (100), and the recipient terminal (100) may transmit a merchant registration approval message to the management server (200) when the merchant information included in the merchant registration request is found in the merchant contract information, such as a merchant contract, that is already stored in the recipient terminal (100) (S430).

[0036] Accordingly, when the receiving unit (210) of the management server (200) receives a merchant registration approval message from the recipient terminal (100), the processing unit (250) of the management server (200) grants the merchant owner the right to use the service, and in this case, the transmitting unit (270) of the management server (200) may send a predetermined merchant registration completion message to the merchant owner based on the merchant owner's ID (e.g., mobile phone number).

[0037] In this way, the present invention grants the head office the authority to approve franchise registration in the service according to the present invention, thereby preventing companies that have not entered into a franchise agreement with the head office from attempting to register as franchisees without authorization.

[0038] Meanwhile, if a franchisee subsequently connects to a management server (200) via a payer terminal (300) to make a payment to the headquarters, etc., and selects 'Pay' in FIG. 4, the management server (200) checks whether the franchisee is a franchisee who has been granted service usage rights in accordance with the headquarters' registration approval in the aforementioned S430 step. If the franchisee has not been granted service usage rights, the management server (200) sends a predetermined message of non-use (e.g., "No franchisee registration information exists. Please use after completing franchisee registration") to the payer terminal (300), and if it is confirmed that the franchisee has been granted service usage rights, the management server (200) may send a credit card payment information input window to the payer terminal (300).

[0039] Accordingly, the franchisee selects the type of payment they intend to proceed with (e.g., paying to a good headquarters, paying to a general headquarters, paying to a partner company, paying other costs, etc.) and inputs various information required for card payment [credit card company, card number, expiration date, payment amount, payment recipient information, payment purpose (startup costs, logistics costs, operating costs, etc.)], and the management server (200) receives a card payment request from the payer terminal (300) that includes the selected information and each input information (S440).

[0040] Accordingly, the management server (200) first extracts payment type selection information included in the card payment request, and if the extracted payment type selection information is 'pay to a partner company', the payment receiving company information included in the card payment request is searched from the partner company information received and stored from the recipient terminal (100) in the aforementioned step S410. If the corresponding payment receiving company is not found, a predetermined payment refusal notice message (e.g., the corresponding payment receiving company is not a partner company of the franchise headquarters.) is sent to the payer terminal (300), and if the corresponding payment receiving company is found, the card payment can be approved (S450).

[0041] As a result, since the franchisee is able to make payments only to partner companies registered by the franchise headquarters, it is possible to prevent the franchisee from arbitrarily trading with external companies, thereby promoting the interests of the franchise headquarters and partner companies.

[0042] Meanwhile, if the payment approval at the aforementioned S450 step is completed, or if there are other payment types that do not require such payment approval, the management server (200) proceeds with the card payment in accordance with the merchant's card payment request (S460).

[0043] Specifically, the management server (200) may extract certain information required for payment approval by the credit card company (e.g., card number, expiration date, payment amount) from the input information included in the card payment request, generate a card payment approval request including the extracted information, and transmit it to the payment server of the credit card company, thereby receiving a card payment approval message from the payment server.

[0044] In this way, when card payment approval through a credit card company is completed, the computation unit (250) of the management server (200) can extract various information included in the card payment request in the aforementioned step S440 and various information included in the approval message received from the payment server (approval amount, approval date and time, etc.), and generate merchant card payment history information including these (S470).

[0045] In addition, the processing unit (250) of the management server (200) may classify and process each card payment history information by payment type based on the payment type selection information included in the card payment request, and may store each type classification information in association with the card payment history information generated in the aforementioned step S470 (S480).

[0046] In addition, the calculation unit (250) of the management server (200) may calculate the amount to be remitted to the headquarters as follows when the payment type selection information included in the card payment request in the aforementioned step S440 is 'pay to the good headquarters', and may store this in association with the card payment history information generated in the aforementioned step S470 (S490).

[0047] FIG. 6 is a flowchart illustrating the process of calculating a remittance amount in a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the present invention. Hereinafter, with reference to FIG. 6, a method for calculating a remittance amount in a method for supporting cost settlement between a payer and a recipient through card payment according to an embodiment of the invention will be described.

[0048] First, the operation unit (250) of the management server (200) searches for payment approval amount information (e.g., 1 million won) included in the payment approval message received from the payment server of the credit card company or payment amount information included in the card payment request in the aforementioned step S440 (S491), and searches for the payment agreement amount (e.g., 1 million won) of the merchant or tenant already stored in the storage unit (230) (S493), and if the two match, it can be determined that the card payment has been successfully made.

[0049] In addition, the computation unit (250) of the management server (200) may be able to retrieve information on the commission rate (e.g., 1.8%) that the headquarters (or lessor) has agreed to bear when a merchant (or lessee) makes a card payment, through the contract information between the headquarters (or lessor) and the service operator according to the present invention that is already stored in the storage unit (230) (S495).

[0050] Next, the calculation unit (250) of the management server (200) can calculate the fee (e.g., 18,000 won) that the head office (or lessor) must bear by applying the fee rate (e.g., 1.8%) to the approval amount or payment amount (e.g., 1 million won), and by subtracting this from the approval amount or payment amount (e.g., 1 million won), it can calculate the amount (e.g., 982,000 won) that the service operator must remit to the head office (or lessor).

[0051] Meanwhile, the computation unit (250) of the management server (200) may calculate the expected deposit date (i.e., the scheduled date for remittance to the service operator's headquarters or tenant), which is the date when the payment amount is deposited from the credit card company into the service operator's bank account in accordance with the credit card company's payment approval, from the deposit history information based on the credit card company's payment approval already stored in the storage unit (230), and may store this as the scheduled remittance date information to the service operator's headquarters (or lessor) in the corresponding payment history information generated in the aforementioned step S470.

[0052] In addition, the management server (200) may process the transfer of the amount calculated in the aforementioned step S499 to the account of the headquarters (or lessor) when the card company processes the payment amount into the service operator's account in the future; however, in implementing the present invention, even before the payment is received from the card company, if the amount to be transferred is calculated in the aforementioned step S499, the transfer may be processed to the account of the headquarters (or lessor), thereby contributing to the sound financial achievement of the franchise headquarters (or lessor).

[0053] Meanwhile, in implementing the present invention, the calculation unit (250) of the management server (200) may calculate the amount to be remitted to the headquarters (or lessor) as follows when the payment approval amount (e.g., 900,000 won) found in the aforementioned step S491 is smaller than the payment agreement amount (e.g., 1,000,000 won) of the merchant (or lessee) found in the aforementioned step S493.

[0054] Specifically, the computation unit (250) of the management server (200) retrieves information on the commission rate (e.g., 1.8%) that the headquarters (or lessor) has agreed to bear when making a card payment at a merchant, which is stored in the storage unit (230) (S495), calculates the commission (e.g., 16,200 won) that the headquarters (or lessor) must bear by applying the commission rate to the approved amount (e.g., 900,000 won), calculates the amount (e.g., 883,800 won) that the service operator must remit to the headquarters (or lessor) by subtracting this from the approved amount (e.g., 900,000 won), and can process the remittance of the calculated amount to the headquarters (or lessor) account.

[0055] In such cases, even if the franchisee (or lessee) is unable to pay the full amount agreed upon with the headquarters (or lessor) and pays only a portion due to financial circumstances, the headquarters (or lessor) can immediately receive the amount after deducting the commission borne by the headquarters (or lessor) from the payment amount, thereby contributing to the financial soundness of the headquarters (or lessor).

[0056] In addition, the calculation unit (250) of the management server (200) may calculate the amount to be remitted to a partner company as follows when the payment type selection information included in the card payment request in the aforementioned step S440 is 'pay to partner company', and may store this in association with the card payment history information generated in the aforementioned step S470 (S490).

[0057] Specifically, the computation unit (250) of the management server (200) may calculate the amount that the service operator must remit to the partner company by subtracting the card payment fee based on the fee rate information for each card company from the payment approval amount (e.g., 1 million won) included in the payment approval message of the credit card company.

[0058] Meanwhile, the management server (200) may contribute to the sound financial achievement of the partner company and the smooth operation of the franchise business by processing the transfer to the partner company's account when the transfer amount is calculated in the aforementioned step S490, even before the payment is received from the card company.

[0059] In addition, the management server (200) may store such remittance processing information to the headquarters or partner company in association with the card payment history information generated in the aforementioned step S470.

[0060] Additionally, the computation unit (250) of the management server (200) may calculate the expected deposit date (i.e., the scheduled date for remittance to the service operator’s partner company), which is the date when the payment amount is deposited from the credit card company into the service operator’s bank account in accordance with the credit card company’s payment approval, from the deposit history information based on the credit card company’s payment approval already stored in the storage unit (230), and may store this as the information on the scheduled date for remittance to the service operator’s partner company in the corresponding payment history information generated in the aforementioned step S470.

[0061] Meanwhile, the payment history information generated in this way and various information stored in association with the payment history information can be accumulated and stored in the company's management account, and the company's representative can collectively check the card payment history information of each merchant by accessing the company's management account through the recipient terminal (100) (S500).

[0062] Specifically, as the head office representative can verify the card payment details to partner companies, such as logistics companies of franchisees, through this, even before the service operator processes the remittance to the partner company based on the card company's deposit, the head office can anticipate future payments to the partner company and instruct logistics delivery to the relevant franchisee.

[0063] In addition, through this, headquarters personnel can check payment history information of merchants classified by payment type (e.g., payments to 'Good' headquarters, payments to general headquarters, payments to partner companies, payments for other expenses, etc.).

[0064] In addition, through this, the head office representative can check the scheduled remittance date for each approval record to the service operator's head office (or partner company), thereby enabling the head office to prepare tasks aligned with the payment purpose of each record (e.g., logistics payments) in accordance with the scheduled remittance date.

[0065] Meanwhile, in implementing the present invention, the management server (200) may store the payment history information of the merchant as described above in the management account of the merchant, and when the merchant owner accesses the management server (200) through the payer terminal (300) and requests to view it, the management server (200) may transmit the payment history information of the merchant to the payer terminal (300) in bulk (S510).

[0066] In addition, in implementing the present invention, the head office representative who approved the registration of the merchant in the aforementioned step S430 may transmit the merchant's periodic (e.g., monthly) payment schedule information (e.g., logistics payment of 1 million won) to the management server (200) via the recipient terminal (100) prior to the aforementioned step S440.

[0067] Accordingly, the management server (200) may generate a list of unpaid bills for the relevant merchant on a periodic basis by storing a list of scheduled periodic payments in the management account of the relevant merchant, and then comparing this with the payment history information generated in the aforementioned step S470 by the relevant merchant's card payment on a periodic basis.

[0068] The management server (200) transmits the list of unpaid amounts generated by each merchant to the recipient terminal (100) and also transmits it to the corresponding payer terminal (300), thereby enabling the head office staff to use it as merchant management information and inducing prompt payment of the merchant's unpaid amount.

[0069] Meanwhile, in implementing the present invention, if the merchant (payer) selects a payment type in which the recipient bears the fee, such as 'pay to the good headquarters', as a payment type in the aforementioned step S440, the management server (200) may send a predetermined guidance message to the recipient terminal (100) and the payer terminal (300), respectively, before proceeding with the card payment in the aforementioned step S460, to inform the recipient that the fee for the card payment will be paid.

[0070] Meanwhile, the management server (200) can provide an application (App) or web environment in which a cost payment support service between a payer and a recipient through card payment according to the present invention is implemented.

[0071] In one embodiment, the service provided by the management server (200) may be provided through an application installed on a user terminal. Here, the application refers to an application program and may include, for example, an app running on a mobile terminal (smartphone).

[0072] The management server (200) according to the embodiments may have aspects that are entirely hardware or partially hardware and partially software. For example, the server (10) of this specification and each module and unit included therein may collectively refer to a device for exchanging data of a specific format and content via electronic communication and software related thereto.

[0073] In addition, in carrying out the present invention, a program for executing a method of supporting cost settlement between a payer and a recipient through card payment according to the present invention may be installed on a management server (200) according to the present invention, recorded on various computer-readable recording media, or stored on a server that transmits the program via a network.

[0074] In addition, the program according to the present invention may be distributed across networked computer systems, and computer-readable code may be stored and executed in a distributed manner; furthermore, the functional program, code, and code segments for implementing the present invention will be easily understood by a person skilled in the art to which the present invention pertains.

[0075] Meanwhile, the order of the steps (S410 to S510) described above in the present invention is merely an example and is not limited thereto. That is, the order of the steps (S410 to S510) described above may vary, and some of these steps may be executed simultaneously or deleted.

[0076] The terms used in this invention are used merely to describe specific embodiments and are not intended to limit the invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, terms such as "comprising" or "having" are intended to indicate the presence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0077] Although preferred embodiments and applications of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments and applications described above. Furthermore, various modifications can be made by those skilled in the art without departing from the essence of the invention as claimed in the claims, and such modifications should not be understood individually from the technical spirit or perspective of the present invention. Explanation of the symbols

[0078] 100: Recipient terminal, 200: Management server, 210: Receiver, 230: Storage, 250: Operation unit, 270: Transmitter unit, 300: Payer terminal

Claims

Claim 1 (a) a management server providing a cost settlement support service between a payer and a recipient, comprising a storage unit in which contract information regarding the card payment fee rate agreed upon by the recipient to bear upon the card payment of the payer is stored; (b) the management server receiving a card payment request from a payer terminal that includes information necessary for card payment regarding costs to be paid to the recipient; (c) the management server receiving an approval message regarding the card payment request from a payment server; and (d) the management server calculating an amount to be remitted to the recipient based on the contract information regarding the card payment fee rate agreed upon by the recipient in the card payment, wherein the card payment request in step (b) includes the payer's selection information regarding the payment type, and the payment type includes payment to a good recipient and payment to a general recipient, and step (d) comprises: (d1) the management server searching for the card payment fee rate agreed upon by the recipient when the payer selects payment to the good recipient; A method for supporting cost settlement between a payer and a recipient through card payment, comprising the step of (d2) the management server calculating the fee to be borne by the recipient by applying the card payment fee rate agreed upon by the recipient to the cost to be paid to the recipient. Claim 2 A method for supporting cost settlement between a payer and a recipient through card payment, wherein in claim 1, step (d) (d3) further includes the step of the management server calculating the amount to be remitted to the recipient by deducting the fee that the recipient must bear from the payment approval amount in the card payment. Claim 3 A management server providing a cost settlement support service between a payer and a recipient, comprising: a storage unit storing contract information regarding a card payment fee rate agreed upon by the recipient to bear when the payer makes a card payment; a receiving unit receiving a card payment request from a payer terminal containing information necessary for card payment regarding costs to be paid to the recipient, and receiving an approval message for the card payment request from a payment server; and a calculation unit calculating an amount to be remitted to the recipient based on the contract information regarding the card payment fee rate agreed upon by the recipient in the card payment, wherein the card payment request includes the payer's selection information regarding a payment type, and the payment type includes payment to a good recipient and payment to a general recipient, and when the payer selects payment to a good recipient, the calculation unit searches for the card payment fee rate agreed upon by the recipient and calculates the fee to be borne by the recipient by applying the card payment fee rate agreed upon by the recipient to the costs to be paid to the recipient. Claim 4 In paragraph 3, the above-mentioned operation unit is a management server that calculates the amount to be remitted to the recipient by subtracting the fee to be borne by the recipient from the payment approval amount in the above-mentioned card payment. Claim 5 A management server on which a program for executing the above method in paragraph 1 or 2 is installed.

Images