Electronic Payment Program

Abstract

An electronic payment program and a payment server that can reduce the risk of users abandoning electronic payment. [Solution] The electronic payment program causes the computer to function as a display control unit that, when it accepts a first electronic payment, which is an electronic payment using a first credit card designated by a user, makes an inquiry to the payment server regarding the use of the first credit card, and if it is confirmed that the first name holder, who is the name holder of the first credit card, needs to be registered, displays a first screen on the display device prompting the user to input the first name holder, a registration unit that requests that the first name holder entered on the first screen be registered with the payment server, and a payment unit that continues the first electronic payment after the registration unit has registered the first name holder with the payment server.

Description

[Technical Field]

[0001] The present invention is an electronic payment program Mu Regarding. [Background technology]

[0002] Credit cards are used for electronic payments for various services. Patent Document 1 discloses that an electronic payment app, which is a program used for electronic payments, manages information such as the card holder's name in addition to the card number and expiration date. With this technology, when registering a credit card in the electronic payment app, the card holder's name must be linked to the card number. However, there are also electronic payment app programs that do not require the card holder's name to be registered when registering a credit card.

[0003] However, from the perspective of strengthening security, credit card security policies may change, and as a result, it may become necessary to hand over the cardholder name linked to the card number to the card management company. [Prior art documents] [Patent documents]

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

[0005] However, if the credit card holder's name is not linked to the card number when the credit card is registered, conventional technology cannot accommodate changes in security policies. As a result, when a user attempts to make an electronic payment using a credit card that has already been registered in an electronic payment app, an error screen is displayed. In this case, the user must discontinue use of the credit card and re-register the credit card in the electronic payment app, or contact the credit card management company and enter the card holder's name. As a result, there is a problem that users may be inferred to abandon electronic payment.

[0006] The present disclosure has been made in consideration of the above-mentioned circumstances, and one of the problems to be solved is to reduce the risk of users abandoning electronic payments when making electronic payments using credit cards whose credit card holders are not registered. [Means for solving the problem]

[0007] In order to solve the above problems, the electronic payment program of the present disclosure causes a computer to function as a display control unit that, when it accepts a first electronic payment, which is an electronic payment using a first credit card designated by a user, makes an inquiry to a payment server regarding the use of the first credit card, and if it is confirmed that a first name holder, who is the name holder of the first credit card, needs to be registered, displays a first screen on a display device prompting the user to input the first name holder, a registration unit that requests that the first name holder input on the first screen be registered with the payment server, and a payment unit that continues the first electronic payment after the first name holder has been registered with the payment server by the registration unit.

[0008] The payment server of the present disclosure comprises a communication control unit that communicates with a card management server and a user's terminal device via a communication device; a management unit that manages a credit card information file that links a first card number, which is the card number of a first credit card that the user can use for electronic payment, with a first cardholder, which is the cardholder of the first credit card; and a judgment unit that, when the communication control unit receives from the terminal device a payment request that includes the first card number and payment amount and requests a first electronic payment, which is an electronic payment using the first credit card, determines whether the first cardholder is registered by referring to the credit card information file; and if the judgment result of the judgment unit is negative, the communication control unit sends a registration request to the terminal device via the communication device, indicating that the first cardholder needs to be registered. [Effects of the Invention]

[0009] According to the present invention, when an electronic payment is made using a credit card whose owner is not registered, the risk of a user abandoning electronic payment can be reduced. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram showing an example of the configuration of an electronic payment system according to an embodiment of the present invention. [Figure 2] 2 is a block diagram showing an example of the configuration of the terminal device of FIG. 1. FIG. [Figure 3] This is an example of the third screen. [Figure 4] This is an example of the first screen. [Figure 5] 10 is an example of an error screen. [Figure 6] 10 is an example of the second screen. [Figure 7] 10 is an example of an authentication error screen. [Figure 8] 10 is an example of a payment completion screen. [Figure 9] FIG. 2 is a block diagram showing an example of the configuration of the payment server of FIG. 1. [Figure 10]1 is an example of a credit card information file. [Figure 11] 1 is a sequence chart showing an example of the operation of the electronic payment system of the present embodiment. [Figure 12] 10 is an example of a service payment screen. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments for carrying out the present disclosure will be described with reference to the drawings. Note that in each drawing, the dimensions and scale of each part are appropriately different from those of the actual parts. Furthermore, the embodiments described below are preferred specific examples of the present disclosure, and therefore various technically preferable limitations are applied, but the scope of the present disclosure is not limited to these embodiments unless otherwise specified in the following description to the effect that the present invention is limited thereto.

[0012] A. This embodiment A-1. Overview of Electronic Payment System 100 Figure 1 is a block diagram showing an example of the configuration of an electronic payment system 100 according to this embodiment. The electronic payment system 100 shown in Figure 1 provides an electronic payment service in which payments are settled through the exchange of electronic data over a network. In the following description, the electronic payment service provided by the electronic payment system 100 will be referred to as electronic payment service X.

[0013] The electronic payment system 100 includes multiple terminal devices 1, a store device 2, a payment server 3, and a card management server 5. The multiple terminal devices 1, the store device 2, the payment server 3, and the card management server 5 can communicate with each other via a network NW. The number of store devices 2, card management servers 5, and terminal devices 1 may be any number.

[0014] In the example of FIG. 1, Q terminal devices 1 are provided as the multiple terminal devices 1. The value Q is a natural number that satisfies "Q≧2". Hereinafter, the qth terminal device 1 among the Q terminal devices 1 will be referred to as terminal device 1[q]. The variable q is a natural number that satisfies "1≦q≦Q". Furthermore, a user U who uses terminal device 1[q] will be referred to as user U[q]. Furthermore, terminal device 1[q] is, for example, a mobile information terminal such as a smartphone or tablet, a personal computer, or a wearable device.

[0015] In this embodiment, the terminal device 1[q] is installed with an electronic payment program PG1 (described below), which is an electronic payment application for making electronic payments, and a store service application for receiving services provided at a store equipped with the store device 2. These applications are linked to each other. Note that, hereinafter, the electronic payment program PG1, which is an electronic payment application, may be referred to as the "payment app."

