JP7394259B1 - Electronic commerce device, payment management device, electronic commerce system, electronic commerce method, and program - Google Patents

Abstract

An object of the present invention is to provide an electronic commerce device, a payment management device, an electronic commerce system, an electronic commerce method, and a program that can timely convey information on the transition destination of a social login service. [Solution] An electronic commerce device that provides electronic commerce services to users, which includes a content providing unit that provides content of the electronic commerce services to user terminal devices, and manages information including images used in the content. a management unit, the management unit acquires information including additional information that changes over time regarding the electronic payment service from a payment management device that provides an electronic payment service that allows payment in the electronic commerce service; An electronic commerce device that causes a user terminal device to display a login method selection screen including an image based on additional information when a content request in a logged-off state is obtained from the user's terminal device. [Selection diagram] Figure 7

Description

The present invention relates to an electronic commerce device, a payment management device, an electronic commerce system, an electronic commerce method, and a program.

In electronic commerce services, social login services provided by various electronic payment services are used. E-commerce services often allow users to use multiple social login services. Authentication APIs are sometimes used in social login services, and Patent Document 1 describes this.

Patent No. 7085700

With conventional technology, there have been cases in which information about the transition destination of the social login service cannot be conveyed in a timely manner.

The present invention has been made in consideration of such circumstances, and provides an electronic commerce device, a payment management device, an electronic commerce system, an electronic commerce method, and a payment management device that can timely convey information on the transition destination of a social login service. One of the purposes is to provide programs.

One aspect of the present invention is an electronic commerce device that provides an electronic commerce service to a user, which includes a content providing unit that provides content of the electronic commerce service to a user terminal device of the user, and an image used for the content. a management unit that manages information including information, the management unit acquires information including additional information that changes over time regarding the electronic payment service from a payment management device that provides an electronic payment service that allows payment in the electronic commerce service. The content providing unit is an electronic commerce device that causes the user terminal device to display a login method selection screen including an image based on additional information when a content request in a logged-off state is obtained from the user terminal device.

According to one aspect of the present invention, it is possible to provide an electronic commerce device, a payment management device, an electronic commerce system, an electronic commerce method, and a program that can timely convey information on the transition destination of a social login service.

1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. FIG. 1 is a sequence diagram (Part 1) illustrating the general flow of electronic payment. FIG. 2 is a sequence diagram (Part 2) illustrating the general flow of electronic payment. FIG. 1 is a configuration diagram of a payment server 100 according to a first embodiment. 3 is a diagram showing an example of the contents of user information 132. FIG. It is a diagram showing an example of the contents of member store/store information 136. This is an example of a configuration for realizing the electronic commerce system 1. It is a table showing an example of the contents of EC user information 254. It is a figure which shows an example of a display of a login method selection screen. It is a figure showing an example of screen transition when a user's login status is not logged in. This is an example of screen transition when the user's login status is “logged in”. 2 is a sequence diagram showing an example of the flow of login status confirmation processing of the electronic commerce system 1. FIG. 2 is a sequence diagram illustrating an example of the flow of processing for acquiring and displaying additional information in the electronic commerce system 1. FIG. 2 is a sequence diagram showing an example of the flow of login processing of the electronic commerce system 1. FIG.

EMBODIMENT OF THE INVENTION Hereinafter, embodiments of an electronic commerce device, a payment management device, an electronic commerce system, an electronic commerce method, and a program of the present invention will be described with reference to the drawings. The various devices mentioned below, such as "servers," "management devices," and "information providing devices," that provide services to users and perform internal analysis are realized by a group of decentralized devices. Often, the operators operating each device may be different. Furthermore, the owner of the device hardware (cloud server provider) and the operator that actually operates the device may be different. The application program and the payment server work together to provide electronic payment services. In the following description, the application program will be referred to as a payment application. An electronic payment service is a service that supports payments for purchases of products and services at stores. A store is, for example, a physical store (actual store) that exists in real space, but may also include a virtual store for electronic commerce. Virtual stores may include those provided by entities different from the operator of the electronic payment service. In this case, when paying for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to a member store (brand), for example, and processing such as payment when a purchase is made at a store is mainly performed between a user and the member store. Alternatively, processing such as payment may be performed between the user and the store.

