Information processing device, system, information processing method, and program

Abstract

It can accurately determine whether or not electronic payment can be used. [Solution] An information processing device comprising: an acquisition unit that acquires information about stores or services that are the target of electronic payment on the network from a user terminal device via the network in response to a user performing an operation on the user terminal device to use a prepaid electronic payment using the network; and a processing unit that determines whether or not to perform the prepaid electronic payment at the target store by referring to determination information which associates information indicating whether or not the prepaid electronic payment can be used with the information about the store or service.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, a system, an information processing method, and a program.

Background Art

[0002] Conventionally, a determination device that acquires credit information regarding the credit of a store and determines whether the credit information satisfies a determination condition has been known (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the conventional technology, it may not be possible to accurately determine whether electronic payment can be used.

[0005] The present invention has been made in consideration of such circumstances, and one of its objects is to provide an information processing apparatus, a system, an information processing method, and a program that can accurately determine whether electronic payment can be used.

Means for Solving the Problems

[0006] One aspect of the present invention is an information processing device comprising: an acquisition unit that acquires information from a user terminal device via a network regarding stores or services that are the target of electronic payment on the network, in response to a user performing an operation on the user terminal device to use a network-based prepaid electronic payment; and a processing unit that determines whether or not to perform the prepaid electronic payment at the target store by referring to determination information that associates information indicating whether or not the prepaid electronic payment can be used with the information regarding the store or service. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to accurately determine whether or not electronic payment can be used. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows an example of a configuration for implementing an electronic payment service. [Figure 2] This diagram shows the functional configuration of the payment server 100. [Figure 3] This figure shows an example of the contents of judgment information 173. [Figure 4] This diagram illustrates the details of the processes performed by the electronic payment system. [Figure 5] This figure shows an example of an interface screen that is displayed on the display unit of the user terminal device 10 when an error is handled. [Figure 6] This is a sequence diagram showing an example of the processing flow performed by an electronic payment system. [Figure 7] This diagram illustrates the details of the processes performed by the electronic payment system. [Figure 8] This is a sequence diagram showing an example of the processing flow performed by an electronic payment system. [Figure 9] This figure shows another example of the functional configuration of an electronic payment system. [Figure 10]This is a sequence diagram (part 1) illustrating the general flow of electronic payments. [Figure 11] This is a sequence diagram (part 2) illustrating the general flow of electronic payments. [Figure 12] This is a diagram showing the configuration of payment server 100. [Figure 13] This figure shows an example of the contents of user information 172. [Figure 14] This figure shows an example of the contents of merchant / store information 176. [Modes for carrying out the invention]

[0009] The following describes embodiments of the information processing apparatus, information processing method, and program of the present invention with reference to the drawings. Various devices such as "servers" that appear below, which provide services to users or perform internal analysis, may be implemented by a distributed group of devices, and the operators of each device may be different. Furthermore, the owner of the hardware of the devices (the provider of the cloud server) and the operator that actually operates them may also be different. The application program and the payment server work together to provide electronic payment services.

[0010] [Electronic payment service] Figure 1 shows an example of the configuration of an electronic payment system that implements electronic payment services. The electronic payment service is implemented with a payment server 100 at its center. An electronic payment system that implements electronic payment services includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, a payment server 100, and a service server 200. These devices communicate with each other, for example, via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, and provider equipment. The payment server 100 or the service server 200 is an example of an "information processing device".

[0011] Some or all of the functional components included in the electronic payment system may be distributed among multiple devices in any form or integrated into any device. For example, some or all of the functional components of the payment server 100 or the service server 200 may be included in one device, the other device, or another device.

[0012] [User terminal device] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is at least a computer device having an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, the wallet application 20 is executed by a processor such as a CPU, and operates to provide an electronic payment service to the user in cooperation with the payment server 100. The wallet application 20 is installed in the user terminal device 10 from, for example, an application store, and controls a camera, a communication device, a touch panel, etc. In the user terminal device 10, a mini application may operate. The mini application is an application program that operates within the wallet application 20 (or the payment application 30 described later). The mini application is, for example, a mini application that provides various services.

[0013] The wallet application 20 is an application program that manages the payment methods of electronic payments registered by users. Electronic payments include, for example, credit cards, debit cards, prepaid cards (electronic payments), so-called transportation IC (Integrated Circuit) cards, and electronic payments issued by each service provider. The above cards are, for example, virtual cards used in the user terminal device 10. The user can use electronic payments by operating the wallet application 20 to select a desired electronic payment method from the registered electronic payment methods and perform operations for electronic payments. The wallet application 20 provides a wallet service for electronic payments that can register and manage so-called various electronic payments in the application as described above.

[0014] [First store terminal device] The first store terminal device 50 is installed in a store, for example. The first store terminal device 50 performs electronic payments using the electronic payment method selected by the user. The first store terminal device 50 communicates with the user terminal device 10, for example, to perform electronic payments.

[0015] [Payment server] Figure 2 shows the functional configuration of the payment server 100. The payment server 100 includes, for example, a communication unit 110, an acquisition unit 111, a determination unit 112, an information processing unit 114, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), GPU (Graphics Processing Unit), and SOC (System On Chip), or by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device with a non-transient storage medium), or it may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed in the storage device when the storage medium is mounted on a drive device.