[0016] The in-store device 2 is a server that provides a service to the user U[q]. The service is assumed to be the sale of goods or the provision of services. In this embodiment, the store in which the in-store device 2 is installed is assumed to be a physical store existing in real space, i.e., a brick-and-mortar store, but may also be an EC (electronic commerce) site that provides services over the Internet.

[0017] When a user U[q] wishes to receive a service at a store having a store device 2, the user U[q] can pay for the service by electronic payment via the terminal device 1[q]. An example of an electronic payment method at the store device 2 is code payment. Code payment is a payment method using a barcode or two-dimensional code. Code payment can be performed in two ways. The first way is to display a barcode or two-dimensional code on the terminal device 1[q] and read the displayed barcode or two-dimensional code with the store device 2. The second way is to display a barcode or two-dimensional code on the store device 2 and read the displayed barcode or two-dimensional code with the terminal device 1[q]. In either way, payment methods may include, for example, payment combined with telephone bills, credit card payment, and balance payment.

[0018] Furthermore, electronic payments using a payment app are not limited to code payments. For example, when making a payment on an e-commerce site using a store service application, electronic payment service X provided by electronic payment system 100 is selected as the payment method. In this case, the store service application and the payment app work together. Specifically, the selection of electronic payment service X triggers the launch of the payment app. Payment methods may include, for example, combined payment with telephone bills, credit card payment, and balance payment.

[0019] Furthermore, when making a payment on an e-commerce site without using a store service application, electronic payment may be made using a payment app. In this case, the web page of the e-commerce site displays electronic payment service X as a payment method option. When user U[q] selects this option, the payment app is launched. Payment methods may include, for example, combined payment with telephone bills, credit card payment, and balance payment.

[0020] The payment server 3 is a server that provides electronic payment service X using a payment app. The payment server 3 manages credit cards registered using the payment app. Of the three payment methods, telephone bill combined payment, credit card payment, and balance payment, the payment server 3 executes the payment for telephone bill combined payment and balance payment. Furthermore, the payment server 3 manages the payment app.

[0021] The card management server 5 is a server owned by, for example, an issuer or an acquirer, and examines the credit risk of a user U[q] who is a credit card user, and approves payments.

[0022] In this electronic payment system 100, when making an electronic payment using a payment app, user U[q] of terminal device 1[q] first registers their credit card with payment server 3, which manages the payment app. This registration procedure requires, for example, registration of the card number and card number card scheme, but registration of the cardholder's name may not be required.

[0023] However, in order to strengthen security, credit card security policies may be changed, and credit cards linked to card numbers may become unusable if the credit card holder's name is not registered. When user U[q] attempts to pay by electronic payment, he or she often realizes for the first time that a registered credit card cannot be used because the holder's name is not registered. If the credit card registered in a payment app cannot be used, the user may abandon code payment using the payment app. In this case, the user may switch to a payment method other than code payment. Furthermore, the user may abandon the service they were planning to use altogether.

[0024] This would undermine the convenience of code payment. The electronic payment system 100 of this embodiment allows easy registration of credit cards whose holders are not yet registered. This prevents users from abandoning electronic payment.

[0025] A-2. Terminal device 1 [q] Fig. 2 is a block diagram showing an example of the configuration of the terminal device 1[q] in Fig. 1. As shown in Fig. 2, the terminal device 1[q] includes a processing device 11, a storage device 12, a display device 13, an input device 14, a communication device 15, and a bus 10 that interconnects these devices.

[0026] The storage device 12 is a recording medium readable by the processing device 11. The storage device 12 includes, for example, a volatile memory such as a random access memory (RAM) that functions as a working area for the processing device 11, and a non-volatile memory such as an electrically erasable programmable read-only memory (EEPROM) that stores various information. The storage device 12 stores an electronic payment program PG1.

[0027] The processing device 11 includes a processor. The processor provided in the processing device 11 includes, for example, one or more central processing units (CPUs). However, the processor provided in the processing device 11 may include hardware such as a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA) in addition to the one or more CPUs, or in place of some or all of the one or more CPUs.

[0028] The processor provided in the processing device 11 executes the electronic payment program PG1 stored in the storage device 12 and operates in accordance with the electronic payment program PG1, thereby functioning as a reception unit 111, a communication control unit 112, a display control unit 113, a registration unit 114, and a payment unit 115.

[0029] The reception unit 111 receives various instructions from the user U[q] via the input device 14. For example, the reception unit 111 receives electronic payments from the user U[q] via the input device 14.

[0030] The communication control unit 112 causes the communication device 15 to transmit and receive various types of information to and from the in-store device 2, the payment server 3, and the card management server 5, respectively.

[0031] Specifically, for example, the communication control unit 112 transmits a payment request, which is a request for electronic payment from user U[q] received by the reception unit 111, to the payment server 3. The payment request that the communication control unit 112 transmits to the payment server 3 includes the terminal ID, which is the identifier of terminal device 1[q], the credit card number, and an inquiry regarding the use of the credit card. The inquiry includes information indicating whether or not the credit card holder needs to be registered, whether or not the credit card holder has already been registered in the card management server 5, etc. Furthermore, for example, the communication control unit 112 receives various responses to the payment request from the card management server 5.

[0032] Display control unit 113 controls the display of display device 13. For example, display control unit 113 causes various screens in the payment app to be displayed on display device 13. Figures 3 to 8 show examples of various screens in the payment app.

[0033] FIG. 3 is an example of the third screen S3. The third screen S3 shown in FIG. 3 is a payment confirmation screen for electronic payments. The third screen S3 is displayed when an electronic payment is made using a payment app. This electronic payment may include, for example, a payment made using a payment app linked to a store service application, a payment made when electronic payment service X is selected on an e-commerce site's web page, and a code payment made using the payment app.

[0034] In the example of FIG. 3, the third screen S3 includes a payment amount A31, multiple options A32 and A33, and a button B31. The payment amount A31 indicates the price for the service. The multiple options A32 and A33 indicate multiple credit card options. Each of the multiple options A32 and A33 indicates the credit card number, expiration date, the registered account holder, and an "unregistered" indication indicating that the account holder is not registered. The option A32 is provided with a selection button B32, and the option A33 is provided with a selection button B33. The user U selects either the selection button B32 or B33 via the input device 14. The number of options may be one. The button B31 is a button used by the user U to accept the payment for the service and decide to purchase it.

