JP6641557B2 - Payment processing device, payment system, payment processing method, and program - Google Patents

Description

  The present invention relates to a payment processing device, a payment system, a payment processing method, and a program.

  In recent years, card payment transactions using payment cards such as credit cards have been widely used. In a payment system for performing card payment transactions, for example, a credit limit is set according to the credit card member, and based on the set credit limit, it is determined whether a credit card transaction is possible. A confirmation is performed. Then, the payment system executes a card payment transaction according to the result of the credit confirmation (for example, see Patent Document 1).

JP-A-2004-145894

  By the way, in the above-described settlement system, transactions directly related to business between companies, such as purchasing, may be performed using a settlement card such as a credit card. However, in the above-mentioned settlement system, the usage limit is set in accordance with, for example, the performance of the company, and the usage limit is often less than the transaction amount such as purchase, and thus, the amount of credit between companies directly related to the business is low. It is rarely used for payment card payment transactions (hereinafter referred to as card payment transactions). Therefore, a settlement system that can increase the use of card settlement transactions between companies has been desired.

  The present invention has been made to solve the above problems, and an object of the present invention is to provide a payment processing apparatus, a payment system, a payment processing method, and a program that can increase the use of card payment transactions between companies. It is in.

  In order to solve the above problem, one embodiment of the present invention stores receivable user information in which supplier identification information for identifying a supplier who sells a product and buyer identification information for identifying a buyer who purchases a product are associated with each other. Based on the receivable user information stored in the receivable user storage unit, the settlement of a card transaction using a settlement card is executed, and in the card transaction, the supplier identification indicating a supplier who sold a product. Information, the buyer identification information indicating a buyer who has purchased the product, the transaction amount of the card transaction, an account receivable amount using the receivable amount in the card transaction of the transaction amount, and the transaction amount of the transaction amount. A settlement processing unit for storing transaction information in which a transaction amount associated with a credit use amount utilizing credit of the settlement card is stored in a transaction information storage unit; The transaction information stored in the unit is aggregated at least for each of the supplier identification information and the buyer identification information stored in the receivable user storage unit, and based on the aggregation result, the supplier identification information A settlement processing unit for determining the sales amount of the supplier corresponding to the buyer identification information and determining the payment amount of the buyer corresponding to the buyer identification information.

  In one embodiment of the present invention, in the above-described settlement processing device, the settlement processing unit includes, among the transaction information stored in the transaction information storage unit, the transaction amount corresponding to the supplier identification information; The receivable amount corresponding to the buyer identification information associated with the supplier identification information stored in the receivable user storage unit is aggregated for each supplier identification information, and the total amount of the transaction amount is calculated. The amount obtained by subtracting the total amount of the accounts receivable from is determined as the sales amount of the supplier, and at least the credit amount corresponding to the buyer identification information is totaled for each of the buyer identification information, and the credit utilization amount is calculated. It is characterized in that the total amount of money is fixed as the payment amount of the buyer.

In one embodiment of the present invention, in the above-described settlement processing device, the credit use included in the transaction information corresponding to the receivable user information is based on the receivable amount corresponding to the receivable user information. A receivable reassignment unit for exchanging the amount with the receivable use amount, the settlement processing unit includes:
For the user corresponding to the accounts receivable user information, one of a process for determining the sales amount of the supplier and a process for determining the payment amount of the buyer is executed. .

In one embodiment of the present invention, in the settlement processing device, the settlement processing unit includes:
When determining the sales amount of the supplier, a sales confirmation request including an amount obtained by subtracting the total amount of the accounts receivable from the total amount of the transaction amounts, a member store management device that manages the member store as the supplier When the payment amount of the buyer is determined, a payment determination request including the credit usage amount is transmitted to a card management device that manages the payment card.

  Further, according to one aspect of the present invention, in the above-described settlement processing device, based on the transaction information stored in the transaction information storage unit, in response to an output request for requesting output of a card transaction usage statement, It is characterized by including a statement output processing unit that generates information indicating the usage statement for each supplier or buyer, and outputs the generated information indicating the usage statement.

  According to another aspect of the present invention, there is provided a payment processing device described above, a member store management device that manages a member store of a payment card used for a transaction, and a card management device that manages the payment card. It is a settlement system characterized by the following.

  In one embodiment of the present invention, the settlement processing unit stores the accounts receivable user information in which supplier identification information for identifying a supplier who sells the product and buyer identification information for identifying a buyer who purchases the product. Based on the receivable user information stored in the receivable user storage unit, the settlement of a card transaction using a payment card is executed, and in the card transaction, the supplier identification information indicating a supplier who sold a product. And the buyer identification information indicating the buyer who purchased the product, the transaction amount of the card transaction, the sales amount using the receivable amount in the card transaction of the transaction amount, and the transaction amount A settlement processing step of storing transaction information associated with a credit use amount using the credit of the settlement card in the transaction information storage unit, and a settlement processing unit, The transaction information stored in the transaction information storage unit, at least for each of the supplier identification information and for each of the buyer identification information stored in the accounts receivable user storage unit, based on the aggregation result, A settlement processing step of determining the sales amount of the supplier corresponding to the supplier identification information and determining the payment amount of the buyer corresponding to the buyer identification information.

  According to another aspect of the present invention, there is provided a computer which stores, on a computer, accounts receivable user information in which supplier identification information for identifying a supplier who sells goods and buyer identification information for identifying a buyer who purchases goods are associated with each other. Based on the accounts receivable user information stored in the user storage unit, executes the settlement of the card transaction using a settlement card, in the card transaction, the supplier identification information indicating the supplier who sold the product, The buyer identification information indicating the buyer who purchased the product, the transaction amount of the card transaction, the receivable amount using the receivable amount in the card transaction of the transaction amount, and the transaction amount of the transaction amount A settlement processing step of storing transaction information in which a transaction amount associated with a credit use amount using the credit of a settlement card is stored in a transaction information storage unit; The transaction information stored in the storage unit is aggregated at least for each of the supplier identification information and the buyer identification information stored in the receivable user storage unit, and the supplier identification is performed based on the aggregation result. A payment processing step of determining the sales amount of the supplier corresponding to the information and determining the payment amount of the buyer corresponding to the buyer identification information.

  According to the present invention, it is possible to increase the use of card settlement transactions between companies.

It is a block diagram showing an example of the settlement system by a 1st embodiment. FIG. 4 is a diagram illustrating an example of data stored in a member store management storage unit, a card management storage unit, and an account storage unit according to the first embodiment. FIG. 4 is a diagram illustrating an example of data stored in a supplier information storage unit, a buyer information storage unit, and a receivable user storage unit according to the first embodiment. FIG. 5 is a diagram illustrating an example of data stored in a transaction information storage unit according to the first embodiment. FIG. 5 is a diagram illustrating an example of data stored in a sales information storage unit according to the first embodiment. It is a figure showing an example of the commission in the settlement system by a 1st embodiment. It is a figure showing an example of operation of registration processing of a member store by a 1st embodiment. It is a figure showing an example of operation of registration processing of a card user by a 1st embodiment. It is a figure showing an example of operation of an application processing of receivables use by a 1st embodiment. It is a figure showing an example of operation of the settlement processing using the receivable according to the first embodiment. It is a figure showing an example of operation of payment cancellation by a 1st embodiment. It is a flowchart which shows an example of the operation | movement of a loan change in 1st Embodiment. FIG. 5 is a diagram illustrating an example of an operation of a payment process according to the first embodiment. It is a flowchart which shows an example of the finalization process of the sales amount of a supplier in 1st Embodiment. It is a flow chart which shows an example of finalization processing of a buyer's payment amount in a 1st embodiment. It is a figure explaining an example of operation of the settlement process by a 1st embodiment. It is a flowchart which shows the modification of the operation | movement of a claim change in 1st Embodiment. It is a block diagram showing an example of the settlement system by a 2nd embodiment. It is a figure showing the example of the data which the receivables storage part in a 2nd embodiment memorizes. It is a block diagram showing an example of the settlement system by a 3rd embodiment. It is a figure explaining an example of operation of settlement processing by a 3rd embodiment. It is the 1st figure explaining the modification of the settlement system by the embodiment of the present invention. It is the 2nd figure explaining the modification of the settlement system by the embodiment of the present invention. It is the 3rd figure explaining the modification of the settlement system by the embodiment of the present invention.

Hereinafter, a payment system according to an embodiment of the present invention will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a block diagram illustrating an example of a payment system 1 according to the first embodiment.
As shown in this figure, the settlement system 1 according to the present embodiment includes a settlement portal server 10, a member store management company server 20, a card issuing company server 30, a member store terminal 40, and a card user terminal 50. Have. The settlement portal server 10, the member store management company server 20, the card issuing company server 30, the member store terminal 40, and the card user terminal 50 can be connected to each other via the network NW1.

In the example shown in FIG. 1, although not shown for the sake of explanation, the settlement system 1 includes a member store management company server 20, a card issuing company server 30, a member store terminal 40, and a card user terminal 50, It is possible to have more than one.
In the present embodiment, for example, a payment system 1 using a credit card will be described as an example of a payment card used for card transactions such as a credit card, a debit card, and a prepaid card.

  The member store management company server 20 (an example of a member store management device) is a server device owned by a member store management company (acquirer) that manages credit card member stores, and manages contracted member stores. The member store management company server 20 includes, for example, a member store management storage unit 21.

  The member store management storage unit 21 stores, for example, member store contract information. Here, the member store contract information is contract information of the member store contracting with the member store management company, and is information registered in advance in the member store management company. The member store management storage unit 21 stores, for example, member store numbers and member store contract information in association with each other. The member store number is an example of member store identification information for identifying a member store. The member store management storage unit 21 stores, for example, member store contract information as shown in FIG.

FIG. 2A is a diagram illustrating an example of data stored in the member store management storage unit 21 in the present embodiment.
In the example shown in FIG. 2A, the member store management storage unit 21 stores “member store number”, “member store name”, “address”, “telephone number”, “representative name”, and the like in association with each other. ing. Here, the member store contract information is, for example, information such as “member store name”, “address”, “telephone number”, and “representative name”.
For example, a member store whose "member store number" is "123456890" indicates that the "member store name" is "XX member store" and the "address" is "Minato-ku, Tokyo ...". ing. The “phone number” of this member store is “03-XXXX-XXXX”, indicating that the “representative name” is “Hanako Yamada”.

Returning to the description of FIG. 1, the card issuing company server 30 (an example of a card management device) is a server device owned by a card issuing company (Issuer) that issues a credit card and manages a credit card usage limit and the like. Yes, manage issued credit cards. The card issuing company server 30, for example, manages the credit limit of each credit card, receives a credit confirmation request for confirming whether settlement using credit card credit is possible, and sends the confirmation result to the request source. Send to
Further, the card issuing company server 30 includes, for example, a card management storage unit 31.

  The card management storage unit 31 stores, for example, card contract information. Here, the card contract information is credit card contract information issued by the card issuing company, and is information registered in advance with the card issuing company. The card management storage unit 31 stores, for example, a card number and card contract information in association with each other. The card number is, for example, a credit card number, and is an example of card identification information for identifying a credit card. The card management storage unit 31 stores card contract information, for example, as shown in FIG.

FIG. 2B is a diagram illustrating an example of data stored in the card management storage unit 31 according to the present embodiment.
In the example illustrated in FIG. 2B, the card management storage unit 31 associates “card number”, “card expiration date”, “corporate name”, “affiliated department”, “user name”, and the like. I remember. Here, the card contract information is, for example, information such as “card expiration date”, “corporate name”, “affiliated department”, and “user name”. The example illustrated in FIG. 2B is card contract information of a corporate card contracted by a corporation such as a company.
For example, for a credit card whose “card number” is “1234-1234-5678-9012”, the “card expiration date” is “XX / 'XX” and the “corporation name” is “XX Corporation”. ". Also, the "department" of the user of this credit card is "XX department", which indicates that the "user name" is "Hanako Yamada".

Returning to the description of FIG. 1 again, the affiliated store terminal 40 (an example of a user terminal) is a terminal device owned by an affiliated store (supplier) who sells products through portal use transactions. Here, the portal use transaction refers to a credit card transaction using a service provided by the settlement system 1. That is, the portal use transaction is an example of a card transaction using a credit card. The member store terminal 40 is connectable to the settlement portal server 10 via the network NW1, and by connecting to the settlement portal server 10, a process for approving the use of accounts receivable, which will be described later, is provided to the buyer (buyer) of the product. It executes various processes such as a process for requesting payment. In addition, the member store terminal 40 outputs information such as a use statement of a portal use transaction (card transaction) using the settlement portal server 10 by connecting to the settlement portal server 10, for example.
In addition, the member store terminal 40 includes an input unit 41 and a display unit 42.

The input unit 41 is, for example, a keyboard, a mouse, or the like, and receives various kinds of necessary information from a user of the member store terminal 40.
The display unit 42 (an example of an output unit) is a display device such as a liquid crystal display, and displays various information. The display unit 42 displays, for example, information indicating a card transaction usage statement.

The card user terminal 50 (an example of a user terminal) is a terminal device owned by a card user (buyer) who purchases a product through a portal use transaction. Here, the card user (buyer) may be the same as the member store (supplier). In the present embodiment, the card user (buyer) and the member store (supplier) are associated with each other, and the receivable is receivable. Make it available for portal use transactions. The card user terminal 50 can be connected to the settlement portal server 10 via the network NW1, and by connecting to the settlement portal server 10, a process for requesting the use of accounts receivable, which will be described later, a merchandise seller (supplier) Execute various processes such as a process for executing payment. In addition, the card user terminal 50 outputs information such as a use statement of a portal use transaction using the settlement portal server 10 by connecting to the settlement portal server 10, for example.
Further, the card user terminal 50 includes an input unit 51 and a display unit 52.

The input unit 51 is, for example, a keyboard, a mouse, or the like, and receives various kinds of necessary information from a user of the card user terminal 50.
The display unit 52 (an example of an output unit) is, for example, a display device such as a liquid crystal display, and displays various information. The display unit 52 displays, for example, information indicating a use statement of the portal use transaction.

The settlement portal server 10 (an example of a settlement processing device) is, for example, a server device that provides a settlement portal service between companies using a credit card (hereinafter, referred to as an inter-company settlement service). The settlement portal server 10 includes, for example, an NW (network) communication unit 11, a storage unit 60, and a control unit 70.
The NW communication unit 11 performs various communications by connecting to the network NW1.

  The storage unit 60 stores information used for various processes of the settlement portal server 10. The storage unit 60 includes, for example, an account storage unit 61, a supplier information storage unit 62, a buyer information storage unit 63, a receivable user storage unit 64, a transaction information storage unit 65, a sales information storage unit 66, A fee storage unit 67;

The account storage unit 61 stores login information such as a login ID and a password for connecting to the settlement portal server 10. The login information is stored in the account storage unit 61 when the member store or card user registers as a member in the inter-company settlement service. The account storage unit 61 stores, for example, login information as shown in FIG.
FIG. 2C is a diagram illustrating an example of data stored in the account storage unit 61 according to the present embodiment.
In this figure, the account storage unit 61 stores, for example, a “login ID”, a “password”, a “password setting date”, a “member store number”, and a “user name (reading)” in association with each other. . In addition, since both the member store and the card user are connected to the settlement portal server 10, a “member store number” is associated with the “login ID” for the member store, and the card user's A “user name (reading)” is associated with the “login ID”.

  For example, in the example shown in FIG. 2C, the “password” corresponding to the “login ID” “11111” is “********” and the “member store number” is “ 1234567890 ". Also, for example, the “password” corresponding to the “login ID” “22222” is “********”, and the “user name (reading)” is “Yamada Hanako”. It is shown that.

  Returning to the description of FIG. 1 again, the supplier information storage unit 62 (an example of a first user storage unit) is information on a supplier (member store) registered as a member in the inter-company settlement service provided by the settlement portal server 10. Store certain supplier information. The supplier information storage unit 62 stores, for example, at least a member store number and a supplier ID (supplier identification information) in association with each other. Here, the supplier ID is, for example, supplier member information (first member information), and is an example of member store identification information for identifying a member store. The supplier information is stored in the supplier information storage unit 62 when the member store registers as a member for the inter-company settlement service. The supplier information storage unit 62 stores supplier information, for example, as shown in FIG.

