JP2024080129A - Settlement apparatus, settlement method, settlement program, and settlement system - Google Patents

Abstract

To simply and accurately verify the age for settlement authentication.SOLUTION: A settlement apparatus includes an acquisition unit, an authentication unit, ad a settlement processing unit. The acquisition unit acquires, from a user terminal, information indicating a request for identification information identifying a user and information indicating the necessity for authentication of the user. The authentication unit performs authentication of the user when acquiring the information indicating that the authentication of the user is necessary. The settlement processing unit provides, when acquiring information indicating that the authentication of the user is not necessary, the identification information identifying the user to the user terminal, or when acquiring the information indicating that the authentication of the user is necessary, verifies the identity of the user and provides identification information including an authentication result of the user to the user terminal, and executes a settlement according to settlement information when receiving the settlement information including the identification information, a store identifier, and the amount to be settled from a store terminal that read the identification information.SELECTED DRAWING: Figure 5

Description

The present invention relates to a payment device, a payment method, and a payment program.

When there are age restrictions for purchasing lottery tickets or cigarettes, age verification is carried out by checking a driver's license, etc.

Conventionally, there is known technology for verifying the user's age before making a payment. For example, when an age verification item is included among the items to be purchased, there is known technology for displaying an age verification screen and verifying the user's age based on the user's input.

International Publication No. 2021/079765

However, with conventional technology, age verification is carried out based on the use of a credit card, so if payment cannot be made with a credit card, a driver's license or other document must be checked each time, which is time-consuming.

This application was made in consideration of the above, and aims to easily and accurately verify age and perform payment authentication.

The payment device according to the present application is characterized by having an acquisition unit that acquires from a user terminal information indicating a request for identification information that identifies a user and information indicating whether user authentication is required, an authentication unit that authenticates the user when information indicating that user authentication is required is acquired, and a payment processing unit that provides the user terminal with identification information that identifies the user when information indicating that user authentication is not required is acquired, identifies the user and provides the user terminal with identification information including the authentication result of the user when information indicating that user authentication is required is acquired, and executes payment according to the payment information when payment information including the identification information, a store identifier, and a payment amount is acquired from a store terminal that reads the identification information.

According to one aspect of the embodiment, it is possible to easily and accurately perform age verification and payment authentication.

FIG. 1 is a diagram illustrating an example of information processing according to an embodiment. FIG. 2 is a diagram illustrating an example of information processing according to the embodiment. FIG. 3 is a diagram illustrating an example of information processing according to the embodiment. FIG. 4 is a diagram illustrating an example of the configuration of a payment system according to an embodiment. FIG. 5 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. FIG. 6 is a diagram illustrating an example of a user identification information storage unit according to the embodiment. FIG. 7 is a diagram illustrating an example of a store identification information storage unit according to the embodiment. FIG. 8 is a diagram illustrating an example of the configuration of a user terminal according to the embodiment. FIG. 9 is a diagram illustrating an example of the configuration of a store terminal according to the embodiment. FIG. 10 is a flowchart illustrating an example of a procedure of information processing according to the embodiment. FIG. 11 is a hardware configuration diagram showing an example of a computer that realizes the function of the payment server.

Below, the form for implementing the payment device, payment method, and payment program according to the present application (hereinafter referred to as "embodiment") will be described in detail with reference to the drawings. Note that the payment device, payment method, and payment program according to the present application are not limited to this embodiment. Furthermore, the same parts in each of the following embodiments will be given the same reference numerals, and duplicated explanations will be omitted.

1. Embodiment
The information processing implemented by the payment device of the present embodiment will be described with reference to Fig. 1 to Fig. 3. Fig. 1 to Fig. 3 are diagrams showing an example of the information processing according to the embodiment. In Fig. 1 to Fig. 3, the information processing according to the embodiment is implemented by a payment server 10, which is an example of the payment device according to the present embodiment.

[1-1. Payment system configuration]
Prior to the description of Figs. 1 to 3, the configuration of the payment system 1 will be described with reference to Fig. 4. Fig. 4 is a diagram showing a configuration example of the payment system according to the embodiment. As shown in Fig. 4, the payment system 1 according to the embodiment includes a payment server 10, a user terminal 100, and a store terminal 200. The payment server 10, the user terminal 100, and the store terminal 200 are connected to each other via a network N in a wired or wireless manner so as to be able to communicate with each other. The network N is, for example, a wide area network (WAN) such as the Internet. Note that the payment system 1 shown in Fig. 4 may include a plurality of payment servers 10, a plurality of user terminals 100, and a plurality of store terminals 200.

The payment server 10 shown in FIG. 4 is an information processing device that executes information processing according to the embodiment, and is realized by a server device, a cloud system, or the like. For example, when a user makes a payment at a payment destination, the payment server 10 determines whether or not a predetermined condition is satisfied, and performs payment processing only when it is determined that the predetermined condition is satisfied.

The user terminal 100 shown in FIG. 4 is an information processing device used by a user making a payment at a payment destination. For example, the user terminal 100 displays the identification information provided by the payment server 10 using a web browser or an application. The user terminal 100 is realized, for example, by a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), etc. Note that the examples shown in FIGS. 1 to 3 show a case where the user terminal 100 is a smartphone.

When the user terminal 100 receives control information for implementing a specified information processing from the payment server 10, the user terminal 100 implements the information processing in accordance with the control information. Here, the control information is described in, for example, a script language such as JavaScript (registered trademark) or a style sheet language such as CSS (Cascading Style Sheets). The specified application provided by the payment server 10 may itself be regarded as control information.

