Chat screen payment support device, chat screen payment support system, chat screen payment support method, and chat screen payment support program

Abstract

To prevent a decline in conversion rate when introducing an identity authentication function for card payments on chat screens on e-commerce sites. [Solution] A chat screen payment support device displays an EC site screen and a chat screen on a user terminal and supports payment card payments on the chat screen, and includes a control unit. The control unit receives payment card information entered on the chat screen, transmits the received payment card information to a card payment system, displays an identity authentication page on the chat screen that prompts the user to enter identity authentication information based on identity authentication page information from the card payment system, and displays a result page on the user terminal according to the success or failure of the identity authentication.

Description

[Technical Field]

[0001] The present invention relates to a chat screen payment support device, a chat screen payment support system, a chat screen payment support method, and a chat screen payment support program. [Background technology]

[0002] Patent Document 1 discloses a system including a payment server, an EC server, and a user terminal. The payment server is a server computer for payment services, and the EC server is a server computer for electronic commerce services. When a user operates the user terminal to select credit card payment on an EC site, personal authentication called 3D Secure, provided by the card company, may be performed to prevent fraudulent use. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2024-3374 Summary of the Invention [Problem to be solved by the invention]

[0004] An EC server may display a chat screen along with the EC site screen on the user's device display. When purchasing a product, it is convenient for the user to be able to enter payment information on the chat screen. However, when identity authentication such as 3D Secure is performed, the user is redirected from the chat screen to an identity authentication screen provided by the card company, and this screen transition may result in a decrease in conversion rate.

[0005] The present invention aims to prevent a decrease in conversion rate when an identity authentication function is introduced into card payments on chat screens on e-commerce sites. [Means for solving the problem]

[0006] A chat screen payment support device according to one embodiment of the present invention is a device that displays an e-commerce site screen and a chat screen on a user terminal and supports payment card payments on the chat screen, and is equipped with a control unit. The control unit receives payment card information entered on the chat screen, transmits the received payment card information to a card payment system, and displays an identity authentication page on the chat screen that prompts the user to enter identity authentication information based on identity authentication page information from the card payment system, and displays a result page on the user terminal according to the success or failure of the identity authentication.

[0007] A chat screen payment support system according to one embodiment of the present invention is a system that displays an e-commerce site screen and a chat screen on a user terminal and supports payment card payments on the chat screen, and is equipped with a chat screen payment support server and the user terminal that is capable of communicating with the chat screen payment support server. The chat screen payment support server receives payment card information entered on the chat screen, transmits the received payment card information to a card payment system, and displays an identity authentication page on the chat screen that prompts the user to enter identity authentication information based on identity authentication page information from the card payment system, and displays a result page on the user terminal according to the success or failure of the identity authentication.

[0008] A chat screen payment support method according to one embodiment of the present invention displays an EC site screen and a chat screen on a user terminal and supports payment card payments on the chat screen, receiving payment card information entered on the chat screen, transmitting the received payment card information to a card payment system, displaying an identity authentication page on the chat screen that prompts the user to enter identity authentication information based on identity authentication page information from the card payment system, and displaying a result page on the user terminal according to the success or failure of the identity authentication.

[0009] A chat screen payment support program according to one aspect of the present invention causes a processor to execute the chat screen payment support method. The program can be stored in a computer-readable storage medium. The storage medium is a non-transitory, tangible medium. [Effects of the Invention]

