Application programs, service systems, and application systems

Abstract

To improve user experience in user-to-user remittances. [Solution] An application program for receiving network services including user-to-user remittances, the application program causing a first user terminal device of a first user to execute the following processes: a first process of recording a first video in accordance with the operation of the first user; a second process of accepting input of the amount to be remitted by the first user to a second user; and a third process of making the first video playable on a second user terminal device of the second user and requesting a service server to deposit the amount into the account of the second user.

Description

[Technical Field]

[0001] The present invention relates to an application program, a service system, and an application system. [Background technology]

[0002] Conventionally, among network services such as electronic payment services, a service for transferring money between users has been provided (Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] Conventional user-to-user remittances only allow simple text comments, which may not improve the user experience when transferring money between users.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objectives is to provide an application program, a service system, and an application system that can enhance the user experience in user-to-user remittances. [Means for solving the problem]

[0006] One aspect of the present invention is an application program for receiving network services including user-to-user remittances, the application program causing a first user terminal device of a first user to execute a first process of recording a first video in accordance with an operation by the first user, a second process of accepting input of an amount to be remitted by the first user to a second user, and a third process of making the first video playable on a second user terminal device of the second user and depositing the amount into the account of the second user. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to improve the user experience in user-to-user remittance. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates basic aspects of brick-and-mortar electronic payment. [Figure 2] FIG. 1 is a diagram illustrating an example of a configuration for performing electronic payment (terminal payment) using a payment application. [Figure 3] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 4] FIG. 10 is a diagram showing an example of the contents of affiliated store / shop information 174. [Figure 5] FIG. 10 is a diagram showing an outline of a processing flow when a user scan is performed. [Figure 6] FIG. 10 is a diagram showing an outline of the processing flow when a store scan is performed. [Figure 7] FIG. 1 is a diagram showing an example of a configuration for performing electronic payment (card payment) using a payment card. [Figure 8] This is a diagram (part 1) conceptually illustrating the flow of user-to-user remittance with video content. [Figure 9] This is a diagram (part 2) conceptually illustrating the flow of user-to-user remittance with video content. [Figure 10] This is a diagram (part 3) conceptually showing the flow of user-to-user remittance with video content. [Figure 11]This is a diagram (part 4) conceptually showing the flow of user-to-user remittance with video content. [Figure 12] FIG. 10 is a diagram showing an example of the contents of remittance content information 176. [Figure 13] 10 is a sequence diagram showing an example of the flow of processing executed by payment application 20 and payment server 100. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0009] [overview] Hereinafter, with reference to the drawings, embodiments of an application program, a service system, and an application system according to the present invention will be described. The application program is an application program for receiving network services, including user-to-user remittances. The service system is an application program with a service server added to the application program, and the application system includes multiple application programs. While the network service may be any service that includes user-to-user remittances, the following description will be directed to an electronic payment service, with the application program referred to as a payment app and the service server referred to as a payment server. The payment app, payment server, and credit card server work together to provide the electronic payment service. The electronic payment service supports payments for the purchase of goods and services at stores. A store may be, for example, a physical store (real-world store) existing in real space, but may also include a virtual store for e-commerce transactions. Virtual stores may also include those operated by entities other than the operator of the electronic payment service. In such cases, when making a payment for a purchase at a virtual store, the user is controlled to transition to an interface screen for the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and electronic payments made at a store are primarily made between the user and the affiliated store. Alternatively, electronic payment may be made between the user and the store.

