Settlement device, settlement method, and settlement program
Patent Information
- Application Number
- JP2023098257
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-15
- Publication Date
- 2025-09-29
AI Technical Summary
Conventional age verification methods require manual checking of identification documents when payment is made without a credit card, which is cumbersome.
A payment device and method that includes a determination unit to authenticate users based on payment-related information, an authentication unit to verify age, and a payment processing unit to execute payments only when authentication is successful.
Enables easy and accurate age verification and payment authentication, reducing the need for manual document checks and streamlining the payment process.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a payment device, a payment method, and a payment program. [Background technology]
[0002] When there are age restrictions for purchasing things such as lottery tickets or cigarettes, age verification is carried out by checking a driver's license, etc.
[0003] Conventionally, there is known a technique for performing age verification before making a payment. For example, when an age verification product is included in products to be purchased, a technique is known in which an age verification screen is displayed and age verification is performed based on an input from a user. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] International Publication No. 2021 / 079765 Summary of the Invention [Problem to be solved by the invention]
[0005] 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.
[0006] The present application has been made in consideration of the above, and aims to perform age verification and payment authentication simply and accurately. [Means for solving the problem]
[0007] The payment device according to the present application is characterized in having a judgment unit that judges whether or not to authenticate a user in a payment based on payment-related information obtainable for a payment made using a user terminal, an authentication unit that authenticates the user when it is determined that the user should be authenticated, and a payment processing unit that executes the payment based on the payment-related information when the authentication of the user is successful. Effect of the Invention
[0008] According to one aspect of the embodiment, it is possible to easily and accurately perform age verification and perform payment authentication. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of information processing according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of information processing according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of information processing according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of a payment system according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of the configuration of the payment server according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a user identification information storage unit according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a store identification information storage unit according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a user terminal according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the configuration of a store terminal according to the embodiment. [Figure 10] FIG. 10 is a flowchart illustrating an example of a procedure of information processing according to the embodiment. [Figure 11] FIG. 11 is a hardware configuration diagram illustrating an example of a computer that realizes the functions of the payment server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] The following describes in detail the form (hereinafter, "embodiment") for implementing the payment device, payment method, and payment program according to the present application with reference to the drawings. Note that the payment device, payment method, and payment program according to the present application are not limited to the embodiment. In addition, the same parts in the following embodiments are given the same reference numerals, and duplicated explanations are omitted.
[0011] 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, it is assumed that 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.
[0012] [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 an example of the configuration 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 WAN (Wide Area Network) 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.
[0013] 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, etc. 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 the payment processing only when it is determined that the predetermined condition is satisfied.
[0014] The user terminal 100 shown in Fig. 4 is an information processing device used by a user who makes 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 by, for example, a smartphone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. Note that the examples shown in Figs. 1 to 3 show a case where the user terminal 100 is a smartphone.
[0015] When the user terminal 100 receives control information for implementing a predetermined information process from the payment server 10, the user terminal 100 implements the information process according to 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). A predetermined application provided by the payment server 10 may itself be regarded as the control information.
[0016] The store terminal 200 shown in Fig. 4 is an information processing device used by a store where a user makes a payment. For example, when a user makes a payment using identification information at a store, the store terminal 200 provides the payment information and the 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, or the like. Note that the examples shown in Figs. 2 and 3 show a case where the store terminal 200 is a POS terminal.
[0017] When the store terminal 200 receives control information for implementing a predetermined information process from the payment server 10, the store terminal 200 implements the information process 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 a predetermined application provided by the payment server 10 may itself be regarded as the control information.
[0018] [1-2. Payment using user terminals] Here, prior to the information processing executed by the payment server 10, an example of payment (electronic payment) using the user terminal 100 will be described. 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 to a case in which 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.
[0019] For example, when user U makes a payment for using or purchasing 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.
[0020] 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. Then, the payment server 10 transmits a notification that the payment has been completed to the user terminal 100. In such a case, the user terminal 100 notifies that the payment has been made with electronic money by outputting a screen or a predetermined sound indicating that the payment has been completed.
[0021] It should be noted 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 a 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 may transfer electronic money in an 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 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.
[0022] Furthermore, 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 above-mentioned payment via a two-dimensional code representing the store identification information (store identification information C) or a payment method via a screen display representing the user identification information. Instead of via a two-dimensional code, a configuration may be used in which information such as user information and payment amount is linked from the user terminal 100 to the affiliated store server via the web and payment information is sent to the payment server 10, or a configuration may be used in which affiliated store information and payment amount are obtained from the affiliated store server and payment information is sent from the user terminal 100 to the payment server 10 to realize the payment. For example, the payment may be made by an affiliated store server that acquires user information of a payment service user (e.g., user U) through user collaboration or the like, and transmitting the payment amount and payment store information to the payment server 10, or by a user terminal 100 acquiring the payment amount and store identification information C from the affiliated store server via the web and transmitting it to the payment server 10.
[0023] 1-3. Overview of the embodiment Payments using QR codes are generally divided into user scans and store scans. In a user scan, a store presents a QR code, which the user reads with the user terminal 100. In a store scan, 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.
[0024] 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, in the following description, a mode (mode 1) in which a QR code for user authentication and a QR code without user authentication are provided to the same store, and payment is made by user scanning, a mode (mode 2) in which a QR code for user authentication is provided to one store, and a QR code without user authentication is provided to another store, and payment is made by user scanning, a mode (mode 3) in which authentication is performed using authentication conditions linked to the store when a store scan is performed, and a mode (mode 4) in which information indicating that the user has been authenticated is displayed on the user terminal 100 when payment is made by store scanning will be described.
[0025] (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 authenticating the user's age at the time of purchase, and a QR code Q2 for not authenticating the user's age 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 to be 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 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 (that is, the QR codes Q1 and Q2) are both linked in advance to an account (wallet) of the same store.
[0026] For example, a store clerk will present QR code Q1 when the user is purchasing a product that requires age verification, such as alcohol or tobacco, or when the group of products the user is purchasing includes products that require age verification. On the other hand, if the user is purchasing only 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 reads QR code Q1 installed in the store for payments that require age verification.
[0027] 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 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 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 predetermined condition regarding age restrictions is met based on the eKYC-completed user information (e.g., age) linked to the user identification information.
[0028] Then, when the user U1 is authenticated as a result of the age verification (i.e., when it is determined that the user U1 is a user who satisfies a predetermined condition), 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, when the payment server 10 is unable to authenticate the user, that is, when the user U1 is a user who does not satisfy the predetermined condition, the payment server 10 may not execute 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 user U1 reads the QR code Q2 and acquires the store identification information M2 (step S17). Then, the user terminal 100 transmits to the payment server 10 payment information indicating the user identification information, the store identification information M2, and the payment amount (step S18).
[0029] 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).
[0030] 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, the payment server 10 may authenticate the user, and if the flag is not included, the payment server 10 may not authenticate the user.
[0031] (Aspect 2) In the above example, the store identification information M1 associated with the authentication condition and the store identification information M2 not associated with the authentication condition are provided to the same store. However, the embodiment is not limited to this. For example, the store identification information M1 associated with the authentication condition and the store identification information M2 not associated with the authentication condition may be given to individual stores. In such a case, the store identification information M1 and M2 are associated with wallets of different stores.
[0032] For example, store A is provided with store identification information A that is linked to store A's wallet and authentication conditions, and store B is provided with store identification information B that is linked to store B's wallet and is not linked to authentication conditions. 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.
[0033] On the other hand, the payment server 10 determines whether or not an authentication condition is linked to the store identification information included in the payment information. For example, when the payment information includes store identification information A, the payment server 10 determines that the authentication condition is linked to the store identification information A. In such a case, the payment server 10 authenticates the user using the authentication condition linked to the store identification information A, and performs payment when the user is authenticated. On the other hand, when the payment information includes store identification information B, the payment server 10 determines that the authentication condition is not linked to the store identification information B. In such a case, the payment server 10 performs payment without performing authentication.
[0034] In this way, authentication conditions may be linked in advance to each store (more specifically, store identification information of each store). In this case, the payment server 10 judges whether authentication conditions are linked to each store, and if it is judged that they are linked, it performs payment processing after authenticating the user, and if it is judged that they are not linked, it performs payment processing without authenticating the user.
[0035] The store identification information may include a flag indicating whether or not the authentication condition is linked. When such a flag is included, the payment server 10 can determine whether or not to authenticate the user (i.e., whether or not the authentication condition is linked to the store identification information or the store) by referring to the store identification information.
[0036] (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).
[0037] When the payment server 10 receives the barcode request, it issues a one-time code, associates it with the user identification information, and transmits it to the user terminal 100 (step S22).
[0038] The user terminal 100 displays a barcode indicating the one-time code, and the store terminal 200 reads the barcode displayed on the user terminal 100 (step S23).
[0039] When the store terminal 200 reads the barcode, it transmits payment information including a one-time code (a one-time code linked to the user identification information), store identification information, and a payment amount to the payment server 10 (step S24).
[0040] Here, when the payment server 10 acquires the payment information from the user terminal 100, it determines whether 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 the store identification information is linked to the authentication condition, as in the first and second aspects, or may determine whether the store identification information includes a flag indicating whether to authenticate the user.
[0041] If the payment server 10 determines that the user should be authenticated, it authenticates the user (step S26), and performs the payment when the authentication is completed (step S27). After that, the payment server 10 transmits a notice that the payment has been completed to the store terminal 200 (step S28).
[0042] Here, unlike the user scan, in the case of the store scan 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 a predetermined condition.
[0043] 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 them to the POS server 300 (step S30). On the other hand, when the payment server 10 receives the payment ID together with the payment information, it uses the payment ID to acquire product information from the POS server 300 (step S31). The payment server 10 may also directly acquire product information of the product to be purchased, which is included in the payment information, from the POS server 300 when acquiring the payment information.
[0044] In such a case, the payment server 10 judges whether or not to authenticate the user based on the product information (step S25). If the payment server 10 judges that the product requires age verification as indicated by the product information, it judges whether or not the user U1 is a user who satisfies a predetermined condition (step S26). If the payment server 10 judges that the product does not require age verification, for example, it executes the payment process without performing age verification.
[0045] The payment server 10 determines that the product requires age verification, and if the age verification result indicates that the user U1 is authenticated (i.e., if the user U1 is determined to be a user who satisfies a predetermined condition), it executes the payment process (step S27). Note that if the payment server 10 determines that the age verification result indicates that authentication is not required, it does not execute the payment process.
[0046] 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).
[0047] As in the above-mentioned aspects 1 to 3, the payment server 10 judges whether or not the store identification information (store) is linked to the authentication condition, whether or not the store identification information includes whether or not authentication is to be performed, and whether or not the purchased item is a purchased item for which authentication is to be performed. That is, the payment server 10 judges whether or not to authenticate the user based on payment-related information such as the store identification information and the purchased item that can be acquired at the time of code payment. Furthermore, if it is determined that the user is to be authenticated, the payment server 10 authenticates the user. Then, the payment server 10 realizes the payment when the user is authenticated, and does not realize the payment when the user is not authenticated. As a result of such processing, the payment server 10 can smoothly realize the payment that requires authentication when the user needs to be authenticated in various situations.
[0048] (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 the fourth aspect, 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.
[0049] When user U1 purchases a product, user terminal 100 receives an operation from the user to display a barcode for store scanning (step S41). At this time, user terminal 100 receives 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 also receive a designation as to whether or not authentication of any other condition is to be performed, in addition to age authentication.
[0050] In such a case, the user terminal 100 transmits a request to display a barcode together with the designated content of age authentication to the payment server 10 (step S42). On the other hand, when there is an instruction to perform age authentication, the payment server 10 performs age authentication of the user who uses 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, when 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 when the user is 20 years old or younger, the payment server 10 transmits a one-time code not including a flag indicating that the user is 20 years old or older. On the other hand, when there is no instruction to perform age authentication, the payment server 10 transmits a one-time code not including a flag related to authentication. In addition, when execution of age authentication is designated and the designated condition of age authentication is not satisfied, the payment server 10 may display that the one-time code cannot be issued.
[0051] In such a case, the store terminal 200 can immediately obtain the authentication result of the user without transmitting 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 transmits 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 transmit the payment information to the payment server 10 and may display a message indicating that the payment cannot be made.
[0052] [1-4. Variations in Processing of the Embodiments] (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, 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, in addition to such age thresholds. 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.
[0053] (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 age confirmation and executes the payment process. However, for payment authentication, 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 eKYC on the store terminal 200, and the store clerk may confirm whether it 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, eKYC may store information such as address, telephone number, date of birth, and nationality, and the store clerk may perform confirmation using this information, and the payment server 10 may execute the payment process when the store clerk performs an operation to indicate that the confirmation is correct.
[0054] (Age verification using an interface) In the above embodiment (aspect 1), the case was shown where the store identification information M1 included in the payment information is referred to, 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 a condition for age authentication, the payment server 10 may display an interface for age confirmation 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" for 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 a response to the question "Are you 20 years old or older?". In addition, when the user selects "No" as a response 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 terminate 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 response. For example, the payment server 10 may assign an age condition confirmation flag to the payment history information of the user and store the response. 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 response. 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 response.
[0055] In the second embodiment, similarly to the first embodiment, the authentication of the user may be performed 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. Note that, when the user selects "No" as an answer to the question "Are you 20 years old or older", the payment server 10 may end the information processing without displaying the payment amount input screen. Also, the payment server 10 may display the payment amount input screen before the age verification screen. For example, when a user reads a store's QR code, the payment server 10 may cause a payment amount input screen to be displayed on the user terminal 100, and when an amount is entered into the payment amount input screen, an age verification screen may be displayed, and the payment process may be executed if the user selects "Yes" in response to the question "Are you over 20 years old?"
[0056] [2. Payment Server Configuration] 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.
[0057] (Communication Department 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.
[0058] (Storage 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.
[0059] The user identification information storage unit 31 stores user identification information. An example of information stored in the user identification information storage unit 31 will now 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".
[0060] "User ID" indicates identification information for identifying a user. "User identification information" indicates user identification information. "One-time code" indicates a one-time code issued when a request for a barcode for store scanning is accepted.
[0061] The store identification information storage unit 32 stores store identification information. An example of information stored in the store identification information storage unit 32 will now 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."
[0062] "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.
[0063] (Control unit 40) The control unit 40 is a controller, and is realized, for example, by a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) 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 ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). 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.
[0064] (Acquisition part 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 a 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.
[0065] 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 with 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 with a predetermined condition for age restriction.
[0066] Furthermore, 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 (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. Furthermore, the acquisition unit 41 acquires product information transmitted from the store terminal 200.
[0067] Furthermore, the acquiring unit 41 acquires information indicating a request for user identification information from the user terminal 100. Furthermore, the acquiring unit 41 acquires information indicating whether or not authentication of the user is required.
[0068] (Judgment unit 42) The determination unit 42 determines whether or not 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 makes the determination based on whether or not an authentication condition is associated with the store identification information. Also, for example, the determination unit 42 determines whether or not to authenticate the user based on whether or not the store identification information includes whether or not to perform authentication. Also, for example, the determination unit 42 makes the 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.
[0069] (Authentication section 43) The authentication unit 43 authenticates the user when the judgment unit 42 judges 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.
[0070] (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.
[0071] 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. 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.
[0072] (Notification section 45) The notification unit 45 notifies the user terminal 100 that payment is complete when payment processing is executed by the payment processing unit 44. For example, in the case of a user scan, the notification unit 45 notifies the user terminal 100 that payment is complete. Also, for example, in the case of a store scan, the notification unit 45 notifies the store terminal 200 that payment is complete.
[0073] [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.
[0074] (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.
[0075] (Input unit 120) The input unit 120 accepts various operations from a user. For example, the input unit 120 may accept various operations from a 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.
[0076] (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.
[0077] (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.
[0078] 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 operations described below.
[0079] (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.
[0080] (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.
[0081] [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.
[0082] (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.
[0083] (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.
[0084] (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.
[0085] (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 acquired 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.
[0086] 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 operations described below.
[0087] (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.
[0088] (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 a user.
[0089] [5. Information processing flow] The 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 the procedure of information processing according to the embodiment.
[0090] As shown in FIG. 10, the payment server 10 acquires user identification information, store identification information, and payment information (step S101).
[0091] The payment server 10 determines whether or not to authenticate the user (step S102).
[0092] When the payment server 10 determines to authenticate the user (step S102; YES), it authenticates the user and executes the payment if the authentication is successful (step S103). On the other hand, when the payment server 10 determines not to authenticate the user (step S102; NO), it executes the payment without authenticating the user (step S104).
[0093] 6. Effects As described above, the payment server 10 according to the embodiment has a determination unit 42, an authentication unit 43, and a payment processing unit 44. The determination unit 42 determines whether or not to authenticate the user in the payment based on payment-related information obtainable for the payment performed using the user terminal 100. The authentication unit 43 authenticates the user when it is determined that the user should be authenticated. When the user authentication is successful, the payment processing unit 44 executes the payment based on the payment-related information.
[0094] This allows the payment server 10 according to the embodiment to easily and accurately perform age verification and perform payment authentication.
[0095] Furthermore, the payment-related information is store identification information.
[0096] As a result, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication by acquiring the store identification information.
[0097] The determination unit 42 also determines whether or not an authentication condition is associated with the store identification information.
[0098] As a result, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication by acquiring the store identification information.
[0099] The determination unit 42 also determines whether or not the store identification information includes a command to perform authentication.
[0100] As a result, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication by acquiring the store identification information.
[0101] Furthermore, the determination unit 42 acquires the user identification information, the payment amount, and the store identification information from the user terminal 100, and makes a determination based on the store identification information.
[0102] As a result, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication when making a payment by user scanning.
[0103] Furthermore, the authentication unit 43 authenticates the user based on the user's response to an inquiry displayed on the screen of the user terminal as to whether or not the authentication condition associated with the store identification information is satisfied.
[0104] As a result, the payment server 10 according to the embodiment can perform authentication based on the feedback of the user, and therefore can perform authentication simply and accurately.
[0105] Furthermore, the determination unit 42 acquires the user identification information, the payment amount, and the store identification information from the store terminal 200, and makes a determination based on the store identification information.
[0106] As a result, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication when making a payment by store scanning.
[0107] In addition, the determination unit 42 further acquires product information of the product that is the object of payment, and if the product indicated by the acquired product information satisfies a predetermined condition, determines that authentication of the user is to be performed.
[0108] As a result, when making a payment by store scanning, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication based on predetermined conditions linked to the product information.
[0109] Furthermore, the authentication unit 43 authenticates the user based on whether or not the user satisfies an authentication condition associated with the store identification information.
[0110] As a result, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication by acquiring the store identification information.
[0111] Furthermore, the authentication unit 43 authenticates the user based on information that can identify the user.
[0112] As a result, the payment server 10 according to the embodiment can easily and accurately perform authentication by acquiring the user's identity verification information.
[0113] The payment-related information also includes condition identification information.
[0114] As a result, the payment server 10 according to the embodiment can easily and accurately perform age verification and perform payment authentication based on the store identification information and the condition identification information.
[0115] Furthermore, if authentication of the user fails, the payment processing unit 44 does not perform payment based on the payment-related information.
[0116] This allows the payment server 10 according to the embodiment to easily and accurately perform age verification and perform payment authentication.
[0117] [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.
[0118] The CPU 1100 operates and controls each unit based on a program stored in the ROM 1200 or the HDD 1400. The ROM 1200 stores a boot program executed by the CPU 1100 when the computer 1000 is started up, programs that depend on the hardware of the computer 1000, and the like.
[0119] The HDD 1400 stores programs executed by the CPU 1100, data used by such programs, etc. The communication interface 1500 receives data from other devices via a communication network 500 (corresponding to the network N in the embodiment) and sends the data to the CPU 1100, and also transmits data generated by the CPU 1100 to other devices via the communication network 500.
[0120] 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.
[0121] 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.
[0122] For example, when the computer 1000 functions as the payment server 10, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1300 to realize the function of the control unit 40. In addition, the HDD 1400 stores each 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 may obtain these programs from another device via a predetermined communication network.
[0123] [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 aspects described in the Disclosure of the Invention section.
[0124] Further, the above-mentioned payment server 10 can be flexibly changed in configuration, for example, by calling an external platform or the like using an API (Application Programming Interface) or network computing, depending on the function.
[0125] Furthermore, the term "unit" in the claims may be read as "means" or "circuit," etc. For example, an acquisition unit may be read as an acquisition means or an acquisition circuit. [Explanation of symbols]
[0126] 10 Payment Server 20 Communications Department 30 Storage section 31 User identification information storage unit 32 Store identification information storage unit 40 Control section 41 Acquisition Department 42 Judgment section 43 Authentication Section 44 Payment processing section 45 Notification Department 100 User terminals 110 Communications Department 120 Input section 130 Output section 140 Control section 141 Receiving unit 142 Transmitter 200 store terminals 210 Communications Department 220 Input section 230 Output section 240 Control Unit 241 Receiving unit 242 Transmitter
Claims
1. a determination unit that determines whether or not to perform age authentication of a user for a payment based on payment-related information that can be acquired for the payment performed using the user terminal; an authentication unit that, when the determination unit determines that age authentication of the user should be performed, performs age authentication of the user based on the age registered by the user in advance, and, when the determination unit determines that age authentication of the user should not be performed, does not perform age authentication of the user; a payment processing unit that executes the payment according to the payment-related information when the user's age is authenticated as a result of the age authentication by the authentication unit, or when the user's age is not authenticated by the authentication unit; A payment device comprising:
2. The payment-related information is store identification information.
2. The settlement device according to claim 1.
3. The determination unit The determination is made based on whether or not an age authentication condition is associated with the store identification information.
3. The settlement device according to claim 2.
4. The determination unit The determination is made based on whether the store identification information includes whether or not age authentication is required.
3. The settlement device according to claim 2.
5. The determination unit The user identification information, the payment amount, and the store identification information are acquired from the user terminal, and a determination is made based on the store identification information.
3. The settlement device according to claim 2.
6. The authentication unit The age of the user is authenticated based on the user's response to an inquiry displayed on the screen of the user terminal, the inquiry being an inquiry as to whether the user satisfies the age authentication condition associated with the store identification information.
6. The settlement device according to claim 5.
7. The determination unit The user identification information, the payment amount, and the store identification information are acquired from the store terminal, and a determination is made based on the store identification information.
3. The settlement device according to claim 2.
8. The determination unit Product information of the product to be paid for is further acquired, and if the product indicated by the acquired product information satisfies a predetermined condition, it is determined that age authentication of the user is to be performed.
8. The settlement device according to claim 7.
9. The authentication unit The age of the user is authenticated based on whether or not the age authentication condition associated with the store identification information is met.
3. The settlement device according to claim 2.
10. The authentication unit The age of the user is authenticated based on information that can verify the user's identity.
3. The settlement device according to claim 2.
11. The payment-related information includes condition identification information.
3. The settlement device according to claim 2.
12. The payment processing unit If the age authentication of the user fails, the payment based on the payment-related information will not be made.
2. The settlement device according to claim 1.
13. The payment is provided by an electronic payment service provider.
2. The settlement device according to claim 1.
14. The payment-related information is information including a payment amount.
2. The settlement device according to claim 1.
15. 1. A computer-implemented payment method comprising: a determination step of determining whether or not to perform age authentication of a user for a payment based on payment-related information obtainable for the payment performed using the user terminal; an authentication step of authenticating the user's age based on the user's pre-registered age when the determination step determines that the user's age should be authenticated, and not authenticating the user's age when the determination step determines that the user's age should not be authenticated; a payment processing step of executing the payment according to the payment-related information when the user's age is authenticated as a result of the age authentication in the authentication step, or when the user's age is not authenticated in the authentication step; A payment method comprising:
16. a determination step for determining whether or not to perform age authentication for a payment based on payment-related information obtainable for the payment performed using the user terminal; an authentication procedure in which, if it is determined by the determination procedure that age authentication of the user is to be performed, age authentication of the user is performed based on the age registered by the user in advance, and, if it is determined by the determination procedure that age authentication of the user is not to be performed, age authentication of the user is not performed; a payment processing procedure in which, as a result of the age authentication by the authentication procedure, the user's age is authenticated, or, if the user's age is not authenticated by the authentication procedure, the payment is executed according to the payment-related information; A payment program that causes a computer to execute the above.