[Electronic payment service]
FIG. 1 is a diagram illustrating 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 communicates with each of the one or more user terminal devices 10, the one or more first store terminal devices 50, and the one or more second store terminal devices 70, for example, 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. Payment server 100 is an example of a payment management device.

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 is installed on the user terminal device 10 from an application store, for example, and controls a camera, a communication device, a touch panel, and the like.

The first store terminal device 50 is installed in a store, for example. The first 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 first 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 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 (or a display of a terminal device such as a smartphone) placed in the store.

The second store terminal device 70 is used by an operator of a member store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for member stores operates. The member store interface 72 may be an application for member stores or may be a browser. The member store interface 72 receives coupon settings and the like from the member store operator and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to the store code image and reading the code image displayed by the user terminal device 10 by executing an application for member stores. have

The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and a member store server, in which case payment information is transmitted from the POS device to the payment server 100 via the member store server. In the following description, it is assumed that payment information is transmitted from the first store terminal device 50 without making any particular distinction.

2 and 3 are sequence diagrams 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 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 using an optical reading function (S1). The store code image 60 includes information on a store URL (Uniform Resource Locator). This store URL is the domain of the electronic payment service added with information that can identify the store, and is associated with member store IDs, store IDs, etc. in the payment server 100 (described later). The payment application 20 transmits first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the member store ID and store ID corresponding to the store URL, obtains the member store name and store name information (S3), and sends the information to the payment application 20 (S4). . The user inputs the payment amount into the user terminal device 10 on the screen on which the member store name and store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). Then, the payment server 100 transmits a payment completion notification (information for displaying the payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display placed in a store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the step for the user to input the payment amount is omitted, and the first payment information includes information on the payment amount and is sent to the payment server 100. Information on the member store name and store name may be included and displayed on the payment completion screen.

In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed on the payment application 20, and when the automatic update timing (for example, every minute) is reached. , and at other timings, the payment application 20 transmits a one-time code issuance request to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment application 20 (S13). The payment application 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds up (presents) the display surface of the user terminal device 10 to the first store terminal device 50, and the first store terminal device 50 decodes the code image using an optical reading function and obtains a one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including a one-time code, payment amount, member store ID, store ID, etc., and transmits it to the payment server 100 (S16). Information on the payment amount is obtained in advance by barcode reading, manual input, etc. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). Then, the payment server 100 transmits a payment completion notification to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

Note that electronic payment may be performed using only one of the above patterns. Moreover, the "account ID" explained in FIG. 2 may be other information (for example, a telephone number) that can be used as user identification information. Furthermore, the issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In that case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[Payment server]
FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content provision unit 115, a payment processing unit 120, an information management unit 125, a storage unit 130, an information provision unit 140, a request reception unit 145, and a URL generation unit. section 150 and a URL transmitting section 155. Components other than the communication unit 110 and the storage unit 130 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 information providing unit 140 and subsequent parts will be described later.

The storage unit 130 is an HDD, flash memory, RAM (Random Access Memory), or the like. The storage unit 130 may be a NAS (Network Attached Storage) device that can be accessed by the payment server 100 via a network. The storage unit 130 stores information such as user information 132, payment content information 134, member store/store information 136, and campaign information 138. Campaign information 138 will be described later.

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 payment content providing unit 115 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 payment content providing unit 115 reads necessary content from the payment content information 134 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 payment processing unit 120 performs payment processing based on payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 120 performs payment processing while referring to the user information 132.