[0035] FIG. 4 is an example of the first screen S1. The first screen S1 shown in FIG. 4 is a screen for registering a cardholder. The first screen S1 is a screen that prompts the user U[q] to input a cardholder name for a credit card for which the cardholder has not yet been registered. The first screen S1 includes a text box A1 and a register button B1. The text box A1 is used by the user U[q] to input a cardholder name. The register button B1 is used to request the payment server 3 to register the cardholder entered in the text box A1. Note that the first screen S1 may further include a text box or the like for inputting additional information such as the cardholder's date of birth in order to identify the cardholder.

[0036] Fig. 5 is an example of the error screen S4. The error screen S4 in Fig. 5 is displayed on the display device 13 when it indicates that payment using the credit card selected by the user U[q] on the third screen S3 is not possible. The error screen S4 displays a message indicating that payment is not possible. For example, the error screen S4 is displayed when the credit limit of the user U[q] is exceeded due to the user's credit status.

[0037] FIG. 6 is an example of the second screen S2. The second screen S2 shown in FIG. 6 is an authentication screen used for identity authentication. The second screen S2 is used to prevent fraudulent use of credit cards when using services over a network. The second screen S2 includes the name of the store where the service will be used, the payment amount indicating the price, the date, and the card number. The second screen S2 also includes a password text box A21 and a send button B21. The text box A21 is a box for entering a password. The password is transmitted from the card management server 5 to the terminal device 1[q], for example, via SMS (Short Message Service) or email. The user U[q] enters the password in the text box A21 and presses the send button B21. By pressing the send button B21, the password is transmitted to the payment server 3 via the communication device 15 as "authentication information" for identity authentication.

[0038] Fig. 7 is an example of an authentication error screen S5. The authentication error screen S5 in Fig. 7 is displayed when the password entered in Fig. 6 is different from the password sent by SMS, email, or the like.

[0039] FIG. 8 is an example of the payment completion screen S6. The payment completion screen S6 in FIG. 8 is used to indicate that the electronic payment has been completed when the credit card holder registration has been completed and the credit card has been authenticated. By displaying the payment completion screen S6, the user U[q] can know that the electronic payment has been successfully completed. For example, after the payment completion screen S6 is displayed, the screen may transition from the payment app screen to the store service application screen at a predetermined time interval, either at the instruction of the user U[q] or without the instruction of the user U[q].

[0040] Returning to Fig. 2, the registration unit 114 requests the settlement server 3 to register the account holder registration of the user U[q] via the input device 14.

[0041] The settlement unit 115 continues processing related to electronic settlement after the registration unit 114 has registered the account holder in the settlement server 3. For example, as processing related to electronic settlement, the settlement unit 115 performs processing related to identity authentication for settlement and processing related to a settlement request when authentication is successful.

[0042] The display device 13 is hardware for displaying various types of information. As the display device 13, various display panels such as a liquid crystal display panel and an organic EL display panel can be adopted. In this embodiment, the display device 13 displays the various images described above under the control of the display control unit 113.

[0043] The input device 14 is hardware for receiving instructions from a user U[q] of the terminal device 1[q]. The input device 14 may be, for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or a combination of these devices. The display device 13 and the input device 14 may be configured as an integrated device. In this case, for example, a touch panel may be used as the display device 13 and the input device 14.

[0044] The communication device 15 is hardware for communicating with external devices such as the payment server 3, the store device 2, and the card management server 5 that exist outside the terminal device 1[q] via the network NW.

[0045] A-3. Payment Server 3 Fig. 9 is a block diagram showing an example of the configuration of the payment server 3 in Fig. 1. As shown in Fig. 9, the payment server 3 includes a processing device 31, a storage device 32, a communication device 35, and a bus 30 connecting these devices to each other.

[0046] The storage device 32 is a recording medium readable by the processing device 31. The storage device 32 includes, for example, a volatile memory such as a RAM that functions as a work area for the processing device 31, and a non-volatile memory such as an EEPROM that stores various information.

[0047] The storage device 32 stores user management information DU and a control program PG2. The user management information DU includes user identification information DID[q] and a credit card information file DCF[q]. The user identification information DID[q] includes an identifier for uniquely identifying the user U[q] of the terminal device 1[q] from among the Q users U[1] to U[Q] managed by the payment server 3, and various identification information related to the terminal device 1[q]. The user management information DU includes the user identification information DID[q] and a credit card information file DCF[q].

[0048] The user identification information DID[q] includes an identifier for uniquely identifying the user U[q] of the terminal device 1[q] from among the Q users U[1] to U[Q] managed by the payment server 3, and various identification information related to the terminal device 1[q].

[0049] FIG. 10 is an example of a credit card information file DCF[q]. The credit card information file DCF[q] contains information about the credit card of user U[q]. The credit card information file DCF[q] includes multiple pieces of credit card information DCR[1] and [2]. Each piece of credit card information DCR[1] and [2] is information about a credit card owned by user U[q], and is information about a credit card that user U[q] has registered with the payment server 3 via terminal device 1[q]. The number of pieces of credit card information may be one, or may be three or more.

[0050] Each of the credit card information DCR[1] and [2] includes, for example, a terminal ID, the card number, expiration date, credit card name, and cardholder of the credit card owned by the user U[q]. The terminal ID is an identifier that indicates the terminal device 1[q]. If the cardholder is registered, the credit card information DCR[q] includes the cardholder's name, but if the cardholder is not registered, it includes a null identifier indicating that nothing is included. The number of pieces of credit card information DCR included in the credit card information file DCF[q] can be any number, as long as it is one or more.

[0051] The credit card information DCR[1] includes information that the international brand of the credit card owned by user U[q] of terminal device 1[q] with terminal ID "00q" is "ABC" and the card number is "1111-2222-3333". The credit card information DCR[1] also includes information that the expiration date is "April 2027" and the cardholder is "AKIRA OBAYASHI". The credit card information DCR[1] also includes information that the international brand of the credit card owned by user U[q] of terminal device 1[q] with terminal ID "00q" is "DEF" and the card number is "1234-3456-6789". The credit card information DCR[2] also includes information that the expiration date is "July 2029" and the cardholder is unregistered, including the identifier "null".

