Settlement management device, user terminal, settlement management method and display control method

Abstract

To provide a settlement management device, a user terminal, a settlement management method and a display control method for preventing a user receiving examination related to electronic settlement from withdrawing from settlement.SOLUTION: In a settlement system, a settlement management device 10 includes a start reception part for receiving first notification based on a start of a settlement application to be used for electronic settlement associated with at least one settlement account from a user terminal 20, an acquisition part for acquiring first information on the settlement account in the case of receiving the first notification, and a settlement processing part for executing settlement from the settlement account on the basis of a settlement code image displayed in the user terminal. The first information is information on an examination state of a use application to use a second account KU-2 as a settlement account. The settlement processing part executes settlement on the basis of a first settlement code image including information with a preregistered first account KU-1 as a settlement account in the case that the first information shows that examination to the use application of the second account KU-2 is not completed.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a payment management device, a user terminal, a payment management method, and a display control method. [Background technology]

[0002] Electronic payments (cashless payments) have become increasingly popular. In electronic payments, payment for goods or services is made by sending and receiving data indicating electronic monetary value (hereinafter referred to as "monetary data"), without the exchange of actual currency such as coins or banknotes (so-called cash). There are a variety of methods for converting currency held by users into monetary data, and in some cases, verification (such as identity verification) is required when using the system.

[0003] For example, in Patent Document 1 below, when contactless online payment using a credit card is specified in a store terminal device, a payment server determines whether contactless payment is enabled. If contactless payment is not enabled (more specifically, if the enablement is under review), the payment server notifies the store terminal device of this fact. The store terminal device displays a notification that the affiliated store is under review of whether to enable contactless payment. [Prior art documents] [Patent documents]

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

[0005] In electronic payments, a user may wish to switch between different payment methods. For example, assume that the user is able to use a first payment method (e.g., a payment using the first account as the payment account) and has applied to use a second payment method (e.g., a payment using the second account as the payment account) but is currently undergoing approval / disapproval. If the above-described conventional technology is applied to such a situation, when the user attempts to use the second payment method, a message will be displayed indicating that approval / disapproval of the second payment method is currently under review. Upon seeing this message, the user is likely to abandon the first payment method, even though it is available.

[0006] The present invention aims to prevent users who are undergoing screening regarding electronic payments from abandoning the payment process. [Means for solving the problem]

[0007] A payment management device according to one embodiment of the present invention comprises a reception unit that receives from a user terminal a first notification based on the launch of an application used for electronic payment linked to at least one payment account, an acquisition unit that acquires first information regarding the payment account when the first notification is received, and a payment processing unit that executes payment from the payment account based on a payment image displayed on the user terminal, wherein the first information is information regarding the review status of an application to use a second account as the payment account, and when the first information indicates that the review of the application to use the second account has not been completed, the payment processing unit executes payment based on a payment image including information specifying a pre-registered first account as the payment account.

[0008] A user terminal according to one embodiment of the present invention comprises a sending unit that sends a first notification to a payment management device based on the launch of an application used for electronic payment linked to at least one payment account, a receiving unit that receives second information regarding the payment account from the payment management device, and a display control unit that displays a payment image to request payment from the payment account from the payment management device, wherein the second information is information regarding the review status of an application to use a second account as the payment account, and when the second information indicates that the review of the application to use the second account has not been completed, the display control unit displays a payment image including information indicating that a pre-registered first account is the payment account.

[0009] A payment management method according to one embodiment of the present invention receives a first notification from a user terminal based on the launch of an application used for electronic payment linked to at least one payment account, and when the first notification is received, obtains first information regarding the payment account and executes payment from the payment account based on a payment image displayed on the user terminal, wherein the first information is information regarding the review status of an application to use a second account as the payment account, and when the first information indicates that the review of the application to use the second account has not been completed, executes payment based on a payment image including information specifying a pre-registered first account as the payment account.

[0010] A display control method according to one embodiment of the present invention sends a first notification to a payment management device based on the launch of an application used for electronic payment linked to at least one payment account, receives second information regarding the payment account from the payment management device, and displays a payment image to request payment from the payment account from the payment management device, wherein the second information is information regarding the review status of an application to use a second account as the payment account, and when the second information indicates that the review of the application to use the second account has not been completed, the payment image includes information specifying a pre-registered first account as the payment account. [Effects of the Invention]

[0011] According to one aspect of the present invention, a user undergoing screening regarding electronic payment can be prevented from abandoning payment. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a block diagram showing the configuration of a payment system 1 according to an embodiment. [Figure 2] FIG. 1 is a schematic diagram showing an overview of electronic payment. [Figure 3] FIG. 1 is a schematic diagram showing the transfer of electronic monetary value between accounts. [Figure 4] This is a table showing the differences between the first account KU-1 and the second account KU-2. [Figure 5] 10 is a flowchart showing the flow for opening a user account KU. [Figure 6A] FIG. 10 is a schematic diagram showing a user terminal 20 on which a payment code image is displayed. [Figure 6B] FIG. 10 is a schematic diagram showing an example of a deposit method selection screen. [Figure 6C] FIG. 10 is a schematic diagram showing an example of a message display screen during review. [Figure 7] 2 is a schematic diagram showing an example of the contents of a block list BL and personal information PD. FIG. [Figure 8] FIG. 2 is a schematic diagram showing an account database DB2. [Figure 9] FIG. 2 is a block diagram showing the configuration of a user terminal 20. [Figure 10] 1 is a block diagram showing the configuration of a payment management device 10. FIG. [Figure 11] 10 is a flowchart showing the operation of a processing device 103 of the payment management apparatus 10. DETAILED DESCRIPTION OF THE INVENTION

[0013] A. Embodiment A-1. System Configuration FIG. 1 is a block diagram showing the configuration of a payment system 1 according to an embodiment. The payment system 1 includes a payment management device 10 and multiple user terminals 20 (20-1 to 20-n, n is an integer equal to or greater than 2). The user terminals 20 are used by users U (U-1 to Un). Hereinafter, when there is no need to distinguish between the individual user terminals 20-1 to 20-n, they will be simply referred to as "user terminal 20." Furthermore, when there is no need to distinguish between the individual users U-1 to Un, they will be simply referred to as "user U." The payment management device 10 and each user terminal 20 are connected via a network N.

[0014] The payment management device 10 manages electronic payments using a user terminal 20. The payment management device 10 is installed, for example, by a payment service administrator who operates an electronic payment service. In this embodiment, the electronic payment service managed by the payment management device 10 may be referred to as "payment service D." The user terminal 20 is an information processing terminal such as a smartphone, tablet terminal, or personal computer. A payment application for using payment service D is installed on the user terminal 20.

