JP7401711B1 - Information processing device, information processing method, and program - Google Patents

Abstract

[Problem] To improve convenience for users of electronic payment services. [Solution] From a first user terminal device of a first user who uses an electronic payment service, one or more users who use the electronic payment service select the amount of money that can be used during a predetermined period for payment of the electronic payment service. an interface unit that receives a designation to allocate the amount frame to the electronic payment service account of the second user; and a payment processing unit that allocates the amount frame to the electronic payment service account based on the accepted designation, When the amount frame is assigned to the electronic payment service account, the payment processing unit allows the use of an amount corresponding to the amount frame among the available quotas in the electronic payment service of the first user terminal device. information processing equipment. [Selection diagram] Figure 4

Description

The present invention relates to an information processing device, an information processing method, and a program.

2. Description of the Related Art Conventionally, techniques for realizing electronic money remittance between individuals have been known. For example, in Patent Document 1, electronic money collected at a predetermined ratio from a plurality of payment methods registered in a first electronic wallet associated with a first user is transferred to a second electronic wallet associated with a second user. A technique for transferring money to at least one of a wallet and a deposit account at a financial institution is disclosed.

Japanese Patent Application Publication No. 2021-189861

However, since the conventional technology does not set a provisional shared amount limit within the same electronic payment service, it is difficult to provide various expanded services such as monitoring the usage status of the remittance recipient. It may not be possible. Therefore, convenience for users of electronic payment services may not be sufficient.

The present invention has been made in consideration of such circumstances, and an object of the present invention is to provide an information processing device, an information processing method, and a program that can improve convenience for users of electronic payment services. be one of the.

One aspect of the present invention is to use a first user terminal device of a first user who uses an electronic payment service to transfer an amount of money that can be used during a predetermined period for payment of the electronic payment service to the first user terminal device of a first user who uses the electronic payment service. an interface unit that receives a designation to allocate the amount frame to the electronic payment service account of one or more second users; and a payment processing unit that allocates the amount frame to the electronic payment service account based on the accepted designation. The interface unit includes a first granting method of granting the amount limit from the charge balance of the first user in the electronic payment service, and a first granting method of granting the amount limit from the charge balance of the first user in the electronic payment service; The information processing device further receives designations from a plurality of granting methods including a second granting method of granting the amount frame.

According to one aspect of the present invention, convenience for users of electronic payment services can be improved.

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. FIG. 1 is a configuration diagram of a payment server 100 according to a first embodiment. 3 is a diagram showing an example of the contents of user information 172. FIG. It is a sequence diagram illustrating the general flow of shared wallet payment using charge balance. It is a flowchart showing an example of the flow of remittance processing in shared wallet payment using charge balance. FIG. 2 is a sequence diagram illustrating the general flow of shared wallet payment using the available deferred payment amount. It is a diagram showing an example of a shared wallet setting screen displayed on the first user terminal device 10A and a payment screen displayed on the second user terminal device 10B. 17 is a diagram illustrating an example of the contents of shared wallet setting information 176. FIG. 17 is a diagram illustrating an example of the contents of shared wallet history information 178. FIG. It is a figure which shows an example of the detailed setting screen of a shared wallet displayed on 1st user terminal device 10A. 3 is a diagram illustrating an example of shared wallet payment proposal information notified by the interface unit 120. FIG. 3 is a diagram illustrating an example of shared wallet payment history information notified by the interface unit 120. FIG. 3 is a diagram illustrating an example of detailed information on shared wallet payment notified by the interface unit 120. FIG. 12 is a diagram illustrating an example of suggested information regarding the use of the balance amount of the shared wallet notified by the interface unit 120. FIG.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of an information processing apparatus, an information processing method, and a program according to the present invention will be described below with reference to the drawings. An application program installed in a user terminal device, which will be described later, and a payment server cooperate to provide an electronic payment service. 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. In this embodiment, the one or more user terminal devices 10 include a first user terminal device 10A held by a first user of the electronic payment service (for example, a parent), and a first user terminal device 10A held by a second user of the electronic payment service (for example, a parent). , child) held by the second user terminal device 10B.

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 according to the first embodiment. The payment server 100 includes, for example, a communication section 110, an interface section 120, a payment content providing section 130, and a payment processing section 140. 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, shared wallet setting information 176, and shared wallet history 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 interface section 120 controls the communication section 110 to exchange information between the user terminal device 10, the first store terminal device 50, and the second store terminal device 70.