[0052] The processing device 31 includes a processor. The processor provided in the processing device 31 is configured to include, for example, one or more CPUs. However, the processor provided in the processing device 31 may be configured to include hardware such as a GPU, DSP, ASIC, PLD, or FPGA in addition to the one or more CPUs, or in place of some or all of the one or more CPUs. The processor provided in the processing device 31 executes a control program PG2 stored in the storage device 32 and operates in accordance with the control program PG2, thereby functioning as a communication control unit 311, a management unit 312, and a determination unit 313.

[0053] The communication control unit 311 causes the communication device 15 to transmit and receive various information between the terminal device 1[q], the store device 2, and the card management server 5. The communication control unit 311 communicates with the terminal device 1[q] of the user U[q] via the communication device 35.

[0054] For example, the communication control unit 311 receives a payment request, which is a request for electronic payment, from the terminal device 1[q] via the communication device 35. The communication control unit 311 also transmits various responses to the payment request to the terminal device 1[q] via the communication device 35. The communication control unit 311 also transmits an authentication request to the card management server 5 via the communication device 35. The communication control unit 311 also receives a response to the authentication request from the card management server 5 via the communication device 35. The authentication request is a request to the card management server 5 for authentication of a credit card for which the cardholder is registered. The authentication request includes the card number and cardholder based on the credit card information file DCF[q] and the payment amount included in the payment request received from the terminal device 1[q]. In response to the response from the card management server 5, the communication control unit 311 also transmits information indicating whether the payment is possible or not to the terminal device 1[q] via the communication device 35.

[0055] The management unit 312 manages the credit card information DCR[q], which associates cardholders with card numbers. Specifically, the management unit 312 updates the credit card information DCR[q]. The management unit 312 also stores various types of information in the storage device 32 and identifies specific information from the various types of information stored in the storage device 32.

[0056] The determination unit 313 determines whether the cardholder is registered by referring to the credit card information DCR[q].

[0057] The communication device 35 is hardware for communicating with external devices such as the terminal device 1[q], the store device 2, and the card management server 5 that are located outside the payment server 3 via the network NW.

[0058] A4. Operation of the Electronic Payment System 100 Fig. 11 is a sequence chart showing an example of the operation of the electronic payment system 100 of this embodiment. Fig. 12 is an example of the service payment screen S8.

[0059] The sequence chart shown in Figure 11 shows the operation of the electronic payment system 100 when a user U[q] who owns a terminal device 1[q] makes an electronic payment to receive a service at a store that has a store device 2.

[0060] For example, when a user U[q] specifies a service that he / she wants to receive at a store that has the in-store device 2 and makes payment for the service, the service payment screen S8 of FIG.

[0061] The service payment screen S8 in FIG. 12 is a screen used by user U[q] to make payment for the service he or she wishes to receive. The service payment screen S8 includes multiple payment method options A81, A82, and A83, and a payment method selection button B85. The payment method option A81 is an option for combined payment with telephone charges, and is accompanied by a selection button B81. The payment method option A82 is an option for credit card payment, and is accompanied by a selection button B82. The payment method option A83 is an option for code payment, and is accompanied by a selection button B83. For example, user U[q] can apply for payment by code payment by selecting the selection button B83 for payment method option A83, which corresponds to code payment, and pressing the payment method selection button B85.

[0062] The following describes an example in which the sequence chart of Fig. 11 starts from a state in which the service payment screen S8 of Fig. 12 is displayed on the display device 13. The following also describes an example of electronic payment using a credit card whose cardholder is registered, and an example of electronic payment using a credit card whose cardholder is not registered.

[0063] A4-1. Electronic payment when the account holder is already registered In the following example, an example of the operation of the electronic payment system 100 in electronic payment when the cardholder has already been registered will be described. In this example, the credit card information DCR[1] shown in FIG. 10 corresponds to the "first credit card information." The card number of the credit card information DCR[1] corresponds to the "first card number." The cardholder of the credit card information DCR[1] corresponds to the "first cardholder." Electronic payment using the credit card information DCR[1] corresponds to the "first electronic payment." The credit card corresponding to the credit card information DCR[1] is the "first credit card."

[0064] In step S101 of FIG. 11, the terminal device 1[q] launches the payment app. There are the following modes for launching the payment app. The first mode is when the user U[q] operates the terminal device 1[q] to launch the payment app. The second mode is when the store service application and the payment app are linked. Specifically, this mode is when electronic payment service X is selected on a screen displayed by the store service application. The third mode is when electronic payment service X is selected from among the payment method options displayed on the web page of an e-commerce site.

[0065] In step S102, the reception unit 111 of the terminal device 1[q] receives a screen transition operation. In this example, the screen transition operation is an operation for displaying the third screen S3, which is a payment confirmation screen. Note that, in the payment method selection screen shown in FIG. 12, a screen transition operation in which the user U[q] selects the selection button B82 corresponding to a credit card and presses the payment method determination button B85 may correspond to the operation for displaying the third screen S3, which is a payment confirmation screen.

[0066] In step S103, the communication control unit 112 of the terminal device 1[q] transmits a screen transition request via the communication device 15. The screen transition request includes the terminal ID and screen identification information indicating that the transition destination screen is the third screen S3, which is the payment confirmation screen.

[0067] In step S104, the management unit 312 of the payment server 3 transmits a response to the screen transition request to the terminal device 1[q] via the communication device 35. Specifically, the management unit 312 identifies control parameters related to the credit card to be displayed on the third screen S3 based on the screen identification information included in the screen transition request. The control parameters include specific credit card information.

[0068] In step S105, the display control unit 113 of the terminal device 1[q] displays the third screen S3 shown in FIG. 3, which is a payment confirmation screen, on the display device 13 based on the control parameters included in the response to the screen transition request.

[0069] In step S106, the acceptance unit 111 of the terminal device 1[q] accepts card payment using the first credit card. That is, the acceptance unit 111 accepts the first electronic payment using the first credit card. In this example, when the selection button B32 of the option A32, whose name is registered, is selected and the button B31 is pressed, the card payment is accepted using the credit card corresponding to the credit card information DCR[1] as the first credit card.

