JP2023141543A - Method for selling online, sale management server, and program - Google Patents

Abstract

To provide a method for selling online that can reduce burden on a salesperson and also can reduce risks of leakage of user settlement information from a management server.SOLUTION: In the method for selling online according to an embodiment of the present invention, the processing of the settlement when a sale target (a product or a service) is being sold or bought is all completed between a user terminal, a management server, and a settlement server and does not involve a salesperson terminal. The burden on the salesperson can be thus reduced. The management server deletes temporarily stored user settlement information after the settlement server completes settlement processing. This can reduce or eliminate the risk of leakage of the user settlement information from the management server.SELECTED DRAWING: Figure 6

Description

TECHNICAL FIELD The present invention generally relates to a method of online mail order sales, and more particularly to a method of selling content, etc. online.

2. Description of the Related Art Online shopping services have been widely used in the past that allow products (including content) or services to be purchased by using communication networks. In such conventional online shopping services, there are various problems in various aspects such as user authentication, credit check, and product payment, and various improvements have been made to date.

For example, an order payment system has been proposed in which a payment institution acts as an intermediary in online shopping and authenticates the seller and the purchaser, thereby allowing the seller and the purchaser to conduct transactions safely (Patent Document 1).

That is, the system disclosed in Patent Document 1 is used in online shopping where a seller's server and a purchaser's information device are connected via a communication network to purchase products, services, information, etc., and a payment institution is connected to the communication network. server is connected, the purchaser's information device searches the sales information on the seller's server, creates purchase information such as necessary products, services, information, etc., and sends the purchase information to the payment institution. The server of the payment institution receives the purchase information sent by the purchaser and checks the purchaser's credit rating prepared in advance. The present invention is characterized by comprising means for transmitting order information to the server of the seller only when the purchase is possible by referring to the information of the seller.

In addition, an electronic commerce method that prevents accidents and reduces risks in deferred payment electronic commerce has been proposed (Patent Document 2).

In other words, Patent Document 2 discloses that order data including price information for goods or services provided from a seller to a purchaser, and personal information including purchaser identification information given to the purchaser in advance, are stored in the purchaser. the payment information included in the order data and the purchaser's personal information included in the purchaser's personal information; and before the goods or services are provided to the purchaser. a payment acceptability determination process that determines whether or not to pay the price for the product or service to the seller on behalf of the purchaser based on the identification information; When it is decided to make a payment on behalf of the purchaser, payment information transmission processing is performed in which payment permission information indicating the payment is sent to a terminal used by the seller, with the purchaser identification information hidden. An electronic commerce method is disclosed.

Furthermore, a safe credit card payment method has been proposed that prevents theft of credit card information in electronic commerce via the Internet (Patent Document 3).

In other words, in Patent Document 3, credit card information is divided by a division process at the time of user registration, the original is discarded as two pieces of divided information, and one piece of the divided information is transferred to the user's information terminal device. The remaining piece of divided information is stored in the information device of the depository center, and at the time of payment, the settlement center stores the remaining piece of divided information stored in the user's information terminal device and the information device of the depository center. A credit card payment method on the Internet is disclosed, which is characterized in that credit card information is restored by acquiring one piece of stored divided information and combining the two pieces of information and using the restored credit card information for credit and payment processing.

Japanese Patent Application Publication No. 2002-63532 Japanese Patent Application Publication No. 2003-44775 Japanese Patent Application Publication No. 2007-41957

However, in the technologies disclosed in Patent Documents 1 to 3, for example, user registration for the system (so-called member registration) is required, and due to the need to manage users' personal information and payment information, these It could not be said that the handling of important information regarding users was not always perfect, as there was a risk of important information being leaked.

In Patent Document 3, at the time of user registration, credit card information is divided into two parts on the deposit center information device 3 or the user terminal 1, the original is discarded, one part of the divided information is stored in the user terminal 1, and the other part is stored in the user terminal 1. is stored in the deposit center information device 3. At the time of payment, the payment center 4 obtains the division information stored in the user terminal 1 and the division information stored in the deposit center information device 3, and combines the two to restore credit card information and issue credit. It is used for payment processing. However, the user is required to register with the depository center, and the operator of the depository center information device, which has a connection with the user and can know the user information, may collect some of the user's payment information. There is still room for further improvement.

In addition, for users themselves, it is important to configure transaction flows so that they can clearly understand how important information such as their payment information will be handled by the operator, etc. as the sales contract process progresses. desired.

Therefore, an online sales method according to an embodiment of the present invention includes a user terminal used by a user who is a purchaser of a product or service, a seller terminal used by a seller of the product or service, and a user terminal used by the seller of the product or service. An online sales method executed by an online sales system having a management server that manages sales of the product or the service, and a payment server that manages payment for the sale of the product or service, the product or service being sold. a sales target information sending step of transmitting sales target information from the seller terminal to the management server; and registering the sales target information received from the seller terminal in the management server and transmitting the sales target information from the user terminal to the management server. a step of registering the information to be sold to make it viewable; a viewing request sending step of transmitting a viewing request for the information to be sold from the user terminal to the management server; and a step of transmitting a viewing request for viewing the information to be sold, which is the information to be sold in response to the viewing request. , a viewing information transmitting step of transmitting the viewing information from the management server to the user terminal, a viewing information outputting step of outputting the viewing information at the user terminal, and a viewing information outputting step of outputting the viewing information to the user terminal, and transmitting a purchase request for the sales object selected from the viewing information to the user. A purchase request sending step of transmitting the purchase request from the terminal to the management server, a purchase request registration step of registering the purchase request in the management server, and an input of user payment information necessary for payment corresponding to the purchase request from the user terminal. a step of inputting user payment information received from the user terminal; a temporary storage step of user payment information transmitting the user payment information from the user terminal to the management server and temporarily storing it in the management server; a payment request step of transmitting the transfer destination information of the amount and the user payment information from the management server to the payment server; and the payment server makes the payment based on the payment amount, the transfer destination information and the user payment information. a payment processing step for performing processing; a payment processing completion notification step for notifying the management server from the payment server of the completion of the payment processing; and a user payment step for deleting the user payment information temporarily stored in the management server. The method is characterized by comprising an information deletion step, and a user payment information deletion notification step of notifying the user terminal from the management server of the deletion of the temporarily stored user payment information and outputting it from the user terminal.