[0010] [Electronic payment methods at brick-and-mortar stores] FIG. 1 illustrates the basic aspects of brick-and-mortar electronic payments. Electronic payments are generally carried out by three parties: a medium M held by a user U, store equipment E, and a payment system S. The medium M may be a portable computer device such as a smartphone or a credit card. The store equipment E resides in a physical brick-and-mortar store (hereinafter simply referred to as the store) in real space and may include a POS device, a wireless communication device, a credit card reader, a printed code image such as a QR Code (registered trademark), or a display device displaying the code image. In brick-and-mortar electronic payments, information that can identify the user and information about the payment amount are first shared unidirectionally or bidirectionally between the medium M and the store equipment E. At this time, either the medium M or the store equipment E optically reads various information from a code image displayed by the other, provides information via near-field communication (NFC), or reads the PAN (primary account number) using a credit card reader. Then, either the medium M or the store equipment E (the party that obtains information from the other) transmits the payment information required for the payment to the payment system S via a network NW. Both the medium M and the store equipment E may send some information to the payment system S. The payment system S manages various information about the user U and performs electronic payments between the store and the user U in various ways. Electronic payments are performed using either or both of a prepaid system and a postpaid system, or by other methods. In addition, electronic payments may also include so-called online shopping, which is performed between the user's terminal device and the payment system. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc. The various devices that communicate via the network NW, which will be described below, are assumed to have communication devices such as network cards and wireless communication modules.

[0011] [Configuration (Terminal Payment)] 2 is a diagram showing an example of the configuration for performing electronic payment (terminal payment) using a payment app. This electronic payment is performed mainly by a payment app 20 running on a user terminal device 10, which is one of the media M, one or more store payment terminals 30 and one or more store code images 40, which are one of the store facilities E, and a payment server 100, which constitutes part of a payment system S. The payment server 100 communicates with the user terminal device 10, the store payment terminal 30, and one or more information terminals 50 via a network NW.

[0012] The user terminal device 10 is a portable terminal device such as a smartphone or tablet. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a central processing unit (CPU), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, which operates in cooperation with a payment server 100 to provide electronic payment services to users. The payment application 20 is installed on the user terminal device 10 from, for example, an application distribution server (not shown) and controls the camera, communication device, touch panel, etc. of the user terminal device 10. In the following description, the terms "send information to the user terminal device 10 (or receive / acquire information from the user terminal device 10)" and "send information to the payment application 20 (or receive / acquire information from the payment application 20)" may be used interchangeably, but these terms are merely different expressions and are not intended to distinguish between them.

[0013] The store payment terminal 30 is installed, for example, in a store. The store payment terminal 30 is a computer device (or a collection of these) that has at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The store payment terminal 30 includes a so-called POS (Point of Sale) device, and the POS device may have a product price acquisition function and an optical reading function.

[0014] The store code image 40 is placed in a store and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 40 may be displayed on a display placed in the store (or on a display of a terminal device such as a smartphone or tablet terminal).

[0015] The information terminal 50 is used by the operator of the affiliated store who oversees the stores. In electronic payment services, customers who provide goods or services are treated as affiliated stores (brands), and one or more stores exist under the affiliated store. An affiliated store may operate only one store. The information terminal 50 is a smartphone, tablet terminal, personal computer, etc. An affiliated store interface 55 runs on the information terminal 50. The affiliated store interface 55 may be an affiliated store app or a web page displayed by a general-purpose browser. The affiliated store interface 55 accepts coupon settings and the like from the affiliated store operator and transmits them to the payment server 100. By executing the affiliated store interface 55, the information terminal 50 may have the function of displaying a code image corresponding to the store code image 40 or reading a code image displayed by the user terminal device 10 (in the latter case, an optical reading function is required).

[0016] The payment server 100 communicates with the credit card server 200 via a network NW. The payment server 100 has, for example, a content provider 110, an information manager 120, a payment processor 130, a user-to-user remittance manager 140, a video monitor 150, and a memory 170. The components other than the memory 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented using a large scale integration (LSI), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. The program may be realized by hardware (including circuitry) such as a Gate Array (GPU) or a Graphics Processing Unit (GPU), or may be realized by a combination of 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 a hard disk drive (HDD) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

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

[0018] The content providing unit 110 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The content providing unit 110 provides the content to the user terminal device 10 in the form of a web page, and provides the user terminal device 10 with parameters required for the payment application 20 to render an image.

[0019] The information management unit 120 edits, adds, deletes, etc., user information 172 and affiliated store / shop information 174, and manages them.

