Settlement management device, settlement management method, and program

Abstract

To provide a settlement management device, a settlement management method, and a program that allow a user of electronic settlement service to more easily change an upper limit amount set at the time of settlement.SOLUTION: A settlement management device that cooperates with an application program running on a terminal device for a user to provide the user with an electronic settlement service as payment means or remittance means includes: an acquisition unit that acquires identification information for the user and settlement information indicating a settlement amount from the terminal device; and a settlement processing unit that identifies, on the basis of the settlement information, an electronic settlement account which is an account for the user to use the electronic settlement service, and performs settlement processing of the settlement amount on the basis of a charge balance of the electronic settlement account. The settlement processing unit changes, if user approval is obtained when the settlement processing results in an error due to an excess of an upper limit amount related to payment with the charge balance, setting of the upper limit amount and executes the settlement processing.SELECTED DRAWING: Figure 7

Description

[Technical field]

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

[0002] There are electronic payment services available that allow users to make payments from the balance charged to their electronic payment accounts (for example, see Patent Literature 1). In such electronic payment services, various upper limits are set for the use of the services, and measures are sometimes taken to prevent overuse or fraudulent use by making the payment an error if the upper limit is exceeded (or has already been exceeded) at the time of payment. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2022-181886 A Summary of the Invention [Problem to be solved by the invention]

[0004] In conventional technology, when the upper limit amount is exceeded at the time of payment, the payment process is not terminated with an error, but rather the user is asked to change the settings to raise the upper limit amount and then the payment is executed, thereby reducing the possibility of the payment being unsuccessful. However, in this case, the user is required to perform many operations, which is time-consuming.

[0005] The present invention has been made in consideration of these circumstances, and one of its objectives is to provide a payment management device, a payment management method, and a program that enable users of electronic payment services to more easily change the upper limit amount set at the time of payment. [Means for solving the problem]

[0006] One aspect of the present invention is a payment management device that works in cooperation with an application program running on a user's terminal device to provide the user with an electronic payment service as a payment means or remittance means, and includes an acquisition unit that acquires from the terminal device the user's identification information and payment information indicating a payment amount, and a payment processing unit that identifies an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and performs payment processing of the payment amount based on the charge balance of the electronic payment account, wherein if the user's approval is obtained during the payment processing when an error occurs due to the payment exceeding an upper limit amount for payment using the charge balance, the payment processing unit changes the setting of the upper limit amount and executes the payment processing. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide a payment management device, a payment management method, and a program that enable users of electronic payment services to more easily change the upper limit amount set at the time of payment. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. [Diagram 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] 1 is a configuration diagram of a payment server 100 according to a first embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] 13 is a flowchart showing an example of a process for changing a payment upper limit setting or a charge upper limit setting when making an electronic payment by paying the charge balance. [Figure 8]13 is a flowchart showing an example of a process for changing a payment upper limit setting or a charge upper limit setting when making an electronic payment by paying the charge balance. [Figure 9] 13 is a flowchart showing an example of a process for changing a payment upper limit setting or a charge upper limit setting when making an electronic payment by paying the charge balance. [Figure 10] 13A and 13B are diagrams illustrating an example of a first setting change confirmation screen and a second setting change confirmation screen. [Figure 11] 13A and 13B are diagrams illustrating an example of a third setting change confirmation screen and a fourth setting change confirmation screen. [Figure 12] 13A and 13B are diagrams illustrating an example of a fifth setting change confirmation screen and a sixth setting change confirmation screen. [Figure 13] FIG. 13 is a diagram showing an example of screen transition in a conventional electronic payment service. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, with reference to the drawings, an embodiment of the payment management device, the payment management method, and the program of the present invention will be described. The application program and the payment server cooperate to provide an electronic payment service. In the following description, the application program is referred to as a payment application. The electronic payment service is a service that supports payments related to the purchase of goods and services at a store. The store is, for example, a physical store (real store) existing in real space, but may also include a virtual store of electronic commerce. The virtual store may include a store provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, the store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at the store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be performed between the user and the store.

[0010] [Electronic payment service] Fig. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 10, one or more first store terminal devices 50, and one or more second store terminal devices 70 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

[0011] 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 a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0012] 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 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the 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) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. An interface 72 for affiliated stores runs on the second store terminal device 70. The interface 72 for affiliated stores may be an app for affiliated stores or a browser. The interface 72 for affiliated stores accepts coupon settings and the like made by the operator of the affiliated store 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 and reading a code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0014] The payment server 100 realizes 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 an affiliated store server, in which case the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the payment information is sent from the first store terminal device 50.

[0015] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns of electronic payment: pattern 1 and pattern 2.

[0016] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits 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 transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0017] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0018] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0019] [Payment server] FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (storage device having a non-transient storage medium) such as an HDD (Hard Disk Drive) or a flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or a CD-ROM, and may be installed in the storage device by mounting the storage medium in a drive device.

[0020] The storage unit 170 is a HDD, a flash memory, a RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, payment content information 174, and affiliated store / shop information 176.

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

[0022] The payment content providing unit 120 has, for example, a function of a Web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content providing unit 120 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0023] The payment processing unit 130 performs payment processing based on the 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.

