Payment server, method, and program

Abstract

Making fraud more difficult while still maintaining convenience. [Solution] A payment server comprising: a payment processing unit that performs electronic payment based on payment information obtained by communication with a payment app running on a first terminal device; and an authentication unit that displays a first code image on a second terminal device in response to a call from an e-commerce interface screen, displays a second code image on the second terminal device when first information indicating that the payment app has read the first code image is received from the payment app, and performs a predetermined operation related to the e-commerce when second information indicating that the payment app has read the second code image is received from the payment app.

Description

[Technical field]

[0001] The present invention relates to a payment server, a method, and a program. [Background technology]

[0002] Conventionally, attempts have been made to smoothly progress electronic payments by linking the services of businesses that mainly provide electronic payment services with electronic commerce. For example, when a business sells a product on a website, if the login information for the business is associated with the login information for the electronic payment service (account linkage), electronic payments can be easily made using the balance of the electronic payment service, etc. In relation to this, Patent Document 1 describes that when an electronic payment service is called from the electronic commerce side, an API provides the function of the electronic payment service without authentication based on the presence or absence of the user's consent, etc. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7085700 Summary of the Invention [Problem to be solved by the invention]

[0004] In addition to the technology described in Patent Document 1, there have been attempts to simplify authentication by displaying a code image for account linking on an electronic commerce site and having the code image loaded into a payment app that constitutes an electronic payment service. However, in recent years, there have been concerns about fraudulent acts in which fraudsters photograph or capture the code image and send it to a terminal device of another person, and then use some kind of fraudulent activity such as spam or phishing to trick the other person into loading the code image into the payment app, thereby making the other person make electronic payments for products purchased in electronic commerce. Conventional technologies have sometimes not provided sufficient countermeasures against such fraudulent activities while maintaining convenience.

[0005] The present invention has been made in consideration of these circumstances, and one of its objectives is to provide a payment server, method, and program that can make fraudulent activities more difficult while maintaining convenience. [Means for solving the problem]

[0006] One aspect of the present invention is a payment server comprising: a payment processing unit that performs electronic payment based on payment information obtained by communication with a payment app running on a first terminal device; and an authentication unit that displays a first code image on a second terminal device in response to a call from an interface screen for electronic commerce, displays a second code image on the second terminal device when first information indicating that the payment app has read the first code image is received from the payment app, and performs a predetermined operation related to the electronic commerce when second information indicating that the payment app has read the second code image is received from the payment app. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to make fraudulent acts more difficult while maintaining convenience. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates basic aspects of brick-and-mortar electronic payment. [Diagram 2] FIG. 1 is a diagram showing an example of a configuration for performing electronic payment (terminal payment) using a payment application. [Diagram 3] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 4] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 174. [Diagram 5] FIG. 13 is a diagram showing an outline of a process flow when a user scan is performed. [Figure 6] FIG. 13 is a diagram showing an overview of the process flow when a store scan is performed. [Figure 7]FIG. 1 is a diagram showing an example of a configuration for performing electronic payment (card payment) using a payment card. [Figure 8] FIG. 13 is a diagram illustrating an example of a configuration related to a predetermined operation. [Figure 9] 11A and 11B are diagrams showing examples of interface screens IM1 and IM2 that the authentication unit 140 causes the second terminal device 80 to display. [Figure 10] 13 is a flowchart showing an example of a process flow relating to account linkage (and login permission). [Figure 11] FIG. 13 is a diagram showing an example of an app screen IA1 for confirming account linkage. [Figure 12] FIG. 13 is a diagram showing an example of an application screen IA2 for additional confirmation. [Figure 13] 13A and 13B are diagrams showing examples of interface screens IM3 and IM4 that the authentication unit 140 causes the second terminal device 80 to display during online payment. [Figure 14] 13A and 13B are diagrams showing examples of interface screens IM5 and IM6 that an IF screen providing unit 310 of an electronic commerce server 300 causes a second terminal device 80 to display. [Figure 15] 13 is a flowchart showing an example of a process flow relating to a predetermined operation 4-6. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] [overview] Hereinafter, with reference to the drawings, an embodiment of a payment server, a method, and a program according to the present invention will be described. In the following description, an electronic payment service and an electronic commerce service will appear. These services are provided by different mechanisms (the businesses may be different or the same). First, the electronic payment service will be described. An application program, a payment server, and a credit card server work together to provide the electronic payment service. In the following description, the application program will be referred to as a payment application. Also, a combination of the payment server and the credit card server may be referred to as a payment management system. The electronic payment service is a service that supports payments related to the purchase of goods and services at a store. A store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for electronic commerce. The virtual store may include a store provided by an entity (a provider of the electronic commerce service) different from the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at a store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be carried out between the user and the store.

[0010] [Electronic payment methods at brick-and-mortar stores] FIG. 1 is a diagram showing a basic aspect of a brick-and-mortar electronic payment. Basically, electronic payment is performed by three parties: a medium M held by a user U, a store facility E, and a payment system S. The medium M is a portable computer device such as a smartphone, a credit card, etc. The store facility E is present in a physical brick-and-mortar store (hereinafter simply referred to as a store) that exists in real space, and is a POS device, a wireless communication device, a credit card reader, a printed matter of a code image such as a QR code (registered trademark), or a display device that displays a code image. In a brick-and-mortar electronic payment, first, information that can recognize the user's identification information and information on the payment amount are shared unidirectionally or bidirectionally between the medium M and the store facility E. At this time, one of the medium M or the store facility E optically reads various information from a code image displayed by the other, information is provided by NFC (Near Field Communication), or a PAN (Primary Account Number) is read by a credit card reader. Then, one of the medium M or the store facility E (the side that acquires information from the other) transmits payment information required for payment to the payment system S via the network NW. Both the medium M and the store equipment E may transmit some information to the payment system S. The payment system S manages various information of the user U and performs electronic payment between the store and the user U in various ways. Electronic payment is performed by one or both of a prepaid system and postpay, or by other methods. In addition, electronic payment may also include the so-called online shopping mode, which is performed by both the user's terminal device and the payment system. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc. Various devices that communicate via the network NW, which will be described later, are assumed to have communication devices such as network cards and wireless communication modules.