FIG. 5 is a diagram showing an example of the contents of the user information 132. User information 132 is an example of user registration information. The user information 132 includes, for example, user URL, account ID, phone number, password, email address, user ID, name/address/date of birth, registration date, charge balance, deferred payment setting, deferred payment limit, deferred payment. Information such as usage amount, available deferred payment amount, payment method settings, bank account, credit card number, charging history information, payment history information, etc. are associated with each other. The user URL is used for remittance processing between users. When registering for a new electronic payment service, it is mandatory to register a phone number and password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be arbitrarily set (or does not need to be set) by the user. Similarly, e-mail address, name, address, and date of birth are information that can (or does not need to be) set arbitrarily by the user. The registration date is the date the user registered with the electronic payment service (the date the account was created). Hereinafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

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 deferred payment setting is information indicating whether the settings for enabling electronic payment by deferred payment have been completed, and is set to either "completed" or "not yet". The deferred payment allowance is the maximum amount of deferred payment that can be used each month, the deferred payment usage amount is the amount of deferred payment that has already been used in the current month, and the available deferred payment amount is calculated by subtracting the deferred payment usage amount from the deferred payment allowance. , is the amount of deferred payment available for the current month. In the figure, only one deferred payment limit is shown, but in reality, there are additional daily upper limit amounts, and the lower of these may be set as the deferred payment limit. Further details of deferred payment will be discussed later. The payment method setting is setting information that indicates whether the user will perform electronic payment using the charge balance or payment by deferred payment at that time. 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 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 the details of the payments made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each payment.

FIG. 6 is a diagram showing an example of the contents of the affiliated store/store information 136. The affiliated store/store information 136 includes, for example, a first table 136A in which affiliated store IDs and store IDs are associated with store URLs, and affiliated store names and sales proceeds (described above) are associated with affiliated store IDs. 136B, and a third table 136C in which store names are associated with store IDs. In addition to this information, the member store/store information 136 may include information such as the member store or store category, store location, payment pattern, and the like.

The information management unit 125 manages user information 132 and member store/store information 136 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 125 adds new records, edits, deletes, etc. the user information 132 and the affiliated store/store information 136.

[Electronic payment]
When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 120 refers to the user information 132 and acquires the "payment method setting" of the user. The payment processing unit 120 performs electronic payment as follows for a user whose "payment method setting" is set to "charge balance". The payment processing unit 120 performs electronic payment by, for example, decreasing the charge balance managed in association with the user ID and increasing the item value of the member store's sales proceeds. For example, the item value of the sales proceeds of a member store is not used as electronic money itself, but the amount corresponding to the item value of the sales proceeds is determined in a cycle according to the agreement between the member store and the electronic payment service. Money will be transferred to your bank account.

The payment processing unit 120 performs electronic payment in the following manner for users whose "setting information" is set to "deferred payment." Deferred payment is set up separately from "credit payment" in collaboration with a credit card company, which is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service is the creditor. , which allows electronic payments that do not depend on the charge balance within the deferred payment limit. Note that in order to receive the deferred payment service, the user may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for deferred payment is paid in one month's worth on the next month's payment date, for example, by debiting from a bank account. In this case, the payment processing unit 120 performs provisional payment by adding the payment amount to the deferred payment usage amount and subtracting the same amount from the available deferred payment amount, and on the closing date, the payment for the current month is transferred to the next month's payment date as described above. or request the operator of the credit card company to perform the processing. Note that if the payment amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is sent back to the payment application 20.

[Social login service]
The social login service performed by cooperation between the electronic commerce device 200 and the payment server 100 will be described below. An electronic commerce device is a device for providing an EC site managed by an EC business operator. FIG. 7 is an example of a configuration for realizing the electronic commerce system 1. The electronic commerce system 1 is configured by the payment server 100 and the electronic commerce device 200 communicating with each other via the NW. The electronic commerce device 200 is a device for providing electronic commerce services. The electronic commerce service is, for example, an EC site. An EC site is an electronic commerce site where, for example, a business operator sells products on a web page, a user uses the user terminal device 10 to access the web page, purchases the product, and pays the purchase price electronically. This is what has been achieved. The EC site is a website, but may also be an EC application provided by a business operator. An EC application is an application that realizes electronic commerce by allowing users to purchase products and electronically pay the purchase price, similar to an EC site. The following will explain the case where the electronic commerce service is an EC site.

The electronic commerce device 200 includes, for example, a content providing section 210, a management section 220, a transaction management section 230, a ranking processing section 240, and a storage section 250. The components other than the storage unit 250 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as LSI, ASIC, FPGA, or GPU, or may be realized by collaboration between software and hardware. Good too. The program may be stored in advance in a storage device such as an HDD or flash memory (storage device equipped with a non-transitory storage medium), or may be stored in a removable storage medium (non-transitory storage medium) such as a DVD or CD-ROM. The software may be installed in the storage device by attaching the storage medium to the drive device.

