KR20170064465A - Apparatus and method for selling sales bond - Google Patents

Abstract

The present disclosure relates to a sales receipt and sales system, which is configured to output a sales slip to an affiliate terminal, generate a sales receipt corresponding to the output slip, and receive a sales receipt sales request message for selling the generated sales receipt The bond buying server determines whether or not to purchase one or more accounts receivable included in the received sales receipt sales request message and transmits the purchase receipt for the purchased receivable to an account associated with the merchant terminal .

Description

[0001] APPARATUS AND METHOD FOR SELLING SALES BOND [0002]

The present specification relates to a system and method for managing a trade receivable, more specifically, a method for selling trade receivable at a merchant and a system for supporting the same.

Generally, a credit card payment is a credit card company's credit, and a card member purchases goods or services from a credit card company, purchases the goods or services on a credit card, and then pays the corresponding purchase price to a credit card company on the settlement day. Means the settlement in such a manner that the payment of the goods or services sold to the card member is received from the credit card company.

Despite recent explosive credit card usage trends, credit card merchants are at a disadvantage due to credit card payments, such as having to sell products or provide services to customers after 5 to 7 days from credit card companies. Several companies are reluctant to pay by credit card.

In order to solve the above problems, the present specification discloses a method of generating a sales receipt related to a sales slip and a sales slip through an affiliate terminal, selling the receivable immediately to a financial institution, In order to solve the problem.

The present disclosure also aims to manage the accounts receivable list and to provide a method for selling a specific trade receivable or a plurality of trade receivables in the trade receivables list.

It is another object of the present invention to provide a method for enhancing security of information or messages transmitted and received between a merchant terminal and a financial institution server when selling a merchandise.

The present disclosure relates to a merchandise sales system, which, when detecting a credit card payment request, transmits a payment approval request including the detected credit card-related information and merchant information, Receiving a payment approval response, outputting a sales slip based on the received payment approval response, generating a receivable corresponding to the output slip, outputting a sales receipt sales request message for selling the generated sales receipt A merchant terminal for transmitting the merchandise; Determines the approval rejection or approval permission by comparing the credit card-related information and the merchant store information included in the received payment approval request with the previously stored credit card member data and the merchant store data, A settlement approval server for transmitting a settlement approval response including the sales slip and paying a price related to the sales slip; The method comprising: receiving the merchandise sales request message, determining whether to purchase one or more merchandise receivables included in the received merchandise sales request message, and transferring a purchase price for the purchased merchandise receipt to an account associated with the merchant terminal A paying bond server; A payment relay server connected to the merchant terminal and the payment approval server via a first communication network to transmit and receive a message; And a system operation server connected to the merchant terminal and the payment approval server via a second communication network to transmit and receive a message.

Also, in this specification, the payment relay server receives the payment approval request from the merchant terminal, reconstructs the received payment approval request, and transmits the payment approval request to the payment approval server, and transmits the determined approval result from the payment approval server And transmits the settlement approval response to the franchisee terminal by reconfiguring the received settlement approval response.

In addition, in this specification, the system operation server receives the sales receipt sales request message from the merchant terminal, transmits the received sales receipt sales request message to the receipt purchase server, receives the purchase receipt from the receipt acceptance server, And provides the received purchase price to an account associated with the merchant terminal.

Also, the payment approval request may further include a sales receipt sales notification information indicating that the credit card payment amount corresponding to the payment approval request is to be directly paid through the bond purchase server.

Also, in the present invention, the sales slip includes at least one of an approval date, an approval number, an approved amount, the merchant terminal information, the merchant information, or credit card company identification information, and the merchandise receipt includes information Or a part of the information included in the sales slip, and the merchandise receipt further comprises a merchandise receipt identifier for distinguishing the generated receivables from each other.

In addition, in the present specification, the sales receipt sales request message is transmitted to the bond purchase server every time the trade receipt is generated, or is transmitted to the bond purchase server according to a predetermined condition.

Also, in the present specification, the predetermined condition is a predetermined time or a predetermined time interval or a user input receiving.

Also, in this specification, the bond purchase server determines whether to purchase the one or more trade receivables in consideration of whether or not the account for sales receivable sale is opened or the information contained in the sales receipt sales request message is validated .

Further, in this specification, the purchase price is paid in a dedicated virtual account associated with the merchant.