[0011] [Configuration (Terminal Payment)] 2 is a diagram showing an example of a configuration for performing electronic payment (terminal payment) using a payment app. This electronic payment is executed mainly by a payment app 20 that runs on a user terminal device 10 that is one of the media M, one or more store payment terminal devices 30 and one or more store code images 40 that are one of the store facilities E, a payment server 100 that constitutes a part of a payment system S, and the like. The payment server 100 communicates with the user terminal device 10, the store payment terminal device 30, and one or more information terminals 50 via a network NW.

[0012] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is, for example, installed in the user terminal device 10 from an application distribution server (not shown), and controls the camera, communication device, touch panel, etc. of the user terminal device 10.

[0013] The store payment terminal device 30 is installed, for example, in a store. The store payment terminal device 30 is a computer device (or a collection of these) having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The store payment terminal device 30 includes a so-called POS (Point of Sale) device, and the POS device may have a product price acquisition function and an optical reading function.

[0014] The store code image 40 is placed in a store and is a code image such as a QR code (registered trademark) printed on a medium such as paper or plastic. The store code image 40 may be displayed on a display placed in the store (or on a display of a terminal device such as a smartphone or tablet terminal).

[0015] The information terminal 50 is used by the operator of the affiliated store who manages the stores. In the electronic payment service, a customer who is a provider of goods or services is treated as an affiliated store (brand), and one or more stores exist under the affiliated store. An affiliated store that operates only one store may exist. The information terminal 50 is a smartphone, a tablet terminal, a personal computer, or the like. The information terminal 50 operates an interface 55 for affiliated stores. The interface 55 for affiliated stores may be an app for affiliated stores, or may be a web page displayed by a general-purpose browser. The interface 55 for affiliated stores accepts coupon settings and the like by the operator of the affiliated store and transmits them to the payment server 100. The information terminal 50 may have a function of displaying a code image equivalent to the store code image 40 or reading a code image displayed by the user terminal device 10 by executing the interface 55 for affiliated stores (in the latter case, an optical reading function is required).

[0016] The payment server 100 communicates with the credit card server 200 via a network NW. The payment server 100 has, for example, a content provider 110, an information manager 120, a payment processor 130, and a memory unit 170. The components other than the memory unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented using a large scale integration (LSI), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. The program may be realized by hardware (including circuitry) such as a Gate Array (GPU) or a Graphics Processing Unit (GPU), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device having a non-transient storage medium) such as a Hard Disk Drive (HDD) or a flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by mounting the storage medium in a drive device.

[0017] The storage unit 170 is a HDD, a flash memory, a RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172 and affiliated store / shop information 174.

[0018] The content providing unit 110 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The content providing unit 110 provides the content in the form of a web page to the user terminal device 10, and provides the parameters required for the payment application 20 to render an image to the user terminal device 10.

[0019] The information management unit 120 manages user information 172 and affiliated store / shop information 174 by editing, adding, deleting, etc.

[0020] 3 is a diagram showing an example of the contents of user information 172. User information 172 is information in which, for example, user URL, account ID, phone number, password, registration date, charge balance, electronic money type, terminal payment method, card payment method, various history information, identity verification flag, name, address, date of birth, email address, bank account, deferred payment settings, deferred payment condition information, etc. are associated with each other. Hereinafter, a user instance (electronic payment account) in which such information is associated may be referred to as an account. In the figure, items marked with "-" indicate that they are not set.

[0021] The user URL is used for the remittance process between users. When registering for the electronic payment service, it is necessary to register a phone number and a password. The account ID is issued to the user by the payment server 100. The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). The charge balance is information indicating the balance of electronic money that is set by the user remitting money to the account in advance. Remittance methods include depositing money into an ATM (Automatic Teller Machine) of a designated company (bank) and remittance from a registered bank account. The type of electronic money is information indicating, for example, whether the electronic money can be withdrawn or can only be used for electronic payment. The terminal payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or deferred payment in terminal payment. The card payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or deferred payment in card payment. The various historical information includes charge history, which is a history of when a user has previously transferred money to an electronic payment service to increase their charge balance, and payment history, which shows the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0022] The identity verification flag is information indicating whether or not the user has completed identity verification using an identification document. Deferred payment can be selected when identity verification has been completed, and since the user with the account ID "002" in the figure has not completed identity verification, the user can only select balance payment as the terminal payment method. The bank account is the account number of a bank account that can be used to deposit funds into the electronic payment service. Deferred payment settings is information indicating whether or not the setting operations for making deferred payment selectable have been completed. Deferred payment condition information is information indicating various conditions such as the limit on deferred payment and the amount used in the current month.