The storage unit 250 is an HDD, flash memory, RAM, or the like. The storage unit 250 may be a NAS (Network Attached Storage) device that the electronic commerce device 200 can access via a network. The storage unit 250 stores content information 252, EC user information 254, seller information 256, and product information 258.

The content information 252 stores content for displaying various screens of the EC site. The exhibitor information 256 stores information about businesses that exhibit products on the EC site. The business information includes, for example, business ID, business name, telephone number, address, email address, and the like. The product information 258 stores information about products listed on the EC site. The product information includes the product name, the price of the product, the ID of the business that exhibited the product, and the like. The EC user information 254 will be described later.

The content providing unit 210 provides the EC site to the user terminal device 10 of the user. The content providing unit 210 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 EC site. The content providing unit 210 reads out necessary content and information from the content information 252 , seller information 256 , and product information 258 as appropriate and provides them to the user terminal device 10 . The user terminal device 10 receives input of various operations from the user regarding product purchase while content is being played on the EC site, creates purchase information based on the input information, and sends the created purchase information to the management unit 220. The purchase information includes, for example, information regarding a product selected by the user for purchase, a payment method for purchasing the product, and the like.

E-commerce sites can register user information. For example, by logging in with a user ID and password, a specific user can save the trouble of entering user information when purchasing a product. I can do it. The user information is referred to as EC user information 254. FIG. 8 is a table showing an example of the contents of the EC user information 254. The EC user information 254 is an example of registered information of a user of an electronic commerce service. The EC user information 254 is, for example, a user ID associated with personal information including essential information such as a password, email address, name, address, and optional information such as a telephone number. Hereinafter, the user instance (personal information) associated with this information will be referred to as an EC account.

It is possible to log into the EC site not only using the EC user information 254 but also by linking user information held by the electronic payment service using a social login service provided by the electronic payment service. The user information includes, for example, information regarding the user whose identity has been verified and is included in the user information 132, the user's charge balance in the payment service, and the like. Details will be described later.

When the user obtains a content request in the logged-off state from the user terminal device 10, the content providing unit 210 requests the payment server 100 for a URL to be specified as a button to be displayed on the login screen of the electronic payment service. do. The content providing unit 210 specifies the URL generated by the payment server 100 as a redirect destination and displays on the user terminal device 10 a login method selection screen including a login button on which additional information is superimposed. The additional information is information regarding a campaign being implemented by the electronic payment service.

When the user selects a login method using an electronic payment service on the login method selection screen, the content providing unit 210 displays a login screen for the electronic payment service on the user terminal device 10. When the user logs in to the electronic payment service, the user's information in the electronic payment service is linked to the EC site, and the login to the EC site is completed. A user can electronically pay for the purchase of a product on an EC site using an electronic payment service.

The management unit 220 manages information including images used in content. The management unit 220 is realized, for example, by software that manages the website provided by the content providing unit 210 in the background. The management unit 220 acquires information including campaign information that changes over time regarding the electronic payment service from the payment server 100 that provides an electronic payment service that allows payment on an EC site, and transmits the information to the content providing unit 210.

The management unit 220 transmits the user's login status on the EC site to the content providing unit 210. When the management unit 220 is inquired about the login status from the content providing unit 210, the management unit 220 verifies the access token and obtains the user's login status on the EC site. The access token is temporary identification information that is linked between the EC site and the payment server 100 to identify the user. The management unit 220 determines whether the access token is OK or NG based on whether the access token can be identified as an individual user. If the access token is OK, the management unit 220 transmits a result indicating that the user has logged in to the EC site to the content providing unit 210. If the access token is NG, the management unit 220 issues an authorization code and transmits the authorization code together with the result that the user has not logged in to the EC site to the content providing unit 210.

The management unit 220 may acquire campaign information that changes over time regarding electronic payment services from the payment server 100 in conjunction with content requests from users, or may acquire campaign information that changes over time regarding electronic payment services in conjunction with content requests from users. , time-varying campaign information regarding electronic payment services may be obtained from the payment server 100.