[0016] The storage unit 170 can be an HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may also be a NAS (Network Attached Storage) device that can be accessed by the payment server 100 via the network. The storage unit 170 stores information such as user information 172 (details will be described later) and judgment information 173.

[0017] User information 172 is information that associates the user identification information for each electronic payment method described above with information about the user. User identification information is, for example, the card number of a credit card, debit card, or prepaid card. Information about the user is information provided by the user when applying to use the above electronic payment methods (e.g., credit card, debit card, or prepaid card) (e.g., address, phone number, occupation, annual income, etc.) and other information about the user. Other information about the user is, for example, the electronic payment usage history. The usage history includes the store used, the store's location, and the amount. In the case of a prepaid card, other information about the user includes the amount that has been charged.

[0018] Figure 3 shows an example of the contents of judgment information 173. Judgment information 173 includes information about a store or service. The information about a store or service includes one or more of the following: store name, service name, information about the store or service's webpage related to electronic payment (e.g., URL; Uniform Resource Locator), and information about the application program of the store or service related to electronic payment (package name of the application program of the store or service attempting to make an electronic payment). A store or service related to electronic payment is a store or service where electronic payment is executed in the capture information without authorization information being transmitted (details will be described later). Also, a store or service related to electronic payment is, for example, a store or service where electronic payment has consistently failed.

[0019] The communication unit 110 is a communication interface for connecting to a network NW. The communication unit 110 is, for example, a network interface card.

[0020] The determination unit 112 refers to determination information, which associates information indicating whether or not prepaid electronic payment is available with information about a store or service, and determines whether or not the information about a store or service related to electronic payment, which is received from another device, corresponds to the information about a store or service in the determination information.

[0021] The information processing unit 114 determines whether or not to allow prepaid electronic payment at the target store based on the determination result of the determination unit 112.

[0022] [Premise] In the comparative example, when a user uses a wallet app to select a prepaid card from among several electronic payment options, the card number is automatically entered into the card number input field displayed on the user terminal device's display, and the electronic payment process is executed in cooperation with the payment server 100 or service server 200.

[0023] In the case of prepaid cards, even if the amount deposited in advance is less than the amount to be used for electronic payment, there is no problem in case (A), but in case (B), the electronic payment may still be processed.