[0023] 4 is a diagram showing an example of the contents of affiliated store / store information 174. The affiliated store / store information 174 includes, for example, a first table 174A in which an affiliated store ID and a store ID are associated with a store URL, a second table 174B in which an affiliated store name and sales amount (described above) are associated with an affiliated store ID, and a third table 174C in which a store ID is associated with a store ID. In addition to this information, the affiliated store / store information 174 may also include information such as the category of the affiliated store or store, the location of the store, and payment patterns.

[0024] The payment processing unit 130 performs various processes for electronic payment. The payment processing unit 130 is an example of the "payment processing unit" in the claims. There are two methods for terminal payment: a first method (user scan) and a second method (store scan), which will be described below.

[0025] FIG. 5 is a diagram showing an outline of the process flow when a user scan is performed. First, the user terminal device 10 with the payment application 20 running reads and decodes the store code image 40 by using an optical reading function (S1). The store code image 40 includes store URL information. The payment application 20 transmits the first payment information including the store URL and the user's account ID to the payment server 100 (S2). The payment server 100 searches the affiliated store / store information 174 using the affiliated store ID and store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount to the payment application 20 on the screen displaying the affiliated store name and store name (S5). The payment application 20 then generates the second payment information including at least the payment amount, and transmits it to the payment server 100 (S6).

[0026] If the "Terminal Payment Method" in the user information 172 of the user is set to "Balance Payment", the payment processing unit 130 of the payment server 100 performs electronic payment based on the received second payment information (S7-1). At this time, the payment processing unit 130 performs electronic payment by, for example, decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, but an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service. On the other hand, if the "Terminal Payment Method" is set to "Postpaid", the payment processing unit 130 transmits the first payment information and the second payment information to the credit card server 200 to request electronic payment (S7-2). The credit card server 200 performs electronic payment by adding the payment amount to the monthly usage amount of the user based on the received information and deducting the monthly usage amount from the user's bank account after the closing date (S7-3).

[0027] Then, the payment processing unit 130 sends a payment completion notice (information for displaying a payment completion screen) to the payment application 20 via the content providing unit 110 (S8), and the payment application 20 displays the payment completion screen (S9). When the store code image 40 is displayed on a display placed in a store, the store code image 40 may include not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0028] FIG. 6 is a diagram showing an outline of the process flow when a store scan is performed. First, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (for example, every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment processing unit 130 of the payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the store payment terminal device 30, and the store payment terminal device 30 reads and decodes the code image by an optical reading function to obtain the one-time code, etc. (S15). Then, the store payment terminal device 30 generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a bar code or by manually entering the information.

[0029] The payment processing unit 130 of the payment server 100 identifies the user corresponding to the one-time code based on the received information, and if the "Terminal payment method" in the user information 172 of the user is set to "Balance payment", performs electronic payment based on the received second payment information (S17-1). The content of the process at this time is the same as the process of S7-1 in FIG. 5. On the other hand, if the "Terminal payment method" is set to "Deferred payment", the payment server 100 transmits the first payment information and the second payment information to the credit card server 200 to request electronic payment (S17-2). The credit card server 200 adds the payment amount to the user's monthly usage amount based on the received information, and performs electronic payment by deducting the monthly usage amount from the user's bank account after the closing date (S17-3).

[0030] Then, the payment processing unit 130 transmits a payment completion notification to the payment application 20 via the content providing unit 110 (S18), and the payment application 20 displays a payment completion screen (S19).

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

[0032] Note that the "deferred payment" settlement may be performed within the settlement server 100, rather than being managed by the credit card server 200. In this case, the components such as the settlement card 60 and the credit card server 200 may be omitted.

[0033] The authentication unit 140 authenticates whether a user who receives electronic payment services is a legitimate user, as will be described in detail later.

[0034] [Configuration (card payment)] 7 is a diagram showing an example of a configuration for performing electronic payment (card payment) using a payment card. This electronic payment is performed mainly with a payment card 60, which is one of the media M, a credit card processing terminal 70, which is one of the store facilities E, a payment server 100 and a credit card server 200, which constitute a part of a payment system S. The credit card server 200 communicates with the credit card processing terminal 70 via a network NW.

[0035] The credit processing terminal 70 is installed in the store, similar to the store payment terminal device 30. The credit processing terminal 70 includes, for example, a credit card payment terminal (credit card reader) and a POS device. The credit card payment terminal reads a PIN (Personal Identification Number) from an inserted or held credit card and collates it with the PIN entered by the user, or transmits a PAN (Primary Account Number) read from the credit card to the credit card server 200 via the POS device. The POS device cooperates with the credit card payment terminal to transmit information such as the payment amount to the credit card server 200. A payment agent server (acquirer) may be interposed between the credit card processing terminal 70 and the credit card server 200, but in the following, the description of the payment agent server will be omitted for the sake of simplicity. The payment card 60 is, for example, of the same type as a commonly used credit card, with a communication chip embedded in the card substrate. The communication chip has a built-in storage medium that stores the PIN, and communicates with an external device via a contactor (or a wireless antenna). Alternatively, the payment card 60 may be a magnetic card. The information (message) sent and received when using a credit card includes an authorization message for authentication and a sales message for conveying the payment amount, but detailed explanations distinguishing between these will be omitted below.

[0036] The credit card server 200 communicates with the payment server 100 via the network NW. The credit card server 200 has, for example, an information management unit 210, a credit interface 220, a payment allocation unit 230, a credit payment processing unit 240, and a storage unit 270. The components other than the storage unit 270 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by cooperation between software and hardware. The program may be stored in a storage device (storage device having a non-transient storage medium) such as an HDD or flash memory in advance, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and may be installed in the storage device by mounting the storage medium in a drive device. Information such as card user information 272 is stored in the storage unit 270.

[0037] The information management unit 210 manages the card user information 272 by editing, adding, deleting, etc. The card user information 272 is information in which, for example, information unique to a user (e.g., PAN), a card payment method, and the user's account ID (used by the payment server 100) are associated with each other. The card payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or deferred payment in card payment.

[0038] The credit interface 220 determines whether the BIN (Bank Identification Number) in the PAN included in the message received from the credit processing terminal 70 is a code for its own company, and if it is, passes the message received from the credit processing terminal 70 to the payment allocation unit 230, and if it is not a code for its own company, discards the received message.

[0039] The payment allocation unit 230 refers to the card user information 272 of the user corresponding to the message obtained from the credit interface 220, and judges whether the "card payment method" is set to "deferred payment". If the "card payment method" is set to "deferred payment", the payment allocation unit 230 notifies the credit interface 220 of that fact, and passes the message obtained from the credit interface 220 to the credit payment processing unit 240. On the other hand, if the "card payment method" is set to "balance payment", the payment allocation unit 230 adds the account ID of the user to the message obtained from the credit interface 220 and sends it to the payment server 100 to request electronic payment. The payment server 100 that has been requested to make electronic payment performs the same process as S7-1 in FIG. 5 and S17-1 in FIG. 6.

[0040] The credit interface 220 checks the PAN and expiration date, and checks whether the cumulative payment amount exceeds the upper limit for the current month, etc. The credit payment processing unit 240 adds the payment amount to the user's monthly usage amount based on the information contained in the message obtained from the payment allocation unit 230, and performs electronic payment by deducting the monthly usage amount from the user's bank account after the closing date.

[0041] [Prescribed action] The following describes the predetermined operation related to the electronic commerce service. The predetermined operation includes, for example, some or all of the following: account linkage, which reduces the authentication operation of the user related to the electronic payment for the subsequent electronic commerce compared to when the account is not linked; permission to log in to the electronic payment service; and online payment, which seamlessly permits electronic payment of the product or service purchased in the electronic commerce. FIG. 8 is a diagram showing an example of a configuration related to the predetermined operation. The electronic commerce server 300 communicates with the second terminal device 80 via the network NW and provides the user of the second terminal device 80 with an electronic commerce service. The electronic commerce service is referred to as online shopping, net auction, flea market, etc. Here, the user terminal device 10 corresponds to the "first terminal device" in the claims.

[0042] The second terminal device 80 is used by the same user as the user terminal device 10. The second terminal device 80 is a computer device such as a personal computer, a smartphone, or a tablet terminal. A UA 90 such as a browser or an application program runs on the second terminal device 80. The UA 90 displays an interface screen provided by an IF (interface) screen providing unit 310 of the electronic commerce server 300, and transmits to the electronic commerce server 300 the content of the user's operation performed on the interface screen.

[0043] The electronic commerce server 300 includes, for example, an IF screen providing unit 310, a payment linking unit 320, an EC payment processing unit 330, a product management unit 340, a seller management unit 350, and a shipping arrangement unit 360. These components are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device having a non-transient storage medium), or may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium), and installed in the storage device by mounting the storage medium in a drive device.

