JP7121169B1 - Provision device, provision method and provision program - Google Patents

Abstract

A provision device, a provision method, and a provision program are provided that allow a user to specifically grasp the purpose of payment. SOLUTION: In a provision system, a payment server 10 includes a reception unit 41 for receiving payment information related to payment made by a user using a predetermined payment method, and a payment purpose (for example, payment by payment) corresponding to the payment information. purpose of payment estimated based on payment information, including destination, transaction target, date and time of payment, location of user at the time of payment, etc.) It has a provision unit 44 for providing information, and a provision unit 45 for providing payment information provided with purpose information to the user. [Selection drawing] Fig. 3

Description

The present invention relates to a provision device, a provision method, and a provision program.

2. Description of the Related Art Conventionally, techniques for managing the history of various payments made by users are known. As an example of such technology, a technology has been proposed that loads the transaction history of a bank account and displays the transaction details for each transaction in the transaction history on a message-by-message basis in a chat room generated for the bank account. there is

JP 2020-109643 A

However, with the conventional technology described above, it is not always possible for the user to specifically grasp the purpose of payment.

For example, in the above conventional technology, the chat room only displays the balance information of the bank account and the deposit/withdrawal history of the bank account, which allows the user to specifically grasp the purpose of the payment. Not necessarily.

The present application has been made in view of the above, and aims to provide a provision device, a provision method, and a provision program that allow the user to specifically grasp the purpose of payment.

The provision device according to the present application includes a reception unit that receives payment information related to payment made by a user using a predetermined payment method, and purpose information that indicates the purpose of the payment corresponding to the payment information received by the reception unit. The present invention is characterized by comprising an adding unit that adds the purpose information to the payment information, and a providing unit that provides the user with the payment information to which the purpose information is added by the adding unit.

According to one aspect of the embodiment, there is an effect that the user can specifically grasp the purpose of payment.

FIG. 1 is a diagram illustrating an example of provision processing according to the embodiment. FIG. 2 is a diagram illustrating an example of a screen of the terminal device according to the embodiment; FIG. 3 is a diagram showing a configuration example of a payment server according to the embodiment. FIG. 4 is a diagram showing an example of an account database according to the embodiment. FIG. 5 is a diagram illustrating an example of a user information database according to the embodiment; FIG. 6 is a flowchart illustrating an example of the procedure of provision processing according to the embodiment. FIG. 7 is a hardware configuration diagram showing an example of a computer that implements the functions of the settlement server.

Embodiments for implementing the provision device, the provision method, and the provision program (hereinafter referred to as "embodiments") according to the present application will be described in detail below with reference to the drawings. Note that the provision device, the provision method, and the provision program according to the present application are not limited by 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]
The providing process realized by the providing apparatus and the like of this embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating an example of provision processing according to the embodiment. Note that in FIG. 1, the provision processing and the like according to the embodiment are realized by the settlement server 10, which is an example of the provision device according to the present embodiment.

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

A settlement server 10 shown in FIG. 1 is an information processing device that executes provision processing according to the embodiment, and is realized by a server device, a cloud system, or the like. For example, the payment server 10 provides an electronic payment service related to electronic payment using the terminal device 100 . For example, the settlement server 10 manages the account of the provider of the transaction object and the account of the user to whom the transaction object is provided. Realize various settlements. In addition, electronic money may be, for example, points or currency used independently by various companies, or may be electronically tradable currency provided by the state such as Japanese yen and dollars. good.

A terminal device 100 shown in FIG. 1 is an information processing device used by a user. The terminal device 100 is realized 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 100 displays information delivered by the payment server 10 using a web browser or an application.

Note that the example shown in FIG. 1 shows a case where the terminal device 100 is a smart phone. Also, in the example shown in FIG. 1, the terminal device 100 will be described as terminal devices 100-1 to 100-N (N is an arbitrary natural number) according to the user who uses the terminal device 100. FIG. For example, the terminal device 100-1 is the terminal device 100 used by the user (user U1) identified by the user ID "U1". Further, hereinafter, the terminal devices 100-1 to 100-N will be referred to as the terminal device 100 when they are described without distinction.

Further, when the terminal device 100 receives control information for implementing predetermined information processing from the settlement server 10, the terminal device 100 implements the information processing according to the control information. Here, the control information is described in, for example, a script language such as JavaScript (registered trademark) or a style sheet language such as CSS (Cascading Style Sheets). Note that the predetermined application itself distributed from the settlement server 10 may be regarded as the control information.

[1-1. Settlement using the terminal device 100]
Here, an example of payment (electronic payment) using the terminal device 100 will be described prior to the providing process executed by the payment server 10. FIG. In the following description, an application distributed from the payment server 10 and used for electronic payment using the terminal device 100 (hereinafter sometimes simply referred to as a “payment application”) is installed on the terminal device 100. It shall be Further, in the following description, the user U1 uses the terminal device 100 using a two-dimensional code (QR code (registered trademark)) placed in the store and indicating store identification information for identifying the store. An example of settlement using -1 will be described, but the embodiment is not limited to this. An example of settlement described below is also applicable when any user uses any terminal device 100 to make a payment at any store. Moreover, the store identification information may be not only a QR code but also a bar code, a predetermined mark, a number, or the like.

