JP7344331B1 - Payment control device, electronic payment system, and payment control method - Google Patents

Abstract

An object of the present invention is to provide a payment control device, an electronic payment system, and a payment control method that enable repurchasing of products purchased at a physical store. [Solution] A payment control device that performs payment for products that are subject to electronic payment in an electronic payment service that allows electronic payment to be made using a terminal device at a physical store, and that registers resale of products that have already been paid for electronically. A payment control device comprising: an acquisition unit that acquires information; and a resale processing unit that performs resale processing of paid products via electronic commerce based on resale registration information. [Selection diagram] Figure 3

Description

The present invention relates to a payment control device, an electronic payment system, and a payment control method.

2. Description of the Related Art Conventionally, when a user wants to repurchase a purchased product, a mechanism has been known in EC (Electronic Commerce) sites and the like that allows the user to repurchase based on the purchase history. For example, a mechanism is known that compiles purchase histories from multiple online shops and enables repurchases based on the purchase histories (see Patent Document 1).

JP2020-35144A

However, for example, when a user wants to repurchase a product purchased at a physical store (offline store) such as a roadside station or a store at a travel destination, such physical stores often do not have an e-commerce site. There was no other way to purchase than to visit a physical store directly. In physical stores that have a sales management system such as a POS (Point of Sale) device, it is possible to track purchase history by linking the user's credit card number, etc. It had not been done. Furthermore, in physical stores that do not have a sales management system in place, it is not possible to electronically manage what is purchased in the first place, making it impossible to track who has purchased what. In addition, there are cases where the products on sale do not have a list price, and it is not easy to repurchase the product at the same price as the previous purchase.

The present invention has been made in consideration of such circumstances, and aims to provide a payment control device, an electronic payment system, and a payment control method that enable repurchasing of products purchased at physical stores. be one of the.

One aspect of the present invention is a payment control device that performs payment for products that are subject to electronic payment in an electronic payment service that allows electronic payment to be performed using a terminal device in a physical store, the payment control device for making payments for products that have already been paid for in electronic payment. The present invention is a payment control device comprising: an acquisition unit that acquires resale registration information; and a resale processing unit that performs resale processing for products for which payment has been made via electronic commerce based on the resale registration information.

According to one aspect of the present invention, it is possible to provide a payment control device, an electronic payment system, and a payment control method that enable repurchase of products purchased at a physical store.

1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. It is a diagram illustrating the general flow of electronic payment. 1 is a configuration diagram of a payment server 100. FIG. 3 is a diagram showing an example of the contents of user information 172. FIG. It is a figure showing an example of the contents of store information 176. 7 is a diagram showing an example of the contents of delivery pattern information 178. FIG. 3 is a diagram showing an example of the contents of resale registration information 180. FIG. 2 is a diagram illustrating an example of a functional unit implemented by a payment application 20. FIG. FIG. 12 is a sequence diagram showing the flow of processing for purchasing products, shipping procedures, and resale registration using electronic payment in pattern 2. FIG. 7 is a diagram illustrating an example of screen transitions of the user terminal device 10 during electronic payment of pattern 2. FIG. It is a diagram showing an example of a shipping management screen. It is a figure which shows an example of a shipping arrangement screen. It is a figure showing an example of a resale registration screen. FIG. 2 is a sequence diagram showing the flow of processing for purchasing products, shipping procedures, and resale registration using electronic payment in pattern 1. FIG. FIG. 3 is a sequence diagram showing the flow of repurchase processing. It is a figure showing an example of transaction history screen P5. It is a figure showing an example of transaction history screen P5. It is a figure which shows an example of inventory and price confirmation screen P6.

Hereinafter, a payment control device, an electronic payment system, and a payment control method according to the present invention will be described with reference to the drawings. The payment control device of this embodiment is realized by one or more processors. The payment control device is a device that performs payment for products that are subject to electronic payment in an electronic payment service that allows electronic payment to be performed using a terminal device at a store. In the following description, the payment control device will be referred to as a "payment server." An electronic payment service is a service that supports payments for purchases of products and services at stores. A store is a physical store (actual store) that exists in real space.

[Electronic payment service]
FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by the payment server 100. The payment server 100 includes, for example, one or more user terminal devices 10, one or more store terminal devices 50, one or more delivery company servers 200, and one or more electronic commerce servers 300 (hereinafter referred to as "EC (Electronic Commerce) servers"). ) via the network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), and the like. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, so that the payment application 20 operates in cooperation with the payment server 100 to provide electronic payment services to the user. The payment application 20 controls the camera, communication device, touch panel, etc. The payment application 20 is an example of an "application program" for providing an electronic payment service that allows electronic payments to be made using a terminal device at a physical store.

The store terminal device 50 is installed in a store, for example. The store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The store terminal device 50 includes a so-called POS (Point of Sale) device, and the POS device may realize a product price acquisition function and an optical reading function. The store terminal device 50 may be, for example, a portable terminal device such as a smartphone or a tablet terminal. The store code image 60 is placed in a store, and a code image such as a QR code (registered trademark) is printed on a paper or plastic medium. Note that the store code image 60 may be displayed on a display placed in the store. In addition, the store terminal device 50 generates resale registration information for resale via electronic commerce of products that have been shipped or are scheduled to be shipped (hereinafter referred to as "shipped items") based on operations by an operator such as a store clerk. is sent to the payment server 100. Processing related to this resale registration information will be described later.

The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the store terminal device 50. The payment server 100 performs electronic payment by, for example, increasing or decreasing the charge balance managed in association with the user ID (in other words, depositing and withdrawing electronic money). Electronic payments may include methods such as revolving payment and credit card payments that enable purchases of a larger amount than the charge balance at the time of purchase. The payment server 100 is an example of a "payment control device" that can communicate with a terminal device and a store terminal device, and performs payment for products subject to electronic payment. Furthermore, the combination of the "application program" and the "payment control device" is an example of an "electronic payment system."

