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

Abstract

An information processing device, an information processing method, and an information processing program for improving usability for a service user when receiving a predetermined gift provided online. A settlement server (100) has a registration section (131) and a remittance processing section (135) in an information processing system in which a terminal device and a settlement server are communicably connected to each other via a network. In response to a request from a service user of an electronic payment service capable of exchanging digital money between individuals, the registration unit 131 associates the service user with the user identification information for identifying the service user. Register the collection identification information assigned individually to each. When the remittance processing unit 135 receives a remittance request with the collection identification information as the remittance destination, the remittance processing unit 135 performs the remittance corresponding to the remittance request without requesting the service user of the remittance destination to perform a receiving operation in response to the remittance request. Automatically process directed transactions. [Selection drawing] Fig. 8

Description

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

In recent years, platforms have been developed that make it possible to distribute independently produced content through networks such as the Internet, and we are entering an era in which anyone can easily become a creator in online communication. Also, for example, in such online communication, a technology has been proposed in which a viewer sends a predetermined gift online to a content provider for the purpose of supporting the content provider.

JP 2022-021250 A

However, conventional technology is required to improve usability for service users when receiving a predetermined gift provided online. For example, when receiving digital money sent online, the service user must perform a receiving operation each time. For this reason, if the frequency of receiving operations increases, the usability for service users will drop significantly.

The present application has been made in view of the above, and aims to provide an information processing device, an information processing method, and an information processing program that can improve usability for service users when receiving a predetermined gift provided online. aim.

An information processing device according to the present application includes a registration unit and a remittance processing unit. In response to a request from a service user of an electronic payment service that enables the exchange of digital money between individuals, the registration unit associates it with user identification information for identifying the service user and sends it to the service user. Individually assigned bill collection identification information is registered. When the remittance processing unit receives a remittance request to which the collection identification information is the remittance destination, the remittance processing unit issues a remittance instruction corresponding to the remittance request without requesting the service user of the remittance destination to perform a receiving operation in response to the remittance request. Process transactions automatically.

According to one aspect of the embodiment, it is possible to improve usability for the service user when receiving a predetermined gift provided online.

FIG. 1 is a diagram illustrating an overview of shared content provision processing according to an embodiment. FIG. 2 is a diagram showing a display example (Part 1) of the tipping room according to the embodiment. FIG. 3 is a diagram showing a display example (part 2) of the tipping room according to the embodiment. FIG. 4 is a diagram showing an example of the tipping room after reflecting the processing result of the remittance instruction transaction corresponding to the tipping request according to the embodiment. FIG. 5 is a diagram showing an example of the remittance destination selection screen after reflecting the processing result of the remittance instruction transaction corresponding to the tip request according to the embodiment. FIG. 6 is a diagram showing an overview of creator registration processing according to the embodiment. FIG. 7 is a diagram showing an example of providing information in a tipping room according to the embodiment. FIG. 8 is a diagram showing a configuration example of a settlement server according to the embodiment. FIG. 9 is a diagram illustrating an example of a user information database according to the embodiment; FIG. 10 is a diagram showing an example of wallet information stored in the wallet information database according to the embodiment. FIG. 11 is a diagram illustrating an example of information stored in a remittance history database according to the embodiment; FIG. 12 is a flowchart illustrating an example of an information processing procedure executed by the settlement server according to the embodiment; FIG. 13 is a hardware configuration diagram showing an example of a computer that implements the functions of the payment server according to the embodiment.

Embodiments for implementing an information processing apparatus, an information processing method, and an information processing program according to the present application (hereinafter referred to as "embodiments") will be described in detail below with reference to the drawings. The information processing apparatus, information processing method, and information processing program according to the present application are not limited to this embodiment. Also, in each of the following embodiments, the same parts are denoted by the same reference numerals, and overlapping descriptions are omitted.

[1. embodiment]
Information processing realized by the information processing apparatus according to the embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating an overview of shared content provision processing according to an embodiment. In FIG. 1, the information processing and the like according to the embodiment are assumed to be realized by the settlement server 100, which is an example of the information processing apparatus according to the embodiment.

(1-1. System configuration)
As shown in FIG. 1, the information processing system SYS according to the embodiment includes a terminal device 10 and a payment server 100. The terminal device 10 and the settlement server 100 are communicably connected to each other by wire or wirelessly via a network N (see FIG. 8, for example). Network N is, for example, a WAN (Wide Area Network) such as the Internet. The information processing system SYS shown in FIG. 1 may include multiple terminal devices 10 and multiple payment servers 100 .

A settlement server 100 shown in FIG. 1 is an information processing device that executes information processing according to the embodiment, and is realized by a server device, a cloud system, or the like. For example, the administrator of the payment server 100 is a platform that provides service users with an electronic payment service related to electronic payment using the terminal device 10 (a service that provides a predetermined means of transaction for controlling the exchange of electronic money by code payment). Deploy services. The payment server 100 executes information processing related to electronic payment services. Also, the electronic payment service includes a remittance service that enables exchange of digital money between individuals. Specifically, the payment server 100 distributes an application program for a user terminal (hereinafter referred to as a “user application” as appropriate) for realizing code payment to general consumers who are service users. When the settlement server 100 receives a transaction request from the user application via the interface dedicated to the user application, the settlement server 100 exchanges electronic money, virtual currency, etc. between accounts (between wallets linked to user accounts) in accordance with the transaction request. Executes information processing including the exchange of digital money (hereinafter referred to as “electronic money”). The user application has a function of transmitting transaction information including information such as a settlement destination (remittance destination), a settlement source (remittance source), and a settlement amount (remittance amount) to the settlement server 100 . In addition to the above-mentioned information, transaction information includes information such as a transaction code to identify individual transactions and date and time information (timestamp) to identify the date and time of a transaction. may

In addition, as part of the services described above, the settlement server 100 accepts use registration of a creator ID (an example of “collection identification information”), which will be described later, in response to a request from a service user. A creator ID is identification information used when a service user of an electronic payment service raises funds from another service user. For example, the creator ID is used as remittance destination identification information indicating the remittance destination of electronic money to be remitted as support from viewers for distributed content.

The terminal device 10 shown in FIG. 1 is an information processing terminal used by a service user (for example, service user UZ) who uses the electronic payment service provided by the payment server 100 . The terminal device 10 is implemented by, for example, a smart phone, a tablet terminal, a notebook PC (Personal Computer), a desktop PC, a mobile phone, a PDA (Personal Digital Assistant), or the like. In addition, the terminal device 10 displays information distributed by the settlement server 100 using a web browser or an application. Note that FIG. 1 illustrates a smartphone as the terminal device 10 .

