JP7372492B1 - Payment management device, payment management method, and application program - Google Patents

Abstract

The present invention provides a payment management device, a payment management method, and an application program that can improve the convenience of electronic payment services. [Solution] A storage unit that stores correspondence information between one or more fund sources possessed by a first user and one or more second users, and a payment processing unit that executes payment processing of the electronic payment service. and a second user is a user who is permitted to use the first user's fund source in payment using the electronic payment service, and the payment processing unit comprises the first user's fund source in response to receiving a notification from the second user's terminal device that the second user has accepted the use of the first user's fund source; Increase the balance of the second user's electronic payment account from , and execute electronic payment using the balance of the second user's electronic payment account in response to a payment request from the second user's terminal device. A payment management device. [Selection diagram] Figure 1

Description

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

Conventionally, a user terminal device or store terminal device generates payment information based on information read from a two-dimensional code and sends it to a payment server, and the payment server receives the payment from the user terminal device or store terminal device. An electronic payment system that executes payment processing based on information has been put into practical use (for example, see Patent Document 1).

Japanese Patent Application Publication No. 2023-005816

With conventional technology, users (such as children) who do not have a fund source other than cash, such as a credit card or bank account, have to use an ATM to deposit cash into their electronic payment account, which is time-consuming. It was something.

The present invention has been made in consideration of such circumstances, and one of the objects is to provide a payment management device, a payment management method, and an application program that can improve the convenience of electronic payment services. do.

One aspect of the present invention is a payment management device that provides an electronic payment service to a user in cooperation with an application program running on a user's terminal device, the payment management device providing an electronic payment service to a first user. a storage unit that stores correspondence information between any one or more fund sources registered as payment methods in the electronic payment service and one or more second users; a payment processing unit that executes payment processing, and the second user is a user who is permitted to use the first user's fund source in payment using the electronic payment service. , the payment processing unit, in response to receiving a notification from the second user's terminal device that the second user has accepted to use the first user's fund source. increase the balance of the second user's electronic payment account from the first user's fund source, and increase the balance of the second user's electronic payment account from the first user's fund source, and increase the balance of the second user's electronic payment account in response to the payment request from the second user's terminal device. This is a payment management device that executes electronic payments using the balance of a person's electronic payment account.

One aspect of the present invention is an application program that operates on a user's terminal device and cooperates with the above-described payment management device to provide the user with an electronic payment service, the application program an application program that acquires the total amount paid by the second user from the balance added from the fund source from the payment management device and displays it on the terminal device of the first user for each of the users; It is.

According to one aspect of the present invention, it is possible to provide a payment management device, a payment management method, and an application program that can improve the convenience of electronic payment services.

1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. FIG. 1 is a sequence diagram (Part 1) illustrating the general flow of electronic payment. FIG. 2 is a sequence diagram (Part 2) illustrating the general flow of electronic payment. 1 is a configuration diagram of a payment server 100. FIG. 3 is a diagram showing an example of the contents of user information 172. FIG. It is a diagram showing an example of the contents of member store/store information 176. 3 is a diagram showing an example of the contents of family information 178. FIG. FIG. 3 is a sequence diagram illustrating an example of the flow of processing executed by the payment application 20 and the payment server 100 in cooperation with each other regarding family payment settings. It is a figure which shows the example of a display of a payment method management screen. It is a figure which shows the example of a display of an administrator's wallet screen. FIG. 6 is a diagram illustrating a display example of a family setting screen. It is a figure which shows the example of a display of a family member's wallet screen. It is a figure which shows the example of a display of a family balance screen.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of a payment management device, a payment management method, and an application program control method of the present invention will be described below with reference to the drawings. The application program and the payment server work together to provide electronic payment services. In the following description, the application program will be referred to as a payment application. An electronic payment service is a service that supports payments for purchases of products and services at stores. A store is, for example, a physical store (actual store) that exists in real space, but may also include a virtual store for electronic commerce. Virtual stores may include those provided by entities different from the operator of the electronic payment service. In this case, when paying for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to a member store (brand), for example, and processing such as payment when a purchase is made at a store is mainly performed between a user and the member store. Alternatively, processing such as payment may be performed between the user and the store.