[0015] A-2. Overview of electronic payments Figure 2 is a schematic diagram showing an overview of electronic payment. In this embodiment, the electronic payment handled by payment system 1 is assumed to be code payment. In the following embodiment, a case will be described in which user U uses code payment (electronic payment) when purchasing a product at a real store T, but code payment (electronic payment) can also be used for shopping at a virtual store on the Internet (online shopping), for example.

[0016] 2 shows a user U, a user terminal 20, a payment management device 10, a store terminal 30, and a store T. The store terminal 30 is installed in the store T and is a terminal that manages the exchange of money at the store T. The store terminal 30 may be, for example, a POS (Point of Sale) terminal, or may be a system in which a POS terminal and a computer for electronic payment are connected.

[0017] There are two methods for code payment: a first method in which the store terminal 30 reads a payment code image displayed on the display device 201 of the user terminal 20, and a second method in which the user terminal 20 reads a payment code posted in front of the store T. In this embodiment, we will mainly explain the case where the payment code is read using the first method.

[0018] First, the details of the first method will be explained. When making a payment at store T, user U launches a payment application. When the payment application is launched, user terminal 20 (more specifically, launch request unit 211, described later; see FIG. 9) sends a request to issue a one-time code to payment management device 10 (S10). The request includes, for example, a user ID that identifies user U in an electronic payment service. Payment management device 10 (more specifically, first display control unit 115, described later; see FIG. 10) generates a one-time code and sends it to user terminal 20 (S11).

[0019] The user terminal 20 (more specifically, the second display control unit 214 described later; see Figure 9) generates a payment code (which in this embodiment is a barcode) based on the one-time code and displays the payment code image on the display device 201.

[0020] Fig. 6A is a schematic diagram showing a user terminal 20 on which a payment code image is displayed. Display device 201 of user terminal 20 shown in Fig. 6A displays a barcode N1 (payment code image) generated based on the one-time code, a point balance N2 indicating the balance of points granted to user U for using payment service D, a point usage switching interface N3 for switching whether or not points are used when making a payment, a reading icon N4 for reading the code using a second method described below, a charge icon N5 for charging the balance to user account KU, and a usage history icon N6 for checking the usage history of payment service D.

[0021] When user U presents user terminal 20 displaying barcode N1, a store clerk at store T reads barcode N1 with an optical reader in store terminal 30 (S12). Store terminal 30 decodes the barcode and obtains a one-time code. Store terminal 30 generates payment information including the one-time code, payment amount, store ID, etc., and transmits it to payment management device 10 (S13).

[0022] As shown in FIG. 3, the payment management device 10 manages a user account KU in which electronic monetary value held by a user U is saved, and a store account KT in which electronic monetary value held by a store T is saved. The payment management device 10 executes a payment process to transfer electronic monetary value equivalent to the payment amount from the user account KU to the store account KT. More specifically, the payment management device 10 identifies a user ID based on a one-time code included in the payment information, and identifies the user account KU corresponding to the user ID. The payment management device 10 also identifies the store account KT based on the store ID included in the payment information. The payment management device 10 then transfers electronic monetary value equivalent to the payment amount from the user account KU corresponding to the user ID to the store account KT.

[0023] When the payment process is completed, the payment management device 10 transmits a payment completion notification indicating that the payment has been completed to the user terminal 20 and the store terminal 30 (S14).

[0024] Next, the second method will be described. When making a payment at store T, user U launches the payment application and taps the reading icon N4 shown in FIG. 6A. Tapping the reading icon N4 launches the camera 203 of the user terminal 20 (see FIG. 9). User U captures an image of the payment code posted in store T with the camera 203. The user terminal 20 (more specifically, the payment request unit 212 described later; see FIG. 9) decodes the payment code captured by the camera 203 and converts it into a store URL (Uniform Resource Locator) that identifies the store. The store URL is the domain of the electronic payment service to which information that can identify the store has been added. The store URL is associated in the payment management device 10 with a store ID or the like that identifies store T (or store terminal 30).

[0025] The user terminal 20 (more specifically, the payment request unit 212 described later; see FIG. 9) transmits the read store URL and the user ID that identifies user U in the electronic payment service to the payment management device 10. The payment management device 10 (more specifically, the payment processing unit 112 described later; see FIG. 10) searches for store information such as the store name from the store ID corresponding to the store URL and transmits the store information to the user terminal 20. The user terminal 20 displays the store information and an input interface for inputting the payment amount. User U checks the store information displayed on the user terminal 20 to confirm that store T, the payment destination, is correct. User U also inputs the payment amount into the input interface and presses the confirm button. The user terminal 20 (more specifically, the payment request unit 212 described later; see FIG. 9) transmits the input payment amount to the payment management device 10.

[0026] The payment management device 10 (more specifically, the payment processing unit 112 described later; see FIG. 10) executes payment processing to transfer electronic monetary value equivalent to the payment amount from the user account KU to the store account KT. When the payment processing is completed, the payment management device 10 (more specifically, the payment processing unit 112 described later; see FIG. 10) transmits a payment completion notification to the user terminal 20 and the store terminal 30, indicating that the payment has been completed.

[0027] FIG. 3 is a schematic diagram showing the transfer of electronic monetary value between accounts. In this embodiment, the electronic monetary value is in the same units as the currency of the applicable region of payment service D. As an example, a case will be described in which the applicable region of payment service D is Japan and the currency is the yen. As described above, user account KU stores electronic monetary value held by user U. When payment management device 10 executes payment processing (transfer of electronic monetary value from user account KU to store account KT), the balance of user account KU decreases by the payment amount, and the balance of store account KT increases.

[0028] Here, there are two types of user accounts KU: a first account KU-1 and a second account KU-2. The user account KU of one user U is either the first account KU-1 or the second account KU-2. In other words, the code payment according to this embodiment is linked to at least one payment account. In this embodiment, a payment when the user account KU is the first account KU-1 is called a "first payment," and a payment when the user account KU is the second account KU-2 is called a "second payment." In other words, the first payment is a payment funded by the balance of the first account KU-1, and the second payment is a payment funded by the balance of the second account KU-2.

[0029] The first account KU-1 is an account that does not require identity verification when opening. On the other hand, the second account KU-2 is an account that requires identity verification when opening. In other words, an application to use the first account KU-1 does not require identity verification of the user U, but an application to use the second account KU-2 requires identity verification of the user U. Note that an application to use includes not only opening a new account but also changing the type of account (in this embodiment, changing from the first account KU-1 to the second account KU-2).