When the terminal device 10 receives control information for implementing predetermined information processing from the settlement server 100, the terminal device 10 implements the information processing according to the control information. Here, the control information includes, for example, a script language such as JavaScript (registered trademark), a style sheet language such as CSS (Cascading Style Sheets), a programming language such as Java (registered trademark), and a markup language such as HTML (HyperText Markup Language). It is described by language or the like. Note that the predetermined application itself distributed from the settlement server 100 may be regarded as the control information.

(1-2. Settlement using terminal device 10)
Here, an example of code payment (electronic payment) using the terminal device 10 will be described. In the following description, a two-dimensional code (QR code (registered trademark)) placed at the store X and indicating store identification information for identifying the store X is used to provide a transaction target from the store X. An example in which the service user UZ who receives the payment makes a payment using the terminal device 10 will be described. It should be noted that an example of code settlement described below can also be applied when any service user uses any terminal device 10 to make a payment at any store. Also, the two-dimensional code indicating the store identification information may be not only a QR code but also a bar code, a predetermined mark, a number, or the like. Further, the two-dimensional code is not limited to the example physically configured by printed matter printed on a medium such as paper, and may be configured by image information displayed on an arbitrary terminal. The store identification information includes a member store ID that is individually assigned to identify the brand of store X as a member store of the electronic payment service, and a store ID that is assigned to identify the store X itself. may be

For example, when the service user UZ makes a payment accompanying the purchase or use of a transaction target such as various products and services at the store X, the service user UZ activates a user application pre-installed in the terminal device 10 . Then, the service user UZ photographs the two-dimensional code installed at the store X via the user application. In such a case, the terminal device 10 displays a screen for inputting the price of the transaction object, and receives the input of the payment amount from the service user UZ or the store X clerk. Then, the terminal device 10 includes user identification information that identifies the service user UZ, shop identification information (or information indicated by the shop identification information, namely information indicating the shop X (for example, shop ID)), and payment to the settlement server 100.

When the settlement server 100 receives the transaction information from the terminal device 10, the account of the service user UZ indicated by the user identification information (wallet linked to the user account) is transferred to the account of the store X indicated by the store identification information (to the user account). The electronic money equivalent to the settlement amount is transferred to the linked wallet). At this time, the settlement server 100 may deduct a predetermined fee to be charged to the store X from the amount of electronic money corresponding to the settlement amount, and then transfer the electronic money to the account of the store X. The settlement server 100 then transmits a notification that the transaction has been completed to the terminal device 10 . In such a case, the terminal device 10 notifies the service user UZ that the transaction with electronic money has been completed by outputting a screen or a predetermined voice indicating that the transaction has been completed. Alternatively, the settlement server 100 withdraws electronic money corresponding to the settlement amount from the account of the service user UZ indicated by the user identification information, manages it as sales information of the store X, and manages the amount corresponding to the sales at a predetermined timing. may be transferred to the bank account owned by store X. In this case, the settlement server 100 may notify the service user UZ that the electronic money transaction is completed at the timing when the electronic money equivalent to the settlement amount is withdrawn from the account of the user UX.

Note that the settlement using the terminal device 10 is not limited to the processing described above. For example, settlement using the terminal device 10 may be performed using a terminal device installed at the store X (hereinafter referred to as a "store terminal"). Specifically, first, the terminal device 10 displays code information indicating user identification information for identifying the service user UZ on the screen. In such a case, the store terminal reads the user identification information from the code information displayed on the terminal device 10, and indicates the read user identification information (or information indicated by the user identification information, that is, the user UX). Transaction information including information (for example, user ID), payment amount, and information identifying store X is transmitted to payment server 100 .

When the transaction information is received from the store terminal, the settlement server 100 transfers electronic money corresponding to the settlement amount from the account of the service user UZ indicated by the user identification information to the account of the store X. The settlement server 100 then transmits a notification to the effect that the transaction has been completed to the shop terminal or the terminal device 10 . The store terminal or the terminal device 10 notifies the service user UZ that the transaction with electronic money has been completed by outputting a screen or a predetermined voice indicating that the transaction has been completed. In addition, the settlement server 100 withdraws electronic money corresponding to the settlement amount from the account of the service user UZ indicated by the user identification information, manages it as sales information of the store X, and manages the amount corresponding to the sales at a predetermined timing. may be transferred to the bank account owned by store X. In this case, the settlement server 100 may notify the clerk or the service user UZ that the electronic money transaction is completed at the timing when the electronic money corresponding to the settlement amount is withdrawn from the account of the service user UZ. good.

In addition, the settlement using the terminal device 10 is not only the process of transferring electronic money from the account charged with electronic money in advance by the service user UZ to the account of the store X, but also, for example, Payment may be made using a credit card. In such a case, for example, the terminal device 10 transfers the amount of electronic money indicated by the settlement amount to the account of the store X, and transfers the amount indicated by the settlement amount to the operating company of the credit card of the service user UZ. may be requested.