FIG. 3A is a diagram illustrating an example of data stored in the supplier information storage unit 62 according to the present embodiment.
In this figure, the supplier information storage unit 62 stores, for example, “supplier ID”, “login ID”, “member store number”, “member store name”, “address”, and “telephone number” in association with each other. I have. Here, "address" and "telephone number" indicate the address and telephone number of the member store.
For example, in the example shown in FIG. 3A, it is assumed that the “login ID” corresponding to the member store with the “supplier ID” of “S111” is “11111” and the “member store number” is “123456890”. Is shown. Also, the “member store name” of this member store is “XX member store”, and the “address” is “Minato-ku, Tokyo...”.

  Returning to the description of FIG. 1 again, the buyer information storage unit 63 (an example of a second user storage unit) stores information on buyers (card users) registered as members in the inter-company payment service provided by the payment portal server 10. Is stored. The buyer information storage unit 63 stores, for example, at least a card number and a buyer ID (buyer identification information) in association with each other. Here, the buyer ID is, for example, buyer member information (second member information), and is an example of card identification information for identifying a credit card. The buyer information is stored in the buyer information storage unit 63 when the card user registers as a member in the inter-company payment service. The buyer information storage unit 63 stores buyer information, for example, as shown in FIG.

FIG. 3B is a diagram illustrating an example of data stored in the buyer information storage unit 63 in the present embodiment.
In this figure, the buyer information storage unit 63 stores, for example, “buyer ID”, “login ID”, “card number”, “card expiration date”, “corporate name”, “affiliated department”, “user name”. ,..., “Address”, “telephone number”, etc. are stored in association with each other.
For example, in the example shown in FIG. 3B, the “login ID” corresponding to the card user whose “buyer ID” is “B222” is “22222”, and the “card number” is “1234-1234-5678-”. 9012 ", indicating that the" card expiration date "is" XX / 'XX ". It also indicates that the "corporate name" and "department" to which this card user belongs are "XX Corporation" and "XX department", and that the "user name" is "Hanako Yamada". I have.

  Returning to the description of FIG. 1 again, the accounts receivable user storage unit 64 stores information on accounts receivable users who use accounts receivable in portal use settlement (settlement of card transactions). Here, the accounts receivable user information is information that links a supplier (a member store) and a buyer (a card user), and is, for example, information that associates at least a supplier ID and a buyer ID. The accounts receivable user information is stored in the accounts receivable user storage unit 64 when the use of accounts receivable is applied and the use of accounts receivable is approved. The receivable user storage unit 64 stores receivable user information, for example, as shown in FIG.

FIG. 3C is a diagram illustrating an example of data stored in the receivable user storage unit 64 in the present embodiment.
In this figure, the receivable user storage unit 64 stores, for example, “supplier ID”, “buyer ID”, “application date”, “applicant”, “approval date”, and the like in association with each other. Here, “application date” and “applicant” indicate the date of application for the use of accounts receivable and the buyer ID of the application. The “approval date” indicates the date when the use of the receivable was approved.
For example, the example illustrated in FIG. 3C indicates that “S111” of “supplier ID” and “B222” of “buyer ID” are linked (associated). In this way, by associating the “supplier ID” (“S111”) with the “buyer ID” (“B222”), the accounts receivable sold by the supplier (member store) corresponding to the “supplier ID” (“S111”) Can be used for the portal use settlement using the settlement portal server 10 by the "buyer ID"("B222").

  Returning to the description of FIG. 1 again, the transaction information storage unit 65 stores transaction information indicating the history of card transactions. The transaction information storage unit 65 includes, for example, an invoice number, a supplier ID indicating a supplier who sells a product, a buyer ID indicating a buyer who purchases a product, a portal usage amount, and a sales amount of the usage amount. At least the amount and the credit use amount are stored in association with each other. Here, the portal usage amount is a transaction amount of a card transaction using the inter-company settlement service, the receivable amount is a usage amount from the receivable amount, and the credit amount is A payment amount using credit card credit (card payment amount). The credit usage amount is limited by the credit card usage limit (credit limit). The transaction information storage unit 65 stores transaction information, for example, as shown in FIG.

FIG. 4 is a diagram illustrating an example of data stored in the transaction information storage unit 65 in the present embodiment.
In this figure, the transaction information storage unit 65 stores, for example, “invoice number”, “supplier ID”, “buyer ID”, “action”, “execution date”, “billing amount”, “credit usage amount”, “ .., “Buyer name”, “supplier name”, and the like are stored in association with each other. Here, “bill number” indicates the number of the claim in the transaction, and “action” indicates the state of the bill such as “issue bill” and “pay”. Also, the “billing amount” indicates the portal usage amount, the “credit usage amount” indicates the payment amount (card payment amount) using the credit card credit as described above, and the “account usage amount” A transaction amount (amount used from the receivable) using the receivable amount is shown. “Accounts Receivable Supplier” indicates a supplier ID of a supplier who holds accounts receivable.

  Each row (each record) of the transaction information stored in the transaction information storage unit 65 is added to the transaction information storage unit 65 each time the “action” changes. For example, a record whose “action” is “issue invoice” is stored in the transaction information storage unit 65 when an invoice is issued by the supplier, and a record whose “action” is “pay” is Is stored in the transaction information storage unit 65 when the payment is settled. Also, in FIG. 4, the record of the final (latest) state (“action”) of each bill number is hatched and displayed.

  In the example shown in FIG. 4, for example, in the latest (final) transaction information in which the "invoice number" is "1", the "supplier ID" is "S00B1" and the "buyer ID" is "B00A1". , "Action" is "payment". Further, in this transaction information, the settlement of the payment is executed on “YYYY / MM / DD” with the “execution date”, the “billed amount” is “1,000,000” (1 million yen), and the “credit The "use amount" is "1,000,000" (1,000,000 yen). Further, this transaction information indicates that the “account receivable amount” is “0” (receivable is not used), and that the merchandise has been sold from “company B” to “company A”.

  Returning to the description of FIG. 1 again, the sales information storage unit 66 stores sales information for each user (for each supplier and each buyer) obtained by totaling the transaction information stored in the transaction information storage unit 65 described above. The sales information storage unit 66 stores sales information, for example, as shown in FIG.

FIG. 5 is a diagram illustrating an example of data stored in the sales information storage unit 66 in the present embodiment.
In this figure, the sales information storage unit 66 stores, for example, “use date”, “ID”, “unconfirmed / confirmed”, “transaction total amount”, “account use amount”, “transfer total amount”, And the “total payment amount” are stored in association with each other. Here, “use date” indicates the date when the sales information is totaled, “ID” indicates the supplier ID or buyer ID which is the member information for identifying the user (member), and “undetermined”. “/ Fixed” indicates that “unconfirmed” indicates a state before the closing day, and “Fixed” indicates a state after the closing day. In the example shown in FIG. 5, it is assumed that sales information is totaled every month. The “transaction total amount” indicates the total amount of one month of portal use transactions, and the “receivable amount” indicates the total amount of accounts receivable. The “total transfer amount” indicates the total amount for one month to be transferred to the supplier, and the “total payment amount” indicates the total amount for one month paid by the buyer.

  For example, in the example shown in FIG. 5, in the sales information corresponding to “S00B1” with “ID” of “June 2015” having “use date” of “June 2015”, “Undetermined / Fixed” is “Fixed”, The total transaction amount is "1,500,000" (1.5 million yen), and the "account receivable amount" is "1,300,000" (1.3 million yen). This sales information also indicates that the “transfer total amount” is “200,000” (200,000 yen). Since the “ID” of “S00B1” is the supplier ID of “Company B”, the sales information for “June 2015” is “200,000” (200,000) for “Company B”. Yen).

  Returning to the description of FIG. 1 again, the fee storage unit 67 stores information relating to various fees collected or paid by using the inter-company settlement service including credit use settlement. Here, the credit use settlement is a settlement using credit of a credit card. The fee storage unit 67 stores, for example, a supplier ID or a buyer ID indicating a user (member) in association with fee information indicating various fees. Here, the commission information is for collecting or paying a predetermined ratio for a predetermined amount, for example, and the predetermined ratio may be set to a different value for each user (member). . Further, the fee information may be a fixed amount (for example, a monthly amount of XXX yen) instead of the predetermined ratio. As a type of the fee information, for example, a fee as shown in FIG. 6 can be considered.

FIG. 6 is a diagram illustrating an example of a commission in the settlement system 1 according to the present embodiment.
In this figure, "item" indicates the type of fee, and "object" indicates the target person (buyer or supplier) of the fee. Further, “collection from user / payment to user” indicates whether a fee is collected or paid.
For example, “discount member store fee” of “item” indicates a fee for the amount used as accounts receivable (amount of accounts receivable) of the portal use amount.

Returning to the description of FIG. 1 again, the control unit 70 is, for example, a processor including a CPU (Central Processing Unit) and controls the settlement portal server 10 in a comprehensive manner. The control unit 70 transmits and receives information to and from the member store management company server 20, card issuing company server 30, member store terminal 40, and card user terminal 50 via the NW communication unit 11, and executes various processes. I do. The control unit 70, for example, a member registration process of the inter-company payment service, determines whether or not a portal use transaction is possible, performs a payment process for the portal use transaction, and setstle the settlement of the portal use transaction. It executes various processes such as a process and a detail output process for outputting details of a transaction using the portal.
The control unit 70 includes a virtual member store management unit 71, a virtual card management unit 72, a transaction determination unit 73, a settlement processing unit 74, a bond reassignment unit 75, a settlement processing unit 76, and a statement output processing unit 77. And

  The registration unit 80 executes processing for registering a member of the inter-company settlement service and associating (associating) the supplier ID with the buyer ID when using the accounts receivable. The registration unit 80 includes, for example, a member store information acquisition unit 81, a supplier registration unit 82, a card information acquisition unit 83, a buyer registration unit 84, and a receivables use registration unit 85.

  The member store information acquisition unit 81 (an example of a first acquisition unit) reads from the member store management storage unit 21 of the member store management company server 20 described above in response to a supplier (member store) registration application (first use application). Get member store contract information. Here, the registration application of the supplier (member store) includes, for example, the member store number and the user information (first application information) of the supplier applied by the member store. The member store information acquiring unit 81 acquires member store contract information corresponding to the member store number included in the supplier (member store) registration application. Specifically, the member store information acquiring unit 81 acquires, for example, member store contract information as shown in FIG. Note that the member store information acquisition unit 81 may cause the storage unit 60 to store the acquired member store contract information.

The supplier registration unit 82 (an example of a first registration unit) responds to the application for registration of the supplier by using the user information of the supplier included in the application for registration of the supplier and the member store contract information acquired by the member store information acquisition unit 81. , A supplier ID (first member information) is issued to the member store number included in the registration application of the supplier. Here, the user information of the supplier (member store) is, for example, information such as the name of the member store, the address of the member store, the telephone number of the member store, and the name of the representative of the member store.
The supplier registration unit 82 compares, for example, the user information of the supplier included in the supplier registration application with the member store contract information acquired from the member store management storage unit 21 by the member store information acquisition unit 81, and compares the comparison result. , A supplier ID is issued. That is, the supplier registration unit 82 determines whether or not information of a predetermined item of the user information of the supplier matches information of the same item of the member store contract information. Issue.

  In addition, the supplier registration unit 82 issues a supplier ID in response to the application for registration of the supplier, and causes the supplier information storage unit 62 to store at least supplier information in which the member store number is associated with the supplier ID. Specifically, the supplier registration unit 82 causes the supplier information storage unit 62 to store the supplier information as shown in FIG. In addition, the supplier registration unit 82 causes the account storage unit 61 to store the login information corresponding to the issued supplier ID, for example, as illustrated in FIG.

  The card information acquisition unit 83 (an example of a second acquisition unit) responds to a buyer (card user) registration application (second usage application) from the card management storage unit 31 of the card issuing company server 30 described above. Get information. Here, the registration application for the buyer (card user) includes, for example, a card number and buyer user information (second application information) applied by the card user of the credit card. The card information acquisition unit 83 acquires card contract information corresponding to the card number included in the registration application for the buyer (card user). Specifically, the card information acquisition unit 83 acquires, for example, card contract information as shown in FIG. Note that the card information acquisition unit 83 may cause the storage unit 60 to store the acquired card contract information.

In response to the buyer registration application, the buyer registration unit 84 (an example of a second registration unit) stores the buyer user information included in the buyer registration application and the card contract information acquired by the card information acquisition unit 83. Based on this, a buyer ID (second member information) is issued to the card number included in the registration application for the buyer. Here, the user information of the buyer (card user) is, for example, information such as a corporate name, an affiliated department, a user name, an address, a telephone number, and the like.
The buyer registration unit 84, for example, compares the buyer user information included in the buyer registration application with the card contract information acquired by the card information acquisition unit 83, and issues a buyer ID based on the comparison result. . That is, the buyer registration unit 84 determines whether or not the information of a predetermined item of the buyer's user information matches the information of the same item of the card contract information, and issues a buyer ID if they match. I do.

  The buyer registration unit 84 issues a buyer ID in response to a buyer registration application, and causes the buyer information storage unit 63 to store at least buyer information in which the card number is associated with the buyer ID. Specifically, the buyer registration unit 84 causes the buyer information storage unit 63 to store the buyer information as shown in FIG. Further, the buyer registration unit 84 causes the account storage unit 61 to store login information corresponding to the issued buyer ID, for example, as shown in FIG.

The accounts receivable registration unit 85 (an example of a third registration unit) stores a member store number stored in the supplier information storage unit 62 and buyer information storage in response to an accounts receivable application (third use application) for applying for accounts receivable. A process of associating (linking) with the card number stored by the unit 63 is executed. The receivable use registration unit 85 transmits, for example, a validity check request for confirming the validity of the credit card corresponding to the card number in response to the receivable use application, and responds to the confirmation result received in response to the validity check request. To associate the member store number with the card number.
Here, the receivables use registration unit 85 transmits the validity confirmation request to the member store management company server 20, and the member store management company server 20 transmits the validity confirmation request to the card issuing company server 30. That is, the receivables use registration unit 85 transmits a validity confirmation request to the card issuing company server 30 via the member store management company server 20.

Then, the accounts receivable registration unit 85 receives the confirmation result of the validity confirmation request from the card issuing company server 30 via the member store management company server 20, and if the confirmation result is “OK” (OK), Further, it approves the receivables application to the affiliated store corresponding to the affiliated store number. Here, when the receivable use registration unit 85 approves the use application, the receivable use registration unit 85 transmits the information requesting the approval to the member store terminal 40 corresponding to the member store number.
The information requesting the approval includes, for example, information such as the name of the buyer (name of the person in charge) and the name of the corporation as card user information (user information of the buyer). Then, when the receivables application is approved by the member store terminal 40, the receivables use registration unit 85 associates the member store number with the card number.

  More specifically, the accounts receivable registration unit 85 associates the supplier ID stored in the supplier information storage unit 62 with the buyer ID stored in the buyer information storage unit 63 in response to the receivable use application and stores the accounts receivable user storage. The member number is associated with the card number by storing it in the unit 64. Note that the receivable use application includes a buyer ID and a supplier ID corresponding to the user acquired from the user terminal (for example, the card user terminal 50).

  The virtual member store management unit 71 acts as a proxy for the member store management company server 20 (executes processing). For example, in response to a settlement request that requests settlement of a credit transaction (an example of settlement of a card transaction using a credit card), the virtual member store management unit 71 changes the credit use amount (card settlement amount) of the credit card. A credit check request for requesting whether or not the amount is equal to or less than the usage limit is transmitted to the card issuing company server 30 without passing through the member store management company server 20 (instead of the member store management company server 20). Here, the credit use amount refers to a settlement amount using credit of a credit card. Specifically, the virtual member store management unit 71 transmits a credit confirmation request to the card issuing company server 30 via the NW communication unit 11. Further, the virtual member store management unit 71 receives a confirmation result for the credit confirmation request from the card issuing company server 30 via the NW communication unit 11.

  In addition, in the settlement of the portal use transaction integrated (payment) by the settlement processing unit 76 described later, the virtual member store management unit 71 determines the payment amount of the card user indicating the credit card user (second payment request). (A settlement confirmation request) is transmitted to the card issuing company server 30 instead of the member store management company server 20. That is, the virtual member store management unit 71 transmits a confirmation request to the card issuing company server 30 via the NW communication unit 11.