According to one embodiment of the present invention, the payment process for buying and selling a sales object (product or service) is completed between the user terminal, the management server, and the payment server, and the seller terminal is not involved. Therefore, the burden on the seller side can be reduced. Furthermore, the management server deletes the temporarily stored user payment information after the payment processing at the payment server is completed. This makes it possible to reduce or eliminate the risk of user payment information leaking from the management server.

In addition, before the step of inputting user payment information, a step of requesting prior consent is performed, in which the management server sends, to the user terminal, an explanation of the purchase guidelines for the sales object and a request for consent to the purchase guidelines; a consent receiving step of receiving the consent from the user at a user terminal; a consent sending step of transmitting the consent from the user terminal to the management server; and transmitting the user payment information from the management server to the user terminal. The method may further include a step of requesting transmission of user payment information.

Thereby, the purchase procedure can be explained to the user, and the payment process can be started after obtaining the user's consent. Therefore, it is possible to improve the user's sense of satisfaction.

Further, after the payment processing completion notification step, the management server may further include a sales completion notification step of transmitting sales completion information, which is information regarding the sales object for which the payment processing has been completed, to the seller terminal. good.
This allows the seller to know the sales completion information at the stage when the payment is completed.

Further, before the sales target information sending step, a step of requesting the creation of a seller account for the management server from the seller terminal to the management server, and a step of requesting the creation of a seller account for the management server; , a step of creating a seller account for the management server to create a seller account for the management server, an account information requesting step of transmitting an input request for seller account information for remittance from the management server to the seller terminal, a seller account information sending step of receiving the remittance seller account information at the seller terminal and transmitting a payment server seller account application simultaneously or separately from the seller terminal to the management server; a payment server seller account creation request step of transmitting the remittance seller account information and the payment server seller account application to the payment server; a payment server merchant account creation step of creating a payment server merchant account based on a payment server merchant account application; and a payment server merchant account creation step of transmitting the payment server merchant account from the payment server to the management server. The method may include a seller account sending step, and an account linking step of linking and registering the management server seller account information and the payment server seller account in the management server.

As a result, the payment server merchant account managed by the payment server can also be managed on the management server (for example, the management server can identify the seller who is the remittance destination for payment and notify the payment server). ) becomes possible.

According to the online sales method and the like according to an embodiment of the present invention, it is possible to reduce the burden on the seller side, and also to reduce or eliminate the risk of user payment information leaking from the management server. play.

FIG. 1 is an explanatory diagram illustrating an example of the overall configuration of an online sales system according to an embodiment of the present invention. FIG. 2 is an explanatory diagram illustrating a functional block configuration of a management server and a payment server in an online sales system according to an embodiment of the present invention. FIG. 1 is an explanatory diagram illustrating an example of the external configuration of an information processing device (user terminal) in an online sales system according to an embodiment of the present invention. FIG. 1 is an explanatory diagram illustrating a functional block configuration of hardware that constitutes an information processing device (user terminal) according to an embodiment of the present invention. FIG. 2 is an explanatory diagram illustrating the flow of processing operations in the online sales system according to an embodiment of the present invention. FIG. 2 is an explanatory diagram illustrating the flow of processing operations in the online sales system according to an embodiment of the present invention. It is a flowchart explaining the processing operation flow in the online sales system according to another embodiment of the present invention. It is a flowchart explaining the processing operation flow in the online sales system according to another embodiment of the present invention. It is a flowchart explaining the processing operation flow in the online sales system according to another embodiment of the present invention. FIG. 2 is a diagram illustrating a display example of an information processing device (store terminal) in an online sales system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a display example of an information processing device (user terminal) in an online sales system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a display example of an information processing device (user terminal) in an online sales system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a display example of an information processing device (user terminal) in an online sales system according to an embodiment of the present invention.

Hereinafter, an online sales method and the like according to an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 shows an example of the overall configuration of an online sales system according to an embodiment of the present invention.

As shown in FIG. 1, the online sales system 10 in one embodiment includes a payment server 11, a management server 12, store terminals 13a to 13c, and an information processing device (in the same figure) as a user terminal. For example, a PC 14, a notebook PC 15, a mobile information terminal, a smartphone, or a tablet terminal 16 to 18 are shown. It consists of As shown in FIG. 1, the payment server 11, management server 12, store terminals 13a to 13c, and various terminals are connected to each other through a private line or a public line such as the Internet (19 as a wired line) so that they can communicate with each other. ing. Further, the line may be wired or wireless, and in the case of wireless, the store terminals 13a to 13c and various terminals 14 to 18 connect to the Internet 19 wirelessly via a base station or access point (not shown). , payment server 11 and/or management server 12 so as to be able to communicate with each other.

Here, the access point is a wireless device that connects wireless terminals such as PCs and smartphones to each other or to other networks. Typically, a radio such as an access point is a device that operates on Layer 1 (Physical Layer) and Layer 2 (Data Link Layer) communication protocols in the OSI reference model.

Furthermore, many smartphones, personal digital assistants, and tablets at the time of filing this application have processing capabilities (communication processing speed, image processing capability, etc.) equivalent to personal computers (PCs), and are also referred to as small computers. It is something that should be done.

Further, the programs or software necessary for carrying out the present invention are usually installed or stored in the HDD, SSD, etc. in the storage unit of a PC or mobile information terminal, and when the program or software is executed, the memory in the storage unit is installed or stored as necessary. All or part of it is read out as a software module, and arithmetic operations are executed by the CPU.