In addition, the settlement using the terminal device 10 is not only the process of transferring electronic money from the account of the service user UZ to the account of the store X, but also, for example, the account of the service user UZ to the account of another service user It may be a settlement (that is, a remittance between service users) that transfers electronic money to a customer. For example, the terminal device 10 used by the service user UZ of the remittance source has user identification information that identifies the service user who is the user of the remittance destination (for example, the The settlement server receives the input of the remittance amount from the service user UZ, receives the read identification information, the remittance amount, and the user identification information that identifies the service user UZ. Send to 100. In such a case, the settlement server 100 transfers the amount of electronic money indicated by the remittance amount from the account of the service user UZ to the account of the service user of the remittee, and uses the terminal device 10 or the service of the remittee. The completion of the remittance may be notified by causing the terminal device 10 used by the person to output a screen or a predetermined voice indicating that the remittance has been completed.

The remittance using the terminal device 10 is not limited to the processing described above. For example, in remittance using the terminal device 10, the telephone number of the service user who is the user to whom the remittance is to be made, and information indicating the service user who is the user to whom the remittance is to be made (for example, user ID) are input to the terminal device 10. It may be done by To give a specific example, the terminal device 10 accepts input of the telephone number or user ID of the service user to whom the remittance is to be made and the remittance amount from the service user UZ, and (remittance destination identification information), the remittance amount, and user identification information (remittance source identification information) identifying the service user UZ are transmitted to the settlement server 100 . Then, the settlement server 100 transfers the amount of electronic money indicated by the remittance amount from the account of the service user UZ to the account of the service user linked to the transmitted telephone number or user ID.

Here, the telephone number and user ID of the service user, who is the user of the remittance destination, may be linked with information about the user and registered in advance in the user application. In this case, the terminal device 10 accepts from the user UX the designation of a user (remittance destination) registered in the user application and the input of the remittance amount to the user, and the telephone number associated with the designated user. Alternatively, the user ID, remittance amount, and user identification information for identifying the user UX are transmitted to the settlement server 100 .

Further, for example, remittance using the terminal device 10 may be performed by providing link information for receiving the remittance amount to the service user who is the remittee user. As a specific example, the terminal device 10 receives an input of the remittance amount from the service user UZ, generates link information for receiving the remittance amount, transmits an e-mail containing the link information, or sends an e-mail containing the link information. By posting posted information including to SNS (Social Networking Service), link information is provided to the terminal device 10 used by the service user who is the user of the remittance destination. Then, when the service user who is the user of the remittance destination selects the link information and performs a receiving operation, the settlement server 100 transfers the information from the account of the service user UZ to the account of the service user who is the user of the remittance destination. , the amount of electronic money indicated by the remittance amount is transferred. As described above, the payment server 100 can execute information processing related to payment using electronic money and remittance of electronic money on the same platform that provides electronic payment services to service users.

It should be noted that the payment means and payment services described above are not limited to those for the provision of compensation for the purchase of goods or the provision of services (settlement of obligations). For example, as described above, the payment means or payment service may have functions related to remittances between accounts owned by multiple users. In other words, the payment means and payment service described above may be any service that controls transmission and reception of electronic money between accounts of any owner linked to the owner of electronic money, such as a user or a store. In other words, the settlement means and settlement service according to the embodiments are not limited to various controls for realizing exchange of electronic money (control of various inter-account remittances via electronic money, but also controls for exchange between an electronic money account and a bank account). Various types of credit processing such as control, division, processing accompanying bonus payments, and other various types of control related to the exchange of property including electronic money) can be provided in any form. good too. In addition, the various controls realized by such transaction means and transaction services may include both control related to payment and control related to remittance, or may include only one of them. That is, "transaction" is a concept that includes not only "settlement" related to electronic money, but also "remittance" of electronic money and various other processes. In other words, the settlement server 100 may be an information processing device that implements transaction means for controlling the exchange of electronic money between arbitrary owners.

(1-3. Outline of Embodiment)
(1-3-1. Shared content provision processing)
The outline of the information processing executed by the settlement server 100 will be described below. First, the process of providing shared content will be described with reference to FIG. FIG. 1 is a diagram illustrating an overview of shared content provision processing according to an embodiment. An example of information processing executed by the payment server 100 when the service user UZ makes an online remittance to a creator who provides content through an electronic payment service platform will be described below. Moreover, below, the case where the gift given to the creator is a coin tip will be exemplified.

As shown in FIG. 1, the terminal device 10-1 transmits, to the settlement server 100, the remittee identification information specified by the service user UZ as the remittee of electronic money (step S1). Hereinafter, the flow until the shared content is provided from the payment server 100 to the terminal device 10-1 will be described in detail, including screen transitions of the user application displayed on the terminal device 10-1.

For example, the service user UZ operates the terminal device 10-1 to activate the user application, thereby displaying the top screen W1 of the user application on the terminal device 10-1. For example, the top screen W1 is provided with an icon OB1 for remittance of electronic money. The service user UZ causes the terminal device 10-1 to display a remittance destination selection screen W2 for selecting a remittance destination of electronic money by operating the icon OB1 provided on the top screen W1 of the user application. Then, the service user UZ selects a remittance destination on the remittance destination selection screen W2.

On the remittance destination selection screen W2 shown in FIG. 1, a list of contact information including icons and display names is displayed. In addition, on the remittance destination selection screen W2 shown in FIG. 1, there are tabs for displaying the selection history of remittance destinations selected by the service user UZ in the past as remittance destinations, and a tab for displaying the selection history of the remittance destinations that the service user UZ has selected as a remittance destination in the past. There are tabs for displaying the contact information set at the time and tabs for displaying creators who have been selected as remittance destinations by the service user UZ in the past. The remittance destination selection screen W2 shown in FIG. 1 shows information in which the remittance destination selection history tab by the service user UZ is selected.

In addition, the remittance destination selection screen W2 shown in FIG. 1 is provided with a search box for searching for remittance destinations. For example, as shown in FIG. 1, when the service user UZ enters information associated with the service user to be designated as the remittee in the search box of the remittance destination selection screen W2, a search result screen W3 showing the search results is displayed on the terminal. Displayed on device 10-1. Examples of information associated with service users that can be entered in the search box include user IDs that are user identification information for electronic payment services, telephone numbers, user display names for electronic payment services, and creator IDs. . Information that can be entered in the search box does not have to be complete information, and may be a character string indicating part of the information.

Specifically, the user application running on the terminal device 10-1 transmits the search character string “XXX” entered in the search box to the settlement server 100. FIG. When receiving the search string "XXX" from the user application, the settlement server 100 refers to the user information, searches for the remittance destination information corresponding to the received search string "XXX", and obtains the remittance destination information. do. At this time, if information linked to the creator ID is included in the search results corresponding to the search character string, the payment server 100 separates the remittance destination information linked to the creator ID from the other remittance destination information. Respond to the user app with search results for display. The user application displays the search results received from the settlement server 100 on the search result screen W3. For example, on the search result screen W3 shown in FIG. 1, two pieces of information about service users are displayed as search results corresponding to the search character string "XXX". They are displayed separately in the column of the creator on the result screen W3.

The service user UZ, for example, selects a service user to be designated as a remittance destination from among the service users displayed as search results on the search result screen W3. For example, FIG. 1 shows an example in which service user UZ selects "USER XXX2" displayed separately in the creator column. As a result, the user application running on the terminal device 10-1 transmits the service user information selected by the service user UZ to the settlement server 100 as the remittance destination information. For example, the user application transmits the creator ID associated with "USER XXX2" selected by the service user UZ to the payment server 100 as the remittance destination information.