The virtual card management unit 72 substitutes for the card issuing company server 30 (executes processing). For example, in the settlement of the portal use transaction integrated by the settlement processing unit 76, the virtual card management unit 72 issues a settlement request (first settlement confirmation request) for fixing the sales amount of the member store instead of the card issuing company server 30, It is received from the member store management company server 20. That is, the virtual card management unit 72 receives the confirmation request from the member store management company server 20 via the NW communication unit 11.
In addition, the virtual card management unit 72 receives the credit confirmation request from the member store management company server 20 instead of the card issuing company server 30. That is, the virtual card management unit 72 receives a credit confirmation request from the member store management company server 20 via the NW communication unit 11. In addition, the virtual card management unit 72 transmits a confirmation result for the credit confirmation request to the member store management company server 20 via the NW communication unit 11.

  The transaction determination unit 73 is configured to store at least the accounts receivable amount and the usage limit corresponding to the accounts receivable user information that associates at least the member store identification information (for example, supplier ID) with the card identification information (for example, buyer ID). It is determined whether settlement of the portal use transaction can be executed based on the. Here, the amount of accounts receivable is the amount of accounts receivable by a portal transaction, and is an example of the amount of accounts receivable (account receivable) by a card transaction using a credit card.

The usage limit is, for example, a credit line of a credit card. For example, when the accounts receivable user information including the buyer ID of the portal use transaction is stored in the accounts receivable user storage unit 64, the transaction determination unit 73 performs the sales corresponding to the receivable user information. Based on the credit holding amount (receivable amount) and the usage limit, it is determined whether or not settlement of the portal use transaction can be executed.
In addition, for example, when the receivable user information including the buyer ID of the portal use transaction is not stored in the receivable user storage unit 64, the transaction determining unit 73 stores the receivable user information in the buyer (credit card). It is determined whether the settlement of the credit use transaction can be executed based on the corresponding usage limit.
Here, in the credit use transaction, for example, when confirming whether or not the credit use amount is available based on the use limit amount, the transaction determination unit 73 requests the virtual member store management unit 71 to make a credit confirmation request. Is sent. Further, the credit use transaction is a card transaction using a credit line of a credit card, and the credit use amount is a transaction amount of the credit use transaction.

In the present embodiment, the transaction determination unit 73 determines that the settlement of the portal use transaction can be executed when the amount obtained by subtracting the amount of accounts receivable from the amount of use of the portal is equal to or less than the use limit. When the transaction determination unit 73 determines that the settlement of the portal use transaction is executable, the settlement processing unit 74 described later preferentially uses the accounts receivable amount for the settlement of the portal use transaction.
Specifically, for example, when the portal usage amount is equal to or less than the accounts receivable amount, the transaction determination unit 73 determines that settlement of the portal usage transaction is executable, and the settlement processing unit 74 described later Execute the settlement process of the portal use transaction by using.

When the portal usage amount exceeds the A / R holding amount, the transaction determination unit 73 sends a credit confirmation request to the virtual member store management unit 71 with the amount obtained by subtracting the A / R holding amount from the portal usage amount as the credit usage amount. Then, based on the confirmation result received in response to the credit confirmation request, it is determined whether the settlement of the credit use transaction can be executed. When the portal usage amount exceeds the A / R holding amount, the transaction determination unit 73 sends a credit confirmation request to the virtual member store management unit 71 with the amount obtained by subtracting the A / R holding amount from the portal usage amount as the credit usage amount. Then, the virtual member store management unit 71 transmits the credit confirmation request to the card issuing company server 30. Then, when the confirmation result is “OK” (when the credit use amount confirmed by the credit is equal to or less than the use limit amount), the settlement processing unit 74 described later uses the credit use amount to execute the portal use transaction. Execute the payment process.
It is assumed that the credit limit is reduced by the used credit amount by the card issuing company server 30 when the credit amount is used (when the confirmation result is “OK”). .

  Further, in the present embodiment, the transaction determination unit 73 calculates the amount of accounts receivable held corresponding to the target buyer of the portal use transaction every time the portal use transaction is performed. For example, based on the transaction information stored in the transaction information storage unit 65, the transaction determination unit 73 calculates the amount of accounts receivable that can be used for settlement of the transaction using the portal. Specifically, the transaction determination unit 73 first reads out the supplier ID associated with the target buyer ID from the receivable user storage unit 64. The transaction determination unit 73 extracts the transaction information corresponding to the read supplier ID from the transaction information stored in the transaction information storage unit 65, and calculates the amount of accounts receivable that can be used for settlement of the portal use transaction. .

  The settlement processing unit 74 executes the settlement of the portal use transaction when the above-described transaction determination unit 73 determines that the settlement of the portal use transaction can be executed. The settlement processing unit 74 executes settlement of the portal use transaction based on the accounts receivable user information stored in the accounts receivable user storage unit 64 that stores the accounts receivable user information, for example. Then, the settlement processing unit 74 causes the transaction information storage unit 65 to store the transaction information of the executed portal use transaction. That is, in the portal use transaction, the settlement processing unit 74 determines the supplier ID, the buyer ID, the portal use transaction amount, the sales amount of the transaction amount, and the credit card of the transaction amount. The transaction information associated with the credit use amount using the credit limit (use limit) is stored in the transaction information storage unit 65 (see FIG. 4).

  The receivable reassignment unit 75 executes a process of replacing the credit use amount included in the transaction information corresponding to the receivable user information with the receivable use amount based on the receivable holding amount corresponding to the receivable user information. . In other words, the reassignment unit 75 executes, for example, a process of replacing at least a part of the above-mentioned amount of accounts receivable with a credit card usage limit. For example, in the case where the receivable amount corresponding to the receivable user information is equal to or more than the credit use amount corresponding to the receivable user information, the receivable reassigning unit 75 calculates the credit use amount from the receivable amount. , Change to the credit limit.

  For example, the reassignment unit 75 calculates the amount of accounts receivable based on the transaction information stored in the transaction information storage unit 65 for each of the accounts receivable user information stored in the accounts receivable user storage unit 64. . When the calculated receivable holding amount is equal to or greater than the credit usage amount of the transaction information corresponding to the receivables user information, the receivable reassigning unit 75 makes a virtual membership request for the credit cancellation of the credit usage amount of the transaction information. The information is transmitted to the card issuing company server 30 via the store management unit 71. As a result, the credit limit of the credit card is increased by the amount of the canceled credit. Then, the loan reassigning unit 75 causes the transaction information storage unit 65 to add a new transaction information record in which the canceled credit use amount is replaced with the receivable use amount. It should be noted that the loan reassigning section 75 executes such a loan reassigning process periodically (for example, every day), for example, by a batch process.

The settlement processing unit 76 (an example of an integration processing unit) integrates settlement of a plurality of portal use transactions based on the transaction information stored in the transaction information storage unit 65. The settlement processing unit 76 adjusts the transaction amount of the portal use transaction for each supplier (member store) or each buyer (card user), for example. For example, the settlement processing unit 76 stores the transaction information stored in the transaction information storage unit 65 for each supplier ID stored in the supplier information storage unit 62 and for each buyer ID stored in the buyer information storage unit 63. Tally. Note that the settlement processing unit 76 converts the transaction information stored in the transaction information storage unit 65 into at least each supplier ID and each buyer ID stored in the accounts receivable user storage unit 64, or the associated supplier ID. And a buyer ID may be totaled. Then, the settlement processing unit 76 determines the sales amount of the supplier corresponding to the supplier ID and the payment amount of the buyer corresponding to the buyer ID based on the result of the aggregation.
Note that the settlement processing unit 76 causes the sales information storage unit 66 to store the totaled results as sales information, for example.

  Specifically, the settlement processing unit 76 stores, among the transaction information stored in the transaction information storage unit 65, the portal usage amount corresponding to the supplier ID and the supplier ID stored in the receivable user storage unit 64. The receivable usage amount corresponding to the associated buyer ID is totaled for each supplier ID. The settlement processing unit 76 determines the amount obtained by subtracting the total amount of the accounts receivable from the total amount of the portal use amount as the sales amount of the supplier. Further, the settlement processing unit 76 determines at least the credit use amount corresponding to the buyer ID as the buyer's payment amount.

Note that, when determining the sales amount of the supplier, the settlement processing unit 76 sends a sales determination request (first settlement determination request) for determining the sales amount to the virtual card management unit 72 via the member store management company server 20. Send. When the payment amount of the buyer is determined, the settlement processing unit 76 sends a payment determination request (second settlement determination request) for determining the payment amount to the card issuing company server 30 via the virtual member store management unit 71. Send.
In addition, the settlement processing unit 76 performs the receivable reassignment processing by the receivable reassignment unit 75 for the user corresponding to the receivable user information stored in the receivable user storage unit 64. One of the processing for determining the sales amount of the supplier and the processing for determining the payment amount of the buyer is executed. Note that the settlement processing unit 76 performs both the process of fixing the sales amount of the supplier and the process of fixing the payment amount of the buyer when the reassignment process is not performed by the reassignment unit 75. May be executed. In addition, the settlement processing unit 76 determines the sales amount of the supplier and the payment amount of the buyer based on the result of the aggregation for each predetermined period (for example, every month). Note that the settlement processing unit 76 determines the payment amount of the buyer for each transaction, but when the pair of the supplier and the buyer is the same, the payment processing unit 76 determines the payment amount of the buyer based on the total amount of the transaction. It may be.

  When finalizing the sales amount of the supplier, the settlement processing unit 76 causes the member store management company server 20 to transmit a sales finalization request including an amount obtained by subtracting the total amount of accounts receivable from the total amount of portal usage. . When the payment amount of the buyer is determined, the settlement processing unit 76 causes the card issuing company server 30 to transmit a payment determination request including the credit usage amount via the virtual member store management unit 71.

  Further, when executing the settlement process, the settlement processing unit 76 performs a process of collecting or paying various fees based on the fee information stored in the fee storage unit 67. For example, the settlement processing unit 76 acquires the fee information corresponding to the buyer ID from the fee storage unit 67 after determining the buyer's payment amount, and reduces the buyer's payment amount based on the acquired fee information. Calculate the amount (the amount changed by the buyer's payment amount). After determining the sales amount of the supplier, the settlement processing unit 76 acquires the fee information corresponding to the supplier ID from the fee storage unit 67, and based on the acquired commission information, the amount reduced from the sales amount of the supplier. (The amount obtained by changing the sales amount of the supplier) is calculated.

The statement output processing section 77 responds to an output request for outputting a statement of use of a portal use transaction, based on the transaction information stored in the transaction information storage section 65, for each supplier (member store) or buyer (card). It generates information indicating a usage statement for each user and outputs information indicating the generated usage statement.
Specifically, when the above-described output request is received from the member store terminal 40, the statement output processing unit 77 transmits information indicating a use statement corresponding to the supplier (member store) using the member store terminal 40, Output to the member store terminal 40. The member store terminal 40 displays, on the display unit 42, information indicating the usage statement received from the settlement portal server 10.
In addition, when receiving the above-described output request from the card user terminal 50, the statement output processing unit 77 outputs information indicating a use statement corresponding to a buyer (card user) using the card user terminal 50. Is output to the card user terminal 50. The card user terminal 50 displays, on the display unit 52, information indicating the usage statement received from the settlement portal server 10.

Next, the operation of the settlement system 1 according to the present embodiment will be described with reference to the drawings.
The settlement portal server 10 of the settlement system 1 has the following functions.
(1) User registration processing (2) Portal use transaction settlement processing (3) Settlement processing (4) Usage statement output processing Hereinafter, each operation in the settlement portal server 10 will be described.

<User registration process>
(Member store registration process)
First, a registration process of a supplier (member store) according to the present embodiment will be described with reference to FIG.
FIG. 7 is a diagram illustrating an example of an operation of a member store registration process according to the present embodiment.
As shown in FIG. 7, when registering a member store in the inter-company payment service of the payment portal server 10, the member store terminal 40 connects to the payment portal server 10 and transmits a registration application (step S101). ). The supplier registration application includes, for example, the member store number and, for example, the user information of the supplier (first application information) received from the input unit 41 of the member store terminal 40.

  Next, the settlement portal server 10 acquires the member store contract information corresponding to the supplier from the member store management company server 20 in response to the registration application of the supplier (step S102). That is, the member store information acquisition unit 81 of the settlement portal server 10 acquires member store contract information from the member store management storage unit 21 of the member store management company server 20 described above in response to a supplier registration application. Here, the registration application of the supplier (member store) includes, for example, the member store number and the user information of the supplier applied by the member store. The affiliated store information acquiring unit 81 acquires affiliated store contract information corresponding to the affiliated store number included in the supplier registration application from the affiliated store management storage unit 21 of the affiliated store management company server 20. Here, the member store information acquisition unit 81 acquires, for example, member store contract information as shown in FIG.

  Next, the settlement portal server 10 compares and confirms the user information of the supplier (first application information) with the member store contract information (step S103). That is, the supplier registration unit 82 of the settlement portal server 10 determines the information of the predetermined items of the user information of the supplier (first application information (application content)) included in the application for registration of the supplier and the information of the acquired member store contract information. It is determined whether the information of the same item matches. The supplier registration unit 82 determines whether the supplier (member store) that has applied is a member store registered in the member store management company server 20 by determining whether or not they match. Here, it is assumed that the information of a predetermined item of the user information (first application information) of the supplier matches the information of the same item of the acquired member store contract information.

Next, the settlement portal server 10 issues supplier member information (supplier ID) (step S104). That is, the supplier registration unit 82 issues a supplier ID to the member store number included in the supplier registration application.
Next, the settlement portal server 10 registers the supplier information (Step S105). That is, the supplier registration unit 82 causes the supplier information storage unit 62 to store the supplier information as shown in FIG. Further, the supplier registration unit 82 generates login information corresponding to the issued supplier ID, for example, as shown in FIG. 2C, and stores the generated login information in the account storage unit 61.

Next, the settlement portal server 10 transmits the member ID (supplier ID, login ID) and the password to the member store terminal 40. That is, the supplier registration unit 82 transmits the issued (generated) supplier ID, login ID, and password to the member store terminal 40.
Thereby, the registration of the supplier (member store) is completed, and the supplier (member store) can use the inter-company settlement service. In the settlement system 1 according to the present embodiment, the validity of the application content is confirmed based on the member store contract information already registered in the member store management company server 20 (the information consistency is ensured). Thus, since the member store is registered in the service provided by the settlement system 1, it is possible to register a highly reliable member store in the inter-company settlement service.