The payment content providing unit 130 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 130 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 140 performs payment processing based on payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 140 performs payment processing while referring to user information 172 and shared wallet setting information 176, which will be described later.

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. The user information 172 includes, for example, user URL, account ID, phone number, password, email address, user ID, name/address/date of birth, registration date, first charge balance, second charge balance, Information such as deferred payment settings, deferred payment limit, deferred payment usage amount, deferred payment usage amount, payment method settings, bank account, credit card number, presence or absence of identity verification, charging history information, payment history information, 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 first charge balance and the second charge balance are 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 first charge balance is the charge balance that is permitted to be used after the user completes personal authentication and registers a bank account in the electronic payment service, and the second charge balance is the charge balance that the user is allowed to use when the user completes personal authentication and registers a bank account in the electronic payment service. This is the charge balance that is permitted to be used regardless of the completion of authentication. According to the law, the balance charged to the first charge balance can be withdrawn to a bank account according to the user's wishes, while the balance charged to the second charge balance can be withdrawn from an electronic payment service. It is used only for limited purposes, including payment. The second charge balance is permitted to be used by all users upon registration with the electronic payment service.

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. The payment method setting is setting information that indicates whether the user will perform electronic payment using the charge balance, deferred payment, or electronic payment using a shared wallet 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. Shared wallet setting information 176 and shared wallet history information 178 will be described later.

[Electronic payment]
When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 140 refers to the user information 172 and acquires the "payment method setting" of the user. The payment processing unit 140 performs electronic payment as follows for a user whose "payment method setting" is set to "charge balance". The payment processing unit 140 performs electronic payment by, for example, decreasing the first charge balance or the second charge balance managed in association with the user ID and increasing the item value of sales proceeds of the member store. . 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. If the values of both the first charge balance and the second charge balance are positive, the payment processing unit 140 preferentially reduces the second charge balance, and if the payment amount exceeds the second charge balance, , the remaining amount is decreased from the first charge balance.

The payment processing unit 140 performs electronic payment as follows for a user whose "payment method setting" is set to "deferred payment". Deferred payment is set up separately from "credit payment" in cooperation with a credit card company that is a separate entity from the operator of the electronic payment service, and is set up separately from the credit card company that is a separate entity from the operator of the electronic payment service or a subsidiary of the operator. The person concerned becomes the creditor and allows electronic payments that do not depend on the charge balance within the deferred payment limit (credit limit). Note that in order to receive the deferred payment service, it may be required to obtain a credit card provided by the operator or subsidiary 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 140 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.

In addition to "deferred payment" where the creditor is a related party such as the operator of the electronic payment service or a subsidiary of the operator, "credit payment" may be set in the "payment method setting". In that case, the credit card company, which is a separate entity from the operator of the electronic payment service, becomes the creditor and provides the user with electronic payment that does not depend on the charge balance within the credit card's available amount (credit limit). It is permissible. Similar to ``deferred payment,'' the amount used for credit card payments is paid in one month's worth on the next month's payment date, for example, by debiting from a bank account.

The payment processing unit 140 performs electronic payment as follows for a user whose "payment method setting" is set to "shared wallet." A shared wallet is a shared wallet in which a first user of an electronic payment service transfers the available amount of money during a predetermined period (for example, one month) to a second user of the electronic payment service according to a predetermined schedule (for example, on the 27th of every month). means a payment method (hereinafter sometimes referred to as "shared wallet payment") that enables electronic payment by the second user by remittance and transfer (sharing) to Therefore, "remittances and transfers" are referred to as remittances). In this case, the "available amount limit" may be the above-mentioned charge balance, deferred payment limit, or credit limit, and may be a limit set in advance by the first user. It is something that Below, we will explain the flow of shared wallet payments based on the charge balance and shared wallet payments based on the available deferred payment amount. The flow of shared wallet payment based on the available amount of credit card is the same as the flow of shared wallet payment using available amount of deferred payment by replacing the available amount of deferred payment with the available amount of credit card, so the explanation will be omitted. .

FIG. 6 is a sequence diagram illustrating the general flow of shared wallet payment using charge balance. First, the first user uses the first user terminal device 10A to share the amount of money available during a predetermined period for remittance from the charge balance to the second user of the electronic payment service according to a predetermined schedule. Perform wallet settings (S21). When the first user sets the shared wallet, the payment server 100 allows the second user terminal device 10B to use the shared wallet for an amount corresponding to the set remittance amount (S22).

Next, the second user uses the second user terminal device 10B to select the use of the shared wallet on the payment screen, and sends a notification to the effect that the electronic payment will be made along with the payment amount to the first user terminal. The notification is sent to the device 10A (in this case, the notification may be sent via the payment server 100) (S23). In response, the first user terminal device 10A remits money equivalent to the payment amount to the second user terminal device 10B (S24). When the second user terminal device 10B receives the remittance, it adds the remittance amount to the first charge balance or the second charge balance to settle the charge balance (S25). When the shared wallet payment is completed, the second user terminal device 10B sends a notification of completion of the shared wallet payment to the payment server 100 (S26). The payment server 100, which has received the notification of completion of the shared wallet payment, subtracts the payment amount from the first charge balance or the second charge balance of the first user terminal device 10A (S27). This completes the electronic payment using the shared wallet.