In addition, the payment server 100 uses the remittance service in association with the user ID, which is user identification information for identifying service users of the electronic payment service with which individuals can exchange digital money. A remittance history, which is a history of remittances received, is stored. When payment server 100 receives the remittance destination information from the user application running on terminal device 10-1, settlement server 100 sets the remittance history to the creator ID on the condition that the received remittance destination information is the creator ID. (step S2). Also, based on the acquired remittance history, the settlement server 100 generates a coin tipping room W4, which is shared content shared by each service user who made a remittance to the creator ID (step S3). Note that the coin tipping room, which is a shared content, is made by the service user who issued the creator ID (for example, the service user UX shown in FIG. 6) through the creator registration process described later. It is generated by the settlement server 100 in response to a room creation request. Then, the settlement server 100 provides (cooperates with) the generated tipping room W4 to the user application running on the terminal device 10-1 (step S4). Note that if the payment server 100 has already created the tipping room W4 corresponding to the received creator ID at the time of receiving the creator ID as the remittance destination information from the user application, the payment server 100 provides the created tipping room W4 to the user application. Alternatively, a new thread may be started to create the tipping room W4 at the time the creator ID is received from the user application, regardless of whether or not there is a tipping room W4 already created.

The user application running on the terminal device 10-1 displays the tipping room W4 provided by the settlement server 100 on the terminal device 10-1. In the tipping room W4 shown in FIG. 1, there are first objects OB1-1, OB1-2, and OB1 indicating the remittance amount of each service user whose remittance destination is the creator "USER XXX2" selected by the service user UZ. -3 is displayed in order of remittance. In addition, in the tipping room W4 shown in FIG. 1, second objects OB2-1, OB2-2, and OB2-3 indicating messages created by each service user at the time of remittance are displayed in the corresponding first object OB1. displayed in association with each other.

The display form is not limited to that shown in FIG. 1, and the settlement server 100 may generate a coin tipping room W4, which is shared content in which the display form of the first object OB1 indicating the remittance amount is changed according to the remittance amount. FIG. 2 is a diagram showing a display example (Part 1) of the tipping room according to the embodiment. For example, the settlement server 100 may increase the display size of the first object OB1 as the remittance amount increases. Specifically, when the remittance amount satisfies a predetermined condition, the settlement server 100 selects the first object OB1 indicating the remittance amount from the first object OB1 generated when the remittance amount is less than the reference amount. A coin tipping room W4, which is a shared content whose display form is changed so that the size is increased, is generated. For example, if the reference amount is "3,000 yen", the settlement server 100 generates shared content with a changed display form as shown in FIGS. 2 and 3 if the remittance amount is larger than this reference amount. According to FIG. 2, the first object OB1-5 indicating the remittance amount of "10,000 yen" indicates the first object OB1-6 indicating the remittance amount of "500 yen" and the remittance amount of "800 yen". An example of a tipping room W4 configured with a display size larger than that of the first object OB1-7 is shown. Further, according to FIG. 2, the first object OB1-6 indicating the remittance amount of "500 yen" and the first object OB1-7 indicating the remittance amount of "800 yen" are configured to have the same display size. An example of room W4 is shown. Note that the display size may be arbitrarily changed by a variation rate that is preset according to the remittance amount. Further, when payment server 100 receives a message for tipping room W4 from a service user (for example, USER XXX2) who is a remittee, settlement server 100 may generate tipping room W4 that displays a third object indicating the message. good.

Further, when the remittance amount is equal to or more than a predetermined amount (for example, 10,000 yen or more), the settlement server 100 displays the first object OB1 even if the display screen displaying the tipping room W4, which is the shared content, is scrolled. A coin tipping room W4 may be generated in which the display form is changed so as to be fixedly displayed on the screen. FIG. 3 is a diagram showing a display example (part 2) of the tipping room according to the embodiment. In FIG. 3, the left figure shows a display example of the tipping room W4 before scrolling, and the right figure shows a display example of the tipping room W4 after scrolling. FIG. 3 shows an example in which the first object OB1-5 indicating the remittance amount of "10,000 yen" is fixedly displayed in the upper area of FIG. 3 on the display screen of the tipping room W4. ing. Further, according to FIG. 3, by scrolling the display screen displaying the tipping room W4, the first object OB1-6 indicating the remittance amount "500 yen" is hidden in the display screen of the tipping room W4, and the remittance amount " An example is shown in which a first object OB1-8 indicating "300 yen" newly appears.

The service user UZ can make a tip to the creator "USER XXX2" directly from the tip room W4 by operating the support button OB3 provided in the tip room W4. An example of a coin tipping operation and screen transitions according to the embodiment will be briefly described below.

The user application running on the terminal device 10-1 displays a remittance amount input screen W5 on the terminal device 10-1 when the support button OB3 is operated. The remittance amount input screen W5 is provided with a plurality of keys for inputting the amount, and a "Next" button for confirming the input of the remittance amount and proceeding to the next process. For example, the "next" button may transition to a valid state in conjunction with entering an amount. Then, when there is an operation on the "next" button provided on the remittance amount input screen W5, the user application causes the terminal device 10-1 to display the tipping screen W6.

The tipping send screen W6 shown in FIG. 1 is provided with a message creation button OB4, theme icons OB5-1, OB5-2, and OB5-3, a tipping request button OB6, and the like. The message creation button OB4 is used when requesting a message to accompany a coin tip. The theme icon OB5 is used to allow the service user to select information indicating the purpose of remittance. For example, the theme icon OB5-1 is an icon selected by the service user UZ when the purpose of the remittance is tipping, and the theme icon OB5-2 is selected by the service user when the purpose of the remittance is to split the bill. The theme icon OB5-3 is an icon selected by UZ, and the theme icon OB5-3 is an icon selected by the service user UZ when the purpose of the remittance is a gift. A tip request button OB6 is used to request the settlement server 100 to process a tip.

The user application running on the terminal device 10-1 displays the message creation screen W7 on the terminal device 10-1 when the message creation button OB4 is operated. The message creation screen W7 is provided with a message input box BX1 for inputting a message from the service user who is the remittance source, a message addition button OB7, and the like. In the message input box BX1 of the message creation screen W7 shown in FIG. 1, it is shown that the message "use it carefully" is input. Further, when the message addition button OB7 is operated, the user application re-displays the tip transmission screen W6 displaying the message whose input has been confirmed on the terminal device 10-1. After selecting the theme icon OB5-1, the user application transmits a tipping request to the settlement server 100 when the tipping request button OB6 is operated. The tip request includes the creator ID designated as the remittance destination, the remittance amount, the user ID of the service user UZ who is the remittance source, and information indicating the theme icon OB5-1.

When settlement server 100 receives a tipping request from a user application running on terminal device 10-1, it automatically processes a remittance instruction transaction corresponding to the received tipping request. Specifically, the settlement server 100 transfers from the account of the service user UZ (wallet linked to the user account) to the account (wallet linked to the user account) of the service user "USER XXX2" who is the remittee. , transfer the amount of electronic money indicated by the remittance amount.