[0044] The IF screen providing unit 310 provides an interface screen to the second terminal device 80. The interface screen is, for example, a web page.

[0045] When a user of an electronic commerce service desires to make an electronic payment using an electronic payment service, the payment linking unit 320 requests the payment server 100 to make the electronic payment. This will be described in detail later.

[0046] The EC payment processing unit 330 processes payments for purchases made by users within the electronic commerce service, regardless of the electronic payment service. The EC payment processing unit 330 processes payments by credit card, bank transfer, carrier payment, etc. The product management unit 340 manages various information about products or services offered on the electronic commerce service. The seller management unit 350 manages various information about sellers who offer products on the electronic commerce service. The shipping arrangement unit 360 executes various processes to deliver products or services for which a transaction has been concluded to users.

[0047] (Prescribed actions 1 and 2: Account linking and login permission) The following describes account linking and login permission, which are among the predetermined operations. Account linking is a process that, when it is confirmed that the user of the electronic payment service and the user of the electronic commerce service are the same, reduces the authentication operation of the user related to the electronic payment for the subsequent electronic commerce compared to when the accounts are not linked. For example, when a user purchases a certain product in an electronic commerce transaction, if the user performs an operation of "pay with electronic payment service", the electronic payment is completed with, for example, a simple approval operation. In addition, the account linking enables services such as point sharing. Login permission is a process that allows a user who has already performed account linking to log in by performing an operation similar to account linking. Note that by performing account linking, the user is put into a logged-in state, and the logged-in state for electronic payment is maintained when using an electronic commerce service in that session.

[0048] In response to a call from an interface screen for electronic commerce provided by the IF screen providing unit 310 (for example, in response to a user operating a link for making a payment through an electronic payment service provided on the interface screen), the authentication unit 140 causes the second terminal device 80 to display a series of authentication images described below. This call is made by redirection, and information such as the user's login information, affiliated store ID, affiliated store logo, and redirect destination held by the electronic commerce server 300 is transmitted to the payment server 100 at any timing, enabling account linking and login.