Also, in the present invention, the purchase price is an amount excluding a predetermined fee from the payment amount of the sales slip, and the predetermined fee includes at least one of a sales receipt discount fee or a credit card fee.

Also, in this specification, the bond purchase server transmits a one-time authentication number to another terminal connected to the merchant terminal and / or the merchant terminal, and receives the same number as the one-time authentication number from the affiliate terminal and / The purchase price is paid to the exclusive virtual account.

Also, in this specification, the bond purchase server determines the number of trade receivables to be purchased and the total amount of trade receivables to be purchased in consideration of the priority of the one or more trade receivables.

Also, in the present specification, the priority order is the order of sales of the merchant, transaction history data between the merchant and the institution that operates the bond purchase server, operation form of the merchant, location of the merchant, type and type of service provided by the merchant, And the customer's level of the merchant.

Also, in the present specification, the merchant terminal stores the receivables as one or more receivables lists, and the one or more receivables lists include a list of completed receivables, a list of receivables requested for sale, And is a receivables list.

Also, in the present specification, the merchant terminal includes an output unit; A communication unit for performing a communication function with the payment relay server and the system operation server; And a control unit operably connected to the output unit and the communication unit, wherein the control unit outputs a sales slip based on the payment approval response, generates a sales receipt corresponding to the sales slip, And transmits the sales receipt sales request message for selling the bond to the bond purchase server.

Also, in this specification, the controller of the affiliate terminal controls to update the one or more accounts receivable lists when the predetermined condition is satisfied, and the predetermined condition is that the number of accounts receivable which are requested to be sold or sold has exceeded the predetermined threshold Is greater than the value of the "

In addition, in this specification, the control unit of the affiliate terminal controls to regenerate the sales receipt identifier only for the sales receivables that can be sold when updating the one or more receivables lists.

The system and method of merchant bond sales proposed by the present invention has the effect of selling the receivables by bond trading method and securing the amount of the receivables directly without depositing the money separately to the merchant stock price financial institution.

In addition, in the case of using the method proposed in the present specification, a merchant registers a virtual account dedicated to sale of merchandise in advance in a financial institution (a bank), and a financial institution pays a purchase price only to a registered account. It is possible to prevent the problem that the account registered by the user is changed.

As a result, the financial institution (bank) has the effect of minimizing the risk of erroneously paying the purchase price.

BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a diagram showing an example of a configuration diagram of a merchandise sales system proposed in the present specification. FIG.
2 is a diagram showing an example of an internal block diagram of an affiliate terminal proposed in the present specification.
FIG. 3 is a flowchart showing an example of a method for selling merchandise receivable of a merchant proposed in the present specification.
4 is a diagram illustrating an example of the operation of a merchant terminal for selling a sales receipt proposed in the present specification.

In order to fully understand the present invention, the operational advantages of the present invention and the objects achieved by the practice of the present invention, reference should be made to the accompanying drawings and the accompanying drawings which illustrate preferred embodiments of the present invention.

In the present specification, when an element 'transmits or transmits data or a signal' to another element, the element can transmit or transmit the data or signal directly to the other element, and at least one Means that the data or signal can be transmitted to the other component via another component. In addition, the suffix "module" and " part "for constituent elements used in the following description are given or mixed in consideration of ease of specification, and do not have their own meaning or role.

The foregoing objects, features and advantages of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Like reference numerals designate like elements throughout the specification. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail.

<Accounts Receivable Sales System>

BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a diagram showing an example of a configuration diagram of a merchandise sales system proposed in the present specification. FIG.

When a customer purchases an item, the customer can make payment through credit card sensing at the merchant terminal of the credit card merchant or online settlement in the online market through the Internet.

The merchandise sales system 100 may include an affiliate shop terminal 110, a payment relay server 120, a payment approval server 130, a system operation server 140 and a bond purchase server 150.

The components shown in Fig. 1 are not essential, and a sales receipt sales system having components having more components or fewer components may be implemented.

Hereinafter, the components will be described in order.

The merchant terminal 110 may include a wired or wireless terminal such as a general credit card reader, a POS terminal, a PDA, a desktop computer, a notebook computer, or a smart phone.