[0010] According to the present invention, a decrease in conversion rate can be prevented when an identity authentication function is introduced into card payments on chat screens on e-commerce sites. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram of a chat screen payment support system according to an embodiment. [Figure 2] FIG. 2 is a block diagram of the hardware of the browser server of FIG. [Figure 3] FIG. 3 is a functional block diagram of the browser server of FIG. [Figure 4] FIG. 4 is a flowchart of the process performed by the chat screen payment support system of FIG. [Figure 5] FIG. 5 is a flowchart continuing from FIG. [Figure 6] FIG. 6 is a diagram showing an EC site screen and a chat screen displayed on the user terminal of FIG. [Figure 7] FIG. 7 is a diagram showing an EC site screen and a chat screen displayed on the user terminal of FIG. [Figure 8] FIG. 8 is a diagram showing an EC site screen and a chat screen displayed on the user terminal of FIG. [Figure 9] FIG. 9 is a diagram showing an EC site screen and a chat screen displayed on the user terminal of FIG. [Figure 10] FIG. 10 is a diagram showing an EC site screen and a chat screen displayed on the user terminal of FIG. [Figure 11]FIG. 11 is a diagram showing an EC site screen and a chat screen displayed on the user terminal of FIG. [Figure 12] FIG. 12 is a diagram showing an EC site screen and a chat screen displayed on the user terminal of FIG. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment will be described with reference to the drawings.

[0013] 1 is a schematic diagram of a chat screen payment support system 1 according to an embodiment. The chat screen payment support system 1 includes a user terminal 2, an EC server 10, and a browser server 11. The user terminal 2, the EC server 10, and the browser server 11 are connected to a communication network N such as the Internet. A card payment system 12 is also connected to the communication network N.

[0014] The user terminal 2 is an information processing terminal such as a personal computer, a smartphone, or a tablet terminal. A user U operates the user terminal 2 to browse an EC site and purchase products. The EC server 10 is a server for operating an e-commerce site for selling and purchasing products over the Internet.

[0015] The browser server 11 provides a function-extending application when a product seller opens a product sales page on the EC server 10, and also mediates the exchange of information between the user terminal 2 and the EC server 10. The browser server 11 displays an EC site screen and a chat screen (described later) on the user terminal 2, and supports payment card settlement on the chat screen. The browser server 11 is an example of a chat screen payment support device. The EC server 10 may also function as the browser server 11.

[0016] The card payment system 12 is a system for credit card payments and includes an issuer and acquirer for the credit card business. The issuer is a company that issues credit cards to users and temporarily advances the payment amount. The acquirer is a company that contracts with affiliated stores to provide a card payment system, and sends card payment data from the affiliated stores to the issuer to complete the payment. The card payment system 12 performs identity authentication for card payments. Identity authentication is, for example, 3D Secure authentication. Note that instead of credit card payments, other payment card payments such as debit card payments may be used.

[0017] FIG. 2 is a hardware block diagram of the browser server 11 of FIG. 1. As shown in FIG. 2, the browser server 11 includes a processor 121, a system memory 122, a storage memory 123, and a communication interface 124. The processor 121 includes a CPU. The system memory 122 includes a volatile memory such as RAM. The storage memory 123 includes a non-volatile memory such as a hard disk and a flash memory. The storage memory 123 stores a chat screen payment support program P. The communication interface 124 is an interface for connecting to the communication network N and includes, for example, an Ethernet interface. The processor 121, the system memory 122, the storage memory 123, and the communication interface 124 are connected to each other via a communication bus.

[0018] 3 is a functional block diagram of the browser server 11 in FIG. 1. As shown in FIG. 3, the browser server 11 includes a control unit 21, a memory unit 22, and a communication unit 23. The control unit 21 is implemented by a processor 121 that executes a program P read from the storage memory 123 shown in FIG. 2 to the system memory 122. The memory unit 22 is implemented by the storage memory 123. The communication unit 23 is implemented by a communication interface 124. The functions disclosed in the present embodiment can be performed using a processing circuit configured to perform the functions, including a general-purpose processor, a special-purpose processor, an integrated circuit, an ASIC, a conventional circuit, and / or a combination thereof.

[0019] Figures 4 and 5 are flowcharts of the processing by the chat screen payment support system 1 of Figure 1. Below, the processing of the chat screen payment support system 1 will be explained along the flow of Figures 4 and 5 with reference to the configurations of Figures 1 and 3 and the screens of Figures 6 to 12. In the following explanation, the processing of the browser server 11 is executed by the control unit 21. Note that the specific displays of the screens shown in Figures 6 to 12 are merely examples, and may be presented in other forms.