[0070] In step S107, the communication control unit 112 of the terminal device 1[q] transmits a payment request to the payment server 3 via the communication device 15. The payment request includes the terminal ID indicating the terminal device 1[q], the first card number of the first credit card, "1111-2222-3333", and the payment amount.

[0071] In step S108, the determination unit 313 of the payment server 3 determines whether or not the first card holder is registered with the first card number by referring to the credit card information DCR[1], which is the first credit card information.

[0072] In this example, the credit card information DCR[1] shown in Fig. 10 includes information about the cardholder. Therefore, in step S108, the determination unit 313 determines that the first cardholder has already been registered for the first card number. The determination result in step S108 is negative, and the processing device 31 proceeds to step S114.

[0073] In step S114, the communication control unit 311 sends an authentication request to the card management server 5 via the communication device 35. The authentication request includes, for example, the first card number, the first cardholder, the payment amount, the telephone number, and the email address. The telephone number and the email address are included in the user management information DU shown in FIG. 3. The communication control unit 311 references the user management information DU to obtain the telephone number and email address corresponding to the user U[q].

[0074] In step S115, the card management server 5 performs authentication processing. Specifically, as part of the authentication processing, for example, it determines whether the combination of the first card number and the first cardholder is correct. In the authentication processing, the card management server 5 may further determine whether the payment amount is within the credit limit. If the determination result is positive, the authentication result indicates that payment is possible, and if the determination result is negative, the authentication result indicates that payment is not possible.

[0075] In step S116, the payment server 3 receives an authentication return from the card management server 5 via the communication device 35. The authentication return includes information indicating whether payment is possible or not, which is the result of the authentication process by the card management server 5. Furthermore, if the authentication return includes information indicating payment is possible, the authentication return also includes destination information. The destination information indicates a URL for redirecting to the card management server 5. The authentication return indicates whether payment is not possible or possible. The destination information is information necessary for the card management server 5 to perform identity authentication to confirm that the person operating the terminal device 1[q] is user U[q].

[0076] In step S117, the payment server 3 transmits an authentication return to the terminal device 1[q] via the communication device 35.

[0077] If authentication is not successful, the authentication return in step S117 indicates that payment is not possible. In this case, for example, the display control unit 113 of the terminal device 1[q] displays the error screen S4 of FIG. 5 indicating that payment is not possible on the display device 13. Furthermore, if the authentication return indicates that payment is not possible, the payment unit 115 of the terminal device 1[q] abandons the first payment process. Note that in this case, for example, the process may return to step S105 again, and the third screen S3 of the terminal device 1[q] may be displayed on the display device 13.

[0078] If the authentication is successful, the authentication return in step S117 includes information indicating that payment is possible and the destination information. Note that if personal authentication is not required, the authentication return does not include the destination information even if payment is possible.

[0079] When the terminal device 1[q] receives an authentication return including information indicating that payment is possible and destination information, the communication control unit 112 of the terminal device 1[q] accesses the redirect URL indicated by the destination information through the authentication return redirect in step S118. As a result, the display control unit 113 of the terminal device 1[q] displays a web page generated by the card management server 5 on the display device 13. Specifically, the second screen S2 of FIG. 6 is displayed on the display device 13. Furthermore, when the authentication return indicates that payment is possible, the payment unit 115 of the terminal device 1[q] continues the first electronic payment.

[0080] The card management server 5 sends the password to be entered in the text box A21 on the second screen S2 to the terminal device 1[q] via SMS or email. The password is authentication information used to authenticate the user U[q].

[0081] After user U[q] enters a password in text box A21, user U[q] presses send button B21, and reception unit 111 receives the password entered by user U[q] in text box A21 and the press of send button B21. Although not shown in the sequence chart, communication control unit 112 of terminal device 1[q] transmits the entered password to the destination indicated in the destination information via communication device 15.

[0082] Although not shown in the sequence chart, the card management server 5 executes personal authentication processing when it detects that a password has been entered into a web page it manages. In the personal authentication processing, it is determined whether the entered password matches the password sent to the terminal device 1[q]. If the determination result is negative, the card management server 5 prompts the user U[q] to re-enter the password in the text box A21, for example, by displaying a message such as "The password is incorrect" on the second screen S2 of FIG. 6. If the correct password is not entered within a predetermined period of time after the second screen S2 is displayed, the personal authentication is deemed to be negative. On the other hand, if the determination result is positive, the personal authentication is deemed to be successful.

[0083] In step S119, the card management server 5 transmits a result return including whether or not the personal authentication using the second screen S2 was successful to the terminal device 1[q].

[0084] If the returned result indicates that the identity authentication is not successful, the display control unit 113 of the terminal device 1[q] displays the identity authentication error screen S5 shown in Figure 7 on the display device 13. In this case, the payment unit 115 of the terminal device 1[q] abandons the first electronic payment. In this case, for example, the process may return to step S105 again, and the terminal device 1[q] may display the third screen S3 on the display device 13.

[0085] If the returned result indicates that user authentication is successful, the settlement unit 115 of the terminal device 1[q] continues the first electronic settlement. That is, the settlement unit 115 continues the first electronic settlement if the card management server 5, to which the password serving as authentication information is sent, authenticates the user U[q] based on the sent password.

[0086] If the returned result indicates that identity authentication is possible, in step S120, the communication control unit 112 of the terminal device 1[q] sends a payment request to the payment server 3 via the communication device 15. In step S121, the payment server 3 sends the payment request to the card management server 5 via the communication device 35. The payment request includes, for example, the payment amount, the first card number, the first cardholder, the terminal ID, information identifying the store that owns the store device 2 that is the payment recipient, and information identifying the card management server 5 that is the transmission destination.

[0087] In step S122, the card management server 5 performs a payment process. The payment process is a process of transferring the payment amount to the payee. In this process, a withdrawal reservation is made from the bank account linked to the first card number.