[0024] (A) For example, when a prepaid card is used at a store, the payment server 100 receives authorization information from the service server 200 or a server that cooperates with the electronic payment of the prepaid card. The payment server 100 executes the electronic payment if the charge amount of the prepaid card managed by the payment server 100 is equal to or greater than the amount of the electronic payment included in the authorization information. Subsequently, the payment server 100 confirms the above electronic payment process if the electronic payment in the authorization information and the electronic payment in the capture information related to the authorization information are consistent, in response to the transmission of the capture information.

[0025] Authorization information is information sent for authorization to confirm whether electronic payment is possible. Capture information is information for the process of actually carrying out the electronic payment approved during authorization. When authorization information is sent to the payment server 100 in this way, the payment server 100 can confirm the balance of the prepaid card, and therefore the following problems do not occur.

[0026] (B) For example, as described above, sometimes CAPTCHA information is sent without authorization information being sent. In this case, the payment server 100 cannot process the electronic payment if the balance on the prepaid card is less than the amount of the electronic payment in the CAPTCHA information. The burden resulting from this will be borne by the administrator of the prepaid card (the administrator of the payment server 100). In order to reduce the burden on the administrator as described above, the following process is performed.

[0027] Furthermore, as described above, if administrators incur an additional burden, users may be informed that their balance was insufficient, which can result in a negative experience for them. In contrast, the following process helps to mitigate this negative experience for users.

[0028] [Process Overview] In response to a user performing an operation on the user terminal device 10 to use a prepaid electronic payment system via the network, the payment server 100 obtains target information from the user terminal device 10 regarding the stores or services that accept electronic payments on the network. The payment server 100 refers to determination information 173, which associates information indicating whether or not prepaid electronic payments are accepted with information regarding the stores or services, and determines whether or not prepaid electronic payments can be made at the target store.

[0029] As described above, the payment server 100 refers to the determination information 173 and suppresses electronic payments if it estimates that the store accepting the electronic payment does not use authorization information. This prevents the payment server 100 from being unable to execute an electronic payment due to insufficient charge balance when acquiring capture information.

[0030] [Overview of the processing flow (1)] Figure 4 is a diagram illustrating the details of the processes performed by the electronic payment system. (1) First, the user operates the wallet app 20 to register a prepaid card or credit card with the wallet app 20. Then, (2) when the user makes an electronic payment at a store or service on the network (when making an electronic payment on a web page), the user operates the wallet app 20.

[0031] (3) When a user operates the wallet app 20 and selects a credit card as the method of electronic payment, the wallet app 20 automatically prompts the user to input the credit card number and other information necessary for electronic payment into the credit card number input field related to electronic payment. This process is performed by one or more functional configurations of the wallet app 20, the service server 200, and the server of the store or service related to electronic payment, or by these in cooperation. Hereinafter, one or more functional configurations of the wallet app 20, the service server 200, and the server of the store or service related to electronic payment may be referred to as the target device.

[0032] The payment server 100 then acquires various information, including the credit card number (user information), transmitted from the target device, and determines the risk related to the electronic payment based on the acquired information. The various information includes, for example, the location of the user terminal device 10, information about the user terminal device 10, information about its operation, information about the store or service being used, information about the web page related to the store or service being used, and the amount of the electronic payment. The credit card number mentioned above is the number automatically entered into the input field described above. The payment server 100 then performs processing according to the determination. The processing according to the determination includes, for example, (4) authentication completion, (5) additional authentication, and (6) error processing. The results of this processing are provided to the wallet application 20 via the service server 200.

[0033] (4) Authentication completion is the process of providing information to the user terminal device 10 via the service server 200 indicating that the credit card is valid and usable, and that authentication has been completed. (5) Additional authentication is a process that verifies the validity of a credit card using two-factor authentication. For example, in addition to the credit card identification information, it is a process that requires the user to enter information to be authenticated, such as a password. (6) Error handling is the process of notifying the user that the validity of the credit card cannot be sufficiently verified and that electronic payment using the credit card cannot be made.