[0030] Identity verification is the process of verifying whether the personal information PD, such as the name and address, submitted by the user U when opening a user account KU is valid using a photo-bearing identification document, such as a driver's license, My Number card, or passport. Specifically, for example, the user U takes a photo of the identification document and a photo of their own face using the camera 203 of the user terminal 20 and sends them to the payment management device 10. The payment management device 10 determines whether the personal information PD submitted by the user U when opening the user account KU matches the personal information PD written on the identification document. The payment management device 10 also determines whether the photo on the identification document matches the photo sent by the user U. If both the personal information PD and the photo match, the result of identity verification is "OK," and identity verification is completed. On the other hand, if at least one of the personal information PD and the photo does not match, the result of identity authentication is "NG," and, for example, the user is requested to submit additional documents, or the opening of the user account KU is denied.

[0031] Furthermore, when opening a user account KU, a check is performed (hereinafter referred to as a "list check") to determine whether the user U is listed on the block list BL, separate from the identity verification. In this embodiment, the block list BL contains information on individuals who belong to anti-social forces. Alternatively, the block list BL may be a list of individuals with a history of financial mishaps, such as late credit card payments. If the personal information PD of the user U (at least one of the personal information PD submitted by the user U when opening the user account KU and the personal information PD listed on the identity verification document) matches (completely or partially matches) the information of a person listed on the block list BL, it is determined that the user U may be a person listed on the block list BL, and the opening of the user account KU is denied. If the personal information PD of the user U does not match the information of a person listed on the block list BL, it is determined that the user U is not a person listed on the block list BL, and the opening of the user account KU is permitted.

[0032] Figure 4 is a table showing the differences between the first account KU-1 and the second account KU-2. Figure 4 shows an excerpt of the functions of the user account KU. As mentioned above, a request to use the first account KU-1 does not require identity verification of the user U, but a request to use the second account KU-2 does require identity verification of the user U.

[0033] The differences in the deposit methods for the first account KU-1 and the second account KU-2 will now be explained. As shown in Figure 3, only cash CA deposits are possible for the first account KU-1. Deposits by cash CA and deposits from user U's bank account BK are possible for the second account KU-2. Deposits by cash CA are an example of deposits by prepayment. Deposits from user U's bank account BK are an example of deposits by fund transfer. In other words, the first payment is a payment sourced from the balance of the first account KU-1, which only allows deposits by prepayment, and the second payment is a payment sourced from the balance of the second account KU-2, which allows deposits by prepayment and fund transfer.

[0034] To deposit cash CA, for example, an ATM of a bank or other institution affiliated with payment service D (hereinafter referred to as an "affiliated ATM") is used. User U can select the menu "Transaction using user terminal 20" at the affiliated ATM. When "Transaction using user terminal 20" is selected, a two-dimensional code is displayed on the display screen of the affiliated ATM. When user U selects charge icon N5 on the payment application, a deposit method selection screen shown in Figure 6B is displayed. When user U selects "Deposit from affiliated ATM" (icon N11) as the deposit method, camera 203 starts up and the two-dimensional code can be read. When the two-dimensional code displayed on the affiliated ATM is read, a one-time password is displayed on the payment application. When user U enters the one-time password into the affiliated ATM, the coin insertion mechanism of the affiliated ATM opens and depositing money becomes possible.

[0035] Depositing money from bank account BK is a method of depositing money from bank account BK held by user U to user account KU of payment service D. When user U selects charge icon N5 on the payment application, a deposit method selection screen shown in FIG. 6B is displayed. When user U selects "Deposit from bank account BK" (icon N12) as the deposit method, an input screen for bank name, account number, PIN, etc. is displayed. Once user U enters information on the input screen and authentication by the bank is completed, depositing money from bank account BK to user account KU (more specifically, converting the currency in bank account BK into electronic monetary value and depositing it into user account KU) becomes possible. Note that if "Deposit from bank account BK" (icon N12) is selected for the second or subsequent time, input of bank name, account number, PIN, etc. may be omitted.

[0036] FIG. 6B is a schematic diagram showing an example of a deposit method selection screen. As described above, when user U taps the charge icon N5 on the screen shown in FIG. 6A, the deposit method selection screen shown in FIG. 6B is displayed. The deposit method selection screen displays an icon N11 for designating deposit from an affiliated ATM and an icon N12 for designating deposit from bank account BK. When user U selects (tap) the icon N11 or N12 corresponding to the desired deposit method, the deposit process is carried out according to the above procedure.

[0037] As one mode of depositing money from bank account BK, it is also possible to set up so-called auto-charge, in which money is automatically deposited from bank account BK to user account KU when a predetermined condition is met. The predetermined condition is, for example, when the balance of user account KU falls below a predetermined amount.

[0038] Next, we will explain the differences in withdrawal methods from the first account KU-1 and the second account KU-2. From the first account KU-1, only payments (payments from the account balance) at the above-mentioned store T, etc. are possible. On the other hand, from the second account KU-2, in addition to payments at store T, etc., it is also possible to withdraw cash CA using affiliated ATMs, etc., and to transfer money between users or to companies using payment service D. It is possible to receive money transfers from another user U using payment service D to the first account KU-1.

[0039] In this way, the functions of the first account KU-1 are limited compared to the second account KU-2, because, as mentioned above, the first account KU-1 does not require identity verification when applying for use, while the second account KU-2 does require identity verification when applying for use.

[0040] When opening a new user account KU, the user U can select whether the user account KU to be opened will be the first account KU-1 or the second account KU-2. After the user U opens the first account KU-1 as the user account KU, the user U can change the type of the user account KU to the second account KU-2.

[0041] 5 is a flowchart showing the process for opening a user account KU. When the user U wishes to open a user account KU (step S100: YES), the payment management device 10 (more specifically, the account processing unit 111; see FIG. 10; the same applies below) confirms whether the user U wishes to open a first account KU-1 or a second account KU-2 (step S102).

[0042] If the user U wishes to open the first account KU-1 (step S102: YES), the payment management device 10 requests the user U to input personal information PD, and performs a list check by comparing the input personal information PD with the block list BL (step S102). If the list check results in no problems (step S103: YES, "list check OK"), the first account KU-1 is opened for the user U (step S104). On the other hand, if the list check results in a problem (step S103: NO, "list check NG"), the opening of the user account KU is rejected (step S108), and the processing of this flowchart ends.

[0043] Furthermore, if the user U wishes to open a second account KU-2 (step S102: NO), the payment management device 10 requests the user U to enter personal information PD and submit identity verification documents, and performs a list check by comparing the personal information PD and identity verification documents with the block list BL (step S105). If there are no problems with the identity verification and list check results (step S106: YES, "identity verification and list check OK"), the second account KU-2 is opened for the user U (step S107), and the processing of this flowchart ends. On the other hand, if there are problems with at least one of the identity verification and list check results (step S106: NO, "identity verification and list check NG"), the opening of the user account KU is rejected (step S108), and the processing of this flowchart ends.

