JP6800940B2 - Event loading / unloading WEB payment system and WEB server - Google Patents

Description

The present invention relates to an event loading / unloading WEB payment system and a WEB server that accepts luggage and settles charges for event exhibitors from a PC / smartphone.

In recent years, events such as Design Festa have been attracting attention. Design Festa is one of the largest international art events in Asia held in Tokyo, and any person can exhibit original works and expressions without judging. A service for delivering home delivery to such an event venue is also known (see, for example, Non-Patent Document 1).

Komigra "Delivery to the event venue", October 1, 2018 search, Internet <URL: https://www.graphic.jp/comic/guide/event_delivery.php>

However, according to the service described in Non-Patent Document 1, there is a problem that cash is collected when the event is carried in and out, and the site is congested. In addition, at an event where a large number of exhibitors gather, there is a problem that a mistake in delivery of luggage to the exhibitors occurs.

In view of the above-mentioned conventional techniques, the present invention provides an event loading / unloading WEB payment system and a WEB server capable of alleviating congestion due to cash collection and suppressing baggage delivery mistakes to exhibitors. The purpose is to provide.

In order to achieve the above object, the event loading / unloading WEB payment system according to one aspect of the present invention is a system for loading / unloading luggage and paying charges for event exhibitors from the user terminal. A WEB server connected to the WEB server and a reception terminal installed at the event venue are provided, and when the WEB server pre-receives a WEB application from the user terminal, the application for the outbound route corresponding to the WEB application is completed. by return mail to the applicant, we verify your identity line of the applicant at the time of luggage delivery of the carry-in by using the accepted information that has been described in its application completion mail, when the WEB server accepts the return path application, the WEB The return route application completion email is returned from the server to the user terminal, and the reception terminal is pasted in the return route application completion email sent from the WEB server , and the reception number issued for each return route application . by issuing an invoice for a carry-out by reading the QR code (registered trademark) corresponding to, at the time of discharge, using the invoice, we verify your identity line at the time of luggage delivery of the carry-out, in the forward path of the application completion mail Is characterized in that a URL for adding a return route is described, and when the URL is selected, the application acceptance screen for the return route is displayed on the user terminal by the WEB server .
The WEB server according to another aspect of the present invention is characterized by being provided by the event import / export WEB payment system according to the one aspect.

According to the present invention, it is possible to provide an event loading / unloading WEB payment system and a WEB server that can alleviate congestion due to cash collection and suppress baggage delivery mistakes to exhibitors. is there.

It is a figure which shows the outline of the event loading / unloading WEB payment system. It is a figure which shows the process at the time of the event carry-in / out WEB payment system. It is a figure which shows the process at the time of carrying out of the event loading / unloading WEB payment system. It is a system configuration diagram of the event loading / unloading WEB payment system. It is a sequence diagram of the event loading / unloading WEB payment system. It is a sequence diagram of the event loading / unloading WEB payment system. It is a sequence diagram of the event loading / unloading WEB payment system. It is a sequence diagram of the event loading / unloading WEB payment system. It is a flow chart from the application of the event loading / unloading WEB payment system to the issuance of the invoice. It is a figure which shows an example of the application acceptance screen of the outbound route displayed on a user terminal. It is a figure which shows an example of the application completion screen of the outbound route displayed on a user terminal. It is a figure which shows an example of the application completion mail of the outbound route displayed on a user terminal. It is a figure which shows another example of the application completion screen of the outbound route displayed on a user terminal. It is a figure which shows another example of the application completion mail of the outbound route displayed on a user terminal. It is a figure which shows an example of the application acceptance screen of a return trip displayed on a user terminal. It is a figure which shows an example of the application completion screen of the return trip displayed on a user terminal. It is a figure which shows an example of the application completion mail of the return trip displayed on a user terminal. It is a figure which shows an example of a sticking slip. It is a figure which shows an example of the invoice for carrying out. It is a figure which shows an example of the application acceptance screen of a return trip displayed on a user terminal. It is a figure which shows an example of the application acceptance screen of a return trip displayed on a user terminal.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the description of the drawings below, the same or similar parts are designated by the same reference numerals. In the following embodiment, an event loading / unloading WEB payment system that accepts luggage and settles charges from a PC / smartphone for event exhibitors is illustrated, but the configuration and arrangement of devices, data types, etc. are described below. It is not limited to things.