FIG. 2 is a diagram illustrating the general flow of electronic payment. There may be two patterns, pattern 1 and pattern 2, in electronic payment. In the case of pattern 1, the payment application 20 is first activated on the user terminal device 10 and displays a code image such as a QR code or barcode. The user holds (presents) the display surface of the user terminal device 10 over the store terminal device 50. The store terminal device 50 decodes the code image using an optical reading function and acquires information such as an account ID. Then, the store terminal device 50 generates payment information including an account ID, payment amount, store ID, etc., and transmits it to the payment server 100. Information on the payment amount is obtained in advance by barcode reading, manual input, etc. Based on the received information, the payment server 100 transfers the payment amount from the user's electronic payment account to the store's electronic payment account and completes the payment process.

In the case of pattern 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 using the optical reading function. The store code image 60 includes information such as the store name. The user inputs the payment amount into the user terminal device 10 on the screen displaying the store name and the like. Then, the user terminal device 10 generates payment information including an account ID, payment amount, store ID, etc., and transmits it to the payment server 100. The payment server 100 performs payment processing based on the received information. Note that electronic payment may be performed only in one of the above patterns. Further, the "account ID" described in FIG. 2 may be other information (for example, a telephone number) that can be used as user identification information.

The payment server 100 performs resale processing for resale via electronic commerce based on the resale registration information transmitted from the store terminal device 50. Further, the payment server 100 transmits a posting request to the EC server 300 requesting that the product to be resold be posted on the EC site. This resale process will be described later.

The delivery company server 200 performs product shipping processing in response to a shipping request from the payment server 100. Products that are subject to shipping processing by the delivery company server 200 are loaded onto a delivery company's vehicle or the like at the store and delivered to the specified delivery destination. Further, the delivery company server 200 generates a shipping QR code in response to a shipping QR code generation request from the payment server 100 and transmits it to the payment server 100. The shipping QR code is a code image that includes information such as the shipping destination. The delivery destination information may be a unique identification number that allows the delivery company to refer to delivery source information, delivery destination information, tracking number, and the like. The shipping QR code is an example of "information in which the shipping destination is anonymized."

The EC server 300 realizes electronic commerce of products sold by member stores of electronic commerce services (hereinafter referred to as "EC member stores"). The EC server 300 transmits product information to the user terminal device 10 and implements electronic commerce based on purchase information received from the user terminal device 10. The purchase information includes information regarding the product selected by the user for purchase, a method of paying for the purchase of the product, and the like. For example, the EC server 300 includes the function of a web server that configures the EC site of each EC member store. The EC server 300 may be a server for each EC member store for each EC member store to implement its own EC site, or a server for a so-called EC vendor that provides an EC site package to each EC member store. It may be a server operated by.

The EC server 300 performs a process of posting products to be resold on the EC site in response to a posting request sent from the payment server 100. Through this posting process, the product is posted on the EC site, and electronic commerce of the product becomes possible.

[Payment server]
FIG. 3 is a configuration diagram of the payment server 100. The payment server 100 cooperates with the payment application 20 to make payments for products that are subject to electronic payment. The payment server 100 includes, for example, a communication unit 110, an acquisition unit 115, a content provision unit 120, a payment processing unit 122, a delivery processing unit 124, an information management unit 126, a resale processing unit 128, and a storage unit 170. Equipped with. Components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components are hardware (circuit parts) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit). (including circuitry), or may be realized by collaboration between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage device such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium), and installed in the storage device by loading the storage medium into a drive device.

The storage unit 170 is an HDD, flash memory, RAM (Random Access Memory), or the like. The storage unit 170 may be a NAS (Network Attached Storage) device that can be accessed by the payment server 100 via a network. The storage unit 170 stores information such as user information 172, payment content information 174, store information 176, delivery pattern information 178, and resale registration information 180, for example.

The communication unit 110 is a communication interface for connecting to the network NW. Communication unit 110 is, for example, a network interface card.

The acquisition unit 115 acquires various information for realizing the electronic payment service from the user terminal device 10, the store terminal device 50, and the delivery company server 200, for example, via the communication unit 110. The acquisition unit 115 is an example of an “acquisition unit”. The acquisition unit 115 acquires resale registration information for products for which payment has been made through electronic payment.

The content providing unit 120 has, for example, the function of a web server, and provides the user terminal device 10 with information (content) for displaying various screens of the electronic payment service. The content providing unit 120 uses, for example, content for displaying various screens related to payment procedures, content for displaying various screens related to delivery procedures, and content for displaying various screens related to product repurchase. provided to the user terminal device 10. The content providing unit 120 reads necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 receives various inputs from the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100. The content providing unit 120 is an example of a “providing unit”.

The payment processing unit 122 performs payment processing based on payment information acquired from the user terminal device 10 or the store terminal device 50. The payment processing unit 122 performs payment processing while referring to the user information 172.

FIG. 4 is a diagram showing an example of the contents of the user information 172. User information 172 is an example of user registration information. The user information 172 includes, for example, an account ID (which may be omitted), in addition to the minimum phone number and password required for new registration, an email address, user ID, name, at least one address, and registration information. Information such as date, charge balance, bank account, credit card number, charge history information, payment history information, etc. are associated with each other. In the user information 172, information such as date of birth, other service collaboration information, radio wave authentication settings, carrier payment settings, chat friend list, chat history information, etc. may be associated with the account ID. Information other than the telephone number, password, at least one address, registration date, charge balance, charge history information, and payment history information is optional setting information. Hereinafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account. Note that the registration date is the date the user registered with the electronic payment service (the date the account was created).