[Electronic payment service]
FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by the payment server 100. The payment server 100 communicates with each of the one or more user terminal devices 10, the one or more first store terminal devices 50, and the one or more second store terminal devices 70, for example, via the 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.

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, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), and the like. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, so that the payment application 20 operates in cooperation with the payment server 100 to provide electronic payment services to the user. The payment application 20 is installed on the user terminal device 10 from an application store, for example, and controls a camera, a communication device, a touch panel, and the like.

The first store terminal device 50 is installed in a store, for example. 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 POS device may realize a product price acquisition function and an optical reading function. The store code image 60 is placed in a store, and a code image such as a QR code (registered trademark) is printed on a paper or plastic medium. Note that the store code image 60 may be displayed on a display (or a display of a terminal device such as a smartphone) placed in the store.

The second store terminal device 70 is used by an operator of a member store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. In the second store terminal device 70, an interface 72 for member stores operates. The member store interface 72 may be an application for member stores or may be a browser. The member store interface 72 receives coupon settings and the like from the member 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 the store code image and reading the code image displayed by the user terminal device 10 by executing an application for member stores. have

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 a member store server, in which case payment information is transmitted from the POS device to the payment server 100 via the member store server. In the following description, it is assumed that payment information is transmitted from the first store terminal device 50 without making any particular distinction.

2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns, pattern 1 and pattern 2, in electronic payment.

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 using an optical reading function (S1). The store code image 60 includes information on a store URL (Uniform Resource Locator). This store URL is the domain of the electronic payment service added with information that can identify the store, and is associated with member store IDs, store IDs, etc. in the payment server 100 (described later). The payment application 20 transmits 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 member store ID and store ID corresponding to the store URL, obtains the member store name and store name information (S3), and sends the information to the payment application 20 (S4). . The user inputs the payment amount into the user terminal device 10 on the screen on which the member store name and 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). Then, the payment server 100 transmits a payment completion notification (information for displaying the 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 placed in a 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 for the user to input the payment amount is omitted, and the first payment information includes information on the payment amount and is sent to the payment server 100. Information on the member store name and store name may be included and displayed on the payment completion screen.

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 on the payment application 20, and when the automatic update timing (for example, every minute) is reached. , and at other timings, the payment application 20 transmits a one-time code issuance request to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment application 20 (S13). The payment application 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds up (presents) the display surface of the user terminal device 10 to the first store terminal device 50, and the first store terminal device 50 decodes the code image using an optical reading function and obtains a one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including a one-time code, payment amount, member store ID, store ID, etc., and transmits it to the payment server 100 (S16). Information on the payment amount is obtained in advance by barcode reading, manual input, etc. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). Then, the payment server 100 transmits a payment completion notification to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

Note that electronic payment may be performed using only one of the above patterns. Moreover, the "account ID" explained in FIG. 2 may be other information (for example, a telephone number) that can be used as user identification information. Furthermore, the 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 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.

[Payment server]
FIG. 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication section 110, a payment content providing section 120, a payment processing section 130, an information management section 140, and a storage section 170. 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 are hardware (circuit parts) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit). (including circuitry), or may be realized by collaboration between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage device such as a DVD or CD-ROM. It may be stored in a medium (non-transitory storage medium), and installed in the storage device by loading the storage medium into a drive device.

The storage unit 170 is an HDD, flash memory, RAM (Random Access Memory), or the like. The storage unit 170 may be a NAS (Network Attached Storage) device that can be accessed by the payment server 100 via a network. The storage unit 170 stores information such as user information 172, payment content information 174, member store/store information 176, and family information 178.

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

The payment content providing unit 120 has, for example, the function of a web server, and provides the user terminal device 10 with information (content) for displaying various screens of the electronic payment service. The payment content providing unit 120 reads necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 receives various inputs from 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.

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 user information 172, family information 178, and the like.