[0020] A user operates the user terminal 2 to launch a web browser and access an EC site via the web browser. Then, as shown in FIG. 6, a browser server 11, which acts as an intermediary between the user terminal 2 and the EC server 10, causes the user terminal 2 to display an EC site screen 30 and a chat screen 40. The EC site screen 30 displays product images, product descriptions, a purchase button, a cart button, and the like. The chat screen 40 is a screen on which users can exchange information through text-based dialogue and is realized by a chatbot. For example, when a user enters a question about a product or the like in text on the chat screen 40, a response to the question is output in text.

[0021] When a user presses the purchase button for a specific product on the EC site screen 30, as shown in Figure 7, the chat screen 40 displays, for example, a frame 41 that prompts the user to enter a delivery address and a frame 42 that prompts the user to enter an email address.

[0022] When a user selects a credit card as the payment method, chat screen 40 displays frame 43 that prompts the user to input credit card information, and also displays frame 44 that shows information related to the transaction for the product purchase, as shown in Fig. 8. Note that chat screen 40 may display frame 44 that shows information related to the transaction for the product purchase on the next screen within chat screen 40. Payment card information is not limited to credit card information, and may be, for example, debit card information.

[0023] When a user inputs credit card information in frame 43 within chat screen 40 (step S1), user terminal 2 transmits the credit card information to browser server 11. Browser server 11 receives the credit card information and the user presses a credit card payment button on an EC processing page internally processed by browser server 11 (step S2). Browser server 11 then transmits the credit card information to card payment system 12 and requests card payment system 12 to authenticate the user (e.g., 3D Secure authentication) (step S3).

[0024] In response to the request, card payment system 12 transmits personal authentication page information including URL information of the personal authentication page to browser server 11. Browser server 11 displays a personal authentication modal on the EC processing page based on the personal authentication page information (step S4). Browser server 11 extracts the URL information of the personal authentication page from the personal authentication page information on the EC processing page (step S5).

[0025] The browser server 11 transmits the URL information to the user terminal 2. As shown in Fig. 9, the chat screen 40 of the user terminal 2 displays an authentication page in the authentication frame 45 within the chat screen 40 based on the URL information (step S6). In this way, the user terminal 2 can display the authentication page on the chat screen 40 based on the URL information, without directly receiving the authentication page information from the card payment system 12.

[0026] The personal authentication page displays, for example, a field for the user to enter a one-time password. In this way, the personal authentication page is displayed on the chat screen 40 without transitioning from the chat screen 40 to the personal authentication screen on the user terminal 2, so the user can smoothly enter personal authentication information on the chat screen 40 where they entered their credit card information. This prevents a decrease in conversion rate when introducing a personal authentication function into card payments on the chat screen 40 of an e-commerce site.

[0027] The one-time password may be a temporary password sent by SMS from the card payment system 12 to the user's mobile phone, or it may be a temporary password sent to the user's email address, a temporary password generated by a dedicated app provided by the credit card company, or a temporary password generated on a one-time password terminal. The identity authentication page may be one that uses fingerprint authentication or face authentication functions on a smartphone to verify the user's identity. The identity authentication page may also be one that requires the user to enter a password previously registered with the credit card company to verify the user's identity.

[0028] Based on the URL information extracted in step S5, browser server 11 displays the personal authentication page on the personal authentication monitoring page processed internally by browser server 11, and periodically reloads the personal authentication page (step S7). That is, browser server 11 repeatedly reloads the personal authentication page for monitoring within browser server 11, separate from the personal authentication page displayed on chat screen 40 of user terminal 2.

[0029] This allows the browser server 11 to monitor the progress of the authentication process between the user terminal 2 and the card payment system 12 on the identity authentication monitoring page. In other words, even if the user terminal 2 performs identity authentication processing in the card payment system 12 without going through the browser server 11, the browser server 11 can know the success or failure of identity authentication in the card payment system 12.

[0030] The browser server 11 determines whether the personal authentication has been completed on the personal authentication monitoring page (step S8). If it is determined that the personal authentication has been completed, the browser server 11 transmits information indicating the completion of authentication to the user terminal 2. In response to the completion of authentication, the user terminal 2 closes the personal authentication page on the chat screen 40 (step S9).