A plurality of pieces of address information can be registered for at least one address. For example, any address such as the user's own address, the address of the user's workplace, or the address of a relative or friend of the user can be registered as at least one address. The charge balance is information indicating the balance of electronic money set by the user transferring money to the account in advance. Methods of remittance include remittance from an ATM (Automatic Teller Machine) of a designated business (bank), remittance from a registered bank account, etc. The bank account and credit card number are each information about a bank account or credit card number (account number, card number) that can be used to deposit money into the electronic payment service. The other service cooperation information is the login ID of another service (for example, operated by an operator belonging to the same business group) that cooperates with the electronic payment service. Radio wave authentication settings are setting information when performing authentication through communication with a specific communication carrier. The carrier payment setting is setting information for transferring at least a part of the payment using the electronic payment service to the communication carrier. The chat friend list is a list of other users with whom you can chat in the chat function provided by the electronic payment service. The charging history information is a history of the user increasing the charging balance by remitting money to the electronic payment service in advance. The payment history information is information that shows details of the payments made by the user (date and time, store ID of the store where the purchase was made, payment amount, etc.) for each payment. Chat history information is a history of the contents of chats conducted by users.

Information regarding stores is managed as store information 176. FIG. 5 is a diagram showing an example of the contents of the store information 176. The store information 176 is, for example, information such as a store category, location, payment pattern, delivery pattern, etc., associated with a store ID. The store category may be information of one level, or may be information having a hierarchical structure of two or more levels. For example, information such as "product store" may be provided as a superordinate concept of "souvenir store" shown in the figure. The location may be represented by hierarchical code information such as JIS code. The payment pattern is information indicating whether payment can be made using pattern 1 or pattern 2 described above. The delivery pattern is, for example, information indicating a delivery company. If one delivery company provides services using multiple delivery methods (for example, delivery in envelopes, delivery in packaging containers such as cardboard, delivery in frozen state, delivery with compensation functions, etc.), The delivery pattern may be, for example, a combination of a delivery company and a delivery method.

FIG. 6 is a diagram showing an example of the contents of the delivery pattern information 178. The delivery pattern information 178 includes, for example, the name of the delivery company, the delivery method (if multiple delivery methods exist), and a predetermined fixed delivery charge (for example, the maximum value of the delivery charge) for each delivery pattern. , maximum shipping charge) are associated with each other. Delivery pattern 1 is associated with "delivery company A" and "maximum delivery charge ("1200" yen)" set by delivery company A. Delivery pattern 2 is associated with "delivery company B" and "maximum delivery charge ("1000" yen)" set by delivery company B.

The delivery processing unit 124 performs product delivery processing based on information acquired from the user terminal device 10, the store terminal device 50, and the delivery company server 200. The delivery processing unit 124 also transmits a request to generate a shipping QR code to the delivery company server 200 and acquires the shipping QR code from the delivery company server 200.

The information management unit 126 creates a new record of the user information 172 or updates each data item in an already created record based on information acquired from the user terminal device 10 or the store terminal device 50. .

The resale processing unit 128 stores information on products to be resold in the storage unit 170 as resale registration information 180 based on the resale registration information transmitted from the store terminal device 50 or the user terminal device 10, and A posting request is sent to the EC server 300. The resale processing unit 128 is an example of a “resale processing unit”. The resale processing unit 128 performs resale processing of products to be resold (products for which payment has been completed) via electronic commerce based on the resale registration information.

FIG. 7 is a diagram showing an example of the contents of the resale registration information 180. The resale registration information 180 includes, for example, the payment number (or the combination of payment number and store ID), product group name, product details, image, price, quantity in stock, location (resale method), Specified Commercial Transactions Law ( Specified Commercial Transactions Act) information is associated with this information.

[Payment app]
FIG. 8 is a diagram illustrating an example of a functional unit implemented by the payment application 20. For example, when a processor such as the CPU of the user terminal device 10 executes the payment application 20, the information management section 22, information processing section 24, reception section 26, and setting section 28 are realized, for example.

The information management unit 22 uses the communication unit of the user terminal device 10 to transmit information to the payment server 100 and obtain information transmitted from the payment server 100. The information processing section 24 cooperates with the payment server 100 to display various contents on the display section of the user terminal device 10. The information processing unit 24 displays the content provided by the payment server 100 on the display unit of the user terminal device 10.

The reception unit 26 receives user operations. For example, when a button included in the content is operated by a user, the reception unit 26 accepts the operation. The setting unit 28 performs various settings according to the operation received by the reception unit 26. Details of these will be described later.

[Payment, delivery, and resale registration processing 1]
Hereinafter, a description will be given of the process when a user purchases a product using the electronic payment (user scan) of Pattern 2 described above, and performs delivery procedures and resale registration. In this process, for example, if a payment company (payment server 100) that provides an electronic payment service stores the user's address in advance, and the user wishes to have the product delivered along with payment at a member store of the payment company, A payment company (payment server 100) issues an anonymous shipping QR code in cooperation with a delivery company (delivery company server 200), and links the affiliated store where the user purchased the shipping QR code. FIG. 9 is a sequence diagram showing the flow of processing for purchasing products, shipping procedures, and resale registration using electronic payment in pattern 2. FIG. 10 is a diagram showing an example of screen transitions of the user terminal device 10 during electronic payment of pattern 2.

First, the information management unit 22 of the user terminal device 10 reads the store code image 60 using the optical reading function based on the user's operation (step S101). The information management unit 22 decodes the read store code image 60 to obtain information for identifying the store (for example, store name, store ID, etc.). Next, the information management unit 22 uses the acquired store ID to transmit a request for store information to the payment server 100 (step S102).

Next, the content providing unit 120 of the payment server 100 uses the store ID included in the store information request received from the user terminal device 10 to store the store information associated with this store ID in the storage unit 170. is read from the store information 176 and transmitted to the user terminal device 10 (step S103).

Next, the information processing unit 24 of the user terminal device 10 uses the store information received from the payment server 100 to display the product information input screen P1 on the display unit of the user terminal device 10 (step S104). As shown in FIG. 10, this product information input screen P1 includes, for example, an area A1 that displays the store name, an area A2 that accepts the input of the payment amount for the item, and an area A3 that accepts instructions regarding the necessity of delivery (for example, , a radio button that accepts a selection of ``Delivery required'' or ``Delivery not required''), and an area that accepts a payment instruction (``Pay'' button B1). When the user inputs the payment amount for the product to be purchased in area A2, inputs an instruction as to whether delivery is required in area A3, and presses button B1, the information management unit 22 inputs the input payment amount, The product payment information including the account ID, store ID, etc., and the input delivery necessity information are transmitted to the payment server 100 (step S105). Product payment information is an example of "first payment information."