[0044] After the first account KU-1 is opened in step S104, if the user U wishes to change the account to the second account KU-2 (step S109: YES), the payment management device 10 requests the user U to submit personal identification documents and performs another list check based on the personal identification documents (step S110). If there are no problems with the results of the personal identification and list check (step S111: YES, "personal identification and list check OK"), the user account KU is changed to the second account KU-2 (step S112), and the processing of this flowchart ends. On the other hand, if there are problems with the results of at least one of the personal identification and list check (step S111: NO, "personal identification and list check NG"), the change to the second account KU-2 is rejected, the user account KU is frozen (step S113), and the processing of this flowchart ends.

[0045] Here, the identity verification performed in steps S105 and S110 will be described in detail. Identity verification is generally performed in two stages: an automatic check by a computer and a visual check by an employee of the operator of payment service D. More specifically, information represented by text, such as name, address, and date of birth, is entered as text into user terminal 20 when opening user account KU. Furthermore, payment management device 10 applies OCR (Optical Character Reader) to the photo of the identity verification document to convert the information written on the identity verification document into text. The payment management device 10 compares these two texts to authenticate user U's personal information PD. Regarding the face photo, for example, AI (Artificial Intelligence) is used to determine whether the two face photos (the face photo on the identity verification document and the face photo sent by user U) are of the same person.

[0046] If both the personal information PD and the facial photograph match, the automatic computer check returns "OK" and identity verification is complete. On the other hand, if at least one of the personal information PD and the facial photograph does not match, the automatic computer check returns "NG" and a visual check is performed by an employee of the operator of payment service D. If the visual check finds no problems (for example, if there is an error in text recognition by OCR), the visual check result returns "OK" and identity verification is complete. If the problem cannot be resolved even after the visual check, identity verification ultimately returns "NG." In this case, for example, user U may be asked to submit additional documents or the opening of user account KU may be denied.

[0047] Next, details of the list checks performed in steps S102, S105, and S110 will be described. List checks are performed not only when (1) a user account KU is opened and (2) when the account type of the user account KU is changed (when the first account KU-1 is changed to the second account KU-2) as described above, but also when, for example, (3) the block list BL is updated and (4) the personal information PD of user U is changed.

[0048] Figure 7 is a schematic diagram showing an example of the contents of the block list BL and personal information PD. The block list BL shown in Figure 7 records the name (kanji) 501, alternate name (kanji) 502, name (kana) 503, alternate name (kana) 504, date of birth 505, and address 506 of persons belonging to anti-social forces. Furthermore, the personal information PD entered by user U when opening a user account KU is assumed to be name (kanji) 601, name (kana) 602, date of birth 603, and address 604.

[0049] In the list check, a match is made between the personal information PD of user U and the information in the block list BL. The list check is carried out in two stages: an automatic check by computer and a visual check by an employee of the operator of payment service D. If the automatic check finds that there are more than a predetermined number of matching items, user U will be subject to a visual check.

[0050] In the automatic check, the name (Kanji) 601 in the personal information PD is compared with the name (Kanji) 501 and the alternate name (Kanji) 502 in the block list BL, and if there is a partial match between the name (Kanji) 601 and the name (Kanji) 501, or between the name (Kanji) 601 and the alternate name (Kanji) 502, the name (Kanji) is determined to be a matching item. Note that, in the comparison, the old and new characters may be considered to be the same characters.

[0051] Furthermore, the automatic check compares the name (kana) 602 in the personal information PD with the name (kana) 503 and alternate name (kana) 504 in the block list BL, and if there is a partial match between the name (kana) 602 and the name (kana) 503, or between the name (kana) 602 and alternate name (kana) 504, the name (kana) is deemed to be a matching item. Note that if the kana is written in alphabetic characters, a difference of three characters or less may be deemed to be a "match."

[0052] Furthermore, in the automatic check, the date of birth 603 in the personal information PD is compared with the date of birth 505 in the block list BL, and if the date of birth 603 and the date of birth 505 are an exact match, the date of birth is determined to be a matching item.

[0053] Furthermore, the automatic check compares address 604 in personal information PD with address 506 in block list BL, and if there is a partial match between address 604 and address 506, the address is determined to be a matching item. For example, address 604 and address 506 may be indicated by city / town / village codes, and if the first eight digits of the city / town / village code match, it may be determined to be a "partial match."

[0054] Furthermore, if the result of the automatic check is, for example, two or fewer matching items for user U, the list check result will be "OK." If the result of the automatic check is, for example, three or more matching items for user U, the list check result will be "OK." In the visual check, an employee of the payment service operator visually compares user U's personal information PD with the block list BL. If the result of the visual check determines that user U is highly likely to be a person listed on the block list BL, the list check result will be "NG." If the result of the visual check determines that user U is highly likely not to be a person listed on the block list BL, specifically if there is a data error or a system error, the error will be corrected and the list check result will be "OK."

[0055] Generally, identity verification and list checks are completed in a very short time (for example, a few seconds to several tens of seconds) by automatic checks performed by a computer (the payment management device 10 in this embodiment). Therefore, steps S102, S105, and S110 in FIG. 5 are completed in a very short time, and from the perspective of user U, the processing is completed immediately. On the other hand, if a visual check is performed, it may take, for example, several days. During this time, identity verification and list checks are considered "under review."

[0056] In this way, the screening of the application to use the second account KU-2 includes a list check that compares information about people belonging to anti-social organizations (block list BL) with user U's personal information PD.

[0057] A-3. User terminal 20 9 is a block diagram showing the configuration of user terminal 20. User terminal 20 includes display device 201, input device 202, camera 203, communication device 204, storage device 205, processing device 206, and bus 220 interconnecting these devices.

[0058] The display device 201 is a display device (for example, various display panels such as a liquid crystal display panel or an organic EL display panel) that displays information to the outside. The input device 202 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, or a sensor) that receives input from the outside. The display device 201 and the input device 202 may be integrated into one device (for example, a touch panel).

[0059] The camera 203 generates an image of the space around the user terminal 20. In this embodiment, the camera 203 is mainly used to read a payment code in code payment. The camera 203 has an imaging optical system and an imaging element. The imaging optical system is an optical system including at least one imaging lens. The imaging optical system may have various optical elements such as a prism, or may have a zoom lens or a focus lens. The imaging element is, for example, a CCD (Charge Coupled Device) image sensor or a CMOS (Complementary MOS) image sensor.

[0060] The communication device 204 has an interface connectable to the network N, and communicates with other devices connected to the network N using wireless or wired communication.

