Settlement server, method, and program

Abstract

To make a fraudulent act more difficult while maintaining convenience.SOLUTION: A settlement processing unit configured to perform an electronic settlement based on settlement information obtained by communication with a settlement application operating on a first terminal; a first code image is displayed on a second terminal in response to a call from an interface screen of an electronic transaction; Display a second code image on the second terminal when first information indicating that the settlement application has read the first code image is received from the settlement application, and perform a predetermined operation related to the e-commerce transaction when second information indicating that the settlement application has read the second code image is received from the settlement application.SELECTED DRAWING: Figure 8

Description

[Technical Field]

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

[0002] Previously, attempts have been made to smoothly facilitate electronic payments by linking the services of businesses that primarily provide electronic payment services with e-commerce transactions. For example, when a business sells a product on its website, if the business's login information is associated with the login information of the electronic payment service (account linking), electronic payments can be easily made using the balance of the electronic payment service. In this regard, Patent Document 1 describes that when an electronic payment service is called from the e-commerce side, an API provides the functions of the electronic payment service without authentication, based on whether or not the user has consented. [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, attempts have been made to simplify authentication by displaying a code image for account linking on an e-commerce website 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 activities in which fraudsters photograph or capture the code image and send it to another person's terminal device, and then use fraudulent activities such as spam or phishing to trick the other person into loading the code image into the payment app, thereby causing the fraudster to make electronic payments for products purchased through e-commerce. Conventional technologies have sometimes failed to provide 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 acts 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 of an e-commerce transaction, 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 transaction when second information indicating that the payment app has read the second code image is received from the payment app. [Effects 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 explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates basic aspects of brick-and-mortar electronic payment. [Figure 2] FIG. 1 is a diagram illustrating an example of a configuration for performing electronic payment (terminal payment) using a payment application. [Figure 3] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 4] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 174. [Figure 5] FIG. 10 is a diagram showing an outline of a processing flow when a user scan is performed. [Figure 6] FIG. 10 is a diagram showing an outline of the processing 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. 10 is a diagram illustrating an example of a configuration related to a predetermined operation. [Figure 9] 10A and 10B 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] 10 is a flowchart showing an example of a processing flow related to account linkage (and login permission). [Figure 11] FIG. 10 is a diagram showing an example of an app screen IA1 for confirming account linkage. [Figure 12] FIG. 10 is a diagram showing an example of an application screen IA2 for additional confirmation. [Figure 13] 10A and 10B 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] 10A and 10B 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] 10 is a flowchart showing an example of a processing flow relating to a predetermined operation 4-6. DETAILED DESCRIPTION OF THE INVENTION

[0009] [overview] Hereinafter, with reference to the drawings, embodiments of a payment server, method, and program according to the present invention will be described. In the following description, an electronic payment service and an e-commerce service will be mentioned. These services are provided by separate mechanisms (they may be provided by different or the same business operators). 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 app. The combination of the payment server and the credit card server may also be referred to as a payment management system. An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store may be, for example, a physical store (real-world store) existing in real space, but may also include a virtual e-commerce store. A virtual store may also include a store provided by an entity (e-commerce service provider) different from the operator of the electronic payment service. In such a case, when making a payment for a purchase at the virtual store, the user is controlled to transition to the interface screen of the electronic payment service. In an 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 primarily conducted 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 illustrates the basic aspects of brick-and-mortar electronic payments. Electronic payments are generally carried out by three parties: a medium M held by a user U, store equipment E, and a payment system S. The medium M may be a portable computer device such as a smartphone or a credit card. The store equipment E resides in a physical store (hereinafter simply referred to as the store) in real space and may include a POS device, a wireless communication device, a credit card reader, a printed code image such as a QR Code (registered trademark), or a display device displaying the code image. In brick-and-mortar electronic payments, information that can identify the user and information about the payment amount are first shared unidirectionally or bidirectionally between the medium M and the store equipment E. At this time, either the medium M or the store equipment E optically reads various information from a code image displayed by the other, provides information via near-field communication (NFC), or reads the PAN (primary account number) using a credit card reader. Then, either the medium M or the store equipment E (the party that obtains information from the other) transmits the payment information required for the payment to the payment system S via a network NW. Both the medium M and the store equipment E may send some information to the payment system S. The payment system S manages various information about the user U and performs electronic payments between the store and the user U in various ways. Electronic payments are performed using either or both of a prepaid system and a postpaid system, or by other methods. In addition, electronic payments may also include so-called online shopping, which is performed between 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. The various devices that communicate via the network NW, which will be described below, 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 the configuration for performing electronic payment (terminal payment) using a payment app. This electronic payment is performed mainly by a payment app 20 running on a user terminal device 10, which is one of the media M, one or more store payment terminal devices 30 and one or more store code images 40, which are one of the store facilities E, and a payment server 100, which constitutes part of a payment system S. 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 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, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment application 20 is installed in the user terminal device 10 from, for example, an application distribution server (not shown), and controls the camera, communication device, touch panel, etc. of the user terminal device 10.