[0020] 3 is a diagram showing an example of the contents of user information 172. User information 172 is information in which, for example, user URL, account ID, phone number, password, registration date, charge balance, electronic money type, terminal payment method, card payment method, various history information, identity verification flag, name, address, date of birth, email address, bank account, deferred payment settings, deferred payment condition information, friend list, and other information are associated with each other. Hereinafter, a user instance (electronic payment account) in which this information is associated may be referred to as an account. In the figure, items marked with "-" indicate that they are not set.

[0021] The user URL is used for remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. The account ID is issued to the user by the payment server 100. The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). The charge balance is information indicating the balance of electronic money that the user has set by transferring money to the account in advance. Remittance methods include depositing money into an ATM (Automatic Teller Machine) of a designated service provider (bank) or transferring money from a registered bank account. The type of electronic money is information indicating, for example, whether the electronic money can be withdrawn or can only be used for electronic payments. The terminal payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or by deferred payment in terminal payment. The card payment method is setting information indicating whether the user will make electronic payment using the charge balance (balance payment) or by deferred payment in card payment. The various historical information includes charge history, which is a history of the user transferring money to the electronic payment service in advance to increase the charge balance; payment history, which shows the details of the payments made by the user for each payment (date and time, store ID of the store where the purchase was made, affiliated store ID, payment amount, payment method, etc.); chat history, which is a history of the chat function provided by the electronic payment service; and user-to-user remittance history, which is a history of user-to-user remittances provided by the electronic payment service.

[0022] The identity verification flag is information indicating whether or not the user has completed identity verification using an ID document. Deferred payment can be selected if identity verification has been completed, and the user with account ID "002" in the figure has not completed identity verification and can only select balance payment as the terminal payment method. The bank account is the account number of a bank account that can be used to deposit funds into the electronic payment service. Deferred payment settings is information indicating whether or not the settings have been completed to make deferred payment available for selection. Deferred payment condition information is information indicating various conditions such as the deferred payment limit and the amount used this month. The friend list is information on other users who are presented as potential recipients for chats and user-to-user money transfers.

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

[0024] The payment processing unit 130 performs various processes for electronic payment. There are two methods for terminal payment: a first method (user scan) and a second method (store scan), which will be explained below.

[0025] FIG. 5 shows an overview of the process flow when a user scan is performed. First, the user terminal device 10, with the payment application 20 running, reads and decodes the store code image 40 using its optical reading function (S1). The store code image 40 contains store URL information. The payment application 20 sends first payment information, including the store URL and the user's account ID, to the payment server 100 (S2). The payment server 100 searches the affiliated store / store information 174 using the affiliated store ID and store ID corresponding to the store URL, acquires information about the affiliated store name and store name (S3), and sends this to the payment application 20 (S4). The user enters the payment amount into the payment application 20 on the screen displaying the affiliated store name and store name (S5). The payment application 20 then generates second payment information including at least the payment amount and sends it to the payment server 100 (S6).

[0026] If the "Terminal Payment Method" in the user information 172 of the user is set to "Balance Payment," the payment processing unit 130 of the payment server 100 performs electronic payment based on the received second payment information (S7-1). At this time, 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 affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not used as electronic money itself, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle determined by an agreement between the affiliated store and the electronic payment service. On the other hand, if the "Terminal Payment Method" is set to "Deferred Payment," the payment processing unit 130 transmits the first payment information and the second payment information to the credit card server 200 to request electronic payment (S7-2). The credit card server 200 performs electronic payment by adding the payment amount to the user's monthly usage amount based on the received information and deducting the monthly usage amount from the user's bank account after the closing date (S7-3).