[0034] (7) When a user operates the wallet app 20 and selects a prepaid card as the method of electronic payment, the wallet app 20 transmits the relevant information to the payment server 100 via the service server 200. The relevant information includes information about the store or service.

[0035] (10) If the information regarding the store or service does not match the determination information 173, proceed to (3). The payment server 100 refers to the determination information 173, which associates information indicating that prepaid electronic payment is not available with the information regarding the store or service, and if it determines that prepaid electronic payment can be made at the target store, it instructs the user terminal device 10 to automatically input the user's information into the input field for inputting the user's information for making a prepaid electronic payment. The payment server 100 then acquires various information, including the prepaid card number, transmitted from the target device in the same manner as above, and determines the risk related to the electronic payment based on the acquired information. This prepaid card number is, for example, the card number that was automatically entered into the input field.

[0036] (8) The payment server 100 refers to the determination information 173 and determines whether the information about the store or service in the target information corresponds to the store or service in the determination information 173. (9) If the information about the store or service corresponds to the determination information 173, the payment server 100 performs error processing.

[0037] If the payment server 100 determines that prepaid electronic payment cannot be made at the target store by referring to determination information 173 which associates information indicating that prepaid electronic payment cannot be made with information about the store or service, it will not automatically prompt the user terminal device 10 to enter the user's information into the input field for entering the user's information for prepaid electronic payment. If the payment server 100 determines that prepaid electronic payment cannot be made at the target store, as determined above, it will notify the user terminal device 10 of information indicating that prepaid electronic payment cannot be made at the target store.

[0038] Figure 5 shows an example of an interface screen displayed on the display unit of the user terminal device 10 when an error is processed. For example, suppose that when an electronic payment is made, the user operates the wallet app 20 and selects a prepaid card as the method of electronic payment on the interface screen IF1. In this case, if the payment server 100 finds that the information regarding the store or service for the electronic payment matches the determination information 173, it displays interface screen IF2 on the display unit, which contains information indicating that electronic payment using a prepaid card cannot be used at that store or service. This allows the user to easily recognize that a prepaid card cannot be used at that store or service.

[0039] [Sequence Diagram (1)] Figure 6 is a sequence diagram showing an example of the processing flow performed by the electronic payment system. This process corresponds to (3), (6)-(10) in Figure 5.

[0040] First, when a user operates the wallet app 20 for electronic payment (S100), the wallet app 20 displays a list of electronic payment methods, such as the type of card registered in the wallet app 20, on the display unit (S102). Next, for example, when a user makes a selection operation for a prepaid card (S104), the wallet app 20 sends information about the store or service (target information) to the service server 200 (S106). In the process of S106, various information may also be sent, such as the location of the user terminal device 10, information about the user terminal device 10, information about the operation, information about the store or service being used, information about the web page related to the store or service being used, and the amount of the electronic payment.

[0041] Next, the service server 200 sends the target information to the settlement server 100 (S108). Then, the settlement server 100 performs a determination process based on the determination information 173 and the target information (S110). The determination process determines whether or not the target information corresponds to the determination information.

[0042] Next, the payment server 100 sends the determination result to the service server 200 (S112). Next, the service server 200 sends the determination result to the wallet application 20 (S114). Next, the wallet application 20 displays information corresponding to the determination result on the display unit of the user terminal device 10 (S116).

[0043] As described above, electronic payment systems can accurately determine whether or not a prepaid card can be used.

[0044] Alternatively, the process described above may be simplified by omitting the service server 200, and the user terminal device 10 and the payment server 100 may communicate directly to execute various processes.

[0045] All or part of the various processes performed by the payment server 100 described above may be performed by the service server 200.

