JP6465149B2 - Payment request service providing program, method, and apparatus - Google Patents

Description

The present invention relates to a payment request service providing program, a payment request service providing method, and a payment request service providing apparatus .

  The following technologies are disclosed as technologies for realizing electronic commerce in which a product purchaser and a payer are different. In other words, the first technology mediates the order procedure between the transaction price payment source and the price payment destination, temporarily interrupts the order procedure until the transaction price payment procedure is completed, and is necessary to resume the order procedure Store the necessary information, and resume the order process after the payment procedure is completed.

  In addition, when the consumer who becomes a member is a family member of a householder who is a contractor with a public service provider, the upper limit payment amount to the seller is preliminarily given to the family member based on the information on the deduction of public charges. A second technique for defining is also disclosed. In the second technology, when the consumer purchases a product from the seller on the homepage, when the payment is requested from the payment settlement agent, whether or not the payment can be made using the information on the utility charge debit account. Determine.

  In addition, a third technique is disclosed in which a “need” button is displayed on a site where a product is sold and a “need” button is pressed, and a message embedded with a link to the product page is transmitted to the nephew partner. In the third technique, when the swearing person selects a link embedded in the message, the person who is struck is led to a product page of an electronic commerce site, and a purchase procedure can be performed from the page.

  Furthermore, a fourth technique for displaying an “onset cart” on a site for selling products is also disclosed. In the fourth technology, when a product is placed in an “Ondori Kart” and proceeding to payment, a one-time ID / password and a link to the payment confirmation screen are generated. A link will be sent and sent. The person who has received the notification mail can log in using the one-time ID / password and make a payment on the payment confirmation screen (or reject it). Further, in the fourth technique, when the notification mail is left for two weeks, the information on the “request cart” is automatically canceled.

JP 2001-283126 A JP 2001-283131 A

Asia Co., Ltd., “Skilled Onedari”, [online], [Search June 27, 2010], Internet <URL: http: // www. onedarizyouzu. jp / guide. html> Triump Online Shop, “Ondake Function”, [online], [Search June 27, 2010], Internet <URL: http: // shop. trinmphjapan. com / info / onedari. html>

  However, since the first technology and the fourth technology have no restrictions on the request destination of the payment, it is not possible to prevent a malicious user from requesting payment of any other user. There are concerns about the safety of transactions. In addition, the second technique is based on the premise that the payment requester and the payer have a family relationship, and users who have a relationship other than the family relationship cannot request for payment. In addition, the third technique is a technique for introducing a product to a beating partner and prompting the purchase, and it is necessary to take a procedure for purchasing the product by the sought person himself, so that the operation is complicated.

  In one aspect, the present invention is directed to realizing secure electronic commerce.

In one embodiment, when receiving a designation of a product or service from a first user and a designation of a second user as a destination to request payment of the price of the product or service, the second user A request for payment of the price is transmitted to the user. When detecting the denial of the said request, and notifies a rejection of the request to the first user, a notice indicating that rejected the request to the second user .

  As one aspect, it has an effect that a safe electronic commerce can be realized.