For example, when the user U1 makes a payment accompanying the use or purchase of a payment target (transaction target) such as various products and services at a store, the user U1 installs a payment application in advance on the terminal device 100-1. to start. Then, the user U1 photographs the store identification information installed in the store via the payment application. In such a case, the terminal device 100-1 displays a screen for inputting the price to be settled, and accepts the input of the payment amount from the user U1 or the store clerk. Then, the terminal device 100-1 stores user identification information for identifying the user U1, shop identification information (or information indicated by the shop identification information, that is, information indicating the shop (for example, shop ID)), and payment payment information indicating the amount of money to be sent to the payment server 10;

In such a case, the settlement server 10 transfers the amount of electronic money indicated by the settlement amount from the account of user U1 indicated by the user identification information to the account of the store indicated by the store identification information. The settlement server 10 then transmits a notification that the settlement has been completed to the terminal device 100-1. In such a case, the terminal device 100-1 notifies that the payment has been made with electronic money by outputting a screen or a predetermined sound indicating that the payment has been completed.

Note that the settlement using the terminal device 100 is not limited to the processing described above. For example, settlement using the terminal device 100 may be made using a store terminal installed in a store. As a specific example, the terminal device 100-1 displays user identification information for identifying user U1 on the screen. In such a case, the store terminal installed in the store reads the user identification information displayed on the terminal device 100-1, and reads the user identification information (or information indicated by the user identification information, that is, user U1). (for example, a user ID)), the payment amount, and the information identifying the store are transmitted to the payment server 10 . In such a case, the settlement server 10 transfers the amount of electronic money indicated by the settlement amount from the account of the user U1 indicated by the user identification information to the account of the store, and the store terminal or terminal device 100- 1 may be notified that the payment has been made by outputting a screen or a predetermined voice indicating that the payment has been completed.

In addition, settlement using the terminal device 100 includes not only the process of transferring electronic money from the account charged with electronic money by the user U1 in advance to the account of the store, but also, for example, the credit card pre-registered by the user U1. Payment may be made using In such a case, for example, the terminal device 100 may transfer the electronic money of the settlement amount to the account of the store, and may request the settlement amount from the operating company of user U1's credit card.

In addition, the settlement using the terminal device 100-1 is not only the process of transferring electronic money from the account of user U1 to the account of the store, but also the transfer of electronic money from the account of user U1 to the account of another user, for example. It may be a payment for transferring electronic money (that is, remittance between users). For example, the terminal device 100-1 used by the remittance source user U1 receives user identification information (for example, user identification information displayed on the terminal device used by the remittee user) that identifies the remittance destination user. information), receives input of the remittance amount from the user U1, and transmits to the settlement server 10 information indicating the read identification information, remittance amount, and user identification information for identifying the user U1. In such a case, the settlement server 10 transfers the amount of electronic money indicated by the remittance amount from the account of the user U1 to the account of the remittee user, and transfers it to the terminal device 100-1 or the remittee user. You may notify that the remittance has been performed by outputting a screen or a predetermined voice indicating that the remittance has been completed to the terminal device used by .

The remittance using the terminal device 100 is not limited to the processing described above. For example, remittance using the terminal device 100 may be performed by inputting into the terminal device 100 the telephone number of the user to whom the remittance is to be made, or information indicating the user to whom the remittance is to be made (for example, user ID). . As a specific example, the terminal device 100-1 accepts input of the telephone number or user ID of the user to whom the remittance is to be made and the remittance amount from the user U1, and receives the input telephone number or user ID. , and the remittance amount and user identification information for identifying user U1 are transmitted to the settlement server 10 . Then, the settlement server 10 transfers the amount of electronic money indicated by the remittance amount from the account of the user U1 to the account of the user linked to the transmitted telephone number or user ID.

Here, the telephone number and user ID of the user to whom the remittance is to be made may be associated with information about the user and registered in advance in the payment application. In this case, the terminal device 100-1 accepts from the user U1 the designation of a user (remittance destination) registered in the payment application and the input of the remittance amount to the user, and the terminal device 100-1 is linked to the designated user. The attached telephone number or user ID, remittance amount, and user identification information for identifying user U1 are transmitted to the settlement server 10 .

Further, for example, remittance using the terminal device 100 may be performed by providing the remittee user with link information for receiving the remittance amount. As a specific example, the terminal device 100-1 accepts an input of the remittance amount from the user U1, 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. Link information is provided to the terminal device used by the user of the remittance destination by posting posted information including information to SNS (Social Networking Service). Then, when the remittance destination user selects the link information and performs a receiving operation, the settlement server 10 transfers the amount indicated by the remittance amount from the user U1 account to the remittance destination user account. transfer money.