The store terminal 200 shown in FIG. 4 is an information processing device used by the store where the user makes the payment. For example, when the user makes a payment using identification information at the store, the store terminal 200 provides the payment information and identification information to the payment server 10. The store terminal 200 is realized by, for example, a smartphone, a tablet terminal, a notebook PC, a desktop PC, a mobile phone, a PDA, etc. Note that the examples shown in FIG. 2 and FIG. 3 show the case where the store terminal 200 is a POS terminal.

When the store terminal 200 receives control information for implementing a specified information processing from the payment server 10, the store terminal 200 implements the information processing according to the control information. Here, the control information is described in, for example, a script language such as JavaScript or a style sheet language such as CSS. Note that the specified application provided by the payment server 10 may itself be regarded as control information.

[1-2. Payment using user terminals]
Here, an example of payment (electronic payment) using the user terminal 100 will be described prior to the information processing executed by the payment server 10. In the following description, an example will be described in which a user U makes a payment using the user terminal 100 using a two-dimensional code (QR code (registered trademark)) placed in store A and indicating store identification information C that identifies store A, but the embodiment is not limited to this. The example of payment described below can also be applied when an arbitrary user makes a payment at an arbitrary store using an arbitrary user terminal 100. In addition, the store identification information C may be not only a QR code (registered trademark) but also a barcode, a predetermined mark, a number, or the like.

For example, when user U makes a payment for the use or purchase of a payment object (transaction object) such as various goods or services at store A, user U launches a payment app pre-installed on user terminal 100. User U then photographs store identification information C installed in store A via the payment app. In such a case, user terminal 100 displays a screen for inputting the price of the payment object and accepts input of the payment amount from user U or a clerk at store A. User terminal 100 then transmits to payment server 10 the user identification information identifying user U, store identification information C (or information indicated by store identification information C, i.e., information indicating store A (e.g., store ID)), and payment information indicating the payment amount.

In such a case, the payment server 10 transfers electronic money in the amount indicated by the payment amount from the account of user U indicated by the user identification information to the account of store A indicated by the store identification information C. The payment server 10 then sends a notification that the payment has been completed to the user terminal 100. In such a case, the user terminal 100 notifies the user that payment has been made with electronic money by outputting a screen or a specified sound indicating that the payment has been completed.

Note that the payment using the user terminal 100 is not limited to the above-mentioned process. For example, the payment using the user terminal 100 may be made using a store terminal installed in store A. For example, the user terminal 100 displays user identification information on the screen to identify user U. In such a case, the store terminal installed in store A reads the user identification information displayed on the user terminal 100 and transmits payment information indicating the user identification information (or information indicated by the user identification information, i.e., information indicating user U (e.g., user ID)), the payment amount, and information identifying store A to the payment server 10. In such a case, the payment server 10 transfers electronic money in the amount indicated by the payment amount from the account of user U indicated by the user identification information to the account of store A, and may notify the store terminal of store A or the user terminal 100 of the completion of the payment by outputting a screen or a predetermined sound indicating that the payment has been completed.

In addition, the payment using the user terminal 100 may not only be a process of transferring electronic money from an account to which the user U has previously charged electronic money to the account of the store A, but may also be, for example, a payment using a credit card registered by the user U in advance. In such a case, for example, the user terminal 100 may transfer electronic money of the payment amount to the account of the store A and bill the management company of the user U's credit card for the payment amount. The payment using the user terminal 100 is not limited to the payment via the two-dimensional code representing the above-mentioned store identification information (store identification information C) or the payment method via a screen display representing the user identification information. It may be configured to link information such as user information and payment amount from the user terminal 100 to the affiliated store server via the web, rather than via the two-dimensional code, and send the payment information to the payment server 10, or to obtain affiliated store information and payment amount from the affiliated store server and send the payment information from the user terminal 100 to the payment server 10 to realize the payment. For example, the affiliated store server may acquire user information of a payment service user (e.g., user U) through user linkage or the like, and then transmit the payment amount and payment store information to the payment server 10 to perform the payment, or the user terminal 100 may acquire the payment amount and store identification information C from the affiliated store server via the web and transmit it to the payment server 10 to perform the payment.

1-3. Overview of the embodiment
Payments using QR codes are generally divided into user scans and store scans. User scans are scans in which a store presents a QR code, which the user reads with the user terminal 100. Store scans are scans in which a user presents a QR code, which the store reads with the store terminal 200. Below, embodiments will be described separately for user scans and store scans.

In the following description, examples of products requiring age verification include, but are not limited to, the purchase of alcohol, tobacco, pachinko balls (balls for playing pachinko), lottery tickets, and insurance. In addition, the following description will explain a mode in which a QR code for user authentication and a QR code that does not perform user authentication are provided to the same store, and payment is made by user scanning (mode 1), a mode in which a QR code for user authentication is provided to one store and a QR code that does not perform user authentication is provided to another store, and payment is made by user scanning (mode 2), a mode in which authentication is performed using authentication conditions linked to the store when the store scans (mode 3), and a mode in which information indicating that the user has been authenticated is displayed on the user terminal 100 when payment is made by store scanning (mode 4).