FIG. 5 is a diagram showing an example of the contents of the user information 172. User information 172 is an example of user registration information. User information 172 includes, for example, user URL, account ID, phone number, password, email address, user ID, name/address/date of birth, registration date, charge balance, deferred payment setting, deferred payment limit, deferred payment. Information such as usage amount, available deferred payment amount, payment method settings, bank account, credit card number, charge history information, payment history information, family payment settings, family payment balance, etc. are associated with each other. The user URL is used for remittance processing between users. When registering for a new electronic payment service, it is mandatory to register a phone number and password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be arbitrarily set (or does not need to be set) by the user. Similarly, e-mail address, name, address, and date of birth are information that can (or does not need to be) set arbitrarily by the user. The registration date is the date the user registered with the electronic payment service (the date the account was created). Hereinafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

The charge balance is information indicating the balance of electronic money set by the user transferring money to the account in advance. Methods of remittance include remittance from an ATM (Automatic Teller Machine) of a designated business (bank), remittance from a registered bank account, etc. The deferred payment setting is information indicating whether the settings for enabling electronic payment by deferred payment have been completed, and is set to either "completed" or "not yet". The deferred payment allowance is the maximum amount 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 available deferred payment amount is calculated by subtracting the deferred payment usage amount from the deferred payment allowance. , is the amount of deferred payment available for the current month. In the figure, only one deferred payment limit is shown, but in reality, there are additional daily upper limit amounts, and the lower of these may be set as the deferred payment limit. Further details of deferred payment will be discussed later. The payment method setting is setting information that indicates 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 each information about a bank account or credit card number (account number, card number) that can be used to deposit money into the electronic payment service. The charging history information is a history of the user increasing the charging balance by remitting money to the electronic payment service in advance. The payment history information is information that shows the details of the payments made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each payment.

Family payment settings are information on various parameters that can be set for each user regarding family payment. Here, "Family Payment" refers to a service that allows a user who is the owner of a fund source (hereinafter referred to as "administrator") to make electronic payments using his or her own fund source to other users who have given permission in advance. This is the payment method. With Family Payment, other users can charge their own electronic payment account (hereinafter sometimes referred to as "Wallet") with the balance within the range set by the administrator. Although the balance charging method for family payment is different from normal balance payment, the process of paying the price from the charge balance may be realized by the same process as for normal balance payment without using family payment.

Hereinafter, a group of users set to enable family payments will be referred to as a "family", and users belonging to the family will be referred to as "family members". Note that the family may be a group of users (family members) who are permitted by the administrator to use their own payment means, and does not necessarily correspond to an actual family structure. For example, a family may be configured as a group of friends or colleagues, or may be configured as members of a specific group (for example, room sharing, study group, online salon, project, etc.). The administrator may set up multiple families. Additionally, the administrator may define families in which some or all of the family members overlap among multiple families. The administrator may also set families so that some or all payment methods overlap among multiple families. The administrator is an example of a "first user," and the family member is an example of a "second user."

For example, family payment settings include information such as the family payment setting status, the family to which the user belongs, the type of user in the family (e.g., administrator or family member), and the maximum family payment amount. It will be done. The family payment upper limit amount is the upper limit set for the total amount that a user can use for family payment payments. The family payment balance is the balance of the amount that the user can use for family payment payments.

The family payment upper limit amount is set in advance by the administrator for each family member of each family, and is set as the total amount available for use in a predetermined set period (for example, every month). The length and range of the setting period may be fixed values or may be variable values that can be set by the administrator. The family payment balance will be reset to the family payment maximum amount every set period. Note that the remaining family payment balance at the time of reset may be carried over to the balance of the next setting period, or may be reset to zero. Furthermore, the administrator may be able to change whether or not the data is carried over at the time of reset by setting.

The family payment balance is appropriately updated by the information management unit 140 when a family member makes a payment using family payment. In addition, when a family member of the family selects family payment as a payment method at the time of payment, the payment processing unit 130 refers to the family payment balance at that time of the family member and calculates the family payment balance for the payment amount. If the amount is sufficient, the payment is executed, and if the amount is insufficient, an error is returned to the payment application 20.