(Card user registration process)
Next, a registration process of a buyer (card user) according to the present embodiment will be described with reference to FIG.
FIG. 8 is a diagram illustrating an example of an operation of a card user registration process according to the present embodiment.
As shown in FIG. 8, when registering a card user in the inter-company payment service of the payment portal server 10, the card user terminal 50 connects to the payment portal server 10 and transmits a registration application ( Step S111). The buyer registration application includes, for example, a card number and, for example, buyer user information (second application information) received from the input unit 51 of the card user terminal 50.

  Next, the settlement portal server 10 acquires card contract information corresponding to the buyer from the card issuing company server 30 in response to the buyer registration application (step S112). That is, the card information acquisition unit 83 of the settlement portal server 10 acquires the card contract information from the card management storage unit 31 of the card issuing company server 30 according to the buyer registration application. Here, the registration application for the buyer (card user) includes, for example, the card number and the user information of the buyer applied by the card user. The card information acquisition unit 83 acquires card contract information corresponding to the card number included in the buyer registration application from the card management storage unit 31 of the card issuing company server 30. Here, the card information acquisition unit 83 acquires, for example, card contract information as shown in FIG.

  Next, the settlement portal server 10 compares and confirms the buyer user information (second application information (application content)) with the card contract information (step S113). That is, the buyer registration unit 84 of the settlement portal server 10 determines the information of the predetermined item of the buyer user information (second application information) included in the buyer registration application and the information of the same item of the acquired card contract information. It is determined whether or not matches. The buyer registration unit 84 determines whether or not the applied buyer (card user) is a card user registered in the card issuing company server 30 by determining whether or not they match. Here, it is assumed that information of a predetermined item of the buyer user information (second application information) matches information of the same item of the acquired card contract information.

Next, the settlement portal server 10 issues buyer member information (buyer ID) (step S114). That is, the buyer registration unit 84 issues a buyer ID to the card number included in the buyer registration application.
Next, the settlement portal server 10 registers the buyer information (Step S115). That is, the buyer registration unit 84 causes the buyer information storage unit 63 to store the buyer information as shown in FIG. Further, the buyer registration unit 84 generates login information corresponding to the issued buyer ID, for example, as shown in FIG. 2C, and stores the generated login information in the account storage unit 61.

Next, the settlement portal server 10 transmits the member ID (the buyer ID and the login ID) and the password to the card user terminal 50. That is, the buyer registration unit 84 transmits the issued (generated) buyer ID, login ID, and password to the card user terminal 50.
Thereby, the registration of the buyer (card user) is completed, and the buyer (card user) can use the inter-company settlement service. In the settlement system 1 according to the present embodiment, based on the card contract information already registered in the card issuing company server 30, the validity of the application content is confirmed (after ensuring the consistency of the information), Since the card user is registered in the service provided by the settlement system 1, a highly reliable card user can be registered in the inter-company settlement service.

(Application process for accounts receivable)
Next, with reference to FIG. 9, an application process for the use of accounts receivable according to the present embodiment will be described.
FIG. 9 is a diagram illustrating an example of an operation of an application process for using the accounts receivable according to the present embodiment.

  In FIG. 9, it is assumed that the user registration of both the card user and the member store of the company (corporation) to which the card user belongs has already been performed. In such a state, the card user terminal 50 is connected to the settlement portal server 10 by the card user's login ID and password received from the input unit 51 of the card user terminal 50.

  The card user terminal 50 transmits a receivable use application to the settlement portal server 10 (step S201). Here, the receivable use application includes the buyer ID and the supplier ID received by the input unit 51 of the card user terminal 50.

  Next, the settlement portal server 10 transmits a card validity confirmation request to the member store management company server 20 (Step S202). That is, the receivable use registration unit 85 of the settlement portal server 10 acquires the card number corresponding to the buyer ID included in the receivable use application from the buyer information storage unit 63, and acquires the card number corresponding to the supplier ID included in the receivable use application. The number is obtained from the supplier information storage unit 62. The accounts receivable registration unit 85 transmits a validity confirmation request including the acquired card number to the member store management company server 20.

Next, the member store management company server 20 transmits the received card validity confirmation request to the card issuing company server 30 (step S203).
Next, the card issuing company server 30 checks the validity of the card (step S204). That is, the card issuing company server 30 confirms the validity of the card based on the card number included in the received validity confirmation request of the card.

Next, the card issuing company server 30 transmits the card validity confirmation result to the member store management company server 20 (step S205).
Next, the member store management company server 20 transmits the received card validity confirmation result to the settlement portal server 10 (step S206).
As a result, when the accounts receivable is used, the validity (validity) of the card has been confirmed. Here, it is assumed that the validity confirmation result is “OK”.

  Next, the settlement portal server 10 transmits a receivable use approval request to the member store terminal 40 (step S207). Here, when the member store terminal 40 is connected to the settlement portal server 10 by the member store login ID and password received from the input unit 41 of the member store terminal 40, the member store terminal 40 A message (information) indicating that the receivable use application has been made is displayed on the display unit 42.

  Next, the member store terminal 40 displays a display screen of the receivable use approval request on the display unit 42, and approves the use of the receivable (step S208). That is, the member store terminal 40 confirms the content to be displayed by the person in charge of the member store. For example, when the buyer ID is received from the input unit 41, the buyer confirmation information for approving the use of the receivable is displayed on the display unit. 42.

  Upon receiving the approval from the input unit 41, the member store terminal 40 transmits an approval result indicating that the approval has been made to the settlement portal server 10 (step S209).

  Next, the settlement portal server 10 registers the use of the accounts receivable based on the approval result (step S210). That is, as shown in FIG. 3C, the accounts receivable registration unit 85 of the settlement portal server 10 associates the supplier ID with the buyer ID and stores it in the accounts receivable user storage unit 64, so that the member store Associate numbers with card numbers.

Next, the settlement portal server 10 transmits a use registration completion notification (for example, information indicating that the receivable use registration has been completed) to the card user terminal 50 (step S211).
Further, the settlement portal server 10 transmits a use registration completion notification (for example, information indicating that the use of the receivable has been completed) to the member store terminal 40 (step S212).

  As described above, in the settlement system 1 according to the present embodiment, the supplier ID (or the member store number) and the buyer ID (or the card number) are associated (linked), and therefore, in the portal use transaction, Can be used. In addition, in the settlement system 1 according to the present embodiment, the use of the accounts receivable is registered after both the validity of the card and the approval of the validity of the buyer are registered. Store and card users) can use the accounts receivable in the transaction using the portal, so that highly reliable inter-company transactions can be realized.

<Payment processing for portal use transactions>
(Settlement process using accounts receivable)
Next, a settlement process using accounts receivable according to the present embodiment will be described with reference to FIG.
FIG. 10 is a diagram illustrating an example of an operation of a settlement process using accounts receivable according to the present embodiment.

First, when a supplier (member store) makes a request for a portal use transaction on the inter-company settlement service, the card user terminal 50 displays information indicating a request for payment for the portal use transaction on the display unit 52.
Upon receiving the payment execution from the input unit 51, the card user terminal 50 transmits a payment execution request to the settlement portal server 10 (Step S301). The payment execution request includes, for example, information indicating a bill number.

  Next, the settlement portal server 10 sends a credit confirmation request to the card issuing company server 30 with the portal usage amount (step S302). That is, the transaction determination unit 73 of the settlement portal server 10 acquires the transaction information corresponding to the bill number included in the payment execution request from the transaction information storage unit 65, and uses the acquired transaction information billing amount as the portal usage amount, A credit confirmation request is transmitted to the card issuing company server 30 via the virtual member store management unit 71. The credit confirmation request includes, for example, a card number, a portal usage amount, a transaction date and time, a card expiration date, a member store number, and the like. Here, the transaction determination unit 73 acquires information such as a card number and a member store number from the buyer information storage unit 63 or the supplier information storage unit 62.

  Next, the card issuing company server 30 executes a credit check on the received credit check request (step S303). If the card issuing company server 30 can confirm the validity of the card number included in the credit confirmation request (for example, at least compare the corresponding usage limit (credit limit) with the portal usage amount included in the credit confirmation request). Then, when the portal usage amount is equal to or less than the usage limit (credit frame), it is determined that the credit confirmation result is “OK”.

Next, the card issuing company server 30 transmits the credit confirmation result to the settlement portal server 10 (Step S304).
Next, the settlement portal server 10 determines whether or not the credit confirmation is “OK” (Step S305). That is, the transaction determination unit 73 determines whether or not the credit confirmation is “OK” based on the received credit confirmation result. If the credit confirmation is “OK” (step S305: YES), the transaction determination unit 73 advances the processing to step S313.
If the credit confirmation is not "OK" (the credit confirmation is "NG") (step S305: NO), the transaction determination unit 73 transmits the credit result (NG) to the card user terminal 50 (step S306). .

  Next, the card user terminal 50 displays the received credit result (NG) on the display unit 52. When accepting the payment execution using the receivable from the input unit 51, the card user terminal 50 transmits a use request for the account receivable amount to the settlement portal server 10 (step S307).

Next, the transaction determination unit 73 of the settlement portal server 10 determines whether or not the receivable amount is equal to or more than the portal use amount (receivable amount ≧ portal use amount) (step S308). If the transaction determination unit 73 is equal to or more than the portal usage amount (receivable amount ≧ portal usage amount) (step S308: YES), the process proceeds to step S313.
In addition, when the account receivable amount is less than the portal use amount (account receivable amount <portal use amount) (step S308: NO), the transaction determination unit 73 calculates (portal use amount-receivable amount). The credit confirmation request is transmitted to the card issuing company server 30 via the virtual member store management unit 71 (step S309).
Next, the card issuing company server 30 executes a credit check on the received credit check request (step S310).
Next, the card issuing company server 30 transmits the credit confirmation result to the settlement portal server 10 (Step S311).

  Next, the transaction determination unit 73 of the settlement portal server 10 determines whether or not the credit confirmation is “OK” based on the received credit confirmation result (Step S312). If the credit confirmation is “OK” (step S312: YES), transaction determination unit 73 advances the process to step S313. If the credit confirmation is not “OK” (the credit confirmation is “NG”) (step S312: NO), the transaction determination unit 73 advances the process to step S314.

In step S313, the settlement portal server 10 executes a settlement process. That is, the settlement processing unit 74 of the settlement portal server 10 executes settlement of the portal use transaction, and adds transaction information such as the record R1 in FIG. 4 to the transaction information storage unit 65, for example.
Next, in step S314, the settlement portal server 10 transmits the payment result to the card user terminal 50. If the credit confirmation is “NG” in step S312, the settlement portal server 10 transmits to the card user terminal 50 information indicating that the settlement of the portal use transaction has not been completed as a payment result.

  Further, the settlement portal server 10 transmits the payment result to the member store terminal 40 (Step S315). If the credit check is “NG” in step S312, the settlement portal server 10 transmits to the member store terminal 40 information indicating that the settlement of the portal use transaction has failed as a payment result.

(Payment cancellation processing)
Next, a payment cancellation process according to the present embodiment will be described with reference to FIG.
FIG. 11 is a diagram showing an example of a payment cancellation operation according to the present embodiment.
In this figure, first, the member store terminal 40 transmits a payment cancellation application to the settlement portal server 10 (step S401). The payment cancellation application includes, for example, information indicating a bill number.

  Next, the settlement portal server 10 transmits a payment cancellation approval request to the card user terminal 50 (Step S402). Here, when the card user terminal 50 is connected to the settlement portal server 10 by the card user's login ID and password received from the input unit 51 of the card user terminal 50, the card user terminal 50 The display unit 52 displays that the payment cancellation application has been made to the card user.

Next, the card user terminal 50 approves the payment cancellation (step S403). That is, the card user terminal 50 confirms the content displayed by the card user, and displays, for example, the billing information for approving the cancellation of the payment on the display unit 52 when the bill number is received from the input unit 51. I do.
Then, when accepting the approval from the input unit 51, the card user terminal 50 transmits an approval result indicating that the approval has been made to the settlement portal server 10 (step S404).

  Next, the settlement portal server 10 transmits a credit cancellation request to the card issuing company server 30 based on the approval result (step S405). That is, the settlement processing unit 74 of the settlement portal server 10 acquires the transaction information corresponding to the bill number included in the payment cancellation application from the transaction information storage unit 65, and uses the credit usage amount of the acquired transaction information to cancel the credit cancellation. The request is transmitted to the card issuing company server 30 via the virtual member store management unit 71. The credit cancellation confirmation request includes, for example, a card number, a credit use amount, a transaction date and time, a card expiration date, a member store number, an approval code added by the card issuing company server 30 at the time of credit confirmation, and the like. Here, the settlement processing unit 74 acquires information such as a card number and a member store number from the buyer information storage unit 63 or the supplier information storage unit 62.

Next, the card issuing company server 30 performs a credit cancellation process on the received credit cancellation request (step S406). The card issuing company server 30 executes a process of returning the usage limit (credit limit) in response to the credit cancellation request.
Next, the card issuing company server 30 transmits the credit cancellation result to the settlement portal server 10 (step S407). That is, the card issuing company server 30 transmits the credit cancellation result to the settlement portal server 10 via the virtual member store management unit 71.

Next, the settlement portal server 10 registers a cancellation process (step S408). That is, the settlement processing unit 74 of the settlement portal server 10 adds transaction information corresponding to the portal use transaction whose settlement has been canceled to the transaction information storage unit 65. Here, the portal use transaction whose settlement has been canceled includes at least a receivable use transaction or a credit use transaction.
Next, the settlement portal server 10 transmits the payment cancellation result to the member store terminal 40 (Step S409). Further, the settlement portal server 10 transmits the payment cancellation result to the card user terminal 50 (Step S410).
As described above, the settlement portal server 10 according to the present embodiment can cancel the transaction using the portal, and can recover the usage limit after the cancellation of the transaction.
Note that, in this figure, an example of transmitting a payment cancellation request from a supplier is described, but the request may be transmitted from a buyer.

(Receivable reassignment processing)
Next, with reference to FIG. 12, a description will be given of the loan reassignment processing in the present embodiment.
FIG. 12 is a flowchart showing an example of the operation of the loan reassignment in the present embodiment.
It is assumed that the bond changing unit 75 of the settlement portal server 10 executes the bond changing process illustrated in FIG. 12 periodically (for example, every day).
In this figure, the reassignment unit 75 first calculates the amount of accounts receivable corresponding to the target supplier ID (step S501). Here, similarly to the above-described transaction determination unit 73, the reassignment unit 75 calculates the amount of accounts receivable based on the transaction information stored in the transaction information storage unit 65.

Next, the loan reassigning unit 75 acquires a buyer ID corresponding to the supplier ID from the accounts receivable user storage unit 64 (step S502).
Next, the loan reassigning unit 75 extracts the portal use transaction of the acquired buyer ID (step S503). That is, the loan reassigning unit 75 extracts the transaction information of the buyer ID from the transaction information stored in the transaction information storage unit 65.

  Next, the loan reassigning unit 75 determines whether or not a credit use transaction exists in the transaction information of the acquired buyer ID (step S504). If there is a credit use transaction in the transaction information of the acquired buyer ID (step S504: YES), the credit transfer unit 75 advances the process to step S505. In addition, when there is no credit use transaction in the transaction information of the acquired buyer ID (step S504: NO), the reassignment unit 75 ends the process.

  In step S505, the loan reassignment unit 75 acquires the extracted credit use amount of the credit use transaction. That is, the credit change unit 75 acquires the credit use amount of the extracted one piece of transaction information. The reassignment unit 75 acquires, for example, the credit use amount of the transaction information having the lowest credit use amount.

  Next, the receivable reassigning unit 75 determines whether or not the receivable holding amount is equal to or more than the acquired credit use amount (receivable holding amount ≧ credit use amount) (step S506). That is, the loan reassigning unit 75 determines whether or not the amount of accounts receivable is equal to or more than the amount of credit used in one piece of transaction information. When the amount of accounts receivable is equal to or more than the amount of credit use (step S506: YES), the reassignment unit 75 advances the process to step S507. In addition, when the amount of accounts receivable is less than the amount of credit use (step S506: NO), the reassignment unit 75 ends the process.

  In step S507, the receivable reassigning unit 75 executes credit reassignment processing (receivable reassignment processing). Specifically, the credit reassignment unit 75 transmits the above-described credit cancellation request to the card issuing company server 30 via the virtual member store management unit 71, and converts the canceled credit use amount into an account receivable amount. Replace. The reassignment unit 75 adds the record in which the transaction information is updated to the transaction information storage unit 65.

  Next, the loan reassigning unit 75 updates the amount of accounts receivable (step S508), and determines whether or not the amount of accounts receivable is present (step S509). When there is an account receivable amount (step S509: YES), the reassignment unit 75 returns the process to step S503, and extracts the next portal use transaction. When there is no account receivable amount (step S509: NO), the loan reassigning unit 75 ends the process. Note that the receivable reassigning unit 75 updates the receivable holding amount by, for example, subtracting the canceled credit use amount from the receivable holding amount.