[0024] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is, for example, a user URL, an account ID, a telephone number, a password, as well as information associated with an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a post-payment setting, a post-payment limit, a post-payment usage amount, a post-payment available amount, a payment method setting, a bank account, a credit card number, a charge history information, and a payment history information. The user URL is used for a remittance process between users. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, and the name, address, and date of birth are information that can be set by the user at will (does not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0025] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to an account in advance. The means of transfer include transfer from an ATM (Automatic Teller Machine) of a designated company (bank) and transfer from a registered bank account. The deferred payment setting is information indicating whether or not the setting for enabling electronic payment by deferred payment has been completed, and is set to either "completed" or "not completed." The deferred payment limit is the limit of deferred payment that can be used each month, the deferred payment usage amount is the amount of deferred payment that has already been used in the current month, and the deferred payment available amount is the amount of deferred payment that can be used in the current month, which is calculated by subtracting the deferred payment usage amount from the deferred payment limit. Although only one deferred payment limit is shown in the figure, in reality, there is also a daily upper limit, and the lower of these may be set as the deferred payment limit. Further details of deferred payment will be described later. The payment method setting is setting information indicating whether the user will perform electronic payment using the charge balance or payment by deferred payment at that time. The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be used to deposit funds into an electronic payment service. Charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. Payment history information is information that indicates the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0026] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store name and sales amount (described above) are associated with an affiliated store ID, and a third table 176C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the location of the store, and payment patterns.

[0027] The information management unit 140 manages user information 172 and affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, and deletes the user information 172 and affiliated store / store information 176.

[0028] [Electronic payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 to acquire the "payment method setting" of the user. For a user 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 managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0029] The payment processing unit 130 performs electronic payment for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit payment" in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service acts as a creditor and allows electronic payment that is not dependent on the charge balance within the deferred payment limit. In order to receive the deferred payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used for deferred payment is settled on the payment date of the following month, for example, by debiting from a bank account, for one month. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the deferred payment amount and subtracting the same amount from the available deferred payment amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above, or requests the operator of the credit card company to perform such processing. In addition, if the payment amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0030] [Auto Charge] In the following, increasing the balance of electronic money by the above-mentioned remittance means is referred to as "charging", and there are two types of charging: one that is done manually by the user using the payment application 20, and one that is done automatically at the required timing by making settings in advance. Hereinafter, when distinguishing between the two, the former charging method will be referred to as "manual charging" and the latter charging method will be referred to as "auto-charging". For example, the setting means for auto-charging is provided by the payment application 20, and the setting contents are transmitted to the payment server 100. The usage setting for auto-charging may be managed as setting information for each user in the user information 172, for example. The user can activate or deactivate auto-charging by operating the payment application 20.

[0031] [Payment Priority] When multiple payment methods are available, such as payment based on remaining charge or deferred payment, the payment application 20 has a function of automatically selecting a payment method based on a preset priority order of the payment methods (hereinafter referred to as "payment priority order"). For example, a means for setting the payment priority order is provided by the payment application 20, and the setting contents are transmitted to the payment server 100. The setting of the priority order of the payment methods may be managed, for example, as setting information for each user in the user information 172. When multiple payment methods are available, the user can make a payment without having to select a payment method each time by setting the payment priority order in advance.

[0032] [Maximum chargeable amount] In the electronic payment service of the embodiment, the amount a user charges to an electronic payment account (hereinafter also referred to as "wallet") is set with an upper limit on the amount that can be charged within a predetermined period (e.g., one day and / or one month). In the present embodiment, the same upper limit setting is applied to manual charge and auto charge, but different upper limits may be set for manual charge and auto charge. Hereinafter, the upper limit common to manual charge and auto charge is referred to as the "charge upper limit," and the setting is referred to as the "charge upper limit setting." The means for setting the charge upper limit is also provided by the payment application 20, similar to the usage setting for auto charge, and the setting contents are transmitted to the payment server 100. The charge upper limit setting may be managed as setting information for each user in the user information 172, for example.

[0033] 2 and 3, the basic process flow of electronic payment has been explained for the two patterns of user scan and store scan, but in electronic payment (S7 or S17), if the user's charge balance is insufficient for the payment amount, the payment server 100 provides the user with a means to increase the charge balance by manual charge or automatic charge (hereinafter referred to as "payment time charge means"). By the payment server 100 providing such a payment time charge means when the charge balance is insufficient at the time of payment, the user can avoid losing a purchase opportunity due to a failed payment.

[0034] Furthermore, in the above-mentioned charge-at-payment means, when a charge of a specified or set amount cannot be executed due to a charge upper limit, the payment server 100 provides the user with a means for changing the charge upper limit setting. By providing such a means for changing the charge upper limit setting in the charge-at-payment means, the payment server 100 can avoid the user losing a purchase opportunity due to a failed payment.

[0035] [Maximum amount that can be paid] In the electronic payment service of the embodiment, an upper limit is set for the amount a user can pay by electronic payment within a predetermined period (e.g., one day and / or one month). Hereinafter, this upper limit is referred to as the "payment upper limit", and its setting is referred to as the "payment upper limit setting". The means for setting the payment upper limit is also provided by the payment application 20, similar to the charge upper limit setting, and the setting contents are transmitted to the payment server 100. The payment upper limit setting may be managed as setting information for each user in the user information 172, for example.

[0036] The set amounts of the payment limit, charge limit, and auto-charge limit may be freely changed by the user as appropriate through the payment application 20 or a website, or may be preset as initial values ​​in the electronic payment service. The set amounts of the various limits may be selected from a list of set values ​​predefined in the electronic payment service, or may be freely set in units of 1 yen. The set value list may be a list of upper limit amounts in a certain amount range, or may be a list of fixed upper limit amounts such as 10,000 yen, 30,000 yen, 50,000 yen, 100,000 yen, and 200,000 yen. Furthermore, in the electronic payment service of the embodiment, the set amounts of the various limits are each set with an upper limit value (hereinafter referred to as the "settable upper limit amount"), and the user cannot set the set amount of each limit to an amount that exceeds the settable upper limit amount.

[0037] 2 and 3, the basic process flow of electronic payment has been explained for two patterns, user scan and store scan, but if the total payment amount of the user in a given period exceeds the payment upper limit by executing the requested electronic payment (S7 or S17), the payment server 100 provides the user with a means for changing the payment upper limit setting. By providing such a setting change means when the payment upper limit is exceeded at the time of payment, the user can avoid losing a purchasing opportunity due to a failed payment.