Note that the notification sent from the second user terminal device 10B to the first user terminal device 10A in S23 above may be a notification as an internal process in each terminal, or may be a notification sent as an internal process in each terminal. It may be displayed on the screen of the first user terminal device 10A and confirmed by the first user. When the notification is displayed on the screen of the first user terminal device 10A, in response to approval by the first user (for example, pressing the approval button on the first user terminal device 10A), the steps from S24 onward are performed. Processing may be executed.

Furthermore, the process of subtracting the payment amount from the first charge balance or second charge balance of the first user terminal device 10A in S27 above may be performed between S23 and S24, or may be performed in S24. It may be executed simultaneously with the processing or between S24 and S25. That is, in these cases, the payment amount is first subtracted from the first charge balance or the second charge balance of the first user terminal device 10A, and then the payment amount is transferred to the second user terminal device 10B, and the remitted amount is The payment amount will be subtracted from the first charge balance or second charge balance of the second user terminal device 10B.

Here, when remitting money from the first user terminal device 10A to the second user terminal device 10B, the charge balance of the first charge balance and the second charge balance is subtracted from the charge balance of the second user terminal device 10B. Which charge balance should be added to depends on whether or not the second user terminal device 10B has completed the identity verification (that is, whether the first charge balance can be used) and whether the electronic payment is executed. This is determined depending on whether the store where the charge is made supports electronic payment for both the first charge balance and the second charge balance. Hereinafter, with reference to the flowchart of FIG. 7, details of the flow of remittance processing in shared wallet payment using charge balance will be described. In addition, in the following flowchart, as an example, the first user terminal device 10A will be described as the main body of the process, but the payment server 100 may be the main body of the process.

FIG. 7 is a flowchart showing an example of the flow of remittance processing in shared wallet payment using charge balance. First, the first user terminal device 10A receives a notification from the second user terminal device 10B that a shared wallet payment will be made (S100). Next, the first user terminal device 10A, for example, inquires the payment server 100 to determine whether the store performing the shared wallet payment supports electronic payment for both the first charge balance and the second charge balance. is determined (S102). If it is determined that the store that performs the shared wallet payment supports electronic payment for both the first charge balance and the second charge balance, the first user terminal device 10A transfers the amount equivalent to the payment amount to the first charge balance. The amount is preferentially subtracted from the second charge balance and transferred to the second user terminal device 10B (step S104). Here, "preferentially subtracted from the second charge balance" means that after first subtracting the payment amount from the second charge balance, if the balance amount obtained by subtracting the second charge balance from the payment amount is positive, then the corresponding balance This means subtracting the amount from the first charge balance. If the balance amount exceeds the first charge balance, the shared wallet payment will fail unless the auto charge setting described below is enabled. The second user terminal device 10B that received the remittance converts the received amount into a first charge balance or a second charge balance and performs electronic payment in S25. More precisely, if the identity verification of the second user terminal device 10B has been completed, the second user terminal device 10B converts the received amounts into a first charge balance and a second charge balance, respectively. On the other hand, if the identity verification is not completed, the second user terminal device 10B converts the entire received amount into a second charge balance and performs the electronic payment in S25.

On the other hand, if it is determined that the store that performs shared wallet payment does not support electronic payment for both the first charge balance and the second charge balance (in other words, the store that performs shared wallet payment does not support electronic payment using the first charge balance) If it is determined that the first user terminal device 10A only supports payment, the first user terminal device 10A, for example, inquires the payment server 100 to determine whether or not the identity verification of the second user terminal device 10B has been completed. (S106). If it is determined that the identity verification of the second user terminal device 10B has been completed, the first user terminal device 10A subtracts an amount corresponding to the payment amount from only the first charge balance, and The money is transferred to the user terminal device 10B (S108). At this time, the second user terminal device 10B that received the remittance converts the received amount into a first charge balance and performs electronic payment in S25.

On the other hand, if it is determined that the identity verification of the second user terminal device 10B has not been completed, this is because the store performing the shared wallet payment only supports electronic payment using the first charge balance. , means that the second user terminal device 10B cannot perform electronic payment using the first charge balance. Therefore, the first user terminal device 10A does not perform the remittance in S24, or the electronic payment in S25 by the second user terminal device 10B that received the remittance fails (S110). This completes the processing of this flowchart.

FIG. 7 is a sequence diagram illustrating the general flow of shared wallet payment using the available deferred payment amount. First, the first user uses the first user terminal device 10A to remit the amount available during a predetermined period to the second user of the electronic payment service from the available deferred payment amount according to a predetermined schedule. Shared wallet settings are performed (S31). When the first user sets the shared wallet, the payment server 100 allows the second user terminal device 10B to use the shared wallet for an amount corresponding to the set remittance amount (S32).