[1-2. Overview of Embodiment]
Here, conventionally, as a technology for managing the history of various payments made by users, the transaction history of the bank account is loaded, and in the chat room generated for the bank account, each transaction in the transaction history A technology has been proposed for displaying transaction details in units of messages. However, such technology only displays the bank account balance information and the deposit/withdrawal history of the bank account in the chat room, and it is not possible for the user to specifically grasp the purpose of the payment. Not exclusively.

Therefore, the settlement server 10 executes provision processing according to the embodiment. The provision processing executed by the settlement server 10 will be described below with reference to FIG. In the following description, the terminal device 100-1 may be identified with the user U1, and the terminal device 100-6 may be identified with the user U6. That is, hereinafter, the user U1 can be read as the terminal device 100-1, and the user U6 can be read as the terminal device 100-6.

First, the terminal device 100-1 activates a payment application installed in the terminal device 100-1 according to an operation from the user U1, and displays a screen for inputting remittance information regarding remittance (step S1). Subsequently, user U1 inputs remittance information on the screen displayed on terminal device 100-1 (step S2). Subsequently, the settlement server 10 receives the remittance information input to the terminal device 100-1 by the user U from the terminal device 100-1 (step S3).

Here, an example of the screen displayed by the terminal device 100-1 and the remittance information transmitted to the settlement server 10 by the terminal device 100-1 in the above embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of a screen of the terminal device according to the embodiment;

First, the terminal device 100-1 displays a screen SC11 for instructing remittance to another user or receipt of remittance from another user. For example, the terminal device 100-1 has an area AR11 for displaying users pre-registered in the payment application, a button B11 for instructing remittance to other users, and a remittance from other users. A screen SC11 including a button B12 for instructing the reception of the is displayed. As a specific example, when the button B11 is pressed, the terminal device 100-1 accepts the designation of the remittance destination user in the area AR11. Further, when the button B12 is pressed, the terminal device 100-1 accepts the designation of the user who has sent money to the user U1 in the area AR11.

In the example of FIG. 2, it is assumed that button B11 has been pressed and user U6 has been designated as the remittance recipient. In this case, the terminal device 100-1 makes a transition to the screen SC12 for receiving input of the remittance amount for the user U6. For example, the terminal device 100-1 displays a screen SC12 including a button B13 for instructing confirmation of the remittance amount and an area AR12 for receiving input of the remittance amount. As a specific example, the terminal device 100-1 accepts the input of the remittance amount in the area AR12, and when the button B13 is pressed, changes the screen SC12 to the screen SC13.

The terminal device 100-1 has an area AR13 for displaying remittance information including the remittance amount, and content visually indicating the purpose of the remittance from the user U1 to the user U6 (hereinafter sometimes referred to as a "theme"). ) and a button B14 for instructing remittance to user U6. For example, the terminal device 100-1 controls the icons corresponding to each theme to be scrollable in the area AR14, and displays the content corresponding to the icon selected by the user U1 in the area AR13.

In the example of FIG. 2, it is assumed that an icon corresponding to the theme "drinking cost" is selected in the area AR14. In this case, the terminal device 100-1 transitions to the screen SC14 displaying the theme "drinking party" in the area AR13. Then, when button B14 is pressed on screen SC14, terminal device 100-1 displays remittance information # including remittance amount, information (user ID) indicating user U6, and information indicating theme "drinking fee". 1 to the settlement server 10.

Returning to FIG. 1, the description continues. The settlement server 10 transfers the remittance amount indicated by the remittance information to the account of the remittee user (step S4). For example, based on the remittance information #1 transmitted from the terminal device 100-1 in the example shown in FIG. 000 yen” worth of electronic money is transferred.

Subsequently, the settlement server 10 provides the content corresponding to the remittance information #1 to the terminal device 100-6 (step S5). For example, the settlement server 10 provides the terminal device 100-6 with a notification indicating that remittance has been received from the user U1. Then, the terminal device 100-6 displays a notification indicating that the remittance has been performed by the user U1 on the payment application, and responds to the user U6's selection operation (in other words, remittance receiving operation) in response to the notification. to display the content corresponding to the theme "drinking fee".

Subsequently, the settlement server 10 adds purpose information indicating the purpose of the remittance to the remittance information #1 (step S6). For example, the settlement server 10 adds purpose information indicating "drinking fee" to remittance information #1 based on the theme indicated by remittance information #1.

Subsequently, the settlement server 10 provides the terminal device 100-1 with the remittance information #1 to which the purpose information is added (step S7). For example, the payment server 10 provides the terminal device 100-1 with the remittance information #1 to which the purpose information is added as information indicating the transaction (payment) history of the user U1 in the payment application.

Subsequently, the terminal device 100-1 displays the remittance information #1 to which the purpose information is added according to the operation by the user U1 (step S8). For example, the terminal device 100-1 displays a screen SC1 showing transaction history in the payment application in response to an operation from the user U1. As a specific example, terminal device 100-1 displays remittance information #1 in area AR1, and text information indicating purpose information given to remittance information #1 in the item "memo" included in area AR1. Display "drinking fee".