[0088] In step S123, the card management server 5 transmits a payment result notification to the payment server 3. In step S124, the payment server 3 transmits the payment result notification to the terminal device 1[q] via the communication device 35. The payment result notification includes information that the payment has been executed and the payment amount.

[0089] In step S125, the display control unit 113 of the terminal device 1[q] causes the display device 13 to display the payment completion screen S6 of FIG. 8, which indicates that the payment has been completed.

[0090] The above is the operation of the electronic payment system 100 in electronic payments when the account holder is not registered. An example of this has been described.

[0091] A4-2. Electronic payment when the account holder is not registered In the following example, an example of the operation of the electronic payment system 100 in electronic payment when the account holder is not registered will be described. Note that the following mainly describes the differences from the electronic payment when the account holder is already registered, and overlapping details will be omitted as appropriate. Also, in the following, credit card information DCR[2] corresponds to the "first credit card information." The card number of the credit card information DCR[2] corresponds to the "first card number." The account holder of the credit card information DCR[2] corresponds to the "first account holder." Electronic payment using credit card information DCR[2] corresponds to the "first electronic payment." The credit card corresponding to credit card information DCR[2] is the "first credit card."

[0092] Steps S101 to S105 are the same as in the previous example.

[0093] In step S106, the acceptance unit 111 of the terminal device 1[q] accepts the card payment using the first credit card. In this example, when the selection button B33 of the option A33, whose name is not registered, is selected on the third screen S3 shown in Figure 3 and the button B31 is pressed, the card payment using the credit card corresponding to the credit card information DCR[2] as the first credit card is accepted.

[0094] In step S107, the communication control unit 112 of the terminal device 1[q] transmits a payment request to the payment server 3 via the communication device 15. The payment request includes the terminal ID indicating the terminal device 1[q], the first card number of the first credit card, “1234-3456-6789”, and the payment amount.

[0095] In step S108, the determination unit 313 of the payment server 3 determines whether the first card holder is registered with the first card number by referring to the credit card information DCR[2], which is the first credit card information.

[0096] In this example, the credit card information DCR[2] shown in Fig. 10 does not include cardholder information. Therefore, in step S108, the determination unit 313 determines that the first cardholder has not yet been registered for the first card number. In this case, in step S109, the communication control unit 311 transmits a registration request to the terminal device 1[q] via the communication device 35. The registration request includes, for example, the first card number, the first cardholder, and the terminal ID.

[0097] In step S110, the display control unit 113 of the terminal device 1[q] displays the first screen S1 of Fig. 4 on the display device 13. The first screen S1 is a screen for registering a holder, and is a screen that prompts the user U[q] to register a holder.

[0098] In step S111, the reception unit 111 of the terminal device 1[q] accepts the first credit card payment by receiving input of the first name by the user U[q] in the text box A1 via the input device 14 and pressing the registration button B1.

[0099] In step S112, the registration unit 114 of the terminal device 1[q] requests that the first cardholder entered on the first screen S1 be registered in the payment server 3. Specifically, the registration unit 114 causes the communication control unit 112 to send a registration response to the payment server 3 via the communication device 15. The registration response includes, for example, the terminal ID, the first card number, and the first cardholder.

[0100] In step S112, the management unit 312 of the payment server 3 performs cardholder registration of the first cardholder. Specifically, the management unit 312 associates the first cardholder with the first card number by updating the credit card information file DCF[q].

[0101] In step S114, the communication control unit 311 sends an authentication request to the card management server 5 via the communication device 35. The authentication request includes, for example, the first card number, the first cardholder, the payment amount, the telephone number, and the email address. The authentication request is determined based on the updated credit card information file DCF[q].

[0102] In step S115, the card management server 5 performs authentication processing. Specifically, as part of the authentication processing, for example, the card management server 5 analyzes whether the combination of the first card number and the cardholder is correct, whether the payment amount is within the credit limit, etc., to check for fraudulent use.

[0103] In step S116, the payment server 3 receives an authentication return from the card management server 5 via the communication device 35. The authentication return includes information indicating the result of the authentication process by the card management server 5. The authentication return also includes a redirect URL to the card management server 5, which is destination information indicating the card management server 5 to which the terminal device 1[q] is the destination. The authentication return also indicates whether payment is possible or not.

[0104] In step S117, the payment server 3 transmits an authentication return to the terminal device 1[q] via the communication device 35.

[0105] If authentication is not successful, the authentication return in step S117 indicates that payment is not possible. In this case, for example, the display control unit 113 of the terminal device 1[q] displays the error screen S4 of FIG. 5 indicating that payment is not possible on the display device 13. Furthermore, if the authentication return indicates that payment is not possible, the payment unit 115 of the terminal device 1[q] abandons the first payment process. Note that in this case, for example, the process may return to step S105 again, and the third screen S3 of the terminal device 1[q] may be displayed on the display device 13.

[0106] If the authentication is successful, the authentication return in step S117 indicates that payment is possible. In this case, for example, the display control unit 113 of the terminal device 1[q] causes the display device 13 to display the second screen S2 of Fig. 6, which indicates that payment is possible. Furthermore, if the authentication return indicates that payment is possible, the payment unit 115 of the terminal device 1[q] continues the first electronic payment.

[0107] If the first electronic payment is to be continued, the acceptance unit 111 accepts the password input by the user U[q] into the text box A21 and the press of the send button B21 via the payment unit 115 of the terminal device 1[q] on the second screen S2.

[0108] Steps S118 to S125 are the same as in the previous example.

[0109] An example of the operation of the electronic payment system 100 in electronic payment when the account holder is already registered has been described above.

[0110] As described above, the electronic payment program PG1 causes the computer to function as the display control unit 113, the registration unit 114, and the settlement unit 115. When the display control unit 113 accepts a first electronic payment, which is an electronic payment using a first credit card designated by the user U[q], it inquires of the payment server 3 about the use of the first credit card. This is mainly the content of steps S106 and S107. If this inquiry confirms that the first cardholder, who is the cardholder of the first credit card, needs to be registered, the display control unit 113 displays on the display device 13 a first screen S1 prompting the user U[q] to input the first cardholder. This is mainly the content of step S110. Furthermore, the registration unit 114 requests that the first cardholder entered on the first screen S1 be registered in the payment server 3. This is mainly the content of step S112. Furthermore, the settlement unit 115 continues the first electronic payment after the registration unit 114 has registered the first cardholder in the payment server 3. Specifically, this mainly corresponds to the operation of the terminal device 1[q] from step S117 onwards.