Next, the second user uses the second user terminal device 10B to select the use of the shared wallet on the payment screen, and sends a notification to the effect that the electronic payment will be made along with the payment amount to the first user terminal. The notification is sent to the device 10A (in this case, the notification may be sent via the payment server 100) (S33). In response, the first user terminal device 10A remits money equivalent to the payment amount to the second user terminal device 10B (S34). Upon receiving the remittance, the second user terminal device 10B adds the remittance amount to the second charge balance to settle the charge balance (S35). When the shared wallet payment is completed, the second user terminal device 10B sends a notification of completion of the shared wallet payment to the payment server 100 (S36). The payment server 100, which has received the notification of completion of the shared wallet payment, subtracts the payment amount from the deferred payment available amount of the first user terminal device 10A (S37). This completes the electronic payment using the shared wallet.

Similarly to FIG. 6, the notification sent from the second user terminal device 10B to the first user terminal device 10A in S33 above may be a notification as an internal process in each terminal, or may be a notification as an internal process in each terminal. It may also be displayed on the screen of the first user terminal device 10A and confirmed by the first user. When the notification is displayed on the screen of the first user terminal device 10A, in response to approval by the first user (for example, pressing the approval button on the first user terminal device 10A), the steps from S34 onward are performed. Processing may be executed.

Furthermore, the process of subtracting the payment amount from the deferred payment available amount of the first user terminal device 10A in S37 above may be executed between S33 and S34, or may be executed simultaneously with the process of S34. Alternatively, it may be executed between S34 and S35. That is, in these cases, the payment amount is first subtracted from the deferred payment available amount of the first user terminal device 10A, and then the money is transferred to the second user terminal device 10B, and the second user terminal device to which the money was transferred is The payment amount will be subtracted from the second charge balance of 10B.

FIG. 9 is a diagram showing an example of a shared wallet setting screen displayed on the first user terminal device 10A and a payment screen displayed on the second user terminal device 10B. The left part of FIG. 9 shows a scene where the first user of the first user terminal device 10A sets up a shared wallet based on the charge balance with the second user terminal device 10B as the remittance destination, and the right part of FIG. represents a scene in which the second user of the second user terminal device 10B executes the shared wallet payment after the first user sets up the shared wallet.

In the left part of FIG. 9, area A1 represents a setting form for setting a sharing partner (remittance destination) for shared wallet payment. The first user of the first user terminal device 10A sets the sharing partner by inputting identification information such as the account ID, user ID, or phone number of the remittance partner on the setting form A1, for example. be able to. Area A2 represents a setting form for setting the available amount to be remitted to a sharing partner on a predetermined schedule (for example, every month). Area A3 represents a setting form for setting whether to settle the payment amount using the charge balance, the available deferred payment amount, or the available credit amount when executing the shared wallet payment. Button B1 represents a button for setting detailed conditions for shared wallet payment, and button B2 represents a button for completing (validating) the entered settings for shared wallet payment. When the first user of the first user terminal device 10A sets each item in the setting forms A1 to A3 and presses the completion button B2, the payment application 20A transmits the setting information to the payment server 100. The interface section of the payment server 100 receives the setting information and stores it in the storage section 170 as shared wallet setting information 176.

In the right part of FIG. 9, area A4 represents a payment amount input form, area A5 represents a payment method selection form, and button B3 represents a payment button. When the first user of the first user terminal device 10A activates the shared wallet payment setting, the shared wallet is displayed as a payment method candidate on the payment method selection form A5. The second user selects the shared wallet on the selection form A5, enters the payment amount in the input form A4, and presses the payment button B3. If the user has selected deferred payment as the payment method, in S33 of FIG. It is transmitted to the first user terminal device 10A.

When the shared wallet payment is executed, an amount corresponding to the payment amount is subtracted from the first charge balance of the first user terminal device 10A and the available amount of the shared wallet. For example, in the situation shown in FIG. 9, the payment amount of 500 yen is subtracted from the charge balance of 35,000 yen of the first user terminal device 10A, resulting in a charge balance of 34,500 yen. Furthermore, for the second user terminal device 10B, the payment amount of 500 yen is subtracted from the available amount of 20,000 yen in the shared wallet, resulting in 19,500 yen. This completes the shared wallet payment.

In addition, in Figure 9, the sharing partner, available amount, and payment method can be set as shared wallet payment settings, but these items are just examples, and other items can also be set. Also good. For example, as settings for shared wallet payment, items such as a remittance schedule and available period, which will be described later, may be set. The details setting button B1 will be described later.

Further, in FIG. 9, balance settlement and deferred payment are shown as examples of payment methods. However, the present invention is not limited to such a configuration, and includes, for example, debit cards, points earned by using an electronic payment service and available for subsequent electronic payment, and asset management operated by or affiliated with an electronic payment service. Payment may be possible from the asset management balance in the service.