[0027] Then, the payment processing unit 130 sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 via the content providing unit 110 (S8), and the payment app 20 displays the payment completion screen (S9). When the store code image 40 is displayed on a display installed in the store, the store code image 40 may include information on the payment amount in addition to the store URL. In this case, the procedure for the user to input the payment amount is omitted, and the information on the payment amount is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0028] FIG. 6 is a diagram showing an overview of the processing flow when a store scan is performed. First, when the payment app 20 is launched, when a payment operation is performed using the payment app 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment app 20 sends a request to issue a one-time code to the payment server 100 (S11). The payment processing unit 130 of the payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code or barcode, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the store payment terminal 30, and the store payment terminal 30 reads and decodes the code image using its optical reading function to obtain the one-time code, etc. (S15). The store payment terminal 30 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it.

[0029] The payment processing unit 130 of the payment server 100 identifies the user corresponding to the one-time code based on the received information, and if the "terminal payment method" in the user information 172 of the user is set to "balance payment," it performs electronic payment based on the received second payment information (S17-1). The processing content at this time is the same as the processing of S7-1 in FIG. 5. On the other hand, if the "terminal payment method" is set to "post-payment," the payment server 100 transmits the first payment information and the second payment information to the credit card server 200 to request electronic payment (S17-2). The credit card server 200 adds the payment amount to the user's monthly usage amount based on the received information, and performs electronic payment by deducting the monthly usage amount from the user's bank account after the closing date (S17-3).

[0030] Then, the payment processing unit 130 transmits a payment completion notification to the payment application 20 via the content providing unit 110 (S18), and the payment application 20 displays a payment completion screen (S19).

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

[0032] It should be noted that the "post-payment" settlement may be performed within the settlement server 100, rather than being managed by the credit card server 200. In this case, the components such as the settlement card 60 and the credit card server 200 may be omitted.

[0033] The inter-user remittance management unit 140, the video monitoring unit 150, and the remittance content information 176 will be described later.

[0034] [Configuration (Card Payment)] 7 is a diagram showing an example of a configuration for performing electronic payment (card payment) using a payment card. This electronic payment is performed mainly using a payment card 60, which is one of the media M, a credit card processing terminal 70, which is one of the store facilities E, a payment server 100, which constitutes part of a payment system S, and a credit card server 200. The credit card server 200 communicates with the credit card processing terminal 70 via a network NW.

[0035] The credit processing terminal 70 is installed in the store, similar to the in-store payment terminal 30. The credit processing terminal 70 includes, for example, a credit card reader and a POS device. The credit card terminal reads a personal identification number (PIN) from an inserted or held-up credit card and compares it with the PIN entered by the user. It also transmits a primary account number (PAN) read from the credit card to the credit card server 200 via the POS device. The POS device cooperates with the credit card terminal to transmit information such as the payment amount to the credit card server 200. A payment agent server (acquirer) may be interposed between the credit card processing terminal 70 and the credit card server 200; however, for simplicity, the following description omits the server server. The payment card 60 is, for example, similar to a commonly used credit card, with a communication chip embedded in the card substrate. The communication chip incorporates a storage medium storing the PIN and communicates with an external device via a contactor (or a wireless antenna). Alternatively, the payment card 60 may be a magnetic card. The information (messages) sent and received when using a credit card include an authorization message for authentication and a sales message for conveying the payment amount, but detailed explanations distinguishing between these will be omitted below.

[0036] The credit card server 200 communicates with the payment server 100 via a network NW. The credit card server 200 includes, for example, an information management unit 210, a credit interface 220, a payment allocation unit 230, a credit payment processing unit 240, and a memory unit 270. The components other than the memory unit 270 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device. The memory unit 270 stores information such as card user information 272.

[0037] The information management unit 210 edits, adds, deletes, etc., and manages the card user information 272. The card user information 272 is information in which, for example, information unique to a user (e.g., PAN), a card payment method, and the user's account ID (used by the payment server 100) are associated with one another. The card payment method is setting information that indicates whether the user will make electronic payment using the charged balance (balance payment) or deferred payment when making a card payment.

[0038] The credit interface 220 determines whether the BIN (Bank Identification Number) in the PAN included in the message received from the credit processing terminal 70 is a code for the company, and if it is a code for the company, passes the message received from the credit processing terminal 70 to the payment allocation unit 230, and if it is not a code for the company, discards the received message.