Next, with reference to FIG. 13, a specific example of the settlement of the portal use transaction using the accounts receivable in the settlement system 1 according to the present embodiment will be described.
FIG. 13 is a diagram illustrating an example of the operation of the payment process according to the present embodiment.
In this figure, the use limit (credit limit) of the credit use transaction of each of the companies A, B, C, and D is “1 million yen”, and the amount of accounts receivable at the start of each company is “ The description will be made assuming that it is "0 yen". In this figure, the control unit 70 will be described as a processing unit (mainly a transaction determination unit 73 and a settlement processing unit 74) excluding the virtual member store management unit 71 and the virtual card management unit 72.

  The portal use transaction KS1 shows an example in which Company A purchases 1 million yen from Company B. In the portal use transaction KS1, the member store terminal 40-1 of the company B bills the control unit 70 of the settlement portal server 10 for 1 million yen, and the card user terminal 50-1 of the company A responds. Transmits a payment execution request of 1,000,000 yen to the control unit 70 of the settlement portal server 10. In this case, the transaction determination unit 73 of the control unit 70 confirms the credit of 1 million yen to the card issuing company server 30-1 of the company A via the virtual member store management unit 71, and the settlement processing unit of the control unit 70 74 records a credit use amount of 1 million yen to Company A.

  Here, a receivable holding amount of 1 million yen is generated at Company B. In the present embodiment, since the card issuing company server 30 and the member store management company server 20 are separated by the virtual member store management unit 71 and the virtual card management unit 72, the settlement portal server 10 (the control unit 70 ) Does not transmit a credit confirmation request to the member store management company server 20-1 of Company B. Then, the settlement portal server 10 (the control unit 70) indicates that the settlement of the portal use transaction has been completed to both the card user terminal 50-1 of the company A and the member store terminal 40-1 of the company B. Notify completion of payment.

  Next, the portal use transaction KS2 shows an example in which Company B has purchased 1.3 million yen from Company C. In the portal use transaction KS2, the member store terminal 40-2 of the company C bills the control unit 70 of the settlement portal server 10 for 1.3 million yen, and the card user terminal 50-2 of the company B responds. Transmits a payment execution request of 1.3 million yen to the control unit 70 of the settlement portal server 10. In this case, the control unit 70 (the transaction determination unit 73) first confirms the credit of 1.3 million yen to the card issuing company server 30-2 of the company B via the virtual member store management unit 71, but the usage limit is Is 1,000,000 yen, the credit confirmation result “NG” is received via the virtual member store management unit 71.

Accordingly, the settlement portal server 10 uses the receivable amount of 1,000,000 yen and performs the credit check of 300,000 yen again through the virtual member store management unit 71. In this case, since 300,000 yen is equal to or less than the usage limit, the card issuing company server 30-2 transmits the credit confirmation result “OK”, and the control unit 70 of the settlement portal server 10 sets the virtual member store management unit 71 The credit result is received via the company, and the credit use amount of 300,000 yen is recorded in Company B, and the receivable use amount of -1 million yen is generated, and the receivable holding amount of Company B becomes 0 yen. . In addition, the company C has a 1.3 million yen receivable holding amount. In this case, the settlement processing unit 74 of the settlement portal server 10 adds the transaction information of the record R1 in FIG.
Further, the settlement portal server 10 (control unit 70) does not transmit the credit confirmation request to the member store management company server 20-2 of the company C, similarly to the portal use transaction KS1. Then, the settlement portal server 10 (control unit 70) indicates that the settlement of the portal use transaction has been completed to both the card user terminal 50-2 of Company B and the member store terminal 40-2 of Company C. Notify completion of payment.

  Next, the portal use transaction KS3 shows an example of a case where Company D has purchased 500,000 yen from Company B. In the portal use transaction KS3, the member store terminal 40-1 of the company B requests the control unit 70 of the settlement portal server 10 for 500,000 yen, and the card user terminal 50-3 of the company D Transmits a payment execution request of 500,000 yen to the control unit 70 of the settlement portal server 10. In this case, the transaction determination unit 73 of the control unit 70 checks the credit of 500,000 yen to the card issuing company server 30-3 of the company D via the virtual member store management unit 71. Further, the transaction determination unit 73 of the control unit 70 receives the credit result via the virtual member store management unit 71, and the settlement processing unit 74 of the control unit 70 records the credit use amount of 500,000 yen to Company D. .

  Company B has a 500,000 yen receivable holding amount. Further, the settlement portal server 10 (control unit 70) does not transmit the credit confirmation request to the member store management company server 20-1 of the company B, similarly to the portal use transaction KS1. Then, the settlement portal server 10 (control unit 70) indicates that the settlement of the portal use transaction has been completed to both the card user terminal 50-3 of the company D and the member store terminal 40-1 of the company B. Notify completion of payment.

Next, the receivable repurchase process KS4 is a process of replacing the credit use amount of Company B of 300,000 yen with the receivable holding amount of 500,000 yen. In the receivable reassignment process KS4, the receivable reassignment unit 75 of the settlement portal server 10 cancels the credit of 300,000 yen to the card issuer server 30-2 of the company B via the virtual member store management unit 71, and uses the credit. Restore the limit by 300,000 yen. The receivable reassigning unit 75 reduces the amount of accounts receivable from 500,000 yen to 300,000 yen, and the ultimate amount of receivable is 200,000 yen.
As described above, the settlement system 1 for the transaction using the portal according to the present embodiment enables the real-time use of the amount of accounts receivable (accounts receivable) and recovers the limit of use (credit limit) by reassignment processing. can do.

<Payment processing>
Next, the settlement process according to the present embodiment will be described with reference to FIGS.
FIG. 14 is a flowchart illustrating an example of a process of determining the sales amount of the supplier according to the present embodiment.
In this figure, the settlement processing unit 76 first calculates the total amount of the portal usage amount corresponding to the target supplier ID (step S601). The settlement processing unit 76 extracts the transaction information corresponding to the target supplier ID from the transaction information stored in the transaction information storage unit 65, and calculates the total amount of the portal usage amount included in the transaction information.

  Next, the settlement processing unit 76 determines whether there is a buyer ID associated with the target supplier ID (Step S602). That is, the settlement processing unit 76 determines whether or not there is a buyer ID associated with the supplier ID from the receivable user storage unit 64. If there is a buyer ID associated with the supplier ID (step S602: YES), the settlement processing unit 76 advances the process to step S603. If there is no buyer ID associated with the supplier ID (step S602: NO), the settlement processing unit 76 advances the process to step S606.

  In step S603, the settlement processing unit 76 calculates the total amount of accounts receivable used corresponding to the associated buyer ID. That is, the settlement processing unit 76 extracts the receivable amount corresponding to the target buyer ID from the transaction information stored in the transaction information storage unit 65, and calculates the total amount of the receivable amount included in the transaction information. Is calculated.

Next, the settlement processing unit 76 calculates the sales amount of the supplier corresponding to the target supplier ID by subtracting the total amount of the accounts receivable from the total amount of the portal use amounts (step S604).
Next, the settlement processing unit 76 executes a process for determining the sales amount of the supplier (step S605). The settlement processing unit 76 transmits, for example, a confirmation request (first settlement confirmation request) for fixing the sales amount of the member store to the member store management company server 20. That is, the settlement processing unit 76 performs a credit check with respect to the member store management company server 20, and then sends a confirmation request (first settlement confirmation request) for fixing the sales amount of the member store to the member store management company server 20. Send. The confirmation request for fixing the sales amount of the supplier includes, for example, a member store number, a card number, a sales date, a total sales amount, and an approval number.

In step S606, the settlement processing unit 76 advances the process to step S605, using the total amount of the portal usage amounts as the sales amount of the supplier.
Note that the processing from step S601 to step S606 described above is performed periodically (for example, on a closing day) for each supplier ID stored in the supplier information storage unit 62.

FIG. 15 is a flowchart illustrating an example of a process for determining a buyer's payment amount in the present embodiment.
In the figure, the settlement processing unit 76 first calculates the total amount of credit use corresponding to the target buyer ID (step S611). The settlement processing unit 76 extracts the transaction information corresponding to the target buyer ID from the transaction information stored in the transaction information storage unit 65, and calculates the total amount of credit use included in the transaction information.

Next, the settlement processing unit 76 sets the total amount of the credit use amount as the buyer's payment amount (step S612).
Next, the settlement processing unit 76 executes a process of determining the payment amount of the buyer (step S613). The settlement processing unit 76 transmits, for example, a settlement request (second settlement settlement request) for fixing the amount paid by the buyer to the card issuing company server 30 via the virtual member store management unit 71. The confirmation request for fixing the payment amount of the buyer includes, for example, the member store number, the card number, the sales date, the total sales amount, and the approval number.

  Note that the processing from step S611 to step S613 described above is executed periodically (for example, on a closing day) for each buyer ID stored in the buyer information storage unit 63.

Next, a specific example of the settlement process in the settlement system 1 according to the present embodiment will be described with reference to FIG.
FIG. 16 is a diagram illustrating an example of the operation of the settlement process according to the present embodiment.
In FIG. 16, the settlement process for the settlement of the portal use transaction described in FIG. 13 will be described.

  The settlement process SS1 shows a settlement process when Company A purchases 1 million yen from Company B in the portal use transaction KS1 shown in FIG. In the settlement process SS1, the settlement processing unit 76 of the settlement portal server 10 determines the sales of 1 million yen to the card issuing company server 30-1 of the company A via the virtual member store management unit 71. The card issuing company server 30-1 collects 1 million yen from the company A (card user terminal 50-1), and deposits the amount obtained by subtracting the commission amount into the virtual member store management unit 71. Then, the virtual member store management unit 71 deposits the amount obtained by further subtracting the commission amount into the settlement portal server 10. In this figure, the depositing process is represented by a broken line, and indicates a process for depositing a bank account corresponding to each configuration.

  Next, the settlement process SS2 shows a settlement process when Company B purchases 1.3 million yen from Company C in the portal use transaction KS2 shown in FIG. In the settlement process SS2, the settlement processing unit 76 of the settlement portal server 10 checks the credit of 1.3 million yen and confirms the sales to the virtual card management unit 72 via the member store management company server 20-2 of the company C. Execute. Then, the virtual card management unit 72 collects 1.3 million yen from the settlement processing unit 76 of the settlement portal server 10, and deposits the amount obtained by subtracting the commission amount into the member store management company server 20-2 of the company C. Then, the member store management company server 20-2 deposits the amount obtained by further subtracting the fee into the member store of the company C (member store terminal 40-2). Note that, in this case, the settlement processing unit 76 of the settlement portal server 10 does not transmit the sales confirmation (payment confirmation) to the card issuing company server 30-2 of the company B via the virtual member store management unit 71.

Next, the settlement process SS3 shows the settlement process when Company D purchases 500,000 yen from Company B in the portal use transaction KS3 shown in FIG. In the settlement process SS3, the settlement processing unit 76 of the settlement portal server 10 performs the credit check and the sales confirmation of 200,000 yen to the virtual card management unit 72 via the member store management company server 20-1 of the company B. Execute. Then, the virtual card management unit 72 collects 200,000 yen from the settlement processing unit 76 of the settlement portal server 10, and deposits the amount after deducting the commission into the member store management company server 20-1 of Company B. Then, the member store management company server 20-1 deposits the amount obtained by further deducting the commission into the member store of the company B (member store terminal 40-1).
Further, the settlement processing unit 76 of the settlement portal server 10 determines the sales of 500,000 yen to the card issuing company server 30-3 of the company D via the virtual member store management unit 71. The card issuing company server 30-3 collects 500,000 yen from the company D (card user terminal 50-3), and deposits the amount obtained by subtracting the commission amount into the virtual member store management unit 71. Then, the virtual member store management unit 71 deposits the amount obtained by further subtracting the commission amount into the settlement processing unit 76 of the settlement portal server 10.

In the example described above, Company B conducts both portal transactions for sales and purchase. However, by using accounts receivable, final settlement will result in a sales of 200,000 yen. become. (However, the deposit amount is the amount after deducting the commission). That is, the company B uses only the receivable, and as a result of the settlement process, receives only the payment.
As described above, in the settlement system 1 according to the present embodiment, the member store and the card user who have applied for the use of accounts receivable can be treated as the same company, and payment or debit can be unified.

<Output processing of usage details>
Next, a process of outputting a usage statement according to the present embodiment will be described.
Here, an example of a usage statement displayed on the card user terminal 50 according to the present embodiment will be described.
The statement output processing unit 77 of the settlement portal server 10 responds to the output request for requesting the output of the statement of use of the portal use transaction from the card user terminal 50, the sales information stored in the sales information storage unit 66, and Based on the transaction information stored in the transaction information storage unit 65, information indicating a usage statement corresponding to the buyer ID is generated. The statement output processing unit 77 outputs (transmits) the generated information indicating the use statement to the card user terminal 50. The card user terminal 50 displays, for example, a use date, a business partner, a portal use amount, a receivable use amount, a credit use amount, and the like on the display unit 52.

Next, an example of a usage statement displayed on the member store terminal 40 according to the present embodiment will be described.
The statement output processing unit 77 of the settlement portal server 10 responds to the output request from the member store terminal 40 to request the use statement of the portal use transaction to be output, and the sales information stored in the sales information storage unit 66 and the transaction. Based on the transaction information stored in the information storage unit 65, information indicating a usage statement corresponding to the supplier ID is generated. The statement output processing unit 77 outputs (transmits) information indicating the generated use statement to the member store terminal 40. Thereby, the member store terminal 40 displays, for example, the use date, the business partner, the portal use amount, the accounts receivable amount, and the like on the display unit 42.
Note that the detail output processing unit 77 may, for example, cause the buyer to display its own usage, and the supplier to display its own usage and the usage of the buyer associated with itself. .

  As described above, the settlement portal server 10 according to the present embodiment includes the member store information acquisition unit 81 (first acquisition unit), the supplier registration unit 82 (first registration unit), and the card information acquisition unit 83 (second acquisition unit). Acquisition unit) and a buyer registration unit 84 (second registration unit). The affiliated store information acquisition unit 81 includes affiliated store identification information (for example, an affiliated store number) for identifying an affiliated store of a credit card (settlement card) used for a transaction, and user information of the supplier (first number) applied by the affiliated store. In response to a supplier registration application (first use application) including the (1 application information), member store contract information corresponding to the member store number included in the supplier registration application is acquired. The member store contract information is information registered in advance by a member store management company that manages the member stores. The supplier registration unit 82 responds to the application for registration of the supplier based on the user information of the supplier included in the application for registration of the supplier and the member store contract information acquired by the member store information acquisition unit 81. A supplier ID (first member information) is issued for the member store number included in the registration application. The supplier registration unit 82 causes the supplier information storage unit 62 (first user storage unit) to store at least supplier information that associates the member store number with the supplier ID. The card information acquisition unit 83 applies for a buyer registration application including card identification information (for example, a card number) for identifying a credit card and buyer user information (second application information) applied by the card user of the credit card. In accordance with the (second use application), card contract information corresponding to the card number included in the buyer registration application is acquired. The card contract information is information registered in advance with a card issuing company that issues a credit card. In response to the buyer registration application, the buyer registration unit 84 applies the buyer registration application based on the buyer user information included in the buyer registration application and the card contract information acquired by the card information acquisition unit 83. A buyer ID (second member information) is issued for the card number included in the buyer information, and at least buyer information (second user information) that associates the card number with the buyer ID is stored in the buyer information storage unit 63 (second usage). In the user storage unit).

  Thereby, the settlement portal server 10 according to the present embodiment confirms the validity of the application content based on the member store contract information registered in advance in the member store management company that manages the member store, and then checks the member store. Since registration is performed, a member store with high reliability can be registered as a user. In addition, the settlement portal server 10 according to the present embodiment registers the card user after confirming the validity of the application content based on the card contract information registered in advance with the card issuing company that issues the credit card. Therefore, a card user with high reliability can be registered as a user. As described above, in the settlement portal server 10 according to the present embodiment, highly reliable member stores and card users can be registered as users, so that highly reliable card transactions can be performed. As a result, the settlement portal server 10 according to the present embodiment can realize a card transaction service using receivables (receivables and receivables) for card transactions between companies by, for example, associating member stores with card users. The use of inter-card payment transactions can be increased.