Note that terminal device 100-1 may accept an editing operation for the item "memo" from user U1. For example, the terminal device 100-1 accepts input of information indicating the situation when the payment was made (for example, the location (store, etc.) where the drinking party was held, the participants, the date and time, etc.). Note that the settlement server 10 may present the user U1 with a suggestion for performing an editing operation on the “memo” item.

As described above, the settlement server 10 according to the embodiment automatically adds purpose information indicating the purpose of the remittance to the remittance information related to the remittance performed by the user by electronic settlement, and provides the purpose information to the user. Thereby, the settlement server 10 according to the embodiment enables the user to grasp to whom the remittance was made and for what purpose. That is, the payment server 10 according to the embodiment allows the user to specifically grasp the purpose of payment.

[2. Configuration of payment server]
Next, the configuration of the settlement server 10 will be described using FIG. FIG. 3 is a diagram showing a configuration example of a payment server according to the embodiment. As shown in FIG. 3, the settlement server 10 has a communication section 20, a storage section 30, and a control section 40.

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

(Regarding storage unit 30)
The storage unit 30 is implemented by, for example, a semiconductor memory device such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in FIG. 3 , the storage unit 30 has an account database 31 and a user information database 32 .

(Regarding account database 31)
The account database 31 stores various types of information regarding accounts of users of the electronic payment service. An example of information stored in the account database 31 will now be described with reference to FIG. FIG. 4 is a diagram showing an example of an account database according to the embodiment. In the example of FIG. 4, the account database 31 has items such as "account ID", "owner information", and "account balance".

"Account ID" indicates identification information for identifying an account. "Owner information" indicates information about the owner (user) who owns the account, and stores, for example, identification information (identifier) for identifying the owner. "Account balance" indicates the balance of the account owned by the user.

That is, FIG. 4 shows an example in which the information of the owner of the account identified by the account ID "AID#1" is "user #1" and the account balance is "7800".

(Regarding the user information database 32)
The user information database 32 stores various information about users of the electronic payment service. An example of information stored in the user information database 32 will now be described with reference to FIG. FIG. 5 is a diagram illustrating an example of a user information database according to the embodiment; In the example of FIG. 5, the user information database 33 has items such as "user ID", "registration information", and "payment history".

"User ID" indicates identification information for identifying a user. "Registration information" indicates information about the user registered as the remittee, such as telephone number, user ID, and information indicating the relationship with the user (for example, parent, child, friend, etc.). Stored. "Payment history" indicates the history (payment information) of payments (remittances) made using the electronic payment service, such as "payment ID", "purpose information", "payee", "transaction target", It has items such as "date and time" and "location information".

"Payment ID" indicates identification information for identifying a payment. "Purpose information" indicates the purpose information attached to the payment information. "Payee" indicates the payment destination (or remittance destination) of settlement. "Transaction object #1" stores the information indicating the transaction object to be settled when the information can be acquired. "Date and time" indicates the date and time when the payment was made. “Position information” indicates the position of the user (in other words, the position of the terminal device 100) when the payment was made.

That is, in FIG. 5, the registration information of the user identified by the user ID "UID#1" is "registration information #1", and the payment information related to the payment identified by the payment ID "PID#1" is given. The purpose information is "Purpose information #1", the payee is "Payee #1", the transaction target is "Transaction target #1", the date and time of the payment is "Date and time #1", the payment was made An example in which the current position is "position information #1" is shown.

(Regarding the control unit 40)
The control unit 40 is a controller, for example, a CPU (Central Processing Unit), MPU (Micro Processing Unit) or the like executes various programs stored in a storage device inside the payment server 10 using the RAM as a work area. It is realized by being executed. Also, the control unit 40 is a controller, and is implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). As shown in FIG. 3, the control unit 40 according to the embodiment includes a reception unit 41, a payment processing unit 42, a presentation unit 43, a provision unit 44, and a provision unit 45, and includes information described below. Realize or perform the function or action of a process.

(Regarding the reception unit 41)
The accepting unit 41 accepts payment information related to payment made by a user using a predetermined payment method. For example, the reception unit 41 receives payment information indicating the user identification information that identifies the user, the store identification information captured via the payment application, and the payment amount input by the user or the store clerk to the terminal. Received from device 100 .

In addition, the reception unit 41 receives payment information including the payee of the payment, the transaction target for the payment, the date and time when the payment was made, and the location information indicating the position of the user when the payment was made. It may be received from the device 100 .

Further, the receiving unit 41 may receive payment information from a terminal device used by a provider of a transaction target. For example, when the store terminal reads the user identification information for identifying the user displayed on the terminal device 100 and the payment is made, the reception unit 41 sends the payment information indicating the payment to the store terminal. accept from