FIG. 6 is a diagram showing an example of the contents of the affiliated store/store information 176. The affiliated store/store information 176 includes, for example, a first table 176A in which affiliated store IDs and store IDs are associated with store URLs, and affiliated store names and sales proceeds (described above) are associated with affiliated store IDs. 176B, and a third table 176C in which store IDs are associated with store IDs. In addition to this information, the member store/store information 176 may include information such as the member store or store category, store location, payment pattern, and the like.

FIG. 7 is a diagram showing an example of the contents of the family information 178. The family information 178 is managed by, for example, a table in which family IDs are associated with family names, family members, payment methods, and administrator IDs. The family ID is identification information for each family. The family ID is uniquely assigned, for example, when the family is created. A family name is a name that can be arbitrarily given to a family. The family name may be designated, for example, by an administrator when creating a family, or may be changed when changing family settings. A family member represents a family member belonging to the family. Family members are selected by the administrator when creating the family. Family members may be changed (added or deleted) by the administrator as appropriate. The payment method is the payment method set to be used for family payments related to the family. The payment method is selected from among the payment methods using the administrator's fund source. The administrator ID is identification information of a user (administrator) who has family management authority. Note that FIG. 7 shows an example in which family member and administrator IDs are managed using the account IDs illustrated in FIG. May be managed.

The information management unit 140 manages user information 172 and member 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, edits, deletes, etc. new records for the user information 172 and member store/store information 176.