Alternatively, a browser-based computer or personal digital assistant may be employed. In this case, a program is distributed to the terminal from another server or computer as needed, and the program is executed by a browser on the terminal.

Furthermore, the hardware configuration of the payment server 11 and the management server 12 can basically be a PC (to be sure, this will be described later with reference to FIG. 2). Although the present invention is not limited to this, the payment server 11 and the management server 12 may be installed on a plurality of PCs (for example, several tens to tens of thousands of PCs) in order to increase their hardware specifications as necessary. ) can be operated in parallel to create a configuration suitable for processing large-scale data.

FIG. 2 shows a functional block diagram of a management server and a payment server in an online sales system according to an embodiment of the present invention. Illustratively, the operations of the management server are realized by the individual operations of hardware and the cooperative operations of software and these hardware, which will be described below.
In the following, a management server will be taken as an example and its functional blocks will be explained. That is, the payment server can also have a similar configuration.

In FIG. 2, the management server 200 as an entire hardware block is roughly divided into a CPU 201 for performing various comparison and arithmetic processing, a storage unit 202 such as RAM, ROM, and flash memory, and a storage unit 202 for performing various comparison and calculation processes, and An input section 203, an output section 204 such as a display or a speaker, a control section 205 for controlling various signals, a communication (interface) section 206 (regardless of whether it is wireless or wired), and a timer for measuring time, etc. section 207 and a power supply section 208.

These modules are connected by appropriate communication buses and power supply lines (in FIG. 2, for convenience, each line is shown as a connection 299 collectively) as necessary.

Further, the programs or software executed on the management server 200 necessary for implementing the present invention are usually installed or stored in a hard disk, SSD (Solid State Drive), flash memory, etc. that constitute the storage unit 202, and the programs or software are When the software is executed, all or part of it is read out as a software module to the memory in the storage unit 202 as needed, and the CPU 201 executes the calculation.

Note that the execution of calculations does not necessarily need to be performed by a central processing unit such as the CPU 201, and an auxiliary calculation device such as a digital signal processor (DSP) (not shown) may also be used.

FIG. 3 shows the external configuration of a smartphone or tablet terminal 16 as an information processing device (user terminal) in an online sales system according to an embodiment of the present invention. In FIG. 3, the smartphone or tablet terminal 16 includes a housing 161, a display 162, and a hardware button 163 provided at the lower center of the housing 161. The display 162 is typically configured with a liquid crystal display (LCD) or the like, and can display various information such as text, still images, and moving images. Further, by displaying a menu button or a software keyboard on the display 162 and touching it with a finger or a touch pen (not shown), instructions (commands) can be given to the tablet terminal 16. In this respect, the hardware button 163 is not an essential component, but for convenience of explanation of the present invention, it is implemented as a button that performs a certain function. In one embodiment of the invention, a physical button such as the hardware button 163 may be replaced by a menu button displayed on a portion of the display 162.

The display 162 also includes a multi-touch input panel, and the touch input position coordinates on the touch input panel are sent to the processing system (CPU) of the smartphone or tablet terminal 16 via an input device interface (not shown). sent and processed. This multi-touch input panel is configured to be able to simultaneously sense multiple touch points on the panel. This detection (sensor) can be realized by various methods, and is not necessarily limited to a contact sensor, for example, it is also possible to extract the indicated point on the panel using an optical sensor. Furthermore, in addition to a contact type sensor or an optical type sensor, a capacitance type sensor that detects contact with a person's skin can also be used as the sensor.

Although not shown in FIG. 3, the smartphone or tablet terminal 16 can also be equipped with a microphone and a speaker. In this case, it is also possible to distinguish the user's voice picked up from a microphone and use it as an input command. Furthermore, although not shown in FIG. 3, a camera device such as CMOS can be mounted on the back of the smartphone or tablet terminal 16.

FIG. 4 illustrates a functional block diagram of hardware that constitutes the smartphone or tablet terminal 16 according to an embodiment of the present invention. The operations of the smartphone or tablet terminal 12 are realized by the individual operations of hardware and the cooperative operations of software and these hardware, which will be described below.

In FIG. 4, the smartphone or tablet terminal 400 as an entire hardware block can be roughly divided into an input unit 401 that includes the hardware button 163 in FIG. 3, a multi-touch input panel provided on the display 162, a microphone, etc. , a storage unit 402 consisting of a hard disk, RAM and/or ROM, etc. for storing programs and data, a central processing unit 403 consisting of a CPU that performs various numerical calculations and logical operations according to the program, and a display. 162, a control section 405 for controlling chips, electrical systems, etc., a slot for accessing the Internet, a port for optical communication, and a communication interface. A communication interface section 406, an output section 407 such as a speaker, vibration, infrared projector, etc., a clock section 408 for measuring time, etc., and a sensor section 409 consisting of an image sensor such as CMOS, an infrared sensor, an inertial sensor, etc. It consists of a power supply unit 410 for supplying power to each module in the device, and these modules are connected to a communication bus or a power supply line as necessary (in FIG. 4, for convenience, each line is grouped together as a connection 499 where each line is divided as appropriate). (represented in ).

Note that the sensor unit 409 may include a GPS sensor module for identifying the location of the smartphone or tablet terminal 400 (16). Further, a signal detected by an image sensor such as a CMOS, an infrared sensor, or the like constituting the sensor unit 409 can be processed as input information in the input unit 401.

Further, programs or software that are executed on the smartphone or tablet terminal 400 necessary for carrying out the present invention are usually installed or stored in a hard disk, SSD (Solid State Drive), flash memory, etc. that constitute the storage unit 402. When a program or software is executed, all or part of it is read out as a software module to the memory in the storage unit 402 as needed, and the CPU 403 executes the calculation.

Note that the execution of calculations does not necessarily need to be performed by the central processing unit 403 such as a CPU, and an auxiliary calculation device such as a digital signal processor (DSP) (not shown) may also be used.