The payment processing unit 122 of the payment server 100 makes payment for the product based on the product payment information received from the user terminal device 10 (step S106). The payment for this product is made to the store where the payment destination (payment destination) is the store. The payment processing unit 122 performs payment for the product while referring to the user information 172.

When the delivery necessity information received from the user terminal device 10 indicates that delivery is not necessary, the content providing unit 120 transmits a payment completion notification for the product to the user terminal device 10 (step S107). Accordingly, the information processing unit 24 of the user terminal device 10 causes the display unit to display the product payment completion screen P4. As shown in FIG. 10, the product payment completion screen P4 notifies the user that payment for the product has been completed.

On the other hand, if the delivery necessity information received from the user terminal device 10 indicates that delivery is required, the content providing unit 120 transmits a payment completion notification for the product and delivery information to the user terminal device 10. (Step S107). The delivery information includes, for example, the payment pattern and delivery pattern read from the store information 176, the name of the delivery company and the maximum delivery charge read from the delivery pattern information 178, and at least one item read from the user information 172. This includes two addresses (address 1, address 2, etc.). The information processing unit 24 of the user terminal device 10 uses the delivery information received from the payment server 100 to display the delivery information input screen P2 on the display unit of the user terminal device 10 (step S108).

As shown in FIG. 10, this delivery information input screen P2 notifies the user that payment for the product has been completed and also guides the user to input delivery information. This delivery information input screen P2 includes, for example, an area A4 (a radio button that accepts an instruction to select "delivery company A" or "delivery company B") that accepts an instruction to select a delivery method included in the delivery information, and An area A5 that displays the estimated amount, an area A6 that displays the delivery destination, an area that accepts instructions to change the delivery destination (“>Change” button B2), and an area that accepts payment instructions (“Pay” button B3). and are included. In area A4, the name of the "delivery company" (or the combination of "delivery company" and "delivery method") read from the delivery pattern information 178 is displayed. The estimated delivery amount displayed in area A5 is the same as the maximum delivery charge read from delivery pattern information 178. Note that the estimated delivery amount may be configured such that the user can manually set (or change) the amount by setting an input form in area A5. In area A5, the corresponding maximum shipping fee is displayed according to the selection of the shipping method accepted in area A4. The delivery destination displayed in area A6 is any one of at least one address (address 1, address 2, etc.) read from the user information 172.

When the “>Change” button B2 is pressed on the delivery information input screen P2 shown in FIG. 10, the information processing unit 24 causes the display unit to display a delivery destination change screen for receiving an instruction to change the delivery destination. . On the delivery destination change screen, for example, a list of delivery destinations (address 1, address 2, etc.) included in the delivery information is displayed, and an instruction for selecting a delivery destination can be received from the user. When the user presses button B3 on the delivery information input screen P2, the information management unit 22 stores delivery instruction information including the delivery destination, account ID, store ID, etc., and the specified delivery pattern (delivery company, delivery method, delivery payment information instructing payment of the delivery fee to the delivery company, including the maximum delivery fee), is transmitted to the payment server 100 (step S109). The delivery payment information is an example of "second payment information."

Next, the payment processing unit 122 of the payment server 100 makes a provisional payment for the delivery fee based on the delivery payment information received from the user terminal device 10 (step S110). This provisional payment of shipping charges is a payment made to a delivery company whose payment destination (payee) is the delivery company. The payment processing unit 122 makes a provisional payment for the delivery fee while referring to the user information 172. The provisional payment is used here because the "estimated delivery amount (maximum delivery charge)" is used as the delivery charge. That is, in this provisional payment, the payment is made at an amount that is greater than the actual delivery fee determined at the time of collection by the delivery company. For payments based on the actual shipping charges determined at the time of pickup by the delivery company (main payment), the "estimated delivery amount (maximum shipping charge)" should be updated with the "actual shipping charge", or the difference between the two should be updated. A confirmation process will be performed to refund the money to the user. In the provisional payment, for example, the payment processing unit 122 provisionally subtracts the "estimated delivery amount (maximum delivery charge)" from the charge balance in the user information 172, and blocks this payment until the final payment (payment is confirmed) or cancellation. The block validity period is set to a predetermined period. Thereafter, the payment processing unit 122 subtracts the difference between the estimated delivery amount (maximum delivery charge) and the actual delivery charge from the blocked charge balance, and completes the payment without requiring any action by the user. determine. At this time, the delivery company (delivery company server 200, a terminal device used by the delivery person, etc.) sends information such as a tracking number that can identify the issued QR code, as well as the actual delivery fee to the payment server 100 side. Payment server 100 finalizes payment based on the actual shipping charges received. The payment processing unit 122 cooperates with the delivery company server 200 to send delivery fee payment information.

Next, the delivery processing unit 124 of the payment server 100 transmits a request to generate a shipping QR code to the delivery company server 200 along with delivery instruction information (step S111). For example, the delivery processing unit 124 requests the generation of a shipping QR code using an API (Application Programming Interface) for delivery cooperation provided by a delivery company. The delivery company server 200 generates a shipping QR code in response to the received shipping QR code generation request and transmits it to the payment server 100 (step S112). Additionally, the delivery company server 200 may also send the delivery date (scheduled delivery date), delivery slip number (delivery number), etc. to the payment server 100.

The content providing unit 120 of the payment server 100 transmits a payment completion notification for the delivery fee to the user terminal device 10 (step S113). The information processing unit 24 of the user terminal device 10 causes the product and delivery payment completion screen P3 to be displayed on the display unit of the user terminal device 10 (step S114). As shown in FIG. 10, the product and delivery payment completion screen P3 includes, for example, an area A6 that displays the total amount of the product payment amount and delivery fee (estimated delivery amount) and its details. The user can confirm the payment amount by checking the delivery payment completion screen P3. Note that when the delivery slip number (delivery number) issued by the delivery company server 200 is received from the payment server 100, the information processing unit 24 of the user terminal device 10 displays the delivery slip number on the delivery payment completion screen P3. (Delivery number) may be displayed.