[0049] FIG. 9 is a diagram showing an example of interface screens IM1 and IM2 that the authentication unit 140 causes the second terminal device 80 to display. First, the authentication unit 140 causes the second terminal device 80 to display the interface screen IM1 including the first code image CD1. The interface screen IM1 displays the name MC of the provider of the product or service related to the electronic commerce for which the user is attempting to link accounts (or is attempting to purchase by logging in to an electronic payment service). The interface screen IM1 is transitioned from, for example, an electronic commerce site provided by this provider. The interface screen IM1 is provided with areas A1 and A2. The area A1 displays the first code image CD1 generated by the authentication unit 140 (or generated parameters for generating the first code image CD1), and further displays the remaining time of the validity period T1 of the first code image CD1. The remaining time of the validity period T1 is controlled to decrease, for example, in predetermined time increments. The interface screen IM1 is also provided with an input area A2 that is used when the user wishes to manually log in. By inputting a phone number and a password in the input area A2, account linking is performed without using the first code image. The first code image CD1 is a one-time code image that is valid only once. The URL (redirect destination) of the second code image CD2 may be encoded in the first code image CD1. This may reduce communication between the payment application 20 and the payment server 100.

[0050] When the user holds the user terminal device 10 over the first code image CD1 with the scan function of the payment application 20 turned on, the payment application 20 transmits to the payment server 100 first information indicating that the payment application 20 has read the first code image CD1. The first information includes, for example, the user's account ID. Furthermore, the first information may include the terminal ID of the user terminal device 10, or may include information obtained by decoding the first code image CD1 or an extracted portion of the information obtained by decoding. Any other information may be used as long as it provides evidence that the first code image CD1 has been read.

[0051] When the first information is received, the authentication unit 140 of the payment server 100 judges whether the time of reception or the time stamp included in the received data is within the validity period T1 of the first code image CD1, and if it is within the validity period T1, causes the second terminal device 80 to display an interface screen IM2 including the second code image CD2. The interface screen IM2 is provided with areas A3 and A2. The second code image CD2 generated by the authentication unit 140 (or generated parameters for generating the second code image CD2) is displayed in the area A3, and further the remaining time of the validity period T2 of the second code image CD2 is displayed. The remaining time of the validity period T2 is controlled to decrease in predetermined time increments, for example. The second code image CD2 is also a one-time code image that is valid only once.

[0052] When the user holds the user terminal device 10 over the second code image CD2 with the scan function of the payment application 20 turned on, the payment application 20 transmits second information indicating that the payment application 20 has read the second code image CD2 to the payment server 100. The second information may be information obtained by decoding the second code image CD2, or may be a part of the information obtained by decoding, or may be any information that provides confirmation that the second code image CD2 has been read.

[0053] When the second information is received, the authentication unit 140 of the payment server 100 judges whether the time of reception or the timestamp included in the received data is within the validity period T2 of the second code image CD2, and if it is within the validity period T2, performs account linkage between the electronic commerce service and the electronic payment service (or permits login for a user who has already performed account linkage). Details will be described later.

[0054] Here, the reason for making the user scan the code image twice in this way will be described. If account linking is performed by scanning the code image once, the fraudulent use assumed in the present invention is that the fraudster himself logs in to the electronic commerce service and displays the code image as in FIG. 9, copies the code image by photographing or scanning the image, and sends it to a third party who is a user of the electronic payment service, and induces the third party to scan the code image using the payment application 20 by some fraudulent act. This may result in an illegal account linking or login, which may result in an inconvenience in which the price of the product or service purchased by the fraudster in the electronic commerce service is paid for by the third party's electronic payment account. In response to this, by making the user scan the code image twice, the fraudster is given the difficulty of having to copy two code images and send them to the third party within the validity period, and the third party is also required to perform the unnatural operation of unintentionally scanning the code image twice with the payment application 20, which increases the psychological hurdle. On the other hand, if account linking or login is performed only by the method shown in input area A2 in Fig. 9, the user often forgets the password (because it is stored in the user terminal device 10), and in such cases the user often gives up on account linking or login using the code image (and as a result, for example, logs in manually). This raises concerns about a loss of convenience. By having the user scan the code image twice as in the present invention, it is possible to maintain convenience while making fraudulent acts more difficult.

[0055] Here, the validity period T1 of the first code image CD1 is longer than the validity period T2 of the second code image CD2 in order to make the above-mentioned illegal acts, particularly the act of copying the second code image CD2 and sending it to a third party, more difficult.

[0056] 10 is a flowchart showing an example of a process flow related to account linking (and login permission). First, the payment server 100 receives a call for the interface screen IM1 and causes the second terminal device 80 to display the interface screen IM1 including the first code image CD1 (S21). The second terminal device 80 displays the interface screen IM1 including the first code image CD1 (S22). When the payment application 20 reads the first code image CD1, first information is transmitted from the payment application 20 to the payment server 100.

[0057] The payment server 100 receives the first information within the validity period T1 from the display of the first code image CD1 and judges whether the first information is correct (S23, S24). If a negative judgment result is obtained in either S23 or S24, that is, if the validity period T1 has elapsed without receiving the first information, or if the first information is incorrect, the payment server 100 causes the second terminal device 80 to display an error (S25). In response to this, the second terminal device 80 displays an error (S26). The error display may be performed by the payment application 20.

[0058] If the payment server 100 receives the first information within the validity period T1 from the display of the first code image CD1 and if the first information is correct, it causes the second terminal device 80 to display the interface screen IM2 including the second code image CD2 (S27). The second terminal device 80 displays the interface screen IM2 including the second code image CD2 (S28). If the payment application 20 reads the second code image CD2, the payment application 20 transmits the second information to the payment server 100.