The merchant terminal reads out the card information from the card reader at the time of payment using the credit card, inputs the card payment information such as the payment amount and installment content through the key input unit, encrypts and stores the card payment information in the memory, The payment approval request can be transmitted to the payment relay server 100 responsible for relaying the payment approval request through the communication unit.

Also, the merchant terminal outputs a sales slip related to card settlement, and generates a sales receipt corresponding to the sales slip.

The payment relay server 120 may correspond to a VAN company server.

The VAN server may be responsible for card issuance of the card company.

The server of the VAN company can relay the payment authorization server to the merchant terminal connected through the communication network.

The payment relay server can perform a communication function between the merchant terminal and the payment approval server through the communication unit.

The customer can make credit card payment through the merchant terminal to purchase the product. The card payment method may be magnetic tape recognition, NFC tagging, internet payment, etc.

The payment approval server 130 receives the payment approval request from the payment relay server through the packet network and transmits a response to the payment approval request to the payment relay server.

The payment approval server may correspond to a (credit) card company server.

The system management server 140 relays information or message exchange between the merchant terminal and the payment approval server.

The bond purchase server 150 may refer to a server operated by a financial institution (e.g., a bank).

The bond purchase server receives a sales receipt sales request message for selling one or more receivables from the merchant terminal through the system operation server.

When receiving the sales receipt sales request message, the receipt purchase server determines whether to purchase the sales receipt based on the information included in the received sales receipt sales request message.

The bond purchase server decides the purchase of the trade receivable considering specific matters or decides the purchase of the trade receivable in consideration of the priority.

The above specific items include sales data (transaction amount, loan status, creditworthiness, etc.) with a financial institution (e.g., a bank) that operates the sales receipt purchase server, (Ie, how much franchises the company has), the location of the merchant (because the deposit or sales of the merchant may vary depending on the location), the type of service and / Or the number, the degree of awareness such as the presence / frequency of the broadcast of the merchant, and the like.

The bond purchase server can determine whether to purchase a trade receivable or the number of trade receivables to be purchased or to prioritize a plurality of receivable sales request messages based on the specific matter, do.

The bond purchase server purchases the sales receipt requested to be sold from the merchant terminal and pays the purchase price of the sales receipt to the exclusive virtual account of the merchant.

The bond purchase server may transmit a purchase payment message for notifying the payment of the purchase price to the merchant terminal and / or another device connected to the merchant terminal through a system operation server.

In addition, the bond purchase server further performs the following procedure before paying the purchase price to the exclusive virtual account of the merchant so as to prevent the payment of the purchase price from being paid to the franchise owner or a third party who does not have a legitimate authority .

That is, before the bond purchase server makes payment of the purchase receipt purchase price, the server (the device of the user) which is connected to the merchant terminal and / or the merchant terminal and registered as a device to receive the purchase payment payment related information in advance (Or password) such as OTP (One-Time-Password).

The meaning of 'A and / or B' can be interpreted the same as 'at least one of A or B.'

In addition, when the receipt purchase server receives an input of the same number as the authentication number from the merchant terminal or the device, the receipt purchase server pays the purchase receipt purchase price to the virtual account of the merchant.

In addition, if the bond purchase server has paid the purchase amount to the virtual account, the payment acceptance server transmits a prepayment message indicating that the payment has been paid in advance by the settlement approval server.

The billing server transmits a purchase payment request message to the payment approval server (or the credit card company server) corresponding to the credit card company after paying the purchase receipt purchase price to the merchant-exclusive virtual account.

The billing server receives the purchase price for the purchase request message from the payment approval server.

The payment approval server may be a server operated by a credit card company associated with a credit card payment.

The settlement approval server approves a payment approval request from the merchant terminal and pays the amount corresponding to the sales slip related to the receivable purchased by the bond purchase server.

<Franchise terminal>

2 is a diagram showing an example of an internal block diagram of an affiliate terminal proposed in the present specification.

2, the merchant terminal 110 may include a communication unit 111, a control unit 112, a memory 113, an output unit 114, and a user input unit 115.

Hereinafter, each component of the merchant terminal will be described in detail.

The communication unit 111 can perform a communication function with the settlement relay server and the system operation server.

The merchant terminal can request the credit card payment approval to the payment relay server through the communication unit.

The merchant terminal can receive a response to the payment approval request from the payment relay server through the communication unit.

The control unit 112 is a module for controlling the overall operation of the merchant terminal for performing the sales of the merchandise, and controls the transmission and reception of messages.