Thereafter, for example, a store clerk operates the store terminal device 50 to ship the product. The store terminal device 50 transmits a request for a shipping list of products to be shipped to the payment server 100 based on the operation of the store clerk (step S115). The payment server 100 transmits the shipping list to the store terminal device 50 in response to the request for the shipping list received from the store terminal device 50 (step S116). The store terminal device 50 generates a shipping management screen based on the shipping list received from the payment server 100, and displays it on the display section of the store terminal device 50 (step S117).

FIG. 11 is a diagram showing an example of a shipping management screen displayed on the store terminal device 50. As shown in FIG. 11, a shipping list is displayed on the shipping management screen. In this shipping list, information such as payment time, payment amount, shipping status, resale registration, etc. is associated with the payment number that identifies each payment. As the payment amount, the payment amount for the product, the payment amount for shipping charges, the total amount of both, etc. may be displayed. If the payment for the product and the shipping fee are made separately, the payment number for identifying the payment for the shipping fee may be displayed in association with the payment number for identifying the payment for the product.

For example, "unshipped", "shipped", "in progress", "delivery completed", etc. are displayed as the shipping status. Items that are "unshipped" are associated with a "shipping arrangement" button B4 for making shipping arrangements. When the store clerk presses the "shipping arrangement" button B4, the store terminal device 50 displays a shipping arrangement screen on the display section of the store terminal device 50. FIG. 12 is a diagram showing an example of a shipping arrangement screen. As shown in FIG. 12, the shipping arrangement screen displays a slip (QR code for shipping), scheduled pickup date, shipping status, and the like. On the shipping arrangement screen, a "print slip" button B6 for instructing printing of the shipping QR code on the delivery slip is displayed. When the clerk presses the "Print this slip" button B6, the store terminal device 50 causes a printing device such as a printer to print the delivery slip S (step S118). On this delivery slip S, information such as a shipping QR code, delivery destination (delivery destination), client (store), etc. is printed. Here, since characters indicating the delivery destination are not printed on the delivery destination (delivery destination), the information on the delivery destination can be anonymized (concealed). This prevents store staff from knowing information about the delivery destination. The store clerk attaches the delivery slip S to the packaged product and hands it over to the delivery company, thereby completing the delivery procedure. By reading the information of this shipping QR code using a dedicated device, the delivery company can obtain information regarding the delivery destination and carry out the delivery work.

For resale registration, for example, "unregistered", "registered", etc. are displayed. For items that are "unregistered", a "resale registration" button B5 for registering the product for resale is displayed in association with the item. When the store clerk presses this "Resale Registration" button B5, the store terminal device 50 displays a resale registration screen on the display section of the store terminal device 50.

FIG. 13 is a diagram showing an example of a resale registration screen. As shown in FIG. 13, the resale registration screen accepts input or designation of various information necessary for resale registration. On the resale registration screen, for example, information such as ``product group,'' ``product details,'' ``photo,'' ``price,'' ``quantity in stock,'' ``place of publication,'' and ``Special Commercial Transaction Law'' are displayed in association with the payment number. Input reception areas such as forms, radio buttons, check boxes, etc. for inputting or specifying information, "Take photo" button B7-1, "Upload photo" button B7-2, "Resale registration" button B8, etc. Is displayed. The "Product Group" column accepts input of information such as the category of the product to be resold. The "Product Details" field accepts input of information on products to be resold. If the store terminal device 50 is a smartphone, for example, when the "take photo" button B7-1 is pressed, the camera installed in the terminal is activated, and an image of the product to be resold can be taken. When the "upload photo" button B7-2 is pressed, a photo of the product to be resold can be selected from among the photos stored in the store terminal device 50 in advance and uploaded. The "Price" column accepts a selection instruction as to whether or not to set the same price as the current sale price as the resale price. If "set separately" is selected, instead of setting the same price as last time, input of that price is also accepted. The "Quantity in Stock" column accepts input of the number of products in stock (sellable quantity) for resale. The "Publication Place" column accepts the designation of the resale method (for example, "Transaction History", "Site A", "Site B"). When "transaction history" is specified, resale is possible from the transaction history screen displayed on the user terminal device 10 by executing the payment application 20. When "Site A" and/or "Site B" is specified, resale at the specified EC site is possible. Resale from the transaction history screen and resale on an EC site are examples of "resale processing via electronic commerce." The "Specified Commercial Transaction Law" column accepts specifications of information on the Specified Commercial Transaction Law to be used in resale.

On the resale registration screen as shown in FIG. 13, when the store clerk inputs or specifies various information and presses the "Resale Registration" button B8, the store terminal device 50 transmits the resale registration information to the payment server 100 (step S119).

Next, the resale processing unit 128 of the payment server 100 registers various information included in the resale registration information in the resale registration information 180 (step S120). Next, the resale processing unit 128 transmits a posting request for a product to be resold to the EC server 300 based on the "posting place" information included in the resale registration information (step S121). In response to the posting request, the EC server 300 performs a process of posting the product to be resold on the EC site (step S122). As a result, the product to be resold is posted on the designated EC site, and the user can subsequently purchase the same product. With the above steps, the processing of this sequence diagram is completed. Note that the product purchase page on the EC site may be configured to be viewable only by users who have a history of purchasing the same product. Alternatively, the resale product purchase page on the EC site may be configured to be viewable by other general users. In this case, in order to avoid a rush of orders, it may be possible to set sales conditions such as the sales area. For example, the resale registration screen shown in FIG. 13 may be configured to accept the specification of sales conditions on the EC site, and to restrict sales on the EC site based on the sales conditions.

In the above example, a configuration was described in which an instruction as to whether or not delivery is necessary is received on the product information input screen P1, but the present invention is not limited to this. For example, instead of accepting instructions on whether delivery is necessary on the product information input screen P1, instructions on whether delivery is necessary may be accepted on a screen that notifies completion of payment for the product (for example, delivery information input screen P2). In addition, the store has a normal store code image 60 (store code image 60 that does not require delivery) and a store code image 60 for delivery, and a user who desires delivery can use the store code image 60 for delivery. By scanning the , a separate process for instructing whether or not delivery is necessary may be omitted.