Note that for the functional blocks of the store terminals 13a to 13c shown in FIG. 1, configurations such as the management server and payment server shown in FIG. 2 may be adopted, or the information processing shown in FIG. A device-like configuration may also be adopted (in this specification, description of the functional blocks of the store terminals 13a to 13c is omitted).

Next, FIGS. 5 and 6 show an example of the flow of processing operations in the online sales system according to an embodiment of the present invention. Of the processing operation flow shown in FIG. 5, the one shown at time t11 to t15 is the flow when a seller's (store) account is issued on the management server. The seller's account issued here is also referred to as a "management server account" or "sales account." The flow shown from time t21 to t27 in FIG. 5 is a flow when a seller (store) account is issued on the payment server. The seller's account issued here is also referred to as a "payment server account" or "payment account." The flow shown from time t31 to t33 in FIG. 5 is a flow for registering information (product information) on products sold by a seller (store) in the management server. When product information is registered in the management server from the store terminal, the product information can be provided from the management server in response to a request from the user terminal. The flow shown from time t41 to time t53 in FIG. 6 is a flow when the user selects a purchased product based on product information provided from the management server and makes payment.

In step S501 (times t11 to t12) in FIG. 5, the store terminal receives a request to create a management server account from the store person (seller). Specifically, although shown in a simplified manner in FIG. 5, the store terminal accesses the management server and receives an operation screen from the management server. When the sales account registration button displayed on the operation screen is selected by the store staff, a sales account creation request is accepted. The store terminal that has received the account creation request transmits a sales account creation request to the management server (step S502). The management server that has received the sales account creation request reads the management server account creation input screen from the storage unit (step S503) and transmits it to the store server (step S504) from time t12 to t13.

The store terminal that receives the management server account creation input screen displays the same screen on the display unit (step S505). This screen includes an input field for management server account information. Therefore, the store terminal accepts input from the store personnel into the information input field. The information input here includes, for example, a corporate name, address, e-mail address, telephone number, contact person, login ID (which may be an e-mail address), and login password. When the management server account information is input at time t13 to t14 and the send button is pressed by the store staff, the information is sent to the management server (step S506). The management server that has received the sales account information registers the same information in the storage unit from time t14 to t15 (step S507), and sends a completion notification to the store terminal (step S508). As described above, from next time onwards, by inputting the registered login ID and login password, the store terminal can use the sales management service (sales management software) provided by the management server.

Next, according to the flow shown from time t21 to t27 in FIG. 5, an account for the seller (store) is issued at the payment server. The store account issued here is used in a payment service provided by a payment server, and is also referred to as a "payment server account" or "payment account." A payment server account is different from a management server account.

In step S511 (times t21 to t22) in FIG. 5, the store terminal receives input of seller account information for deposit from the seller (store staff). Specifically, although shown in a simplified manner in FIG. 5, the store terminal accesses the management server, logs into the sales management service, and receives an account information input screen displayed during the service. The seller's account information (for depositing money at the time of product sale) is input into the input screen by the store staff's operation (step S511). After the account information is input, when the registration button is selected by the store staff, the store terminal transmits the account information to the management server (step S512).

At time t22 to t23, the management server registers the received account information in the storage unit (step S513). As described above, when account information is input at the store terminal, the store terminal has already logged into the sales management service. Therefore, the management server registers the received account information in association with the seller's management server account. When the registration of account information is completed, the management server sends a completion notification to the store terminal (step S514).

In step S515 (times t23 to t24), the store terminal receives a request to create a payment server account from the store staff. Specifically, although shown in a simplified manner in FIG. 5, the store terminal accesses the management server and receives an operation screen from the management server. When the payment server account registration button displayed on the operation screen is selected by the store staff, a payment server account creation request is accepted. The store terminal that received the account creation request transmits a payment server account creation request to the management server (step S516).

Note that the flow from steps S511 to S516 in FIG. 5 is only one embodiment. For example, before registration (step S513), input of merchant account information for deposit (step S511) and step S515 (payment server account creation request) may be accepted at the same time. In this case, the notification of completion of step S514 will be given after step S515 in FIG.

The management server that has received the payment server account creation request reads information necessary for creating a payment server account from the storage unit at time t24 to t25 (step S517). The necessary information here includes, for example, a corporate name, address, e-mail address, telephone number, contact person, login ID (may be an e-mail address), login password, and deposit course information. The login ID and login password here are for logging into the payment service (payment software) provided by the payment server. The login ID and login password for the payment service may be input by the store staff when accepting the payment server account creation request (step S515). Alternatively, it is also possible to arbitrarily set it on the management server side.

The management server transmits a payment account creation request to the payment server together with the read necessary information (step S518). The payment server that has received the payment account creation request and the necessary information creates a payment account and registers the necessary information in the storage unit at time t25 to t26 (step S519). When the registration is completed, the payment server sends a completion notification to the management server (step S520). The completion notification here may include unique identification information (customer number, etc.) generated by the payment server for each seller in addition to the information (part of the necessary information) that the management server has notified the payment server. can.

In step S521 (times t26 to t27), the management server that has received the completion notification registers the contents of the completion notification in the storage unit in association with the seller (cooperation with the payment server). For example, the management server sets a flag indicating that account creation on the payment server has been completed in association with the seller's sales account. Alternatively, the management server stores the customer number generated by the payment server in association with the sales account. When the registration is completed, the management server notifies the store terminal that the creation of the payment account has been completed (step S522). The management server also opens a page (seller page) for the seller to sell products (step S523). Thereby, the store terminal can register the product that the seller desires to sell in the sales management service provided by the management server. In other words, until the creation of a payment account is completed, each seller cannot sell his or her own products via the sales management service provided by the management server.