Furthermore, in the shared wallet payment described with reference to FIGS. 6 and 8, the first user terminal device 10A realizes the shared wallet payment by remitting money to the second user terminal device 10B. However, the present invention is not limited to such a configuration, and the first user terminal device 10A that received the notification in S23 of FIG. 6 or S33 of FIG. The shared wallet payment may be completed by subtracting it directly from the charge balance or deferred payment available amount of the device 10A (in other words, by the first user terminal device 10A itself performing the charge balance payment or deferred payment payment). . In that case, if balance payment is selected as the payment method in the settings for shared wallet payment shown in FIG. It may be locked and prohibited from being used for anything other than shared wallet payments. On the other hand, if deferred payment is selected as the payment method in the shared wallet payment settings shown in FIG. You may. Thereby, when the second user terminal device 10B executes the shared wallet payment, the payment amount is deducted from the locked charge balance, so it is possible to prevent failure of the shared wallet payment.

[Remembering shared wallet information]
The storage unit 170 stores, as information regarding the shared wallet, shared wallet setting information 176, which is information regarding the settings of the shared wallet, and shared wallet history information 178, which is information regarding the history of electronic payments using the shared wallet. FIG. 10 is a diagram showing an example of the contents of the shared wallet setting information 176. The shared wallet setting information 176 includes, for example, the setting date, remittance source, remittance destination, remittance amount, balance amount, payment method, remittance schedule, usable period, and availability for the shared wallet ID for identifying the shared wallet. Information such as time, available store industry, history viewing authority, etc. are associated with each other.

The setting date is information representing the date on which the shared wallet was set by the first user terminal device 10A. The setup date may further include, for example, time information when the shared wallet was setup. The remittance source is the identification information (for example, account ID) of the first user terminal device 10A that performs remittance using the shared wallet. The remittance destination is identification information (for example, account ID) of the second user terminal device 10B that receives remittance through the shared wallet. The remittance amount is information representing the amount to be sent from the remittance source to the remittance destination. The balance amount is information representing the amount obtained by subtracting the amount actually paid by the second user in the shared wallet from the remittance amount. The payment method is information representing the payment method by which the payment amount is debited from the first user's account when executing the shared wallet payment.

The remittance schedule is information representing the timing of remittance from the remittance source to the remittance destination. As for the remittance schedule, the first user inputs an arbitrary schedule (monthly, weekly, every few days, etc.) when setting up the shared wallet on the first user terminal device 10A, and the interface unit 120 accepts it. It is something. At this time, a default schedule may be set, for example, the 27th of every month. The available period is information indicating the period during which electronic payment using the shared wallet can be made using the remitted amount. The usable period is usually set to a period corresponding to the remittance schedule (for example, one month if the remittance schedule is monthly), but the first user uses the shared wallet on the first user terminal device 10A. When setting, an arbitrary period (for example, two weeks even if the remittance schedule is monthly) may be set.

The available time is information indicating the time period during which electronic payments using the shared wallet can be used. The first user enters an arbitrary time slot as the available time when setting up the shared wallet on the first user terminal device 10A, and the interface section 120 accepts it. The available store industry is information representing the industry of a store that can use electronic payment using a shared wallet. The first user selects an arbitrary business type as the usable store type when setting up a shared wallet on the first user terminal device 10A, and the interface unit 120 accepts the selected type of store. Alternatively, or in addition to this, it may be possible to select prohibited store industries that prohibit the use of electronic payments using a shared wallet. Furthermore, for example, it may be possible to directly specify stores that can be used or stores that cannot be used. For example, if the first user is a parent and the second user is a minor child, the first user can limit the stores where shared wallet payments can be used to You can develop a sound financial sense.

The history viewing authority represents the information items that can be viewed by the first user, who is the remitter, among the information items of the payment history information stored in the shared wallet history information 178. For example, if the history viewing authority is set to the payment amount and payment time, the first user can view the payment amount and payment time among the history information of the shared wallet payment by the second user ( On the other hand, viewing payment stores is prohibited). The history viewing authority may be settable by the first user or the second user when setting up a shared wallet on the first user terminal device 10A, or may be settable by the first user and the second user. It may also be something that can be set based on user agreement. Furthermore, for example, the history viewing authority is not limited to setting only information items that can be viewed, but may also be capable of setting conditions that allow viewing of information items. For example, the first user may be able to view the history of electronic payments only for electronic payments where the payment amount is a predetermined amount (for example, 1000 yen) or more. In this way, by setting history viewing authority for the first user, the first user can understand and supervise the usage status of shared wallet payments by the second user.