[0038] 7 to 9 are flowcharts showing an example of the flow of the process of setting the payment upper limit or changing the charge upper limit setting when making an electronic payment by paying the charge balance. The flowcharts in FIG. 7 to FIG. 9 are executed in the payment process when the payment server 100 accepts a payment request by paying the charge balance (for example, when the user inputs an operation to execute a payment on the payment screen of the payment application 20). In this case, the payment server 100 judges whether or not the user's charge balance is insufficient for the requested payment amount (S201). If it is determined that the charge balance is not insufficient for the payment amount, the payment server 100 then judges whether or not the total payment amount of the user (the total amount of electronic payments of the user during the target period) when the electronic payment being processed is completed reaches the payment upper limit (S202). If it is determined that the total payment amount does not reach the payment upper limit, the payment server 100 executes the payment by the charge balance and completes the user's payment (S203: payment completed).

[0039] On the other hand, if it is determined in S202 that the total payment amount reaches the payment upper limit, the payment server 100 determines whether or not the set amount of the payment upper limit can be changed to the maximum amount that can be paid (S204). The maximum amount that can be paid is the minimum amount of the payment upper limit that should be changed so that the amount to be paid in the electronic payment being processed can be paid. Here, if it is determined that the set amount of the payment upper limit can be changed to the maximum amount that can be paid, the payment server 100 causes the user's payment application 20 to display a first setting change confirmation screen regarding the payment upper limit (S205). The first setting change confirmation screen is a screen for allowing the user to select whether or not to change the set amount of the payment upper limit to the maximum amount that can be paid and continue the payment.

[0040] For example, if the payment upper limit is the upper limit of the amount that can be paid in one day, the payment server 100 judges whether the total of the payment amounts of payments already completed on that day (total payment amount) and the amount to be paid in this payment exceeds the currently set amount of the payment upper limit. In this case, if the total amount exceeds the currently set amount, it proposes raising the payment upper limit, and if the user accepts this proposal, it changes the set amount to the maximum amount that can be paid and completes the payment. In other words, in this case, the maximum amount that can be paid is set to an amount that exceeds the total amount of payments on that day and the amount to be paid in this payment.

[0041] If the user selects to raise the payment upper limit on the first setting change confirmation screen, the payment server 100 changes the set amount of the payment upper limit to the maximum amount that can be paid and then performs the payment process (S206). This completes the user's payment. On the other hand, if the user does not select to raise the payment upper limit on the first setting change confirmation screen, the payment server 100 responds to the payment application 20 that the electronic payment has failed due to exceeding the payment upper limit (S207).

[0042] On the other hand, if it is determined in S204 that the set amount of the payment upper limit cannot be changed to the maximum payable amount, the payment server 100 displays a second setting change confirmation screen regarding the payment upper limit on the user's payment application 20 (S208). Here, as a case where the set amount of the payment upper limit cannot be changed to the maximum payable amount, it is assumed that the set amount of the payment upper limit has already reached the maximum amount that can be set (hereinafter referred to as the "maximum settable payment amount"), and the set amount of the payment upper limit cannot be changed to an amount larger than the current set amount (maximum settable payment amount). The second setting change confirmation screen is a screen for allowing the user to select whether or not to disable the setting of the payment upper limit and continue the payment.

[0043] If the user selects to invalidate the payment upper limit setting on the second setting change confirmation screen, the payment server 100 invalidates the payment upper limit setting and performs the payment process (S209). This completes the user's payment. On the other hand, if the user selects not to invalidate the payment upper limit setting on the second setting change confirmation screen, the payment server 100 responds to the payment application 20 that the electronic payment has failed due to exceeding the payment upper limit (S210).

[0044] As described above, the upper limit of payment may be set as a daily upper limit and a monthly upper limit. In S202 to S210, a process according to the upper limit of payment set may be executed. In addition, when the upper limit of payment is set as a daily upper limit and a monthly upper limit, the process of S202 to S210 may be executed for both upper limits. For example, the payment server 100 may be configured to complete the electronic payment when the total payment amount is less than both upper limits, and to return an error without completing the electronic payment when the total payment amount is equal to or greater than either upper limit, or to change the upper limit of payment to the maximum amount payable with the user's consent and complete the electronic payment. Furthermore, in this case, the payment server 100 may be configured to invalidate the setting of the upper limit of payment with the user's consent and complete the electronic payment when the set amount of the upper limit of payment cannot be changed to the maximum amount payable.

[0045] Return to S201. On the other hand, if it is determined in S201 that the charge balance is insufficient for the payment amount, the payment server 100 then determines whether or not auto-charge is set for the wallet of the user (S211). If it is determined that auto-charge is not set for the wallet of the user, the payment server 100 then determines whether or not the total charge amount of the user in a predetermined period exceeds the charge upper limit (S212). If it is determined that the total charge amount does not exceed the charge upper limit, the payment server 100 accepts a charge operation via the payment application 20 and then performs payment processing (S213). This completes the user's payment.

[0046] On the other hand, if it is determined in S212 that the total recharge amount exceeds the recharge upper limit, the payment server 100 determines whether or not the set amount of the recharge upper limit can be changed to the rechargeable upper limit amount (S214). The rechargeable upper limit amount is the minimum amount of the recharge upper limit to which the amount to be paid in the electronic payment being processed can be paid. Here, if it is determined that the set amount of the recharge upper limit can be changed to the rechargeable upper limit amount, the payment server 100 causes the user's payment application 20 to display a third setting change confirmation screen regarding the recharge upper limit (S215). The third setting change confirmation screen is a screen for allowing the user to select whether or not to change the set amount of the recharge upper limit to the rechargeable upper limit amount and continue the payment.