Although the flow from step S501 to step S523 in FIG. 5 has been clearly divided into the flow from step S501 to step S508 and the flow from step S511 to step S523, the present invention is not limited to this. Instead, it may be configured to accept steps S501, S505, S511, and S515 all at once (in this case, the store terminal inputs through one input reception screen or a series of input receptions). The information and requests input from the store terminal may be sent to the management server each time, or may be sent to the management server all at once after all information has been input. The management server can create necessary accounts and associate information based on the collectively transmitted information.

At time points t31 to t33 in FIG. 5, the seller registers information on products he/she wishes to sell (product information) from the store terminal to the management server. That is, in step S531 (times t31 to t32) in FIG. 5, the store terminal receives input of product information from the seller (store staff). Specifically, the store terminal accesses the management server, logs into the sales management service, and receives the product information input screen displayed during the service. Product information is input into the input screen by the operation of the store staff (step S531). The product information here includes the contents of the product. In one embodiment of the present invention, the contents of the product include the name of the content, such as an online seminar, the outline, the instructor's name, the date and time (period), and the price.
After the product information is input, when the registration button is selected by the store staff, the store terminal transmits the product information to the management server (step S532).

In step S533 (times t32 to t33), the management server registers the received product information in the storage unit. As described above, when product information is input at the store terminal, the store terminal has already logged into the sales management service. Therefore, the management server registers the received product information in association with the seller's sales account. When the registration of product information is completed, the management server enables access to the registered product information from the outside (user terminal, etc.).

At time points t41 to t53 in FIG. 6, an example of a flow when a user selects a purchased product based on product information provided from the management server and makes payment is shown. In step S601 (times t41 to t42), the user terminal starts a purchase application (hereinafter also referred to as "purchase application") in response to an operation by a user (purchaser, customer). The user terminal then transmits a product viewing request to the management server in response to the user's operation (step S602). In step S603 (times t42 to t43), the management server extracts product information corresponding to the product viewing request received from the user terminal from the storage unit, and transmits the extraction result (product information) to the user terminal (step S604). .

In step S605 (times t43 to t44), the user terminal displays the product information received from the management server on the display unit and accepts input of a product purchase request from the user. The user terminal then transmits a product purchase request to the management server (step S606).

In step S607 (times t44 to t45), the management server records the product purchase request received from the user terminal in the storage unit. Next, the management server transmits a purchase procedure explanation and a consent request to the user terminal (step S608). In step S609 (times t45 to t46), the user terminal displays the purchase procedure explanation and consent request received from the management server on the display unit, and accepts input from the user for consent to the purchase procedure. When the user inputs consent, the user terminal transmits the consent to the management server (step S610). In step S611 (times t46 to t47), the management server records in the storage unit that consent has been obtained from the user, and prepares a payment page (reads payment page information from the storage unit). The management server then transmits the payment page to the user terminal (step S612).

In step S613 (times t47 to t48), the user terminal displays the payment page received from the management server on the display unit and accepts input of payment information (user payment information) from the user. The user payment information here includes, for example, the user's credit card number, user name, and credit card expiration date. Further, in an embodiment of the present invention, the user may be required to input the user's contact information such as an e-mail address here.
After the user payment information is input, when the payment button on the payment page is pressed, the user terminal transmits a payment request (including the user payment information) to the management server (step S614).

In step S615 (times t48 to t49), the management server stores the user payment information and purchased product information from the user terminal in the storage unit, and also stores the seller information necessary for payment (seller payment information). Read from storage. Note that, as described later, the storage of user payment information in the management server is temporary. Further, the seller payment information here includes, for example, the login ID and login password for the payment server (as well as unique information of the purchaser). Then, the management server transmits a payment request (including user payment information, product information (price, etc.), and seller payment information) to the payment server (step S616).

In step S617 (times t49 to t50), the payment server performs payment processing based on the payment request (including user payment information, product information (price, etc.), and seller payment information) from the management server. Specifically, the payment server performs processing for billing the user based on user payment information and product information (price) (this billing processing itself does not need to be completed between times t49 and t50). ). Furthermore, the payment server performs processing for remittance to the seller based on the seller payment information and product information (price) (this remittance processing itself does not need to be completed between times t49 and t50). . When the processing for payment is completed, the payment server notifies the management server of completion (step S618).

In step S619 (times t50 to t51), the management server records the contents of the completion notification (that the payment has been completed) in the storage unit. Then, the management server notifies the store terminal of completion (step S620), and also notifies the user terminal of completion (step S621).

In an embodiment of the present invention, in step S621, access information (access method, access destination such as link, and access password if necessary) to the purchased product (content such as online seminar) is sent to the user terminal. is sent.

Then, in step S622 (times t52 to t53), the management server deletes the temporarily stored user payment information from the storage unit and notifies the user terminal of the deletion (deletion notification). Step S623).
In addition, in this embodiment, although the notification of step S621 and the notification of step S623 were explained separately, the present invention is not limited to this, and for example, the notification may be notified at once after step S622. good.
Furthermore, the access information can be notified at any timing other than the timing of step S621 described above.

Note that the object sold via the management server (sales object) may be a downloadable file. In this case, the management server notifies the user terminal of the file download method together with or separately from the payment completion notification (S621) or the user payment information deletion notification (S623). As a result, when the payment is completed, it becomes possible for the management server to promptly notify the user terminal of the Internet access method and file download method for online content without going through the store terminal. After completing the payment, the user is immediately ready to download the file or access the online content for which the event date and time have been specified.

FIG. 7 is a flowchart illustrating a processing operation flow in an online sales system according to another embodiment of the present invention. The flow in FIG. 7 is mainly shown from the perspective of the seller. Further, the process in FIG. 7 is a variation of, for example, the process in FIG. 5 (times t11 to t15, t21 to t27).
When the process starts in step S701, the store terminal requests the management server to create a sales account in response to an operation by the seller (store staff) (step S702). The request here may include the seller's email address and login password.