It is a functional block diagram of a purchase service providing apparatus. It is a schematic block diagram of an electronic commerce system. It is a flowchart of a delegation approval reception process. It is a flowchart of a delegation approval permission process. It is a flowchart of an automatic payment reception process. It is a flowchart of a payment commission acceptance process. It is a flowchart of an inventory allocation process. It is a flowchart of a payment process. It is a flowchart of an order process. It is a chart which shows delegation permission information. It is a chart which shows automatic payment information. It is a chart which shows inventory information. It is a chart which shows merchandise provision information. It is a chart which shows shopping cart shared information. It is a chart which shows payment commission detailed information. It is a chart which shows purchase details information. It is an image figure which shows an example of a payment commission request selection screen. It is an image figure which shows an example of the notification screen during permission request. It is an image figure which shows an example of a payment commission request screen. It is an image figure which shows an example of a permission notification screen. It is an image figure which shows an example of an automatic payment information registration screen. It is an image figure which shows an example of a payment completion notification screen. It is an image figure which shows an example of a payment incomplete notification screen. It is an image figure which shows an example of a shopping cart display screen. It is an image figure which shows an example of a request destination selection screen. It is an image figure which shows an example of a payment request screen. It is an image figure which shows an example of a stock allocation failure screen. It is an image figure which shows an example of a shopping cart display screen. It is an image figure which shows an example of the payment method selection screen. It is an image figure which shows an example of a payment completion screen. It is an image figure which shows an example of a reason input screen. It is an image figure which shows an example of a payment refusal notification screen. It is an image figure which shows an example of a payment details display screen. It is an image figure which shows an example of a shopping cart display screen. It is an image figure which shows an example of a purchase details screen. It is an image figure which shows an example of the payment commission approval request notification mail transmitted to the user A. It is an image figure which shows an example of the payment commission approval request notification mail transmitted to the user B. It is an image figure which shows an example of the completion mail of the payment commission transmitted to the user A. It is an image figure which shows an example of the completion mail of the payment commission transmitted to the user B. It is an image figure which shows an example of the cancellation mail of the payment commission transmitted to the user A. It is an image figure which shows an example of the cancellation mail of the payment commission transmitted to the user B. It is an image figure which shows an example of the time limit overdue mail of the payment commission transmitted to the user B. It is an image figure which shows an example of the payment completion notification mail transmitted to the user B. It is an image figure which shows an example of the payment incomplete notification mail transmitted to the user B. It is an image figure which shows an example of the payment request notification mail transmitted to the user A. It is an image figure which shows an example of the payment request notification mail transmitted to the user B. It is an image figure which shows an example of the payment completion notification mail transmitted to the user A. It is an image figure which shows an example of the payment completion notification mail transmitted to the user B. It is an image figure which shows an example of the payment refusal notification mail transmitted to the user A. It is an image figure which shows an example of the payment refusal notification mail transmitted to the user B. It is an image figure which shows an example of the shopping cart display screen in case several users receive payment commission.

  Hereinafter, an example of an embodiment of the disclosed technology will be described in detail with reference to the drawings. FIG. 1 shows a purchase service providing apparatus 10 according to the present embodiment. The purchase service providing apparatus 10 includes a delegation information management unit 12, a user management unit 14, a shopping basket management unit 16, an inventory information management unit 18, a reason notification unit 20, a settlement processing unit 22, a delegation information storage unit 24, and automatic payment information. A storage unit 26 and a shopping cart shared information storage unit 28 are provided. The purchase service providing apparatus 10 includes an inventory information storage unit 30 and a detailed information storage unit 32.

  The delegation information management unit 12 inquires of the second user whether or not to accept the delegation of payment for delegating payment for the product purchased by the first user to the second user, and the delegation of payment is granted by the second user. In this case, a process of setting the delegation permission information in the delegation permission information table 80 (see FIG. 2) is performed. The delegation permission information table 80 is stored in the delegation information storage unit 24.

  The user management unit 14 sets the automatic payment information including the input limit in the automatic payment information table 82 (see FIG. 2) when the limit of automatic payment in the payment delegation is input from the second user. Perform the process. The automatic payment information table 82 is stored in the automatic payment information storage unit 26.

  The shopping cart management unit 16 requests the first user to pay for the product purchased by the first user from the first user and stores the delegation permission information corresponding to the delegation information storage unit 24. The following processing is performed. That is, the shopping cart management unit 16 displays a list of shopping carts in which the name, quantity, and price of the product purchased by the first user are displayed on the display device referred to by the second user, and allows the second user to Ask for payment.

  Further, displaying the shopping cart list on the display device referred to by the second user is performed by sharing the shopping cart list between the first user and the second user. The shopping cart management unit 16 stores the shopping cart shared information including information indicating that the list of shopping carts is shared between the first user and the second user, as shown in FIG. Set to Browse). The shopping cart shared information table 84 is stored in the shopping cart shared information storage unit 28.

  When the first user requests payment by the first user for the product purchased by the first user, the stock information management unit 18 stocks the product by the quantity described in the shopping cart list. Subtract from table 86 (see FIG. 2). Further, the inventory information management unit 18 performs a process of temporarily securing the product by registering the product in a provisionally secured state in the product allocation table 88 (see FIG. 2) for the quantity described in the shopping cart list. . The inventory information table 86 and the product allocation table 88 are stored in the inventory information storage unit 30.

  The reason notifying unit 20 refused the payment when the second user refused to pay for the goods or services listed in the shopping cart list displayed on the display device referred to by the second user. A reason input screen for inputting the reason is displayed on the display device. And the reason notification part 20 notifies the reason for the payment refusal input via the reason input screen to a 1st user.

  When the payment processing unit 22 is instructed by the second user to pay for the product whose name, quantity, and price are listed in the shopping cart list displayed on the display device referred to by the second user. The following processing is performed. In other words, the settlement processing unit 22 performs a settlement process in which the price of the product is settled with the funds of the second user, sets purchase detail information in the purchase detail table 90 stored in the detail information storage unit 32, and makes payment delegation. Payment delegation item information is set in the item table 92.

  The purchase service providing apparatus 10 can be realized by an electronic commerce server 38 included in the electronic commerce system 36 shown in FIG. The electronic commerce system 36 includes an electronic commerce server 38 and a plurality of terminal devices 42 connected to the electronic commerce server 38 via a network 40 such as the Internet.

  The electronic commerce server 38 includes a CPU 44, a memory 46, a storage unit 48, an input unit 50, a display unit 52, a medium read / write device (R / W) 54, and a communication interface (I / F) unit 58. The CPU 44, the memory 46, the storage unit 48, the input unit 50, the display unit 52, and the medium read / write device 54 are connected to each other via a bus 60. The medium read / write device 54 reads information written on the recording medium 62 and writes information on the recording medium 62.

  The storage unit 48 can be realized by an HDD (Hard Disk Drive), a flash memory, or the like. The storage unit 48 stores a purchase service providing program 64 for causing the electronic commerce server 38 to function as the purchase service providing apparatus 10. In the purchase service providing program 64, the recording medium 62 in which the purchase service providing program 64 is written is set in the medium read / write device 54, and the medium read / write device 54 reads the purchase service providing program 64 from the recording medium 62. It is stored in the storage unit 48. The CPU 44 reads the purchase service providing program 64 from the storage unit 48 and expands it in the memory 46, and sequentially executes the processes of the purchase service providing program 64.

  The purchase service providing program 64 includes a delegation information management process 66, a user management process 68, a shopping basket management process 70, an inventory information management process 72, a reason notification process 74, and a settlement processing process 76. The CPU 44 operates as the delegation information management unit 12 illustrated in FIG. 1 by executing the delegation information management process 66. The CPU 44 operates as the user management unit 14 shown in FIG. 1 by executing the user management process 68. The CPU 44 operates as the shopping cart management unit 16 shown in FIG. 1 by executing the shopping cart management process 70. The CPU 44 operates as the inventory information management unit 18 shown in FIG. 1 by executing the inventory information management process 72. The CPU 44 operates as the reason notifying unit 20 shown in FIG. 1 by executing the reason notifying process 74. The CPU 44 operates as the payment processing unit 22 shown in FIG. 1 by executing the payment processing process 76. Thereby, the electronic commerce server 38 that has executed the purchase service providing program 64 functions as the purchase service providing apparatus 10. The purchase service providing program 64 is an example of a purchase service providing program according to the disclosed technology.

  In addition, a delegation permission information table 80, an automatic payment information table 82, a shopping cart sharing information table 84, an inventory information table 86, a product allocation table 88, a purchase details table 90 and a payment delegation details table 92 are stored in the storage unit 48. Yes. Thereby, the storage unit 48 functions as the delegation information storage unit 24, the automatic payment information storage unit 26, the shopping cart shared information storage unit 28, the inventory information storage unit 30, and the detailed information storage unit 32. The purchase service providing apparatus 10 can be realized by, for example, a semiconductor integrated circuit, more specifically, an ASIC (Application Specific Integrated Circuit).

  On the other hand, the terminal device 42 includes a CPU 94, a memory 96, a storage unit 98, an input unit 100, a display unit 102, and a communication interface (I / F) unit 104. As the terminal device 42, for example, a personal computer (PC: Personal Computer) or a smart terminal which is a portable information processing device equipped with a personal digital assistant (PDA) function can be applied. A browser (browsing software) is installed in the storage unit 98.

  Next, the operation of this embodiment will be described. The electronic commerce server 38 introduces products to be sold through the network 40 and operates a product sales website for accepting product orders from arbitrary users. The merchandise sales website operated by the electronic commerce server 38 allows the first user (user A) to pay for the merchandise purchased by the second user (user B). It is also possible to settle the price of.

  When using the payment delegation, the user A first accesses the merchandise sales website by starting a browser on the terminal device 42 and performing an operation such as specifying a URL (Uniform Resource Locator). Thereby, the homepage of the product sales website is distributed from the electronic commerce server 38 to the terminal device 42 operated by the user A, and the homepage of the product sales website is displayed on the display unit 102. The home page displayed on the display unit 102 displays options for instructing a payment delegation request, and the user A instructs the payment delegation request by selecting the option. With this operation as a trigger, the delegation approval acceptance process shown in FIG. 3 is executed by the electronic commerce server 38.

  In step 118 of the delegation approval reception process, the delegation information management unit 12 operates the payment delegation request target person input screen provided with an input field for inputting information for specifying a person delegated to the request for payment delegation. To the terminal device 42 to be delivered. As a result, the payment delegation request target person input screen is displayed on the display unit 102 of the terminal device 42 operated by the user A.

  In the next step 119, the delegation information management unit 12 determines whether or not information for specifying a payment delegation request target person has been input via the payment delegation request target person input screen, and step 119 until the determination is affirmed. repeat. When the payment delegation request target person input screen is displayed on the display unit 102 of the terminal device 42, the user A inputs information for specifying the payment delegation request target person (user B) in the input field in the screen. . As a result, the determination at step 119 is affirmed and the routine proceeds to step 120.

  In step 120, the delegation information management unit 12 has buttons 300 and 302 for selecting whether or not to request permission for payment delegation, as shown in FIG. The provided payment delegation request selection screen 304 is distributed to the terminal device 42. As a result, the payment delegation request selection screen 304 is displayed on the display unit 102 of the terminal device 42 operated by the user A.

  In the next step 122, the delegation information management unit 12 determines whether or not permission for payment delegation is requested via the payment delegation request selection screen 304. When the payment delegation request selection screen 304 is displayed on the display unit 102 of the terminal device 42, the user A performs an operation of selecting the button 300 or the button 302. When the user A performs an operation of selecting the button 302 for not requesting permission for payment delegation, the determination in step 122 is denied and the delegation approval acceptance process is terminated.

  On the other hand, when the user B performs an operation of selecting the button 300 for requesting permission for payment delegation, the determination in step 122 is affirmed and the process proceeds to step 124. In step 124, the delegation information management unit 12 registers the request of the user A as information in the delegation permission information table 500 shown in FIG.

  The delegation permission information table 500 has fields of “item number”, “delegation source”, “delegation destination”, “license flag”, and “expiration date”, and information corresponding to each record is set. ing. Information for specifying a requester of payment delegation is set in the “delegation source”, and information for specifying a requester of payment delegation is set in the “delegation destination”. In the “license flag”, “REQ” is set when the license is requested, and “OK” is set when the license is approved. In the “expiration date”, the expiration date of the payment delegation is set. For example, when user A requests user B to grant payment delegation, information specifying user A is set in “delegation source”, and information specifying user B is set in “delegation destination”. Then, “REQ” is set in the “permission flag”, and the expiration date of the payment delegation is set in the “expiration date”.

  In the next step 126, the delegation information management unit 12 transmits to the user B a payment delegation approval request notification mail 602 as shown in FIG. The payment delegation approval request notification mail 602 describes that the user A has requested payment delegation permission. As a result, the user B performs a mail receiving operation and confirms the text of the payment delegation approval request notification mail 602, so that the user B is notified of the payment delegation permission request from the user A. .

  In step 128, the delegation information management unit 12 transmits a payment delegation approval request notification mail 600 as shown in FIG. The payment delegation approval request notification mail 600 describes that the user B has been requested to grant payment delegation. Accordingly, the user A performs a mail receiving operation and confirms the text of the payment delegation approval request notification mail 600, thereby notifying the user A that the user B has been requested to grant the delegation of payment. Further, as shown in FIG. 18, the delegation information management unit 12 distributes a permission request notification screen 306 for notifying the user B that the payment delegation is being requested to the terminal device 42 operated by the user A. To do. As a result, the permission request notification screen 306 is displayed on the display unit 102 of the terminal device 42 operated by the user A.

  By the way, a link 604 to the payment delegation request screen of the product sales website is pasted on the payment delegation approval request notification mail 602 transmitted to the user B. When the user B confirms the text of the approval request notification mail 602 for payment delegation and performs an operation of selecting the link 604, the browser is activated on the terminal device 42 operated by the user B, and the merchandise sales website Access to the payment delegation request screen is performed. With this access as a trigger, a delegation approval permission process shown in FIG.

  In step 130 of the delegation approval permission process, the delegation information management unit 12 distributes the payment delegation request screen 312 shown in FIG. 19 to the terminal device 42 operated by the user B. On the payment delegation request screen 312, the user A is clearly specified as a delegation source, and buttons 308 and 310 for selecting whether or not to grant payment delegation are provided. As a result, the payment delegation request screen 312 is displayed on the display unit 102 of the terminal device 42 operated by the user B.

  In the next step 132, the delegation information management unit 12 determines whether or not payment delegation is permitted via the payment delegation request screen 312. When the payment delegation request screen 312 is displayed on the display unit 102 of the terminal device 42, the user B performs an operation of selecting the button 308 or the button 310. When the user B performs an operation of selecting the button 308 for permitting payment delegation, the determination in step 132 is affirmed and the process proceeds to step 134.

  In step 134, the delegation information management unit 12 records that the delegation of payment has been permitted by the user B by setting “OK” to the “permission flag” of the delegation permission information table 500 (FIG. 10). Further, as shown in FIG. 20, the delegation information management unit 12 distributes a permission notification screen 314 for notifying that payment delegation is permitted to the terminal device 42 operated by the user B, so that the user B operates. The permission notification screen 314 is displayed on the display unit 102 of the terminal device 42.

  In the next step 136, the delegation information management unit 12 transmits a payment delegation completion mail 606 as shown in FIG. 38 to the user A as an example, and a payment delegation completion mail 608 as shown in FIG. 39 as an example. Is transmitted to the user B, and the delegation approval permission process is terminated. The payment delegation completion mails 606 and 608 indicate that the user B has permitted the payment delegation. Accordingly, the user A performs a mail receiving operation and confirms the text of the payment delegation completion mail 606, thereby notifying the user A that the user B has permitted the payment delegation. Further, by confirming the text of the payment delegation completion mail 608 by the user B performing a mail receiving operation, it can be confirmed that the user B himself has permitted the payment delegation.

  On the other hand, when the user B performs an operation of selecting the button 310 for refusing payment delegation in Step 132, the determination in Step 132 is denied and the process proceeds to Step 138. In step 138, the delegation information management unit 12 deletes the record corresponding to the delegation of payment from the user A to the user B in the delegation permission information table 500 (FIG. 10).

  In the next step 140, the delegation information management unit 12 transmits a payment delegation cancellation mail 610 as shown in FIG. 40 to the user A as an example, and as an example, a payment delegation cancellation mail 612 as shown in FIG. Is transmitted to the user B, and the delegation approval permission process is terminated. The payment delegation cancellation e-mail 610 describes that the request for payment delegation has become invalid, and as a reason describes that the requesting party did not approve or that the payment delegation has expired. As a result, the user A performs a mail receiving operation and confirms the text of the payment delegation cancellation mail 610, thereby notifying the user A that the user B has not accepted the payment delegation. Further, the payment delegation cancellation email 612 describes that the payment delegation has been refused. By confirming the text of the payment delegation cancellation mail 612, the user B can confirm that the user B himself has refused the payment delegation.

  Note that an expiration date is set for the payment delegation, and if user B does not select the link 604 pasted on the text of the payment delegation approval request notification email 602 within the expiration date, Delegation expires. The delegation information management unit 12 sends a payment delegation stop mail 610 (FIG. 40) to the user A triggered by the expiration of the payment delegation, and also, as an example, the delegation of payment delegation as shown in FIG. The expired mail 614 is transmitted to the user B.

  The payment delegation cancellation mail 610 and the payment delegation expiration mail 614 indicate that the payment delegation has expired. As a result, the user A performs a mail receiving operation and confirms the text of the payment delegation cancellation mail 610 to notify the user A that the payment delegation has expired. In addition, when the user B performs a mail receiving operation and confirms the text of the payment delegation expired mail 614, the user B is notified that the payment delegation request from the user A has passed the approval deadline. .

  In this embodiment, user B who has granted payment delegation automatically sets a limit amount for automatic payment and performs payment settlement processing in advance, thereby automatically paying the product price below the limit amount. It is possible to make automatic payments.

  When setting automatic payment, the user B first activates a browser on the terminal device 42 and accesses the product sales website by performing an operation such as specifying a URL. Thereby, the homepage of the product sales website is distributed from the electronic commerce server 38 to the terminal device 42 operated by the user B, and the homepage of the product sales website is displayed on the display unit 102. An option for setting automatic payment is displayed on the home page displayed on the display unit 102, and the user B instructs setting of automatic payment by selecting the option. With this operation as a trigger, the automatic payment acceptance process shown in FIG.

  In step 144 of the automatic payment acceptance process, the user management unit 14 stores in the automatic payment information table 502 (see FIG. 11) stored in the automatic payment information storage unit 26 the user B who is the setting instruction source of automatic payment. It is determined whether automatic payment information corresponding to is registered. The automatic payment information table 502 has fields of “item number”, “user information”, “payment method”, “balance” and “payment date”, and information corresponding to each record is set. ing. In the “user information”, information for specifying an automatic payment setting instruction source is set, and in the “payment method”, information for specifying a payment method of funds used for automatic payment is set. In “Balance”, the balance of funds used for automatic payment is set, and in “Payment date”, the payment date of funds used for automatic payment is set.

  If automatic payment information corresponding to the user B is registered in the automatic payment information table 502, the determination in step 144 is affirmed and the process proceeds to step 146. In step 146, the user management unit 14 reads the automatic payment information of the user B from the automatic payment information table 502, and proceeds to step 148. If the automatic payment information corresponding to the user B is not registered in the automatic payment information table 502, the determination in step 144 is negative and the process proceeds to step 148.

  In step 148, the user management unit 14 delivers an automatic payment information registration screen 316 shown in FIG. 21 as an example to the terminal device 42 operated by the user B. Thereby, the automatic payment information registration screen 316 is displayed on the display unit 102 of the terminal device 42 operated by the user B. The automatic payment information registration screen 316 is provided with a radio button 318 for selecting a payment method (payment method) of funds used for automatic payment, an input field 322 for inputting a deposit amount, and instructing the deposit. A button 324 is provided. When automatic payment information corresponding to the user B is registered in the automatic payment information table 502, a character string 320 representing the balance of funds used for automatic payment is also displayed.

  In the next step 150, the user management unit 14 determines whether payment is instructed via the automatic payment information registration screen 316. When the user B sets automatic payment, the user B inputs a deposit amount in the input field 322, selects a payment method (payment method) with the radio button 318, and performs an operation of pressing the button 324. When the operation of selecting the button 324 is performed by the user B, the determination in step 150 is affirmed and the process proceeds to step 152. In step 152, the user management unit 14 performs a deposit settlement process for depositing the deposit amount fund input in the input field 322 using the payment method (payment method) selected by the radio button 318.

  In the next step 154, the user management unit 14 determines whether or not the payment settlement process in step 152 has been normally completed. If the determination in step 154 is affirmed, the process proceeds to step 156. In step 156, the user management unit 14 registers the automatic payment information of the user B in the automatic payment information table 502 or updates the automatic payment information of the user B registered in the automatic payment information table 502. To do. For example, when user B newly deposits with a credit card, information specifying user B is set in “user information”, “credit card” is set in “payment method”, and “balance” is set. The deposit amount is set, and the date of deposit is set in the “deposit date”.

  In the next step 158, the delegation information management unit 12 performs a process of notifying the user B that the deposit process has been completed. That is, as shown in FIG. 22, the delegation information management unit 12 distributes a payment completion notification screen 326 for notifying that the payment process is completed to the terminal device 42 operated by the user B, so that the user B A payment completion notification screen 326 is displayed on the display unit 102 of the terminal device 42 to be operated. Further, the delegation information management unit 12 transmits a payment completion notification mail 616 as shown in FIG. 43 to the user B as an example, and ends the automatic payment acceptance process. The payment completion notification mail 616 describes that the payment process has been completed. As a result, the user B refers to the payment completion notification screen 326 and confirms the text of the payment completion notification email 616 by performing an email reception operation to notify the user B that the payment processing has been completed. .

  On the other hand, if the payment settlement process in step 152 has not been completed normally (if payment has failed), the determination in step 154 is negative and the process proceeds to step 160. In step 160, the user management unit 14 performs a process of notifying the user B that the money could not be deposited. That is, as shown in FIG. 23, the delegation information management unit 12 distributes a payment incomplete notification screen 328 for notifying that payment has failed to the terminal device 42 operated by the user B, so that the user B A payment incomplete notification screen 328 is displayed on the display unit 102 of the terminal device 42 to be operated. Further, the delegation information management unit 12 transmits a payment incomplete notification mail 618 as shown in FIG. 44 to the user B as an example, and ends the automatic payment acceptance process. The incomplete payment notification mail 618 describes that the payment could not be made. As a result, the user B is notified to the user B that payment could not be made by referring to the payment incomplete notification screen 328 and confirming the text of the payment incomplete notification email 618 by performing a mail receiving operation. The

  By the way, when the user A purchases a product sold on the product sales website, the user A starts a browser on the terminal device 42 and accesses a product introduction page introducing individual products on the product sales website. To do. Thereby, the product introduction page is distributed from the electronic commerce server 38 to the terminal device 42 operated by the user A, and the product introduction page is displayed on the display unit 102 of the terminal device 42 operated by the user A. In addition, when the user A desires to purchase the product introduced on the product introduction page displayed on the display unit 102, the user A provides purchase application information including the purchase quantity of the product via the input unit 100 or the like. input.

  Each time the purchase application information is input by the user A, the electronic commerce server 38 registers information on the product for which purchase has been applied by the purchase application information in the shopping cart corresponding to the user A. Then, as shown in FIG. 24 as an example, the electronic commerce server 38 generates a shopping cart display screen 330 representing the contents of the shopping cart, and distributes the generated shopping cart display screen 330 to the terminal device 42 operated by the user A. Perform the process. As a result, the shopping cart display screen 330 is displayed on the display unit 102 of the terminal device 42 operated by the user A.

  The shopping cart display screen 330 displays the product name, status (presence / absence of stock), price, and quantity for all products in the shopping cart. In addition, the shopping cart display screen 330 has a button 334 for paying for the item in the shopping cart by itself and a payment delegation for requesting another user to pay for the item in the shopping cart. A button 332 for performing the above is provided. When the button 334 is selected by the user A, the user A shifts to a normal payment process in which the user A pays for the product. On the other hand, when the button 332 is selected by the user A, the payment delegation acceptance process shown in FIG.

  In step 163 of the payment delegation acceptance process, the shopping cart management unit 16 sets information for identifying the user A as the “delegation source” from the delegation permission information stored in the delegation permission information table 500. Search for delegation permission information. Then, as shown in FIG. 25, a request destination selection screen 336 is generated that displays a user set as a “delegation destination” in the delegation permission information extracted by the search as an option, and the generated request destination selection screen 336 is distributed to the terminal device 42 operated by the user A. Accordingly, the request destination selection screen 336 is displayed on the display unit 102 of the terminal device 42 operated by the user A.

  In the next step 164, the shopping cart management unit 16 determines whether any one of the users displayed as options on the request destination selection screen 336 has been selected as a request destination for payment delegation, Step 164 is repeated until the determination is positive. When the request destination selection screen 336 is displayed on the display unit 102 of the terminal device 42 operated by the user A, the user A requests payment delegation from among the users displayed as options on the request destination selection screen 336. Perform an operation to select a user. When user A performs the operation, the determination in step 164 is affirmed and the process proceeds to step 165.

  In step 165, the shopping cart management unit 16 reads the delegation permission information of the user (user B) selected as the payment delegation request destination from the delegation permission information table 500. In step 166, the shopping cart management unit 16 determines that the read delegation permission information is valid based on whether or not “OK” is set in the “permission flag” of the delegation permission information read in step 165. It is determined whether it is permission information.

  When “REQ” is set in the “permission flag” of the delegation permission information read in step 165, it is determined that it is not valid delegation permission information because the user who has requested payment delegation does not permit payment delegation. Thus, the determination at step 166 is negative. In this case, the process proceeds to step 182, and in step 182, the shopping cart management unit 16 notifies the user A by displaying a screen notifying that the user B does not permit delegation, and the payment delegation acceptance process Exit.

  Further, when “OK” is set in the “permission flag” of the delegation permission information read in step 165, the user who has requested payment delegation has permitted the payment delegation, and valid delegation permission information. And the determination in step 166 is affirmed. In this case, as shown in FIG. 26, a payment requesting screen 338 for notifying that payment is being requested is displayed on the display unit 102 of the terminal device 42 operated by the user A, and the process proceeds to step 168.

  In step 168, the inventory information management unit 18 performs inventory allocation processing. This inventory allocation process will be described with reference to FIG. In step 186 of the inventory allocation process, the inventory information management unit 18 selects the inventory corresponding to the purchase target product in the shopping basket of the user A among the inventory information registered in the inventory information table 504 shown in FIG. Search and read information. The stock information table 504 has fields of “item number”, “product number”, “stock quantity”, “sales flag”, and “sales deadline”, and information corresponding to each record is set. In addition, “OK” is set in the “sales flag” for products that are permitted to be sold, and “NG” is set for products that have been stopped due to lack of inventory or that have passed the date set for “sales due date”. The search for inventory information in step 186 can be realized by using “product number” as a key.

  In the next step 188, the inventory information management unit 18 determines whether or not “OK” is set in the “sales flag” in the inventory information read in step 186. If the determination in step 188 is affirmative, the routine proceeds to step 190. In step 190, the inventory information management unit 18 determines whether or not the “inventory quantity” in the inventory information read in step 186 is greater than or equal to the quantity of products in the user A shopping cart. If the determination in step 190 is affirmed, the process proceeds to step 192. In step 192, the inventory information management unit 18 temporarily reserves the product by registering information on the product in the shopping basket of the user A in the product allocation table 506 shown in FIG. 13.

  The product allocation table 506 includes fields of “item number”, “product number”, “number of allocations”, “allocation destination”, “allocation status”, and “expiration date”. In the product allocation table 506, the number of products in the shopping basket of the user A is set in the “allocation number”, and information for identifying the user A is set in the “allocation destination”. In addition, “RESERVE” is set in the “allocation state” if the product is temporarily secured, and “SOLD” is set if the price of the product has been paid. In step 192, “RESERVE” is set in the “allocation state”. "Is set. In addition, the “expiration date” is set with an expiration date (a date after a certain number of days have elapsed from the current date) for temporarily securing the product.

  In the next step 194, the inventory information management unit 18 reduces the “inventory number” in the inventory information of the temporarily reserved products registered in the inventory information table 504 by the “allocation number” of the temporarily reserved products. Then, the inventory information of the temporarily secured product is updated. In the next step 196, the inventory information management unit 18 notifies the fact that the allocation of inventory has been successful with an end code, and ends the inventory allocation process.

  On the other hand, if the determination in step 188 or 190 is negative, the process proceeds to step 198. In step 198, the inventory information management unit 18 notifies the fact that the allocation of inventory has failed with an end code, and the inventory allocation process Exit.

  When the above-described inventory allocation process ends, the process proceeds to step 170 of the payment commission acceptance process. In step 170, the shopping cart management unit 16 determines whether or not the inventory has been allocated based on the end code notified from the inventory allocation process. If the end code notified from the inventory allocation process is an end code notifying that allocation of inventory has been successful, the determination at step 170 is affirmed and the routine proceeds to step 172.

  In step 172, the shopping cart management unit 16 issues an identification key for identifying individual payments, and performs shopping for each item in the shopping cart with respect to the shopping cart shared information table 508 shown in FIG. Record the shared information of the basket. The shopping cart shared information table 508 includes fields of “item number”, “share source”, “share destination”, “identification key”, “product number”, and “status flag”. The “status flag” in the shopping cart shared information table 508 includes “waiting for payment” at the time of payment request, “paid” if paid, and “payment rejected” when payment is denied. Is set.

  In step 172, in the shopping cart shared information table 508, information for specifying the user A is set in the “share source”, information for specifying the user B is set in the “share destination”, and issued to the “identification key”. Is set, and the product number of the product to be paid is set in “product number”. In the shopping cart shared information table 508, “waiting for payment” is set in the “status flag”.

  In step 174, the shopping cart management unit 16 sets a flag indicating that the contents of the shopping cart shared information table 508 are locked. By setting this flag, the user B is prohibited from changing the contents of the shopping cart shared information table 508.