Note that each item of the shared wallet setting information 176 described above may be set by the second user on the second user terminal device 10B, or may be set by the second user based on the agreement between the first user and the second user. Based on the settings (for example, when the second user presses the permission button on the second user terminal device 10B for the contents set by the first user on the first user terminal device 10A), It may be something that is done.

FIG. 11 is a diagram showing an example of the contents of the shared wallet history information 178. The shared wallet history information 178 is, for example, information such as a shared wallet ID, user (account ID), payment amount, payment store, etc., associated with the payment date and time. When the electronic payment using the shared wallet by the second user terminal device 10B is completed, the payment processing unit 140 links information such as the payment date and time, the payment amount, and the payment store to the account ID and records them in chronological order. is stored in the shared wallet history information 178.

FIG. 12 is a diagram showing an example of a shared wallet detailed setting screen displayed on the first user terminal device 10A. The screen shown in FIG. 12 changes in response to the first user of the first user terminal device 10A pressing button B1 on the shared wallet setting screen shown in FIG. 9, for example. In FIG. 10, area A6 represents a setting form for setting the available time for shared wallet payment, and area A7 represents a setting form for setting the store industry in which shared wallet payment can be used. When the first user of the first user terminal device 10A sets available hours or available store industries and presses button B4, the interface unit 120 stores the settings in the shared wallet setting information 176. Then, the detailed setting screen shown in FIG. 12 is changed to the setting screen shown in FIG. The electronic payment service may provide these detailed settings as a paid service. More specifically, when the first user of the first user terminal device 10A makes detailed settings, the electronic payment service allows payment of a predetermined amount in one time or periodically, balance payment, deferred payment, Alternatively, the bill for the paid service may be settled by a payment method such as a withdrawal from a bank account. Note that the detailed setting items shown in FIG. 12 are merely examples, and any item among the information items stored in the shared wallet setting information 176 may be subject to detailed setting.

[Various functions related to shared wallet payments]
Hereinafter, various functions related to shared wallet payment will be explained with reference to FIGS. 13 to 16. As described above, when the payment method for shared wallet payment is set to balance payment, when the shared wallet payment is executed, the payment processing unit 140 calculates the payment amount from the first user's first charge balance. Subtract. However, at this time, if the first charge balance of the first user is less than the available amount for shared wallet payment, the second user who is a user of shared wallet payment may It is possible that a shared wallet payment with a payment amount exceeding one charge balance may be executed. In that case, the shared wallet payment will fail, and the second user may feel uncomfortable about the failure of the shared wallet payment.

In consideration of the above circumstances, one function of the interface unit 120 is to set the payment method for shared wallet payment to balance payment, and the first charge balance of the first user does not exceed the available amount for shared wallet payment. If the amount is below, the first user terminal device 10A displays notification information suggesting application of a setting to automatically charge the first charge balance (hereinafter sometimes referred to as "auto charge"). Further, for example, the interface unit 120 causes the first user terminal device 10A to display notification information proposing to change the payment method for shared wallet payment from balance payment to deferred payment.

FIG. 13 is a diagram showing an example of shared wallet payment proposal information notified by the interface unit 120. As shown in FIG. 13, if the payment method for shared wallet payment is set to balance payment and the first charge balance of the first user is less than the available amount for shared wallet payment, the interface unit 120, for example, Notification information is displayed on the first user terminal device 10A suggesting setting up auto-charging or switching the payment method for shared wallet payment from balance payment to deferred payment. When the first user selects the auto charge setting by pressing the button B5, the interface section 120 accepts the selection and enables the auto charge setting. As a result, each time the first user's first charge balance falls below the available amount for shared wallet payment, the payment processing unit 140 increases the 1 Charge the balance. The payment source for auto-charging may be deferred payment from an electronic payment service, or may be debited from a bank account linked to the first user. If the first user selects to switch the payment method to deferred payment by pressing button B6, the interface unit 120 accepts the selection and changes the payment method in the shared wallet setting information 176 from balance payment to deferred payment. . This can prevent the second user from feeling uncomfortable due to a shared wallet payment failure.

As mentioned above, auto-charging may be executed when the first user's first charge balance is less than the available amount for shared wallet payment, or the first user's first charge balance is It may be executed when the amount is less than the settlement amount. In the latter case, the payment processing unit 140 charges the first charge balance by at least an amount corresponding to the difference between the first charge balance and the payment amount. Furthermore, auto-charging may be set not only for shared wallet payments but also for normal balance payments. For example, the interface unit 120 accepts a setting to charge a predetermined amount when the first charge balance becomes equal to or less than a threshold (that is, setting a threshold and a predetermined amount), and the payment processing unit 140 The first charge balance may be charged according to the settings. In this case, the payment source for auto-charge for normal balance settlement and the payment source for auto-charge for shared wallet settlement may be different.