[0047] For example, if the charge upper limit is the upper limit of the amount that can be charged in one day, the payment server 100 judges whether the total of the deposit amounts from charges already completed on that day (total charge amount) and the charge amount required to complete the current payment exceeds the currently set amount of the charge upper limit. In this case, if the total amount exceeds the currently set amount, it proposes raising the charge upper limit, and if the user accepts this proposal, it changes the set amount to the maximum chargeable amount and completes the payment. In other words, in this case, the maximum chargeable amount is set to an amount that exceeds the total of the charge total for that day and the charge amount required for the current payment.

[0048] If the user selects to increase the recharge limit on the third setting change confirmation screen, the payment server 100 changes the set amount of the recharge limit to the rechargeable upper limit amount and performs the payment process (S216). This completes the user's payment. On the other hand, if the user does not select to increase the recharge limit on the third setting change confirmation screen, the payment server 100 responds to the payment application 20 that the electronic payment has failed due to exceeding the recharge limit (S217).

[0049] On the other hand, if it is determined in S214 that the set amount of the charge limit cannot be changed to the maximum chargeable amount, the payment server 100 displays a fourth setting change confirmation screen regarding the charge limit on the user's payment application 20 (S218). Here, as a case in which the set amount of the charge limit cannot be changed to the maximum chargeable amount, it is assumed that the set amount of the charge limit has already reached the maximum amount that can be set (hereinafter referred to as the "maximum settable charge amount"), and the set amount of the charge limit cannot be changed to an amount greater than the current set amount (maximum settable charge amount). The fourth setting change confirmation screen is a screen for allowing the user to select whether or not to disable the setting of the charge limit and continue the payment.

[0050] If the user selects to disable the charge upper limit setting on the fourth setting change confirmation screen, the payment server 100 performs the payment process after disabling the charge upper limit setting (S219). This completes the user's payment. On the other hand, if the user selects not to disable the charge upper limit setting on the fourth setting change confirmation screen, the payment server 100 responds to the payment application 20 that the electronic payment has failed due to exceeding the charge upper limit (S220).

[0051] As described above, the charge upper limit may be set as a daily charge upper limit and a monthly charge upper limit. In S212 to S220, a process according to the charge upper limit to be set may be executed. In addition, when a daily charge upper limit and a monthly charge upper limit are set as the charge upper limit, the process of S212 to S220 may be executed for both charge upper limits. For example, the payment server 100 may be configured to complete the electronic payment when the total charge amount is less than both upper limit amounts, and to return an error without completing the electronic payment when the total charge amount is equal to or greater than either upper limit amount, or to change the charge upper limit to the chargeable upper limit amount with the user's consent and complete the electronic payment. Furthermore, in this case, the payment server 100 may be configured to invalidate the setting of the charge upper limit with the user's consent and complete the electronic payment when the charge upper limit cannot be changed to the chargeable upper limit amount.

[0052] Return to S211. On the other hand, if it is determined in S211 that the auto-charge setting is set for the wallet of the user, the payment server 100 then determines whether or not the total auto-charge amount of the user for the predetermined period for the auto-charge setting exceeds the auto-charge upper limit (S222). If it is determined that the total auto-charge amount does not exceed the auto-charge upper limit, the payment server 100 executes the auto-charge process to increase the charge balance and then performs the payment process (S223). This completes the user's payment.

[0053] On the other hand, if it is determined in S222 that the auto-charge total amount exceeds the auto-charge upper limit, the payment server 100 determines whether or not the set amount of the auto-charge upper limit can be changed to the auto-chargeable upper limit amount (S224). The auto-chargeable upper limit amount is the minimum amount of the auto-charge upper limit that should be changed so that the amount to be paid in the electronic payment being processed can be paid. Here, if it is determined that the set amount of the auto-charge upper limit can be changed to the auto-chargeable upper limit amount, the payment server 100 causes the user's payment application 20 to display a fifth setting change confirmation screen regarding the auto-charge upper limit (S225). The fifth setting change confirmation screen is a screen for allowing the user to select whether or not to change the set amount of the auto-charge upper limit to the auto-chargeable upper limit amount and continue the payment.

[0054] For example, if the autocharge upper limit is the upper limit of the amount that can be autocharged in one day, the payment server 100 judges whether the total of the deposit amounts by autocharges already completed on the day (total autocharge amount) and the autocharge amount required to complete the current payment exceeds the currently set amount of the autocharge upper limit. In this case, if the total amount exceeds the currently set amount, it proposes raising the autocharge upper limit, and if the user accepts this proposal, it changes the set amount to the autochargeable upper limit amount and completes the payment. In other words, in this case, the autochargeable upper limit amount is set to an amount that exceeds the total of the autocharge total amount on the day and the autocharge amount required for the current payment.

[0055] If the user selects to raise the auto-charge upper limit on the fifth setting change confirmation screen, the payment server 100 changes the set amount of the auto-charge upper limit to the auto-chargeable upper limit amount and performs the payment process (S226). This completes the user's payment. On the other hand, if the user does not select to raise the auto-charge upper limit on the fifth setting change confirmation screen, the payment server 100 responds to the payment application 20 that the electronic payment has failed due to the auto-charge upper limit being exceeded (S227).

[0056] On the other hand, if it is determined in S224 that the set amount of the auto-charge upper limit cannot be changed to the auto-chargeable upper limit amount, the payment server 100 displays a sixth setting change confirmation screen regarding the auto-charge upper limit on the user's payment application 20 (S228). Here, as a case in which the set amount of the auto-charge upper limit cannot be changed to the auto-chargeable upper limit amount, it is assumed that the set amount of the auto-charge upper limit has already reached the upper limit of the amount that can be set (hereinafter referred to as the "settable auto-charge upper limit amount"), and the set amount of the auto-charge upper limit cannot be changed to an amount larger than the current set amount (settable auto-charge upper limit amount). The sixth setting change confirmation screen is a screen for allowing the user to select whether or not to disable the setting of the auto-charge upper limit and continue the payment.