[0061] The storage device 205 is a recording medium readable by the processing device 206. The storage device 205 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory). The volatile memory is, for example, a RAM (Random Access Memory). The storage device 205 stores a program PG2. The program PG2 is a program for operating the user terminal 20.

[0062] The storage device 205 also stores a display data group HD used for screen display in the payment application. The display data group HD includes, for example, multiple pieces of image data and text data. Each piece of image data and text data is assigned a display data ID. The second display control unit 214, which will be described later, causes the display device 201 to display, as part of the payment application, at least one of the image data and text data corresponding to a display data ID specified by, for example, the payment management device 10.

[0063] The processing device 206 includes one or more central processing units (CPUs). The one or more CPUs are examples of one or more processors. Each of the processor and the CPU is an example of a computer.

[0064] Processing device 206 reads program PG2 from storage device 205. By executing program PG2, processing device 206 functions as start-up request unit 211, payment request unit 212, account request unit 213, and second display control unit 214. Start-up request unit 211, payment request unit 212, account request unit 213, and second display control unit 214 may be configured with circuits such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). In this embodiment, start-up request unit 211, payment request unit 212, account request unit 213, and second display control unit 214 are realized as functions of a payment application.

[0065] The activation request unit 211 sends a first notification to the payment management apparatus 10 when a payment application is activated by user U. The activation request unit 211 sends the first notification to the payment management apparatus 10 based on the activation of a payment application used for electronic payment linked to at least one payment account. The activation request unit 211 is an example of a transmission unit. The first notification is a notification indicating that a payment application has been activated on the user terminal 20. The first notification includes, for example, a user ID that identifies user U in payment service D. In response to the first notification, a one-time code is sent from the payment management apparatus 10 (more specifically, the first display control unit 115). The second display control unit 214, which will be described later, causes the display device 201 to display a payment code image (e.g., a barcode N1) generated using the one-time code.

[0066] When the payment code is read using the second method (when the payment code posted in front of store T is read by the user terminal 20), the payment request unit 212 requests the payment management device 10 to perform payment processing to transfer electronic monetary value from the user account KU to the store account KT, etc. When the payment code is read using the first method (when the payment code image displayed on the user terminal 20 is read by the store terminal 30), the payment request unit (not shown) of the store terminal 30 requests the payment management device 10 to perform payment processing.

[0067] The account request unit 213 makes a request regarding a user account KU to the payment management apparatus 10. A request regarding a user account KU is, for example, a request to open a user account KU, a request to change the type of the user account KU, and a request to change the personal information PD of a user U associated with the user account KU.

[0068] The second display control unit 214 controls the display on the display device 201 of the user terminal 20. The second display control unit 214 generates a payment code image (e.g., barcode N1) based on display control information transmitted from, for example, the payment management device 10, and displays it on the display device 201. The second display control unit 214 also obtains display data corresponding to a display data ID transmitted from, for example, the payment management device 10 from the display data group HD, and displays it on the display device 201.

[0069] In this embodiment, the second display control unit 214 has the functions of a receiving unit that receives second information about the payment account from the payment management device 10, and a display control unit that displays a payment code image for requesting payment from the payment account to the payment management device 10. The second information is information about the status of the review of the application to use the second account KU-2 as a payment account. Details of these functions will be described later.

[0070] A-4. Payment management device 10 10 is a block diagram showing the configuration of the payment management apparatus 10. The payment management apparatus 10 includes a communication device 101, a storage device 102, a processing device 103, and a bus 109 that interconnects these devices.

[0071] The communication device 101 has an interface connectable to a network N, and communicates with other terminals connected to the network N using wireless or wired communication.

[0072] The storage device 102 is a recording medium readable by the processing device 103. The storage device 102 includes, for example, a non-volatile memory and a volatile memory. The non-volatile memory is, for example, a ROM, an EPROM, and an EEPROM. The volatile memory is, for example, a RAM. The storage device 102 stores a program PG1. The program PG1 is a program for operating the payment management device 10. The storage device 102 also stores a block list BL (see FIG. 7), a user database DB1, and an account database DB2. The user database DB1 stores personal information PD (see FIG. 7) entered by the user U when opening the user account KU.

[0073] FIG. 8 is a schematic diagram showing the account database DB2. The account database DB2 stores a user ID 701, a user account KU type 702, a user account KU balance 703, and a withdrawal and deposit history 704. The user account KU type 702 indicates, for example, "first account KU-1," "second account KU-2," "under review," or "rejected." "First account KU-1" indicates that the user account KU is the first account KU-1. "Second account KU-2" indicates that the user account KU is the second account KU-2. "Under review" indicates that a request to change the type of the user account KU from the first account KU-1 to the second account KU-2 is under review (mainly during the visual check described above). "Rejected" indicates that the change request was rejected as a result of the review. In the case of "rejected," for example, the user account KU is frozen, and user U cannot use code payment.

[0074] The user database DB1 and the account database DB2 may be integrated into one database.

[0075] The processing device 103 includes one or more CPUs. The one or more CPUs are an example of one or more processors. Each of the processor and the CPU is an example of a computer. By executing the program PG1, the processing device 103 functions as an account processing device 111, a payment processing device 112, a start-up reception device 113, an acquisition device 114, and a first display control device 115. At least some of these functions may be configured by circuits such as a DSP, an ASIC, a PLD, and an FPGA.

[0076] The account processing unit 111 performs processing related to a user account KU. Processing related to a user account KU is processing requested by the account request unit 213 of the user terminal 20. Specifically, processing related to a user account KU includes, for example, opening a user account KU, changing the type of user account KU, and changing the personal information PD of a user U associated with the user account KU. When changing the type of a user account KU, the account processing unit 111 performs the automatic check by a computer described above. If the check is not completed by the automatic check, a visual check is performed by an employee or the like. Furthermore, when the type of a user account KU is changed, the account processing unit 111 updates the content of the user account KU type 702 in the account database DB2. Furthermore, when a visual check by an employee or the like is performed, the account processing unit 111 sets the user account KU type 702 in the account database DB2 to "under review."

[0077] The payment processing unit 112 executes payment processing to transfer electronic monetary value from the user account KU to the store account KT, etc. In this embodiment, the payment processing unit 112 performs code payment using a payment code image. Therefore, it can be said that the payment processing unit 112 executes payment from the payment account based on the payment code image displayed on the user terminal 20. The payment processing unit 112 executes payment processing based on a request from, for example, the payment request unit 212 of the user terminal 20 or a payment request unit (not shown) of the store terminal 30. Furthermore, when the payment processing is completed, the payment processing unit 112 transmits a payment completion notification to the user terminal 20 and the store terminal 30, indicating that the payment has been completed.