In step 176, the shopping cart management unit 16 indicates that the shopping cart of the user A (the shopping cart sharing information table 508) is shared between the user A and the user B. Set.

  In step 178, the shopping cart management unit 16 transmits an email notifying that the payment request has been made to the users A and B. That is, as shown in FIG. 45 as an example, a payment request notification mail 620 describing that a payment request has been made to the user B is transmitted to the user A. As a result, the user A performs a mail receiving operation and confirms the text of the payment request notification mail 620 to notify the user A that the payment request has been made to the user B.

  As an example, as shown in FIG. 46, a payment request notification mail 622 describing that the payment is requested is transmitted to the user B. Accordingly, the user B performs a mail receiving operation and confirms the text of the payment request notification mail 622, thereby notifying the user B that the payment is requested. Further, a link 624 for jumping to a screen for making payment according to the request is pasted on the payment request notification mail 622. User B can jump to a screen for making a payment by selecting link 624 provided in payment request notification mail 622.

  On the other hand, if the end code notified from the inventory allocation process is an end code notifying that allocation of inventory has failed, the determination in step 170 is negative and the routine proceeds to step 180. In step 180, as shown in FIG. 27, the shopping cart management unit 16 cannot operate the inventory allocation failure screen 340 for notifying that the payment request cannot be accepted because the inventory of the product cannot be secured. 42 are displayed on the display unit 102. Thereby, the user A can recognize that the stock of the product could not be secured.

  Next, the payment process activated by the electronic commerce server 38 when the user B selects the link 624 provided in the payment request notification mail 622 will be described with reference to FIG. In step 202, as shown in FIG. 28 as an example, the shopping cart management unit 16 generates a shopping cart display screen 342 that displays the contents of the shopping cart of the user A, and uses the generated shopping cart display screen 342 as the user. B is displayed on the display unit 102 of the terminal device 42 operated by B. The shopping cart display screen 342 displays the product name, status (presence / absence of inventory), price, and quantity for all the products in the shopping cart. The shopping cart display screen 342 displays a message notifying that there is a request for payment, and buttons 344 and 346 for selecting whether or not to pay are provided.

  In the next step 204, the settlement processing unit 22 tries to read the automatic payment information of the user B registered in the automatic payment information table 502. In the next step 206, the settlement processing unit 22 determines whether valid automatic payment information of the user B exists. When valid automatic payment information of user B can be read, the determination in step 206 is affirmed and the routine proceeds to step 208. In step 208, the settlement processing unit 22 determines whether or not the amount set in the “balance” in the read automatic payment information is equal to or greater than the payment commission amount requested by the user A.

  If the determination in step 208 is affirmed, the process proceeds to step 210, and automatic payment processing is performed after step 210. In step 210, the settlement processing unit 22 executes the payment process without waiting for the user B's payment operation. That is, the “allocation state” of the corresponding record in the product allocation table 506 is changed from “RESERVE” to “SOLD”. In the next step 212, the user management unit 14 reduces the “balance” in the automatic payment information of the user B registered in the automatic payment information table 502 by the product price.

  If the process of step 212 is performed, it will transfer to step 220, and the shopping cart management part 16 will change the "status flag" of the shopping cart shared information table 508 from "waiting for payment" to "paid" in step 220. In the next step 222, the settlement processing unit 22 records the payment delegation detail information of the user B in the payment delegation payment detail table 510 stored in the detail information storage unit 32. As shown in FIG. 15, the payment delegation payment details table 510 includes “item number”, “payer”, “purchase date”, “item number”, “payment amount”, “delegator”, and “payment delegation date”. "Each field is provided. Information specifying the user B is set in the “payer”, information specifying the user A is set in the “delegator”, and the price of the product is set in the “payment amount”.

  In step 224, the settlement processing unit 22 transmits an email notifying that the payment has been completed to the users A and B. That is, as an example, a payment completion notification mail 626 as shown in FIG. As a result, the user A performs a mail receiving operation and confirms the text of the payment completion notification mail 626 to notify the user A that the payment by the user B has been made. Further, the settlement processing unit 22 displays the payment completion screen 352 shown in FIG. 30 on the display unit 102 of the terminal device 42 operated by the user B.

  Further, as an example, a payment completion notification mail 628 as shown in FIG. Accordingly, the user B performs a mail receiving operation and confirms the text of the payment completion notification mail 628, thereby notifying the user B that the payment is completed. Also, a link 630 for jumping to a screen for confirming payment details is pasted on the payment completion notification mail 628. User B can jump to the payment details display screen 362 shown in FIG. 33 by selecting the link 630 provided in the payment completion notification mail 628.

  If there is no valid automatic payment information for user B or valid automatic payment information for user B, but the “balance” is less than the commission amount, step 206 or The determination at step 208 is negative, and the routine proceeds to step 214. In step 214, the settlement processing unit 22 determines whether or not any operation has been performed by the user B, and repeats step 214 until the determination is affirmed.

  When the automatic payment process based on the automatic payment information is not performed, the user B performs an operation of selecting the button 344 or the button 346 while the shopping cart display screen 342 illustrated in FIG. 28 is displayed. When the button 344 is selected, the electronic commerce server 38 displays a payment method selection screen 348 (FIG. 29) in which a plurality of types of payment methods are displayed as options and a button 350 for confirming the payment method is provided. It is displayed on the display unit 102 of the terminal device 42 operated by the user B. Thereby, the user B performs an operation of selecting a payment method via the payment method selection screen 348.

  When the above operation is performed by the user B, the determination in step 214 is affirmed, and the process proceeds to step 216. In step 216, the settlement processing unit 22 determines whether or not the payment is instructed by the user B and the payment method is selected. When the operation for selecting the button 344 is performed by the user B while the shopping cart display screen 342 is displayed, and the operation for selecting the payment method is performed via the payment method selection screen 348, The determination is affirmed and the routine proceeds to step 218.

  In step 218, the settlement processing unit 22 executes a payment process. That is, the “allocation state” of the corresponding record in the product allocation table 506 is changed from “RESERVE” to “SOLD”. Moreover, the process for paying the price for the merchandise by the payment method selected by the user B is performed. If the process of step 218 is performed, it will transfer to step 220 and the process of step 220-step 224 mentioned above will be performed.

  On the other hand, when the user B performs an operation of selecting the button 346 while the shopping cart display screen 342 is displayed, the determination in step 216 is denied and the process proceeds to step 226. In step 226, the reason notifying unit 20 operates the reason input screen 354 (see FIG. 31) in which the input field 356 for inputting the reason for rejecting the payment by selecting the button 346 is operated by the user B. It is displayed on the display unit 102 of the terminal device 42.

  In the next step 228, the settlement processing unit 22 determines whether or not a reason for refusing payment is input in the input field 356 of the reason input screen 354, and repeats step 228 until the determination is affirmed. When the user B refuses payment, the user B operates the input unit 100 to input the reason for payment refusal. When the input is completed, the button 358 in the reason input screen 354 is selected, so that the determination in step 228 is affirmed, and the process proceeds to step 230. In step 230, the shopping cart management unit 16 deletes the correspondence information registered in the shopping cart sharing information table 508, thereby performing processing for canceling the sharing of the shopping cart between the user A and the user B. .

  In the next step 232, the inventory information management unit 18 deletes information on the product temporarily reserved for the user A by registering in the product allocation table 506 from the product allocation table 506. In addition, the inventory information management unit 18 increases the “inventory number” in the inventory information of the temporarily reserved product registered in the inventory information table 504 by the “reserved number” of the temporarily secured product. As a result, the temporarily reserved product is returned to stock.

  In step 234, the reason notifying unit 20 transmits an email notifying the users A and B together with the reason why the user B has input that the user B has refused to pay. That is, as an example, a payment refusal notification mail 630 as shown in FIG. Thereby, the user A performs a mail receiving operation and confirms the text of the payment rejection notification mail 630, so that the payment by the user B is rejected and the reason thereof is notified to the user A. Also, as an example, a payment rejection notification mail 632 as shown in FIG. Accordingly, the user B performs a mail receiving operation and confirms the text of the payment rejection notification mail 632 to notify the user B that the payment is rejected.

  Further, as shown in FIG. 32, a payment rejection notification screen 360 for notifying that the payment request has been declined is displayed on the display unit 102 of the terminal device 42 operated by the user B. User B can confirm that he / she has refused the payment by referring to the payment rejection notification screen 360.

  On the other hand, when the user A receives the payment completion notification mail 626, the user A starts a browser on the terminal device 42 and performs an operation such as specifying a URL, and then follows the link after accessing the product sales website. To access your shopping cart. As a result, the shopping cart display screen 364 shown in FIG. 34 is displayed on the display unit 102 of the terminal device 42 operated by the user A. The shopping cart display screen 364 is provided with a button 366 for selecting a delivery method. When the user A selects the button 366, a delivery method selection screen in which a plurality of delivery methods are displayed as options is displayed. Is done. When the user A selects a delivery method via the delivery method selection screen, the electronic commerce server 38 executes the order process shown in FIG.

  In step 240 of the order processing, the shopping cart management unit 16 cancels sharing of the shopping cart between the user A and the user B by deleting the correspondence information registered in the shopping cart sharing information table 508. Process. In the next step 242, the settlement processing unit 22 performs order processing for shipping the product ordered from the user A by the delivery method selected by the user A.

  In step 244, the settlement processing unit 22 records the purchase details information of the user A in the purchase details table 512. The purchase details table 512 includes fields of “item number”, “purchaser”, “purchase date”, “product number”, “purchase amount”, “payer”, and “payment date”. Information corresponding to each field is set. In step 246, a purchase details screen 368 as shown in FIG. 35 is displayed on the display unit 102 of the terminal device 42 operated by the user A. Thereby, the user A can confirm the purchase details.

  As described above, in the present embodiment, the user B is inquired about whether or not to accept payment delegation for delegating payment for the product purchased by the user A to the user B, and the payment delegation is permitted by the user B. The delegation permission information is stored in the delegation permission information table 500. Further, for the product purchased by the user A, when the payment by the user B is requested from the user A and the delegation permission information corresponding to the delegation permission information table 500 is stored, the name and quantity of the product to be purchased And a list of shopping carts with the price written is presented to user B. Then, the user B is requested to pay. Further, when the user B instructs to pay for the product whose name, quantity, and price are listed in the shopping cart list, a settlement process is performed to settle the price of the product with the funds of the user B.

  This makes it possible to prevent malicious users from requesting payment of other arbitrary users because they request payment after taking the payment delegation procedure in advance. , The safety of e-commerce is ensured. It is also possible for users who are in a relationship other than family relationships. Furthermore, since the payer only has to pay for the products already in the shopping cart list, the payer's burden is reduced as compared with the case where the payer performs the operation of putting the products into the shopping cart. E-commerce can be realized.

  In the present embodiment, when automatic payment setting is instructed and the automatic payment limit amount in the payment delegation is input from the user B, the automatic payment information including the input limit amount is displayed in the automatic payment information table 502. Remember me. For the product purchased by user A, payment by user B is requested by user A, delegation permission information is stored in delegation permission information table 500, and the price of the product is stored in automatic payment information table 502. When the amount is below the limit included in the information, the following processing is performed. That is, without waiting for an instruction from the user B, the payment for the product is settled with the funds of the user B, and a settlement process for updating the limit included in the automatic payment information is performed. Thereby, payment of the goods whose price is below the limit can be realized without bothering the user B who makes the payment.

  Further, in the present embodiment, when the user A requests payment by the user A for the product purchased by the user A, the stock information table 504 is the same as the quantity described in the shopping cart list. Is reduced from. In addition, a process of temporarily securing the product is performed by registering the product in a provisionally secured state in the product allocation table 506 in the quantity indicated in the shopping cart list. Accordingly, it is possible to prevent the product B from being out of stock at the timing when the user B pays for the product.

  In the present embodiment, when the shopping cart list is displayed on the display unit 102 of the terminal device 42 operated by the user B, the shopping cart list is locked, and the shopping cart list is changed by the user B. It is prohibited. Thereby, it is possible to prevent the shopping cart list from being inadvertently changed by the user B.

  Further, in the present embodiment, when the payment of the price of the product listed in the shopping cart list is rejected by the user B, the reason input screen 354 for inputting the reason for rejecting the payment is displayed on the display unit 102. It is displayed. And the reason of the payment refusal input via the reason input screen 354 is notified to the user A. Thereby, even when the payment is rejected by the user B, the user A can recognize the reason for the payment rejection.

  In addition, although the above demonstrated the case where one user B received payment commission from the user A per shopping cart, the same user for each product in which several users are in the shopping cart You may make it receive payment commission from. In this aspect, when making a payment request, the shopping cart display screen 380 shown in FIG. 51 can be displayed instead of the shopping cart display screen 330 shown in FIG. In the shopping cart display screen 380, a payment delegation destination can be selected for each product unit in the shopping cart. Listed as a choice. By selecting a desired user from among the users displayed in a list with each product as a unit, it becomes possible to change the payment delegation destination for each product.

  In addition, although the case where the payment settlement process is actually performed at the time of registration of the automatic payment information is described above, only the limit amount is registered at the time of registration of the automatic payment information, and the user A is requested to settle the product price. In this case, the payment settlement process may be performed.

  In the above description, the case of purchasing a product has been described as an example. However, the present invention can also be applied to a case where payment is made after receiving a service.

  In the above description, the purchase service providing program 64, which is an example of the purchase service providing program according to the disclosed technology, is stored (installed) in the storage unit 48 in advance. However, the present invention is not limited to this. The purchase service providing program according to the disclosed technology can be provided in a form recorded on a recording medium such as a CD-ROM or a DVD-ROM.

  All documents, patent applications and technical standards mentioned in this specification are to the same extent as if each individual document, patent application and technical standard were specifically and individually stated to be incorporated by reference. Incorporated by reference in the book.

  Regarding the above embodiment, the following additional notes are disclosed.