Settlement server 100 may process a remittance instruction transaction corresponding to a tip request received from terminal device 10-1 on condition that a theme is set in the tip request. As a result, the settlement server 100 can efficiently manage information on remittances made by the service user UZ for the purpose of requesting tipping.

Further, when the processing of the remittance instruction transaction corresponding to the tip request from the service user UZ is completed, the settlement server 100 reflects the processing result of the remittance instruction transaction in the tip room W4. FIG. 4 is a diagram showing an example of the tipping room after reflecting the processing result of the remittance instruction transaction corresponding to the tipping request according to the embodiment. In the tipping room W4 shown in FIG. 4, the first object OB1-4 and the second object OB2-4 are reflected as the remittance history corresponding to the tipping request by the service user UZ.

Further, when the processing of the remittance instruction transaction corresponding to the tip request from the service user UZ is completed, the settlement server 100 reflects the information based on the processing result of the remittance instruction transaction on the remittance destination selection screen W2. FIG. 5 is a diagram showing an example of the remittance destination selection screen after reflecting the processing result of the remittance instruction transaction corresponding to the tip request according to the embodiment. In the remittance destination selection screen W2 shown in FIG. 5, the information of "USER XXX2" designated as the remittance destination by the service user UZ is reflected in the creator tab.

(1-3-2. Creator registration process)
Next, creator registration processing according to the embodiment will be described with reference to FIG. FIG. 6 is a diagram showing an overview of creator registration processing according to the embodiment. Hereinafter, the flow of creator registration processing by the service user UX will be described in detail, with screen transitions of user applications displayed on the terminal device 10 . Note that the terminal device 10-2 shown in FIG. 6 is an example of an information processing terminal used by the service user UX.

As shown in FIG. 6, the service user UX displays a menu M on the remittance destination selection screen W2, and operates a creator registration button OB11 provided on the menu M. FIG. As a result, when the service user UX operates the creator registration button OB11, the user application running on the terminal device 10-2 displays the top screen W11 for creator registration on the terminal device 10-2.

A top screen W11 for registering a creator displayed on the terminal device 10 is provided with a button OB12 for proceeding with the registration process. The user application running on the terminal device 10-2 displays an account information setting screen W12 on the terminal device 10-2 when the service user UX operates the button OB12. The setting screen W12 is provided with an area for displaying the setting status of a plurality of setting items such as a display name, a creator ID, personal identification and account authentication, and a save button OB13 for saving account information. In the example shown in FIG. 6, the setting screen W12 shows a state in which all information is unset except for the default icon indicating the service user UX. As the default icon indicating the service user UX, the icon used in the electronic payment service may be used as it is.

When the service user UX operates the creator ID area, the user application running on the terminal device 10-2 displays a creator ID setting screen W13 on the terminal device 10-2. The setting screen W13 is provided with a creator ID input area, a creator ID setting button OB14, and the like. In the example shown in FIG. 6, the setting screen W13 shows that "CRE_XXX" is input as the creator ID. For example, the user application transmits the information of the character string entered as the creator ID on the setting screen W13 to the payment server 100 in real time, and sequentially obtains from the payment server 100 the determination result as to whether or not the character string is valid. , are reflected in the setting screen W13. The setting button OB14 may transition to a valid state, for example, when an appropriate character string is entered as the creator ID. Note that the creator ID is not limited to an arbitrary character string set by the service user, and may be a two-dimensional code uniquely issued by the settlement server 100 to the service user.

Although not shown in FIG. 6, when the service user UX operates the setting button OB14, the user application redisplays the account information setting screen W12 on the terminal device 10-2, Update status. Then, in the setting screen 12, the user application causes the terminal device 10-2 to display the corresponding setting screen according to the operation for the setting item of the account information that has not been set by the service user UX.

When the service user UX operates the save button OB13 provided on the setting screen W12, the user application running on the terminal device 10-2 stores the user ID of the service user UX together with the service user application. The account information set by the UX is transmitted to the settlement server 100 (step S11). When the account information is received from the user application running on the terminal device 10-2, the settlement server 100 executes a registration process of registering the account information in association with the user ID received together with the account information (step S12). When the registration process is completed, the settlement server 100 provides the user application with a registration completion screen W14 (step S13). The user application displays the registration completion screen W14 received from the settlement server 100 on the terminal device 10-2. For example, the registration completion screen W14 shown in FIG. 6 is provided with a button OB15 for displaying a tutorial about the creator ID.

In this way, the payment server 100 provides a service that enables the service user to provide a gift through the electronic payment service platform that the service user UZ is using. As a result, the payment server 100 allows the service user UZ who wants to support the creator to use the platform of the electronic payment service used by the service user without registering on the same platform as the creator or registering the payment method. By using it, it is possible to easily give money to the creator, and the usability of the service user UZ can be improved. On the other hand, the settlement server 100 can assist service users in procuring funds through creator registration, and can improve usability for service users who wish to be active as creators. More specifically, among service users who wish to be active as creators, there are some who distribute performances of playing musical instruments online. It is difficult for such a creator to confirm from which user the coin was tipped by operating the terminal device 10-1 during the demonstration. If it is possible to display like the tipping room W4, which is the shared content, there is an effect that the occurrence of tipping can be viewed at a glance even when the creator is performing.

In addition, the settlement server 100 may provide information on tipping rooms in response to a request from a service user UX who has registered as a creator. FIG. 7 is a diagram showing an example of providing information in a tipping room according to the embodiment.

As shown in FIG. 7, the user application running on the terminal device 10-2 transmits a tipping room information acquisition request to the settlement server 100 in response to a request from the service user UX (step S21). The settlement server 100 provides the user application with a tipping room management screen W21 corresponding to the service user UX in response to a request from the user application (step S22). As shown in FIG. 7, on the tipping room management screen W21, tipping room information is managed in a threaded state (aggregated in units of a series of flows (for example, units of content) in exchanging tips). ing. Threading of the tipping room may be performed automatically based on the processing status of the tipping request with the service user UX as the remittance destination by the payment server 100, or the topic for the tipping room may be sent from the service user UX. (including the start time and end time of acceptance of tipping), and threading may be executed based on the accepted settings. In addition, the settlement server 100 may provide the service user with a tipping room for a limited time period set in advance.

[2. Configuration of payment server]
Next, the configuration of the settlement server 100 will be described using FIG. FIG. 8 is a diagram showing a configuration example of a settlement server according to the embodiment. As shown in FIG. 8, the settlement server 100 has a communication section 110, a storage section 120, and a control section .

(Regarding communication unit 110)
Communication unit 110 is realized by, for example, a NIC (Network Interface Card) or the like. The communication unit 110 is connected to the network N by wire or wirelessly, and transmits and receives information to and from the terminal device 10 and the like.