≪Overview≫
FIG. 1 is a diagram showing an outline of an event loading / unloading WEB payment system (hereinafter, simply referred to as “the present system”) according to the embodiment of the present invention. Here, an example is shown in which the exhibitor 10 exhibits his work at an event such as Design Festa or a comic market.

The event referred to in the embodiment of the present invention is typically an exhibition event for individuals or sole proprietors, but may be an exhibition event for companies. At least, as long as there is an act of bringing in luggage to the event venue 50 or an act of carrying out luggage from the event venue 50 and payment of the charges (for example, freight, sorting fee) is incurred, the event referred to in the embodiment of the present invention. include. In this system, the following methods are adopted in order to alleviate congestion due to cash collection that occurs when loading and unloading this type of event and to suppress baggage delivery mistakes for exhibitors 10.

That is, as shown in FIG. 1, it is assumed that the exhibitor 10 possesses a user terminal 11 such as a PC or a smartphone, and a credit card 12 as a payment means. When the exhibitor 10 accesses the event delivery reception site (WEB site) using the user terminal 11 and inputs the required items on the application reception screen on the outbound route, the goods received 1A is received and the fee is settled, and the reception is received. The information is returned to the exhibitor 10 who is the applicant by e-mail. Information such as the reception number is described in this reply mail (hereinafter referred to as "outbound application completion mail"). As a result, the delivery company can confirm the identity of the applicant at the time of delivery of the delivered goods 1A based on the information such as the reception number written in the application completion email on the outbound route.

An invoice 2A for carrying in is attached to the delivered item 1A, and a sticking slip (described later) is further attached to facilitate sorting. The delivered goods 1A are sorted in the distribution warehouse 3 and then brought into the event venue 50. Exhibitor 10 may sell his work during the event. This system can also be used when the event period is approaching the end and luggage is taken out from the event venue 50.

That is, the event delivery reception site (WEB site) is accessed using the user terminal 11, and essential items are input on the return application reception screen. In order to save the trouble of the exhibitor 10 at this time, the URL for adding the return route is described in the application completion email for the outward route, and when the URL is selected, the application acceptance screen for the return route is displayed on the user terminal 11. ing. At this time, the input items registered last time are reflected on the application reception screen for the return trip.

When the exhibitor 10 inputs the required items, the shipment 1B is accepted and the fee is settled, and the acceptance information is returned to the exhibitor 10 who is the applicant by e-mail. A QR code is pasted in this reply email (hereinafter referred to as "return application completion email"). In the QR code, the reception number associated with the input item registered on the return application reception screen is embedded. Exhibitor 10 displays the QR code on the user terminal 11 and presents it at the reception counter of the event venue 50. As a result, the reception terminal 51 installed at the reception counter reads the QR code to obtain the reception number, and issues an invoice 2B for carrying out that reflects the reception information registered in association with the reception number. Since the courier company 4 can confirm the identity at the time of delivery of the delivery shipment 1B based on the contents of the invoice 2B, it is possible to suppress a delivery error of the delivery shipment 1B.

As described above, according to this system, it is possible to eliminate cash collection at the event venue 50 and eliminate congestion at the time of baggage delivery by performing WEB settlement at the time of advance application. In addition, it is possible to confirm the identity of the applicant by different methods, considering the operational aspects of loading and unloading when delivering the package. Further, in consideration of the operational aspects of carry-in and carry-out, it is possible to use different invoices 2A and 2B at the time of carry-in and at the time of carry-out.

If all round-trip applications are accepted and WEB payment is made in advance, the number and size of luggage on the return trip will change depending on the sales of the work at the event, causing inconvenience in terms of charges. Therefore, in this system, while applying for the outbound route and the inbound route separately, a mechanism is adopted that saves the trouble of the exhibitor 10 when applying for the inbound route. This makes it possible to build a system with extremely high practical value that suits the circumstances peculiar to the event.