(Aspect 1)
In the first aspect, store identification information for each store is set in advance. Store identification information is also set for the store where the user makes payment, and a QR code indicating the store identification information is issued and installed in the store. Here, two types of QR codes indicating the store identification information are issued and installed in the store: a QR code Q1 for performing age authentication of the user at the time of purchase, and a QR code Q2 for not performing age authentication of the user at the time of purchase. One of the two types of QR codes includes condition identification information for identifying a predetermined condition related to age restriction, and based on the store identification information and the condition identification information, it is determined whether or not age authentication is performed at the store where the payment is made. For example, the QR code Q1 is a QR code indicating store identification information M1 for age authentication and condition identification information indicating a predetermined condition for performing age restriction, and the QR code Q2 is a QR code indicating store identification information M2 for not requiring age authentication. For example, the QR code indicating the store identification information M1 includes condition identification information indicating a predetermined condition related to age restriction, such as "the user's age is 20 years old or older." It is assumed that the store identification information M1 and the store identification information M2 (i.e., the QR codes Q1 and Q2) are both linked in advance to an account (wallet) of the same store.

For example, a store clerk will present QR code Q1 when attempting to purchase a product that requires age verification, such as alcohol or tobacco, or when the group of products the user is attempting to purchase includes products that require age verification. On the other hand, if the user is only attempting to purchase products that do not require age verification, such as toilet paper, the clerk will present QR code Q2. As a result, when user U1 purchases a product that requires age verification, he or she will read QR code Q1 installed in the store for payments that require age verification.