In addition, the receiving unit 41 may receive remittance information related to settlement (that is, remittance between users) for transferring electronic money from one user's account to another user's account. For example, in the example of FIG. 1, the reception unit 41 transmits the remittance information #1 including the remittance amount, information (user ID) indicating the user U6, and information indicating the theme "drinking fee" to the terminal device 100-1. accept from

(Regarding the payment processing unit 42)
The payment processing unit 42 executes payment processing according to the payment information received by the reception unit 41 . For example, the payment processing unit 42 transfers the amount of electronic money indicated by the payment amount from the account of the user indicated by the user identification information to the account of the shop indicated by the shop identification information.

Further, the settlement processing unit 42 may execute a process of transferring the remittance amount from the user's account to the user's account to which the remittance amount is to be remitted. For example, in the example of FIG. 1, the settlement processing unit 42 executes a process of transferring the amount of electronic money indicated by the remittance amount from the account of user U1 to the account of user U6.

(About presentation part 43)
Here, when the user attaches a memo to the payment information, there may be a desire to realize smooth input of the memo by presenting information indicating the status of the payment. Therefore, the presentation unit 43 presents the user with context information indicating the context when the payment is made. For example, in the example of FIG. 1, the presentation unit 43 presents a suggestion based on the remittance information #1 to the user U1.

In addition, the presentation unit 43 provides the user with context information indicating at least one of the payee of the payment, the transaction target of the payment, the date and time when the payment was made, and the user's position when the payment was made. may be presented. For example, when the payee by settlement is a business operator that provides services (public utilities) that supply water, electricity, gas, etc. to users, and the date of settlement is "May", the presentation unit 43 , a suggestion such as "Is it the public utility bill for April?" is presented to the user. Further, when the user's position when the payment is made is in "store A" and the date and time when the payment is made is "May 31st", the presentation unit 43 displays "May 31st Shopping at store A?” is presented to the user.

(Regarding the granting unit 44)
The adding unit 44 adds purpose information indicating the purpose of payment corresponding to the payment information received by the receiving unit 41 to the payment information. For example, in the example of FIG. 1, the adding unit 44 adds purpose information indicating "drinking fee" to remittance information #1 based on the theme indicated by remittance information #1.

Here, it is conceivable that the purpose of payment should be estimated based on various contexts indicated by the payment information and added to the payment information. Therefore, the adding unit 44 may add purpose information indicating the purpose of payment estimated based on the payment information. For example, the granting unit 44 uses payment information estimated based on payment information including a payee for payment, a transaction target for payment, the date and time of payment, and the position of the user when payment was made. Give purpose information indicating the purpose of

Further, the granting unit 44 may grant purpose information according to the payee of settlement. For example, the adding unit 44 adds purpose information to the payment information based on the information regarding the payee of the payment.

Further, the granting unit 44 may grant purpose information according to the category to which the payee belongs. For example, if the category to which the payee's store belongs is "bar", the adding unit 44 adds the purpose information "drinking fee" to the payment information. Further, when the category to which the payee belongs is "public service provider", the adding unit 44 adds the purpose information "public utility charges" to the payment information.

Further, the granting unit 44 may grant purpose information according to information about the user who is the payee. For example, referring to the information stored in the "registration information" item of the user information database 32, if the user of the remittance destination is registered as "child", the granting unit 44 adds the payment information (remittance information) is given the purpose information "pocket money".

Further, the granting unit 44 may grant purpose information corresponding to a transaction target for settlement. For example, when the category to which the transaction target for payment belongs is "groceries", the adding unit 44 adds the purpose information "food and drink expenses" to the payment information.

Further, the granting unit 44 may grant the purpose information according to the date and time when the payment was made. For example, when the date and time when the payment was made is during the daytime (for example, 11:00 to 14:00) and the payee of the payment belongs to the category “restaurant”, the provision unit 44 adds the purpose information “ Give a lunch fee.

Further, the adding unit 44 may add purpose information according to the position of the user when the payment is made. For example, if the user's position at the time of payment is inside a store belonging to the category "Izakaya", the adding unit 44 adds the purpose information "drinking fee" to the payment information.

Further, the adding unit 44 may add purpose information indicating information input by the user. For example, in the example of FIG. 1, the adding unit 44 receives input of information indicating the situation when payment is made, and adds the received information to the remittance information.

Further, the adding unit 44 adds purpose information, which is information input by the user and indicates information indicating the situation when the payment was made, and purpose information indicating the purpose of the payment estimated based on the payment information. may For example, the adding unit 44 adds purpose information indicating the information (memo) input by the user and the purpose of payment estimated based on the payment information.

Further, the adding unit 44 may add the purpose information based on the context information and the information input by the user to the payment information. For example, the adding unit 44 adds purpose information indicating information input by the user according to the context information presented by the presenting unit 43 to the payment information.

(Regarding the providing unit 45)
The providing unit 45 provides the user with the payment information to which the purpose information is added by the providing unit 44 . For example, in the example of FIG. 1, the providing unit 45 provides the remittance information #1 to which the purpose information is added to the terminal device 100-1 as information indicating the transaction history of the user U1 in the payment application.