In addition, the controller 112 implements the functions, processes, and / or methods suggested in FIGS. 3 and 4, which will be described later.

The control unit may be represented by a processor, a control unit, a controller, or the like.

The memory 113 may store various programs and data for driving the merchant terminal.

The memory may permanently or temporarily store data generated during operation of the merchant terminal.

For example, the memory may store user information, transaction details, merchant information, and the like stored in a credit card for credit card settlement.

The output unit 114 may include a print unit 114-1, a display unit 114-2, and the like.

The printing unit 114-1 can output the payment approval result received from the payment relay server as a slip.

The display unit 114-2 can display the payment approval result received from the payment relay server. The payment approval result may include confirmation of payment completion, transaction history, payment amount, and the like.

The user input unit 115 may generate data for inputting a card payment amount, inputting a split amount of a payment amount, transmitting an approval request, etc. according to a user's operation.

The business operator can divide the card settlement price into a plurality of product groups at the time of settlement of the card and input.

Hereinafter, a method for selling merchandise receivables proposed by the present invention will be described in detail.

<How to sell merchandise at merchants>

FIG. 3 is a flowchart showing an example of a method for selling merchandise receivable of a merchant proposed in the present specification.

The method of selling merchandise receipts of merchants includes (1) issuance of a sales slip (or output) and creation of a merchandise receipt at a merchant terminal (S310), (2) purchase and sale of accounts receivable created between the merchant terminal and the buyer Step S320, and (3) settlement of the paid purchase price between the creditor buying server and the settlement approval server (or the card company server) (S330).

The above steps (1) to (3) will be described in more detail.

First, a method of outputting a sales slip at the merchant terminal at the step (1), that is, a credit card payment, and generating a receivable corresponding to the sales slip will be described.

A customer or user may use credit card payment instead of cash when purchasing goods or paying for the use of a particular service.

Generally, a credit card payment is a credit card company's credit, and a credit card company purchases goods or services from a credit card company as a credit card, and after a predetermined time, a corresponding credit card is paid to a credit card company , And the merchant refers to the settlement in such a manner that the price of the goods or services sold to the card member is paid from the credit card company.

The credit card settlement is performed through the merchant terminal, and the merchant terminal can perform settlement (including Internet settlement) through credit card sensing.

The payment method of the credit card may be magnetic tape recognition, NFC tagging, Internet payment, or the like.

The merchant terminal may include a general credit card reader, a POS terminal, a PDA, a desktop, a smart phone, and the like.

1) The card reading unit of the merchant terminal reads the sensed card information. 2) The key input unit of the merchant terminal receives the input of the card settlement information such as the settlement amount and the installment contents. 3) the memory of the merchant terminal encrypts and stores the received card settlement information, and 4) the communication unit of the merchant terminal transmits a payment approval request to the payment relay server responsible for the role of the payment approval request / response (S311).

The payment relay server may be referred to as a VAN server.

The payment approval request may include credit card information (card number), installment month information, approval request amount, authorization request date, merchant terminal information, merchant information, sales receipt sales notification information, and the like.

The sales receipt sales notification information is information for notifying that the payment amount is to be sold to a financial institution operating the purchase account server and receiving the payment amount from the financial institution.

The payment approval server receives the payment approval request from the payment relay server through a communication network (e.g., packet network) (S312) and transmits a response (approval or rejection) to the payment relay server (S313).

The payment approval server may be referred to as a (credit) card issuer server.

As previously mentioned, if a customer (a credit card holder) makes a purchase request using a credit card at a credit card merchant to pay for goods or services, the settlement procedure can be summarized as follows.

First, when the credit card payment is sensed, the merchant terminal generates a payment approval request related to the credit card payment.

The payment approval request is generated by combining user information, transaction details, and merchant information stored in the customer's credit card.

The merchant terminal transmits the generated payment approval request to the payment relay server through a public switched telephone network (PSTN), a wireless communication network, a leased line, or a CO-LAN.

Here, the merchant terminal includes a module for sending the payment approval request to a specific payment relay server. Accordingly, the payment approval request transmitted from the specific merchant terminal is transmitted only to the specific payment relay server.

Then, the payment relay server confirms the information related to the payment approval server included in the user information in the payment approval request, and transmits the combination of data related to the payment approval request to the payment approval server through the dedicated packet network.