[0046] [Overview of the processing flow (2)] In this process, the judgment information 173 is held by the service server 200, and the service server 200 uses the judgment information 173 to make a judgment. When a user performs an operation on the user terminal device 10 to use a prepaid electronic payment system via the network, the service server 200 obtains information from the user terminal device 10 regarding the stores or services that are eligible for electronic payment on the network via the network. The service server 200 refers to the judgment information 173 and decides whether or not to allow the user to make a prepaid electronic payment at the target store. Figure 7 is a diagram illustrating the details of the process performed by the electronic payment system. The explanation will focus on the differences from Figure 5 mentioned above.

[0047] (1) First, the user operates the wallet app 20 to register a prepaid card or credit card to the wallet app 20. Then, (2) when the user makes an electronic payment at a store or service on the network (when making an electronic payment on a web page), the user operates the wallet app 20.

[0048] (#7) The wallet application 20 sends the target information to the service server 200. The target information includes information about a store or service. (8) The service server 200 refers to the determination information 173 and determines whether the information about the store or service in the target information is a store or service that corresponds to the determination information 173.

[0049] (9) If the judgment information 173 is met, (11) the service server 200 executes custom error processing. Custom error processing is a process in which the service server 200, in cooperation with the wallet app 20, displays a list of other electronic payment options on the display unit of the user terminal device 10, in a manner that excludes prepaid cards from the electronic payment options. In other words, the service server 200 excludes prepaid cards from the options without automatically entering the user's information into the input field for entering user information to perform prepaid electronic payment on the user terminal device 10.

[0050] On the other hand, if the case does not fall under (10) judgment information 173, the process proceeds to (3). The service server 200 refers to judgment information 173, which associates information indicating that prepaid electronic payment is not available with information about the store or service, and if it determines that prepaid electronic payment can be made at the target store, it displays a list of electronic payment options, including prepaid cards. If the user selects a prepaid card, the service server 200 instructs the user terminal device 10 to automatically input the user's information into the input field for entering the user's information for electronic payment with a prepaid card. The service server 200 then sends various information, including the entered user information, to the payment server 100, causing the payment server 100 to determine the risk associated with the electronic payment. The prepaid card number is the card number automatically entered into the input field. The judgment process of the payment server 100 may also be performed by the service server 200.

[0051] As described above, the service server 200 uses the determination information 173 to display a list of electronic payment methods on the display unit for electronic payments at stores or services that match the determination information 173, excluding prepaid card electronic payments from the list of electronic payment methods that the user can select. This allows the user to select an available electronic payment method without having to select an unavailable one.

[0052] If, as described above, a prepaid card cannot be used, instead of removing the prepaid card from the options, the service server 200 may display information indicating that it cannot be used, associated with the prepaid card, thereby preventing the user from selecting a prepaid card.

[0053] [Sequence Diagram (2)] Figure 8 is a sequence diagram showing an example of the processing flow performed by the electronic payment system. This process corresponds to (3), (6)-(11) in Figure 7.

[0054] First, the payment server 100 sends judgment information 173 to the service server 200 (S200). The service server 200 stores the transmitted judgment information 173 in its memory unit. When a user operates the wallet app 20 for electronic payment (S202), the wallet app 20 sends information about the store or service (target information) to the service server 200 (S204).

[0055] Next, the service server 200 performs a determination process (S206) based on the determination information 173 and the target information. The determination process determines whether or not the target information corresponds to the determination information 173.

[0056] Next, the service server 200 sends the determination result to the wallet application 20 (S208). Next, the wallet application 20 displays a list of electronic payments corresponding to the determination result on the display unit of the user terminal device 10 (S210). For example, if the store or service to which the electronic payment is applicable matches the determination information 173, the electronic payment using a prepaid card will not be displayed in the above list, and a list of other electronic payments will be displayed. For example, if the store or service to which the electronic payment is applicable does not match the determination information 173, a list of electronic payments using a prepaid card and other electronic payments will be displayed.

[0057] As described above, the electronic payment system improves user convenience because it displays a list of available electronic payment methods on the display unit.

[0058] [Examples of integration with payment apps] The wallet app 20 may perform processing in cooperation with the payment app 30. For example, the wallet app 20 and the payment app 30 may be linked through account linking, and a virtual prepaid card provided by the payment app 30 may be registered in the wallet app 20.

[0059] The electronic payment service provided by the payment app 30 is a service that supports payments related to the purchase of goods and services at stores. A store refers to, for example, a physical store (brick-and-mortar store) that exists in the real world, but may also include a virtual store for e-commerce. A virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when settling a purchase at a virtual store, the system is controlled to transition to the interface screen of the electronic payment service. In the electronic payment service, stores are treated as belonging to, for example, affiliated merchants (brands), and processing such as payment when a purchase is made at a store is mainly carried out between the user and the affiliated merchant. Alternatively, processing such as payment may be carried out between the user and the store.

[0060] Figure 9 shows another example of the functional configuration of an electronic payment system. An electronic payment system that implements electronic payment services includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, a payment server 100, and a service server 200. These devices communicate with each other, for example, via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, provider equipment, etc.

[0061] Some or all of the functional components included in an electronic payment system may be distributed across multiple devices in any form, or integrated into any device. For example, some or all of the functional components of payment server 100 may be included in other devices.

[0062] [Store Terminal Device #1] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 may include a so-called POS (Point of Sale) device, and the product price acquisition function and optical reading function may be realized by the POS device. The store code image 60 is placed in the store and is a code image such as a QR code (registered trademark) or barcode printed on a paper or plastic medium. The store code image 60 may also be displayed on a display placed in the store (this may also be the display of a terminal device such as a smartphone). The store code image is an example of "code information". The code information is not limited to QR codes or barcodes, but can be any information used in an electronic payment service. For example, the code information can be used in electronic payments of an electronic payment service and can include information for identifying a store.

[0063] [Second store terminal device] The second store terminal device 70 is used by the operator of the affiliated store or the store operator. The second store terminal device 70 is a smartphone, tablet, personal computer, etc. The affiliated store interface 72 operates on the second store terminal device 70. The affiliated store interface 72 may be an affiliated store application or a browser. The affiliated store interface 72 accepts coupon settings etc. from the affiliated store operator and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image by running an affiliated store application, or reading a code image displayed by the user terminal device 10.

[0064] The payment application 30 stored in the user terminal device 10 executes the electronic payment process as described later.

[0065] [Payment Server] The payment server 100 implements electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and a merchant server, in which case payment information is transmitted from the POS device to the payment server 100 via the merchant server. In the following description, this distinction will not be made, and it will be assumed that payment information is transmitted from the first store terminal device 50.

[0066] Figures 10 and 11 are sequence diagrams illustrating the general flow of electronic payments. There may be two patterns for electronic payments: Pattern 1 and Pattern 2.

[0067] In the case of Pattern 1 shown in Figure 10 (hereinafter referred to as User Scan), the user terminal device 10, with the payment application 30 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 contains information about the store URL (Uniform Resource Locator). This store URL is an electronic payment service domain to which information that can identify the store has been added, and is associated with the merchant ID and store ID, etc., at the payment server 100 (described later). The payment application 30 sends the first payment information, including the store URL and account ID, to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the merchant ID and store ID corresponding to the store URL, obtains the merchant name and store name information (S3), and sends it to the payment application 30 (S4). The user enters the payment amount into the user terminal device 10 on the screen where the merchant name and store name are displayed (S5). The user terminal device 10 then generates second payment information, including at least the payment amount, and sends it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notification (information for displaying the payment completion screen) to the payment application 30 (S8), and the payment application 30 displays the payment completion screen (S9). If the store code image 60 is displayed on a display placed in the store, the store code image 60 may include payment amount information as well as the store URL. In this case, the procedure for the user to enter the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Merchant name and store name information may be included and displayed on the payment completion screen.

[0068] In the case of Pattern 2 shown in Figure 11 (hereinafter referred to as Store Scan), when the payment app 30 is launched, when a payment operation is performed in the payment app 30, when it is time for an automatic update (for example, every minute), and at other times, the payment app 30 sends a request to the payment server 100 to issue a one-time code (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 30 (S13). The payment app 30 displays a code image such as a QR code or barcode that was generated based on the one-time code (S14). The user holds the display surface of the user terminal device 10 over the first store terminal device 50 (presents it), and the first store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including the one-time code, payment amount, merchant ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is obtained in advance by barcode scanning or manual input. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs the electronic payment (S17). The payment server 100 then sends a payment completion notification to the payment app 30 (S18), and the payment app 30 displays a payment completion screen (S19).

[0069] Furthermore, electronic payment may be performed using only one of the above patterns. Also, the "account ID" explained in Figure 10 may be other information that can be used as user identification information (for example, a phone number). In addition, the issuance of a one-time code may be omitted during store scanning, and the payment app 30 may display a code image generated based on the user's account ID. In that case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0070] [Payment Server Functional Configuration] Figure 12 is a diagram of the configuration of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a determination unit 112, an information processing unit 114, a content provision unit 120, a payment processing unit 130, an information management unit 140, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as LSIs, ASICs, FPGAs, GPUs, and SOCs, or by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed in the storage device when the storage medium is mounted on a drive device.

[0071] The memory unit 170 stores user information 172 and judgment information 173, as well as content information 174 and merchant / store information 176. Some of this information may also be stored in the memory unit of the user terminal device 10.

[0072] The content provider unit 120, for example, has the functionality of a web server and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10 or the second store terminal device 70. The content provider unit 120 reads the necessary content from the content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs from the user with the content being played by the payment application 30 and transmits the aforementioned payment information to the payment server 100. The above content may also be generated by the payment application 30. In this case, the content provider unit 120 provides the payment application 30 with the information necessary for generating the content.

[0073] The payment processing unit 130 performs payment processing based on payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0074] [User information] Figure 13 shows an example of the contents of User Information 172. User Information 172 is an example of user registration information. User Information 172 includes, for example, user URL, account ID, telephone number, password, as well as information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit payment settings, credit payment limit, credit payment amount, available credit payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for money transfer processing between users. When registering for a new electronic payment service, registration of a telephone number and password is mandatory. The account ID is issued to the user by the payment server 100, and the user ID is an ID that the user can set at will (or does not have to set). Similarly, the email address, name, address, and date of birth are also information that the user can set at will (or does not have to set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

[0075] The charge balance is information indicating the balance of electronic money set by the user by sending money to their account in advance. Methods of sending money include sending from an ATM (Automatic Teller Machine) of a designated provider (bank) and sending from a registered bank account. The credit payment setting indicates whether or not the user has completed the settings to enable electronic payments by credit card, and is set to either "Completed" or "Not Completed". The credit payment limit is the monthly limit for credit payments, the credit payment amount is the amount already used for credit payments in the current month, and the available credit payment amount is the amount available for credit payments in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the diagram shows only one credit payment limit, in reality there are also daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be described later. The payment method setting indicates whether the user will use electronic payment with the charge balance or payment by credit card at that time. The bank account and credit card number information, respectively, refers to the bank account or credit card number (account number, card number) to which funds can be deposited into the electronic payment service. The charge history information is a record of when the user has previously sent money to the electronic payment service to increase the charge balance. The payment history information shows the details of each payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0076] [Franchise / Store Information] Figure 14 shows an example of the contents of the merchant / store information 176. The merchant / store information 176 includes, for example, a first table 176A in which the merchant ID, store ID, and merchant category are associated with the store URL; a second table 176B in which the merchant name and sales amount (as described above) are associated with the merchant ID; and a third table 176C in which the store name is associated with the store ID. In addition to this information, the merchant / store information 176 may also include information such as the merchant or store category, store location, and payment pattern.

[0077] [Electronic payment] When the payment processing unit 130 obtains payment information from the user terminal device 10 or the first store terminal device 50, it refers to the user information 172 to obtain the user's "payment method setting". For users whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance, which is managed in association with the user ID, and increasing the sales amount item value of the merchant (or store). The sales amount item value of the merchant is not used as electronic money itself, for example, but rather the amount corresponding to the sales amount item value is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service.

[0078] The payment processing unit 130 performs electronic payment as follows for users whose "settings information" is set to "credit payment". Credit payment is a payment method that is carried out in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the donor and allows electronic payment that does not depend on the charge balance within the credit payment limit. In order to use the credit payment service, it may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used by credit payment is settled in a lump sum for the month on the payment date of the following month, for example, by withdrawal from a bank account. In this case, the payment processing unit 130 performs a provisional settlement by adding the settlement amount to the amount used by credit payment and subtracting the same amount from the available credit payment amount. When the closing date arrives, it processes the payment for the current month to be withdrawn on the payment date of the following month as described above, or requests the operator of the credit card company to perform the said process. If the settlement amount exceeds the available credit payment amount at the time of provisional settlement, an error notification is sent back to the payment application 30.

[0079] The information management unit 140 acquires information provided by other server devices and terminal devices. Based on the information acquired from the user terminal device 10 and the second store terminal device 70, the information management unit 140 manages user information 172 and affiliated store / store information 176. The information management unit 140 performs operations such as adding, editing, and deleting new records for user information 172 and affiliated store / store information 176. Furthermore, the information management unit 140 processes information provided by other server devices and terminal devices, and provides information stored in the storage unit 170 to the user terminal device 10.

[0080] The payment app 30 mentioned above links its account with the wallet app 20. As a result, a virtual prepaid card usable with the payment app 30 is registered in the wallet app 20.

[0081] In this way, electronic payments can be made by using the payment app 30, and it can also be easily linked with the wallet app 20 to allow the use of prepaid cards within the wallet app 20.

[0082] The functional configuration of the wallet app 20 described above may be included in the payment app 30, or it may function as a mini-app of the payment app 30. Furthermore, the functional configuration of the payment app 30 may be included in the wallet app 20, or it may function as a mini-app of the wallet app 20.

[0083] The above example described the process when using a prepaid card, but in addition to (or instead of) this, the same process may also be performed when using a credit card or other prepaid electronic payment methods. This can more effectively prevent inappropriate payments from occurring during capture.

[0084] According to the embodiment described above, when a user performs an operation on a user terminal device to use a prepaid electronic payment method via the network, the payment server 100 (or service server 200) obtains information from the user terminal device via the network regarding stores or services that are eligible for electronic payment on the network, and by referring to determination information that associates information indicating whether or not prepaid electronic payment is available with information regarding stores or services, it determines whether or not prepaid electronic payment can be made at the target store, thereby enabling an accurate determination of whether or not electronic payment can be used.

[0085] Although embodiments for carrying out the present invention have been described above using examples, the present invention is not limited in any way to these embodiments, and various modifications and substitutions can be made without departing from the spirit of the present invention. [Explanation of Symbols]

[0086] 10. User terminal device 20 Wallet Apps 30 Payment Apps 100 Payment Servers 111 Acquisition Department 112 Judgment section 114 Information Processing Section 120 Content Provision Department 130 Payment Processing Unit 140 Information Management Department 200 service servers

Claims

[Claim 1] In response to a user performing an operation on a user terminal device to use a network-based prepaid electronic payment system, an acquisition unit acquires information from the user terminal device via the network regarding stores or services that are eligible for electronic payment on the network. By referring to determination information that associates information indicating whether or not the aforementioned prepaid electronic payment method can be used with information about the store or service, A processing unit that determines whether or not the aforementioned prepaid electronic payment can be made at the aforementioned target store, An information processing device equipped with the following features.

Images