[0039] The payment allocating unit 230 refers to the card user information 272 of the user corresponding to the message obtained from the credit interface 220, and determines whether the "card payment method" is set to "post-payment." If the "card payment method" is set to "post-payment," the payment allocating unit 230 notifies the credit interface 220 of this and passes the message obtained from the credit interface 220 to the credit payment processing unit 240. On the other hand, if the "card payment method" is set to "balance payment," the payment allocating unit 230 adds the user's account ID to the message obtained from the credit interface 220 and sends it to the payment server 100, requesting electronic payment. When requested to make electronic payment, the payment server 100 performs the same processes as S7-1 in Figure 5 and S17-1 in Figure 6.

[0040] The credit interface 220 checks the PAN and expiration date, and verifies whether the cumulative payment amount exceeds the current month's upper limit, etc. The credit payment processing unit 240 adds the payment amount to the user's monthly usage amount based on the information contained in the message obtained from the payment allocation unit 230, and performs electronic payment by deducting the monthly usage amount from the user's bank account after the closing date.

[0041] [User-to-user remittance with video content] The following describes user-to-user remittance with video content provided by the payment app 20 and the payment system. In response to an operation by a first user, the payment app 20 and the payment system generate content (remittance content) in which information on the amount of remittance to be made between users is embedded in a video, for example in the form of an animation, and make the remittance content playable by the payment app 20 of a second user. Note that the term "third user" in the claims refers, for convenience, to the user who sends the remittance content when the destination of the remittance content is the first user; the second user may also be the "third user."

[0042] 8 to 11 are diagrams conceptually illustrating the flow of user-to-user remittance with video content. Referring to FIG. 8, the process of user-to-user remittance with video content is initiated, for example, by the first user U1 operating icon IC1 on the display screen of the payment application 20 of the first user terminal device 10-1 ((1) in the figure). Note that a flow line for starting the process of user-to-user remittance with video content from the display screen of a chat room, etc., may be provided. First, the first user U1 selects a remittance recipient from the friend list of the user information 172, etc. (not shown), sets the amount to be remitted, and the payment application 20 accepts this ((2) in the figure). This process is an example of the second process.

[0043] Referring to FIG. 9, the payment application 20 records the first video in response to an operation by the first user U1 ((3) in the figure). This process is an example of the first process. It does not matter which of the first process and the second process is executed first. In a typical usage scenario, the first user U1 takes (records) an image of his or her own face using the camera function of the first user terminal device 10-1, and also records a congratulatory message or the like.

[0044] Next, the payment application 20 accepts editing of the remittance content by the first user U1 ((4) in the figure). This process is an example of the fourth process. The remittance content is content in which an image displaying the amount is embedded in the first video. The first user U1 can select graphics (sunglasses, hat, etc.) to accompany the facial image, effects to apply to the entire first video, and the playback start and end timings for the remittance content image displaying the amount. The timing is specified, for example, by the first user U1 specifying the playback start and end timings for a time bar that indicates the temporal progression of the first video. Next, the payment application 20 accepts the first user U1's selection of the format of the image displaying the amount (for example, a lucky envelope from which a card showing the amount is taken out) ((5) in the figure).

[0045] Next, when the payment application 20 receives a confirmation operation for the remittance content from the first user U1, it generates the remittance content based on the results of the processes (2) to (5) in the figure. The image displaying the amount is, for example, an animation generated to display the amount while the first video is playing. Then, when the payment application 20 receives an instruction to send the remittance content from the first user U1, it requests the payment server 100 to transfer (transfer) the set amount of the charge balance to the account of the second user U2, for example, as the remittance content is played. The payment application 20 transmits to the payment server 100, for example, the remittance content (including the first video, graphics, effects, the format and display timing of the image displaying the amount, and audio), information specifying the second user U2, and package information including the amount to be remitted. Note that the payment application 20 may transmit the remittance content itself to the payment server 100, or may store the remittance content on a video distribution server different from the payment server 100 and transmit information about the available location (for example, a URL) to the payment server 100. This allows the remittance content (first video) to be played on the second user terminal device 10-2 of the second user U2. Information that the remittance content has been acquired is notified to the second user U2, for example, by posting activation information for the remittance content in a chat room and sending a push notification. This series of processes is an example of the third process. The payment application 20 may generate the remittance content with the support of the payment server 100 or an external video generation server (by requesting partial processing).