≪Processing at the time of loading and unloading≫
FIG. 2A is a diagram showing processing at the time of importing the event import / export WEB payment system according to the embodiment of the present invention. Hereinafter, the processing at the time of delivery will be described in detail with reference to FIG. 2A.

First, the exhibitor 10 accesses the WEB site 20 using the user terminal 11, inputs customer information, exhibition information, baggage information, etc. on the WEB site 20, and performs "credit", "convenience store prepayment", and "convenience store prepayment". Make a payment with either. In the following explanation, "convenience store prepaid" and "convenience store deferred payment" may be collectively referred to as "convenience store payment".

When the WEB site 20 accepts the outbound application, it performs processing such as receiving collection and creating collection request data, and returns an application completion email to the user terminal 11. At this time, a unique reception number is issued for each outbound application, and the reception number and the reception information of the outbound application are linked and registered in the database. In addition, processing such as event correspondence, pasting paper upload, explanation paper upload, collection request cooperation, corporate correspondence (master management), individual correspondence (payment correspondence), charge calculation (size input), checklist creation, etc. are also performed. The checklist is a list for checking all packages to be delivered to the event venue 50.

The courier company 4 performs processing such as a collection request, issuance of an invoice 2A, and handling of collection, and collects the delivered goods 1A. The application completion email will be used to verify your identity on site. The courier company 4 delivers the collected goods 1A to the distribution warehouse 3.

In the distribution warehouse 3, PDT (portable data terminal) balance input, arrival handling (sorting), storage management, shipping correspondence, checklist check, arrival confirmation, booth-specific sorting (cargo sorting), and the like are performed. Information such as the booth number of the event venue 50 is obtained in advance from the event organizer. After that, the delivered goods 1A are brought into the event venue 50. At the event venue 50, processing such as delivery by booth, confirmation at the time of delivery (email body), input of PDT delivery completion, receipt of judgment, and guidance of delivery is performed.

FIG. 2B is a diagram showing a process at the time of carrying out the event loading / unloading WEB payment system according to the embodiment of the present invention. Hereinafter, the processing at the time of carrying out will be described in detail with reference to FIG. 2B.

First, the exhibitor 10 can access the WEB site 20 by selecting the URL described in the application completion email on the outbound route. Enter the required items on the WEB site 20 and settle the payment by either "credit", "convenience store prepayment", "convenience store prepayment", or "electronic money".

A QR code in which the URL of the WEB site 20 is embedded in the reception counter 50C of the event venue 50 may be prepared. In this way, even the exhibitor 10 who has not applied for the outbound route can access the WEB site 20 by reading the QR code prepared at the reception counter 50C of the event venue 50 with the user terminal 11. Can be done.

When the WEB site 20 accepts the return trip application, the WEB site 20 returns the return trip application completion email to the user terminal 11. At this time, a unique reception number is issued for each return trip application, and the reception number and the reception information of the return trip application are linked and registered in the database. In addition, a QR code with a reception number embedded is pasted in the return application completion email.

The reception counter 50C will accept the return trip. At this return trip reception, the identity of the exhibitor 10 who applied is confirmed by reading the QR code attached to the return trip application completion email, and an invoice 2B for carrying out is issued. For exhibitors who selected electronic money at the time of application, an invoice 2B for shipping will be issued after the payment is completed. Since corporate customers can make invoices by accounts receivable, it is also possible to accept shipments when applying for imports. The courier company 4 attaches the invoice 2B for carrying out to the shipping item 1B and delivers it from the event venue 50 to the exhibitor 10's home or the like.

As described above, this system accepts luggage and settles charges from exhibitors 10 (corporations / individuals) at events. In addition, regarding the WEB reception, we will consider the operation at the time of loading and unloading, and also build the correspondence of "credit", "convenience store payment" and "electronic money" for the payment type.

≪System configuration example≫
FIG. 3 is a system configuration diagram of the event loading / unloading WEB payment system according to the embodiment of the present invention. Hereinafter, the configuration of this system will be described with reference to FIG.