[0031] Browser server 11 closes the personal authentication page in the personal authentication monitoring page (step S10). Browser server 11 generates a URL for a thank you page with the detailed order information on the EC processing page (step S11). Browser server 11 transmits the URL for the thank you page with the detailed order information to user terminal 2.

[0032] 10, the user terminal 2 displays a thank you page 46 with detailed order information as a result page in a result display frame 46 on the chat screen 40 (step S12). This thank you page 46 displays information indicating that the user has been authenticated and that the product purchase has been completed, as well as detailed information about the confirmed product order (e.g., product name, billing amount, etc.). This allows the user to know the result of the user authentication on the chat screen 40.

[0033] On the other hand, if it is determined that the result of the personal authentication is unsuccessful, the browser server 11 sends information indicating that the authentication was unsuccessful to the user terminal 2, closes the personal authentication page on the personal authentication monitoring page, and generates a URL for an authentication failure page on the EC processing page. The browser server 11 sends the URL for the authentication failure page to the user terminal 2. As shown in FIG. 11 , upon receiving the information indicating that the authentication was unsuccessful, the user terminal 2 displays the authentication failure page indicating that the personal authentication was unsuccessful as a result page in the result display frame 47 on the chat screen 40.

[0034] 12, the browser server 11 may display a result page such as a thank you page on a screen (e.g., the EC site screen 30) different from the chat screen 40 of the user terminal 2. In this case, the screen transition to a screen different from the chat screen 40 occurs after the product purchase procedure is completed, preventing a decrease in the conversion rate due to the screen transition. Also, by displaying the result page on a screen different from the chat screen 40, for example, the EC site screen 30, the degree of freedom in displaying the result page is increased.

[0035] 6 to 12 show screen examples when the user terminal 2 is a personal computer, but when the user terminal 2 is a smartphone, the chat screen 40 may be displayed in full screen while the chat screen 40 is being displayed. Therefore, when the user terminal 2 is a smartphone, it is possible to sufficiently increase the effect of preventing a decrease in the conversion rate caused by the personal authentication page being displayed on the user terminal 2 without transitioning from the chat screen 40 to the personal authentication screen.

[0036] [Note] The above-described embodiments are specific examples of the following disclosure.

[0037] (Appendix 1) A device that displays an EC site screen and a chat screen on a user terminal and supports payment card settlement on the chat screen, A control unit is provided, the control unit receiving payment card information entered on the chat screen; Transmitting the received payment card information to a card payment system; displaying an identity authentication page on the chat screen that prompts the user to input identity authentication information based on identity authentication page information from the card payment system; monitor the success or failure of the personal authentication in the card payment system; The chat screen payment support device displays a result page on the user terminal according to the success or failure of the personal authentication.

[0038] (Appendix 2) The control unit monitors the success or failure of personal authentication in the card payment system.

[0039] (Appendix 3) The control unit of the chat screen payment support device described in Appendix 2 monitors the success or failure of the personal authentication by periodically reloading the personal authentication page from the card payment system.

[0040] (Appendix 4) The chat screen payment support device described in Appendix 1, wherein the control unit displays the personal authentication page on a frame within the chat screen.

[0041] (Appendix 5) The chat screen payment support device according to claim 1, wherein the control unit displays the results page on the chat screen.

[0042] (Appendix 6) The chat screen payment support device described in Appendix 1, wherein the control unit displays the results page on a screen different from the chat screen.

[0043] (Appendix 7) The chat screen payment support device described in Appendix 1, wherein the result page is a thank you page indicating that the identity authentication has been successful and the product purchase has been completed, or an authentication failure page indicating that the identity authentication has not been successful.

[0044] (Appendix 8) The thank you page includes detailed information about the product order.

[0045] (Appendix 9) The chat screen payment support device described in Appendix 1, wherein the personal authentication page information includes URL information of the personal authentication page.

[0046] (Appendix 10) The chat screen payment support device according to claim 1, wherein the payment card information is credit card information or debit card information.

[0047] (Appendix 11) The chat screen payment support device described in Appendix 1, wherein the personal authentication is 3D Secure.