When the user U1 reads the QR code Q1 installed in the store for payment with age verification, the user terminal 100 acquires the store identification information M1 (step S11). Then, the user terminal 100 transmits payment information including the user identification information (user's login ID), the store identification information M1, and the payment amount to the payment server 10 (step S12). Meanwhile, the payment server 10 refers to the store identification information M1 included in the payment information and determines whether there is a condition linked to the store identification information M1 (step S13). For example, the payment server 10 determines whether there is a condition linked to the store identification information M1, and if there is, acquires a condition such as "the user's age is 20 years old or older". Then, the payment server 10 acquires registered user information from the user identification information included in the payment information, and authenticates the user by determining whether the acquired user information satisfies the acquired condition, for example, "the user's age is 20 years old or older" (step S14). Specifically, the payment server 10 determines whether or not the user has completed eKYC (electronic Know Your Customer) based on the user identification information. If the payment server 10 determines that the user has not completed eKYC, it notifies the user that age authentication is not possible and that eKYC is required for age authentication, and displays a page directing the user to eKYC. If the payment server 10 determines that the user has completed eKYC, it determines whether or not a specified condition regarding age restrictions is met based on the eKYC-completed user information (e.g., age) linked to the user identification information.

Then, if the user U1 is authenticated as a result of the age verification (i.e., if it is determined that the user U1 is a user who satisfies the predetermined conditions), the payment server 10 executes the payment process (step S15). For example, when executing the payment process, the payment server 10 transfers electronic money for the payment amount indicated by the payment information from the account linked to the user identification information to the account linked to the store identification information. Then, the payment server 10 transmits to the user terminal 100 a notice that the payment process has been completed (step S16). Note that, if the payment server 10 is unable to authenticate the user, that is, if the user U1 is a user who does not satisfy the predetermined conditions, the payment server 10 may not perform step S15 and may transmit to the user terminal 100 a notice that the payment has not been made. On the other hand, when the user U1 purchases a product that does not require age verification, the QR code Q2 is read and the store identification information M2 is obtained (step S17). Then, the user terminal 100 transmits payment information indicating the user identification information, the store identification information M2, and the payment amount to the payment server 10 (step S18).

In such a case, the payment server 10 refers to the store identification information M2 included in the payment information and determines whether there is a condition linked to the store identification information M2 (step S19). If there is no condition linked to the store identification information M2, the payment server 10 executes normal payment processing based on the payment information without authenticating the user (step S20), and transmits the result to the user terminal 100 (step S21).

For example, the store identification information M1 may include a flag indicating whether or not to authenticate the user, and the store identification information M2 may not include a flag indicating whether or not to authenticate the user. In such a case, the payment server 10 refers to the store identification information included in the payment information, and if the flag indicating whether or not to authenticate the user is included, it may authenticate the user, and if the flag is not included, it may not authenticate the user.

(Aspect 2)
In the above example, the store identification information M1 linked to the authentication condition and the store identification information M2 not linked to the authentication condition are provided to the same store. However, the embodiment is not limited to this. For example, the store identification information M1 linked to the authentication condition and the store identification information M2 not linked to the authentication condition may be provided to individual stores. In such a case, the store identification information M1 and M2 are linked to the wallets of the individual stores.

For example, store A is provided with store identification information A that is linked to store A's wallet and has authentication conditions linked to it, and store B is provided with store identification information B that is linked to store B's wallet and has no authentication conditions linked to it. In this situation, when using store A, the user terminal 100 transmits payment information including store identification information A to the payment server 10, and when using store B, the user terminal 100 transmits payment information including store identification information B to the payment server 10.

On the other hand, the payment server 10 determines whether or not authentication conditions are linked to the store identification information included in the payment information. For example, if the payment information includes store identification information A, the payment server 10 determines that authentication conditions are linked to store identification information A. In such a case, the payment server 10 authenticates the user using the authentication conditions linked to store identification information A, and performs payment when the user is authenticated. On the other hand, if the payment information includes store identification information B, the payment server 10 determines that authentication conditions are not linked to store identification information B. In such a case, the payment server 10 performs payment without performing authentication.

In this way, authentication conditions may be linked in advance to each store (more specifically, the store identification information of each store). In such a case, the payment server 10 determines whether or not authentication conditions are linked to each store, and if it determines that they are linked, it performs payment processing after authenticating the user, and if it determines that they are not linked, it performs payment processing without authenticating the user.

The store identification information may include a flag indicating whether or not authentication conditions are linked. If such a flag is included, the payment server 10 can determine whether or not to authenticate the user (i.e., whether or not authentication conditions are linked to the store identification information or to the store) by referring to the store identification information.

(Aspect 3)
In the third aspect, when the user U1 purchases a product, the user terminal 100 transmits a request for a barcode for store scanning to the payment server 10 (step S21).

When the payment server 10 receives the barcode request, it issues a one-time code, links it to the user identification information, and sends it to the user terminal 100 (step S22).

The user terminal 100 displays a barcode indicating the one-time code. The store terminal 200 also reads the barcode displayed on the user terminal 100 (step S23).

When the store terminal 200 reads the barcode, it transmits payment information including the one-time code (the one-time code linked to the user identification information), store identification information, and the payment amount to the payment server 10 (step S24).

Here, when the payment server 10 acquires the payment information from the user terminal 100, it determines whether or not to authenticate the user based on the store identification information included in the payment information (step S25). For example, the payment server 10 may determine whether or not the store identification information is linked to the authentication conditions, as in aspects 1 and 2, or may determine whether or not the store identification information includes a flag indicating whether or not to authenticate the user.

If the payment server 10 determines that the user should be authenticated, it authenticates the user (step S26) and, upon authentication, makes a payment (step S27). The payment server 10 then transmits a message to the store terminal 200 indicating that the payment has been made (step S28).

Here, unlike user scanning, in the case of the store scanning method, it may be possible to identify the product that the user is trying to purchase. Therefore, the payment server 10 may authenticate the user when the product that the user is trying to purchase satisfies certain conditions.

For example, when the store terminal 200 transmits payment information to the payment server 10, it also provides a payment ID for identifying the payment action. The store terminal 200 also associates product information (e.g., JIS code, etc.) of the product to be paid with the payment ID and uploads it to the POS server 300 (step S30). Meanwhile, when the payment server 10 receives the payment ID along with the payment information, it uses the payment ID to obtain product information from the POS server 300 (step S31). The payment server 10 may also obtain product information of the product to be purchased, which is included in the payment information, directly from the POS server 300 when obtaining the payment information.

In such a case, the payment server 10 determines whether or not to authenticate the user based on the product information (step S25). If the payment server 10 determines that the product requires age verification as indicated by the product information, it determines whether or not the user U1 is a user who satisfies predetermined conditions (step S26). Furthermore, if the payment server 10 determines that the product does not require age verification, for example, it executes the payment process without performing age verification.

The payment server 10 determines that the product requires age verification, and if the age verification results in authentication (i.e., if it is determined that user U1 is a user who satisfies the predetermined conditions), it executes the payment process (step S27). Note that if the payment server 10 determines as a result of the age verification that authentication is not required, it does not execute the payment process.

When executing the payment process, the payment server 10 transfers electronic money for the payment amount indicated in the payment information from the account linked to the user identification information linked to the one-time code to the account linked to the store identification information, and transmits a notification that the payment has been completed to the store terminal 200 (step S28).

As in aspects 1 to 3 described above, the payment server 10 determines whether the store identification information (store) is linked to the authentication conditions, whether the store identification information includes whether authentication is to be performed, and whether the purchased item is a purchased item that requires authentication. That is, the payment server 10 determines whether to authenticate the user based on payment-related information such as the store identification information and purchased item that can be obtained at the time of code payment. Furthermore, if the payment server 10 determines that the user should be authenticated, it authenticates the user. Then, when the user is authenticated, the payment server 10 realizes the payment, and when the user is not authenticated, the payment server 10 does not make the payment. As a result of such processing, the payment server 10 can smoothly realize a payment that requires authentication when user authentication is required in various situations.

(Aspect 4)
The payment server 10 may verify the age of the user U1 when issuing the one-time code, and transmit the one-time code including the result of the age verification to the user terminal 100. The store terminal 200 may then verify the age of the user U1 by reading a barcode indicating the one-time code. For example, in aspect 4, store identification information is set in advance for each store. Store identification information is also set for the store where the user makes payment, and is stored in the store terminal 200.

When user U1 purchases a product, user terminal 100 accepts an operation from the user to display a barcode for store scanning (step S41). At this time, user terminal 100 accepts a designation from the user as to whether or not age authentication is to be performed. For example, when using store scanning to purchase a product that requires age authentication, such as alcoholic beverages, the user designates that age authentication will be performed, whereas when using store scanning to purchase only products that do not require age authentication, the user performs an operation to display the barcode without designating that age authentication is to be performed. Note that user terminal 100 may accept a designation as to whether or not authentication of any condition is to be performed in addition to age authentication.

In such a case, the user terminal 100 transmits a request to display a barcode to the payment server 10 together with the specified content of age authentication (step S42). On the other hand, if there is an instruction to perform age authentication, the payment server 10 performs age authentication of the user using the user terminal 100 (step S43). Then, the payment server 10 generates a one-time code including the result of the age authentication (step S44) and transmits the generated one-time code to the user terminal 100 (step S45). For example, if the user is 20 years old or older, the payment server 10 transmits a one-time code including a flag indicating that the user is 20 years old or older, and if the user is 20 years old or younger, the payment server 10 transmits a one-time code that does not include a flag indicating that the user is 20 years old or older. On the other hand, if there is no instruction to perform age authentication, the payment server 10 transmits a one-time code that does not include a flag related to authentication. In addition, if the execution of age authentication is specified and the specified condition of age authentication is not met, the payment server 10 may display that the one-time code cannot be issued.

In such a case, the store terminal 200 can obtain the user authentication result on the spot without sending the payment information to the payment server 10. For example, if the items to be purchased include products that require age authentication, such as alcoholic beverages, and the one-time code includes a flag indicating that the user is 20 years of age or older, the store terminal 200 sends the payment information to the payment server 10 (step S46). On the other hand, if the items to be purchased include products that require age authentication, such as alcoholic beverages, and the one-time code does not include a flag indicating that the user is 20 years of age or older, the store terminal 200 may not send the payment information to the payment server 10 and may display a message indicating that payment cannot be made.

1-4. Variations of the Processing in the Embodiment
(Using conditions other than age restrictions)
In the above embodiment, the payment server 10 executes the payment process based on whether or not the user U1 satisfies a predetermined condition for age restriction. However, the predetermined condition is not limited to the condition for age restriction. For example, in addition to such age thresholds, the store identification information may be associated with conditions related to various demographic attributes and psychographic attributes such as the user's gender, generation, and residential area, and conditions related to past usage history. For example, the payment server 10 may perform authentication based on whether or not the payment amount satisfies a predetermined condition. For example, when a payment upper limit is set as the predetermined condition, the payment server 10 may perform payment authentication and execute the payment process if the payment amount does not exceed the payment upper limit. Also, for example, the payment server 10 may perform authentication based on whether or not the gender of the user satisfies a predetermined condition. For example, when the predetermined condition is set to target only one gender, the payment server 10 may perform payment authentication and execute the payment process if the user is of the target gender. Also, for example, the payment server 10 may perform authentication based on whether or not the nationality of the user satisfies a predetermined condition. For example, if a predetermined condition is set to target only users of a specific nationality, the payment server 10 may authenticate the payment and execute the payment processing if the user has the specific nationality.

(Use a photo of your face)
In the above embodiment, the store terminal 200 reads the barcode displayed on the user terminal 100, and the payment server 10 performs the age confirmation and executes the payment process. However, for payment authentication, a further confirmation may be performed in addition to the age confirmation. For example, when the age confirmation is successful, the payment server 10 may display the face photo stored in the eKYC on the store terminal 200, and the store clerk may confirm whether the face photo matches the face of the customer visiting the store, and execute the payment process when the store clerk performs an operation to indicate that the face photo matches. In addition to the face photo, the eKYC may store information such as an address, a telephone number, a date of birth, and a nationality, and the store clerk may use this information to perform confirmation, and the payment server 10 may execute the payment process when the store clerk performs an operation to indicate that the confirmation is correct.

(Age Verification Using an Interface)
In the above embodiment (aspect 1), a case was shown in which the store identification information M1 included in the payment information is referenced, and it is determined whether or not a condition linked to the store identification information M1 exists. If the condition exists, the condition is acquired, and the registered user's information is determined to satisfy the condition, thereby authenticating the user. Here, instead of authenticating the user by determining whether or not the registered user's information satisfies the condition, the user may be authenticated by displaying an interface for confirming the age. For example, when the condition linked to the store identification information M1 includes an age authentication condition, the payment server 10 may display an age confirmation interface on the user terminal 100. For example, the payment server 10 may display a question such as "Are you 20 years old or older?" and a choice of "Yes" or "No" in response to the question "Are you 20 years old or older?". The payment server 10 may then execute the payment process when the user selects (e.g., presses) "Yes" as the answer to the question "Are you 20 years old or older?". In addition, when the user selects "No" as the answer to the question "Are you 20 years old or older?", the payment server 10 may display on the user terminal 100 a message indicating that the payment cannot be made and may end the information processing without making the payment. In addition, when the user responds to the question "Are you 20 years old or older", the payment server 10 may assign an age condition confirmation flag to the user and store the answer. For example, the payment server 10 may assign an age condition confirmation flag to the payment history information of the user and store the answer. For example, when the user selects "Yes" to the question "Are you 20 years old or older", the payment server 10 may assign information indicating that "Yes" was selected for the payment to the payment history information of the payment together with the age condition confirmation flag and store the answer. In addition, for example, when the user selects "No" to the question "Are you 20 years old or older", the payment server 10 may assign information indicating that "No" was selected for the payment to the payment history information of the payment together with the age condition confirmation flag and store the answer.

In the second embodiment, similar to the first embodiment, the user may be authenticated by displaying an age verification interface. For example, the payment server 10 may display an age verification interface on the user terminal 100 after the user reads the QR code of the store. For example, the payment server 10 may display an age verification screen on the user terminal 100 when the user reads the QR code of the store, and may display a payment amount input screen when the user selects "Yes" as an answer to the question "Are you 20 years old or older?", and may execute the payment process based on the payment amount input on the payment amount input screen. In addition, the payment server 10 may end the information processing without displaying the payment amount input screen when the user selects "No" as an answer to the question "Are you 20 years old or older?". In addition, the payment server 10 may display the payment amount input screen before the age verification screen. For example, the payment server 10 may cause the user terminal 100 to display a payment amount input screen when the user reads a store's QR code, and may cause an age verification screen to be displayed when an amount is entered into the payment amount input screen, and may execute the payment process if the user selects "Yes" in response to the question "Are you over 20 years old?".

[2. Configuration of the payment server]
Next, the configuration of the payment server 10 according to the embodiment will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the configuration of the payment server 10 according to the embodiment. As shown in Fig. 5, the payment server 10 has a communication unit 20, a storage unit 30, and a control unit 40. Note that the payment server 10 may have an input unit (e.g., a keyboard, a mouse, etc.) that accepts various operations from an administrator of the payment server 10, and a display unit (e.g., a liquid crystal display, etc.) that displays various information.

(Communication unit 20)
The communication unit 20 is realized by, for example, a network interface card (NIC) etc. The communication unit 20 is connected to a network N by wire or wirelessly, and transmits and receives information to and from the user terminal 100 etc. via the network N.

(Memory unit 30)
The storage unit 30 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 5 , the storage unit 30 has a user identification information storage unit 31 and a store identification information storage unit 32.

The user identification information storage unit 31 stores user identification information. Here, an example of information stored in the user identification information storage unit 31 will be described with reference to FIG. 6. FIG. 6 is a diagram showing an example of the user identification information storage unit 31 according to an embodiment. In the example of FIG. 6, the user identification information storage unit 31 has items such as "user ID", "user identification information", and "one-time code".

"User ID" indicates identification information for identifying the user. "User identification information" indicates user identification information. "One-time code" indicates the one-time code issued when a request for a barcode for store scanning was accepted.

The store identification information storage unit 32 stores store identification information. Here, an example of information stored in the store identification information storage unit 32 will be described with reference to FIG. 7. FIG. 7 is a diagram showing an example of the store identification information storage unit 32 according to an embodiment. In the example of FIG. 7, the store identification information storage unit 32 has items such as "store ID," "store identification information," and "age verification flag."

"Store ID" indicates identification information for identifying a store. "Store identification information" indicates store identification information. "Age verification flag" indicates whether the store sells products that require age verification.

(Control unit 40)
The control unit 40 is a controller, and is realized, for example, by a central processing unit (CPU) or a micro processing unit (MPU) executing various programs stored in a storage device inside the payment server 10 using a RAM as a working area. The control unit 40 is also realized, for example, by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). As shown in FIG. 5, the control unit 40 according to the embodiment has an acquisition unit 41, a determination unit 42, an authentication unit 43, a payment processing unit 44, and a notification unit 45, and realizes or executes the functions and actions of information processing described below.