[0057] If the user selects to disable the auto-charge upper limit setting on the sixth setting change confirmation screen, the payment server 100 performs the payment process after disabling the auto-charge upper limit setting (S229). This completes the user's payment. On the other hand, if the user selects not to disable the auto-charge upper limit setting on the sixth setting change confirmation screen, the payment server 100 responds to the payment application 20 that the electronic payment has failed due to exceeding the auto-charge upper limit (S230).

[0058] As described above, the autocharge upper limit may be set as an autocharge upper limit per day and an autocharge upper limit per month. In S222 to S230, processing according to the autocharge upper limit set may be executed. In addition, when an autocharge upper limit per day and an autocharge upper limit per month are set for the autocharge upper limit, the processing of S222 to S230 may be executed for both autocharge upper limits. For example, the payment server 100 may be configured to complete the electronic payment if the autocharge total amount is less than both upper limit amounts, and to return an error without completing the electronic payment if the autocharge total amount is equal to or greater than either upper limit amount, or to change the autocharge upper limit to the autochargeable upper limit amount with the user's consent and complete the electronic payment. Furthermore, in this case, the payment server 100 may be configured to disable the setting of the autocharge upper limit with the user's consent and complete the electronic payment if the autocharge upper limit cannot be changed to the autochargeable upper limit amount.

[0059] In addition, in the explanation of Figs. 7 to 9, it is assumed that the set amount of the charge upper limit and the set amount of the auto-charge upper limit are different settings, but they may be the same amount, or the settings of both may be the same. Similarly, the set amount of the charge upper limit and the set amount of the auto-charge upper limit may be the same amount, or the settings of both may be the same. Furthermore, the total charge amount may be the sum of the amount charged manually, or the sum of the amount charged by manual charge and auto-charge. Similarly, the total auto-charge amount may be the sum of the amount charged by auto-charge, or the sum of the amount charged by manual charge and auto-charge.

[0060] FIG. 10 is a diagram showing an example of the first setting change confirmation screen M11 and the second setting change confirmation screen M12. In FIG. 10, the screen M13 is an example of a payment confirmation screen. The payment confirmation screen M13 is an example of a screen where the user inputs the payment amount in the user scan method, and is a screen displayed in the payment application 20 in S5 of FIG. 2, for example. The payment confirmation screen M13 in the example of FIG. 10 shows a situation where the charge balance is 500000 yen, the point balance (999 points) is set for use, and the user inputs 60000 yen as the payment amount. In this situation, the total payment amount of the user is in a state where it would exceed the payment upper limit if the payment was made according to the contents of the payment confirmation screen M13. Here, when the user operates the payment button BT11, payment information is transmitted to the payment server 100, and the payment server 100 executes the payment process. At this time, the payment server 100 recognizes that the total payment amount of the user will exceed the payment upper limit due to the payment, and responds to that effect to the payment application 20. Screen M11 is an example of a first setting change confirmation screen that payment application 20 displays in response to this response.

[0061] FIG. 10 shows a case where the first setting change confirmation screen M11 is displayed in front of the payment confirmation screen M13 in the form of a so-called half sheet. The first setting change confirmation screen M11 may be displayed with a visual effect of rising from the lower screen edge of the payment confirmation screen M13. The first setting change confirmation screen M11 includes, for example, a payment impossible message MG11, a payment upper limit change button BT12, and a payment cancellation button BT13. The payment impossible message MG11 is a message notifying the user that the total payment amount of the day exceeds the daily payment upper limit and the requested electronic payment cannot be made. The payment upper limit change button BT12 is a button that accepts an input operation to change the set amount of the payment upper limit to the maximum amount that can be paid and continue the payment. The payment upper limit change button BT12 may display text indicating details of the change, such as "change the available amount to X yen and pay". The payment cancellation button BT13 is a button that accepts an operation to cancel the payment. On the first setting change confirmation screen M11, when the change payment upper limit button BT12 is operated, the payment application 20 displays a payment completion screen M14, and when the cancel payment button BT13 is operated, the payment application 20 displays a payment cancellation screen M15.

[0062] For example, suppose that the set amount of the daily payment limit is set to 100,000 yen, and the current total amount of payment for the day is 70,000 yen. In this case, if the payment for the current payment is 60,000 yen, the total amount of payment for the day will be 130,000 yen, which exceeds the current set amount of 100,000 yen. In this case, the payment server 100 proposes raising the payment limit so that the payment of 130,000 yen can be made. For example, if the set amount list of the payment limit is defined in increments of 50,000 yen, the payment server 100 proposes raising the current upper limit of 100,000 yen to 150,000 yen, which is one level higher. Then, if the user approves this proposal, the payment server 100 changes the set amount of the payment limit from 100,000 yen to 150,000 yen and completes the payment. In this case, the payment limit change button BT12 may display text indicating details of the change, such as "change the available amount to 150,000 yen and pay". The payment limit change button BT12 may display both the current set amount and the changed set amount.

[0063] On the other hand, in the situation when payment button BT11 is operated, if the set amount of the payment upper limit is the settable payment upper limit amount, it recognizes that there is no option for a settable payment upper limit and responds to that effect to payment application 20. Screen M12 is an example of a second setting change confirmation screen that payment application 20 displays in response to this response.

[0064] FIG. 10 shows a case where the second setting change confirmation screen M12 is displayed in front of the payment confirmation screen M13 in the form of a so-called half sheet. The second setting change confirmation screen M12 may be displayed with a visual effect of rising from the lower screen edge of the payment confirmation screen M13, similar to the first setting change confirmation screen M11. The second setting change confirmation screen M12 includes, for example, a payment impossible message MG12, a payment upper limit invalidation button BT14, and a payment cancellation button BT15. The payment impossible message MG12 is a message notifying the user that the total payment amount of the day exceeds the daily payment upper limit and the requested electronic payment cannot be made, and that the payment upper limit setting needs to be invalidated to execute the electronic payment. The payment upper limit invalidation button BT14 is a button that accepts an input operation to invalidate the payment upper limit setting and continue the payment. The payment cancellation button BT15 is a button that accepts a payment cancellation operation, similar to the payment cancellation button BT13. On the second setting change confirmation screen M12, when the disable payment upper limit button BT14 is operated, the payment application 20 displays a payment completion screen M16, and when the cancel payment button BT15 is operated, the payment application 20 displays a payment cancellation screen M17.