[0059] The payment server 100 receives the second information within the validity period T2 from the display of the second code image CD2 and judges whether the second information is correct (S29, S30). When judging whether the second information is correct, the payment server 100 confirms that at least the user's account ID is the same in the first information and the second information. The payment server 100 may also confirm that the terminal ID is the same in the first information and the second information. If a negative judgment result is obtained in either S29 or S30, that is, if the validity period T2 has elapsed without receiving the second information, or if the second information is incorrect, the payment server 100 causes the second terminal device 80 to display an error (S31). In response to this, the second terminal device 80 displays an error (S32). This error display may also be performed by the payment application 20.

[0060] If the payment server 100 receives the second information within the validity period T2 from the display of the second code image CD2 and if the second information is correct, it performs account linking (S33). For a user who has already performed account linking, the process of S33 is interpreted as "permitting login." When account linking is performed, the payment server 100 and the payment application 20 confirm the details of the account linking as described below. FIG. 11 is a diagram showing an example of an application screen IA1 for confirming account linking. In the application screen IA1, information to be provided to the e-commerce service by the account linking is listed, and a button B1 is provided for receiving an operation indicating that the user agrees to the information.

[0061] In addition, the payment server 100 may measure the average value or standard deviation of the elapsed time from the time of receiving the first information to the time of receiving the second information, and may generate an internal warning process when the elapsed time for a certain user is significantly different from the average value (for example, when it is different by 2σ or more). In this case, the user may add a confirmation operation to confirm the certainty that the operation is performed by the same user. FIG. 12 is a diagram showing an example of an application screen IA2 for additional confirmation. The application screen IA2 may be displayed before the application screen IA2 in FIG. 11, or may be displayed instead of the application screen IA2 in FIG. 11. In the application screen IA2, a message is displayed to alert the user that the account linking is in progress, and a button B2 is provided for accepting an operation of the user agreeing to proceed to the next step. The same applies to the predetermined operation 4-6.

[0062] According to the above-described process of account linking or login permission, it is possible to make fraudulent acts more difficult while maintaining convenience.

[0063] (Prescribed action 3: Online payment) The following describes online payment, which is one of the predetermined operations. The account linking described above is performed independently of electronic payment, but online payment is performed for electronic payment when the product or service the user wants to purchase is decided. Account linking may also be performed in conjunction with online payment. The names of the first code image CD1 and the second code image CD2 are the same as those in the case of account linking.

[0064] In the case of online payment, the authentication unit 140 also displays a series of interface screens, described below, on the second terminal device 80 in response to a call from an interface screen for electronic commerce provided by the IF screen providing unit 310 (for example, in response to the user operating a link for making a payment through an electronic payment service, which is provided on the interface screen). This call is made by redirection, and information on the product or service designated by the user (which may include the affiliated store name, payment amount, etc.) is transmitted to the payment server 100 at any timing, enabling online payment.

[0065] FIG. 13 is a diagram showing an example of interface screens IM3 and IM4 that the authentication unit 140 causes the second terminal device 80 to display in online payment. Each of the interface screens IM3 and IM4 is a web page that is displayed over the entire browser screen. First, the authentication unit 140 causes the second terminal device 80 to display the interface screen IM3 including the first code image CD1. The interface screen IM3 displays the name of the provider MC of the product or service purchased by the user in electronic payment. The interface screen IM3 also includes an area A1 including the same content as in FIG. 9, and an area A4 displaying the payment amount and product name (service name) of the product or service purchased by the user. The interface screen IM3 is displayed as a screen provided by the payment server 100 when the product or service to be purchased is confirmed on an electronic commerce site that provides an electronic commerce service, and the user selects to pay with the electronic payment service. The first code image CD1 is a one-time code image that is valid only once.

[0066] When the user holds the user terminal device 10 over the first code image CD1 with the scan function of the payment application 20 turned on, the payment application 20 transmits to the payment server 100 first information indicating that the payment application 20 has read the first code image CD1. The contents of the first and second information may be the same as those of the predetermined actions 1 and 2.

[0067] When the first information is received, the authentication unit 140 of the payment server 100 judges whether the time of reception or the time stamp included in the received data is within the validity period T1 of the first code image CD1, and if it is within the validity period T1, causes the second terminal device 80 to display an interface screen IM4 including the second code image CD2. The interface screen IM2 has areas A4 and A3. The second code image CD2 generated by the authentication unit 140 (or generated parameters for generating the second code image CD2) is displayed in the area A3, and further the remaining time of the validity period T2 of the second code image CD2 is displayed. The remaining time of the validity period T2 is controlled to decrease in predetermined time increments, for example. The second code image CD2 is also a one-time code image that is valid only once.

[0068] When a user holds the user terminal device 10 over the second code image CD2 with the scanning function of the payment application 20 turned on, the payment application 20 transmits second information to the payment server 100 indicating that the payment application 20 has read the second code image CD2.

[0069] Upon receiving the second information, the authentication unit 140 of the payment server 100 judges whether the time of reception or the timestamp included in the received data is within the validity period T2 of the second code image CD2, and permits the electronic payment if it is within the validity period T2. As a result, the electronic payment by the payment processing unit 130 proceeds. The payment processing unit 130 performs the electronic payment by the various methods described above (balance payment, deferred payment, etc.). At this time, the authentication unit 140 may also implement account linking.

[0070] The reason for scanning the code image twice in online payment is the same as in the case of account linking. Also, the validity period T1 of the first code image CD1 is longer than the validity period T2 of the second code image CD2.