[0048] (Appendix 12) A server; a user terminal that communicates with the server and displays an EC site screen and a chat screen; The server receiving payment card information entered on the chat screen; Transmitting the received payment card information to a card payment system; displaying an identity authentication page on the chat screen that prompts the user to input identity authentication information based on identity authentication page information from the card payment system; monitor the success or failure of the personal authentication in the card payment system; A chat screen payment support system that displays a result page on the user terminal according to the success or failure of the personal authentication.

[0049] (Appendix 13) A method for displaying an EC site screen and a chat screen on a user terminal and supporting payment card settlement on the chat screen, comprising: receiving payment card information entered on the chat screen; Transmitting the received payment card information to a card payment system; displaying an identity authentication page on the chat screen that prompts the user to input identity authentication information based on identity authentication page information from the card payment system; monitor the success or failure of the personal authentication in the card payment system; A chat screen payment support method that displays a result page on the user terminal according to the success or failure of the personal authentication.

[0050] (Appendix 14) A chat screen payment support program that causes a processor to execute the chat screen payment support method described in Appendix 13. [Explanation of symbols]

[0051] 1. Chat screen payment support system 2. User terminal 11 Browser server (chat screen payment support device) 12. Card payment system 21 Control Unit 30 EC site screen 40 Chat screen 121 processors P Chat screen payment support program

Claims

1. A device that displays an EC site screen and a chat screen on a user terminal and supports payment card settlement on the chat screen, A control unit is provided, the control unit receiving payment card information entered on the chat screen; Transmitting the received payment card information to a card payment system; displaying an identity authentication page on the chat screen that prompts the user to input identity authentication information based on identity authentication page information from the card payment system; A chat screen payment support device that displays a result page on the user terminal according to the success or failure of the personal authentication.

2. The chat screen payment support device according to claim 1 , wherein the control unit monitors whether or not personal authentication has been successful in the card payment system.

3. The chat screen payment support device according to claim 2 , wherein the control unit monitors the success or failure of the personal authentication by periodically reloading the personal authentication page from the card payment system.

4. The chat screen payment support device according to claim 1 , wherein the control unit displays the personal authentication page on a frame within the chat screen.

5. The chat screen payment support device according to claim 1 , wherein the control unit causes the result page to be displayed on the chat screen.

6. The chat screen payment support device according to claim 1 , wherein the control unit displays the result page on a screen different from the chat screen.

7. 2. The chat screen payment support device according to claim 1, wherein the result page is a thank you page indicating that the personal authentication has been successful and the product purchase has been completed, or an authentication failure page indicating that the personal authentication has not been successful.

8. The chat screen payment support device according to claim 7 , wherein the thank you page includes detailed information about the product order.

9. The chat screen payment support device according to claim 1 , wherein the personal authentication page information includes URL information of the personal authentication page.

10. The chat screen payment support device according to claim 1 , wherein the payment card information is credit card information or debit card information.

11. The chat screen payment support device according to claim 1 , wherein the personal authentication is 3D Secure.

12. A server; a user terminal that communicates with the server and displays an EC site screen and a chat screen; The server receiving payment card information entered on the chat screen; Transmitting the received payment card information to a card payment system; displaying an identity authentication page on the chat screen that prompts the user to input identity authentication information based on identity authentication page information from the card payment system; monitor the success or failure of the personal authentication in the card payment system; A chat screen payment support system that displays a result page on the user terminal according to the success or failure of the personal authentication.

13. 1. A method executed by a processor for displaying an EC site screen and a chat screen on a user terminal and supporting payment card settlement on the chat screen, comprising: receiving payment card information entered on the chat screen; Transmitting the received payment card information to a card payment system; displaying an identity authentication page on the chat screen that prompts the user to input identity authentication information based on identity authentication page information from the card payment system; monitor the success or failure of the personal authentication in the card payment system; A chat screen payment support method that displays a result page on the user terminal according to the success or failure of the personal authentication.

14. A chat screen payment support program that causes a processor to execute the chat screen payment support method according to claim 13.

Images