[0046] Referring to FIG. 10, the second user U2 plays the remittance content by selecting chat room activation information in the payment application 20 running on the second user terminal device 10-2 ((6) to (8) in the figure). As shown in the figure, the remittance content is content in which the amount to be remitted is displayed as the video plays. By associating the remittance content including the first video with a user-to-user remittance, the user experience can be improved compared to simply sending money with a text message.

[0047] Referring to FIG. 11, when playback of the remittance content is completed, the payment app 20 of the second user U2 sends a playback completion notification to the payment server 100 and displays icon IC2, which prompts the user to shoot and send a reaction video ((9) in the figure). When icon IC2 is operated by the second user U2, the payment app 20 of the second user U2 starts shooting (recording) a reaction video to be sent back to the first user U1 (or a third user if the first user U1 has acquired the remittance content). This shooting is performed in the same way as shooting the first video, and the reaction video may be editable. When shooting of the reaction video is completed, the payment app 20 of the second user U2 sends the reaction video to the payment app 20 of the first user U1 via the payment server 100 in response to an operation by the second user U2.

[0048] Here, activation information for one or both of the remittance content and the reaction video may be transmitted and received between users using a network service separate from the payment service. For example, they may be transmitted and received using a channel such as a social network service (SNS). In this case, a link for playing the remittance content or the reaction video is transmitted and received on the SNS, and operating the link launches the payment application 20 to play the content.

[0049] The user-to-user remittance management unit 140 of the payment server 100 manages normal user-to-user remittances that do not involve remittance content, and also manages user-to-user remittances that involve the remittance content described above, using the remittance content information 176. FIG. 12 is a diagram showing an example of the contents of the remittance content information 176. The remittance content information 176 associates, for example, a remittance content ID with information such as a remitter ID, a remittance receiver ID, a remittance content (or reference information thereof), a played flag, an amount, an expiration date, and a reaction video (or reference information thereof). When the user-to-user remittance management unit 140 receives a playback completion notification from the payment app 20 of the second user U2 that has received the remittance content, it searches the remittance content information 176 for a record in which the ID of the second user U2 is registered as the receiver ID, changes the played flag of that record from "not yet" to "played," and adds the corresponding amount to the second user U2's charge balance (or an equivalent to the charge balance, such as points). The process of deducting the amount from the charge balance of the first user U1 may be performed when the remittance content is acquired from the payment application 20 of the first user U1, or when a playback completion notice is acquired from the payment application 20 of the second user U2. The expiration date may be set to, for example, one to several months from the creation of the remittance content, and the user-to-user remittance management unit 140 may notify the remitter and invalidate the remittance content when the expiration date has passed.

[0050] The video monitoring unit 150 determines whether remittance content or reaction videos registered in the remittance content information 176 with a played flag set to "not played" contain inappropriate content. For example, the video monitoring unit 150 obtains the determination result as to whether inappropriate content is included by inputting the remittance content or reaction video into a generation AI. The generation AI may be held by the payment server 100 or may be provided by an external generation AI server. If it is determined that inappropriate content is included, the video monitoring unit 150 notifies the payment application 20 that is the sender and prohibits playback of the remittance content or reaction video (or allows playback only if the playback user agrees to the warning).

[0051] 13 is a sequence diagram showing an example of the flow of the processing executed by the payment application 20 and the payment server 100 described above. First, the payment application 20 of the first user U1 generates remittance content (S100). The payment application 20 of the first user U1 transmits the remittance content to the payment server 100 and makes a remittance request (S102). The payment server 100 registers the received information in the remittance content information 176 (S104) and notifies the payment application 20 of the second user U2 that the remittance content has been sent (S106).