Thereafter, the payment approval server compares the user information transaction details and the merchant information included in the payment approval request with their own member data or merchant data, respectively, to determine whether the credit card user and the merchant both have a reason for disqualification as a transaction member, And verifies that the transactions generated between the parties are valid.

Thereafter, the payment approval server transmits the result (or response) of the payment approval request to the payment relay server that relays the payment approval request through the dedicated packet network.

Here, the payment approval server may receive information related to the payment relay server when receiving a payment approval request from the payment relay server.

That is, the payment relay server can process the payment approval request transmitted from the merchant terminal and transmit the payment approval request processed to the payment approval server.

Here, the processing may include adding other information to existing information, and reconfiguring a packet that can be transmitted to the payment approval server when packet configuration such as packet size is changed by adding other information.

Then, the payment relay server confirms the merchant information included in the result of the payment approval request, and transmits the result of the transaction approval request to the merchant terminal of the merchant where the transaction approval request is first generated through the communication network ).

At this time, the payment relay server can additionally transmit the transaction approval request result to not only the merchant terminal but also other devices connected to the merchant terminal.

Then, the merchant terminal issues or outputs a sales slip so that the user can visually recognize the payment result based on the payment approval request result, and generates a sales receipt corresponding to the sales slip (S315).

The sales receipt may be configured to include information included in the sales slip.

In addition, the trade receivable may further include an identifier for identifying each of the generated trade receivables.

For example, the receivable may include an approval date, an approval number, an approved amount, merchant terminal information (number), merchant information (number), credit card company name, and an identifier.

In addition, the merchandise receipt can be stored in the merchant terminal in the form of a barcode, a text message, or the like so that the merchant can easily recognize the merchant.

Then, the merchant terminal transmits a sales receipt sales request message for sales receipt to the (sales) receipt buy server.

Here, the sales receipt sales request message may be transmitted to the bond purchase server through a system operator server.

The sales receipt sales request message can be transmitted to the bond purchase server every time a sales receipt is generated or when a certain condition is satisfied.

Also, the sales receipt sales request message may include a plurality of trade receivables.

The plurality of trade receivables can be grouped and classified.

The predetermined condition may be a predefined time and time interval, (cumulative) number of predefined accounts receivable, user input receiving, and the like.

The predefined time and time interval may be set in minutes, hours, days, weeks, or the like.

In addition, the merchant terminal can store a sales receipt list in a database (DB) and store it in a memory.

The receivables list may be composed of one or more sub-receipt lists.

As an example of the one or more sub-accounts receivable lists, there may be a sub-accounts receivable list in a state of being requested to be sold, a list of accounts receivable in a completed state, and the like.

Also, the merchant terminal can update the receipt list according to a specific condition.

When the merchant terminal updates the merchandise receipt list, the merchant terminal can regenerate an identifier (e.g., a serial number) for identifying the merchandise receivables again only for the sales receivable that can be sold.

Here, sales receivables that can be sold can be sales receivables excluding sales receivables that have already been requested to be sold and sales receivables that have been completed.

 The specific condition may be a certain point in time, a user input indicating an update, a number of accounts receivable exceeding a predefined threshold value, or the like.

Next, a description will be given of a step of purchasing the merchandise receipt requested by the merchant terminal at the purchase server and paying the purchase price.

As described above, the merchant terminal transmits a sales receipt sales request message for selling one or more receivables to the system operation server (S321), and the system operation server transmits the sales receipt sales request message to the receipt purchase server (S322).

The bond purchase server may be a server of a financial institution, that is, a bank server, or the like.

When the sales receipt sales commission is added to each sales receivable (through a contract between the merchant and the financial institution), the merchant terminal collects a certain number of receivables and transmits a single sales receipt request message.

Alternatively, the merchant terminal may transmit a sales receipt sales request message including one sales receipt when one sales receipt amount is larger than a predetermined amount.

This is because, even if a fee is imposed, a large amount of cash can be immediately recovered from the position of the merchant.

Also, the merchant terminal may not be included in the sales receipt sales request message in the case of the sales receivable excluding sales.

As an example of non-sales trade receivables, trade receivables that are more advantageous in terms of cost than those that are not sold.