[0065] In the examples of Figures 7 to 9, a case has been described in which the upper limit setting is invalidated with the user's consent when an increase in various upper limits exceeds the settable upper limit amount. In this case, however, the payment server 100 may be configured to immediately return a payment error to the payment application 20 without proposing invalidation of the upper limit setting.

[0066] FIG. 11 is a diagram showing an example of a third setting change confirmation screen M21 and a fourth setting change confirmation screen M22. FIG. 12 is a diagram showing an example of a fifth setting change confirmation screen M31 and a sixth setting change confirmation screen M32. The third to sixth setting change confirmation screens are similar in basic display form to the first and second setting change confirmation screens. More specifically, the third and fifth setting change confirmation screens correspond to the first setting change confirmation screen, and can be understood by replacing the payment upper limit in FIG. 10 with the charge upper limit. The fourth and sixth setting change confirmation screens correspond to the second setting change confirmation screen, and can be understood by replacing the payment upper limit in FIG. 10 with the auto-charge upper limit.

[0067] For example, suppose that the set amount of the charge limit for one day is set to 100,000 yen, and the current total charge amount for one day is 70,000 yen. In this case, if a payment of 60,000 yen is made in this payment, the total charge amount for one day will be 130,000 yen, which exceeds the current set amount of 100,000 yen. In this case, the payment server 100 proposes raising the charge limit so that a payment of 130,000 yen can be made. For example, if the set amount list of the charge limit is defined in increments of 50,000 yen, the payment server 100 proposes raising the current limit of 100,000 yen to 150,000 yen, which is one level higher. Then, if the user approves this proposal, the payment server 100 changes the set amount of the charge limit from 100,000 yen to 150,000 yen and completes the payment. In this case, the charge limit change button on the third setting change confirmation screen M21 may display either the current set amount or the changed set amount, or both. The aspect of changing the setting of the charge limit described here may also be applied to the auto charge limit.

[0068] 10 to 12, when an error occurs during a payment process for processing a payment request, the first, third, and fifth setting change confirmation screens allow the set amount to be increased during the payment process. In this way, when a violation of the various upper limit amounts that caused the payment error occurs, the upper limit setting can be changed on the spot and the payment process can be retried, thereby reducing the possibility that the user will give up on the opportunity to make an electronic payment.

[0069] Fig. 13 is a diagram showing an example of screen transitions in a case where a user changes the set amount of the payment upper limit and completes the payment when a payment error occurs due to exceeding the payment upper limit in a conventional electronic payment service. More specifically, Fig. 13 shows the transition of screens of the payment application 20 in the following order: a payment confirmation screen M91, a payment upper limit exceeding error screen M92, a confirmation screen M93 of the set amount of the payment upper limit (per day), a selection screen M94 of the set amount of the payment upper limit (per month), an SMS (Short Message Service) authentication screen M96, and a payment completion screen M97.

[0070] Thus, in the conventional flow of electronic payment, when a payment error occurs due to exceeding the payment limit and the user tries to continue the payment by changing the payment limit setting amount, many screen transitions occur before the payment is completed, and the user has to perform many operations. For example, in addition to sending each screen, the user has to select the new setting amount from a list of setting amount candidates and perform identity verification processing to change the setting (SMS authentication in the example of Figure 13). Also, in the example of Figure 13, for example, five screen transitions occur between the payment confirmation screen and the payment completion screen, and in SMS authentication, the user also has to confirm the contents of the notification sent to the registered phone number.

[0071] In contrast, according to the electronic payment service of this embodiment, when a payment error occurs due to exceeding the payment limit, the user can appropriately raise the current payment limit to a level at which the payment related to the payment error is possible, and complete the payment. In this case, the user must perform an operation to agree (approve) to change the set amount of the payment limit to the maximum amount that can be paid and make the payment. Therefore, the user can recover from the payment error due to exceeding the payment limit quickly and easily, and complete the payment.

[0072] That is, according to the embodiment described above, it is possible for users of electronic payment services to more easily change the upper limit amount when making a payment. In Fig. 13, a case where the upper limit amount for payment is changed is described, but as can be seen from Figs. 11 and 12, the electronic payment service of the embodiment also enables similar recovery of the charge upper limit and auto-charge upper limit.

[0073] <Modification> Screen display by the payment application 20 may be controlled solely by the payment application 20 itself, or may be controlled in cooperation with the payment application 20 and the payment server 100. In the former case, the payment application 20 may switch the display screen by appropriately selecting a display target from screen data stored in the user terminal device 10. In the latter case, the payment server 100 may supply information required for screen display to the payment application 20. The payment server 100 may supply the screen data itself to the payment application 20, or may supply information required for generating a screen to the payment application 20. For example, the payment application 20 may generate a display screen by combining screen format data stored in the user terminal device 10 with information supplied from the payment server 100.

[0074] In the above embodiment, a method for changing the set amounts of various upper limits when a payment error occurs mainly in the user scan method has been described, but changing the set amounts of various upper limits when a payment error occurs may be performed not only in the user scan method but also in the store scan / store scan method. For example, in the example of Fig. 3, when a payment error occurs in the electronic payment of S17 due to exceeding the upper limit, the payment server 100 may be configured to notify the payment application 20 of the payment error instead of the payment completion notification of S18 and to display an upper limit exceeding error screen, and thereafter to change the set amounts in the same manner and re-execute the payment process.