(Appendix 1)
When the first user asks the second user whether or not to accept the payment delegation for delegating payment for the goods or services purchased by the first user to the second user, and the payment delegation is granted by the second user A delegation information management unit for storing delegation permission information in the storage unit;
When the product or service purchased by the first user is requested by the first user for payment by the second user and the delegation permission information corresponding to the storage unit is stored, A list of shopping carts describing at least the name and price of goods or services purchased by the first user is displayed on a display device referred to by the second user, and the second user is requested to pay. Shopping cart management department,
When the second user has instructed to pay for a product or service whose name and price are listed in the shopping cart list displayed on the display device, the product is funded by the second user. Or a payment processing unit that performs a payment process for payment for the service;
A purchase service providing device.

(Appendix 2)
A user management unit for storing automatic payment information including the input limit amount in the storage unit when a limit amount of automatic payment in the payment delegation is input from the second user;
The settlement processing unit is requested by the first user to make a payment for the product or service purchased by the first user from the first user, and the delegation permission information corresponding to the storage unit is stored. And the second use without waiting for an instruction from the second user when the price of the product or service is less than or equal to the limit included in the automatic payment information stored in the storage unit The purchase service providing apparatus according to supplementary note 1, wherein payment for the product or service is settled with a person's funds and a settlement process is performed to update a limit included in the automatic payment information.