[0078] The activation reception unit 113 receives a first notification regarding the activation of a payment application from a user terminal 20 on which a payment application used for code payment is installed. The activation reception unit 113 is an example of a reception unit. As described above, the first notification is a notification sent from the user terminal 20 when the payment application is activated on the user terminal 20, and includes, for example, a user ID.

[0079] When the activation reception unit 113 receives the first notification, the acquisition unit 114 acquires type information indicating the type of user account KU corresponding to the user ID. In this embodiment, the acquisition unit 114 refers to the account database DB2 and identifies a record in which the user ID written in the user ID 701 matches the user ID included in the first notification. Then, the acquisition unit 114 refers to the user account KU type 702 of the record and acquires one of "first account KU-1," "second account KU-2," "under review," or "rejected" as the type information.

[0080] The first display control unit 115 generates display control information for controlling the display on the display device 201 of the user terminal 20 and transmits it to the user terminal 20. The first display control unit 115 generates the display control information based on the first information acquired by the acquisition unit 114, for example. When the type information is "first account KU-1" and "second account KU-2", the first display control unit 115 generates display control information for displaying on the user terminal 20-1 a payment code image corresponding to a payment using the user account KU as the payment account.

[0081] More specifically, when the type information is "first account KU-1," the user account KU is the first account KU-1, and therefore the display control information can be said to be information for displaying on the user terminal 20 a first payment code image corresponding to a payment using the first account KU-1 as the payment account. When the type information is "second account KU-2," the user account KU is the second account KU-2, and therefore the display control information can be said to be information for displaying on the user terminal 20 a second payment code image corresponding to a payment using the second account KU-2 as the payment account. The display control information for displaying the payment code image on the user terminal 20-1 includes, for example, a one-time code for payment and control information that instructs the user terminal 20 to generate a payment code image and display it on the display device 201. The first payment code image and the second payment code image may be substantially the same image.

[0082] Furthermore, if the type information is "under review," the user account KU is still the first account KU-1, and therefore the first display control unit 115 generates display control information for displaying on the user terminal 20 a first payment code image corresponding to the payment using the first account KU-1 as the payment account. If the type information is "rejected," the first display control unit 115 generates display control information for displaying on the user terminal 20 a message indicating that the change in the type of the user account KU has been rejected. This message may be stored, for example, in the display data group HD (see FIG. 9) stored in the user terminal 20. In this case, the first display control unit 115 transmits to the user terminal 20 a display data ID corresponding to the message indicating that the change in the type of the user account KU has been rejected.

[0083] Here, the functions of the activation reception unit 113, the acquisition unit 114, and the first display control unit 115 will be specifically described using a user U-1 who is an example of a user U, and a user terminal 20-1 (an example of a user terminal 20) held by the user U-1. After opening a user account KU as a first account KU-1, the user U-1 applies for use of a second account KU-2.

[0084] When a payment application is launched on user terminal 20-1, launch acceptance unit 113 accepts a first notification sent from user terminal 20-1. In other words, launch acceptance unit 113 accepts a first notification based on the launch of a payment application used for electronic payment linked to at least one payment account from user terminal 20. Launch acceptance unit 113 is an example of a acceptance unit.

[0085] The acquisition unit 114 refers to the account database DB2 and acquires type information of the user account KU of user U-1 (the user account KU corresponding to the user ID included in the first notification). Because user U-1 is applying to use the second account KU-2, the type information acquired at this time can be said to be first information indicating the review status of the application. In other words, when the activation acceptance unit 113 accepts the first notification from the user terminal 20-1, the acquisition unit 114 acquires first information related to the payment account. The first information is information related to the review status of the application to use the second account KU-2 as a payment account. The first information is either "under review," "second account KU-2," or "rejected."

[0086] The first display control unit 115 generates display control information based on the first information (an example of type information) acquired by the acquisition unit 114. For example, if the first information indicates "under review," the user account KU is still the first account KU-1, and therefore the first display control unit 115 generates display control information for displaying, on the user terminal 20-1, a first payment code image corresponding to a payment using the first account KU-1 as the payment account. In other words, if the first information acquired by the acquisition unit 114 indicates that the application for use of the second account KU-2 is "under review," the first display control unit 115 causes the user terminal 20-1 to display a first payment code image corresponding to a payment using the first account KU-1 as the payment account. The user terminal 20-1 displaying the first payment code image is, for example, the user terminal 20 shown in FIG. 6A. In FIG. 6A, the first payment code image corresponds to the barcode N1.

[0087] When user U-1 makes a payment (settlement) at store T or the like using the first payment code image, the payment processing unit 112 will make the settlement using first account KU-1 as the settlement account. In other words, if the first information indicates that the review of the application to use second account KU-2 has not been completed, the payment processing unit 112 will execute the settlement based on the first payment code image including information that specifies pre-registered first account KU-1 as the settlement account.

[0088] When viewed from the user terminal 20, the above processing can be said to be second information regarding the status of the review of the application to use the second account KU-2 as a payment account. The display control information for displaying the first payment code image on the user terminal 20-1 is an example of second information indicating that the review of the application to use the second account KU-2 has not been completed. When the second information indicates that the review of the application to use the second account KU-2 has not been completed, the second display control unit 214 of the user terminal 20 will display a payment code image including information specifying the pre-registered first account KU-1 as the payment account.

[0089] Furthermore, for example, if the first information is "second account KU-2," the user account KU has been changed to the second account KU-2, and therefore the first display control unit 115 generates display control information for displaying on the user terminal 20-1 a second payment code image corresponding to a payment using the second account KU-2 as the payment account. In other words, if the first information indicates that use of the second account KU-2 has been approved, the first display control unit 115 causes the user terminal 20-1 to display a second payment code image corresponding to a payment using the second account KU-2 as the payment account. Note that if the change to the second account KU-2 is approved, a notification to that effect (which may be a notification on the payment application or may be by email, etc.) may be sent to the user terminal 20-1. Furthermore, if the payment application is launched for the first time after the change to the second account KU-2 has been approved, a dialog message such as "The change to the second account has been completed" may be displayed before the second payment code image is displayed.

[0090] When user U-1 makes a payment (settlement) at store T or the like using the second payment code image, the payment processing unit 112 will make the payment using second account KU-2 as the payment account. In other words, when the first information indicates that use of second account KU-2 has been approved, the payment processing unit 112 executes the payment based on the second payment code image including information specifying second account KU-2 as the payment account.