In the above example, a configuration was described in which the payment for the product and the payment for the shipping fee are performed separately, and the shipping fee is directly paid to the shipping company in cooperation with the shipping company server 200. However, the present invention is not limited to this. do not have. For example, shipping charges may also be paid to the store once. Furthermore, when making a payment for a product, the user may enter the total amount including shipping charges. In this case, there is no need to acquire the delivery method (store information) linked to the store in steps S102 and 103 in the above process, or to make individual payments for the delivery fee. Further, the store clerk informs the user of the expected maximum shipping amount, and the user inputs the maximum shipping amount plus the amount of the product. In addition, in this case, on the payment server 100 side, the shipping fee (for example, maximum shipping fee) stored in the shipping pattern linked to the store is the amount calculated by subtracting the shipping fee from the total amount as a payment for the shipping company. is a payment targeted at a store.

[Payment, delivery, and resale registration processing 2]
Hereinafter, a description will be given of a process when a user purchases a product using the above-described pattern 1 electronic payment (store scan) and performs delivery procedures and resale registration. In this process, for example, if a payment company (payment server 100) that provides an electronic payment service stores the user's address in advance, and the user wishes to have the product delivered along with payment at a member store of the payment company, A payment company (payment server 100) issues an anonymous shipping QR code in cooperation with a delivery company (delivery company server 200), and links the affiliated store where the user purchased the shipping QR code. FIG. 14 is a sequence diagram showing the flow of processing for purchasing products, shipping procedures, and resale registration using electronic payment in pattern 1. Compared to the payment, delivery, and resale registration process 1 shown in FIG. (hereinafter, steps S201 to S203) are different. In the following, the differences from this payment, delivery, and resale registration processing 1 will be mainly explained, and the explanation of the common points will be omitted.

First, the information processing section 24 of the user terminal device 10 displays a code reading screen including a code image on the display section of the user terminal device 10 based on the user's operation (step S201). For example, a QR code or barcode is displayed on this code reading screen. The user presents this code screen to the clerk and verbally tells the clerk whether or not delivery is required.

The store clerk reads the code image displayed on the code reading screen using the optical reading function of the store terminal device 50 (step S202). The store terminal device 50 decodes the read code image and obtains information for identifying the user (eg, account ID, telephone number, etc.). Next, the store terminal device 50 stores information identifying the acquired user, product payment information including the payment amount for the product set based on the store clerk's operation, and delivery information set based on the store clerk's operation. The necessity information is transmitted to the payment server 100 (step S203).

The payment processing unit 122 of the payment server 100 performs payment for the product based on the received product payment information (step S106). Thereafter, the processing of steps S107 to S122 in the above-described payment, delivery, and resale registration processing 1 is performed. With the above steps, the processing of this sequence diagram is completed.

In the above example, a configuration has been described in which the store clerk sets whether delivery is necessary or not based on information about whether delivery is necessary orally conveyed from the user, but the present invention is not limited to this. For example, the necessity of delivery can be selected on the user terminal device 10 side according to the user's operation, and a corresponding code image can be displayed on the code screen P6 and read by the optical reading function of the store terminal device 50. , a configuration may be adopted in which delivery necessity information is automatically transmitted to the payment server 100 side together with payment information without verbally conveying the necessity or necessity of delivery.

In the above example, a configuration was described in which the payment for the product and the payment for the shipping fee are performed separately, but the present invention is not limited to this. For example, a store clerk may accept a request for delivery from a user at the time of purchase, and then pay the amount including the delivery fee. In this case, in the process of step S109, the user only sets the delivery destination. Further, an instruction as to whether or not delivery is necessary may be received on a screen that notifies completion of payment for a product (for example, delivery information input screen P2). In this case, on the payment server 100 side, the shipping fee (for example, the maximum shipping fee) stored in the shipping pattern associated with the store is calculated as a payment for the shipping company, and the shipping fee is excluded from the total amount. The amount will be used as a payment for the store.

[Repurchase process]
Below, we will explain the process when a user repurchases a product purchased in the past at a physical store. This process will be described using an example in which the user makes a repurchase from the transaction history screen displayed on the user terminal device 10 when the payment application 20 is executed. FIG. 15 is a sequence diagram showing the flow of repurchase processing.

First, when the user operates the user terminal device 10 to launch the payment application 20 and instruct a transition to the transaction history screen, the user terminal device 10 sends a transaction history request to the payment server 100. (Step S301). The content providing unit 120 of the payment server 100 refers to the user information 172 and resale registration information 180 stored in the storage unit 170, and transmits transaction history information and resale availability information to the user terminal device 10 (step S302 ). The resale availability information indicates whether or not a paid product can be resold. For example, the resale permission information indicates that a product registered in the resale registration information 180 can be resold, and a product not registered in the resale registration information 180 cannot be resold.

Next, the information processing unit 24 of the user terminal device 10 displays a transaction history screen on the display unit of the user terminal device 10 based on the transaction history information and resale availability information received from the payment server 100 (step S303). ). 16A and 16B are diagrams showing an example of a transaction history screen P5 displayed on the user terminal device 10. By operating the "Transaction History" tab T1 and the "Repurchase" tab T2 displayed on the transaction history screen P5, the user displays a screen showing the transaction history shown in FIG. 16A and a repurchase instruction shown in FIG. 16B. It is possible to switch between the screen and the screen for accepting messages. On the screen shown in FIG. 16A, past transactions are displayed for each payment, and for transactions where repurchase is possible, a message saying "You can repurchase" is also displayed. The repurchase screen shown in Figure 16B displays information about products that can be repurchased from past transactions (payment number, product group name, product information, price, etc.) and the "Repurchase" screen that accepts repurchase instructions. ” button B9 is displayed.