(Regarding storage unit 120)
The storage unit 120 is realized by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 8 , storage unit 120 has user information database 121 , wallet information database 122 , and remittance history database 123 . Note that the storage unit 120 is not limited to the example shown in FIG. 8, and may store one database in which the user information database 121 and the wallet information database 122 are integrated. A database for storing may be stored.

(Regarding the user information database 121)
The user information database 121 stores information about service users. FIG. 9 is a diagram illustrating an example of a user information database according to the embodiment; As shown in FIG. 9, the user information database 121 includes a "user ID" item, a "creator ID" item, a "display name" item, an "icon" item, and an "identity verification information" item. items, and items such as “Wallet ID”, and these items are associated with each other.

The "user ID" item stores a user ID for identifying a service user who uses the electronic payment service. User IDs are individually assigned, for example, when registering for use of an electronic payment service.

The "creator ID" item stores a creator ID that is individually assigned to a service user who has registered as a creator in association with the user ID.

The “display name” item stores information indicating the display name displayed in the remittance destination information when the creator ID is used to receive a tip.

The “display name” item stores information indicating an icon displayed in the remittance destination information when the creator ID is used to receive a tip.

In the item of "identity verification information", the identity verification information provided by the service user when the creator is registered is stored.

The “wallet ID” item stores a wallet ID for identifying a wallet assigned to a service user in an electronic payment service.

According to FIG. 9, the creator ID: "CRE_XXX" is associated with the service user identified by the user ID: "U#001". Also, according to FIG. 9, the display name is "USER XXX2", the icon is "icon EX-1", and the creator is registered when receiving a coin tip using creator ID: "CRE_XXX". It is shown that the personal identification information at the time of the confirmation is "principal EX-1" and the corresponding wallet ID is "wallet #001".

(Regarding wallet information database 122)
The wallet information database 122 stores information about wallets corresponding to service users. FIG. 10 is a diagram showing an example of wallet information stored in the wallet information database according to the embodiment. As shown in FIG. 10, the wallet information database 121 has items of "wallet ID" and items of "money balance", and these items are associated with each other.

The “wallet ID” item stores a wallet ID for identifying a wallet assigned to a service user in an electronic payment service. The information stored in the “wallet ID” item of the wallet information database 122 corresponds to the information stored in the “wallet ID” item of the user information database 121 . Information indicating the balance of electronic money recorded in the wallet is stored in the "money balance" item.

FIG. 10 shows that the money balance recorded in the wallet identified by wallet ID: "wallet #001" is "money balance EX-1".

(Regarding remittance history database 123)
The remittance history database 123 stores the remittance history of each service user of a remittance service that enables exchange of digital money between individuals. For example, the remittance history database 123 stores information about remittance history performed using the remittance service in association with user IDs, which are user identification information for identifying service users. FIG. 11 is a diagram illustrating an example of information stored in a remittance history database according to the embodiment;

As shown in FIG. 11 , the remittance history database 123 has a “user ID” item, a “remittee ID” item, a “remittance date and time” item, and a “remittance amount” item for each service user. , a “remittance theme” item, and a “message” item. These items in the remittance history database 123 are associated with each other.

The "user ID" item stores a user ID for identifying a service user who uses the electronic payment service. The information stored in the “user ID” item of the remittance history database 123 corresponds to the information stored in the “user ID” item of the user information database 121 .

A remittance destination ID for identifying a remittance destination designated as a remittance destination is stored in the item of “remittance destination ID”. For example, in the "remittance destination ID" item, the user ID is stored in the case of a normal remittance other than a tip, and the creator ID is stored in the case of a tip. When a creator ID is stored in the item of "remittance destination ID", the remittance history can be divided into threads based on the remittance received by the creator ID. Note that each thread created by a creator may be divided into threads based on the remittance received by the creator ID.

The item "remittance date and time" stores information indicating the date and time when the remittance was performed. Information indicating the remittance amount is stored in the "remittance amount" item. The "remittance theme" item stores information corresponding to theme icons (for example, see FIG. 1) selected by the service user when performing remittance or tipping. The "message" item stores information indicating a message created by the service user when making a remittance or a tip.

According to FIG. 11, as part of the remittance history of the service user identified by the user ID: "U#001", for the service user identified by the remittee ID: "CRE_XXX", in April 2022 It is recorded that at 16:15 on the 1st, a 100-yen tip was given along with the message, "Please use it carefully."

(Regarding the control unit 130)
The control unit 130 is a controller, and various programs stored in a storage device inside the payment server 100 are executed by a CPU (Central Processing Unit) or MPU (Micro Processing Unit), for example, using the RAM as a work area. It is realized by being executed. Also, the control unit 130 can be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The control unit 130 according to the embodiment has a registration unit 131, a determination unit 132, a generation unit 133, a provision unit 134, and a remittance processing unit 135, as shown in FIG. It implements or executes the information processing functions and actions described below.

(Regarding registration unit 131)
In response to a request from a service user (creator registration request), the registration unit 131 registers an identification for collection individually assigned to the service user in association with the user ID, which is user identification information for the electronic payment service. A creator ID, which is information, is registered.

(Regarding the determination unit 132)
The determination unit 132 determines whether or not the remittance destination identification information specified as the remittance destination by the service user is a creator ID (hereinafter referred to as “creator ID”), which is collection identification information. If the remittee identification information is the creator ID, the determination unit 132 passes a determination result indicating that fact to the generation unit 132 . On the other hand, if the remittee identification information is not the creator ID, the determination unit 133 sends a processing request to the remittance processing unit 133 .

(Regarding the generation unit 133)
When receiving from the determination unit 132 the determination result that the remittance destination identification information is the creator ID, the generation unit 133 acquires the remittance history linked to the creator ID from the remittance history, and based on the acquired remittance history , generates a tipping room (for example, see FIGS. 1 to 4), which is shared content shared by each service user who made a remittance with the creator ID as the remittance destination.

The generating unit 132 can generate a tipping room, which is shared content that displays first objects indicating remittance amounts by service users in order of remittances. In addition, the generation unit 132 can generate a tipping room, which is shared content in which the display form of the first object is changed according to the remittance amount. In addition, the generation unit 132 can generate a coin tipping room, which is shared content in which a second object indicating a message created by each service user at the time of remittance is displayed in association with the first object. Further, when receiving a message for shared content from a service user who is a remittance destination, the generating unit 132 can generate a tipping room, which is shared content displaying a third object indicating the message. In addition, the generating unit 132 can generate a tipping room, which is shared content threaded in a predetermined unit.