Next, in step S703, the store terminal receives input of seller information (seller information for sale) from the store staff. The sales seller information here may include, for example, a corporate name, postal code, address, and telephone number. Further, when inputting the seller information for sale, consent regarding the handling of personal information may be obtained from the seller. When the input seller information for sale is transmitted from the store terminal to the management server, the seller information is registered in the management server (step S704).

In step S705, the store terminal requests the management server to call up the payment server cooperation page in response to the operation of the store staff. When there is an operation request from the store staff with the payment server cooperation page displayed on the store terminal, the store terminal accesses the payment server via the management server (step S706). If a payment account corresponding to the seller does not exist and a new payment account needs to be created (step S707: Yes), the seller information (payment seller information) is sent to the payment server in step S708. register. The payment seller information here includes, for example, a corporate name, corporate number (corporate my number), telephone number, industry type, head office location, bank account number for deposit, etc. After step S708, the process advances to step S709.

If a payment account already exists (S707: No) or after step S708, registration information (cooperation information) in which the management server cooperates with the payment server is presented to the seller in step S709. Here, the seller can confirm the content of the collaboration information. If the content of the cooperation information is correct (step S710: Yes), the process advances to step S711, where the payment server or a person related to the payment server evaluates the seller. For example, an assessment of a seller is performed by a payment agent. If the assessment result is acceptable (step S712: Yes), the cooperation between the seller information in the management server and the payment server is determined (step S713).

If the content of the cooperation information is incorrect in step S710 (S710: No) or if the assessment result is unacceptable in step S712 (S712: No), the store terminal displays an error such as an alert (step S714). After step S713 or S714, the flow of this embodiment ends (step S715).

FIG. 8 is a flowchart illustrating a processing operation flow in an online sales system according to another embodiment of the present invention. In particular, FIG. 8 focuses on a scene in which a user (purchaser or customer) of a user terminal uses a sales management service (sales management application) provided by a management server. Further, the process in FIG. 8 is a variation of, for example, the process in FIG. 6 (times t41 to t53).
When the process in FIG. 8 is started (step S801), a sales management application is started in step S802. In step S803, a product search or list display is performed on the user terminal. In step S804, the product to be purchased is selected and the product purchase button is pressed.

Next, in step S805, the management server presents payment conditions and requests consent.
In one embodiment of the present invention, if the user agrees to the payment conditions (step S806: Yes), the process proceeds to step S807, and if the user does not consent (step S806: No), the process returns to step S803.

In step S807, the management server prepares a payment page and sends it to the user terminal. Then, user payment information is input at the user terminal and transmitted to the payment server via the management server (step S808). The user payment information here includes, for example, the user's email address as contact information, credit card information, and the like. Furthermore, in one embodiment of the present invention, the management server communicates and exchanges data with the payment server via an API (Application Programming Interface). At that time, the management server can temporarily store user payment information. Note that in other embodiments of the present invention, user payment information may be sent directly to the payment server without going through the management server.

Next, payment processing is performed in the payment server (step S809). After that, the payment server transmits a payment completion notification to the management server and/or the user terminal (step S810). Next, the temporarily stored user payment information is deleted in the management server (step S811). The management server then notifies the user terminal that the user payment information has been deleted (step S812). Note that the payment completion notification to the user terminal (S810) and the user payment information deletion notification (S812) may be combined into one. When step S812 ends, the process ends in this flow (step S813).

FIG. 9 is a flowchart illustrating a processing operation flow in an online sales system according to another embodiment of the present invention. FIG. 9 is a modification of FIG. 8, and in FIG. 9, the focus is particularly on a scene in which a user (purchaser or customer) of a user terminal uses a sales management service (sales management application) provided by a management server. ing. Further, the process in FIG. 9 is a variation of, for example, the process in FIG. 6 (times t41 to t53).
When the process in FIG. 9 is started (step S901), the sales management application is started in step S902. In step S903, the management server presents payment conditions and requests consent. If the user agrees to the payment conditions (step S904: Yes), the process proceeds to step S905; if the user does not agree (step S904: No), the process returns to step S903.

In step S905, a product search or list display is performed on the user terminal. Then, with the product selected and the user payment information (for example, the user's name, email address, and credit card number) entered, the product purchase button is pressed (step S906). The user payment information is transmitted to the payment server via the management server (step S907). At this time, user payment information is temporarily stored on the management server.

Next, payment processing is performed in the payment server (step S908). Next, the temporarily stored user payment information is deleted in the management server (step S909). After that, the payment server transmits a payment completion notification to the management server and/or the user terminal (step S910). Then, the management server notifies the user terminal that the user payment information has been deleted (step S911). Note that the payment completion notification to the user terminal (S910) and the user payment information deletion notification (S911) may be combined into one. When step S911 ends, the process ends in this flow (step S912).

FIG. 10 is a diagram illustrating a display example of an information processing device (store terminal) in an online sales system according to an embodiment of the present invention. In FIG. 10, a smartphone or tablet terminal 1000 (store terminal) includes a housing section 1010, a display 1020, and hardware buttons 1030. The display screen of the display 1020 is an example of a screen when inputting the seller's deposit bank account information at the store terminal (for example, S511 in FIG. 5, S708 in FIG. 7). The display screen of the display 1020 has an account name input field 1021, a financial institution name input field 1022, a branch name input field 1023, an account number input field 1024, an account number re-entry field 1025, and a continue button 1026. . In one embodiment of the present invention, when the continue button 1026 is pressed, another input screen is displayed including representative information input fields and the like. Alternatively, in another embodiment of the present invention, the continue button 1026 may be omitted and the input may be completed on the screen of FIG.

FIG. 11 is a diagram illustrating a display example of an information processing device (user terminal) in an online sales system according to an embodiment of the present invention. In FIG. 11, a smartphone or tablet terminal 1100 (user terminal) includes a housing section 1110, a display 1120, and hardware buttons 1130. The display screen of the display 1120 is an example of a screen when the user confirms payment conditions on the user terminal (for example, S609 in FIG. 6, S805 in FIG. 8, and S903 in FIG. 9). The display screen of the display 1120 has a title display field 1121, a payment condition (purchase procedure) display field 1122, a payment information deletion explanation field 1123, and an acceptance button 1124.

FIG. 12 is a diagram illustrating a display example of an information processing device (user terminal) in an online sales system according to an embodiment of the present invention. In FIG. 12, a smartphone or tablet terminal 1200 (user terminal) includes a housing section 1210, a display 1220, and hardware buttons 1230. The display screen of the display 1220 is an example of a screen when a user makes a purchase request for a product (service) on a user terminal (eg, S613 in FIG. 6, S808 in FIG. 8, and S906 in FIG. 9). The display screen of the display 1220 includes a product (service) title display field 1221, a product (service) description display field 1222, an event date/content display field 1223, a name input field 1224, an email address input field 1225, and a credit field. It has a card information input field 1226 and a purchase button 1227.

FIG. 13 is a diagram illustrating a display example of an information processing device (user terminal) in an online sales system according to an embodiment of the present invention. In FIG. 13, a smartphone or tablet terminal 1300 (user terminal) includes a housing section 1310, a display 1320, and hardware buttons 1330. The display screen of the display 1320 includes payment completion notifications (for example, S621 in FIG. 6, S810 in FIG. 8, and S910 in FIG. 9) and user payment information deletion notifications (for example, S623 in FIG. 6, S812 in FIG. 8, and S910 in FIG. 9). This is an example of a screen when displaying a combination of S911). The display screen of the display 1320 has a payment completion notification field 1321, a user payment information deletion notification field 1322, and an OK button 1323.