Further, in the present embodiment, the supplier registration unit 82 compares the user information of the supplier included in the supplier registration application with the member store contract information acquired by the member store information acquisition unit 81, and based on the comparison result. Issue a supplier ID. Further, the buyer registration unit 84 compares the buyer user information included in the buyer registration application with the card contract information acquired by the card information acquisition unit 83, and issues a buyer ID based on the comparison result. .
As a result, the settlement portal server 10 according to the present embodiment can register more reliable users (member stores and card users).

In addition, the settlement portal server 10 according to the present embodiment stores the member store number (member store identification information) stored in the supplier information storage unit 62 and the buyer information storage unit 63 in response to a use application for applying for use of accounts receivable. And a receivable use registration unit 85 for associating with a card number (card identification information).
Thereby, the settlement portal server 10 according to the present embodiment can link (associate) the member store using the accounts receivable with the card user, and can handle both as one company. Therefore, the settlement portal server 10 according to the present embodiment can provide, for example, a card transaction service that uses accounts receivable for card transactions between companies.

In the present embodiment, the receivable use registration unit 85 transmits a validity check request for checking the validity of the credit card corresponding to the card number in response to the receivable use application, and receives the validity check request. The member number is associated with the card number according to the confirmation result.
As a result, the settlement portal server 10 according to the present embodiment can permit the use of the accounts receivable to a highly reliable card user whose validity of the credit card is confirmed.

Further, in the present embodiment, the receivables use registration unit 85 approves the receivables use application to the member store corresponding to the member store number in response to the use application, and, in accordance with the approval result, sets the member store number and , Associate with card number. The receivable use registration unit 85 transmits information for requesting the approval to the member store terminal 40 corresponding to the member store number when approving the receivable use application.
Thereby, the settlement portal server 10 according to the present embodiment can permit the use of the accounts receivable to the card user with high reliability whose application for the account receivable has been approved.

Further, in the present embodiment, the receivable use registration unit 85 associates the supplier ID stored in the supplier information storage unit 62 with the buyer ID stored in the buyer information storage unit 63 in response to the receivable use application. The member store number and the card number are associated with each other by being stored in the store unit 64.
Thereby, the settlement portal server 10 can reliably associate the member store number with the card number by a simple method.

Further, in the present embodiment, the receivable use application includes the buyer ID and the supplier ID corresponding to the user acquired from the user terminal (for example, the card user terminal 50).
Thereby, the settlement portal server 10 according to the present embodiment can easily associate the card number and the member store number based on, for example, the buyer ID and the supplier ID.

The settlement system 1 according to the present embodiment includes the settlement portal server 10 described above, a member store management company server 20, and a card issuing company server 30. Then, the settlement portal server 10 executes a card settlement process for performing settlement of a card transaction using a credit card based on the supplier information (first user information) and the buyer information (second user information). .
Thereby, the settlement system 1 has the same effect as the settlement portal server 10 described above.

Further, the user registration method according to the present embodiment includes a first acquisition step, a first registration step, a second acquisition step, and a second registration step. In the first acquisition step, the affiliated store information acquiring unit 81 determines the affiliated store identification information (for example, the affiliated store number) for identifying the affiliated store of the credit card (settlement card) used for the transaction and the supplier applied by the affiliated store. In response to a supplier registration application (first usage application) that includes the user information (first application information), member store contract information corresponding to the member store number included in the supplier registration application is acquired. Further, in the first registration step, the supplier registration unit 82, in response to the application for registration of the supplier, obtains the user information of the supplier included in the application for registration of the supplier and the member store contract information acquired in the first acquisition step. , A supplier ID (first member information) is issued for the member store number included in the registration application of the supplier, and at least supplier information in which the member store number is associated with the supplier ID is stored in the supplier information storage unit. 62 (first user storage unit). In the second acquisition step, the card information acquisition unit 83 sets the card identification information (for example, card number) for identifying the credit card and the user information of the buyer applied for by the card user of the credit card (second application information) In response to a buyer registration application (second usage application), the card contract information corresponding to the card number included in the buyer registration application is acquired. In the second registration step, the buyer registration unit 84, based on the buyer registration application, based on the buyer user information included in the buyer registration application and the card contract information acquired in the second acquisition step. Then, a buyer ID (second member information) is issued for the card number included in the registration application of the buyer, and at least buyer information (second user information) that associates the card number with the buyer ID is included in the buyer information. It is stored in the storage unit 63 (second user storage unit).
Thereby, the user registration method according to the present embodiment has the same effect as that of the settlement portal server 10 described above.

Further, according to the present embodiment, the settlement portal server 10 includes the transaction determination unit 73 and the settlement processing unit 74. The transaction determination unit 73 is a merchant identification information (a member store number) that is a credit amount (amount held by a credit) and a credit card use limit amount by a card transaction using a credit card, and at least a credit card member store. , Supplier ID) and card identification information (card number, buyer ID) for identifying a credit card can be settled for a card transaction based on the receivable amount and the usage limit corresponding to the receivable user information. Is determined. The settlement processing unit 74 executes the settlement of the card transaction when the transaction determination unit 73 determines that the settlement of the card transaction can be executed.
As a result, the settlement portal server 10 according to the present embodiment can settle a card transaction using accounts receivable. In the conventional settlement system, even a card transaction which was impossible due to the usage limit can be made by using the accounts receivable. Therefore, the settlement portal server 10 according to the present embodiment uses the card settlement transaction between companies. Can be increased. In addition, the settlement portal server 10 according to the present embodiment can use the accounts receivable for transactions directly related to business between companies, such as purchasing, and thus can improve the cash flow of the company.

Further, in the present embodiment, the transaction determination unit 73 stores identification information (card number, buyer ID) indicating a buyer who purchases a product in a card transaction in a receivable user storage unit 64 that stores receivable user information. If the receivable user information including the receivable user information is stored, it is determined whether or not the settlement of the card transaction can be executed based on the receivable amount and the use limit amount corresponding to the user information. When the user information including the identification information (card number, buyer ID) indicating the buyer is not stored in the receivable user storage unit 64, the transaction determination unit 73 uses the usage limit amount corresponding to the buyer. Then, it is determined whether the settlement of the card transaction can be executed.
Thereby, the settlement portal server 10 according to the present embodiment can coexist the settlement processing of the card transaction using the receivable with the settlement processing of the conventional card transaction without using the receivable.

In the present embodiment, the transaction determination unit 73 determines that the settlement of the card transaction can be executed when the amount obtained by subtracting the amount of the receivable from the transaction amount of the card transaction is equal to or less than the usage limit. When the transaction determination unit 73 determines that the settlement of the card transaction is executable, the settlement processing unit 74 preferentially uses the receivable amount for the settlement of the card transaction.
As a result, the settlement portal server 10 according to the present embodiment preferentially uses the accounts receivable, so that when the card transaction is completed only with the accounts receivable, there is no need to confirm the credit with the card issuing company. Further, the settlement portal server 10 according to the present embodiment preferentially uses the accounts receivable, so that it is possible to reduce the possibility that the credit card usage limit (credit limit) is reduced. Therefore, the settlement portal server 10 according to the present embodiment can reduce the influence on card transactions that do not use the settlement portal server 10. That is, in the settlement portal server 10 according to the present embodiment, in the card transaction in the settlement portal server 10, there is a high possibility that the credit limit is not reduced, so that the card transaction in other than the settlement portal server 10 becomes easy.

Further, in the present embodiment, when executing the settlement of the card transaction, the settlement processing unit 74 sets the merchant identification information, the card identification information, the transaction amount of the card transaction, the transaction amount of the credit, the credit amount and the credit amount. Is stored in the transaction information storage unit 65. Here, the member store identification information is a supplier ID indicating a supplier who sells the product, a member store number, and the like. The card identification information is a card number indicating a buyer who purchases a product, a buyer ID, and the like. Further, the accounts receivable amount is the amount used from the accounts receivable amount (account amount) of the transaction amount. The credit use amount (card settlement amount) is a settlement amount using credit of a credit card. Then, the transaction determination unit 73 calculates the amount of accounts receivable that can be used for the settlement of the card transaction based on the transaction information stored in the transaction information storage unit 65, It is determined whether or not the settlement of the card transaction can be executed based on the above.
As a result, the settlement portal server 10 according to the present embodiment calculates the account receivable amount each time the card transaction is settled, so that it is possible to execute the card transaction settlement based on the latest account receivable amount. It is not necessary to provide a storage unit for storing the amount of accounts receivable while being able to judge whether or not this is the case.

Further, in the present embodiment, when the credit usage amount, which is the payment amount using credit of the credit card for the settlement of the card transaction, is used, the used credit amount is reduced by the used credit usage amount. In addition, the settlement portal server 10 further includes a receivable reassigning unit 75 for exchanging at least a part of the accounts receivable holding amount to a usage limit. In addition, for example, when the account receivable amount corresponding to the user information is equal to or greater than the credit use amount corresponding to the user information, the receivable reassigning unit 75 calculates the credit use amount of the account receivable amount. , Change to the credit limit.
As a result, the settlement portal server 10 according to the present embodiment can replace the amount of accounts receivable with the usage limit, thereby recovering the usage limit (credit limit).

Further, in the present embodiment, the settlement portal server 10 according to the present embodiment includes the settlement processing unit 76 that setstle the transaction amount of the portal use transaction for each supplier (member store) or each buyer (card user). ing.
Thus, the settlement portal server 10 according to the present embodiment can settle the transaction amount of the portal use transaction for each supplier (member store) or each buyer (card user).

Further, the payment processing method according to the present embodiment includes a transaction determination step and a payment processing step. In the transaction determination step, the transaction determination unit 73 determines, based on the credit card transaction amount using the credit card and the credit card usage limit, at least member store identification information (member store identification) for identifying the credit card member store. No., Supplier ID) and credit card transaction information are executed based on the credit amount and credit limit corresponding to the user information in which the card identification information (card number, buyer ID) for identifying the credit card is associated. It is determined whether or not it is possible. In the settlement processing step, the settlement processing unit 74 executes the settlement of the card transaction when it is determined in the transaction determination step that the settlement of the card transaction can be executed.
Thereby, the settlement processing method according to the present embodiment has the same effect as the settlement portal server 10 described above.

  According to the present embodiment, the settlement portal server 10 includes the virtual member store management unit 71 acting as the member store management company server 20 for managing the member stores of the credit card, and the settlement processing unit 74. In response to the settlement request for requesting the settlement of the card transaction using the credit card, the virtual member store management unit 71 changes the credit use amount (card settlement amount), which is the settlement amount using the credit of the credit card, to the credit card. Issue a card for managing a credit card instead of the member store management company server 20 (without passing through the member store management company server 20) instead of the member store management company server 20 It transmits to the company server 30 and receives the confirmation result for the first credit confirmation request. The settlement processing unit 74 executes the settlement of the card transaction according to the confirmation result received by the virtual member store management unit 71, and causes the transaction information storage unit 65 to store the transaction information of the executed card transaction.

  Thereby, the settlement portal server 10 according to the present embodiment divides the member store management company server 20 and the card issuing company server 30, so that, for example, a plurality of card transactions are collectively (integrated) and collectively. It will be possible to settle. The settlement portal server 10 according to the present embodiment collectively (integrates) and collectively settles a plurality of card transactions, so that, for example, a card transaction using accounts receivable, or a transaction amount is offset between two companies. Convenience can be improved in the settlement of card transactions, for example, a volume discount can be obtained by combining a plurality of transactions. Therefore, the settlement portal server 10 according to the present embodiment can increase the use of credit card settlement transactions between companies.

The settlement portal server 10 according to the present embodiment includes a settlement processing unit 76 (integration processing unit) that integrates settlement of a plurality of card transactions based on the transaction information stored in the transaction information storage unit 65, and a settlement processing unit 76. In response to the second credit confirmation request transmitted by the member store management company server 20 based on the first settlement confirmation request for fixing the sales amount of the member store in the settlement of the card transaction integrated by And a virtual card management unit 72 for transmitting the confirmation result to the member store management company server 20. In the settlement of the card transaction integrated by the settlement processing unit 76, the virtual member store management unit 71 transmits to the card issuing company server 30 a second settlement confirmation request for confirming the payment amount of the card user indicating the credit card user. I do.
Accordingly, the settlement portal server 10 according to the present embodiment can integrate a plurality of card transactions and determine the sales amount of the member store and the payment amount of the card user.

In the present embodiment, the transaction determination unit 73 includes at least member store identification information (member number, supplier ID, etc.) for identifying the member store, and card identification information (card number, buyer ID, etc.) for identifying the credit card. It is determined whether or not the settlement of the card transaction can be executed based on the account receivable amount and the usage limit amount corresponding to the user information associated with. The transaction determination unit 73 causes the virtual member store management unit 71 to transmit a credit confirmation request when confirming whether or not the credit use amount is available based on the use limit amount in the card transaction.
Thereby, the settlement portal server 10 according to the present embodiment can execute the credit check on the card issuing company server 30 without going through the member store management company server 20.

Further, in the present embodiment, the settlement processing unit 74 executes a cancellation process for canceling the settlement of the card transaction in response to the cancellation request for canceling the settlement of the card transaction, and outputs information indicating the executed cancellation process to the transaction information. It is stored in the storage unit 65.
Thereby, the settlement portal server 10 according to the present embodiment can cancel the card transaction and can recover the usage limit.

Further, the settlement processing method according to the present embodiment includes a virtual member store management section 71 in which a virtual member store management step acting on behalf of the member store management company server 20 that manages a credit card member store, and a settlement processing step. I have. In the virtual member store management step, the virtual member store management unit 71 sets the credit use amount, which is the settlement amount using the credit card credit, in response to the settlement request for requesting the settlement of the card transaction using the credit card. A credit confirmation request for requesting confirmation of whether or not the amount is equal to or less than the credit card limit is transmitted to the card issuing company server 30 for managing the credit card without passing through the member store management company server 20, and the credit confirmation request is transmitted. Receive the confirmation result for. In the settlement processing step, the settlement processing unit 74 executes the settlement of the card transaction according to the confirmation result received by the virtual member store management unit 71, and stores the transaction information of the executed card transaction in the transaction information storage unit 65. .
Thereby, the settlement processing method according to the present embodiment has the same effect as the settlement portal server 10 described above.