[0111] The electronic payment program PG1 displays the first screen S1 on the display device 13 if the first cardholder is not registered at the time of the first electronic payment. Therefore, if the security policy of the first credit card registered by user U[q] for use in electronic payments is changed, making it necessary to register the first cardholder, the first cardholder can be registered at the time the first electronic payment is made using the first credit card. This allows the first electronic payment to continue. As a result, re-registration of the first credit card, which involves inputting the first cardholder's name, is not required. Furthermore, since the first electronic payment is not canceled and user U[q] is not prompted to register the first cardholder, the risk of user U[q] abandoning the first electronic payment can be reduced.

[0112] Furthermore, if the display control unit 113 determines through the above-mentioned inquiry that there is no need to register the first account holder, it does not display the first screen S1 on the display device 13. As explained in the example of electronic payment when the account holder is already registered, in this example, steps S109 to S113 for account holder registration are not performed, and the first screen S1 is not displayed on the display device 13.

[0113] If it is determined that there is no need to register the first account holder, the first screen S1 prompting the user U[q] to enter the first account holder is hidden. This improves convenience for the user U[q] compared to when the first electronic payment prompts the user U[q] to enter the first account holder, regardless of whether the first account holder of the first credit card is registered or not.

[0114] Furthermore, the electronic payment program PG1 causes the computer to function as a reception unit 111 and a communication control unit 112. The reception unit 111 receives the first electronic payment. This is mainly the content of step S106. When the reception unit 111 receives the first electronic payment, the communication control unit 112 transmits a payment request, including an inquiry, to the payment server 3 via the communication device 15. The communication control unit 112 then receives a registration request from the payment server 3 via the communication device 15, indicating that the first account holder needs to be registered. If the display control unit 113 does not receive a registration request, for example, if the registration request of step S109 is not received, the display control unit 113 displays the first screen S1 on the display device 13. On the other hand, if the display control unit 113 receives a registration request, for example, if the registration request of step S109 is received, the display control unit 113 does not display the first screen S1 on the display device 13, as described in the example of electronic payment when the account holder is already registered.

[0115] In this way, the terminal device 1[1] using the electronic payment program PG1 can accommodate both cases where the cardholder is registered and cases where it is not. Therefore, the user U[q] does not need to significantly change the operation for electronic payment depending on whether or not the cardholder is registered. If the cardholder is not registered, the cardholder can be registered simply by using the first screen S1. Furthermore, since the link between the first card number and the first cardholder is managed by the payment server 3, for example, if a new terminal device 1[q] is introduced following a breakdown of the terminal device 1[q], installing the electronic payment program PG1 on the new terminal device 1[q] makes it possible to register the first cardholder during the first electronic payment, even if the first cardholder of the first credit card is not registered.

[0116] Furthermore, if there is no need to register the first user and personal authentication is required for the first electronic payment, the communication control unit 112 receives from the payment server 3 via the communication device 15 in step S117 an authentication return including destination information indicating a destination of authentication information for personal authentication. Furthermore, upon receiving the destination information, the display control unit 113 displays on the display device 13 a second screen S2 prompting the user to enter authentication information. When the authentication information is entered on the second screen S2, the communication control unit 112 transmits a password, which is the authentication information, to the card management server 5, which is the destination, via the communication device 15 by an authentication return redirect in step S118. If the card management server 5, which is the destination, authenticates the user U[q] based on the authentication information, the payment unit 115 continues the first electronic payment.

[0117] In this way, when further personal authentication is required, the authentication information is sent to the card management server 5, which is the destination of the authentication information, and if the authentication information is authenticated, the first electronic payment can be continued. This makes it possible to prevent the user U[q] from abandoning the electronic payment and reduce fraudulent use.

[0118] 3 includes a payment amount A31, multiple credit card options A32 and A33, and a button B31 for accepting the payment. The acceptance unit 111 accepts the first electronic payment when the button B31 is pressed while the option A32 or A33 corresponding to the first credit card is selected from the multiple credit card options A32 and A33 on the third screen S3.

[0119] When user U[q] makes an electronic payment, multiple options A32 and A33 are presented, which improves convenience for user U[q].

[0120] On the third screen S3, the option A32 or A33 corresponding to the first credit card includes the first card number. Furthermore, the option A32 or A33 corresponding to the first credit card includes an indication that the first cardholder is not registered, or the first cardholder.

[0121] The user U[q] can determine whether the first cardholder of the first credit card is registered or not via the third screen S3, which improves the convenience of electronic payment.

[0122] The payment server 3 also includes a communication control unit 311, a management unit 312, and a determination unit 313. The communication control unit 311 communicates with the card management server 5 and the terminal device 1[q] of the user U[q] via the communication device 35. The management unit 312 manages a credit card information file DCF[q] that links a first card number, which is the card number of a first credit card that the user U[q] can use for electronic payments, with a first name, which is the name of the cardholder of the first credit card.

[0123] When the communication control unit 311 receives from the terminal device 1[q] a payment request including the first card number and payment amount, and requesting a first electronic payment, which is an electronic payment using the first credit card, the determination unit 313 determines whether the first cardholder is registered by referring to the credit card information file DCF[q]. Specifically, this determination is mainly the content of steps S107 and S108. Furthermore, when the determination result of the determination unit 313 is negative, in step S109, the communication control unit 112 transmits a registration request indicating that the first cardholder needs to be registered to the terminal device 1[q] via the communication device 35.

[0124] If registration of the first cardholder is required, the payment server 3 sends a registration request to the terminal device 1[q]. In response to this registration request, the user U[q] registers the cardholder. Therefore, the user U[q] can register the first cardholder when making the first electronic payment using the first credit card. The payment server 3 manages the association between the first card number and the first cardholder. For example, if a new terminal device 1[q] is installed after the failure of the terminal device 1[q], installing the electronic payment program PG1 in the new terminal device 1[q] makes it possible to register the first cardholder at the time of the first electronic payment, even if the first cardholder of the first credit card has not yet been registered. Furthermore, if the first card number and the first cardholder have been associated, the payment server 3 queries the card management server 5 for credit-related information, thereby reducing the processing load on the card management server 5 and simplifying card payments at the in-store device 2.