For example, if you are paid late for a period of time through a contract with a (credit) card issuer, then it is better not to sell the trade receivables for accounts receivable that are more likely to benefit from the payment, It may be an ex-trade receivable.

Thereafter, when the bond purchase server receives the sales receipt sales request message through the system operator server, the receipt purchase server determines whether or not to purchase the sales receipt based on the information included in the received sales receipt sales message (S323).

Whether or not the accounts related to payment of the purchase receipt amount is established as an account owned by a financial institution (for example, a bank or the like) operating the bond purchase server, whether the account is purchased or not, Whether or not the information in the sales receipt sales request message is valid, and the like.

The account associated with payment of the purchase receipt purchase amount may be a virtual account managed for each merchant and allocated for each specific merchant.

In addition, the bond purchase server may similarly assign an account number related to the account to the franchisees of the same business type or franchisees.

For example, a virtual account number assignment for ten franchisee franchises is xxxx1, xxxx2, ... , xxxx10, the same number can be used for the first part, and the second part can be assigned differently.

Thereafter, when it is determined that there is no abnormality in the purchase of the receivable requested by the buyer, the buyer purchases the receivable requested for sale and pays the purchase price to the exclusive virtual account of the merchant S324).

Here, the bond buying server may transmit a purchase payment message to the device connected to the merchant terminal and / or the merchant terminal through the system operation server, which informs the payment of the purchase price.

The purchase price present message may include a purchase payment date, a purchase price payment number, a deposited bank and account number, a merchant number, card company information, and the like.

Here, the bond purchase server may further perform the following procedure before paying the purchase price to the exclusive virtual account of the merchant. This is to prevent the payment of the purchase price from being paid to the merchant who has no legitimate authority.

That is, before the bond purchase server makes payment of the purchase receipt purchase price, the server (the device of the user) which is connected to the merchant terminal and / or the merchant terminal and registered as a device to receive the purchase payment payment related information in advance (Or password) such as OTP (One-Time-Password).

Thereafter, when receiving the input of the same number as the authentication number from the merchant terminal or the device, the bond purchase server pays the purchase receipt purchase price to the virtual account of the corresponding merchant.

In addition, when the bond purchase server has paid the purchase price to the virtual account, the bond purchase server transmits to the payment approval server a prepayment message indicating that the customer himself / herself has paid for the sales receipt corresponding to the specific sales slip Can be transmitted.

The prepayment message may include sales voucher identification information that can identify a voucher corresponding to the purchased trade receipt.

In addition, when the payment approval server receives the pre-payment message from the bond purchase server, the payment approval server may transmit a confirmation message to the bond purchase server.

The confirmation message may include an authentication number associated with the payment confirmation.

The authentication number associated with the payment confirmation is received from the bond purchase server with an input having the same number as the authentication number before transferring the amount of the sales slip related to the purchased receipt of the payment approval server to the bond purchase server , It can be used to transmit the corresponding amount to the bond purchase server.

The purchase purchase price paid by the bond purchase server may be an amount excluding the predetermined fee (s) from the sales amount of the sales receipt.

The predetermined fee may include a receivable discount commission and a card fee set through a contract between the financial institution that operates the bond purchase server and the merchant.

In another embodiment, when receiving a plurality of merchandise sales request messages from one or more merchant terminals, the bond purchase server may decide to purchase a trade receivable in consideration of specific matters, You can decide to buy the bonds.

The above specific items include sales data (transaction amount, loan status, creditworthiness, etc.) with a financial institution (e.g., a bank) that operates the sales receipt purchase server, (Ie, how much franchises the company has), the location of the merchant (because the deposit or sales of the merchant may vary depending on the location), the type of service and / Or the number, the degree of awareness such as the presence / frequency of the broadcast of the merchant, and the like.

That is, the bond purchase server can determine whether to purchase a trade receivable or the number of trade receivables to be purchased or to prioritize a plurality of trade receivable sale request messages based on the specific matter, .

As another embodiment, the bond purchase server may determine whether the merchant is an affiliate shop for VIP customers, an evaluation of a cardholder who has generated a sales receipt (that is, a financial institution (a bank) Etc.), it is possible to determine the priority of the trade receivable to be purchased.

Next, a step of settlement of the paid purchase price between the bond purchase server and the payment approval server will be described.

After receiving the merchandise purchase price, the bond purchase server transmits a purchase payment request message to the payment approval server corresponding to the credit card company (S331).