(Appendix 3)
In the shopping cart list, the name, quantity and price of the product purchased by the first user are described,
For the product purchased by the first user, when the payment by the second user is requested by the first user, the quantity of the product is stored in the inventory information table by the amount described in the shopping cart list. Or an inventory information management unit that performs a process of temporarily securing the product by registering the product in a provisionally secured state in the product allocation table by the quantity described in the shopping cart list. The purchase service providing apparatus according to attachment 2.

(Appendix 4)
The shopping cart management unit prohibits the second user from changing the shopping cart list when displaying the shopping cart list on a display device referred to by the second user. The purchase service providing apparatus according to any one of supplementary notes 1 to 3, wherein the list is locked.

(Appendix 5)
A reason input screen for inputting a reason for refusing payment when the second user refuses to pay for the goods or services listed in the shopping cart list displayed on the display device; The purchase service according to any one of appendix 1 to appendix 4, further comprising a reason notifying unit which is displayed on a display device and notifies the first user of the reason for payment refusal input via the reason input screen. Providing device.

(Appendix 6)
There are a plurality of the second users whose delegation permission information is stored in the storage unit by the delegation information management unit,
The list display processing unit displays a list of the shopping carts on a display device referred to by the second user selected by the first user among the plurality of second users, and the selected first 2. The purchase service providing apparatus according to any one of appendix 1 to appendix 5, which requests payment from a user.