Furthermore, in the above description, the automatic charge setting or switching of the payment method is executed based on the consent of the first user, but the present invention is not limited to such a configuration, and the payment processing unit 140 , failure of shared wallet payment may be prevented by performing auto-charging or switching the payment method from balance payment to deferred payment without the consent of the first user.

The interface unit 120 may also notify the user of proposal information for setting auto-charge or switching the payment method for shared wallet payment to deferred payment at a timing different from the above. For example, the interface unit 120 may notify proposal information when the first user performs initial settings of the shared wallet, or the first user's first charge balance is greater than or equal to the available amount for shared wallet payment. However, the proposal information may be notified at the timing when the difference between the first charge balance and the available amount falls within the threshold.

As another function, in order to prevent shared wallet payment failures, if the first charge balance of the first user is less than the payment amount of the shared wallet payment, the payment processing unit 140 transfers the insufficient amount to the second user. The amount may be applied from the first charge balance or the second charge balance. In this case, the payment processing unit 140 may allocate the amount from the first charge balance or the second charge balance based on the second user's prior consent, or may automatically allocate the amount from the first charge balance or the second charge balance based on the second user's prior consent. Appropriations may be made.

As yet another function, in order to prevent failures in shared wallet payments, the interface unit 120 may allow the first user to set priorities regarding payment methods for shared wallet payments. For example, if the first user sets balance settlement as the highest priority and deferred payment as the next highest priority as a payment method for shared wallet payment, the payment processing unit 140 Balance settlement may first be applied to the amount, and if the first user's first charge balance is less than the settlement amount for shared wallet settlement, deferred payment may be applied to the insufficient amount.

As another function, the interface unit 120 provides history information of shared wallet payments according to the sender's history viewing authority based on the history viewing authority set in the shared wallet setting information 176 and the shared wallet history information 178. may be displayed on the first user terminal device 10A.

FIG. 14 is a diagram illustrating an example of shared wallet payment history information notified by the interface unit 120. As shown in the left part of FIG. 14, for example, the payment application 20A has a button B7 for displaying the history of electronic payments made by the first user himself, and a button B7 for displaying the history of electronic payments made by the first user himself, and a Display button B8 for displaying the shared wallet payment history. In the state shown in the left part of FIG. 14, when the first user clicks button B8, the interface unit 120 refers to the shared wallet setting information 176, acquires the history viewing authority of the first user, Shared wallet history information 178 corresponding to the history viewing authority obtained is displayed on the first user terminal device 10A. For example, in the case of the history viewing authority set in the first line of the shared wallet setting information 176, the first user has viewing authority regarding the payment amount and payment time, but does not have viewing authority regarding the store name. Therefore, the interface unit 120 displays payment history information including only the payment amount and payment time on the first user terminal device 10A. Further, as shown in areas A8 and A9 of FIG. 14, the interface unit 120 may display the shared amount to the remittance recipient and the available amount at the time of displaying the history, together with the history information. In FIG. 14, as an example, for convenience of explanation, the shared amount and the available amount, and the history information are displayed on the same screen, but the present invention is not limited to such a configuration, and the interface unit 120 The amount, the available amount, and the history information may be displayed on different screens.

In addition, in FIG. 14, as an example, the first user selects between the first user's own payment history information and the second user's shared wallet payment history information on the first user terminal device 10A. Although an example in which one is selected and viewed is described, the present invention is not limited to such a configuration. For example, the payment application 20A displays both the first user's payment history information and the second user's shared wallet payment history information, and performs filtering according to the first user's selection. Only one of the history information may be displayed. In this case, in addition to displaying only the history information of one of the parties, filtering may be performed by displaying the history information of both parties and then filtering by items such as payment amount, date and time, store type, etc. good.

Furthermore, as another function, when the payment processing unit 140 processes the second user's shared wallet payment, the interface unit 120 may notify the first user terminal device 10A of detailed information on the payment. . In this case, the interface unit 120 may send a push notification to the first user terminal device 10A, or may display detailed information on the top page of the payment application 20A.

FIG. 15 is a diagram illustrating an example of detailed information on shared wallet payment notified by the interface unit 120. As shown in FIG. 15, when the second user's shared wallet payment is processed by the payment processing unit 140, the interface unit 120 sends detailed information such as the payment amount, store name, date and time of the shared wallet payment to the first user. The terminal device 10A is notified. At this time, the interface unit 120 refers to the shared wallet setting information 176, acquires the history viewing authority of the first user, and notifies the first user terminal device 10A only of the information items for which the history viewing authority is set. You can. For example, in the case of the example shown in FIG. 12, since the first user does not have viewing authority regarding the store name, the interface unit 120 does not notify the first user terminal device 10A of the store name, and the payment amount and date and time. We are providing information only.