Here, there may be a demand for a payment application to have a function such as a household account book function by aggregating and providing payment information to which corresponding purpose information is added to the user. Therefore, the providing unit 45 may classify the payment information into predetermined categories according to the purpose information provided by the providing unit 44, and provide the payment information for each category. For example, the provision unit 45 aggregates and provides the user with the payment information to which the purpose information classified into the same category is added.

In addition, the providing unit 45 may further provide information related to sums of payment amounts indicated by payment information classified into the same category. For example, the providing unit 45 aggregates the payment amounts indicated by the payment information related to payments made within a predetermined period (for example, one week, one month), which are classified into the same category. provide information about

[3. Provision processing flow]
Next, with reference to FIG. 6, a procedure of provision processing of the settlement server 10 according to the embodiment will be described. FIG. 6 is a flowchart illustrating an example of the procedure of provision processing according to the embodiment.

As shown in FIG. 6, the payment server 10 receives payment information related to payment made by a user using a predetermined payment method (step S101). Subsequently, the payment server 10 adds purpose information indicating the purpose of payment corresponding to the payment information to the payment information (step S102). Subsequently, the payment server 10 provides the user with the payment information to which the purpose information is attached (step S103), and ends the process.

[4. Modification]
The above-described embodiment is an example, and various modifications and applications are possible.

[4-1. About payment]
"Settlement" in the present application is not limited to what the user makes in consideration for the provision of various goods and services, for example, simple fund transfer such as remittance between individuals, that is, payment for the provision of goods and services The concept includes the exchange of funds (remittance) that is not compensation. That is, in the present application, "a reception unit that receives payment information related to a payment made by a user using a predetermined payment method, and purpose information that indicates the purpose of the payment corresponding to the payment information received by the reception unit is sent to the payment. A provision device characterized by having an addition unit that adds information and a provision unit that provides the payment information to which the purpose information is added by the addition unit to the user. The concept includes not only the settlement of payments, but also the processing of remittances related to simple fund transfers that are not consideration.

[4-2. About payment information]
In the above-described embodiment, the granting unit 44 performs Although an example of adding purpose information has been shown, payment information is not limited to such an example. For example, the imparting unit 44 may impart the purpose information based on any information that can be acquired from the terminal device 100, the store terminal, or the like.

[4-3. About purpose information]
In the above embodiment, an example in which the adding unit 44 adds the purpose information estimated based on the payment information or the purpose information input by the user according to the context information presented by the presentation unit 43 to the payment information. Although shown, the purpose information is not limited to such examples. For example, the adding unit 44 may add information arbitrarily input by the user to the payment information as the purpose information.

[4-4. About processing mode]
Of the processes described in the above embodiments, all or part of the processes described as being automatically performed can be manually performed, and conversely, all of the processes described as being manually performed can be performed manually. Alternatively, some can be done automatically by known methods. In addition, information including processing procedures, specific names, and various data and parameters shown in the above text 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/integration of each device is not limited to the illustrated one, and all or part of them can be functionally or physically distributed/integrated in arbitrary units according to various loads and usage conditions. Can be integrated and configured.

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 payment server 10 according to the embodiment has the reception unit 41 , the payment processing unit 42 , the presentation unit 43 , the provision unit 44 and the provision unit 45 . The accepting unit 41 accepts payment information related to payment made by a user using a predetermined payment means. The payment processing unit 42 executes payment processing according to the payment information received by the reception unit 41 . The presentation unit 43 presents the user with context information indicating the context when the payment is made. The user is presented with contextual information indicating at least one of the user's location when the payment was made. The adding unit 44 adds purpose information indicating the purpose of payment corresponding to the payment information received by the receiving unit 41 to the payment information. Further, the adding unit 44 adds the purpose information based on the context information and the information input by the user to the payment information. The providing unit 45 provides the user with the payment information to which the purpose information is added by the providing unit 44 .

As a result, the payment server 10 according to the embodiment can automatically add purpose information indicating the purpose of payment to payment information related to payment made by the user by electronic payment, and provide the information to the user. , the user can grasp the purpose of the payment concretely.

In addition, in the payment server 10 according to the embodiment, for example, the adding unit 44 adds purpose information indicating the purpose of payment estimated based on the payment information. Further, the granting unit 44 grants purpose information according to the payee of the settlement. Further, the granting unit 44 grants purpose information according to the category to which the payee belongs. Further, the granting unit 44 grants purpose information according to information about the user who is the payee. Further, the granting unit 44 grants purpose information according to the transaction target that is the target of settlement. Further, the adding unit 44 adds purpose information according to the date and time when the payment is made. Further, the granting unit 44 grants purpose information according to the position of the user when the payment is made.

As a result, the payment server 10 according to the embodiment can automatically provide the purpose information estimated based on the payment information related to the payment made by the user and provide it to the user, thereby improving convenience. be able to.