(Acquisition unit 41)
The acquisition unit 41 acquires various information from an external information processing device. For example, the acquisition unit 41 acquires various information from another information processing device such as the user terminal 100. The acquisition unit 41 also acquires various information from the storage unit 30. The acquisition unit 41 also stores the acquired various information in the storage unit 30.

When a user performs a user scan to purchase a product at a store where payment is to be made, the acquisition unit 41 acquires user identification information, store identification information, and payment information transmitted from the user terminal 100 by the user reading a QR code installed at the store where payment is to be made. For example, when the user reads a QR code installed for payment with age verification among multiple QR codes installed at the store where payment is to be made, the acquisition unit 41 acquires store identification information linked to a predetermined condition for age restriction. Also, for example, when the user reads a QR code installed for payment without age verification among multiple QR codes installed at the store where payment is to be made, the acquisition unit 41 acquires store identification information not linked to a predetermined condition for age restriction.

In addition, when a user performs a store scan to purchase a product at a store where payment is to be made, the acquisition unit 41 acquires the one-time code (a one-time code linked to user identification information), store identification information, and payment information transmitted from the store terminal 200 by a store clerk reading a barcode indicating the one-time code displayed on the user terminal 100. In addition, the acquisition unit 41 acquires product information transmitted from the store terminal 200.