[Further variations of embodiments of the present invention]
Other embodiments of the present invention include the following variations.

(1) Giving a purchased product (content) as a gift to another person In another embodiment of the present invention, the purchaser may present the purchased product (content) at the time of purchase with the purpose of having the content purchased by the purchaser consumed by someone other than the purchaser. It can also be controlled so that viewing rights to the content can be gifted to others. In this case, as one embodiment, the following arrangement is added to the purchase screen shown in FIG. 12.

First, although not shown in FIG. 12, there is an input field for entering an expression of intent to purchase the purchased content for the purpose of a gift, and an input field for entering the name and/or email address of the gift recipient. A purchaser who purchases content for this purpose enters necessary information in these items and input fields.

When the payment process for purchasing the content is completed, access information for the purchased content (access method, link, etc., and access password if necessary) is sent to the email address of the gift recipient.
For other processes (notification of deletion of user payment information, etc.), embodiments similar to those of the embodiments described so far can be adopted.

(2) Transfer when the purchaser suddenly becomes unable to view the content, etc. In yet another embodiment of the present invention, if the purchaser becomes unable to view the content at a later date, the purchase It is also possible to control the transfer of content from one person to another. In this case, the following arrangement (not shown) is added.

The basic mechanism is that if a purchaser becomes unable to view or otherwise view content after purchasing the content, access information for this content is sent by email to a new user (transferee), and this new user This allows the content to be viewed, etc.
At this time, the access information email received by the purchaser is not simply transferred from the purchaser to the new user, but the user registration information is rewritten via the management server.

Specifically, first, the purchaser terminal issues a user registration information rewriting request to the management server, and the management server accepts registration of new user information in response to this request. Then, the management server changes the user information of the content according to the changes received from the purchaser terminal, performs update registration, and then sends an access information email to the new user. At this time, the store terminal can be notified of this, if necessary. Thereafter, the new user attempts to access the content at a scheduled time. At this time, the user information will also be requested to be input, and if the input user information matches the information after the user information has been changed, the management server will control the user to allow this user to participate. .

Note that if content management and viewing control are performed by a store terminal instead of a management server, part or all of the processing performed by the management server can be performed by the store terminal. At this time, necessary notifications and cooperation are performed between the management server and the store terminal as appropriate.

The embodiments of the online sales system and the like have been described above based on specific examples, but the embodiments of the present invention include a method or program for implementing the system or device, as well as a storage medium on which the program is recorded (for example, It is also possible to take an embodiment as an optical disk, magneto-optical disk, CD-ROM, CD-R, CD-RW, magnetic tape, hard disk, memory card, etc.

Furthermore, the implementation form of a program is not limited to an application program such as an object code compiled by a compiler or a program code executed by an interpreter, but may also be in the form of a program module incorporated into an operating system. good.

Furthermore, the program does not necessarily need to execute all processing only in the CPU on the control board, but may be executed on an expansion board attached to the board or another processing unit (DSP, etc.) mounted on the expansion unit as necessary. ) may be implemented in part or in whole.

All features recited in this specification (including the claims, abstract, and drawings) and/or all steps of any method or process disclosed are mutually exclusive. Can be combined in any combination except for combinations where .

In addition, each feature described in the specification (including the claims, abstract, and drawings) serves the same, equivalent, or similar purpose, unless expressly contradicted. Can be replaced with alternative features. Thus, unless expressly stated to the contrary, each feature disclosed is one example only of a generic series of identical or equivalent features.

Furthermore, the present invention is not limited to any of the specific configurations of the embodiments described above. The invention resides in every novel feature or combination thereof described in the specification (including the claims, abstract, and drawings), or every novel method or process step described, or It can be expanded to a combination of

10 Online sales system 11 Payment server 12 Management server 13a to 13c Store terminals 14 to 18 PC, smartphone or tablet terminal (one form of user terminal)
19 Public line (dedicated line, Internet, etc.)

Claims (6)