[0013] Store payment terminal device 30 is installed, for example, in a store. Store payment terminal device 30 is a computer device (or a collection of these) that has at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. 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 paper or plastic medium. 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 oversees the stores. In electronic payment services, customers who provide goods or services are treated as affiliated stores (brands), and one or more stores exist under the affiliated store. An affiliated store may operate only one store. The information terminal 50 is a smartphone, tablet terminal, personal computer, etc. An affiliated store interface 55 runs on the information terminal 50. The affiliated store interface 55 may be an affiliated store app or a web page displayed by a general-purpose browser. The affiliated store interface 55 accepts coupon settings and the like from the affiliated store operator and transmits them to the payment server 100. By executing the affiliated store interface 55, the information terminal 50 may have the function of displaying a code image corresponding to the store code image 40 or reading a code image displayed by the user terminal device 10 (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 management unit 120, a payment processing unit 130, and a storage unit 170. The components other than the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components 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 with a non-transitory storage medium) such as a hard disk drive (HDD) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0017] The storage unit 170 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that can be accessed by the payment server 100 via a network. The storage unit 170 stores information such as user information 172 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 to the user terminal device 10 in the form of a web page, and provides the user terminal device 10 with parameters required for the payment application 20 to render an image.

[0019] The information management unit 120 edits, adds, deletes, etc., user information 172 and affiliated store / shop information 174, and manages them.