[0075] The amount set as the upper limit of payment may be selected from a list of preset amounts. In this case, the upper limit of payment may be any of the set amounts that can be selected to enable the user to make payments by electronic payment, but in order not to raise the payable amount more than necessary, it is typically assumed that the minimum of the set amounts that can be selected is set as the upper limit of payment. (Example of changing payment limit settings) Current payment limit: 10,000 yen Total amount currently paid by users: 9,000 yen - Amount the user is trying to pay by electronic payment: 2,500 yen The maximum payment amount setting list has the following amounts defined: 10,000 yen, 12,000 yen, 14,000 yen, and 16,000 yen. For example, in the situation of the above setting change example, 12,000 yen, 14,000 yen, or 16,000 yen, which are greater than the total payment amount of 11,500 yen after settlement, can be selected as the new payment upper limit, and typically the minimum amount of 12,000 yen would be selected.

[0076] Also, instead of selecting the new payment upper limit from a list of set amounts, the user may be allowed to specify and set the new payment upper limit at any amount as long as the amount the user is about to pay becomes payable by changing the payment upper limit. Also, the new payment upper limit may be set to an amount obtained by increasing the current set amount by the amount that is insufficient for the settlement amount the user is about to pay. For example, in the above setting change example, the new payment upper limit may be set to 11,500 yen, which is an increase of the current payment upper limit of 10,000 yen by the amount of 1,500 yen that is insufficient for the amount of 2,500 yen that the user is about to pay.

[0077] The set amounts of the various upper limits changed via the first to sixth setting change confirmation screens may be continued as they are, or may be set as valid only for the payment that triggered the setting change. The set amounts of the various upper limits that have been changed may be returned to the original set amounts at a predetermined timing, or may be changed to an amount closer to the original set amounts. The original set amount may be the set amount immediately before the change, or may be the maximum amount among the set amounts before the change. The setting change may be reversed, for example, by the payment processing unit 130 or by the information management unit 140.

[0078] The third to sixth setting change confirmation screens regarding the excess of the charge upper limit or the auto-charge upper limit may be configured to present other available payment methods in addition to accepting an approval operation to continue the payment by changing the set amount of each upper limit. For example, if post-payment is possible, the third to sixth setting change confirmation screens may be configured to notify that effect, or to provide a means to change the payment method to post-payment. Furthermore, the third to sixth setting change confirmation screens may be configured as screens that display both options, allowing the user to select either the setting change of the upper limit amount or the change of the payment method. In addition, if the user is able to use multiple payment methods and priorities are set for them, the payment server 100 may be configured to automatically select the payment method with the highest priority based on the user's pre-setting and make the payment. In this case, the payment server 100 may determine the other available payment methods to present on the third to sixth setting change confirmation screens based on the priorities.

[0079] In the above embodiment, the total payment amount used to determine whether the payment limit has been exceeded may be the total payment amount paid by any of the payment methods available in the electronic payment service, or the total payment amount paid from the charge balance by any of the payment methods available in the electronic payment service.

[0080] The electronic payment service of the above embodiment provides a user with a payment means by electronic payment, but may also provide a remittance means by a similar electronic payment mechanism. For example, the remittance means may be realized by making the recipient of the payment amount, instead of the affiliated store, another user who has an electronic payment account with the same electronic payment service in the above embodiment. In this case, as with electronic payment as a payment means, various upper limit amounts may be set for the remittance means. For example, an upper limit may be set for the amount that can be remitted in a specified period, or an upper limit may be set for the amount that can be charged for remittance or the amount that can be automatically charged. In this case, the upper limit amount for the remittance means may also be changed in the same manner as for the payment means. Furthermore, the setting of various upper limit amounts may be common to the payment means and the remittance means.

[0081] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0082] 10 User terminal device 20. Payment App 50 First store terminal device 60 Store Code Image 70 Second store terminal device 72 Merchant Interface 100 Payment Server 110 Communications Department 120 Payment Contents Provider 130 Payment processing unit 140 Information Management Department 170 Storage section 172 User information 174 Payment Content Information 176 Affiliated Stores / Store Information

Claims

1. A payment management device that provides an electronic payment service as a payment means or a remittance means to a user in cooperation with an application program that runs on a user's terminal device, an acquisition unit that acquires identification information of the user and payment information indicating a payment amount from the terminal device; a payment processing unit that identifies an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and performs payment processing of the payment amount based on the charge balance of the electronic payment account; Equipped with When the charge balance is not insufficient for the payment amount and the total amount of payments made using the electronic payment service in a predetermined period of time exceeds a predetermined upper limit amount, the payment processing unit changes the setting of the upper limit amount based on an approval operation by the user and executes the payment processing. Payment management device.

2. the method of charging the balance of the electronic payment account includes a first charging method which is executed by the payment management device through manual operation by the user, and a second charging method which is executed by the payment management device based on settings by the user without manual operation by the user; the predetermined upper limit amount includes an upper limit amount that the user can charge to the balance of the electronic payment account during the predetermined period, the payment processing unit, when the charge balance is insufficient for the payment amount and the use setting of the second charge method is not set, changes the setting of the charge upper limit amount based on an approval operation of the user, and executes the payment processing. The payment management device according to claim 1 .

3. A payment management device that provides an electronic payment service as a payment means or a remittance means to a user in cooperation with an application program that runs on a user's terminal device, an acquisition unit that acquires identification information of the user and payment information indicating a payment amount from the terminal device; a payment processing unit that identifies an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and performs payment processing of the payment amount based on the charge balance of the electronic payment account; Equipped with An upper limit is set for the total amount of use for a specified period related to the use of the electronic payment service, which can be selected from a plurality of predetermined options; the payment processing unit, when the total usage amount in the predetermined period exceeds the upper payment limit amount, changes a setting of the upper limit amount of the total usage amount based on an approval operation of the user, and executes the payment processing; The total usage amount is a payment upper limit amount, which is the upper limit of the amount that the user can pay using the charge balance in a specified period, or a charge upper limit amount, which is the upper limit of the amount that the user can charge to the balance of the electronic payment account in a specified period. Payment management device.