In addition, in the settlement server 10 according to the embodiment, for example, the adding unit 44 adds purpose information indicating information input by the user. In addition, the adding unit 44 adds purpose information, which is information input by the user and indicates information indicating the situation when the payment was made, and purpose information indicating the purpose of the payment estimated based on the payment information. .

As a result, the settlement server 10 according to the embodiment can automatically add purpose information arbitrarily input by the user, thereby improving convenience.

Further, in the payment server 10 according to the embodiment, for example, the providing unit 45 classifies the payment information into predetermined categories according to the purpose information provided by the providing unit 44, and provides the payment information for each category. good too. For example, the provision unit 45 aggregates and provides the user with the payment information to which the purpose information classified into the same category is added. In addition, the providing unit 45 further provides information related to sums of payment amounts indicated by payment information classified into the same category.

As a result, the payment server 10 according to the embodiment aggregates the payment information to which the corresponding purpose information is added and provides it to the user, thereby allowing the payment application to have a function such as a household account book function. Therefore, convenience can be improved.

[6. Hardware configuration]
Also, the settlement server 10 according to each of the embodiments described above is implemented by, for example, a computer 1000 configured as shown in FIG. The settlement server 10 will be described below as an example. FIG. 7 is a hardware configuration diagram showing an example of a computer that implements the functions of the settlement server. Computer 1000 has CPU 1100 , ROM 1200 , RAM 1300 , HDD 1400 , communication interface (I/F) 1500 , input/output interface (I/F) 1600 and media interface (I/F) 1700 .

The CPU 1100 operates based on programs stored in the ROM 1200 or HDD 1400 and controls each section. The ROM 1200 stores a boot program executed by the CPU 1100 when the computer 1000 is started, programs dependent on the hardware of the computer 1000, and the like.

The HDD 1400 stores programs executed by the CPU 1100, data used by the programs, and the like. Communication interface 1500 receives data from another device via communication network 500 (corresponding to network N in the embodiment) and sends it to CPU 1100 , and transmits data generated by CPU 1100 via communication network 500 to other devices. Send to device.

The CPU 1100 controls output devices such as displays and printers, and input devices such as keyboards and mice, through an input/output interface 1600 . CPU 1100 acquires data from an input device via input/output interface 1600 . Also, CPU 1100 outputs the generated data to an output device via input/output interface 1600 .

Media interface 1700 reads programs or data stored in recording medium 1800 and provides them to CPU 1100 via RAM 1300 . CPU 1100 loads such a program from recording medium 1800 onto RAM 1300 via media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable disc), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. etc.

For example, when the computer 1000 functions as the settlement server 10 , the CPU 1100 of the computer 1000 implements the functions of the control unit 40 by executing programs loaded on the RAM 1300 . Further, each data in the storage device of the settlement server 10 is stored in the HDD 1400 . CPU 1100 of computer 1000 reads these programs from recording medium 1800 and executes them, but as another example, these programs may be obtained from another device via a predetermined communication network.