Thereafter, the payment approval server confirms whether the sales receipt or the sales slip related to the receivable is related to the sales slip approved by itself (S332).

If it is determined that there is no abnormality, the payment approval server transmits the requested purchase price to the bond purchase server (S333).

Here, the payment approval server may transmit a purchase payment payment completion message informing that the purchase price has been paid to the merchant terminal and / or the bond purchase server at the same time of payment of the purchase price.

The transmission / reception of messages or information between the merchant terminal and the bond purchase server mentioned above can be performed through the system operation server.

<Merchant terminal operation for sales receipt sales>

4 is a diagram illustrating an example of the operation of a merchant terminal for selling a sales receipt proposed in the present specification.

It is assumed that the merchant terminal carries out a function related to the sales of the receivables and includes the necessary modules for performing this.

First, when the merchant terminal senses an input of a credit card payment request from the user, the merchant terminal transmits a payment approval request related to the use of the card to the payment relay server (S410).

Then, the merchant terminal receives a response to the payment approval request from the payment relay server (S420). Here, the response to the payment approval request may be payment approval.

Then, the merchant terminal outputs a sales slip related to the credit card payment request, and generates a sales receipt corresponding to the sales slip (S430).

Then, the merchant terminal transmits a sales receipt sales request message for selling the receivable to the system operation server (S440).

Thereafter, the merchant terminal receives a response message to the sales receipt sales request message through the system operation server (S450).

The response message may be information indicating that the purchasing rejection of the bond purchase server or the payment of purchase approval / purchase price has been completed.

As shown in FIG. 3, the sales receipt sales request message may be transmitted if the automatic setting function satisfies a certain condition, or may be transmitted to the bond purchase server when receiving a user's input.

As discussed above, the merchant bond sales system and method of the merchant proposed in this specification can be used to sell the receivables by bond trading method without having to deposit the money in the financial institution first, .

In addition, since the merchant registers a virtual account for exclusive use of sales receivables in advance with the financial institution (bank), and the financial institution pays the purchase price only to the registered account, the problem that the account registered by the merchant's state or a third party is changed .

As a result, the financial institution (bank) has the effect of minimizing the risk of erroneously paying the purchase price.

Each of the settlement methods performed in the merchandise sales system proposed herein may be implemented in a form of a program that can be executed through various computer means and recorded in a computer readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program recorded on the medium may be those specially designed and constructed for the present invention or may be those known to those skilled in the computer software.

Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of programs include high-level language code that can be executed by a computer using an interpreter or the like, as well as machine code as produced by a compiler. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined by the equivalents of the claims, as well as the claims.

100: Sales receipt sales system 140: System operation (g) Server
110: Merchant terminal 150: Bond purchase server
120: Payment relay server
130: Approval Approval Server

Claims (1)

In the trade receivable sales system,
A payment approval request including the sensed credit card related information and merchant store information is received and a payment approval response including an approval result for the payment approval request is received, A merchant terminal for outputting a sales slip based on a payment approval response, generating a sales receipt corresponding to the output sales slip, and transmitting a sales receipt sales request message for selling the generated sales receipt;
Determines the approval rejection or approval permission by comparing the credit card-related information and the merchant store information included in the received payment approval request with the previously stored credit card member data and the merchant store data, A settlement approval server for transmitting the settlement approval response including the sales slip and paying a price related to the sales slip;
The method comprising: receiving the merchandise sales request message; determining whether to purchase the one or more merchandise receivables included in the received merchandise sales request message; comparing the purchase amount of the purchased merchandise receipt to an account Said bond buying server paying said bond purchase server;
A payment relay server connected to the merchant terminal and the payment approval server via a first communication network to transmit and receive a message; And
And a system operation server connected to the merchant terminal and the payment approval server via a second communication network to transmit and receive a message,
The settlement approval request further includes a sales receipt sales notification information indicating that the credit card settlement amount corresponding to the approval approval request is to be directly paid through the bond purchase server,
Wherein the sales receipt sales request message comprises one or more receivables,
The trade receivable includes a trade receipt identifier for distinguishing the generated receivables from each other,
The sales receipt sales request message includes a plurality of receivables when the amount of the receivables is greater than a specified amount or when a commission for sales of each of the receivables is added, Sales receivable sales system.

Images