(Appendix 7)
When the first user asks the second user whether or not to accept the payment delegation for delegating payment for the goods or services purchased by the first user to the second user, and the payment delegation is granted by the second user The delegation permission information is stored in the storage unit,
When the product or service purchased by the first user is requested by the first user for payment by the second user and the delegation permission information corresponding to the storage unit is stored, A list of shopping carts describing at least the name and price of goods or services purchased by the first user is displayed on a display device referred to by the second user, and the second user is requested to pay. ,
When the second user has instructed to pay for a product or service whose name and price are listed in the shopping cart list displayed on the display device, the product is funded by the second user. Alternatively, a method for providing a purchase service including performing a payment process for payment for the service.

(Appendix 8)
When the limit amount of automatic payment in the payment delegation is input from the second user, the storage unit stores automatic payment information including the input limit amount;
For the product or service purchased by the first user, payment by the second user is requested by the first user, the delegation permission information corresponding to the storage unit is stored, and the product Alternatively, when the price of the service is equal to or less than the limit amount included in the automatic payment information stored in the storage unit, the product is funded by the second user without waiting for an instruction from the second user. Alternatively, the purchase service providing method according to appendix 7, wherein the payment for the service is settled and a settlement process is performed to update a limit included in the automatic payment information.

(Appendix 9)
In the shopping cart list, the name, quantity and price of the product purchased by the first user are described,
For the product purchased by the first user, when the payment by the second user is requested by the first user, the quantity of the product is stored in the inventory information table by the amount described in the shopping cart list. The purchase service providing method according to appendix 7 or appendix 8, wherein a process of temporarily securing the product is performed by registering the product in a provisionally secured state in the product allocation table by the quantity described in the shopping cart list .