The acquisition unit 41 also acquires information indicating a request for user identification information from the user terminal 100. The acquisition unit 41 also acquires information indicating whether or not authentication of the user is required.

(Determination unit 42)
The determination unit 42 determines whether to authenticate the user based on payment-related information (specifically, store identification information) that can be acquired for a payment made using the user terminal 100. For example, the determination unit 42 determines whether an authentication condition is associated with the store identification information. Also, for example, the determination unit 42 determines whether or not the store identification information includes whether or not authentication is to be performed. Also, for example, the determination unit 42 makes a determination based on the store identification information out of the user identification information, payment amount, and store identification information acquired by the acquisition unit 41. Also, for example, the determination unit 42 determines to authenticate the user if the product indicated by the product information acquired by the acquisition unit 41 satisfies a predetermined condition.

(Authentication unit 43)
The authentication unit 43 authenticates the user when the determination unit 42 determines that the user should be authenticated. For example, the authentication unit 43 authenticates the user based on whether or not the user satisfies an authentication condition associated with the store identification information. Also, for example, the authentication unit 43 authenticates the user when the acquisition unit 41 acquires information indicating that the user needs to be authenticated.

(Payment Processing Unit 44)
If the authentication of the user is successful, the payment processing unit 44 executes the payment based on the payment-related information. If the authentication of the user is unsuccessful, the payment processing unit 44 does not execute the payment based on the payment-related information.

When the payment processing unit 44 acquires information indicating that user authentication is not required, it provides user identification information to the user terminal 100. In addition, when the payment processing unit 44 acquires information indicating that user authentication is required, it identifies the user and provides identification information including the user authentication result to the user terminal 100.

(Notification unit 45)
The notification unit 45 notifies the user terminal 100 of the completion of payment when the payment processing unit 44 executes the payment processing. For example, in the case of a user scan, the notification unit 45 notifies the user terminal 100 of the completion of payment. Also, for example, in the case of a store scan, the notification unit 45 notifies the store terminal 200 of the completion of payment.

[3. Configuration of user terminal]
Next, the configuration of the user terminal 100 according to the embodiment will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the configuration of the user terminal 100 according to the embodiment. As shown in Fig. 8, the user terminal 100 has a communication unit 110, an input unit 120, an output unit 130, and a control unit 140.