As shown in FIG. 3, the user terminal 11 is connected to the WEB server 21 via the provider 61 and the Internet 62. The WEB server 21 is a computer that provides the WEB site 20, and the HP management DB 22 is a database necessary for providing the WEB site 20. The WEB server 21 performs various processes in cooperation with an external system such as the business management system 30 and the collection request system 40, and another company's server 70 such as VeriTrans.

The business management system 30 is a core system of a company that operates this system. The business management server 31 is a computer that operates this system, and the business management DB 32 is a database that is necessary for operating this system. The pickup request system 40 is a system of the delivery company 4 that manages the pickup request. In the case of carrying in, since collection is required, data is passed from the business management system 30 to the collection request system 40. VeriTrans is a company whose main business is the Internet payment agency business.

The reception terminal 51 is a computer installed at the reception counter 50C of the event venue 50, and is connected to the business management system 30 via the VPNN 63. Of course, it is also possible to connect to the WEB server 21 via the Internet 62.

The reception terminal 51 is a computer equipped with an application (invoice issuing system) for issuing an invoice 2B for carrying out, a QR code scanner 52 for reading a QR code, and electronic money payment capable of electronic money payment. It includes a terminal 53 and a printer 54 for printing an invoice 2B for carrying out. The electronic money payment terminal 53 is connected to another company's server 70 such as VeriTrans via Wi-Fi 64. The reception terminal 51 searches the business management DB 32 with the reception number embedded in the QR code, acquires the reception information associated with the reception number, and prints the invoice 2B for carrying out that reflects the reception information. It is designed to do.

≪Operation example: Credit / electronic money≫
FIG. 4 is a sequence diagram of the event loading / unloading WEB payment system according to the embodiment of the present invention. Here, an operation example when the payment type is "credit" or "electronic money" will be described.

First, the exhibitor 10 accesses the event delivery reception site (WEB site 20) using the user terminal 11 (step S1). When the application acceptance screen is displayed on the user terminal 11, the required items are input to the application acceptance screen (steps S2 → S3).

Here, when "credit" is selected as the payment type, the credit information is input (steps S4 → S5). If the payment content is OK, a confirmation screen is displayed on the user terminal 11 and examined by VeriTrans (step S6 → S7 → S8). If the credit is OK, the application completion screen is displayed on the user terminal 11 and an e-mail is sent (step S8 → S10 → S11). A QR code will be attached to this email when it is taken out. If the credit is NG, the NG screen is displayed on the user terminal 11 (step S8 → S9 → S4).

When "credit" is selected as the payment type, the following cooperation processing is performed. That is, when the WEB server 21 receives the luggage at the WEB site 20, it passes the reception information together with the reception number to the business management system 30 and cooperates with the business management system 30 (step S12). The business management system 30 cooperates with the collection request system 40 at the time of carry-in (step S13), and cooperates with the invoice issuing system at the time of carry-out (step S14). At the time of unloading, the application is made at the reception counter 50C, and collection is not required, so the system does not cooperate with the collection request system 40.

On the other hand, when "electronic money" is selected as the payment type, a confirmation screen is displayed on the user terminal 11, an application completion screen is displayed on the user terminal 11, and an email with a QR code attached is sent. (Step S15 → S16 → S17).

When "electronic money" is selected as the payment type, the following linkage processing is performed. That is, when the WEB server 21 receives the luggage at the WEB site 20, it passes the reception information together with the reception number to the business management system 30 and cooperates with the business management system 30 (step S18). The business management system 30 cooperates with the invoice issuing system at the time of carrying out (step S19). Electronic money is accepted only when it is taken out.

≪Operation example: Convenience store payment≫
FIG. 5 is a sequence diagram of the event loading / unloading WEB payment system according to the embodiment of the present invention. Here, an operation example when the payment type is "convenience store payment" will be described.

First, the exhibitor 10 accesses the event delivery reception site (WEB site 20) using the user terminal 11 (step S21). When the application acceptance screen is displayed on the user terminal 11, essential items are input to the application acceptance screen (steps S22 → S23).