[0071] Regarding the online payment flowchart, the same explanation will be omitted since it is applicable if the interface screens IM1 and IM2 in the flowchart in Figure 10 are replaced with interface screens IM3 and IM4, respectively, and "Perform account linking" in S33 is replaced with "Allow electronic payment" or "Allow electronic payment and perform account linking."

[0072] The online payment process described above makes it possible to make fraudulent acts more difficult while maintaining convenience.

[0073] (Prescribed action 4-6: Account linking by providing embedded image / Login permission / Online payment) The provision of embedded images will be described below. In the predetermined operation 1-3, the interface image displayed on the second terminal device 80 is mainly provided by the payment server 100. In contrast, in the predetermined operation 4-6, the first code image CD1 and the second code image CD2 provided by the payment server 100 are embedded in the interface screen (web page) provided by the electronic commerce server 300 by a method such as redirection.

[0074] FIG. 14 is a diagram showing an example of interface screens IM5 and IM6 that the IF screen providing unit 310 of the electronic commerce server 300 causes the second terminal device 80 to display. First, the IF screen providing unit 310 causes the second terminal device 80 to display the interface screen IM5 including the first code image CD1. The interface screen IM5 displays the name MC of the provider of the product or service that the user is about to purchase. The interface screen IM5 is an extension of the electronic commerce site provided by the electronic commerce service, and is displayed when the product or service to be purchased at the electronic commerce site is confirmed and the user selects to pay with the electronic payment service. The interface screen IM5 is provided with areas A5 and A6. The area A5 displays a description of the product or service to be purchased at the electronic commerce site. The area A6 displays the first code image CD1 provided by the payment server 100 as an embedded image, and the remaining time of the validity period T1 of the first code image CD1. The remaining time of the validity period T1 is controlled to decrease, for example, at predetermined time intervals. The first code image CD1 is a one-time code image that is valid only once.

[0075] When the user holds the user terminal device 10 over the first code image CD1 with the scan function of the payment application 20 turned on, the payment application 20 transmits the first information indicating that the payment application 20 has read the first code image CD1 to the payment server 100. The contents of the first information and the second information may be the same as those in the case of the predetermined action 1-3.

[0076] When the first information is acquired, the authentication unit 140 of the payment server 100 judges whether the time of reception or the time stamp included in the received data is within the validity period T1 of the first code image CD1, and if it is within the validity period T1, transmits the second code image CD2 and the remaining time of the validity period T2 of the second code image CD2 as an embedded image to the second terminal device 80. The embedded image is reflected in the interface screen IM6. The interface screen IM6 is provided with areas A5 and A7. The second code image CD2 provided by the payment server 100 as an embedded image and the remaining time of the validity period T2 of the second code image CD2 are displayed in the area A7. The remaining time of the validity period T2 is controlled to decrease, for example, in predetermined time increments. The second code image CD2 is also a one-time code image that is valid only once.

[0077] When the user holds the user terminal device 10 over the second code image CD2 with the scan function of the payment application 20 turned on, the payment application 20 transmits to the payment server 100 second information indicating that the payment application 20 has read the second code image CD2. In response to this, the payment server 100 performs account linkage / permits login / and / or permits electronic payment for the product or service purchased by the user. If electronic payment is permitted, the payment processing unit 130 of the payment server 100 performs electronic payment by the various methods described above (balance payment, deferred payment, etc.). Details will be described later.

[0078] In the predetermined operation 4-6, the reason for scanning the code image twice is the same as in the case of account linking. Also, the validity period T1 of the first code image CD1 is longer than the validity period T2 of the second code image CD2.

[0079] Fig. 15 is a flow chart showing an example of the process flow related to the predetermined operation 4-6. First, the payment server 100 receives a call of the first code image CD1 from the interface screen IM5 and provides the first code image CD1 to the second terminal device 80 (S41). The second terminal device 80 displays the interface screen IM5 in which the first code image CD1 is embedded (S42). When the payment application 20 reads the first code image CD1, the first information is transmitted from the payment application 20 to the payment server 100.

[0080] The payment server 100 receives the first information within the validity period T1 from the display of the first code image CD1 and judges whether the first information is correct (S43, S44). If a negative judgment result is obtained in either S43 or S44, that is, if the validity period T1 has elapsed without receiving the first information, or if the first information is incorrect, the payment server 100 causes the second terminal device 80 to display an error (S45). In response to this, the second terminal device 80 displays an error (S46). The error display may be performed by the payment application 20.

[0081] If the payment server 100 receives the first information within the validity period T1 from the display of the first code image CD1 and if the first information is correct, it provides the second code image CD2 to the second terminal device 80 (S47). The second terminal device 80 displays the interface screen IM6 in which the second code image CD2 is embedded (S48). If the payment application 20 reads the second code image CD2, the second information is transmitted from the payment application 20 to the payment server 100.

[0082] The payment server 100 receives the second information within the validity period T2 from the display of the second code image CD2 and judges whether the second information is correct (S49, S50). When judging whether the second information is correct, the payment server 100 confirms that at least the user's account ID is the same in the first information and the second information. The payment server 100 may also confirm that the terminal ID is the same in the first information and the second information. If a negative judgment result is obtained in either S49 or S50, that is, if the validity period T2 has elapsed without receiving the second information, or if the second information is incorrect, the payment server 100 causes the second terminal device 80 to display an error (S51). In response to this, the second terminal device 80 displays an error (S52). This error display may also be performed by the payment application 20.