[0052] The payment application 20 of the second user U2 notifies the second user U2 of the existence of the remittance content (S108). When the remittance content is played back in response to the operation of the second user U2 (S110), the payment application 20 of the second user U2 sends a playback completion notice to the payment server 100 (S112). At this time, if a reaction video has been filmed, it is also sent to the payment server 100. The payment server 100 completes the remittance process in response to the playback completion notice (S114) and rewrites various information in the remittance content information 176. The payment server 100 sends a remittance completion notice to the payment application 20 of the first user U1 (S116). If a reaction video has been filmed, it is also sent to the payment application 20 of the first user U1. In this case, the reaction video is played back in the payment application 20 of the first user U1 (S118).

[0053] The above-described embodiment enhances the user experience of user-to-user remittances compared to simply sending a text message. For example, when sending money as a New Year's gift or birthday present, accompanying remittance content conveys the feelings of both the sender and the recipient, and can also foster communication beyond the exchange of money. Furthermore, by requiring the remittance content to be played before the remittance process can be performed, the recipient can decline to receive the money if they are not interested.

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

[0055] E. Store Facilities M medium S payment system 10 User terminal device 20. Payment App 30 Store payment terminals 40 Store code image 60 Payment Cards 70 Credit card processing terminal 100 Payment Server 130 Payment processing unit 140 User Remittance Management Department 150 Video Surveillance Department 176 Remittance Content Information 200 Credit Card Server

Claims

1. An application program for receiving network services including user-to-user remittance, to a first user terminal device of the first user, a first process of recording a first video in response to an operation by the first user; a second process of accepting an input of an amount of money to be remitted by the first user to the second user; a third process of transmitting information for enabling the first video to be played on the second user terminal device of the second user and for depositing the amount into the account of the second user to a service server that provides the network service and that deducts the amount related to the user-to-user remittance from the balance of the remitter and adds it to the balance of the receiver; An application program for executing the third process is a process of generating remittance content in which an image displaying the amount is embedded in the first video, and making the remittance content reproducible on the second user terminal device; Application program.

2. causing the first user terminal device to execute a fourth process of accepting editing of the remittance contents by the first user; 2. The application program according to claim 1.

3. the fourth process includes a process of accepting a selection of a display mode of the image displaying the amount, 3. The application program according to claim 2.

4. the fourth process includes a process of accepting a selection of an effect to be added to the first moving image.

4. The application program according to claim 2 or 3.

5. the remittance content is content in which the amount is displayed during playback of the first video; 2. The application program according to claim 1.

6. the third process is a process of requesting the service server to deposit the amount into the account of the second user on the condition that the remittance content has been played; 2. The application program according to claim 1.

7. The first user terminal device When the remittance content is received from the third user, a second video is recorded as a reply to the third user.

2. The application program according to claim 1.

8. The application program according to claim 1; the service server having a user-to-user remittance management unit that deducts the amount of the user-to-user remittance from the remitter's balance and adds it to the recipient's balance; A service system comprising:

9. the service server includes a video monitoring unit that restricts playback of inappropriate videos; The service system according to claim 8.

10. An application system having a plurality of application programs for receiving network services including user-to-user remittance, to a first user terminal device of the first user, a first process of recording a first video in response to an operation by the first user; a second process of accepting an input of an amount of money to be remitted by the first user to the second user; a third process of transmitting information for enabling the first video to be played on the second user terminal device of the second user and for depositing the amount into the account of the second user to a service server that provides the network service and that deducts the amount related to the user-to-user remittance from the balance of the remitter and adds it to the balance of the receiver; a first application program for executing the above; The second user terminal device a second application program for recording a second video to be sent back to the first user when the first video is received from the first user; An application system comprising: the third process is a process of generating remittance content in which an image displaying the amount is embedded in the first video, and making the remittance content reproducible on the second user terminal device; App system.

Images