Here, when "convenience store prepayment" is selected as the payment type, a confirmation screen is displayed on the user terminal 11, an application completion screen is displayed, and an e-mail is sent (steps S25 → S26 → S27). A QR code will be attached to this email when it is taken out.

If "Convenience store prepayment" is selected as the payment type, the following linkage processing is performed. That is, when the WEB server 21 receives the payment information from the VeriTrans side, it performs the payment processing, passes the reception information together with the reception number to the business management system 30, and cooperates with the business management system 30 (steps S29 → S30 → S31). ). The business management system 30 cooperates with the collection request system 40 at the time of carry-in (step S32), and cooperates with the invoice issuing system at the time of carry-out (step S33). At the time of unloading, the application is made at the reception counter 50C, and collection is not required, so the system does not cooperate with the collection request system 40.

On the other hand, when "convenience store deferred payment" is selected as the payment type, a confirmation screen is displayed on the user terminal 11 and the examination is performed by VeriTrans (steps S34 → S35). If the examination is OK, the application completion screen is displayed on the user terminal 11 and an e-mail is sent (step S35 → S37 → S38). A QR code will be attached to this email when it is taken out. If the examination is NG, the NG screen is displayed on the user terminal 11 (step S35 → S36 → S24).

In addition, when "convenience store deferred payment" is selected as the payment type, the following cooperation processing is performed. That is, when the WEB server 21 receives the luggage at the WEB site 20, it passes the reception information together with the reception number to the business management system 30 and cooperates with the business management system 30 (step S39). The business management system 30 cooperates with the collection request system 40 at the time of carry-in (step S40), and cooperates with the invoice issuing system at the time of carry-out (step S41). At the time of unloading, the application is made at the reception counter 50C, and collection is not required, so the system does not cooperate with the collection request system 40. After the receipt of the package is completed, the transfer form is sent to the exhibitor 10 (step S42).

≪Operation example: At the time of delivery≫
FIG. 6 is a sequence diagram of the event loading / unloading WEB payment system according to the embodiment of the present invention. Here, an operation example at the time of delivery (collection request) will be described.

First, it is assumed that the application is in the state of FIG. 4 or FIG. Here, when "credit" or "convenience store prepayment" is selected as the payment type, the invoice 2A for delivery is issued in cooperation with the business management system 30 and the collection request system 40, and the e-mail is confirmed locally. , Receive the package (step S51 → S52 → S53 → S54 → S55). On the other hand, when "Convenience store deferred payment" is selected as the payment type, the business management system 30 is linked, the pickup request system 40 is linked, the invoice 2A for delivery is issued, the mail is confirmed locally, and the package is received. After the receipt of the baggage is completed, the transfer form is sent to the exhibitor 10 (step S56 → S57 → S58 → S59 → S60 → S61).

≪Operation example: When carrying out≫
FIG. 7 is a sequence diagram of the event loading / unloading WEB payment system according to the embodiment of the present invention. Here, an operation example at the time of carrying out (receipt of luggage at the event venue 50) will be described.

First, it is assumed that the application is in the state of FIG. 4 or FIG. Here, when "credit", "convenience store prepayment", or "convenience store deferred payment" is selected as the payment type, the QR code pasted in the mail is read and carried out in cooperation with the business management system 30 and the invoice issuing system. Invoice 2B is issued and the package is received (step S71 → S72 → S73 → S74 → S75). Further, only in the case of "convenience store deferred payment", the transfer form is sent to the exhibitor 10 after the receipt of the package is completed (step S76). On the other hand, when "electronic money" is selected as the payment type, the electronic money payment is performed by linking with the business management system 30 and the invoice issuing system, reading the QR code pasted in the mail (step S71). → S72 → S77 → S78). If the balance is insufficient, the NG screen is displayed on the user terminal 11 (step S79 → S80), and if the balance is sufficient, the settlement is completed, the invoice 2B for carrying out is issued, and the package is received (step S79). → S81 → S82 → S83).