Furthermore, as another function, the payment processing unit 140 may make the remaining balance amount after the expiration of the usable period of the shared wallet available for other purposes in the electronic payment service. FIG. 16 is a diagram illustrating an example of suggested information regarding the use of the balance amount of the shared wallet notified by the interface unit 120. As shown in FIG. 16, the interface unit 120 uses the balance amount of the shared wallet to charge the first charge balance or the second charge balance of the second user, or transfers it to another user of the electronic payment service. You can choose from multiple uses, such as using it for asset management services operated by or affiliated with an electronic payment service, or sending the balance as a gift (for example, a coupon that can be used at a restaurant). It may be displayed on the second user terminal device 10B as follows.

For example, when the second user presses button B9, the payment processing unit 140 charges the balance amount of the shared wallet to the second user's first charge balance or second charge balance. When the second user presses button B10, the interface unit 120 displays a setting form for specifying the remittance destination, and accepts the second user's specification of the remittance destination (for example, account ID, phone number, etc.) Then, the payment processing unit 140 charges the remaining amount to the specified remittance destination. When the second user presses button B11, the interface unit 120 displays a screen for asset management services (or transitions to an external site), and the second user can check the balance amount on the displayed screen. Specify the operation method. When the second user presses the button B12, the interface unit 120 displays a list of gifts redeemable within the balance amount, and when the user specifies the gift and the destination of the gift, the payment processing unit 140 will convert the balance amount into a gift and send it to the specified destination. Note that use of these uses may be restricted depending on whether or not the second user has completed identity verification. For example, if the second user has not completed identity verification, remittance or use of asset management services may be prohibited. Furthermore, for example, when the first user sets up a shared wallet, he or she may specify the purpose for which the second user is permitted to use the shared wallet (the purpose specification may be included in the paid service). Thereby, inappropriate use of the balance amount by the second user can be prevented.

According to the present embodiment described above, from the first user terminal device of the first user who uses the electronic payment service, the amount limit that can be used during a predetermined period for payment of the electronic payment service is transferred to the electronic payment service. Accepts the designation to be added to the electronic payment service account of one or more secondary users who use the service, and based on the accepted designation, assigns the amount limit to the electronic payment service account, and the first use of the electronic payment service. Specify from a plurality of granting methods, including a first granting method that grants a monetary limit from the charge balance of the first user, and a second granting method that grants a monetary limit from the deferred payment available amount of the first user in the electronic payment service. Accept more. Thereby, convenience for users of the electronic payment service can be improved.

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.

10 User terminal device 20 Payment application 50 First store terminal device 70 Second store terminal device 100 Payment server 110 Communication section 120 Interface section 130 Payment content providing section 140 Payment processing section 170 Storage section

Claims (6)

A first user terminal device of a first user using the electronic payment service transfers the amount of money that can be used during a predetermined period for payment of the electronic payment service to one or more second users using the electronic payment service. an interface unit that accepts a designation to be granted to a person's electronic payment service account;
a payment processing unit that grants the amount limit to the electronic payment service account with usage restrictions based on the received designation;
As the usage restriction, after the predetermined period has elapsed, the payment processing unit sets a balance amount obtained by subtracting the usage amount used during the predetermined period from the amount frame to a second electronic payment service account linked to the electronic payment service account. enabling the user terminal device to be used for one or more purposes in the electronic payment service;
Information processing device. The interface unit further receives a designation regarding any one of the one or more uses from the second user terminal device.
The information processing device according to claim 1. The interface unit further receives, from the first user terminal device, a specification regarding a use that can be specified to the second user terminal device among the one or more uses.
The information processing device according to claim 2. The interface unit determines which of the one or more uses can be specified to the second user terminal device, depending on whether or not the second user's identity verification has been completed.
The information processing device according to claim 2. The computer is
A first user terminal device of a first user using the electronic payment service transfers the amount of money that can be used during a predetermined period for payment of the electronic payment service to one or more second users using the electronic payment service. accepts the designation to be granted to the electronic payment service account of the person,
Based on the received designation, grant the amount limit to the electronic payment service account with usage restrictions;
As the usage restriction, after the predetermined period has elapsed, the remaining amount obtained by subtracting the usage amount used during the predetermined period from the amount frame is set as the usage limit of the second user terminal device linked to the electronic payment service account. make it available for one or more purposes in electronic payment services;
Information processing method. to the computer,
A first user terminal device of a first user using the electronic payment service transfers the amount of money that can be used during a predetermined period for payment of the electronic payment service to one or more second users using the electronic payment service. accept the designation to be granted to the person's electronic payment service account,
Based on the received specification, grant the amount limit to the electronic payment service account with usage restrictions;
As the usage restriction, after the predetermined period has elapsed, the remaining amount obtained by subtracting the usage amount used during the predetermined period from the amount frame is set as the usage limit of the second user terminal device linked to the electronic payment service account. make it available for one or more purposes in electronic payment services;
program.

Images