[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 this 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 remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. 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 the user has set by transferring money to the account in advance. Remittance methods include depositing money into an ATM (Automatic Teller Machine) of a designated service provider (bank) or transferring money 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 payments. The terminal payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or by 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 by deferred payment in card payment. The various historical information includes charge history, which is a record of the user transferring money to the electronic payment service in advance to increase the charge balance, and payment history, which shows the details of the 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 ID document. Deferred payment can be selected if identity verification has been completed, and the user with account ID "002" in the figure has not completed identity verification and 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 settings have been completed to make deferred payment selectable. Deferred payment condition information is information indicating various conditions such as the deferred payment limit and the amount used for 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 ID is associated with an affiliated store name and sales amount (described above), 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 store's location, and payment patterns.

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

[0025] FIG. 5 shows an overview 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 using its optical reading function (S1). The store code image 40 contains store URL information. The payment application 20 sends 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 information about the affiliated store name and store name (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the payment application 20 on the screen displaying the affiliated store name and store name (S5). The payment application 20 then generates second payment information including at least the payment amount and sends 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 proceeds. The item value of the affiliated store's sales proceeds is not used as electronic money itself, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle determined by an agreement between the affiliated store and the electronic payment service. On the other hand, if the "Terminal Payment Method" is set to "Deferred Payment," 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 user's monthly usage amount 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 app 20 via the content providing unit 110 (S8), and the payment app 20 displays the payment completion screen (S9). When the store code image 40 is displayed on a display installed in the store, the store code image 40 may include information on the payment amount in addition to the store URL. In this case, the procedure for the user to input 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 overview of the processing flow when a store scan is performed. First, when the payment app 20 is launched, when a payment operation is performed using the payment app 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment app 20 sends a request to issue 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 sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or 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 using its optical reading function to obtain the one-time code, etc. (S15). The store payment terminal device 30 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it.

[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," it performs electronic payment based on the received second payment information (S17-1). The processing content at this time is the same as the processing of S7-1 in FIG. 5. On the other hand, if the "terminal payment method" is set to "post-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, issuing a one-time code may be omitted in store scanning, 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] It should be noted that the "post-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 receiving 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 using 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, which constitutes part of a payment system S, and a credit card server 200. 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 reader and a POS device. The credit card terminal reads a personal identification number (PIN) from an inserted or held-up credit card and compares it with the PIN entered by the user. It also transmits a primary account number (PAN) read from the credit card to the credit card server 200 via the POS device. The POS device cooperates with the credit card terminal to transmit information such as the payment amount to the credit card server 200. A payment agent (acquirer) server may be interposed between the credit processing terminal 70 and the credit card server 200; however, for simplicity, the following description omits the explanation of the payment agent server. The payment card 60 is, for example, similar to a commonly used credit card, with a communication chip embedded in the card substrate. The communication chip incorporates a storage medium storing 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 (messages) sent and received when using a credit card include 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 a network NW. The credit card server 200 includes, for example, an information management unit 210, a credit interface 220, a payment allocation unit 230, a credit payment processing unit 240, and a memory unit 270. The components other than the memory unit 270 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be implemented 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 with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device. The memory unit 270 stores information such as card user information 272.

[0037] The information management unit 210 edits, adds, deletes, etc., and manages the card user information 272. 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 one another. The card payment method is setting information that indicates whether the user will make electronic payment using the charged balance (balance payment) or deferred payment when making a 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 the company, and if it is a code for the company, passes the message received from the credit processing terminal 70 to the payment allocation unit 230, and if it is not a code for the company, discards the received message.

[0039] The payment allocating unit 230 refers to the card user information 272 of the user corresponding to the message obtained from the credit interface 220, and determines whether the "card payment method" is set to "post-payment." If the "card payment method" is set to "post-payment," the payment allocating unit 230 notifies the credit interface 220 of this 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 allocating unit 230 adds the user's account ID to the message obtained from the credit interface 220 and sends it to the payment server 100, requesting electronic payment. When requested to make electronic payment, the payment server 100 performs the same processes as S7-1 in Figure 5 and S17-1 in Figure 6.

[0040] The credit interface 220 checks the PAN and expiration date, and verifies whether the cumulative payment amount exceeds the current month's upper limit, 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 predetermined operations related to e-commerce services. The predetermined operations include, for example, some or all of account linking, which reduces the user's authentication operations for subsequent electronic payments for the e-commerce compared to when accounts are not linked; permission to log in to the electronic payment service; and online payment, which seamlessly permits electronic payments for goods or services purchased in the e-commerce transaction. Figure 8 shows an example of a configuration related to the predetermined operations. The e-commerce server 300 communicates with a second terminal device 80 via a network NW and provides e-commerce services to users of the second terminal device 80. Examples of e-commerce services include online shopping, online auctions, and flea markets. 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 e-commerce server 300, and transmits to the e-commerce server 300 the content of the user's operations performed on the interface screen.

[0043] The e-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 with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into 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 user purchases within the e-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 e-commerce service. The seller management unit 350 manages various information about sellers who offer products on the e-commerce service. The shipping arrangement unit 360 performs various processes to deliver the products or services for which a transaction has been concluded to the user.

[0047] (Predetermined 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 e-commerce service are the same, reduces the user's authentication operations related to electronic payments for subsequent e-commerce transactions compared to when accounts are not linked. For example, when a user purchases a product in an e-commerce transaction, if the user selects "pay with electronic payment service," the electronic payment is completed with, for example, a simple approval operation. Account linking also enables services such as point sharing. Login permission is a process that allows a user whose accounts have already been linked to log in by performing operations similar to account linking. Note that account linking places the user in a logged-in state, and the logged-in state for electronic payment remains when using e-commerce services 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 using 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, which will be described below. This call is made by redirection, and information held by the electronic commerce server 300, such as the user's login information, affiliated store ID, affiliated store logo, and redirect destination, is transmitted to the payment server 100 at any timing, enabling account linking and login.

[0049] FIG. 9 shows examples 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 e-commerce transaction for which the user is attempting to link their accounts (or for which they are attempting to purchase by logging in to an electronic payment service). The interface screen IM1 is transitioned from, for example, an e-commerce site provided by this provider. The interface screen IM1 has 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 also has an input area A2 that is used when the user wishes to log in manually. By entering a phone number and password in 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 confirmation 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 determines whether the time of reception or the timestamp 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 has 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 area A3, and further displays the remaining time of the validity period T2 of the second code image CD2. 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.

[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 portion of the information obtained by decoding, or may be any information that can provide 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 determines 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, it links the accounts of the electronic commerce service and the electronic payment service (or allows a user who has already linked their accounts to log in). Details will be described later.

[0054] Here, we explain why the user is required to scan the code image twice. If account linking is achieved by scanning the code image once, the fraudulent use envisioned by the present invention involves a fraudulent person logging in to an e-commerce site and displaying a code image as shown in FIG. 9 , copying the code image by photographing or scanning it, sending it to a third party who is a user of the electronic payment service, and then, through some other fraudulent act, tricking the third party into scanning the code image using the payment app 20. This could result in unauthorized account linking or login, which could result in the payment of the goods or services purchased by the fraudulent person through the e-commerce site being paid for using the third party's electronic payment account. By requiring the user to scan the code image twice, the fraudster faces the difficulty of having to copy two code images and send them to the third party within the validity period. This also raises a psychological hurdle for the third party by requiring them to unintentionally perform the unnatural operation of scanning the code image twice with the payment app 20. On the other hand, if account linking or login is performed only using the method shown in input area A2 in Figure 9, the user often forgets their password (because it is stored in the user terminal device 10), and in such cases, the user often gives up on account linking or logging in using the code image (and as a result, for example, logs in manually). Therefore, there is a concern that convenience will be lost. By requiring the user to 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 fraudulent acts, in particular 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 the process flow for 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 sent 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 determines whether the first information is correct (S23, S24). If a negative determination result is obtained in either S23 or S24, that is, if the validity period T1 has elapsed without the first information being received, 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). Note that 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 the first information is correct, it causes the second terminal device 80 to display an 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 determines whether the second information is correct (S29, S30). When determining 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 determination result is obtained in either S29 or S30, i.e., if the validity period T2 has elapsed without the second information being received, 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 app 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 linked their accounts, the process of S33 can be interpreted as "permitting login." When account linking is performed, the payment server 100 and payment application 20 confirm the details of the account linking, as described below. Figure 11 is a diagram showing an example of an application screen IA1 for confirming account linking. The application screen IA1 lists information to be provided to the e-commerce service through account linking, and provides a button B1 that accepts an operation by the user to indicate consent to the information.

[0061] Furthermore, the payment server 100 may measure the average value and standard deviation of the elapsed time from the time the first information is received to the time the second information is received, and may generate an internal warning process if the elapsed time for a certain user significantly deviates from the average value (for example, if it deviates by 2σ or more). In this case, the user may perform an additional confirmation operation to confirm the reliability of the operation being 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 of FIG. 11 or may be displayed instead of the application screen IA2 of FIG. 11. The application screen IA2 displays a message alerting the user that account linking is in progress, and includes a button B2 for accepting the user's consent to proceed. The same applies to predetermined operations 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] (Predetermined 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 user decides on the product or service to purchase. 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 used 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 paying using an electronic payment service, which is provided on the interface screen). This call is made by redirection, and information on the product or service specified by the user (which may include the name of the affiliated store, the payment amount, etc.) is transmitted to the payment server 100 at any timing, enabling online payment.

[0065] FIG. 13 shows examples of interface screens IM3 and IM4 that the authentication unit 140 displays on the second terminal device 80 during online payment. Each of the interface screens IM3 and IM4 is a web page that is displayed across the entire browser screen. First, the authentication unit 140 displays the interface screen IM3, including a first code image CD1, on the second terminal device 80. The interface screen IM3 displays the name MC of the provider of the product or service purchased by the user through electronic payment. The interface screen IM3 also includes an area A1 containing the same content as that shown 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 e-commerce site providing an e-commerce service and the user selects to pay using 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 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 cases of the predetermined actions 1 and 2.

[0067] When the first information is received, the authentication unit 140 of the payment server 100 determines whether the time of reception or the timestamp 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 area A3, and the remaining time of the validity period T2 of the second code image CD2 is also displayed. 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.

[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 indicating that the payment application 20 has read the second code image CD2 to the payment server 100.

[0069] Upon receiving the second information, the authentication unit 140 of the payment server 100 determines 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, authorizes the electronic payment. 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 payments is the same as in 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 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 activities more difficult while maintaining convenience.

[0073] (Prescribed action 4-6: Account linking / Login permission / Online payment by providing embedded image) The provision of embedded images will be explained below. In 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 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 e-commerce server 300 by a method such as redirection.

[0074] FIG. 14 shows examples of interface screens IM5 and IM6 that the IF screen providing unit 310 of the e-commerce server 300 causes the second terminal device 80 to display the interface screen IM5, which includes the first code image CD1. The interface screen IM5 displays the name MC of the provider of the product or service the user is attempting to purchase. The interface screen IM5 is an extension of the e-commerce site provided by the e-commerce service, and is displayed when the product or service to be purchased on the e-commerce site is confirmed and the user selects to pay using the electronic payment service. The interface screen IM5 includes areas A5 and A6. Area A5 displays a description of the product or service to be purchased on the e-commerce site. 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, in predetermined time increments. 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 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 determines whether the time of reception or the timestamp 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. This embedded image is reflected in the interface screen IM6. The interface screen IM6 has areas A5 and A7. Area A7 displays 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. 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 scanning function of the payment application 20 turned on, the payment application 20 sends second information to the payment server 100 indicating that the payment application 20 has read the second code image CD2. In response, the payment server 100 performs account linking, grants login permission, and / or authorizes electronic payment for the product or service purchased by the user. If electronic payment is authorized, the payment processing unit 130 of the payment server 100 performs electronic payment using the various methods described above (balance payment, deferred payment, etc.). Details will be described later.

[0078] The reason for scanning the code image twice in the predetermined operation 4-6 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] 15 is a flowchart showing an example of the processing flow related to predetermined operation 4-6. First, the payment server 100 receives a call for 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, 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 determines whether the first information is correct (S43, S44). If a negative determination result is obtained in either S43 or S44, that is, if the validity period T1 has elapsed without the first information being received, 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). Note that 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 an interface screen IM6 in which the second code image CD2 is embedded (S48). When the payment application 20 reads the second code image CD2, the payment application 20 transmits the second information 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 determines whether the second information is correct (S49, S50). When determining 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 determination result is obtained in either S49 or S50, i.e., if the validity period T2 has elapsed without the second information being received, 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 app 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 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 Department 200 Credit Card Server 300 E-commerce Server 310 IF screen provision department 320 Payment Cooperation Department

Claims

1. a payment processing unit that performs electronic payment based on payment information obtained through communication with a payment application running on the first terminal device; displaying the first code image on the second terminal device in response to a call from an interface screen of the electronic commerce; 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 a predetermined operation related to the electronic commerce transaction when second information indicating that the payment application has read the second code image is received from the payment application; A payment server comprising:

2. 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; performing the predetermined operation 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.

3. The first validity period is longer than the second validity period. The payment server according to claim 2.

4. 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 2 or 3.

5. each of the first information and the second information includes identification information of a user in the electronic payment; the authentication unit performs the predetermined operation when it is confirmed that the identification information in the first information and the second information is the same. The payment server according to claim 1.

6. the authentication unit performs, as the predetermined operation, account linking that reduces the user's authentication operation related to subsequent electronic payment for the electronic commerce transaction compared to when accounts are not linked; The payment server according to claim 1.

7. The payment server according to claim 1 , wherein the authentication unit performs the predetermined operation to permit a user to log in to the electronic commerce transaction.

8. The payment server according to claim 6 , wherein the authentication unit performs the predetermined operation by allowing a user whose account has already been linked to log in to the electronic commerce transaction.

9. the authentication unit, as the predetermined operation, permits electronic payment for goods or services purchased in the electronic commerce transaction; The payment server according to claim 1.

10. 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 9.

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

12. The computer performing electronic payment based on payment information obtained through communication with the payment application running on the first terminal device; displaying the first code image on the second terminal device in response to a call from an interface screen of the electronic commerce; 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 a predetermined operation related to the electronic commerce transaction when second information indicating that the payment application has read the second code image is received from the payment application; method.

13. On the computer, A process of making an electronic payment based on payment information obtained by communication with a payment application running on the first terminal device; a process of displaying the first code image on the second terminal device in response to a call from an interface screen of the electronic commerce; a process of displaying a second code image 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; performing a predetermined operation related to the electronic commerce transaction when second information indicating that the payment application has read the second code image is received from the payment application; A program to execute.

Images