In addition, when the remittance amount satisfies a predetermined condition, the generation unit 133 changes the display form so that the first object is larger than the first object generated when the remittance amount is less than the predetermined amount. You can generate a tipping room, which is shared content. In addition, when the remittance amount is equal to or greater than the predetermined amount, the generation unit 133 changes the display mode so that the first object is displayed fixedly on the display screen even if the display screen on which the coin tipping room, which is the shared content, is displayed is scrolled. You can also generate tipping rooms that are modified shared content.

(Regarding the providing unit 134)
The providing unit 134 refers to the determination result received from the determining unit 133, and if the remittee identification information specified as the remittee by the service user is the creator ID, the service user who specified the remittance destination Offer a te-nage room. In addition, the providing unit 134 can provide a tipping room, which is shared content, for a limited time period set in advance. For example, the period during which the tipping room is provided can be determined based on the setting by the service user who is the remittance destination corresponding to the tipping room.

In addition, in response to a request from the service user, the providing unit 134 acquires a remittance history with the collection identification information linked to the service user as the remittance destination, and threads the acquired remittance history in a predetermined unit. Provided to service users.

(Regarding the remittance processing unit 135)
When the remittance processing unit 135 receives a remittance request to a creator ID as a remittance destination from a service user through the tipping room, which is shared content provided by the provision unit 134, the remittance processing unit 135 processes a remittance instruction transaction corresponding to the remittance request. . In addition, when the remittance request is for a creator ID as the remittee, the remittance processing unit 135 can automatically process the remittance instruction transaction corresponding to the remittance request without requesting the remittance destination user to perform a receiving operation. This eliminates the need for the service user of the remittance destination to perform a receiving operation each time a coin is tipped, thereby improving usability for the service user of the remittance destination. Also, the remittance processing unit 135 may process a remittance instruction transaction on condition that a corresponding theme is set for a remittance request to a creator ID as a remittance destination.

[3. Processing procedure example]
An example of the processing procedure in the settlement server 100 according to the embodiment will be described below. FIG. 12 is a flowchart illustrating an example of an information processing procedure executed by the settlement server according to the embodiment;

As shown in FIG. 12, the determination unit 132 determines whether or not the remittee identification information specified by the service user is the creator ID (step S101).

If the determination unit 132 determines that the remittance destination identification information is the creator ID (step S101: Yes), the generation unit 133 acquires the remittance history with the creator ID as the remittance destination from the remittance history database 123. Then, based on the acquired remittance history, a coin tipping room is generated (step S102).

Further, the providing unit 134 provides the tipping room generated by the generating unit 133 to the remittance source service user (hereinafter referred to as the "remitter user") who specified the remittance identification information (step S103).

The providing unit 134 also determines whether or not a message has been input by the remitter user (step S104). If the providing unit 134 determines that a message has been input by the remitter user (step S104: Yes), the providing unit 134 associates the information of the message input by the remitter user with the remitter user (step S105).

In addition, the remittance processing unit 135 processes a remittance instruction transaction corresponding to the remittance request from the remittance source user (step S106).

Further, after completing the processing of the remittance instruction transaction, the remittance processing unit 135 updates the remittance history (step S107), and ends the processing procedure shown in FIG. For example, the remittance processing unit 135 associates the user ID of the remittance source user, the remittee identification information, the remittance amount, and the message information in step S105, and records them in the remittance history database 123 .

In step S104 described above, when the providing unit 134 determines that no message has been input from the remittance source user (step S104: No), the procedure proceeds to step S106 described above.

Further, in step S101 described above, when the determination unit 132 determines that the remittee identification information is not the creator ID (step S101: No), the generation unit 133 proceeds to the processing procedure of step S106 described above. That is, the remittance processing unit 135 processes a normal remittance instruction transaction other than a tip in response to a remittance request from a remitter user.

[4. Modification]
(4-1. Restriction on remittance amount)
In the above-described embodiment, the settlement server 100 may limit the amount of tips that can be accepted from the service user of the remittance source. For example, the limit on the amount of tipping money may be a limit per predetermined time set in advance, or a limit for a predetermined period set in advance.

(4-2.Regarding restrictions on the area of the remittance source)
Further, in the above-described embodiment, the settlement server 100 may set restrictions on areas where tipping is accepted based on the location information of the service user of the remittance source. For example, settlement server 100 may determine whether or not tipping can be accepted based on the IP (Internet Protocol) address of the service user of the remittance source.

(4-3. Remittance Destination)
In the above-described embodiment, the settlement server 100 performs information processing in a remittance service in which electronic money can be exchanged between individuals. , the information processing according to the embodiment can be applied.

(4-4. Coordination with platforms for content distribution)
In the above-described embodiment, the payment server 100 accepts pre-registration of the platform used for content distribution from service users who have registered as creators, and only while content is being distributed. The remittance process may be controlled so that tips from service users are accepted.

Further, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can also be performed manually. All or part of the processing can also be performed automatically by known methods. In addition, information including processing procedures, specific names, various data and parameters shown in the above documents and drawings can be arbitrarily changed unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

Also, each component of each device illustrated is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution and integration of each device is not limited to the one shown in the figure, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions. Can be integrated and configured. For example, the determination unit 132, generation unit 133, and provision unit 134 included in the control unit 130 of the payment server 100 may be functionally integrated.

Moreover, each of the embodiments described above can be appropriately combined within a range that does not contradict the processing contents.