A user terminal used by a user who is a purchaser of a product or service;
a seller terminal used by the seller of the product or the service;
a management server that manages sales of the product or the service by the seller;
An online sales method executed in an online sales system comprising: a payment server that manages payment for sales of the product or the service;
a sales target information transmitting step of transmitting sales target information, which is information about a product or service to be sold, from the seller terminal to the management server;
a sales target information registration step of registering the sales target information received from the seller terminal in the management server and making it viewable from the user terminal;
a viewing request sending step of transmitting a viewing request for the sales target information from the user terminal to the management server;
a viewing information transmitting step of transmitting viewing information, which is the information to be sold in response to the viewing request, from the management server to the user terminal;
a viewing information output step of outputting the viewing information at the user terminal;
a purchase request transmitting step of transmitting a purchase request for the sales object selected from the viewing information from the user terminal to the management server;
a purchase request registration step of registering the purchase request in the management server;
a user payment information input step of accepting, at the user terminal, input of user payment information necessary for payment corresponding to the purchase request;
a step of temporarily storing user payment information, transmitting the user payment information from the user terminal to the management server and temporarily storing it in the management server;
a payment request step of transmitting the payment amount of the sale object, the transfer destination information of the payment amount, and the user payment information from the management server to the payment server;
a payment processing step in which the payment server performs payment processing based on the payment amount, the transfer destination information, and the user payment information;
a payment processing completion notification step of notifying the management server from the payment server of the completion of the payment processing;
a user payment information deletion step of deleting the temporarily stored user payment information in the management server;
An online sales method characterized by comprising: a user payment information deletion notification step of notifying the user terminal from the management server of the deletion of the temporarily stored user payment information and outputting it at the user terminal. The online sales method according to claim 1,
Before the user payment information input step,
a pre-approval requesting step in which the management server sends, to the user terminal, an explanation of the purchasing guidelines for the sale object and a request for consent to the purchasing guidelines;
a consent acceptance step of receiving the consent from the user at the user terminal;
a consent sending step of transmitting the consent from the user terminal to the management server;
The online sales method further comprises the step of requesting transmission of user payment information from the management server to the user terminal. The online sales method according to claim 1 or 2,
After the payment processing completion notification step, the management server further includes a sales completion notification step of transmitting sales completion information, which is information regarding the sales object for which the payment processing has been completed, to the seller terminal. How to sell online. In the online sales method according to any one of claims 1 to 3,
Before the sales target information sending step,
a step of requesting the creation of a management server seller account from the seller terminal to the management server;
a management server seller account creation step of creating a management server seller account in the management server;
an account information request step of transmitting an input request for remittance seller account information from the management server to the seller terminal;
a seller account information sending step of receiving the remittance seller account information at the seller terminal and simultaneously or separately transmitting a payment server seller account application from the seller terminal to the management server;
a step of requesting the creation of a payment server merchant account, in which the management server sends the remittance merchant account information and the payment server merchant account application to the payment server;
a step of creating a payment server merchant account in the payment server based on the remittance merchant account information and the payment server merchant account application;
a step of transmitting the payment server merchant account from the payment server to the management server;
An online sales method characterized by comprising an account linking step of registering, in the management server, the seller account information for the management server and the seller account for the payment server in a linked manner. A sales management server that manages sales of products or services by sellers,
The sales management server is
a user terminal used by a user who is a purchaser of the product or the service;
a seller terminal used by the seller of the product or service;
is capable of communicating with a payment server that manages payment for sales of the product or service;
Furthermore, the server:
a sales target information receiving step of receiving sales target information, which is information about a product or service to be sold, from the seller terminal;
a sales target information registration step of registering the sales target information received from the seller terminal and making it viewable from the user terminal;
a viewing request receiving step of receiving a viewing request for the sales target information from the user terminal;
a viewing information transmitting step of transmitting viewing information, which is the sales target information in response to the viewing request, to the user terminal;
a purchase request receiving step of receiving, from the user terminal, a purchase request for the sales object selected from the viewing information at the user terminal;
a purchase request registration step of registering the purchase request;
a step of transmitting a user payment information input screen to the user terminal, a user payment information input screen necessary for payment corresponding to the purchase request;
a user payment information temporary storage step of receiving and temporarily storing the user payment information from the user terminal;
a payment request step of transmitting the payment amount of the sale object, the transfer destination information of the payment amount, and the user payment information to the payment server;
a payment processing completion notification receiving step of receiving from the payment server a notification of completion of the payment processing performed by the payment server based on the payment amount, the transfer destination information, and the user payment information;
a user payment information deletion step of deleting the temporarily stored user payment information;
A sales management server characterized by executing the following steps: a user payment information deletion notification step of notifying the user terminal of deletion of the temporarily stored user payment information. A program executable on a sales management server that manages sales of products or services by a seller,
The sales management server is
a user terminal used by a user who is a purchaser of the product or the service;
a seller terminal used by the seller of the product or service;
is capable of communicating with a payment server that manages payment for sales of the product or service;
Furthermore, the server:
a sales target information receiving step of receiving sales target information, which is information about a product or service to be sold, from the seller terminal;
a sales target information registration step of registering the sales target information received from the seller terminal and making it viewable from the user terminal;
a viewing request receiving step of receiving a viewing request for the sales target information from the user terminal;
a viewing information transmitting step of transmitting viewing information, which is the sales target information in response to the viewing request, to the user terminal;
a purchase request receiving step of receiving, from the user terminal, a purchase request for the sales object selected from the viewing information at the user terminal;
a purchase request registration step of registering the purchase request;
a step of transmitting a user payment information input screen to the user terminal, a user payment information input screen necessary for payment corresponding to the purchase request;
a user payment information temporary storage step of receiving and temporarily storing the user payment information from the user terminal;
a payment request step of transmitting the payment amount of the sale object, the transfer destination information of the payment amount, and the user payment information to the payment server;
a payment processing completion notification receiving step of receiving from the payment server a notification of completion of the payment processing performed by the payment server based on the payment amount, the transfer destination information, and the user payment information;
a user payment information deletion step of deleting the temporarily stored user payment information;
and a step of notifying the user payment information of deletion of the temporarily stored user payment information to the user terminal.

Images