[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 and acquires the "payment method setting" of the user. The payment processing unit 130 performs electronic payment as follows for a user whose "payment method setting" is set to "charge balance". The payment processing unit 130 performs electronic payment by, for example, decreasing the charge balance managed in association with the user ID and increasing the item value of the member store's sales proceeds. For example, the item value of the sales proceeds of a member store is not used as electronic money itself, but the amount corresponding to the item value of the sales proceeds is determined in a cycle according to the agreement between the member store and the electronic payment service. Money will be transferred to your bank account.

The payment processing unit 130 performs electronic payment in the following manner for users whose "setting information" is set to "deferred payment." Deferred payment is set up separately from "credit payment" in collaboration 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 is the creditor. , which allows electronic payments that do not depend on the charge balance within the deferred payment limit. Note that in order to receive the deferred payment service, the user may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for deferred payment is paid in one month's worth on the next month's payment date, for example, by debiting from a bank account. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the deferred payment usage amount and subtracting the same amount from the available deferred payment amount, and on the closing date, the payment for the current month is transferred to the next month's payment date as described above. Process to withdraw the money. Note that if the payment amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is sent back to the payment application 20.

[Family payment settings]
FIG. 8 is a sequence diagram illustrating an example of the flow of processing executed by the payment application 20 and the payment server 100 in cooperation regarding family payment settings. 9 to 11 show examples of screen displays of the payment application 20 on the administrator's user terminal device 10, and FIG. 12 shows an example of screen display of the payment application 20 on the user terminal device 10 of a family member. The flow of the process shown in FIG. 8 will be described below, with appropriate reference to screen display examples shown in FIGS. 9 to 12. In addition, below, in order to distinguish between the administrator's user terminal device 10 and the family member's user terminal device 10, the former will be described as the user terminal device 10A, and the latter will be described as the user terminal device 10B. Similarly, in order to distinguish between the payment application 20 that operates on the user terminal device 10A and the payment application 20 that operates on the user terminal device 10B, the former will be referred to as the payment application 20A, and the latter will be referred to as the payment application 20B. do.

First, in the user terminal device 10A, the payment application 20A receives a selection operation for payment method management by the administrator (S101). In response to receiving the payment method management selection operation, the payment application 20A requests the payment server 100 to distribute content to display a payment method management screen (S102). The payment server 100 generates content data in response to the content distribution request in S102 and distributes it to the user terminal device 10A (S103). The payment application 20A displays a payment method management screen based on the received content data (S104). Here, the payment method management screen includes a link to a screen that accepts setting operations related to family payment (family payment setting screen), and the payment application 20A accepts the selection operation of this link (S105) and performs payment. A content distribution request for displaying a family payment setting screen is made to the server 100 (S106).

FIG. 9 is a diagram showing a display example of the payment method management screen. For example, the payment method management screen G10 shown in FIG. 9 displays information INF11 regarding the available amount (charge balance and point balance) and menu information INF12 regarding settings of various payment methods. Further, in this example, setting menus M11 to M16 for deferred payment, family payment, addition of bank account for charging, auto charging, addition of credit card, and import from wallet are displayed as menu information INF12. The display of each setting menu may include information indicating the setting status. The example in FIG. 9 shows a situation where deferred payment and family payment are "not set" and auto charge is "disabled". In this case, the payment application 20A may change the display of "not set" to a display of "set", "edited", etc. when settings are made for deferred payment or family payment.

In the example of FIG. 9, the payment application 20A requests content distribution of the family payment setting screen in response to an operation to select the family payment setting menu M12 on the payment method management screen G10. Although a case is described here in which the family payment setting screen is called from the payment method management screen, this is just an example, and the family payment setting screen may be called from a screen other than the payment method management screen. Further, the payment method management screen may also be called up from any screen of the payment application 20A. For example, the payment method management screen may be called from the administrator's wallet screen.

FIG. 10 is a diagram showing a display example of the administrator's wallet screen. The wallet screen is a screen for managing the wallet of the user (in this case, the administrator). Wallet is a function that plays the role of a user's wallet in electronic payment services. The wallet screen displays basic information about the charge balance, as well as information about payment methods other than the charge balance, transaction history, and other information. For example, the wallet screen G20 shown in FIG. 10 displays information INF21 to INF23 regarding various payment methods and transaction history information INF24. For example, the information INF21 is information regarding the charge balance of the wallet.

Further, the information INF22 is, for example, information regarding credit cards (○○ cards) and deferred payment. The example in FIG. 10 represents a situation in which a message is displayed to a user (administrator) who has not applied for credit card or deferred payment, recommending that the user apply for use. Further, the information INF23 is, for example, information regarding family payment. The example in FIG. 10 represents a situation in which a message is displayed to a user (administrator) who has not set up the use of family payment, recommending that the user do so. The transaction history of the information INF 24 includes at least the transaction history of each family member. This allows administrators to share information about family members and how much they spent. The transaction history of the information INF 24 may include the transaction history of the administrator. Note that in order to protect the privacy of family members, the administrator's payment application 20 may be configured not to acquire or display detailed transaction history information (such as where and what was purchased). Further, whether or not such detailed information is displayed may be managed so as to be changeable depending on the relationship between members and administrators, family attributes, and the like. For example, if the administrator and family members are in a parent-child relationship, the administrator may be able to view detailed information about each family member. Furthermore, if the family is a group for controlling spending among specific groups, all family members may be allowed to view detailed information of other family members. The wallet screen 20 is an example of "second content".

The wallet screen G20 may be configured to arrange a UI such as a button that accepts an action execution operation related to the corresponding payment method in association with information regarding various payment methods. For example, a button BT11 for displaying information on the breakdown of the charge balance may be arranged on the wallet screen G20 in association with the information INF21. Further, a button BT12 for making an application for use may be arranged in association with the information INF22 on the wallet screen G20. Furthermore, a button BT13 for setting the use of family payment may be arranged in association with the information INF23 on the wallet screen G20. In this case, when the button BT13 is pressed, the payment application 20A may, for example, display the family payment setting screen G30 shown in FIG. 11 below, or display the payment method management screen G10 including the family payment setting menu M12. It may be displayed.

Regarding the display of the wallet screen G20, the payment server 100 can recognize the administrator's charge balance and transaction history by referring to the user information 172. In addition, by referring to the user information 172, the payment server 100 recognizes the status of applications for other payment methods, the status of family payment usage settings, etc., and provides information according to these situations to the user. may be notified. The payment server 100 may change the notification content depending on the situation, or may not display the information on the wallet screen G20.

FIG. 11 is a diagram showing a display example of the family payment setting screen. For example, the family payment setting screen G30 shown in FIG. 11 includes setting information INF31 for the family name, setting information INF32 for the payment method used for family payment, setting information INF33 for family members, and settings for the family payment being displayed. A button BT21 for deletion is displayed. For example, the setting information INF31 displays the current settings of the family name (in the example of FIG. 11, "My Family") as well as an edit button BT22 that allows the settings to be changed. Further, the payment method setting information INF32 displays, for example, a list of fund sources that can be used for family payment, as well as check boxes CB23 to CB25 that accept selection operations for each fund source. In addition, in the family member information INF33, for example, registered family members and their respective upper limit amounts are displayed in a list, and edit buttons BT26 to BT28 that allow changing the upper limit amounts for family members other than the administrator are displayed. and a button BT29 for adding a new family member are displayed. The family payment setting screen G30 is an example of "third content".

The payment server 100 generates content data in response to the content distribution request in S106 and distributes it to the user terminal device 10A (S107). The payment application 20A displays a family payment setting screen based on the received content data (S108). Subsequently, the payment application 20A accepts the family payment setting operation (S109), and transmits the input setting details to the payment server 100 (S110). The payment server 100 stores the settings received from the payment application 20A (S111). For example, the payment server 100 stores the maximum amount of money for each family member in the user information 172 and stores the settings of the family in the family information 178.

The processing up to this point completes the family payment settings by the administrator. When the family payment settings are completed, the family member's payment application 20B is notified that payment by family payment is now possible.

FIG. 12 is a diagram showing a display example of a family member's wallet screen. For example, the wallet screen G40 shown in FIG. 12 includes charge balance information INF41, transaction history information INF42, information INF43 about application for use of other payment methods, and information about whether family payment has been approved by the administrator. Notification information INF44 to that effect is displayed. As in the case of the administrator's wallet screen, the payment server 100 can recognize these pieces of information INF41 to INF44 by referring to the user information 172 of the family members. For example, the notification information INF44 shown in FIG. 12 notifies that the administrator (here, Uncle Sam) recommends (invites) the use of family payment, and also informs that the administrator (here Uncle Sam) recommends (invites) the use of family payment. It displays the maximum payment amount. Further, as in the example of FIG. 12, the payment application 20B may display the notification information INF44 as well as a button BT31 for the family member to accept the notified content and start using family payment. good. For example, when the button BT31 is pressed, the payment application 20 cooperates with the payment server 100 to automatically charge a family member's wallet from the administrator's fund source, and instructs the family member to perform a balance charge operation. To transition to a state in which family payment can be used without requiring payment.

Note that a family member's charge balance may be displayed as the sum of the amount charged using family payment and the amount charged using other methods, or may be displayed individually. Further, charging the balance using family payment may be performed an arbitrary number of times as long as the cumulative amount of charging within the set period does not exceed the upper limit for family payment. Additionally, depending on settings, charging the balance using family payment may be automatically performed as long as the total charging amount falls within the upper limit for family payment. Such automatic balance charging may be performed when the charging balance falls below a threshold value, or may be performed when the balance becomes insufficient at the time of payment. Further, the payment server 100 may be configured to charge the entire family payment upper limit amount at the start of the set period.

Returning to FIG. 8, the flow of processing when a family member of the family charges the balance by family payment after the family payment setting (S101 to S111) is completed will be described. First, in the family member's user terminal device 10B, the payment application 20B accepts an operation to charge the balance by family payment (S201). In response to receiving the balance charge execution operation, the payment application 20B withdraws the specified amount from the administrator's fund source to the payment server 100 and adds it to the family member's charge balance (S202). . The payment server 100 notifies the payment application 20B that the balance charge has been completed (S203). Upon receiving this charge completion notification, the payment application 20B updates the display of the charge balance (S204). Note that, as explained in FIG. 12, the balance charge for family payment may be automatically performed in response to a family member's acceptance operation.

Through the above process, the amount available within the family payment limit will be charged to the family member's wallet from the administrator's fund source. This allows family members to pay within the family payment limit within the set period.

FIG. 13 is a diagram illustrating a display example of a breakdown screen showing a breakdown of the administrator's charge balance. For example, the breakdown screen G50 shown in FIG. 13 is displayed when button BT11 is pressed on the administrator's wallet screen G20. The breakdown screen G50 includes, for example, information INF51 indicating the total amount of available charge balances, information INF52 of charge balances available for family payment, and information INF53 indicating usage status of family payment by each family member. Further, the information INF 53 includes, for example, the upper limit amount of family payment set for each family member and the total amount paid by each family member as family payment. The payment server 100 can recognize this information by referring to the user information 172 of the administrator and family members. For example, payment server 100 can recognize information INF 52 by summing the family payment balances of all family members. Further, for example, the payment server 100 can recognize the total amount paid by the family member using family payment by referring to the family member's payment history and totaling the payment amount made within the corresponding set period. I can do it. In addition to being displayed as the breakdown screen G50, the breakdown information of the charge balance may be additionally displayed within the wallet screen G20 in response to pressing the button BT11. The breakdown screen G50 is an example of "first content".

According to the embodiment described above, by setting up a family, the administrator can have family members make payments using family payment, so for example, children who do not have a fund source other than cash can Users can use electronic payment services more easily, and the convenience of electronic payment services can be improved.

Furthermore, according to the above embodiment, the administrator can set the maximum amount that can be used for family payments for each family member, so that the administrator can make family members pay appropriately within the allowable range. can.

Further, according to the above embodiment, the administrator can check the usage status of family payment for each family member, and therefore can appropriately manage the purchasing behavior of family members.

Note that the display control of the various screens described in the above embodiments may be performed by either the payment server 100 or the user terminal device 10. For example, if the payment application 20 includes a web browser or a web view, the payment server 100 may deliver HTML data for displaying various screens to the user terminal device 10 as content data. In this case, since the actual display control is executed on the payment server 100 side, for example, a web server or a web application operating on the payment server 100 plays the role of the display control unit. Further, for example, if the payment application 20 imports variable information into various screen formats and displays the screen, the payment server 100 distributes the necessary variable information to the user terminal device 10 as content data. It's okay. In this case, since the actual display control is executed on the payment application 20 side, the payment application 20 plays the role of the display control section. The payment application 20 and the payment server 100 may be configured to perform such display control in a distributed manner as appropriate.

Although the mode for implementing the present invention has been described above using embodiments, the present invention is not limited to these embodiments in any way, and various modifications and substitutions can be made without departing from the gist of the present invention. can be added.

DESCRIPTION OF SYMBOLS 10... User terminal device, 20... Payment application, 50... First store terminal device, 60... Store code image, 70... Second store terminal device, 72... Interface for member stores, 100... Payment server, 110... Communication department , 120...Payment content providing unit, 130...Payment processing unit, 140...Information management unit, 170...Storage unit, 172...User information, 174...Payment content information, 176...Store information, 178...Family information, G10...Payment Method management screen, G20...Wallet screen, G30...Family payment setting screen, G40...Wallet screen, G50...Breakdown screen

Claims (10)

A payment management device that provides an electronic payment service to the user in cooperation with an application program running on the user's terminal device,
A storage unit that stores correspondence information between any one or more fund sources owned by the first user and registered as a payment method in the electronic payment service and one or more second users. and,
a payment processing unit that executes payment processing to realize the electronic payment service;
Equipped with
The second user is a user who is permitted to use the first user's fund source in payment using the electronic payment service,
The payment processing unit is
a first notification from said first user to said second user, said first notification recommending that said first user make an electronic payment using a fund source; In response to receiving a second notification from the second user 's terminal device indicating that the second user has accepted the notification, the first user receives funds from the first user's fund source. Increase the balance of the electronic payment account of the user in 2.
executing electronic payment using the balance of the electronic payment account of the second user in response to a payment request from the second user's terminal device;
Payment management device. A payment management device that provides an electronic payment service to the user in cooperation with an application program running on the user's terminal device,
Correspondence information that associates any one or more fund sources owned by a first user and registered as a payment method in the electronic payment service with one or more second users, A memory for storing corresponding information including a setting of an upper limit amount that can be added from the fund source to the electronic payment account of the user related to the electronic payment service within a predetermined setting period for each of the second users. Department and
a payment processing unit that executes payment processing to realize the electronic payment service;
Equipped with
The second user is a user who is permitted to use the first user's fund source in payment using the electronic payment service,
The payment processing unit is
said first user in response to receiving a notification from said second user's terminal device that said second user has accepted to use said first user's fund source; increasing the balance of the electronic payment account of the second user from a fund source of the second user within the upper limit amount set for the second user;
executing electronic payment using the balance of the electronic payment account of the second user in response to a payment request from the second user's terminal device;
Payment management device. further comprising a content providing unit that provides content related to the electronic payment service to the application program,
The content providing unit provides, for each of the one or more second users, first content including the total amount paid by the second user from the balance added from the fund source. displayed on the user's terminal device,
The payment management device according to claim 2. The first content displays the total amount and the upper limit amount in association with each other for each of the one or more second users;
The payment management device according to claim 3. The first content includes the total amount of the upper limit amount set for the one or more second users;
The payment management device according to claim 3. further comprising a content providing unit that provides content related to the electronic payment service to the application program,
The content providing unit provides, for each of the one or more second users, second content including a transaction history in which the second user made a payment from the balance added from the fund source. display on the terminal device of user 1,
The payment management device according to claim 1 or 2 . further comprising a content providing unit that provides content related to the electronic payment service to the application program,
The content providing unit receives an operation for selecting a fund source to be used for payment by the second user from among one or more fund sources owned by the first user, and selects the selected fund source. Displaying third content that accepts an operation for registering the one or more second users associated with the first user on the terminal device of the first user;
The payment management device according to claim 1 or 2 . A payment management method using a payment management device that provides an electronic payment service to the user in cooperation with an application program running on the user's terminal device, the method comprising:
The payment management device includes:
storing correspondence information between any one or more fund sources owned by a first user and registered as a payment method in the electronic payment service and one or more second users;
It executes payment processing to realize the electronic payment service,
a first notification from said first user to said second user, said first notification recommending that said first user make an electronic payment using a fund source; In response to receiving a second notification from the second user 's terminal device indicating that the second user has accepted the notification, the first user receives funds from the first user's fund source. Increase the balance of the electronic payment account of the user in 2.
executing electronic payment using the balance of the electronic payment account of the second user in response to a payment request from the second user's terminal device;
Payment management methods. A payment management method using a payment management device that provides an electronic payment service to the user in cooperation with an application program running on the user's terminal device, the method comprising:
The payment management device includes:
Correspondence information that associates any one or more fund sources owned by a first user and registered as a payment method in the electronic payment service with one or more second users, storing correspondence information including a setting of an upper limit amount that can be added from the fund source to the electronic payment account of the user related to the electronic payment service within a predetermined setting period for each of the second users;
It executes payment processing to realize the electronic payment service,
The second user is a user who is permitted to use the first user's fund source in payment using the electronic payment service,
said first user in response to receiving a notification from said second user's terminal device that said second user has accepted to use said first user's fund source; increasing the balance of the electronic payment account of the second user from a fund source of the second user within the upper limit amount set for the second user;
executing electronic payment using the balance of the electronic payment account of the second user in response to a payment request from the second user's terminal device;
Payment management methods. An application program that operates on a user's terminal device and cooperates with the payment management device according to claim 1 or 2 to provide the user with an electronic payment service,
For each of the one or more second users, the total amount paid by the second user from the balance added from the fund source is obtained from the payment management device, and the total amount paid by the second user is calculated by the first user. display on the terminal device,
application program.

Images