[5. effect〕
As described above, the settlement server 100 according to the embodiment has the registration unit 131 and the remittance processing unit 135. In response to a request from a service user of an electronic payment service capable of exchanging digital money between individuals, the registration unit 131 associates the service user with the user identification information for identifying the service user. Register the collection identification information assigned individually to each. When the remittance processing unit 135 receives a remittance request with the collection identification information as the remittance destination, the remittance processing unit 135 performs the remittance corresponding to the remittance request without requesting the service user of the remittance destination to perform a receiving operation in response to the remittance request. Automatically process directed transactions.

In addition, the remittance processing unit 135 processes a remittance instruction transaction on the condition that a corresponding theme is set for a remittance request to which the collection identification information is the remittance destination.

In addition, the payment server 100 according to the embodiment provides, in response to a request from a service user, a remittance history in which the remittance destination is the collection identification information linked to the service user, threaded in a predetermined unit, and provided. 134 further.

In this way, the settlement server 100 according to the embodiment, through the processing executed by the respective units described above, or any combination of the respective units, allows the service user to receive a predetermined gift provided online. Usability can be improved. That is, since the settlement server 100 automatically processes a tipping request with the creator ID as the remittance destination, the service user who has registered as a creator does not need to perform a receiving operation every time a remittance request is made to himself/herself. , Usability can be improved for service users who wish to be active as creators.

[6. Hardware configuration]
Also, the settlement server 100 according to the present embodiment described above is implemented by, for example, a computer 1000 configured as shown in FIG. FIG. 11 is a hardware configuration diagram showing an example of a computer that implements the functions of the payment server according to the embodiment.

A computer 1000 is connected to an output device 1010 and an input device 1020, and an arithmetic device 1030, a primary storage device 1040, a secondary storage device 1050, an output IF (Interface) 1060, an input IF 1070, and a network IF 1080 are connected via a bus 1090. have

Arithmetic device 1030 operates based on programs stored in primary storage device 1040 and secondary storage device 1050, programs read from input device 1020, and the like, and executes various types of processing. The primary storage device 1040 is a memory device such as a RAM that temporarily stores data used by the arithmetic device 1030 for various calculations. The secondary storage device 1050 is a storage device in which data used for various calculations by the arithmetic device 1030 and various databases are registered, and is implemented by a ROM (Read Only Memory), HDD, flash memory, or the like.

The output IF 1060 is an interface for transmitting information to be output to the output device 1010 that outputs various types of information such as a monitor and a printer. It is realized by a connector conforming to a standard such as HDMI (registered trademark) (High Definition Multimedia Interface). Also, the input IF 1070 is an interface for receiving information from various input devices 1020 such as a mouse, keyboard, scanner, etc., and is implemented by, for example, USB.

Note that the input device 1020 includes, for example, optical recording media such as CDs (Compact Discs), DVDs (Digital Versatile Discs), PDs (Phase change rewritable discs), magneto-optical recording media such as MOs (Magneto-Optical discs), and tapes. It may be a device that reads information from a medium, a magnetic recording medium, or a semiconductor memory. Also, the input device 1020 may be an external storage medium such as a USB memory.

Network IF 1080 receives data from other devices via network N and sends the data to arithmetic device 1030, and also transmits data generated by arithmetic device 1030 via network N to other devices.

The arithmetic device 1030 controls the output device 1010 and the input device 1020 via the output IF 1060 and the input IF 1070 . For example, arithmetic device 1030 loads a program from input device 1020 or secondary storage device 1050 onto primary storage device 1040 and executes the loaded program.

For example, when the computer 1000 functions as the payment server 100, which is an example of the information processing apparatus according to the present embodiment, the computing device 1030 of the computer 1000 stores a program (for example, an information processing program) loaded on the primary storage device 1040. A function similar to that of the control unit 130 is realized by executing That is, the computing device 1030 realizes processing by the payment server 100 according to this embodiment in cooperation with a program (for example, an information processing program) loaded on the primary storage device 1040 .

[7. others〕
As described above, some of the embodiments of the present application have been described in detail based on the drawings. It is possible to carry out the invention in other forms with modifications.

In addition, the configuration of the settlement server 100 described above can be flexibly changed, for example, by calling an external platform or the like using an API (Application Programming Interface) or network computing depending on the function.

In addition, the "unit" described in the claims can be read as "means", "circuit", or the like. For example, the controller can be read as control means or a control circuit.

10 terminal device 100 settlement server 110 communication unit 120 storage unit 121 user information database 122 wallet information database 123 remittance history database 130 control unit 131 registration unit 132 determination unit 133 generation unit 134 provision unit 135 remittance processing unit

Claims (6)

User identification information for identifying the service user in response to the user's registration for use of the remittance service provided through the same platform as the electronic payment service that allows the exchange of digital money between individuals; , in association with the wallet identification information for identifying the wallet assigned to the service user, separately from the user identification information and the wallet identification information , the service user acting as a creator a registration unit for registering collection identification information individually assigned to the service user, which is identification information for receiving a tip from the service user by remittance of the digital money;
When a remittance request to which the remittance destination is the collection identification information is received, a remittance instruction transaction corresponding to the remittance request without requesting the service user of the remittance destination to perform a receiving operation in response to the remittance request. a remittance processing unit that automatically processes
and a remittance history database that stores a remittance history with the user identification information or the collection identification information as a remittee in association with the user identification information. The remittance processing unit
processing the remittance instruction transaction on the condition that tipping is set as a corresponding theme in response to a remittance request to which the collection identification information is the remittance destination;
In the remittance history database,
When the theme is other than the tip, the remittance history with the user identification information as the remittee is stored, and when the theme is the tip, the remittance history with the collection identification information as the remittee is stored. The information processing apparatus according to claim 1, wherein the information is stored. Acquiring from the remittance history database, in response to a request from the service user, the remittance history with the identification information for money collection as the remittee among the remittance histories linked to the service user, and the acquired remittance 2. The information processing apparatus according to claim 1, further comprising a providing unit that automatically threads and provides the history in a predetermined unit based on the processing status of the remittance instruction transaction. The providing unit
4. The information processing apparatus according to claim 3, wherein the remittance history is threaded based on the setting of the acceptance time and end time of the tip accepted from the service user. A computer-executed information processing method comprising:
User identification information for identifying the service user in response to the user's registration for use of the remittance service provided through the same platform as the electronic payment service that allows the exchange of digital money between individuals; , in association with the wallet identification information for identifying the wallet assigned to the service user, separately from the user identification information and the wallet identification information , the service user acting as a creator a registration step of registering collection identification information individually assigned to the service user, which is identification information for receiving a tip from the service user by remittance of the digital money;
When a remittance request to the remittance destination of the identification information for collection is accepted, the remittance instruction transaction corresponding to the remittance request is performed without requesting the service user of the remittance destination to receive the remittance request in response to the remittance request. an automatically processed remittance process; and
An information processing method, wherein a remittance history with the user identification information or the collection identification information as a remittee is stored in a remittance history database in association with the user identification information. to the computer,
User identification information for identifying the service user in response to the user's registration for use of the remittance service provided through the same platform as the electronic payment service that allows the exchange of digital money between individuals; , in association with the wallet identification information for identifying the wallet assigned to the service user, separately from the user identification information and the wallet identification information , the service user acting as a creator a registration procedure for registering collection identification information individually assigned to the service user, which is identification information for receiving a tip from the service user by remittance of the digital money;
When a remittance request to the remittance destination of the identification information for collection is accepted, the remittance instruction transaction corresponding to the remittance request is performed without requesting the service user of the remittance destination to receive the remittance request in response to the remittance request. Execute the automatic remittance processing procedure and
An information processing program characterized by storing, in a remittance history database, a remittance history with the user identification information or the collection identification information as a remittee in association with the user identification information.

Images