<< Example >>
Hereinafter, a more specific description will be given with reference to examples. It goes without saying that this embodiment is exemplified for facilitating the understanding of the present invention and is not limited to this content.

FIG. 8 is a flow chart from application for the event loading / unloading WEB payment system to issuance of an invoice according to the embodiment of the present invention. As shown in this figure, when the required items are entered on the outbound application acceptance screen 8A ₁ , the outbound application completion screen 8A ₂ is displayed and the outbound application completion email 9A is returned. When the URL for adding the return route described in the application completion email 9A for the outward route is selected, the application acceptance screen 8B _{1 for the} return route is displayed. At this time, the reception information at the time of the outbound route application is reflected on the return route application reception screen 8B ₁ . Normally, baggage information (number, size, etc.) for the return trip cannot be known accurately until the return trip application, so it is necessary to manually enter it when applying for the return trip. When the required items are entered on the return trip application acceptance screen 8B ₁ , the return trip application completion screen 8B ₂ is displayed and the return trip application completion email 9B is returned. When the QR code 7 pasted on the return trip application completion screen 8B ₂ or the return trip application completion email 9B is read by the QR code scanner 52 of the reception terminal 51, the invoice 2B for carrying out reflecting the reception information at the time of the return trip application is reflected. Is issued.

FIG. 9 is a diagram showing an example of the outbound application reception screen 8A ₁ displayed on the user terminal 11. As shown in this figure, the input items on the outbound application reception screen 8A ₁ are "name", "frigana", "number of family members accompanying", "phone number", "email address", "booth number", and "number of applications (outbound)". Is provided. Further, "number of applications (return trip)" and "return destination address" may be provided. It is also possible to enter "payment type" and other payment information.

FIG. 10 is a diagram showing an example of the application completion screen 8A ₂ on the outbound route displayed on the user terminal 11. As shown in this figure, the application completion screen 8A ₂ on the outbound route is provided with a button for downloading the affixed slip 6 and a button for downloading the instruction manual, in addition to a message indicating that the application has been completed. There is. In this embodiment, the sticking slip 6 is downloaded, the sticking slip 6 is printed, and then the sticking slip 6 is pasted on the delivered goods 1A and shipped.

FIG. 11 is a diagram showing an example of the outbound application completion mail 9A displayed on the user terminal 11. As shown in this figure, the outbound application completion email 9A includes a message indicating that the application has been completed, a URL for adding the return route, and a URL for downloading the sticker 6. The attachment slip 6 may be attached to this e-mail.

FIG. 12 is a diagram showing another example of the outbound application completion screen 8A ₂ displayed on the user terminal 11. As shown in this figure, the QR code 7 may also be pasted on the outbound application completion screen 8A ₂ . The method of using the QR code 7 is not limited, but if the QR code 7 is read by the reception counter 50C on the day of the event, an invoice 2B for carrying out may be issued.

FIG. 13 is a diagram showing another example of the outbound application completion mail 9A displayed on the user terminal 11. As shown in this figure, the QR code 7 may also be pasted on the outbound application completion email 9A. The method of using the QR code 7 is not limited, but if the QR code 7 is read by the reception counter 50C on the day of the event, an invoice 2B for carrying out may be issued.

FIG. 14 is a diagram showing an example of the return route application reception screen 8B ₁ displayed on the user terminal 11. As shown in this figure, as the return of the application acceptance screen 8B ₁ of input items, the "name", "kana", "telephone number", "email address", "booth number", "application number (Return),""ReturnAddress" It is provided. It is also possible to enter "payment type" and other payment information. When the URL described in the outbound application completion email 9A is used, the address registered last time is displayed, and only the "number of applications" and "return address" cannot be edited.

FIG. 15 is a diagram showing an example of the return application completion screen 8B ₂ displayed on the user terminal 11. As shown in this figure, a QR code 7 is pasted on the return application completion screen 8B ₂ in addition to a message indicating that the application has been completed. When this QR code 7 is read by the reception counter 50C on the day of the event, an invoice 2B for carrying out is issued.