(Appendix 10)
Supplement 7 for locking the shopping cart list by prohibiting the second user from changing the shopping cart list when displaying the shopping cart list on a display device referred to by the second user. The purchase service providing method according to any one of to appendix 9.

(Appendix 11)
A reason input screen for inputting a reason for refusing payment when the second user refuses to pay for the goods or services listed in the shopping cart list displayed on the display device; 11. The purchase service providing method according to any one of appendix 7 to appendix 10, wherein the purchase service is displayed on a display device and notifies the first user of the reason for payment refusal input via the reason input screen.

(Appendix 12)
There are a plurality of second users whose delegation permission information is stored in the storage unit,
A list of the shopping carts is displayed on a display device referred to by the second user selected by the first user among the plurality of second users, and payment is made to the selected second user. The purchase service providing method according to any one of appendix 7 to appendix 11, wherein the purchase service is requested.

(Appendix 13)
On the computer,
When the first user asks the second user whether or not to accept the payment delegation for delegating payment for the goods or services purchased by the first user to the second user, and the payment delegation is granted by the second user The delegation permission information is stored in the storage unit,
When the product or service purchased by the first user is requested by the first user for payment by the second user and the delegation permission information corresponding to the storage unit is stored, A list of shopping carts describing at least the name and price of goods or services purchased by the first user is displayed on a display device referred to by the second user, and the second user is requested to pay. ,
When the second user has instructed to pay for a product or service whose name and price are listed in the shopping cart list displayed on the display device, the product is funded by the second user. Or a purchase service providing program for performing processing including performing settlement processing for settlement of the price of the service.