Further, according to the present embodiment, the settlement portal server 10 includes the settlement processing unit 74 and the settlement processing unit 76. The settlement processing unit 74 uses a credit card based on the accounts receivable user information stored in the accounts receivable user storage unit 64 that stores the accounts receivable user information in which the supplier ID and the buyer ID are associated with each other. Perform payment for card transactions. In the card transaction, the settlement processing unit 74 determines the supplier ID indicating the supplier who sold the product, the buyer ID indicating the buyer who purchased the product, the transaction amount of the card transaction, and the sales amount of the transaction amount in the card transaction. The transaction information storage unit 65 stores transaction information in which the credit amount (credit amount) using the credit amount (credit amount) and the credit amount (card settlement amount) using the credit frame of the credit card in the transaction amount are used. To memorize. The settlement processing unit 76 totals the transaction information stored in the transaction information storage unit 65 at least for each supplier ID and each buyer ID stored in the accounts receivable user storage unit 64. The settlement processing unit 76 determines the sales amount of the supplier corresponding to the supplier ID and the payment amount of the buyer corresponding to the buyer ID based on the result of the aggregation.
Thereby, the settlement portal server 10 according to the present embodiment can collectively settle settlements of a plurality of card transactions, thereby improving convenience. Therefore, the settlement portal server 10 according to the present embodiment can increase the use of credit card settlement transactions between companies.

Further, in the present embodiment, the settlement processing unit 76 includes, among the transaction information stored in the transaction information storage unit 65, the transaction amount corresponding to the supplier ID and the supplier amount stored in the receivable user storage unit 64. The sales receivable amount corresponding to the buyer ID associated with the ID is totaled for each supplier ID. The settlement processing unit 76 determines an amount obtained by subtracting the total amount of accounts receivable from the total amount of transaction amounts as the sales amount of the supplier. Further, the settlement processing unit 76 totals at least the credit use amount corresponding to the buyer ID for each buyer ID, and determines the total amount of the credit use amounts as the buyer's payment amount.
Thereby, the settlement portal server 10 according to the present embodiment stores the supplier (member store) corresponding to the supplier ID stored in the receivable user storage unit 64 and the buyer (card user) corresponding to the buyer ID. As the same company, it can be settled and managed centrally.

Further, in the present embodiment, the settlement portal server 10 determines the credit use amount included in the transaction information corresponding to the receivable user information based on the receivable holding amount (receivable amount) corresponding to the receivable user information. A receivable reassigning unit 75 is provided for rewriting to the accounts receivable amount. Then, the settlement processing unit 76 executes one of a process for determining the sales amount of the supplier and a process for determining the payment amount of the buyer for the user corresponding to the accounts receivable user information. .
As a result, the settlement portal server 10 according to the present embodiment unifies the affiliated store and the card user who have applied for the use of the accounts receivable to one of the sales amount and the payment amount as the same company. can do. For this reason, the settlement portal server 10 according to the present embodiment simplifies the processing for the user (company), thereby improving convenience.

Further, in the present embodiment, when determining the sales amount of the supplier, the settlement processing unit 76 sends the sales determination request including the amount obtained by subtracting the total amount of the accounts receivable from the total amount of the transaction amount to the supplier. When the payment is made to the member store management company server 20 for managing the member store and the payment amount of the buyer is determined, a payment confirmation request including the credit use amount is transmitted to the card issuing company server 30 for managing the credit card.
As a result, the settlement portal server 10 according to the present embodiment can collectively settle settlements of a plurality of card transactions, and can reduce the amount actually paid using accounts receivable.

In the present embodiment, the settlement processing unit 76 stores the fee information corresponding to the buyer ID from the fee storage unit 67 that stores the supplier ID or the buyer ID in association with the fee information indicating the fee in the settlement of the card transaction. Based on the acquired commission information, the payment amount of the buyer is determined, and transmitted to the card issuing company server 30 via the virtual member store management unit 71. Further, when determining the sales amount of the supplier, the settlement processing unit 76 acquires the fee information corresponding to the supplier ID from the fee storage unit 67, and determines the sales amount of the supplier based on the acquired fee information. Then, the data is transmitted to the member store management company server 20.
Thereby, the settlement portal server 10 according to the present embodiment can appropriately cope with collection or payment of a commission. In addition, the settlement portal server 10 according to the present embodiment collects or pays a fee based on the fee information associated with the supplier ID or the buyer ID, and therefore, for each supplier (member store) or buyer (card user). The rate or amount of commission can be changed for each.

Further, in the present embodiment, the settlement portal server 10 responds to an output request for requesting the output of a card transaction usage statement, based on the transaction information stored in the transaction information storage unit 65, for each supplier or for each buyer. And a detail output processing unit 77 that generates information indicating the usage details of the application and outputs the information indicating the generated usage details.
Thereby, the settlement portal server 10 can confirm the usage statement. In addition, the settlement portal server 10 can appropriately confirm the sales or purchase results. Further, since the settlement portal server 10 can be made online, it is possible to reduce, for example, the mailing cost of bills and receipts.

Further, the settlement processing method according to the present embodiment includes a settlement processing step and a settlement processing step. In the settlement processing step, the settlement processing unit 74 sets the supplier ID and the buyer ID based on the accounts receivable user information stored in the accounts receivable user storage unit 64 that stores the accounts receivable user information. The settlement of a card transaction using a credit card is executed, and in the card transaction, a supplier ID indicating a supplier who sold the product, a buyer ID indicating a buyer who purchased the product, a transaction amount of the card transaction, and the transaction amount Transactions in which the amount of accounts receivable using the amount of accounts receivable (account receivable) in card transactions and the amount of credit use (card settlement amount) using the credit line of the credit card of the transaction amount The information is stored in the transaction information storage unit 65. In the settlement processing step, the settlement processing unit 76 aggregates the transaction information stored in the transaction information storage unit 65 at least for each supplier ID and each buyer ID stored in the receivable user storage unit 64, and Based on the aggregation result, the sales amount of the supplier corresponding to the supplier ID is determined, and the payment amount of the buyer corresponding to the buyer ID is determined.
Thereby, the settlement processing method according to the present embodiment has the same effect as the settlement portal server 10 described above.

Note that, in the above-described embodiment, an example of the operation of the loan reassignment has been described with reference to FIG. 12, but the processing illustrated in FIG.
FIG. 17 is a flowchart showing a modified example of the operation of the loan reassignment in the present embodiment.
In this figure, the processing from step S701 to step S705 is the same as the processing from step S501 to step S505 shown in FIG. 12 described above, and a description thereof will be omitted here.

In step S706, the loan reassigning unit 75 determines whether or not the receivable holding amount is equal to or more than the acquired credit use amount (receivable holding amount ≧ credit use amount). That is, the loan reassigning unit 75 determines whether the amount of accounts receivable is equal to or more than the amount of credit used for one transaction. If the receivables holding amount is equal to or greater than the credit use amount (step S706: YES), the receivable reassigning unit 75 advances the process to step S707. When the amount of accounts receivable is less than the amount of credit use (step S706: NO), receivable reassigning section 75 advances the process to step S710.
In addition, the processing from step S707 to step S709 is the same as the processing from step S507 to step S509 shown in FIG. 12 described above, and a description thereof will not be repeated.

  In step S710, the receivable reassigning unit 75 executes a credit exchanging process for the amount of accounts receivable. Here, the credit reassigning unit 75 transmits a credit cancellation request for the credit usage amount to the card issuing company server 30 via the virtual member store management unit 71 and cancels the credit for the credit usage amount. , (Credit usage amount-receivable holding amount). This means that the credit exchange processing for the accounts receivable amount has been executed. In addition, the loan reassigning unit 75 adds a record in which the transaction information is updated to the transaction information storage unit 65. After the process in step S710, the loan reassigning unit 75 causes the process to proceed to step S708.

As described above, in the present modification, the receivable reassignment unit 75 determines that the amount of accounts receivable held is less than the amount of accounts receivable corresponding to To the usage limit.
As a result, the settlement portal server 10 according to the present embodiment can easily execute the loan reassignment process, and can more appropriately recover the usage limit (credit limit).
In the example of the receivable reassignment process described above, the receivable reassignment unit 75 is described as executing the receivable remittance process periodically (for example, every day). The reassignment process may be executed at any time. Further, the example in which the reassignment unit 75 extracts the transaction information in ascending order of the credit use amount has been described, but in the present modification, the extraction condition of the transaction information is not limited to this.

Further, in the above-described embodiment, the example in which the settlement portal server 10 preferentially uses the amount of accounts receivable (accounts receivable) when utilizing accounts receivable, but is not limited thereto. The credit line may be used with priority. That is, the transaction determination unit 73 determines that the settlement of the card transaction can be executed when the amount obtained by subtracting the usage limit from the transaction amount of the card transaction is equal to or less than the amount of the accounts receivable. When the transaction determination unit 73 determines that the settlement of the card transaction can be executed, the settlement processing unit 74 determines that the credit use amount (the credit card amount) which is the settlement amount using the credit card credit for the settlement of the card transaction. (Payment amount) may be used with priority.
As a result, the payment portal server 10 can make a card transaction by using the accounts receivable, even in the conventional payment system, which is impossible due to the usage limit amount, as in the above-described example.

[Second embodiment]
Next, a payment system 1a according to a second embodiment will be described with reference to the drawings.
FIG. 18 is a block diagram illustrating an example of a payment system 1a according to the present embodiment.
As shown in this figure, the settlement system 1a includes a settlement portal server 10a, a member store management company server 20, a card issuing company server 30, a member store terminal 40, and a card user terminal 50. The settlement portal server 10a, the member store management company server 20, the card issuing company server 30, the member store terminal 40, and the card user terminal 50 can be connected to each other via the network NW1.
In this figure, the same components as those shown in FIG. 1 are denoted by the same reference numerals, and description thereof will be omitted.

The settlement portal server 10a includes an NW communication unit 11, a storage unit 60a, and a control unit 70a.
The storage unit 60a stores information used for various processes of the settlement portal server 10a. The storage unit 60a includes, for example, an account storage unit 61, a supplier information storage unit 62, a buyer information storage unit 63, a receivable user storage unit 64, a transaction information storage unit 65, and a sales information storage unit 66. A commission storage unit 67 and a receivable storage unit 68 are provided.

The receivable storage unit 68 stores the amount of accounts receivable. For example, as shown in FIG. 19, the receivable storage unit 68 stores “supplier ID”, “receivable amount”, “update date”, and “invoice number” in association with each other. The “invoice number” stores the number of the invoice that triggered the update of the amount of accounts receivable.
FIG. 19 is a diagram illustrating an example of data stored in the receivable storage unit 68 in the present embodiment.
In the example shown in FIG. 19, the “supplier ID” corresponding to “S00B1” is “1,000,000” (1,000,000 yen), and the “update date” is “YYYY / MM / DD ", indicating that the" bill number "is" 1 ".

  Returning to the description of FIG. 18, the control unit 70a is, for example, a processor including a CPU and the like, and controls the settlement portal server 10a as a whole. The control unit 70a includes a virtual member store management unit 71, a virtual card management unit 72, a transaction determination unit 73, a settlement processing unit 74, a debt reassignment unit 75, a settlement processing unit 76, and a statement output processing unit 77. And a receivable changing unit 78.

  When executing the portal use transaction, the accounts receivable change unit 78 determines, based on the portal use amount of the portal use transaction, the accounts receivable amount related to the portal use transaction among the accounts receivable stored in the receivable storage unit 68. Change the amount of accounts receivable corresponding to the customer information. For example, when executing the portal use transaction, the accounts receivable change unit 78 holds the accounts receivable corresponding to the accounts receivable user information including the member store identification information (supplier ID, member store number, etc.) indicating the supplier selling the product. The portal usage amount is added to the amount, and the payment amount for the portal usage transaction is calculated based on the accounts receivable amount corresponding to the accounts receivable user information including the identification information (card number, buyer ID, etc.) indicating the buyer who purchases the product. Subtract the used accounts receivable amount.

As described above, in the settlement portal server 10a according to the present embodiment, the receivable storage unit 68 stores the receivable holding amount corresponding to the receivable user information, and the receivable changing unit 78 stores the receivable amount in the portal use transaction. The receivable amount stored in the receivable storage unit 68 is changed accordingly.
Accordingly, the settlement portal server 10a according to the present embodiment does not need to calculate the amount of accounts receivable each time at the time of a transaction using the portal, and can simplify the processing.

[Third Embodiment]
Next, a payment system 1b according to a third embodiment will be described with reference to the drawings.
FIG. 20 is a block diagram illustrating an example of a payment system 1b according to the present embodiment.
As shown in this figure, the settlement system 1b includes a settlement portal server 10b, a member store management company server 20, a card issuing company server 30, a member store terminal 40, and a card user terminal 50. The settlement portal server 10b, the member store management company server 20, the card issuing company server 30, the member store terminal 40, and the card user terminal 50 can be connected to each other via the network NW1.
In this figure, the same components as those shown in FIG. 1 are denoted by the same reference numerals, and description thereof will be omitted.

The settlement portal server 10b includes an NW communication unit 11, a storage unit 60, and a control unit 70b.
The control unit 70b is, for example, a processor including a CPU and the like, and controls the settlement portal server 10b as a whole. The control unit 70b includes a transaction determination unit 73, a settlement processing unit 74, a reassignment unit 75, a settlement processing unit 76, and a statement output processing unit 77.
This embodiment is different from the first embodiment in that the control unit 70b does not include the virtual member store management unit 71 and the virtual card management unit 72.
Since the settlement portal server 10b according to the present embodiment does not include the virtual member store management unit 71 and the virtual card management unit 72, there is no disconnection between the member store management company server 20 and the card issuing company server 30. The settlement processing shown in FIG.

FIG. 21 is a diagram illustrating an example of the operation of the payment process according to the present embodiment.
In FIG. 21, the portal use transaction KS5 indicates the same transaction as the portal use transaction KS2 in FIG. 13. In the state where the amount of accounts receivable is 1,000,000 yen, B purchases 1.3 million yen from C company. An example in the case of performing is shown. In the portal use transaction KS5, the member store terminal 40-2 of the company C bills the settlement portal server 10b for 1.3 million yen, while the card user terminal 50-2 of the company B charges 1.3 million yen. Is transmitted to the settlement portal server 10b. In this case, the settlement portal server 10b first confirms the credit of 1.3 million yen to the card issuing company server 30-2 of the company B via the member store management company server 20-2 of the company C. Is 1 million yen, the credit confirmation result “NG” is received.

Therefore, the settlement portal server 10b uses the amount of accounts receivable of 1 million yen, and the settlement portal server 10b communicates with the card issuing company server 30-2 of the company B via the member store management company server 20-2 of the company C. A credit check of 300,000 yen is made again. In this case, since 300,000 yen is equal to or less than the usage limit, the card issuing company server 30-2 transmits the credit confirmation result “OK”, and the settlement portal server 10b sends the credit usage amount of 300,000 yen to Company B. And a receivable use amount of -1 million yen is generated, and the receivable amount of Company B is 0 yen. In addition, the company C has a 1.3 million yen receivable holding amount. In this case, the settlement processing unit 74 of the settlement portal server 10b adds the transaction information of the record R1 in FIG.
Further, the settlement portal server 10b notifies both the card user terminal 50-2 of Company B and the member store terminal 40-2 of Company C of the completion of payment indicating that the portal use settlement has been completed.

As described above, in the settlement portal server 10b according to the present embodiment, the transaction determination unit 73 determines that settlement of the portal use transaction can be executed when the portal use amount is equal to or less than the accounts receivable amount. Then, when the portal usage amount exceeds the accounts receivable amount, the transaction determination unit 73 requests the confirmation whether the amount obtained by subtracting the accounts receivable amount from the portal usage amount is equal to or less than the usage limit amount. The confirmation request is transmitted to the card issuing company server 30 that manages the credit card via the member store management company server 20 that manages the member store, and based on the confirmation result received in response to the credit confirmation request, the portal is executed. It is determined whether the settlement of the use transaction can be executed.
As a result, the settlement portal server 10b according to the present embodiment can realize a card transaction using accounts receivable (accounts receivable), as in the first embodiment.