FIG. 16 is a diagram showing an example of the return application completion mail 9B displayed on the user terminal 11. As shown in this figure, a QR code 7 is attached to the return application completion email 9B in addition to a message indicating that the application has been completed. A URL for adding a return route may be provided. When this QR code 7 is read by the reception counter 50C on the day of the event, an invoice 2B for carrying out is issued.

FIG. 17 is a diagram showing an example of the affixed slip 6. As described above, in this embodiment, the sticking slip 6 is pasted on the delivered goods 1A and shipped. In order to facilitate sorting, it is desirable to describe "event name", "number of luggage", "placement location", "exhibitor name", "person in charge name", etc. on the sticker 6.

FIG. 18 is a diagram showing an example of the invoice 2B for carrying out. The invoice 2B is an invoice for the return route created by the invoice issuing system of the reception terminal 51. The invoice issuing system reflects the input items (see FIGS. 19 and 20) registered on the return application reception screen 8B ₁ on the invoice 2B. The input items registered on the return application reception screen 8B ₁ can be acquired from the business management DB 32 of the business management system 30 via the VPNN 63. The format of the invoice 2B is not particularly limited, but (1) exhibition event, (2) municipality, (3) booth name, (4) booth number, (5) municipality (collection), (6) ) It is desirable to set the delivery date and time, (7) delivery quantity, (8) remarks, etc. Further, since it is most crowded at the time of carrying out, it is desirable that the invoice 2B for carrying out has a simple structure with few cut points.

≪Summary≫
As described above, the event loading / unloading WEB payment system according to the embodiment of the present invention is a system that carries out loading / unloading of luggage and payment of charges from the user terminal 11 for event exhibitors. It includes a WEB server 21 connected so as to be able to communicate, and a reception terminal 51 installed at the event venue 50. Then, when the WEB server 21 receives the WEB application in advance from the user terminal 11, the application completion mail 9A is returned to the applicant, and the person himself / herself at the time of delivery of the delivered baggage using the reception information described in the application completion mail 9A. Confirmation is performed, and the QR code 7 received in advance at the time of carrying out is read by the reception terminal 51 and an invoice 2B for carrying out is issued to confirm the identity at the time of delivery of the carried out baggage. As a result, it is possible to alleviate congestion due to cash collection that occurs when the event is carried in and out, and to suppress mistakes in the delivery of luggage to exhibitors.

Further, the URL for adding the return route is described in the application completion mail 9A for the outward route, and when the URL is selected, the application reception screen 8B ₁ for the return route is displayed on the user terminal 11. As a result, it is possible to save the trouble of the exhibitor 10 when applying for the return trip.

Also, if you've been a transition from the URL, the input matters that have previously registered are displayed on the return path of the application acceptance screen 8B _1. As a result, it is possible to further save the trouble of the exhibitor 10 when applying for the return trip.

In addition, among the input items displayed on the return route application reception screen 8B ₁ , information other than the return route information cannot be edited at the site. As a result, it is possible to avoid the inconvenience that the exhibitor 10 mistakenly edits the correct information.

Moreover, when completing the application in the return path of the application reception screen 8B _1, QR code 7 is displayed on the return path of the application reception screen 8B ₁ and return of the application completion mail 9B. As a result, the QR code 7 displayed on the screen of the user terminal 11 can be accurately read by the camera. That is, when the barcode displayed on the screen of the user terminal 11 is read by the laser beam, it may not be read accurately, but there is an effect that such a problem is unlikely to occur.

Further, the reception terminal 51 reads the QR code 7 to obtain a reception number, and reflects the reception information registered in the business management DB 32 in the corresponding column of the invoice 2B for carrying out in association with the reception number. As a result, the input items registered on the return application reception screen 8B ₁ can be reflected on the invoice 2B for carrying out by simply performing a simple operation of reading the QR code 7.

In addition, when applying for the outbound route, you can select any payment method from multiple payment methods including at least credit, convenience store prepayment, and convenience store prepayment, and when applying for the return trip, at least credit, convenience store prepayment, convenience store prepayment, and electronic money are available. Any payment method can be selected from the plurality of payment methods included. This has the effect of alleviating congestion due to cash collection at the time of loading and unloading.