[0083] If the payment server 100 receives the second information within the validity period T2 from the display of the second code image CD2 and if the second information is correct, it performs account linking, grants login permission, and / or permits electronic payment (S53).

[0084] According to the embodiment described above, it is possible to make fraudulent acts more difficult while maintaining convenience.

[0085] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0086] E. Store Facilities M medium S Payment System 10 User terminal device 20. Payment App 30 Store payment terminal device 40 Store code image 60 Payment Cards 70 Credit card processing terminal 100 Payment Server 130 Payment processing unit 140 Authentication Section 200 Credit Card Server 300 E-commerce Server 310 IF screen provision department 320 Payment Cooperation Department

Claims

1. A payment server that provides electronic payment services in cooperation with a payment app, a payment processing unit that performs electronic payment based on payment information obtained by communication with the payment application operating on a terminal device including a first terminal device, and performs electronic payment in response to a request from an electronic commerce service that is a service different from the electronic payment; displaying a first code image on a second terminal device in response to a call from an interface screen of the electronic commerce service displayed on the second terminal device; When first information indicating that the payment application has read the first code image is received from the payment application, a second code image is displayed on the second terminal device; an authentication unit that, when second information indicating that the payment application has read the second code image is received from the payment application, authorizes an electronic payment using the electronic payment service in the electronic commerce service by a user who uses the first terminal device and the second terminal device; A payment server comprising:

2. A payment server that provides an electronic payment service in cooperation with a payment app, a payment processing unit that performs electronic payment based on payment information obtained by communication with the payment application operating on a terminal device including a first terminal device, and performs electronic payment in response to a request from an electronic commerce service that is a service different from the electronic payment; displaying a first code image on a second terminal device in response to a call from an interface screen of the electronic commerce service displayed on the second terminal device; When first information indicating that the payment application has read the first code image is received from the payment application, a second code image is displayed on the second terminal device; performing account linking when second information indicating that the payment application has read the second code image is received from the payment application; an authentication unit that allows a user who has already linked their accounts to log in to the electronic payment service when second information indicating that the payment application has read the second code image is received from the payment application; A payment server comprising:

3. A payment server that provides an electronic payment service in cooperation with a payment app, a payment processing unit that performs electronic payment based on payment information obtained by communication with the payment application operating on a terminal device including a first terminal device, and performs electronic payment in response to a request from an electronic commerce service that is a service different from the electronic payment; displaying a first code image on a second terminal device in response to a call from an interface screen of the electronic commerce service displayed on the second terminal device; When first information indicating that the payment application has read the first code image is received from the payment application, a second code image is displayed on the second terminal device; an authentication unit that performs an operation of permitting a user who uses the first terminal device and the second terminal device to log in to the electronic commerce service when second information indicating that the payment application has read the second code image is received from the payment application; A payment server comprising:

4. The authentication unit When the first information is received from the payment application within a first validity period after the first code image is displayed, the second code image is displayed on the second terminal device; permitting an electronic payment using the electronic payment service in the electronic commerce service by a user of the first terminal device and the second terminal device when the second information is received from the payment application within a second validity period after the second code image is displayed; The payment server according to claim 1.

5. The first validity period is longer than the second validity period; The payment server according to claim 4.

6. The authentication unit When the first information is not received from the payment application within the first validity period after the first code image is displayed, and when the second information is not received from the payment application within the second validity period after the second code image is displayed, an error is displayed on the second terminal device. The payment server according to claim 4 or 5.

7. each of the first information and the second information includes identification information of a user of the electronic payment service; when the authentication unit confirms that the identification information is the same between the first information and the second information, the authentication unit permits electronic payment using the electronic payment service in the electronic commerce service by the user who uses the first terminal device and the second terminal device. The payment server according to claim 1.

8. The authentication unit Displaying a web page including the first code image on the second terminal device; Then, a web page including the second code image is displayed on the second terminal device. The payment server according to claim 1.

9. the authentication unit transmits each of the first code image and the second code image to the second terminal device as an image to be embedded in an interface screen of the electronic commerce service; The payment server according to any one of claims 1 to 3.

10. A payment server that provides an electronic payment service in cooperation with a payment app, performing electronic payment based on payment information obtained by communication with the payment application running on a terminal device including a first terminal device; making an electronic payment in response to a request from an electronic commerce service which is a service different from the electronic payment; displaying a first code image on a second terminal device in response to a call from an interface screen of the electronic commerce service displayed on the second terminal device; When first information indicating that the payment application has read the first code image is received from the payment application, a second code image is displayed on the second terminal device; when second information indicating that the payment application has read the second code image is received from the payment application, permitting electronic payment using the electronic payment service in the electronic commerce service by a user who uses the first terminal device and the second terminal device; method.

11. A payment server computer that provides an electronic payment service in cooperation with a payment app, A process of making an electronic payment based on payment information obtained by communication with the payment application operating on a terminal device including a first terminal device; A process of making an electronic payment in response to a request from an electronic commerce service which is a service different from the electronic payment; a process of displaying a first code image on a second terminal device in response to a call from an interface screen of the electronic commerce service displayed on the second terminal device; When first information indicating that the payment application has read the first code image is received from the payment application, a process of displaying a second code image on the second terminal device; a process of permitting an electronic payment using the electronic payment service in the electronic commerce service by a user of the first terminal device and the second terminal device when second information indicating that the payment application has read the second code image is received from the payment application; A program for executing the above.

Images