[0125] Furthermore, if the determination result of the determination unit 313 is positive in step S108, the communication control unit 311 sends an authentication request including the first card number, the first cardholder name, and the payment amount to the card management server 5 via the communication device 35 in step S114. The communication control unit 311 receives an authentication return corresponding to the authentication request from the card management server 5 via the communication device 35 in step S116. The communication control unit 311 sends the authentication return to the terminal device 1[q] via the communication device 35 in step S117. The authentication return indicates whether the payment is possible or not.

[0126] In this way, the payment server 3 makes the determination and communicates with the card management server 5. This reduces the processing load on the card management server 5 and simplifies card payment at the in-store device 2.

[0127] In response to the registration request of step S109, the communication control unit 311 receives a registration response including the first cardholder name and the first card number from the terminal device 1[q] via the communication device 35 in step S112. The management unit 312 associates the first cardholder with the first card number by updating the credit card information file DCF[q]. This is performed in step S113. In step S114, the communication control unit 311 sends a request including the first card number and first cardholder based on the updated credit card information file DCF[q] and the payment amount included in the payment request as an authentication request to the card management server 5 via the communication device 35.

[0128] In this way, the payment server 3 performs the cardholder registration and also performs communication with the card management server 5. This makes it possible to reduce the processing load on the card management server 5.

[0129] B. Other (1) In the above-described embodiment, storage device 12 and storage device 32 are exemplified by ROM and RAM, but may be a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory device (e.g., a card, a stick, a key drive), a CD-ROM (Compact Disc-ROM), a register, a removable disk, a hard disk, a floppy (registered trademark) disk, a magnetic strip, a database, a server, or any other suitable storage medium. The program may also be transmitted from a network via a telecommunications line. The program may also be transmitted from a communications network NET via a telecommunications line.

[0130] (2) In the above-described embodiments, the described information, signals, etc. may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0131] (3) In the above-described embodiment, input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0132] (4) In the above-described embodiment, the determination may be made by a value (0 or 1) represented using one bit, by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0133] (5) The order of the process procedures, sequences, flowcharts, etc. illustrated in the above-described embodiments may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0134] (6) Each function illustrated in Figures 2 and 9 is realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. A functional block may also be realized by combining software with the single device or the multiple devices.

[0135] (7) The programs exemplified in the above-described embodiments should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether they are called software, firmware, middleware, microcode, hardware description language, or by other names.

[0136] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0137] (8) In each of the foregoing embodiments, the terms "system" and "network" are used interchangeably.

[0138] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0139] (10) In the above-described embodiments, the terminal device 1[q] may be a mobile station (MS). Those skilled in the art may also refer to a mobile station as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term. In this disclosure, the terms "mobile station," "user terminal," "user equipment (UE)," "terminal," etc. may be used interchangeably.

[0140] (11) In the above-described embodiments, the terms "connected," "coupled," or any variations thereof refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0141] (12) In the above embodiments, the phrase "based on" does not mean "based only on," unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0142] (13) As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0143] (14) In the above embodiments, when "include," "including," and variations thereof are used, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive or.

[0144] (15) In this disclosure, where articles are added by translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are plural.

[0145] (16) In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

[0146] (17) The contents of the embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0147] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0148] 1...terminal device, 2...store device, 3...payment server, 5...card management server, 100...electronic payment system, 111...reception unit, 112...communication control unit, 113...display control unit, 114...registration unit, 115...payment unit, 311...communication control unit, 312...management unit, 313...determination unit, A31...payment amount, A32...options, A33...options, DCF...credit card information file, DCR...credit card information, DID...user identification information, DU...user management information, NW...network, PG1...electronic payment program, PG2...control program, S1...first screen, S2...second screen, S3...third screen, S4...error screen, S5...personal authentication error screen, S6...payment completion screen, S8...service payment screen, U...user.

Claims

1. Computer, a display control unit that, when accepting a first electronic payment using a first credit card designated by a user, makes an inquiry to a payment server regarding the use of the first credit card, and when it is confirmed that a first cardholder who is the cardholder of the first credit card needs to be registered, displays a first screen on a display device that prompts the user to input the first cardholder; a registration unit that requests that the first account holder input on the first screen be registered in the payment server; After the first account holder is registered in the payment server by the registration unit, the payment server functions as a payment unit that continues the first electronic payment. Electronic payment programs.

2. the display control unit does not display the first screen on the display device when it is confirmed by the inquiry that there is no need to register the first user. The electronic payment program according to claim 1 .

3. The computer a reception unit that receives the first electronic payment; when the first electronic payment is accepted by the accepting unit, the accepting unit functions as a communication control unit that transmits a payment request for the first electronic payment to the payment server via a communication device, and receives a registration request from the payment server via the communication device, indicating that the first account holder needs to be registered; The display control unit When the registration request is received, the first screen is displayed on the display device; If the registration request is not received, the first screen is not displayed on the display device. The electronic payment program according to claim 2 .

4. the communication control unit receives, when it is not necessary to register the first account holder and personal authentication is required for the first electronic payment, from the payment server via the communication device, destination information indicating a destination of authentication information for the personal authentication; the display control unit, when receiving the destination information, displays a second screen on the display device prompting the user to input the authentication information; the communication control unit, when the authentication information is input to the second screen, transmits the authentication information to the destination via the communication device; the settlement unit continues the first electronic settlement if the user is authenticated at the destination based on the authentication information; The electronic payment program according to claim 3 .

5. the display control unit displays, on the display device, a third screen including a payment amount, a plurality of credit card options, and a button to accept the payment; the accepting unit accepts the first electronic payment when the button is pressed with an option corresponding to the first credit card selected from the plurality of credit card options on the third screen; The electronic payment program according to claim 3 .

6. The options corresponding to the first credit card include an indication of "not registered cardholder" indicating that the first cardholder is not registered, or the first cardholder and the card number. The electronic payment program according to claim 5 .

Images