If electronic money is selected when applying for the return trip, an invoice 2B for carrying out will be issued after the settlement is completed. As a result, it is possible to issue an invoice 2B for carrying out only when the balance is sufficient.

The present invention can be realized not only as such an event import / export WEB payment system, but also as a WEB server 21 or a reception terminal 51 included in such an event import / export WEB payment system. Further, a program that realizes as an event import / export WEB payment method in which a characteristic functional unit of such an event import / export WEB payment system, a WEB server 21, or a reception terminal 51 is a step, or causes a computer to execute those steps. It can also be realized as. Needless to say, such a program can be distributed via a recording medium such as a CD-ROM or a transmission medium such as the Internet.

<< Other Embodiments >>
As described above, embodiments of the present invention have been described, but the statements and drawings that form part of the disclosure are exemplary and should not be understood to be limiting. Various alternative embodiments, examples and operational techniques will be apparent to those skilled in the art from this disclosure. That is, embodiments of the present invention include various embodiments not described here.

1A Inbound goods 1B Inbound shipment 2A Invoice for inbound 2B Invoice for export 3 Logistics warehouse 7 QR code 8A ₁ Outbound application acceptance screen 8A ₂ Outbound application completion screen 8B ₁ Inbound application acceptance screen 8B ₂ Inbound application completion screen 9A Outbound application completion email 9B Return application completion email 10 Exhibitor 11 User terminal 20 WEB site 21 WEB server 30 Business management system 40 Collection request system 50 Event venue 50C Reception counter 51 Reception terminal

Claims (8)

It is an event loading / unloading WEB payment system that carries out loading / unloading of luggage and payment of fees from the user terminal for event exhibitors.
A WEB server that is communicatively connected to the user terminal,
The reception terminal installed at the event venue and
With
When the WEB server pre-receives a WEB application from the user terminal, it returns an application completion email for the outbound route corresponding to the WEB application to the applicant, and carries in using the reception information described in the application completion email. identification of the applicant is our line at the time of the luggage delivery,
When the WEB server accepts the return route application, the return route application completion email is returned from the WEB server to the user terminal, and the reception terminal pastes it into the return route application completion email sent from the WEB server. By reading the QR code (registered trademark) corresponding to the receipt number issued for each return trip application and issuing an invoice for unloading, the person at the time of delivery of the unloading baggage will be used at the time of unloading. It confirmed our line,
The URL for adding the return route is described in the application completion email for the outward route, and when the URL is selected, the WEB server displays the application acceptance screen for the return route on the user terminal. WEB payment system. The event loading / unloading WEB payment system according to claim 1 , wherein when the URL is transitioned, the input items registered last time are displayed on the application reception screen for the return route by the WEB server. The event loading / unloading WEB payment system according to claim 2 , wherein among the input items displayed on the return route application reception screen by the WEB server, information other than the information related to the return route cannot be edited at the site. The event according to claim 3 , wherein when the application is completed on the return route application acceptance screen, the QR code is displayed on the return route application completion screen and the return route application completion email by the WEB server. Carry-in / out WEB payment system. The receiving terminal, according to the reading the QR code to obtain the reception number, characterized in that it reflects the reception information registered in the database in association with the reception number in the appropriate field of the invoice for the unloading The event loading / unloading WEB payment system according to item 1 or 4 . In the WEB server, any payment method can be selected from a plurality of payment methods including at least credit, convenience store prepayment, and convenience store prepayment at the time of outbound application, and at least credit, convenience store prepayment, convenience store prepayment, at the time of return application. The event carry-in / out WEB payment system according to any one of claims 1 to 5 , wherein any payment method can be selected from a plurality of payment methods including electronic money. The event carry-in / out WEB payment system according to claim 6 , wherein when the electronic money is selected at the time of the return trip application, the reception terminal issues an invoice for carrying out after the payment is completed. A WEB server provided in the event loading / unloading WEB payment system according to any one of claims 1 to 7 .