When the "Repurchase" button B9 is pressed on the repurchase screen shown in FIG. 16B, the user terminal device 10 transmits a repurchase request to the payment server 100 (step S304). This repurchase request includes information about the product to be repurchased (payment number, product group name, product information, price, quantity, etc.).

Next, in order to obtain the latest product inventory and price information, the resale processing unit 128 of the payment server 100 transmits an inventory and price confirmation request to the store terminal device 50 (step S305). In response to the inventory and price confirmation request, the store terminal device 50 transmits information on the inventory and latest price of the product to be repurchased that is currently registered in its own device, etc. to the payment server 100 (step S306). .

Next, the content providing unit 120 of the payment server 100 transmits the inventory and price information of the product to be repurchased to the user terminal device 10 (step S307). The information processing unit 24 of the user terminal device 10 displays the inventory and price confirmation screen P6 on the display unit of the user terminal device 10 based on the inventory and price information received from the payment server 100 (step S308). FIG. 17 is a diagram showing an example of the inventory and price confirmation screen P6. This stock and price confirmation screen P6 displays information indicating whether the product is in stock, and if the product is in stock, the latest price and a "purchase again" button B10 that accepts a repurchase instruction.

When the "Purchase again" button B10 is pressed on the inventory and price confirmation screen P6, the information management unit 22 of the user terminal device 10 transmits product payment information and delivery necessity information to the payment server 100. (Step S309). At this repurchase stage, it is assumed that the user of the user terminal device 10 is performing the repurchase procedure from a location different from the actual store selling the same product, so the delivery necessity information is "Kanma".

Thereafter, the same product payment process, shipping fee payment process, and shipping process as in steps S106 to S118 shown in FIG. 9 are performed. First, the payment processing unit 122 of the payment server 100 makes payment for the product based on the product payment information received from the user terminal device 10 (step S106). The payment for this product is made to the store where the payment destination (payment destination) is the store. The payment processing unit 122 performs payment for the product while referring to the user information 172. Next, the content providing unit 120 of the payment server 100 transmits a notification of completion of payment for the product and delivery information to the user terminal device 10 (step S107).

The information processing unit 24 of the user terminal device 10 uses the delivery information received from the payment server 100 to display, for example, the delivery information input screen P2 shown in FIG. 10 on the display unit of the user terminal device 10 (step S108 ). When the user presses button B3 on the delivery information input screen P2, the information management unit 22 stores delivery instruction information including the delivery destination, account ID, store ID, etc., and the specified delivery pattern (delivery company, delivery method, delivery payment information instructing payment of the delivery fee to the delivery company, including the maximum delivery fee), is transmitted to the payment server 100 (step S109).

Next, the payment processing unit 122 of the payment server 100 makes a provisional payment for the delivery fee based on the delivery payment information received from the user terminal device 10 (step S110). This provisional payment of shipping charges is a payment made to a delivery company whose payment destination (payee) is the delivery company. The payment processing unit 122 makes a provisional payment for the delivery fee while referring to the user information 172. Next, the delivery processing unit 124 of the payment server 100 transmits a request to generate a shipping QR code to the delivery company server 200 along with delivery instruction information (step S111). The delivery company server 200 generates a shipping QR code in response to the received shipping QR code generation request and transmits it to the payment server 100 (step S112). The content providing unit 120 of the payment server 100 transmits a payment completion notification for the delivery fee to the user terminal device 10 (step S113). The information processing unit 24 of the user terminal device 10 displays the product and delivery payment completion screen P3 shown in FIG. 10 on the display unit of the user terminal device 10 (step S114).

Thereafter, for example, a store clerk operates the store terminal device 50 to ship the product. The store terminal device 50 transmits a request for a shipping list of products to be shipped to the payment server 100 based on the operation of the store clerk (step S115). The payment server 100 transmits the shipping list to the store terminal device 50 in response to the request for the shipping list received from the store terminal device 50 (step S116). The store terminal device 50 generates a shipping management screen based on the shipping list received from the payment server 100, and displays it on the display section of the store terminal device 50 (step S117). On the shipping arrangement screen, a "print slip" button B6 for instructing printing of the shipping QR code on the delivery slip is displayed, and when the store clerk presses this button B6, the store terminal device 50 prints the QR code for printing on the delivery slip. The printing device is caused to print the delivery slip S (step S118). The store clerk attaches the delivery slip S to the packaged product and hands it over to the delivery company, thereby completing the delivery procedure. By reading the information of this shipping QR code using a dedicated device, the delivery company can obtain information regarding the delivery destination and carry out the delivery work.

In addition, if the product targeted for resale is posted on an EC site, the resale processing unit 128 of the payment server 100 calculates the number of items in stock of the same product registered on the EC site and the resold product. A process of subtracting by the number of is performed (step S310). For example, the resale processing unit 128 transmits an inventory update instruction to the EC server 300. As a result, the inventory quantity managed on the EC site side is updated. With the above steps, the processing of this flowchart is completed.

That is, the content providing unit 120 provides the user terminal device 10 with the transaction history information of the settled product and the resale availability information of the settled product, and the acquisition unit 115 provides the transaction history information of the settled product and the resale availability information of the settled product, and the acquisition unit 115 provides the transaction history information of the settled product and the resale availability information of the settled product. The resale processing unit 128 obtains a resale request input by the user of the user terminal device 10 on the screen displayed on the user terminal device 10, and, in response to the resale request, Process the resale of products.

In response to a resale request, the acquisition unit 115 acquires updated information on inventory and prices of paid products from the store terminal device 50, and the content providing unit 120 acquires updated information acquired from the store terminal device 50 of the physical store. is provided to the user terminal device 10. The acquisition unit 115 acquires resale registration information from the store terminal device 50 or the user terminal device 10 of the physical store. The resale registration information includes at least information on the content and price of the paid product.

The resale processing unit 128 performs processing for registering (posting) paid products in the electronic commerce service based on the resale registration information. The resale registration information includes at least information on the resale method for the paid product, and the resale processing unit 128 performs processing to register the paid product in an electronic commerce service according to the resale method. The resale processing unit 128 performs a process of updating the inventory quantity of the paid products managed by the electronic commerce service after the payment for the resale of the paid products is completed.