(Appendix 14)
When the limit amount of automatic payment in the payment delegation is input from the second user, the storage unit stores automatic payment information including the input limit amount;
For the product or service purchased by the first user, payment by the second user is requested by the first user, the delegation permission information corresponding to the storage unit is stored, and the product Alternatively, when the price of the service is equal to or less than the limit amount included in the automatic payment information stored in the storage unit, the product is funded by the second user without waiting for an instruction from the second user. Or the purchase service provision program of Additional remark 13 which performs the payment process which settles the price for a service and updates the limit included in automatic payment information.

(Appendix 15)
In the shopping cart list, the name, quantity and price of the product purchased by the first user are described,
For the product purchased by the first user, when the payment by the second user is requested by the first user, the quantity of the product is stored in the inventory information table by the amount described in the shopping cart list. 15. The purchase service providing program according to appendix 13 or appendix 14, wherein the product is temporarily reserved in the product allocation table by registering the product in the product allocation table by the quantity described in the shopping cart list. .

(Appendix 16)
Supplementary note 13 for locking the shopping cart list by prohibiting the second user from changing the shopping cart list when displaying the shopping cart list on a display device referred to by the second user. The purchase service providing program according to any one of to Appendix 15.

(Appendix 17)
A reason input screen for inputting a reason for refusing payment when the second user refuses to pay for the goods or services listed in the shopping cart list displayed on the display device; The purchase service providing program according to any one of supplementary notes 13 to 16, which is displayed on a display device and notifies the first user of the reason for payment refusal input via the reason input screen.

(Appendix 18)
There are a plurality of second users whose delegation permission information is stored in the storage unit,
A list of the shopping carts is displayed on a display device referred to by the second user selected by the first user among the plurality of second users, and payment is made to the selected second user. The purchase service providing program according to any one of appendix 13 to appendix 17, which requests

DESCRIPTION OF SYMBOLS 10 Purchase service provision apparatus 12 Delegation information management part 14 User management part 16 Shopping basket management part 18 Inventory information management part 20 Reason notification part 22 Settlement processing part 24 Delegation information storage part 26 Automatic payment information storage part 28 Shopping basket shared information storage Unit 30 Inventory information storage unit 32 Detailed information storage unit 36 Electronic commerce system 38 Electronic commerce server 40 Network 42 Terminal device 44 CPU
46 memory 48 storage unit

Claims (6)

When receiving the designation of the product or service from the first user and the designation of the second user as the destination to request payment of the price of the product or service, Send a payment request,
Notifying the first user of the rejection of the request when detecting a rejection of the request, and notifying the second user of the rejection of the request;
A payment request service providing program for causing a computer to execute processing. When receiving the designation of the product or service from the first user and the designation of the second user as the destination to request payment of the price of the product or service, Send a payment request,
Notifying the first user of the rejection of the request when detecting a rejection of the request, and notifying the second user of the rejection of the request;
Payment request service providing method characterized that you execute processing computer. When receiving the designation of the product or service from the first user and the designation of the second user as the destination to request payment of the price of the product or service, It sends a request for payment of the price, when detecting a denial of the said request, and notifies a rejection of the request to the first user, the request to the second user An apparatus for providing a payment request service, characterized by comprising a management unit for notifying that a rejection has occurred . When receiving a request for requesting the second user to pay for the goods or services desired by the first user from the first terminal device, the request is transmitted to a destination corresponding to the second user;
When receiving the rejection of the request from the terminal device corresponding to the second user, it notifies both the first user and the second user,
A payment proxy request service providing program characterized by causing a computer to execute processing. When receiving a request for requesting the second user to pay for the goods or services desired by the first user from the first terminal device, the request is transmitted to a destination corresponding to the second user;
When receiving the rejection of the request from the terminal device corresponding to the second user, it notifies both the first user and the second user,
A payment proxy request service providing method, wherein a computer executes processing .   When receiving a request for requesting the second user to pay for the goods or services desired by the first user from the first terminal device, the request is transmitted to a destination corresponding to the second user; A payment proxy request service comprising a management unit for notifying both the first user and the second user when receiving a rejection of the request from a terminal device corresponding to the second user Providing device.