[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 10 described above can be flexibly changed, for example, by calling an external platform or the like using an API (Application Programming Interface), network computing, or the like, depending on the function.

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

10 settlement server 20 communication unit 30 storage unit 31 account database 32 user information database 40 control unit 41 reception unit 42 settlement processing unit 43 presentation unit 44 grant unit 45 provision unit 100 terminal device

Claims (22)

a reception unit that receives payment information related to payment made by a user using a predetermined payment method;
an addition unit that extracts a payment target from the payment information received by the reception unit and adds memorandum information estimated based on the payment target to the payment information;
a providing unit that provides the user with the payment information to which the memorandum information has been added by the providing unit;
The granting unit is
A providing device that automatically provides the memorandum information estimated based on the payment object extracted from the payment information. a reception unit that receives payment information related to payment made by a user using a predetermined payment method;
a presenting unit that extracts context information about payment details when the payment is made from the payment information and presents the context information to the user;
a granting unit that generates memorandum information based on information input by the user based on the context information and the context information, and adds the memorandum information to the payment information;
and a providing unit that provides the user with the payment information to which the memorandum information has been added by the providing unit. a reception unit that receives payment information related to payment made by a user using a predetermined payment method;
a presenting unit that extracts context information about payment details when the payment is made from the payment information and presents the context information to the user;
a granting unit that generates memorandum information based on information input by the user based on the context information and the context information, and adds the memorandum information to the payment information;
and a providing unit that provides the user with the payment information to which the memorandum information has been added by the providing unit as a transaction history list. a reception unit that receives payment information related to payment made by a user using a predetermined payment method;
an addition unit that extracts a payment target from the payment information received by the reception unit and adds memorandum information estimated based on the payment target to the payment information;
a providing unit that provides the user with the payment information to which the memorandum information has been added by the providing unit;
The providing unit
A providing device, further comprising: providing information relating to an aggregate amount of settlement amounts indicated by the settlement information classified into the same category. The granting unit is
The provision device according to any one of claims 1 to 4, wherein the estimated memorandum information is provided based on a payee extracted from the payment information received by the receiving unit. The granting unit is
6. The provision device according to claim 5, wherein the memorandum information estimated based on the category to which the payee belongs is provided. The granting unit is
7. The providing device according to claim 5 or 6, wherein the memorandum information estimated based on information about the user who is the payee is provided. The granting unit is
Any one of claims 1 to 7, wherein the estimated memorandum information is given based on the transaction target to be settled, which is extracted from the payment information received by the reception unit. 1. The delivery device according to 1. The granting unit is
Any one of claims 1 to 8, wherein the memorandum information estimated based on the date and time when the payment is made is extracted from the payment information received by the reception unit. 2. The delivery device described in . The granting unit is
10. The memorandum information estimated based on the position of the user when the payment is made , which is extracted from the payment information received by the reception unit, is given. A provider according to any one of The providing unit
The payment information estimated based on the memorandum information provided by the provision unit is classified into predetermined categories, and the payment information is provided for each category. or a provider according to one of the preceding claims. The providing unit
12. The providing device according to claim 11, further providing information on an aggregate amount of payment amounts indicated by the payment information classified into the same category. The granting unit is
Giving the information input by the user, which indicates the situation when the payment was made, and the memorandum information related to the payment target estimated based on the payment information. 13. A provider according to any one of claims 2-12. The presentation unit
The user is provided with the context information indicating at least one of the payee of the payment, the transaction target for the payment, the date and time when the payment was made, and the position of the user when the payment was made. 4. The providing device according to claim 2 or 3, characterized in that it presents. A computer-implemented method of providing, comprising:
a receiving step of receiving payment information related to payment made by a user using a predetermined payment method;
an addition step of extracting a payment target from the payment information received in the receiving step and adding memorandum information estimated based on the payment target to the payment information;
a provision step of providing the user with the payment information to which the memorandum information is attached by the provision step;
The applying step includes
A provision method, wherein the memorandum information estimated based on the payment object extracted from the payment information is automatically provided. a reception procedure for receiving payment information related to payment made by a user using a predetermined payment method;
an attachment procedure for extracting a payment target from the payment information received by the reception procedure and adding memorandum information estimated based on the payment target to the payment information;
causing a computer to execute a provision procedure of providing the user with the payment information to which the memorandum information is attached by the provision procedure;
The granting procedure includes:
A providing program for causing a computer to automatically provide the memorandum information estimated based on the payment object extracted from the payment information. A computer-implemented method of providing, comprising:
a receiving step of receiving payment information related to payment made by a user using a predetermined payment method;
a presenting step of extracting from the payment information context information about payment details when the payment is made, and presenting the context information to the user;
an attachment step of generating memorandum information based on the context information and the information input by the user based on the context information, and attaching the memorandum information to the payment information;
and a providing step of providing the payment information to which the memorandum information has been added by the providing step to the user. a reception procedure for receiving payment information related to payment made by a user using a predetermined payment method;
a presentation procedure for extracting from the payment information context information about payment details when the payment is made, and presenting the context information to the user;
an attachment procedure for generating memorandum information based on the context information and information input by the user based on the context information, and attaching the memorandum information to the payment information;
A providing program for causing a computer to execute a providing procedure for providing the payment information to which the memorandum information is attached by the providing procedure to the user. A computer-implemented method of providing, comprising:
a receiving step of receiving payment information related to payment made by a user using a predetermined payment method;
a presenting step of extracting from the payment information context information about payment details when the payment is made, and presenting the context information to the user;
an attachment step of generating memorandum information based on the context information and the information input by the user based on the context information, and attaching the memorandum information to the payment information;
and a providing step of providing the payment information to which the memorandum information has been added by the providing step as a transaction history list to the user. a reception procedure for receiving payment information related to payment made by a user using a predetermined payment method;
a presentation procedure for extracting from the payment information context information about payment details when the payment is made, and presenting the context information to the user;
an attachment procedure for generating memorandum information based on the context information and information input by the user based on the context information, and attaching the memorandum information to the payment information;
and a providing procedure for providing the payment information to which the memorandum information has been added by the providing procedure to the user as a transaction history list. A computer-implemented method of providing, comprising:
a receiving step of receiving payment information related to payment made by a user using a predetermined payment method;
an addition step of extracting a payment target from the payment information received in the receiving step and adding memorandum information estimated based on the payment target to the payment information;
a provision step of providing the user with the payment information to which the memorandum information is attached by the provision step;
The providing step includes
A providing method, further comprising: providing information on an aggregate amount of settlement amounts indicated by the settlement information classified into the same category. a reception procedure for receiving payment information related to payment made by a user using a predetermined payment method;
an attachment procedure for extracting a payment target from the payment information received by the reception procedure and adding memorandum information estimated based on the payment target to the payment information;
causing a computer to execute a provision procedure of providing the user with the payment information to which the memorandum information is attached by the provision procedure;
The providing procedure includes:
A providing program for causing a computer to further provide information on an aggregate amount of settlement amounts indicated by the settlement information classified into the same category.

Images