The management unit 220 acquires the user's verified information from the payment server 100. Identity-confirmed information includes information such as name, address, date of birth, email address, and telephone number. The user-verified information is displayed on the EC site provided by the content providing unit 210, for example. When a user registers as a new member, the user can save the effort of entering information by having the EC site display in advance information such as the name of the user's verified information in the input field.

The management unit 220 may obtain the user's charge balance in the electronic payment service from the payment server 100. By acquiring the charge balance, the management unit 220 can determine whether or not payment is possible on the electronic commerce device 200 when a user performs a transaction on an EC site. That is, the electronic commerce device 200 can determine that payment is possible if the desired purchase amount is less than or equal to the charge balance, and can determine that payment is not possible if not.

The transaction management unit 230 manages transactions in which a user purchases products on an EC site. The transaction management unit 230 considers that a transaction has occurred when a user purchases a product, and manages information and status regarding the transaction as necessary.

The ranking processing unit 240 determines the popularity of products listed on the EC site based on user attributes, number of accesses, number of purchases, etc., performs ranking processing, and transmits the ranking results to the content providing unit 210.

[Payment server]
The components of the payment server 100 will be described below with reference to FIG. 4. Campaign information 138 stores campaign information provided by the electronic payment service. Campaign information changes over time, and the latest possible campaign information is stored in campaign information 138.

The information providing unit 140 provides campaign information (which changes over time) to be included in the screen (login method selection screen) displayed in the logoff state of the EC site. The information providing unit 140 may provide campaign information and an image of a button to be displayed on the login method selection screen.

The request receiving unit 145 receives a request from the content providing unit 210 for a URL to be specified as a button to be displayed on the login screen. The request reception unit 145 transmits to the URL generation unit 150 that a URL request has been made.

The URL generation unit 150 generates a URL to be specified as a button to be displayed on the login screen. When receiving a request for a URL from the request reception unit 145, a URL is generated.

The URL transmitter 155 transmits the URL generated by the URL generator 150 to the content provider 210.

FIG. 9 is a diagram showing an example of the display of the login method selection screen. On the login method selection screen G10, the user can log in using an EC account, but can also select a login method using one desired service from among a plurality of login services. The login method selection screen G10 is provided with a text box B1 where you can enter the user ID of your EC account, a text box B2 where you can enter your password, and a login button B3 that, when pressed, runs the login process to the EC site. At the bottom, a button B4 is provided with words such as "Log in with payment service" displayed. Campaign information B5 "Up to 5% Rewards" is displayed superimposed on button B4. The campaign information B5 has superimposed words and designs that change depending on the campaign information that changes over time. The button B4 containing the campaign information B5 is set as a link to the login screen of the electronic payment service. Similarly, text such as "Log in with SNS" is displayed on button B6. A link to a login screen of an SNS (Social Network Service) is set to the button B6, and a login service using an SNS account can be used. In this way, the campaign information B5 is displayed on the login method selection screen G10 in a manner superimposed on the button B4, thereby attracting the user's attention. In the example in Figure 9, a login service using an EC account on which campaign information B5 is displayed is more likely to appeal to users than a login service using an SNS account on which campaign information is not displayed. It has the effect of saying that it can be done.

An example of the processing flow and screen transition flow of the electronic commerce system 1 will be described below with reference to FIGS. 10 to 14. FIG. 10 is a diagram showing an example of screen transition when the user's login status is not logged in. FIG. 11 is an example of screen transition when the user's login status is “logged in”. FIG. 12 is a sequence diagram showing an example of the flow of the login status confirmation process of the electronic commerce system 1. FIG. 13 is a sequence diagram illustrating an example of the flow of processing for acquiring and displaying additional information in the electronic commerce system 1. FIG. 14 is a sequence diagram showing an example of the flow of login processing of the electronic commerce system 1. In these figures, the user logs into the EC site, selects and purchases the product he or she wishes to purchase. A user accesses an EC site using a shopping site UA (User Agent) of the user terminal device 10. The shopping site UA is, for example, a browser that can display an EC site.

The user accesses the login method selection screen G10 in FIG. 10 in order to log in to the EC site (S1 in FIG. 12). The content providing unit 210 checks the user's login status with the management unit 220 (S2 in FIG. 12). Even if the user does not access the login method selection screen G10 to actively log in, for example, the user may transition to the login method selection screen G10 when selecting and purchasing a product.