Note that the present invention is not limited to the above embodiments, and can be modified without departing from the spirit of the present invention.
For example, in the above first and second embodiments, the settlement portal server 10 (10a) does not include the virtual member store management unit 71 and the virtual card management unit 72, and the virtual member store management unit 71 and the virtual card management Each of the units 72 may be configured by a server device.
FIG. 22 is a first diagram illustrating a modified example of settlement system 1.
In this figure, as an example, in the settlement system 1 of the first embodiment, the virtual member store management unit 71 and the virtual card management unit 72 include a virtual member store management server 71A (virtual member store management device) and a virtual card management An example in the case of a server 72A (virtual card management device) is shown. The configuration shown in FIG. 22 may be, for example, a case where a card company having the functions of a card issuing company (Issuer) and a member store management company (Acquirer) provides the inter-company settlement service described above.

As described above, the settlement system 1 illustrated in FIG. 22 includes the virtual member store management server 71A, the settlement portal server 10, and the virtual card management server 72A. The virtual affiliate store management server 71A is a virtual affiliate store management device acting as a proxy for the affiliate store management company server 20 that manages the affiliate store of the credit card. The virtual member store management server 71A changes the credit use amount (card settlement amount), which is the settlement amount using the credit of the credit card, in response to the settlement request for requesting the settlement of the card transaction using the credit card. A first credit confirmation request for requesting confirmation of whether or not the amount is equal to or less than the usage limit is transmitted to a card issuing company server 30 for managing a credit card instead of the member store management company server 20, and the first credit confirmation is performed. Receive the confirmation result for the request. The settlement portal server 10 executes the settlement of the card transaction according to the confirmation result received by the virtual member store management server 71A, and stores the transaction information of the executed card transaction in the transaction information storage unit 65. Based on the transaction information stored in the transaction information storage unit 65, the virtual card management server 72A determines the sales amount of the member store in the settlement of the card transaction in which the settlement portal server 10 integrates the settlement of a plurality of card transactions. In response to the second credit confirmation request transmitted by the member store management company server 20 based on the first settlement confirmation request, a confirmation result is transmitted instead of the card issuing company server 30.
Thereby, the settlement system 1 shown in FIG. 22 has the same effect as the first embodiment.

FIG. 23 is a second diagram illustrating a modified example of settlement system 1.
In this figure, in the settlement system 1 according to the first embodiment, the virtual member store management unit 71 and the virtual card management unit 72 include a virtual member store management server 71A (virtual member store management device) and a virtual card management server 72A ( 5 shows another example in the case of a virtual card management device). The configuration shown in FIG. 23 may be, for example, a case where a card company having the functions of a card brand, a card issuing company (Issuer) and a member store management company (Acquirer) provides the inter-company settlement service described above.

In the case shown in FIG. 23, the virtual member store management server 71A (virtual member store management unit 71) provides the card user managed by the virtual card management server 72A (virtual card management unit 72) with a credit usage amount ( When confirming whether or not the card payment amount is available based on the usage limit, the first credit confirmation request is transmitted to the virtual card management server 72A. That is, in this case, the settlement system 1 can provide an inter-company settlement service without requiring the member store management company server 20 and the card issuing company server 30. The virtual member store management server 71A (virtual member store management unit 71) provides the card user not managed by the virtual card management server 72A (virtual card management unit 72) to the card user in the same manner as shown in FIG. The first credit confirmation request is transmitted to the card issuing company server 30.
The payment portal server 10 including the virtual member store management unit 71 and the virtual card management unit 72 shown in FIG. 1 may execute the same processing as that in FIG.

FIG. 24 is a third diagram illustrating a modification of settlement system 1.
In this figure, in the settlement system 1 according to the first embodiment, the virtual member store management unit 71 and the virtual card management unit 72 include a virtual member store management server 71A (virtual member store management device) and a virtual card management server 72A ( 5 shows another example in the case of a virtual card management device). The configuration shown in FIG. 24 is, for example, a case where a finance company or the like provides the inter-company settlement service described above in cooperation with a card company having the functions of a card issuing company (Issuer) and a member store management company (Acquirer). Can be considered. In this case, as shown in FIG. 24, the settlement system 1 provided by the finance company includes a virtual member store management server 71A (virtual member store management unit 71) and a virtual card management server 72A (virtual card management unit 72). It may be configured without being performed.

Further, in each of the above embodiments, the example in which the settlement portal server 10 (10a, 10b) includes the storage unit 60 (60a) has been described. 10 (10a, 10b). For example, part or all of the storage unit 60 (60a) may be an external storage device connected to the network NW1.
Further, in each of the above-described embodiments, an example in which a credit card is used as an example of a payment card has been described. However, the present invention is not limited to this. You may make it apply to the payment system 1 (1a, 1b).

In each of the above embodiments, the member store management company server 20 includes the member store management storage unit 21, and the member store information acquisition unit 81 acquires the member store contract information from the member store management storage unit 21. Although described, the present invention is not limited to this. The storage unit 60 (60a) may store member store contract information, or another server device may store member store contract information.
Further, in each of the above embodiments, an example has been described in which the card issuing company server 30 includes the card management storage unit 31 and the card information acquisition unit 83 acquires the card contract information from the card management storage unit 31. However, the present invention is not limited to this. The storage unit 60 (60a) may store the card contract information, or another server device may store the card contract information.

  Further, in each of the above embodiments, the example in which the settlement portal server 10 (10a, 10b) can use the entire amount of the accounts receivable for the card transaction has been described. ) May be used, or the upper limit of accounts receivable may be set separately. When the use of accounts receivable is restricted, the settlement portal server 10 (10a, 10b) stores the usable ratio information or the upper limit of use in the storage unit 60 (60a) in association with the accounts receivable user information. You may do so. In this case, the settlement portal server 10 (10a, 10b) can change the usable ratio information or the use upper limit amount for each user.

Each of the components included in the payment system 1 (1a, 1b) and the payment portal server 10 (10a, 10b) has a computer system therein. Then, a program for realizing the functions of the respective components of the payment system 1 (1a, 1b) and the payment portal server 10 (10a, 10b) is recorded on a computer-readable recording medium, and is recorded on the recording medium. The computer system may read and execute the recorded program to execute the processes in the respective configurations of the payment system 1 (1a, 1b) and the payment portal server 10 (10a, 10b) described above. Here, "to make the computer system read and execute the program recorded on the recording medium" includes installing the program in the computer system. The “computer system” here includes an OS and hardware such as peripheral devices.
Further, the “computer system” may include a plurality of computer devices connected via a network including a communication line such as the Internet, a WAN, a LAN, and a dedicated line. The “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, and a CD-ROM, and a storage device such as a hard disk built in a computer system. As described above, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM.

  The recording medium also includes an internal or external recording medium accessible from the distribution server for distributing the program. It should be noted that the program is divided into a plurality of programs, each of which is downloaded at a different timing, and then combined with each of the components included in the settlement system 1 (1a, 1b) and the settlement portal server 10 (10a, 10b). The distribution server that distributes each may be different. Further, the “computer-readable recording medium” holds a program for a certain period of time, such as a volatile memory (RAM) in a computer system serving as a server or a client when the program is transmitted via a network. Shall be included. Further, the program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

  Further, some or all of the above functions may be realized as an integrated circuit such as an LSI (Large Scale Integration). Each of the above-described functions may be individually formed into a processor, or a part or all of the functions may be integrated into a processor. The method of circuit integration is not limited to an LSI, and may be realized by a dedicated circuit or a general-purpose processor. Further, in the case where a technology for forming an integrated circuit that replaces the LSI appears due to the progress of the semiconductor technology, an integrated circuit based on the technology may be used.

1, 1a, 1b payment system 10, 10a, 10b payment portal server 11 NW communication unit 20, 20-1, 20-2 member store management company server 21 member store management storage unit 30, 30-1, 30-2, 30 -3 Card issuing company server 31 Card management storage unit 40, 40-1, 40-2 Member store terminal 41, 51 Input unit 42, 52 Display unit 50, 50-1, 50-2, 50-3 Card user terminal 60, 60a storage unit 61 account storage unit 62 supplier information storage unit 63 buyer information storage unit 64 accounts receivable user storage unit 65 transaction information storage unit 66 sales information storage unit 67 commission storage unit 68 accounts receivable storage unit 70, 70a, 70b control Part 71 Virtual member store management part 71A Virtual member store management server 72 Virtual card management part 72A Virtual card management server 73 Transaction determination 74 Settlement processing unit 75 Receivable reassignment unit 76 Settlement processing unit 77 Statement output processing unit 78 Accounts receivable changing unit 80 Registration unit 81 Member store information acquisition unit 82 Supplier registration unit 83 Card information acquisition unit 84 Buyer registration unit 85 Accounts receivable registration unit NW1 network

Claims (14)

The accounts receivable stored in the accounts receivable user storage unit that stores the accounts receivable user information that associates the supplier identification information for identifying the supplier who sells the goods with the buyer identification information for identifying the buyer who purchases the goods. Based on the user information, the settlement of the card transaction using the settlement card is executed, and in the card transaction, the supplier identification information indicating the supplier who sold the product and the buyer identification information indicating the buyer who purchased the product. And the transaction amount of the card transaction, the credit amount using the credit amount of the settlement card of the transaction amount, and the credit amount using the credit amount of the settlement card of the transaction amount. A payment processing unit for storing the associated transaction information in the transaction information storage unit,
The transaction information stored in the transaction information storage unit, at least for each of the supplier identification information and for each buyer identification information stored in the receivable user storage unit, based on the aggregation results, A settlement processing unit for fixing the sales amount of the supplier corresponding to the supplier identification information and fixing the payment amount of the buyer corresponding to the buyer identification information ,
The time when the receivable amount is used for the receivable amount in the aggregated transaction information is the same as the time when the credit of the settlement card is used for the credit amount in the aggregated transaction information. Payment processing device. The settlement processing unit,
Among the transaction information stored in the transaction information storage unit, the transaction amount corresponding to the supplier identification information, and the transaction amount associated with the supplier identification information stored in the receivable user storage unit. The receivable amount corresponding to the buyer identification information and the receivable amount are totaled for each supplier ID information, and the amount obtained by subtracting the total amount of the receivable amount from the total amount of the transaction amount is determined as the sales amount of the supplier. Let me
The settlement according to claim 1, wherein at least the credit usage amount corresponding to the buyer identification information is totaled for each of the buyer identification information, and the total amount of the credit usage amounts is determined as the payment amount of the buyer. Processing equipment. Based on the receivable amount corresponding to the receivables user information, comprising a receivable reassignment unit that replaces the credit use amount included in the transaction information corresponding to the receivables user information with the receivable amount,
The settlement processing unit,
For the user corresponding to the accounts receivable user information, one of a process for determining the sales amount of the supplier and a process for determining the payment amount of the buyer is executed. The settlement processing device according to claim 2. The settlement processing unit,
When determining the sales amount of the supplier, a sales confirmation request including an amount obtained by subtracting the total amount of the accounts receivable from the total amount of the transaction amounts, a member store management device that manages the member store as the supplier Sent to
The payment according to claim 2 or 3, wherein when the payment amount of the buyer is determined, a payment determination request including the credit usage amount is transmitted to a card management device that manages the payment card. Processing equipment. In response to an output request requesting output of a usage statement of the card transaction, information indicating the usage statement for each supplier or each buyer is generated based on the transaction information stored in the transaction information storage unit. The settlement processing device according to any one of claims 1 to 4, further comprising a statement output processing unit that outputs information indicating the generated usage statement. A settlement processing device according to any one of claims 1 to 5,
A franchise store management device for managing franchise stores of payment cards used for transactions,
A card management device for managing the payment card. The settlement processing unit is stored in an accounts receivable user storage unit that stores accounts receivable user information in which supplier identification information for identifying a supplier who sells the product and buyer identification information for identifying a buyer who purchases the product. Based on the accounts receivable user information, the settlement of a card transaction using a settlement card is executed, and in the card transaction, the supplier identification information indicating the supplier who sold the product, and the buyer who purchased the product, The buyer identification information, the transaction amount of the card transaction, the credit amount of the settlement card using the receivable amount using the receivable amount in the card transaction of the transaction amount, and the credit of the settlement card of the transaction amount are used. A settlement processing step of storing transaction information associated with a credit use amount in a transaction information storage unit;
A settlement processing unit that aggregates the transaction information stored in the transaction information storage unit at least for each of the supplier identification information and the buyer identification information stored in the receivable user storage unit, and based on the results, along with the corresponding finalizing the sales amount of suppliers to the supplier identification information, settlement processing method characterized by comprising the settlement process step for confirming the payment amount of the buyer corresponding to the buyer identification information So,
The time when the receivable amount is used for the receivable amount in the aggregated transaction information is the same as the time when the credit of the settlement card is used for the credit amount in the aggregated transaction information.
Payment processing method . On the computer,
The accounts receivable stored in the accounts receivable user storage unit that stores the accounts receivable user information in which the supplier identifying information for identifying the supplier who sells the goods and the buyer identifying information for identifying the buyer who purchases the goods. Based on the user information, the settlement of the card transaction using the settlement card is executed, and in the card transaction, the supplier identification information indicating the supplier who sold the product and the buyer identification information indicating the buyer who purchased the product. And the transaction amount of the card transaction, the credit amount using the credit amount of the settlement card of the transaction amount, and the credit amount using the credit amount of the settlement card of the transaction amount. A payment processing step of storing the associated transaction information in the transaction information storage unit;
The transaction information stored in the transaction information storage unit, at least for each of the supplier identification information and the buyer identification information stored in the receivable user storage unit, based on the aggregation result, based on the aggregation result, And a settlement processing step for fixing the sales amount of the supplier corresponding to the supplier identification information and for fixing the payment amount of the buyer corresponding to the buyer identification information .
The time when the receivable amount is used for the receivable amount in the aggregated transaction information is the same as the time when the credit of the settlement card is used for the credit amount in the aggregated transaction information.
Program . A transaction determination unit that determines whether settlement of the card transaction is executable,
When the amount obtained by subtracting the receivable amount from the transaction amount of the card transaction is equal to or less than the usage limit, the transaction determination unit determines that the settlement of the card transaction is executable, and the settlement processing unit determines that the card transaction is The settlement processing apparatus according to claim 1, wherein the receivable amount is preferentially used for settlement of the payment. A transaction determination unit that determines whether settlement of the card transaction is executable,
When the amount obtained by subtracting the usage limit from the transaction amount of the card transaction is equal to or less than the receivable amount, the transaction determination unit determines that the settlement of the card transaction is executable, and the settlement processing unit performs the card transaction. The payment processing device according to claim 1, wherein a credit card payment amount, which is a payment amount using credit of the payment card, is used for the payment of the credit card with priority. When the amount obtained by subtracting the receivable amount from the transaction amount of the card transaction is equal to or less than a usage limit, a step in which the transaction determination unit determines that settlement of the card transaction is executable,
A step of, if the transaction determination unit determines that the settlement of the card transaction is executable, the settlement processing unit preferentially using the receivable amount for the settlement of the card transaction. Item 7. The settlement processing method according to Item 7. When the amount obtained by subtracting the receivable amount from the transaction amount of the card transaction is equal to or less than the receivable amount, the transaction determining unit determines that settlement of the card transaction is executable,
When the transaction determination unit determines that the settlement of the card transaction is executable, the settlement processing unit gives priority to a card settlement amount that is a settlement amount using credit of the settlement card for settlement of the card transaction. The settlement processing method according to claim 7, further comprising the step of: On the computer,
When the amount obtained by subtracting the receivable amount from the transaction amount of the card transaction is equal to or less than a usage limit, determining that the settlement of the card transaction is executable;
The program according to claim 8, further comprising, if it is determined that the settlement of the card transaction can be executed, preferentially using the receivable amount in the settlement of the card transaction. On the computer,
When the amount obtained by subtracting the receivable amount from the transaction amount of the card transaction is equal to or less than a usage limit, determining that the settlement of the card transaction is executable;
If it is determined that the settlement of the card transaction is executable,
The program according to claim 8, further comprising: prioritizing a card payment amount, which is a payment amount using credit of the payment card, in the settlement of the card transaction.

Images