[0091] Furthermore, for example, if the first information is "rejected," the first display control unit 115 generates display control information for displaying a message indicating that the change of the type of user account KU has been rejected on the user terminal 20-1. An example of a message indicating that the change of the type of user account KU has been rejected is, for example, "As a result of the screening, we regret to inform you that payment service D cannot be used." At this time, the message may include contact information for an inquiry desk that accepts inquiries from user U-1. Note that if the change to the second account KU-2 is rejected, a notification to that effect (which may be a notification on the payment application, or may be an email, etc.) may be sent to the user terminal 20-1.

[0092] Next, a case will be described in which user U-1 selects to deposit money from bank account BK when the first information is "under review." As described above, when the first information is "under review," a screen including a first payment code image (barcode N1) is displayed on user terminal 20-1 as shown in FIG. 6. In this state, user U-1 taps charge icon N5 and then selects icon N12 corresponding to "deposit money from bank account BK." In this case, activation reception unit 113 receives a second notification from user terminal 20-1 indicating that user U-1 has selected icon N12.

[0093] As described above, the first account KU-1 cannot be deposited from the user U's bank account BK, but the second account KU-2 can be deposited from the user U's bank account BK. Icon N12 corresponds to the function of depositing money from the user U's bank account BK to the second account KU-2. In other words, icon N12 is an icon corresponding to a function that cannot be executed on the first account KU-1 but can be executed on the second account KU-2.

[0094] When the activation reception unit 113 receives the second notification and the first information indicates that the review of the application to use the second account KU-2 has not been completed, the first display control unit 115 displays a message M on the user terminal 20-1 indicating that the application to use the second account KU-2 is currently under review.

[0095] Figure 6C is a schematic diagram showing an example of a message display screen indicating that the application for use of second account KU-2 is "under review." When user U-1 selects icon N12 in Figure 6B (an interface for instructing a deposit from a bank account), dialog N13 shown in Figure 6C is displayed. Dialog N13 displays a message M explaining that the change to second account KU-2 is under review, an inquiry icon N14 for calling the inquiry desk, an icon N15 for moving to a screen for detailed explanations regarding the review, and the like.

[0096] When user U-1 taps icon N16 for closing dialog N13, dialog N13 is closed and the screen transitions to a screen including a payment code image (barcode N1) as shown in FIG. 6A. That is, message M is displayed in dialog N13, and when dialog N13 is closed, first display control unit 115 causes user terminal 20-1 to display the first payment code image (barcode N1). The first payment code image is an example of a payment image including information specifying first account KU-1 as the payment account.

[0097] By displaying the dialog N13 on the user terminal 20-1, the user U-1 can check the status of the examination. Furthermore, when the dialog N13 is closed, the first payment code image is displayed on the user terminal 20-1, allowing the user U-1 to make a payment immediately, improving convenience.

[0098] A-5. Flowchart Fig. 11 is a flowchart showing the operation of the processing device 103 of the payment management device 10. In more detail, Fig. 11 mainly shows the operation when a payment application is launched on the user terminal 20, and does not include, for example, the operation during payment processing. The following explanation will be given for the case when the payment application is launched on the user terminal 20-2 used by user U-2.

[0099] The processing device 103 functions as the activation receiving unit 113 and waits until the payment application is activated on any of the user terminals 20, that is, until a first notification regarding the activation of the payment application is received from any of the user terminals 20 (step S200: NO). When the payment application is activated on user terminal 20-2, in other words, when the first notification is received from user terminal 20-1 (step S200: YES), the processing device 103 functions as the acquiring unit 114 and acquires type information indicating the type of user account KU of user U-2 who owns user terminal 20-2 (step S201).

[0100] If the type of user account KU is the first account KU-1 (step S202: YES), the processing device 103 functions as the first display control unit 115, generates display control information for displaying the first payment code image on the user terminal 20-2, transmits it to the user terminal 20-2 (step S203, indicated as "Display first payment code image" in the figure), and terminates the processing of this flowchart.

[0101] Furthermore, if the type of user account KU is not the first account KU-1 (step S202: NO) but the second account KU-2 (step S204: YES), the processing device 103 functions as the first display control unit 115, generates display control information for displaying the second payment code image on the user terminal 20-2, transmits it to the user terminal 20-2 (step S205, indicated as "Display second payment code image" in the figure), and terminates the processing of this flowchart.

[0102] Also, if the type of user account KU is not second account KU-2 (step S204: NO) and a change from first account KU-1 to second account KU-2 is under review (step S206: YES), the processing device 103 functions as the first display control unit 115, generates display control information for displaying the first payment code image on the user terminal 20-2, and transmits it to the user terminal 20-2 (step S207, indicated as "Display first payment code image" in the figure).

[0103] Furthermore, if the user account KU is not under review, i.e., if the review result for changing the type of user account KU is "rejected" (step S206: NO), the processing device 103 functions as the first display control unit 115, generates display control information for displaying a message indicating that the change of the type of user account KU has been rejected, transmits it to the user terminal 20-2 (step S208, indicated as "display rejection message" in the figure), and terminates the processing of this flowchart.

[0104] After the first payment code image is displayed on the user terminal 20-2 in step S207, if the user U-2 selects the icon N12 (represented as "bank deposit icon" in the figure) that instructs a deposit from bank account BK (step S210: YES), the processing device 103 functions as the first display control unit 115, generates display control information for displaying a dialog N13 (represented as "review dialog" in the figure) containing a message M explaining that the change to the second account KU-2 is under review, and sends it to the user terminal 20-2 (step S211).

[0105] If the dialog N13 is closed (step S212: YES), the processing device 103 functions as the first display control unit 115, generates display control information for displaying the first payment code image on the user terminal 20-2, transmits it to the user terminal 20-2 (step S213, indicated as "Display first payment code image" in the figure), and terminates the processing of this flowchart.

[0106] A-6. Summary of embodiments As described above, the payment management device 10 according to the embodiment enables payment based on the first payment code image corresponding to payment using the first account KU-1 as the payment account when a payment application is launched on the user terminal 20 of the user U whose application to use the second account KU-2 is under review. Therefore, even if the application to use the second account KU-2 is under review, the user U can execute code payment using the first account KU-1, which can prevent the user U from abandoning the payment.

[0107] Furthermore, the first account KU-1 only allows deposits by prepayment, i.e., deposits using cash CA, while the second account KU-2 allows deposits by prepayment and by fund transfer, i.e., deposits using cash CA and deposits from user U's bank account BK. Since the second account KU-2 involves fund transfers, identity verification may be required by law. On the other hand, the first account KU-1 allows deposits by prepayment, which is not subject to identity verification restrictions by law. Therefore, if an application to use the second account KU-2 is under review, user U's convenience is improved by allowing payments to be made using the payment code image corresponding to the first account KU-1.