(Communication unit 110)
The communication unit 110 is realized by, for example, a NIC etc. The communication unit 110 is connected to a predetermined network N by wire or wirelessly, and transmits and receives information to and from the payment server 10 etc. via the predetermined network N.

(Input unit 120)
The input unit 120 accepts various operations from the user. For example, the input unit 120 may accept various operations from the user via a display surface using a touch panel function. The input unit 120 may also accept various operations from buttons provided on the user terminal 100 or a keyboard or mouse connected to the user terminal 100.

(Output unit 130)
The output unit 130 is a display screen of a tablet terminal or the like realized by, for example, a liquid crystal display or an organic EL (Electro-Luminescence) display, and is a display device for displaying various information. For example, the output unit 130 displays information acquired from the payment server 10.

(Control unit 140)
The control unit 140 is, for example, a controller, and is realized by a CPU, an MPU, or the like executing various programs stored in a storage device inside the user terminal 100 using a RAM as a working area. For example, the various programs include application programs installed in the user terminal 100. For example, the various programs include application programs that display information obtained from the payment server 10. The control unit 140 is also realized by an integrated circuit, for example, an ASIC, an FPGA, or the like.

As shown in FIG. 8, the control unit 140 has a receiving unit 141 and a transmitting unit 142, and realizes or executes the information processing functions described below.

(Receiving unit 141)
The receiving unit 141 receives various information from an external information processing device. For example, the receiving unit 141 receives various information from another information processing device such as the payment server 10. For example, the receiving unit 141 receives a notification that payment has been completed.

(Transmitter 142)
The transmission unit 142 provides various information to an external information processing device. For example, the transmission unit 142 transmits various information to another information processing device such as the payment server 10. For example, the transmission unit 142 transmits user identification information, store identification information, and payment information.

[4. Store terminal configuration]
Next, the configuration of the store terminal 200 according to the embodiment will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the configuration of the store terminal 200 according to the embodiment. As shown in Fig. 9, the store terminal 200 has a communication unit 210, an input unit 220, an output unit 230, and a control unit 240.

(Communication unit 210)
The communication unit 210 is realized by, for example, a NIC etc. The communication unit 210 is connected to a predetermined network N by wire or wirelessly, and transmits and receives information to and from the payment server 10 etc. via the predetermined network N.

(Input unit 220)
The input unit 220 accepts various operations from a store clerk. For example, the input unit 220 may accept various operations from a store clerk via a display screen using a touch panel function. The input unit 220 may also accept various operations from buttons provided on the store terminal 200 or a keyboard or mouse connected to the store terminal 200.

(Output unit 230)
The output unit 230 is a display screen of a tablet terminal or the like realized by, for example, a liquid crystal display, an organic EL display, etc., and is a display device for displaying various information. For example, the output unit 230 displays information acquired from the payment server 10.

(Control unit 240)
The control unit 240 is, for example, a controller, and is realized by a CPU, an MPU, or the like executing various programs stored in a storage device inside the store terminal 200 using a RAM as a working area. For example, the various programs include application programs installed in the store terminal 200. For example, the various programs include application programs that display information obtained from the payment server 10. The control unit 240 is also realized by an integrated circuit, for example, an ASIC, an FPGA, or the like.

As shown in FIG. 9, the control unit 240 has a receiving unit 241 and a transmitting unit 242, and realizes or executes the information processing functions described below.

(Receiving unit 241)
The receiving unit 241 receives various information from an external information processing device. For example, the receiving unit 241 receives various information from another information processing device such as the payment server 10. For example, the receiving unit 241 receives a notification that payment has been completed.

(Transmitter 242)
The transmission unit 242 provides various information to an external information processing device. For example, the transmission unit 242 transmits various information to another information processing device such as the payment server 10. For example, the transmission unit 242 transmits a one-time code, store identification information, and payment information. Also, for example, the transmission unit 242 transmits product information of a product purchased by the user.

5. Information Processing Flow
A procedure of information processing of the payment server 10 according to the embodiment will be described with reference to Fig. 10. Fig. 10 is a flowchart showing an example of a procedure of information processing according to the embodiment.

As shown in FIG. 10, the payment server 10 acquires user identification information, store identification information, and payment information (step S101).

The payment server 10 determines whether or not to authenticate the user (step S102).

If the payment server 10 determines that the user should be authenticated (step S102; YES), it authenticates the user and executes the payment if the authentication is successful (step S103). On the other hand, if the payment server 10 determines that the user should not be authenticated (step S102; NO), it executes the payment without authenticating the user (step S104).

6. Effects
As described above, the payment server 10 according to the embodiment includes an acquisition unit 41, an authentication unit 43, and a payment processing unit 44. The acquisition unit 41 acquires information indicating a request for identification information for identifying a user and information indicating whether or not the user needs to be authenticated from the user terminal 100. When the authentication unit 43 acquires information indicating that the user needs to be authenticated, it authenticates the user. When the payment processing unit 44 acquires information indicating that the user needs not to be authenticated, it provides the user terminal 100 with identification information for identifying the user, and when the payment processing unit 44 acquires information indicating that the user needs to be authenticated, it provides the user terminal 100 with identification information for identifying the user and identification information including the authentication result of the user, and when the payment processing unit 44 acquires payment information including the identification information, a store identifier, and a payment amount from the store terminal 200 that reads the identification information, it executes payment according to the payment information.

This allows the payment server 10 according to the embodiment to easily and accurately perform age verification and payment authentication.

The acquisition unit 41 also acquires information indicating a request for identification information that identifies the user based on the user's operation to display a barcode for store scanning.