4. the payment processing unit determines the changed upper limit payment amount based on the past payment amounts of the user and the payment amounts included in the payment information; The payment management device according to claim 3.

5. The payment processing unit determines the changed upper charge limit amount based on the past charge amount of the user and the payment amount included in the payment information. The payment management device according to claim 3.

6. A payment management device that provides an electronic payment service as a payment means or a remittance means to a user in cooperation with an application program that runs on a user's terminal device, an acquisition unit that acquires identification information of the user and payment information indicating a payment amount from the terminal device; a payment processing unit that identifies an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and performs payment processing of the payment amount based on the charge balance of the electronic payment account; Equipped with An upper limit is set for the total amount of use for a specified period related to the use of the electronic payment service, which can be selected from a plurality of predetermined options; the payment processing unit, when a total amount of use for the predetermined period exceeds the upper limit amount, changes a setting of the upper limit amount based on an approval operation of the user, and executes the payment processing; The payment processing unit determines the smallest amount that is greater than the total amount of use from among the multiple options, as the changed upper limit amount. Payment management device.

7. The predetermined period is a period of one day or one month. The payment management device according to any one of claims 1, 3 and 6.

8. When the upper limit amount before the change is already the maximum amount among the multiple options and the upper limit amount cannot be increased any more, the payment processing unit invalidates the setting of the upper limit amount based on an approval operation of the user and executes the payment processing.

7. The payment management device according to claim 3 or 6.

9. When the upper limit amount is changed, the settlement processing unit returns the changed upper limit amount to the upper limit amount before the change at a predetermined timing, or changes the changed upper limit amount to an amount closer to the upper limit amount before the change. The payment management device according to any one of claims 1, 3 and 6.

10. a payment management device which cooperates with an application program running on a user's terminal device to provide the user with an electronic payment service as a payment means or a remittance means, acquiring identification information of the user and payment information indicating a payment amount from the terminal device; Identifying an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and performing a payment process for the payment amount based on the charge balance of the electronic payment account; 1. A payment management method, comprising: In the payment process, if the charge balance is not insufficient for the payment amount and the total amount of payments made using the electronic payment service in a predetermined period exceeds a predetermined upper limit amount, the setting of the upper limit amount is changed based on an approval operation by the user and the payment process is executed. Payment management methods.

11. a payment management device which cooperates with an application program running on a user's terminal device to provide the user with an electronic payment service as a payment means or a remittance means, acquiring identification information of the user and payment information indicating a payment amount from the terminal device; Identifying an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and performing a payment process for the payment amount based on the charge balance of the electronic payment account; 1. A payment management method, comprising: An upper limit is set for the total amount of use for a specified period related to the use of the electronic payment service, which can be selected from a plurality of predetermined options; When the total usage amount in the predetermined period exceeds the upper payment limit amount in the payment process, a setting of the upper payment limit amount of the total usage amount is changed based on an approval operation of the user, and the payment process is executed. Payment management methods.

12. a payment management device which cooperates with an application program running on a user's terminal device to provide the user with an electronic payment service as a payment means or a remittance means, acquiring identification information of the user and payment information indicating a payment amount from the terminal device; Identifying an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and performing a payment process for the payment amount based on the charge balance of the electronic payment account; 1. A payment management method, comprising: An upper limit is set for the total amount of use for a specified period related to the use of the electronic payment service, which can be selected from a plurality of predetermined options; in the payment process, if the total amount used during the specified period exceeds the upper limit amount, the setting of the upper limit amount is changed based on an approval operation of the user, and the payment process is executed; determining the smallest amount among the multiple options that is greater than the total amount of use as the changed upper limit amount; Payment management methods.

13. A payment management device that provides an electronic payment service as a payment means or a remittance means to a user in cooperation with an application program that runs on the user's terminal device, acquiring, from the terminal device, identification information of the user and payment information indicating a payment amount; Identifying an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and executing a payment process for the payment amount based on the charge balance of the electronic payment account. A program for: when the total amount of payments settled using the electronic payment service during a predetermined period exceeds a predetermined upper limit amount, the setting of the upper limit amount is changed based on an approval operation by the user, and the payment processing is executed; Program for.

14. A payment management device that provides an electronic payment service as a payment means or a remittance means to a user in cooperation with an application program that runs on the user's terminal device, acquiring, from the terminal device, identification information of the user and payment information indicating a payment amount; Identifying an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and executing a payment process for the payment amount based on the charge balance of the electronic payment account; A program for: An upper limit is set for the total amount of use for a specified period related to the use of the electronic payment service, which can be selected from a plurality of predetermined options; in the payment process, when the total usage amount in the specified period exceeds the upper payment limit amount, a setting of the upper limit amount of the total usage amount is changed based on an approval operation of the user, and the payment process is executed; The total usage amount is a payment upper limit amount, which is the upper limit of the amount that the user can pay using the charge balance in a specified period, or a charge upper limit amount, which is the upper limit of the amount that the user can charge to the balance of the electronic payment account in a specified period. program.

15. A payment management device that provides an electronic payment service as a payment means or a remittance means to a user in cooperation with an application program that runs on the user's terminal device, acquiring, from the terminal device, identification information of the user and payment information indicating a payment amount; Identifying an electronic payment account, which is an account for the user to use the electronic payment service, based on the payment information, and executing a payment process for the payment amount based on the charge balance of the electronic payment account; A program for: An upper limit is set for the total amount of use for a specified period related to the use of the electronic payment service, which can be selected from a plurality of predetermined options; In the payment process, if the total amount used during the specified period exceeds the upper limit amount, the setting of the upper limit amount is changed based on an approval operation by the user, and the payment process is executed; determining the smallest amount that is greater than the total amount of use among the multiple options as the changed upper limit amount; Program for.

Images