The management unit 220 verifies the access token (S3 in FIG. 12). If the access token is NG, the management unit 220 determines that the login status is not logged in and issues an authorization code (S4 in FIG. 12). The management unit 220 transmits the login status and authorization code to the content providing unit 210 (S5 in FIG. 12). If the access token is OK, the management unit 220 determines that the login status is “logged in” and transmits only the login status to the content providing unit 210 (S5 in FIG. 12). Only when the login status is logged in, the process of this sequence diagram transitions to S25 in FIG. 14. Details will be described later.

The content providing unit 210 requests the management unit 220 to obtain additional information (S6 in FIG. 13). The management unit 220 requests the payment server 100 to send additional information (S7 in FIG. 13). The payment server 100 acquires the latest campaign information from the campaign information 138 and transmits the image for the button to the management unit 220 (S8 in FIG. 13). The management unit 220 provides campaign information and button images to the content providing unit 210 (S9 in FIG. 13). The content providing unit 210 displays a login method selection screen G10 based on the acquired additional information (S10 in FIG. 13).

The user presses the "Log in with electronic payment service" button on the login method selection screen G10 (S11 in FIG. 13). The content providing unit 210 requests the payment server 100 to specify a URL to be redirected to the login button displayed on the electronic payment service login screen G11 in FIG. 10 (S14 in FIG. 13). The request receiving unit 145 of the payment server 100 receives a request from the content providing unit 210, and the URL generating unit 150 of the payment server 100 generates the URL of the electronic payment service login screen G11 in response to the request of the request receiving unit 145. (S13 in FIG. 13). The URL transmitter 155 of the payment server 100 transmits the URL generated by the URL generator 150 to the content provider 210 (S14 in FIG. 13). The content providing unit 210 specifies the received URL as a redirect destination on the login button displayed on the electronic payment service login screen G11 (S15 in FIG. 13). The content providing unit 210 displays the electronic payment service login screen G11 (S16 in FIG. 13).

The user enters the user ID and password of the account previously registered in the electronic payment service on the electronic payment service login screen G11, and presses the login button (S17 in FIG. 14). The content providing unit 210 opens the payment application 20 (S18 in FIG. 14). The payment application 20 displays the account linkage screen G12 in FIG. 10 (S19 in FIG. 14). The user confirms the content displayed on the account linkage screen G12, and if he or she agrees to the linkage between the electronic payment service and the EC site, presses the "Agree" button (S20 in FIG. 14). If the user does not agree to the cooperation between the electronic payment service and the EC site, the process of this sequence diagram ends.

The payment application 20 requests the payment server 100 to perform a login process for the electronic payment service, and sends a notification that the user has agreed to the cooperation between the electronic payment service and the EC site (S21 in FIG. 14). The payment server 100 transmits the URL of the redirected EC site and the one-time token to the content providing unit 210 (S22 in FIG. 14). The content providing unit 210 transmits the authorization code and one-time token received in S5 to the payment server 100, and requests an access token (S23 in FIG. 14). The payment server 100 checks the authorization code and one-time token sent from the content providing unit 210, and if they are correct, issues an access token (S24 in FIG. 14). If the authorization code and one-time token are incorrect, the payment server 100 does not issue an access token and ends the process of this sequence diagram. The payment server 100 transmits the issued access token to the management unit 220 (S25 in FIG. 14). The management unit 220 stores the received access token (S26 in FIG. 14). The management unit 220 instructs the content providing unit 210 to redirect to the EC site (S26 in FIG. 14). The content providing unit 210 opens the redirected URL and opens the product selection screen G13 in FIG. 10 (S27 in FIG. 14).

The screen of the EC site to which the content providing unit 210 redirects does not necessarily have to be the product selection screen G13; for example, the screen immediately before the user accesses the login method selection screen G10 may be displayed. When the user presses the "Purchase" button on the product selection screen G13, the shopping site UA displays the product purchase screen G14 in FIG. 10. The user can select a payment method for the purchase price of the product on the product purchase screen G14. For example, the product purchase screen G14 may be displayed so that the linked electronic payment service is selected as the payment method by default. When the user selects "electronic payment service" as the payment method and presses the "Execute Payment" button, the shopping site UA pops up the payment screen G15 of FIG. 10 so as to be superimposed on the product purchase screen G14. The user can check the purchase amount and the balance of the payment service on the payment screen G15, and can charge the balance as necessary. When the user presses the "Pay" button on the payment screen G15, payment processing is performed and the product on the EC site can be purchased.