This allows the payment server 10 according to the embodiment to properly perform payment authentication when making a payment by store scanning.

In addition, the identification information that identifies the user is a one-time code.

This allows the payment server 10 according to the embodiment to properly perform payment authentication based on the one-time code.

In addition, if the items to be purchased include a product that requires authentication and the identification information does not include information indicating the authentication result of the user, the store terminal 200 will not send the payment information to the payment device.

This allows the payment server 10 according to the embodiment to make payments only when appropriate.

7. Hardware Configuration
The payment server 10 according to each of the above-described embodiments is realized, for example, by a computer 1000 having a configuration as shown in Fig. 11. The payment server 10 will be described below as an example. Fig. 11 is a hardware configuration diagram showing an example of a computer that realizes the functions of the payment server 10. The computer 1000 has a CPU 1100, a ROM 1200, a RAM 1300, a HDD 1400, a communication interface (I/F) 1500, an input/output interface (I/F) 1600, and a media interface (I/F) 1700.

The CPU 1100 operates based on a program stored in the ROM 1200 or the HDD 1400, and controls each component. The ROM 1200 stores a boot program executed by the CPU 1100 when the computer 1000 is started, and programs that depend on the hardware of the computer 1000, etc.

HDD 1400 stores programs executed by CPU 1100 and data used by such programs. Communication interface 1500 receives data from other devices via communication network 500 (corresponding to network N in the embodiment) and sends it to CPU 1100, and also transmits data generated by CPU 1100 to other devices via communication network 500.

The CPU 1100 controls output devices such as a display and a printer, and input devices such as a keyboard and a mouse, via the input/output interface 1600. The CPU 1100 acquires data from the input devices via the input/output interface 1600. The CPU 1100 also outputs data generated via the input/output interface 1600 to the output devices.

The media interface 1700 reads a program or data stored in the recording medium 1800 and provides it to the CPU 1100 via the RAM 1300. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1300 via the media interface 1700 and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable Disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

For example, when the computer 1000 functions as the payment server 10, the CPU 1100 of the computer 1000 executes a program loaded onto the RAM 1300 to realize the functions of the control unit 40. In addition, the HDD 1400 stores each piece of data in the storage device of the payment server 10. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, the CPU 1100 of the computer 1000 may obtain these programs from another device via a specified communication network.

[8. Other]
Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the Disclosure of the Invention section.

The above-mentioned payment server 10 can also be flexibly configured to call external platforms, etc., using an API (Application Programming Interface) or network computing, depending on the function.

In addition, the word "unit" in the claims can be read as "means" or "circuit." For example, an acquisition unit can be read as an acquisition means or an acquisition circuit.

REFERENCE SIGNS LIST 10 Payment server 20 Communication unit 30 Storage unit 31 User identification information storage unit 32 Store identification information storage unit 40 Control unit 41 Acquisition unit 42 Determination unit 43 Authentication unit 44 Payment processing unit 45 Notification unit 100 User terminal 110 Communication unit 120 Input unit 130 Output unit 140 Control unit 141 Reception unit 142 Transmission unit 200 Store terminal 210 Communication unit 220 Input unit 230 Output unit 240 Control unit 241 Reception unit 242 Transmission unit

The present invention relates to a payment device, a payment method , a payment program , and a payment system .

Claims (6)

an acquisition unit that acquires information indicating a request for identification information for identifying a user from the user terminal and information indicating whether authentication of the user is required;
an authentication unit that performs authentication of a user when information indicating that authentication of the user is required is acquired;
When information indicating that user authentication is not required is obtained, providing identification information for identifying the user to the user terminal, and when information indicating that user authentication is required is obtained, providing identification information for identifying the user and including the authentication result of the user to the user terminal;
and a payment processing unit that, when payment information including the identification information, a store identifier, and a payment amount is obtained from the store terminal that reads the identification information, executes payment in accordance with the payment information. The acquisition unit is
The payment device according to claim 1 , further comprising: acquiring information indicating a request for identification information for identifying the user based on an operation by the user to display a barcode for store scanning. The payment device according to claim 1 , wherein the identification information for identifying the user is a one-time code. The payment device according to claim 1, characterized in that the store terminal does not transmit the payment information to the payment device if the items to be purchased include a product that requires authentication and the identification information does not include information indicating the authentication result of the user. 1. A computer implemented payment method comprising:
an acquisition step of acquiring information indicating a request for identification information for identifying a user from the user terminal and information indicating whether authentication of the user is required;
an authentication step of authenticating the user when information indicating that authentication of the user is required is obtained;
When information indicating that user authentication is not required is obtained, providing identification information for identifying the user to the user terminal, and when information indicating that user authentication is required is obtained, providing identification information for identifying the user and including the authentication result of the user to the user terminal;
a payment processing step of, when payment information including the identification information, a store identifier, and a payment amount is obtained from the store terminal that read the identification information, executing a payment in accordance with the payment information. an acquisition step of acquiring information indicating a request for identification information for identifying a user from a user terminal and information indicating whether authentication of the user is required;
an authentication step for authenticating the user when information indicating that authentication of the user is required is obtained;
When information indicating that user authentication is not required is obtained, providing identification information for identifying the user to the user terminal, and when information indicating that user authentication is required is obtained, providing identification information for identifying the user and including the authentication result of the user to the user terminal;
and when payment information including the identification information, a store identifier, and a payment amount is obtained from the store terminal that reads the identification information, the computer executes a payment processing procedure to execute payment in accordance with the payment information.

Images