[0108] In addition, the screening of applications for use of the second account KU-2 includes a list check (so-called antisocial check) that compares information about persons belonging to antisocial organizations (block list BL) with the personal information PD of user U. The list check prevents inappropriate transactions and maintains the social credibility of payment service D.

[0109] Furthermore, if the user U is authorized to use the second account KU-2, the payment management device 10 enables payment based on the second payment code image corresponding to payment using the second account as the payment account. This allows the user U to make payments using the second account KU-2, improving user U's convenience.

[0110] Furthermore, when a user U, whose use of the second account KU-2 is under review, selects an icon corresponding to a function that cannot be executed in the first account KU-1 but can be executed in the second account KU-2, the payment management device 10 displays a dialog N13 including a message M indicating that the application to use the second account KU-2 is under review on the user terminal 20. Thus, the user U can know the status of the review regarding the use of the second account KU-2.

[0111] Furthermore, when the above dialog is closed, the payment management device 10 causes the user terminal 20 to display a first payment code image corresponding to the payment using the first account KU-1 as the payment account. Therefore, after closing the dialog N13, the user U can quickly execute the payment using the first account KU-1 as the payment account.

[0112] In this embodiment, the user terminal 20 displays the first payment code image, the second payment code image, etc., based on the display control information transmitted from the payment management device 10. In other words, the payment management device 10 acquires information regarding the review status of the second account use application and transmits display control information to the user terminal 20 instructing whether the first payment code image or the second payment code image should be displayed on the user terminal 20. This is not a limitation, and for example, the user terminal 20 may acquire information regarding the review status of the second account use application and determine whether the first payment code image or the second payment code image should be displayed. In the above-described embodiment, the second information was display control information. However, when determining whether the first payment code image or the second payment code image should be displayed on the user terminal 20, the second information may be, for example, the type information described above (either "First Account KU-1," "Second Account KU-2," "Under Review," or "Rejected"). In this case, the second display control unit 214 of the user terminal 20 that acquired the type information determines the type of payment code image based on the type information and displays the determined type of payment code image on the display device 201. For example, if the type information is "under review" (if the second information indicates that the review of the application to use the second account KU-2 has not been completed), the second display control unit 214 may display a first payment code image including information indicating that the pre-registered first account KU-1 is the payment account.

[0113] B: Other (1) In the above-described embodiment, ROM and RAM are exemplified as storage devices 102 and 204, but storage devices 102 and 204 may also be flexible disks, magneto-optical disks (e.g., compact disks, digital versatile disks, Blu-ray (registered trademark) discs), smart cards, flash memory devices (e.g., cards, sticks, key drives), CD-ROMs (Compact Disc-ROMs), registers, removable disks, hard disks, floppy (registered trademark) disks, magnetic strips, databases, servers, or other suitable storage media.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0130] (17) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information). [Explanation of symbols]

[0131] 1...payment system, 10...payment management device, 20 (20-1 to 20-N)...user terminal, 30...store terminal, 101...communication device, 102...storage device, 103...processing device, 111...account processing device, 112...payment processing device, 113...startup reception unit, 114...acquisition unit, 115...first display control unit, 201...display device, 202...input device, 203...camera, 204...communication device, 205...storage device, 206...processing device, 211...startup request unit, 212...payment request unit, 213...account request unit, 214...second display control unit, BK...bank account, BL...block list, CA...cash, DB1...user database, DB2...account database, KU...user account, KU-1...first account, KU-2...second account, N...network, T...store, U (U-1 to UN)...user.

Claims

1. a reception unit that receives, from a user terminal, a first notification based on the launch of an application used for electronic payment linked to at least one payment account; an acquisition unit that acquires first information related to the settlement account when the first notification is received; a payment processing unit that executes payment from the payment account based on the payment image displayed on the user terminal, The first information is information regarding the status of an examination of an application for using a second account as the settlement account, When the first information indicates that the examination of the application for use of the second account has not been completed, the payment processing unit executes the payment based on a payment image including information specifying the pre-registered first account as the payment account. Payment management device.

2. The first account is capable of receiving deposits in advance, The second account can be deposited by the advance payment and by fund transfer, The application for use of the first account does not require the user to verify his / her identity, The application for use of the second account requires the user to verify his / her identity. The payment management device according to claim 1 .

3. The screening of the application for use of the second account includes comparing information about a person belonging to an anti-social organization with the user's personal information. The payment management device according to claim 2 .

4. When the first information indicates that use of the second account is approved, the payment processing unit executes payment based on a payment image including information specifying the second account as the payment account. The payment management device according to claim 1 .

5. the application displays an icon corresponding to a function that cannot be performed by the first account but can be performed by the second account; the receiving unit receives, from the user terminal, a second notification indicating that the user has selected the icon; and a display control unit that, when the receiving unit receives the second notification and the first information indicates that the review of the application for use of the second account has not been completed, displays on the user terminal a message indicating that the application for interest on the second account is under review. The payment management device according to claim 1 .

6. The message is displayed in a dialog box, When the dialog is closed, the display control unit causes the user terminal to display a payment image including information specifying the first account as the payment account. The payment management device according to claim 5 .

7. The first account cannot be credited from the user's bank account, The second account can be funded from the user's bank account; the icon corresponds to a function of depositing money from the user's bank account to the second account; The payment management device according to claim 5 .

8. a transmitter that transmits a first notification to the payment management device based on the activation of an application used for electronic payment linked to at least one payment account; a receiving unit that receives second information related to the payment account from the payment management device; a display control unit that displays a payment image for requesting the payment management device to make a payment from the payment account, The second information is information regarding the status of an examination of an application to use the second account as the settlement account, When the second information indicates that the examination of the application for use of the second account has not been completed, the display control unit displays a payment image including information specifying a pre-registered first account as the payment account. User terminal.

9. receiving, from the user terminal, a first notification based on the launch of an application used for electronic payment linked to at least one payment account; When the first notification is received, first information regarding the settlement account is acquired; Execute payment from the payment account based on the payment image displayed on the user terminal. A payment management method, comprising: The first information is information regarding the status of an examination of an application for using a second account as the settlement account, If the first information indicates that the examination of the application for use of the second account has not been completed, the payment is executed based on a payment image including information specifying the pre-registered first account as the payment account. Payment management methods.

10. transmitting a first notification to the payment management device based on the activation of an application used for electronic payment linked to at least one payment account; receiving second information relating to the payment account from the payment manager; displaying a payment image for requesting the payment management device to make a payment from the payment account; The second information is information regarding the status of an examination of an application to use the second account as the settlement account, If the second information indicates that the review of the application for use of the second account has not been completed, the payment image includes information indicating that the pre-registered first account is the payment account. Display control method.

Images