In the process of S3 in FIG. 12, the management unit 220 verifies the access token, and if the result is OK, the process moves to S25 in FIG. 14 and stores the access token. The management unit 220 instructs the content providing unit 210 to redirect to the EC site (S26 in FIG. 14). The content providing unit 210 opens the redirected URL and opens the product selection screen G13 in FIG. 10 (S27 in FIG. 14). As in the example of the screen transition in FIG. 11, the login process is omitted and the user can purchase the product using the payment service.

According to the embodiment described above, information on the transition destination of the social login service can be conveyed in a timely manner.

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 100 Payment server 115 Payment content provision unit 120 Payment processing unit 125 Information management unit 138 Campaign information 140 Information provision unit 145 Request reception unit 150 URL generation unit 155 URL transmission unit 200 Electronic commerce device 210 Content provision Department 220 Management Department 230 Transaction Management Department 240 Ranking Processing Department 240
250 Storage unit 252 Content information 254 EC user information 256 Seller information 258 Product information

Claims (10)

An electronic commerce device that provides electronic commerce services to users,
a content providing unit that provides content of the electronic commerce service to the user terminal device of the user;
a management unit that manages information including images used in the content;
The management unit acquires information including additional information that changes over time regarding the electronic payment service from a payment management device that provides an electronic payment service that allows payment in the electronic commerce service,
The content providing unit causes the user terminal device to display a login method selection screen including an image based on the additional information when a content request in a logged-off state is obtained from the user terminal device.
E-commerce equipment. The additional information is information regarding a campaign being implemented by the electronic payment service.
The electronic commerce device according to claim 1. The login method selection screen includes information regarding the campaign superimposed on a button with a link to the login screen for the electronic payment service.
The electronic commerce device according to claim 2. The management unit acquires additional information that changes over time regarding the electronic payment service from the payment management device in conjunction with a content request from the user.
The electronic commerce device according to claim 1. The management unit acquires additional information that changes over time regarding the electronic payment service from the payment management device asynchronously with the content request from the user.
The electronic commerce device according to claim 1. The content providing department is
requesting a URL for displaying a login screen of the electronic payment service to the payment management device;
displaying on the user terminal device the login method selection screen including a button on which campaign information is superimposed by specifying the URL generated by the payment management device as a redirect destination;
The electronic commerce device according to claim 1. A payment management device that provides users with an electronic payment service that allows them to make payments in an electronic commerce service managed by an electronic commerce device,
an information providing unit that provides additional information to be included in a screen displayed in a logoff state of the e-commerce service in response to a request from the e-commerce device;
a request receiving unit that receives a request for a URL for logging into the e-commerce service from the e-commerce device;
a URL generation unit that generates the URL;
a URL transmitter that transmits the generated URL to the electronic commerce device;
Payment management device. The electronic commerce device according to claim 1;
A payment management device according to claim 7;
An electronic commerce system equipped with An e-commerce device that provides e-commerce services to users is
a process of providing content of the electronic commerce service to a user terminal device;
a process for managing information including images used in the content;
a process of acquiring information including additional information that changes over time regarding the electronic payment service from a payment management device that provides an electronic payment service that allows payment in the electronic commerce service;
When a content request in a logged-off state is obtained from the user's terminal device, a process of displaying a login method selection screen including an image based on the additional information on the user terminal device;
e-commerce methods to carry out. A processor of an electronic commerce device that provides electronic commerce services to users,
a process of providing content of the electronic commerce service to a user terminal device;
a process for managing information including images used in the content;
a process of acquiring information including additional information that changes over time regarding the electronic payment service from a payment management device that provides an electronic payment service that allows payment in the electronic commerce service;
When a content request in a logged-off state is obtained from the user's terminal device, a process of displaying a login method selection screen including an image based on the additional information on the user terminal device;
A program to run.

Images