In the above example, a configuration has been described in which a product can be repurchased through processing on a screen displayed when the payment application 20 is executed, but the present invention is not limited to this. For example, if a product targeted for resale is posted on an EC site, when the "Purchase again" button B9 is pressed on the repurchase screen shown in Figure 16B, the product purchase on the EC site side is You may also make the transition to a screen. Thereafter, resale processing, delivery processing, etc. may be performed on the EC site side.

In addition, instead of or in addition to performing resale registration according to resale registration information from the store terminal device 50, the user can, for example, register at a physical store (payment A receipt issued when purchasing a product at a company's member store) is read and sent to the payment server 100, and the payment server 100 analyzes the information on the receipt to determine the product and price, and registers it in the resale registration information 180. It may be a configuration. In addition, although the system is such that products registered for resale by physical stores can be repurchased, a user can, for example, send a repurchase request by operating the user terminal device 10 (payment application 20). A configuration may also be adopted in which the physical store that receives the product checks the inventory, presents the price, and makes the purchase. In this way, prices can be presented to users from the physical store side. In this case, since it takes time from the repurchase request to the payment, for example, if a user previously purchased a certain product for 5,000 yen, the user may decide to purchase the same product for up to 7,000 yen. Payment processing (payment suspension) is carried out (specification of price range is accepted in advance), and if the physical store has the same product that can be sold within the range of 7,000 yen, it links the price to the payment server 100. A configuration may be adopted in which the shipping process is carried out, and when the item is shipped, only the determined amount is paid, and the remaining amount is refunded to the user.

Furthermore, instead of a delivery company delivering the products, for example, an individual registered with the matching arrangement service may undertake the delivery of the products. In this case, the payment server 100 provides information such as the pick-up location (receipt location), delivery destination, and reservation time of the product to the individual undertaking the delivery via a dedicated application for the matching arrangement service. The payment server 100 receives an ID for identifying the delivery person from the matching arrangement service, and cooperates with the member store and the user. The location of the delivery person may be confirmed on the payment application 20 of the user terminal device 10 or on the store terminal device 50.

According to the embodiment described above, it is possible to repurchase products purchased at a physical store. Since the user can easily identify and repurchase products previously purchased at a physical store, the convenience of repurchasing can be improved. In addition, since physical stores can resell products simply by registering information for resale, they can sell products through electronic commerce with simple procedures.

Moreover, a part or all of each of the above-described processes and each embodiment may be executed in combination. Further, part or all of the processing executed in the payment application 20 may be executed by the payment server 100 or by another device. Part or all of the processing executed in the payment server 100 may be executed by the payment application 20 or by another device. For example, part or all of the functional configuration of the payment application 20 or the payment server 100 may be distributed among multiple devices. Furthermore, the information stored in the storage unit 170 of the payment server 100 may also be stored in the user terminal device 10.

Although the mode for implementing the present invention has been described above using embodiments, the present invention is not limited to these embodiments in any way, and various modifications and substitutions can be made without departing from the gist of the present invention. can be added.

10 User terminal device 20 Payment application 50 Store terminal device 60 Store code image 100 Payment server 110 Communication section 115 Acquisition section 120 Content provision section 122 Payment processing section 124 Delivery processing section 126 Information management section 128 Resale processing section 170 Storage section 172 Usage customer information 174 payment content information 176 store information 178 delivery pattern information 180 resale registration information 200 delivery company server 300 EC server

Claims (8)

In an electronic payment service that allows electronic payments to be made using a terminal device at a physical store, a payment control device that performs payment for products subject to the electronic payment, comprising:
an acquisition unit that acquires resale registration information including information on the contents of products for which payment has been made in the electronic payment from a store terminal device of the physical store or the terminal device ;
a resale processing unit that performs resale processing of the settled product via electronic commerce by performing a process of registering the settled product included in the resale registration information in an electronic commerce service;
A payment control device comprising: further comprising a providing unit that provides transaction history information of the settled product and resale availability information of the settled product to the terminal device,
The acquisition unit acquires a resale request input by a user of the terminal device on a screen displayed on the terminal device based on the transaction history information and the resale availability information,
The resale processing unit performs resale processing of the settled product via the electronic commerce in response to the resale request.
The payment control device according to claim 1. The acquisition unit acquires inventory and price update information of the settled product from a store terminal device of the physical store in response to the resale request;
The providing unit provides the update information acquired from the store terminal device to the terminal device.
The payment control device according to claim 2. The resale registration information further includes information on the price of the settled product.
The payment control device according to any one of claims 1 to 3 . The resale registration information further includes information on a resale method for the settled product,
The resale processing unit performs a process of registering the settled product in an electronic commerce service according to the resale method.
The payment control device according to any one of claims 1 to 4 . The resale processing unit performs a process of updating the inventory quantity of the paid product managed by the electronic commerce service after the payment for resale of the paid product is completed.
The payment control device according to claim 5 . An application program for providing an electronic payment service that allows electronic payments to be made using a terminal device at a physical store;
a payment control device that is capable of communicating with a store terminal device of the physical store and the terminal device, and that performs payment for products subject to the electronic payment;
An electronic payment system comprising:
The payment control device includes:
an acquisition unit that acquires resale registration information including information on the contents of products for which payment has been made in the electronic payment from the store terminal device or the terminal device ;
a resale processing unit that performs resale processing of the settled product via electronic commerce by performing a process of registering the settled product included in the resale registration information in an electronic commerce service;
Equipped with
Electronic payment system. A payment control method using a payment control device that performs payment for products subject to electronic payment in an electronic payment service that allows electronic payment to be performed using a terminal device at a physical store, the method comprising:
The computer of the payment control device,
Obtaining resale registration information including information on the content of the product for which payment has been made in the electronic payment from the store terminal device of the physical store or the terminal device ;
performing a process of registering the paid item included in the resale registration information in an electronic commerce service , thereby reselling the paid item via electronic commerce;
Payment control method.

Images