Information processing device, information processing program, and information processing method
The information processing device optimizes transaction information acquisition by adjusting frequencies based on financial service types, addressing inefficiencies in aggregation services and reducing costs.
Patent Information
- Application Number
- JP2024088466
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-05-31
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2044-05-31
AI Technical Summary
Existing technologies lack efficient methods for aggregating transaction information from multiple financial services, leading to high communication load and cost in aggregation services.
An information processing device that adjusts the frequency of transaction information acquisition based on the type of financial service, using a transaction information acquisition unit to store and retrieve data efficiently, and a calculation unit to process and display the information.
Enables efficient and effective acquisition of transaction information across various financial services, reducing communication load and cost while ensuring real-time updates for critical services.
Smart Images

Figure 0007587787000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to an information processing device, an information processing program, and an information processing method. [Background technology]
[0002] Conventionally, when obtaining information on the balance or deposits and withdrawals of a bank account or virtual account using an API (Application Programming Interface) provided by a bank, a function has been known that changes the frequency of obtaining such information depending on the frequency of deposits, withdrawals, or settlements (see, for example, Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 6831165 Summary of the Invention [Problem to be solved by the invention]
[0004] In recent years, financial services that provide payment services and the like (hereinafter simply referred to as "financial services") have become more diverse, and it is becoming increasingly common for one user to use multiple financial services. For this reason, there is a need for a service (hereinafter referred to as "aggregation service") that collectively provides transaction information for the multiple financial services used by a user. Hereinafter, the financial services that are the target of an aggregation service are also referred to as "target financial services." Aggregation services can be provided, for example, by acquiring transaction information using APIs published by businesses that provide each target financial service. However, from the perspective of communication load or cost, it is necessary to efficiently acquire transaction information using APIs. Until now, there has been a problem in that there has not been any technology available to efficiently obtain transaction information in aggregation services. For example, the technology disclosed in Patent Document 1 does not provide an aggregation service, and does not solve the above-mentioned problems.
[0005] The present disclosure has been made to solve the above-mentioned problems, and aims to provide an information processing device that can efficiently acquire transaction information in an aggregation service. [Means for solving the problem]
[0006] The information processing device according to the present disclosure includes a transaction information acquisition unit that acquires transaction information of a target user regarding a plurality of target financial services, and a calculation unit that calculates at least one of expenditures or a balance of the target user based on the transaction information acquired by the transaction information acquisition unit, and the frequency of acquisition of transaction information by the transaction information acquisition unit varies depending on the type of target financial service. The transaction information acquisition unit specifies the frequency of acquisition of transaction information based on the ID unique to the target financial service or the ID capable of distinguishing the type of the target financial service and the information indicating the acquisition frequency, which is stored in a storage unit that stores information indicating the frequency of acquisition of transaction information by the transaction information acquisition unit in association with the ID unique to the target financial service or the ID capable of distinguishing the type of the target financial service. It is characterized by: Effect of the Invention
[0007] According to the present disclosure, since the above-mentioned configuration is adopted, it is possible to change the transaction frequency of transaction information depending on the type of target financial service. Therefore, according to the present disclosure, it is possible to efficiently or effectively obtain transaction information in an aggregation service. [Brief description of the drawings]
[0008] [Figure 1] 1 is a diagram illustrating an example of a configuration of an information processing system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a configuration of a server according to the first embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of a configuration of a client terminal according to the first embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of a server and a client terminal according to the first embodiment. [Diagram 5] 5 is a flowchart showing an example of the operation of the server according to the first embodiment. [Figure 6]1 is a diagram for explaining linkage of financial services to personal accounts in the information processing system according to the first embodiment. FIG. [Figure 7] FIG. 4 is a diagram showing an example of an individual account screen displayed on a client terminal in accordance with the first embodiment. [Figure 8] FIG. 11 is a diagram illustrating an example of a configuration of an information processing system according to a second embodiment. [Figure 9] FIG. 11 is a diagram illustrating an example of a configuration of a server according to the second embodiment. [Figure 10] FIG. 11 is a diagram illustrating an example of a configuration of a client terminal according to the second embodiment. [Figure 11] A diagram explaining the linkage of financial services to a joint account in an information processing system relating to embodiment 2. [Figure 12] FIG. 11 is a diagram illustrating an example of a configuration of a server according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, the embodiments will be described in detail with reference to the drawings. Embodiment 1 FIG. 1 is a diagram showing an example of a configuration of an information processing system 1 according to the first embodiment. In an information processing system 1, as shown in FIG. 1, a server 3 (information processing device), a client terminal 2 used by a target user, and a store terminal 4 are connected via a network NW. An existing electric communication line can be used as the network NW. The network NW is, for example, the Internet. Note that "target" means a target from which transaction information is to be obtained. In the example of FIG. 1, an external server 5 is additionally connected to the network NW. In the example of FIG. 1, the client terminal 2 is a client terminal 2A1 used by a target user A1.
[0010] Although only one client terminal 2 is shown in FIG. 1, a plurality of client terminals 2 can be connected to the network NW. Although only one store terminal 4 is shown in FIG. 1, a plurality of store terminals 4 can be connected to the network NW.
[0011] The server 3 provides an aggregation service to the target user. The business entity that provides the aggregation service using the server 3 may be the same business entity as the business entity that provides the target financial service. In the following, a business providing aggregation services using server 3 (hereinafter referred to as "aggregation service provider") is also considered to be one of the businesses providing payment services that enable payment transactions using a payment card or code payment. Examples of payment cards include any card that can be used to pay for a price, such as a prepaid card or credit card. Examples of code payment include displaying a barcode or two-dimensional barcode on the screen of a smartphone or the like.
[0012] In the example of FIG. 1, the target user purchases a product or receives a service at a store equipped with a store terminal 4. When the target user pays for the product with a payment card, the store terminal 4 transmits transaction information to the server 3 or the external server 5. The transaction information includes, for example, the store name, the product name, the service name, the transaction date and time, the transaction amount, and the identification information of the payment card. The transaction information acquired from the store terminal 4 is stored in the memory unit 33 of the server 3 or the memory unit of the external server 5. In addition, the transaction information stored in the memory unit 33 of the server 3 or the memory unit of the external server 5 includes information such as the transaction date and time and transaction amount when a deposit or withdrawal transaction is made in the payment service, or the transaction date and time and transaction amount when an account transaction and bank settlement is made in the banking service, as described below. The transaction information also includes information on the balance of various accounts in a payment service or the balance of an account in a banking service.
[0013] The external server 5 is a server for providing an external service different from the aggregation service using the server 3. The external service is a target financial service provided by a business other than the aggregation service provider. For example, the external service may be a bank service provided by a bank or a payment service provided by a business other than a bank, and the external server 5 may be a server used in the bank service provided by a bank or a server used in the payment service provided by a business other than a bank, as described below. When the transaction information is transmitted to the external server 5, the server 3 can acquire the transaction information from the external server 5 by API linkage with the external server 5. The transaction information acquired from the external server 5 is stored in the memory unit 33 of the server 3 (see FIG. 2).
[0014] The server 3 includes a communication unit 31, a calculation unit 32, and a storage unit 33, as shown in FIG. The server 3 may be physically configured with one terminal, or may be configured with multiple terminals.
[0015] The communication unit 31 communicates with the client terminal 2, the store terminal 4, or the external server 5 via the network NW.
[0016] The calculation unit 32 controls the overall operation of the server 3. The calculation unit 32 executes information processing device applications to realize various functions.
[0017] The storage unit 33 stores information processing device applications and stores data used in the arithmetic processing of the arithmetic unit 32. In addition, when the server 3 executes a client terminal application to provide each function to the client terminal 2 via the network NW, the storage unit 33 also stores the client terminal application. The storage unit 33 may be provided outside the server 3 as long as it is accessible from the server 3 .
[0018] 2, the calculation unit 32 includes a transaction information acquisition unit 301, a calculation unit 302, a display information output unit 303, and an association information acquisition unit 304. The calculation unit 32 executes, for example, an information processing device application, thereby realizing the functions of the transaction information acquisition unit 301, the calculation unit 302, the display information output unit 303, and the association information acquisition unit 304.
[0019] The transaction information acquisition unit 301 acquires transaction information of a target user regarding a plurality of target financial services. As described above, when the aggregation service provider is one of the providers that provide a payment service that enables a payment transaction using a payment card or a payment transaction by code payment, the transaction information acquisition unit 301 acquires transaction information from the store terminal 4, for example, every time a payment transaction is made by the target user using the payment card or a code such as a two-dimensional barcode. Also, when the payment card is a so-called rechargeable prepaid card, transaction information indicating the recharge can be acquired every time the target user's prepaid card is recharged. Also, in the case of code payment, transaction information indicating a deposit / withdrawal transaction can be acquired every time the target user recharges the code payment account of the target user or withdraws money for remittance to another person. Furthermore, the transaction information acquisition unit 301 can acquire transaction information of the target user in the target financial service provided by another business operator at a timing to be described later by performing API cooperation with the external server 5.
[0020] The frequency with which the transaction information acquisition unit 301 acquires transaction information varies depending on the type of target financial service.
[0021] Examples of target financial service types include banking services provided by banks and payment services provided by businesses other than banks. Transaction information related to payment services is information indicating payment transactions and information indicating deposit / withdrawal transactions, while transaction information related to bank services is information indicating account transactions. Examples of payment transactions in payment services include payment transactions using prepaid cards or credit cards, or payment transactions by code payment. Account transactions include all transactions related to deposits and withdrawals from bank accounts, such as bank payment transactions and deposit / withdrawal transactions.
[0022] For example, each of the multiple target financial services may be assigned a unique ID (hereinafter referred to as the "target financial service ID"), and each type of target financial service may be assigned an ID (hereinafter referred to as the "type ID") that allows each type to be distinguished, and the name, type ID, and target financial service ID indicating each of the multiple target financial services may be stored in association with each other in the memory unit 33 of the server 3. Furthermore, the information indicating the acquisition frequency for each type may be linked to the above-mentioned type-specific ID and stored in the storage unit 33, or may be linked to the target financial service ID and stored in the storage unit 33. The acquisition frequency for each type of target financial service is set in advance by, for example, an aggregation service provider, and information indicating the acquisition frequency is stored in the storage unit 33. Here, when a target user registers to use the aggregation service, each target user is assigned a unique ID (hereinafter referred to as a "user ID"), and the user ID may be stored in memory unit 33 in association with the target financial service IDs of each of a number of target financial services that the target user indicated by the user ID has specified as being subject to the aggregation service. Hereinafter, by storing various types of information as described above in the memory unit 33, the transaction information acquisition unit 301 can identify the acquisition frequency at which transaction information should be acquired for each type of target financial service, and can identify, for each target user, the target financial service that the target user has targeted in the aggregation service.
[0023] Furthermore, when the target financial services are banking services and payment services, the transaction information acquisition unit 301 acquires transaction information more frequently for the payment services than for the banking services.
[0024] If the payment service is a specific payment service, the transaction information acquisition unit 301 may acquire transaction information (information indicating the payment transaction) when the payment transaction is executed. Furthermore, when the payment service is a payment service other than the specific payment service, the transaction information acquisition unit 301 may acquire transaction information less frequently than when the payment service is the specific payment service. The business providing the specific payment service may be an aggregation service provider. When the specific payment service is a service provided by the aggregation service provider itself, the transaction information acquired from the store terminal 4 is stored in the storage unit 33 of the server 3. Therefore, the transaction information acquisition unit 301 can acquire the transaction information every time a payment transaction is executed, and can acquire the transaction information relatively frequently. In contrast, in the above case, payment services other than the specific payment service are provided by businesses other than the aggregation service provider, and transaction information from the payment services is managed by external server 5. From the viewpoint of communication load or cost when using an API, transaction information acquisition unit 301 does not acquire transaction information every time a payment transaction is executed, but acquires transaction information from external server 5 at a relatively low frequency. The acquisition frequency for each payment service is set in advance by, for example, an aggregation service provider, and information indicating the acquisition frequency is stored in storage unit 33 in association with the target financial service ID. By storing the various information as described above in the memory unit 33, the transaction information acquisition unit 301 can specify the acquisition frequency at which transaction information should be acquired depending on whether the payment service provided by the target financial service is a specific payment service or another payment service. Then, the transaction information acquisition unit 301 acquires transaction information for each payment service depending on the transaction frequency acquired from the memory unit 33.
[0025] Furthermore, the transaction information acquisition unit 301 may treat the specific service as a payment service designated by the client terminal 2 used by the target user. In other words, which payment service among the payment services provided by a plurality of target financial services is the specific payment service and which payment service is the other payment service may be designated, for example, by the target user, and information indicating whether or not a payment service is the specific payment service may be stored in the storage unit 33 in association with each target financial service ID. When the target user operates the operation unit 23 (described later) to acquire operation information for designating a specific payment service and other services from the operation unit 23, the client terminal 2 generates information indicating the content of the designation (hereinafter referred to as "specific payment service designation information") and transmits the generated specific payment service designation information to the server 3. The specific payment service designation information may include the user ID of the target user who operated the client terminal 2, the above-mentioned target financial service ID, and information indicating whether a payment service provided by the target financial service indicated by each target financial service ID has been designated as a specific payment service. When the server 3 acquires the specific payment service designation information from the client terminal 2, it stores the acquired specific payment service designation information in the storage unit 33. By storing the various information as described above in the memory unit 33, the transaction information acquisition unit 301 can specify, for each target user, the acquisition frequency at which transaction information should be acquired depending on whether the payment service provided by the target financial service is a specific payment service designated by the target user or another payment service. Then, the transaction information acquisition unit 301 acquires transaction information for each payment service depending on the transaction frequency acquired from the memory unit 33.
[0026] Furthermore, the transaction information acquisition unit 301 may acquire transaction information related to target financial services with different acquisition frequencies on a specific day. The specific day may be, for example, a day on which transaction information is acquired for a target financial service with a low acquisition frequency among the target financial services with different acquisition frequencies. For example, in the case where the target financial services are a payment service and a banking service, the transaction information acquisition unit 301 may acquire transaction information related to the payment service on the day when it acquires transaction information related to the banking service.
[0027] Furthermore, the transaction information acquisition unit 301 may acquire transaction information related to target financial services with different acquisition frequencies at a specific timing on the specific day. The specific timing may be, for example, the timing of acquiring transaction information for a target financial service with a low acquisition frequency among the target financial services with different acquisition frequencies. For example, if the target financial services are payment services and bank services, and transaction information regarding the bank services is acquired first thing in the morning on a particular day, the transaction information acquisition unit 301 may also acquire transaction information regarding the payment services first thing in the morning on the day on which the transaction information regarding the bank services is acquired. A specific day or a specific timing on a specific day (for example, a specific time such as "first thing in the morning") is set in advance by the aggregation service provider, and information indicating the timing for acquiring such transaction information is stored in memory unit 33 in association with the target financial service ID. By storing various types of information as described above in the memory unit 33, the transaction information acquisition unit 301 determines whether or not to acquire transaction information depending on whether the current date is a specific day or whether the current date is a specific timing on a specific day, and acquires the transaction information if it is determined that the transaction information should be acquired.
[0028] When the transaction information acquisition unit 301 acquires the transaction information of the target user regarding multiple target financial services, it links the acquired transaction information to the user ID of the target user and stores it in the memory unit 33, or in addition, outputs it to the calculation unit 302.
[0029] The calculation unit 302 calculates at least one of the expenditures or balance of the target user based on the transaction information acquired by the transaction information acquisition unit 301. That is, the calculation unit 302 has any one of the functions of calculating the expenditures of the target user from the transaction information, calculating the balance of the target user from the transaction information, or calculating the expenditures and balance of the target user from the transaction information. The expenditures or balance are expenditures or balances based on the transaction information of the entirety of multiple target financial services linked to the target user's account.
[0030] In addition, when the calculation unit 302 has a function of calculating expenditures, the calculation unit 302 can calculate the expenditures of the target user for any period based on the transaction information of the target user. For example, the calculation unit 302 can calculate the expenditures within a one-month period from the current time. The period for which the calculation unit 302 calculates the expenditure may be set in advance by an aggregation service provider, and information indicating the period (hereinafter referred to as "period information") may be stored in the storage unit 33. Alternatively, the period for which the calculation unit 302 calculates the expenditure may be specified by the target user. When the target user operates the operation unit 23 to obtain operation information for specifying the period for which the expenditure is to be calculated from the operation unit 23, the client terminal 2 generates period information indicating the specified period, and transmits the generated period information to the server 3. The period information may include the user ID of the target user who operated the client terminal 2. When the server 3 obtains the period information from the client terminal 2, it stores the obtained period information in the storage unit 33. In this case, the calculation unit 302 can obtain the period information from the storage unit 33 according to the user ID of the target user for which the expenditure is to be calculated, when calculating the expenditure. When the transaction information acquisition unit 301 acquires transaction information, the calculation unit 302 identifies transactions to be used to calculate expenditures based on the transaction dates and times included in the transaction information of the target user for multiple target financial services acquired by the transaction information acquisition unit 301 and the period information stored in the memory unit 33, identifies, from among the identified transactions, transactions whose transaction amounts in the transaction information indicate expenditures, and calculates expenditures by totaling the expenditure amounts.
[0031] In addition, when the calculation unit 302 has a function of calculating a balance, the calculation unit 302 can calculate the balance of the target user at any time based on the transaction information of the target user. For example, the calculation unit 302 can calculate the balance at the current time. The calculation unit 302 calculates the balance by adding up the balances included in the transaction information of the target user for multiple target financial services acquired by the transaction information acquisition unit 301.
[0032] The display information output unit 303 outputs the display information in response to a request for display information of the personal account screen from the client terminal 2 used by the target user. When the target user operates the operation unit 23, and the client terminal 2 acquires operation information for requesting acquisition of display information for an individual account screen from the operation unit 23, the client terminal 2 generates an acquisition request and transmits the generated acquisition request to the server 3. When the display information output unit 303 of the server 3 acquires the acquisition request from the client terminal 2, it outputs the display information to the communication unit 31 to transmit it to the client terminal 2. When the communication unit 31 acquires the display information from the display information output unit 303, it transmits the display information to the client terminal 2. At this time, the display information output unit 303 outputs display information that enables display of information related to the transaction information acquired by the transaction information acquisition unit 301. For example, the display information output unit 303 generates, as display information, information that enables display of at least one of the transaction information of the target user related to the target financial service, the expenditure calculated using the transaction information, or the balance calculated using the transaction information. It should be noted that this display information may be information showing the individual account screen itself, or may be information that enables the individual account screen to be generated.
[0033] The link information acquisition unit 304 acquires personal account link information used by the server 3 from the client terminal 2. The personal account link information is information indicating a target financial service to be linked to the personal account of the target user. In this case, the personal account of the target user is a personal account of the target user in a payment service provided by an aggregation service provider. As described above, when a target user registers to use an aggregation service, a user ID is assigned to each target user, and the user ID and the target financial service ID of each of the multiple target financial services designated as targets of the aggregation service by the target user indicated by the user ID may be stored in association with each other in the storage unit 33. In other words, in this case, the information indicating the target financial services linked to the target user's personal account is the user ID, the target financial service ID indicating the payment service provided by the aggregation service provider, and the target financial service ID indicating the target financial service providing a payment service other than the payment service specified by the target user, all of which are stored in association with each other in the storage unit 33.
[0034] The client terminal 2 is a terminal capable of communicating with the server 3 via the network NW, and is used by a user. Examples of the client terminal 2 include a smartphone, a tablet terminal, and a PC (Personal Computer).
[0035] The client terminal 2 includes a communication unit 21, a calculation unit 22, an operation unit 23, a display unit 24, and a storage unit 25, as shown in FIG.
[0036] The communication unit 21 communicates with the server 3 via the network NW.
[0037] The calculation unit 22 controls the overall operation of the client terminal 2. For example, when a client terminal application is installed in the client terminal 2, the calculation unit 22 executes the client terminal application to realize various functions. Also, for example, when the client terminal application is executed in the server 3, the calculation unit 22 receives instructions from the server 3 to realize various functions.
[0038] The operation unit 23 is an input device that accepts operations on a screen displayed on the display unit 24 of the client terminal 2. For example, when the client terminal 2 is a smartphone or a tablet terminal, the operation unit 23 is a touch panel that is integral with the display unit 24. Also, when the client terminal 2 is a PC, the operation unit 23 is, for example, a mouse or a keyboard.
[0039] The display unit 24 is a display device included in the client terminal 2. The display unit 24 is, for example, an LCD (Liquid Crystal Display) or an organic EL (Electroluminescence) display device.
[0040] The storage unit 25 stores client terminal applications and stores data used in the arithmetic processing of the arithmetic unit 22 . The storage unit 25 may be provided outside the client terminal 2 as long as it is accessible from the client terminal 2 .
[0041] 3, the calculation unit 22 includes an operation information acquisition unit 201, a linkage information output unit 202, a display information acquisition unit 203, and a display control unit 204. The calculation unit 22 executes, for example, a client terminal application, thereby realizing the functions of the operation information acquisition unit 201, the linkage information output unit 202, the display information acquisition unit 203, and the display control unit 204.
[0042] The operation information acquisition unit 201 acquires operation information. The operation information acquired by the operation information acquisition unit 201 is information indicating an operation accepted by the operation unit 23.
[0043] The linking information output unit 202 outputs personal account linking information to the server 3 based on the operation information acquired by the operation information acquisition unit 201. When the target user operates operation unit 23 to acquire operation information for designating multiple target financial services from operation unit 23, client terminal 2 generates information indicating the content of the designation (hereinafter referred to as "target financial service designation information") and transmits the generated target financial service designation information to server 3. The target financial service designation information may include the user ID of the target user who operated client terminal 2 and the target financial service ID of the designated target financial service. When server 3 acquires the target financial service designation information from client terminal 2, server 3 stores the acquired target financial service designation information in memory unit 33 in association with the user ID of the target user.
[0044] The display information acquisition unit 203 makes a request to acquire display information for the personal account screen to the server 3 based on the operation information acquired by the operation information acquisition unit 201, and acquires the display information from the server 3. When the target user operates the operation unit 23 to acquire operation information for requesting acquisition of display information for the personal account screen from the operation unit 23, the client terminal 2 generates an acquisition request and transmits the generated acquisition request to the server 3. When the display information output unit 303 of the server 3 acquires an acquisition request from the client terminal 2, it transmits the display information to the client terminal 2 via the communication unit 31. When the display information acquisition unit 203 of the client terminal 2 acquires the display information, it outputs the acquired display information to the display control unit 204.
[0045] The display control unit 204 displays an individual account screen on the display unit 24 based on the operation information acquired by the operation information acquisition unit 201 and the display information acquired by the display information acquisition unit 203. If the display information is information indicating the individual account screen itself, the display control unit 204 displays the individual account screen indicated by this information on the display unit 24. If the display information is information that enables an individual account screen to be generated, the display control unit 204 generates an individual account screen from this information and displays the generated individual account screen on the display unit 24. The personal account screen displayed by the display control unit 204 displays, for example, at least one of the following information: transaction information of the target user regarding the target financial service, expenditures calculated using the transaction information, or balance calculated using the transaction information. The display by the display control unit 204 may be performed via a client terminal application downloaded to the client terminal 2, or via a Web application accessible from the client terminal 2 via a Web browser.
[0046] FIG. 4 is a block diagram showing an example of a hardware configuration for implementing the server 3 or the client terminal 2. As shown in FIG.
[0047] For example, the functions of the server 3 are realized by the calculation unit 32. The calculation unit 32 has, as hardware components, a communication interface 100, an input / output interface 101, a processor 102, and a memory 103. The functions of the transaction information acquisition unit 301, the calculation unit 302, the display information output unit 303, and the association information acquisition unit 304 included in the calculation unit 32 are realized by these hardware components.
[0048] The communication interface 100 outputs data received from the client terminal 2 via the network NW by the communication unit 31 to the processor 102, and transmits data generated by the processor 102 to the client terminal 2 via the network NW. The processor 102 controls reading and writing of data from and to the storage unit 33 via the input / output interface 101.
[0049] An information processing program (information processing device application) for realizing each function of the transaction information acquisition unit 301, the calculation unit 302, the display information output unit 303, and the linkage information acquisition unit 304 is stored in the memory 103. The memory 103 is, for example, a semiconductor memory provided in a computer functioning as the server 3. The processor 102 executes the program loaded from the storage unit 33 to the memory 103 via the input / output interface 101. In this way, the processor 102 realizes each function of the transaction information acquisition unit 301, the calculation unit 302, the display information output unit 303, and the linkage information acquisition unit 304.
[0050] The functions of the client terminal 2 are realized by a calculation unit 22. The calculation unit 22 has, as hardware configurations, a communication interface 100, an input / output interface 101, a processor 102, and a memory 103. The functions of an operation information acquisition unit 201, a linkage information output unit 202, a display information acquisition unit 203, and a display control unit 204 included in the calculation unit 22 are realized by these hardware configurations.
[0051] The communication interface 100 outputs data received from the server 3 via the network NW to the processor 102 by the communication unit 21, and transmits data generated by the processor 102 to the server 3 via the network NW. The processor 102 controls the display of the display unit 24 and acquires operation information from the operation unit 23 via the input / output interface 101.
[0052] When a client terminal application is installed in the client terminal 2, a client terminal program (client terminal application) for realizing each function of the operation information acquisition unit 201, the association information output unit 202, the display information acquisition unit 203, and the display control unit 204 is stored in the memory 103. The memory 103 is, for example, a semiconductor memory mounted on a tablet terminal that functions as the client terminal 2.
[0053] When the client terminal application is installed in the client terminal 2, the processor 102 executes a program loaded into the memory 103 via the input / output interface 101. In this way, the processor 102 realizes the functions of an operation information acquisition unit 201, a linkage information output unit 202, a display information acquisition unit 203, and a display control unit 204.
[0054] Next, an example of the operation of the server 3 according to the first embodiment shown in FIG. 2 will be described with reference to FIG. It is assumed that the link information acquisition unit 304 acquires, from the client terminal 2, personal account link information indicating the target financial service to be linked to the personal account of the target user, and stores the information in the storage unit 33 in advance. Fig. 6 is a diagram for explaining the linkage of financial services to a personal account of a target user. In the example of Fig. 6, a case is shown in which an aggregation service provider is one of the providers providing a payment service. In the example of Fig. 6, two target financial services b1 and b2 are linked to a personal account a1 of a target user of this payment service.
[0055] In an example of the operation of server 3 according to embodiment 1 shown in Fig. 2, first, as shown in Fig. 5, transaction information acquisition unit 301 acquires transaction information of a target user regarding a plurality of target financial services (step ST101). The frequency with which transaction information acquisition unit 301 acquires transaction information varies depending on the type of target financial service. For example, when the target financial services are a payment service and a bank service, transaction information acquisition unit 301 acquires transaction information more frequently for the payment service than for the bank service.
[0056] If the payment service is a specific payment service, the transaction information acquisition unit 301 may acquire transaction information (information indicating the payment transaction) when the payment transaction is executed. Furthermore, when the payment service is a payment service other than the specific payment service, the transaction information acquisition unit 301 may acquire transaction information less frequently than when the payment service is the specific payment service.
[0057] Furthermore, the transaction information acquisition unit 301 may acquire transaction information related to target financial services with different acquisition frequencies on a specific day. Furthermore, the transaction information acquisition unit 301 may acquire transaction information related to target financial services with different acquisition frequencies at the specific timing on the specific day.
[0058] Next, the calculation unit 302 calculates at least one of the expenditure or the balance of the target user based on the transaction information acquired by the transaction information acquisition unit 301 (step ST102). When the calculation unit 302 has a function of calculating expenditures, it can calculate the expenditures of the target user for any period based on the transaction information of the target user. Furthermore, if the calculation unit 302 has a function for calculating a balance, it can calculate the balance of the target user at any point in time based on the transaction information of the target user.
[0059] Next, the display information output unit 303 outputs the display information in response to a request for display information of the personal account screen from the client terminal 2 used by the target user (step ST103). At this time, the display information output unit 303 outputs display information that enables display of information related to the transaction information acquired by the transaction information acquisition unit 301. For example, the display information output unit 303 generates, as display information, information that enables display of at least one of the transaction information of the target user related to the target financial service, the expenditure calculated using the transaction information, or the balance calculated using the transaction information. It should be noted that this display information may be information showing the individual account screen itself, or may be information that enables the individual account screen to be generated.
[0060] Fig. 7 is a diagram showing an example of an individual account screen. In the example of the individual account screen shown in Fig. 7, information showing the expenditures of the target user in the target period calculated by the calculation unit 302 is displayed. In this example, the target period is shown to be "January 1 to 16, 2024," and the budget for combined expenditures on multiple target financial services in January 2024 is 180,000, while as of January 16, the total expenditures on multiple target financial services is 82,000 yen, and the remaining budget is 98,000 yen.
[0061] Here, when using an API to obtain transaction information, the cost of obtaining information indicating bank account transactions is generally higher than the cost of obtaining information indicating payment transactions. Furthermore, the frequency of payment transactions is generally higher than the frequency of account transactions. Therefore, it is considered desirable to obtain information indicating payment transactions more frequently than information indicating account transactions. Therefore, in the information processing device according to the first embodiment, the frequency with which transaction information is acquired by transaction information acquisition unit 301 is changed depending on the type of target financial service. For example, when the target financial services are a payment service and a bank service, the frequency with which transaction information is acquired by transaction information acquisition unit 301 is set to be higher for the payment service than for the bank service. As a result, the information processing device according to the first embodiment is able to acquire transaction information relating to the target financial service at an acquisition frequency suited to the type of the target financial service.
[0062] For example, if the target financial service is a payment service, the transaction information acquisition unit 301 may acquire transaction information at a specific timing (for example, first thing in the morning) every day. Furthermore, for example, if the target financial service is a banking service, the transaction information acquisition unit 301 may acquire transaction information at a specific timing every week (e.g., first thing on Monday morning) and at a timing when a specific event occurs (e.g., payday, card withdrawal day, or rent withdrawal day). Note that the server 3 may set the timing when the specific event occurs based on a specification by the client terminal 2 used by the target user, or may automatically infer and set it from past transaction information.
[0063] In addition, with regard to the timing of acquiring transaction information, the transaction information acquisition unit 301 may acquire transaction information each time a payment transaction is executed for a specific payment service, and may acquire transaction information less frequently for payment services other than the specific payment service. For example, if the specific payment service is a service provided by the company itself, there is no need to consider the cost of acquiring information indicating a payment transaction. Therefore, for such a payment service, by acquiring transaction information every time a payment transaction is executed, it is possible to grasp the latest transaction information in real time. In addition, by setting a payment service among the target financial services for which one wishes to obtain transaction information as the specific payment service, it becomes possible to obtain transaction information for that payment service each time a payment transaction is executed, making it possible to obtain the latest transaction information in real time.
[0064] In addition, if the frequency of acquiring transaction information varies, some information may be up-to-date at a given time, while other information may not be. This can make it difficult to manage accounts appropriately. Therefore, in the transaction information acquisition unit 301 in embodiment 1, even if the frequency of acquiring transaction information related to the target financial service varies, it is possible to update all transaction information on a specific day or at a specific time on a specific day. For example, if the target financial services are banking services and payment services, and transaction information related to the banking services is acquired on the day when a specific event occurs, the transaction information acquisition unit 301 may acquire not only transaction information related to the banking services, but also transaction information related to other payment services on the day when the specific event occurs. As a result, in the information processing device of embodiment 1, although the acquisition frequency varies, at a certain point in time, transaction information regarding all target financial services is made the latest information, and it becomes possible to regularly obtain the latest transaction information for all target financial services.
[0065] As described above, according to this embodiment 1, the information processing device includes a transaction information acquisition unit 301 that acquires transaction information of the target user regarding a plurality of target financial services, and a calculation unit 302 that calculates at least one of the target user's expenditure or balance based on the transaction information acquired by the transaction information acquisition unit 301, and the frequency with which the transaction information is acquired by the transaction information acquisition unit 301 varies depending on the type of target financial service. This allows the information processing device according to the first embodiment to change the frequency of acquiring transaction information depending on the type of target financial service, and therefore allows the information processing device according to the first embodiment to efficiently or effectively acquire transaction information in the aggregation service.
[0066] Furthermore, according to this embodiment 1, the target financial services are banking services provided by banks and payment services provided by businesses other than banks, and the transaction information acquisition unit 301 acquires transaction information more frequently for payment services than for banking services. Furthermore, according to the first embodiment, the transaction information related to the payment service is information indicating a payment transaction and information indicating a deposit / withdrawal transaction, and the transaction information related to the banking service is information indicating an account transaction. As a result, in the information processing device according to embodiment 1, the acquisition cost of transaction information is high and the frequency of acquiring transaction information regarding banking services, which are traded infrequently, can be reduced relative to the frequency of acquiring transaction information regarding payment services.
[0067] Furthermore, according to this embodiment 1, if the payment service is a specific payment service, the transaction information acquisition unit 301 acquires transaction information when a payment transaction is executed, and if the payment service is a payment service other than the specific payment service, it acquires transaction information less frequently than when the payment service is the specific payment service. As a result, the information processing device according to the first embodiment can obtain the latest transaction information in real time for the target financial services, such as the company's own services or payment services for which transaction information is particularly desired.
[0068] Furthermore, according to the first embodiment, the transaction information acquisition unit 301 acquires all transaction information related to target financial services with different acquisition frequencies on a specific day. Furthermore, according to the first embodiment, the transaction information acquisition unit 301 acquires, at a specific timing, transaction information related to target financial services with different acquisition frequencies. As a result, in the information processing device of embodiment 1, by acquiring transaction information on a specific day or at a specific time on a specific day for target financial services that have different frequencies of acquiring transaction information, it becomes possible to regularly obtain the latest transaction information for each target financial service.
[0069] Furthermore, according to the first embodiment, the information processing program causes the computer to function as an information processing device. As a result, the information processing program according to the first embodiment makes it possible to change the frequency of acquiring transaction information depending on the type of target financial service, and therefore the information processing program according to the first embodiment makes it possible to efficiently or effectively acquire transaction information in the aggregation service.
[0070] Furthermore, according to this embodiment 1, the information processing method includes a step in which a transaction information acquisition unit 301 acquires transaction information of the target user regarding a plurality of target financial services, and a step in which a calculation unit 302 calculates at least one of the expenditure or balance of the target user based on the transaction information acquired by the transaction information acquisition unit 301, and the frequency of acquisition of transaction information by the transaction information acquisition unit 301 varies depending on the type of target financial service. As a result, the information processing method according to the first embodiment makes it possible to change the frequency of acquiring transaction information depending on the type of target financial service, and therefore, the information processing method according to the first embodiment makes it possible to efficiently or effectively acquire transaction information in the aggregation service.
[0071] Embodiment 2 In the first embodiment, the acquisition of transaction information related to a target financial service linked to an individual account is described. In contrast, in the second embodiment, the acquisition of transaction information related to a target financial service linked to a joint account is described.
[0072] Fig. 8 is a configuration example of an information processing system 1 according to embodiment 2. In the information processing system 1 according to embodiment 2 shown in Fig. 8, the client terminal 2 in the information processing system 1 according to embodiment 1 shown in Fig. 1 is changed to a plurality of client terminals 2. Fig. 9 is a configuration example of the server 3 according to the embodiment 2. In the server 3 according to the embodiment 2 shown in Fig. 9, the display information output unit 303 and the linkage information acquisition unit 304 of the server 3 according to the embodiment 1 shown in Fig. 2 are changed to a display information output unit 303b and a linkage information acquisition unit 304b. Fig. 10 is a configuration example of a client terminal 2 according to embodiment 2. In the client terminal 2 according to embodiment 2 shown in Fig. 10, the linkage information output unit 202, the display information acquisition unit 203, and the display control unit 204 of the client terminal 2 according to embodiment 1 shown in Fig. 3 are changed to a linkage information output unit 202b, a display information acquisition unit 203b, and a display control unit 204b. Other configuration examples of the information processing system 1, server 3, and client terminal 2 in embodiment 2 are similar to the configuration examples of the information processing system 1, server 3, and client terminal 2 in embodiment 1, and the same symbols are used and only the different parts will be described.
[0073] In the second embodiment, the target users are multiple target users linked to a joint account. A joint account is an account shared by multiple people and reflects the expenditures of each person. Examples of multiple target users linked to a joint account include, for example, a married couple, a couple, or business partners, but may also include people with other relationships. Also in the second embodiment, as in the first embodiment, the aggregation service provider is one of the providers that provides a payment service that enables payment transactions using a payment card or code payment, and in particular in the second embodiment, the payment service may provide individual accounts as well as the above-mentioned joint accounts. A joint account is opened, for example, with the consent of multiple target users who share one joint account. 8, target users A1 and A2 are shown as target users. Both target users A1 and A2 are target users linked to a joint account. In the example of FIG. 8, the client terminals 2 shown are a client terminal 2A1 used by a target user A1 and a client terminal 2A2 used by a target user A2.
[0074] The link information acquisition unit 304b acquires joint account link information used by the server 3 from the client terminal 2. The joint account link information is information indicating target financial services to be linked to the joint account. Here, the target financial services to be linked to the joint account are also referred to as linked financial services. As described above in the first embodiment, when a target user registers to use an aggregation service, a user ID is assigned to each target user. In the case where the target user A1 and the target user A2 have a joint account shared by both of them, for example, a user ID is assigned to each of the target users A1 and A2. The user IDs of both target users A1 and A2 and the target financial service IDs of each of a plurality of target financial services designated by either of the target users A1 and A2 as targets of the aggregation service including the joint account may be stored in association with each other in the storage unit 33. That is, in this case, the information indicating the target financial services linked to the joint account of the target user A1 and the target user A2 is the user IDs of both target users A1 and A2, the target financial service ID indicating the payment service (joint account) provided by the aggregation service provider, and the target financial service ID indicating the target financial service providing the payment service designated by both target users A1 and A2 other than the payment service, which are stored in association with each other in the storage unit 33.
[0075] Furthermore, the link information acquisition unit 304b may acquire, as the link information, information indicating the transaction information to be shared in addition to the linked financial service. Here, the transaction information to be shared is also referred to as shared transaction information. In this case, each of the target users A1 and A2 may select whether or not to share the transaction information after confirming the contents of the transaction information. When each of the target users A1 and A2 selects the transaction information to be shared one by one, for example, each of the target users A1 and A2 can display the transaction information of the payment using the payment service of each target financial service acquired by the transaction information acquisition unit 301 on the display unit 24 of the client terminal 2A1 or 2A2 used by the target user, and select which transaction information to share. Here, the transaction information includes a corresponding user ID depending on whether the transaction was made by either of the target users A1 and A2. The client terminal 2A1 and 2A2 transmit information indicating the selected transaction information to the server 3, and the server 3 stores the information in the storage unit 33 in association with the user IDs of both target users A1 and A2 and the target financial service ID indicating the payment service (joint account) provided by the aggregation service provider. Such conditions as to which transaction information is shared between the two target users A1 and A2 may be set in advance by either the target user A1 or A2, and may be associated with the user IDs of the two target users A1 and A2 and stored in the storage unit 33. As described above, the conditions may be specified, for example, by the target user A1 operating the client terminal 2A1 or by the target user A2 operating the client terminal 2A2.
[0076] Furthermore, the link information acquisition unit 304b may acquire, as the link information, information indicating a category of transaction information to be shared in addition to the linked financial service. Here, the category of transaction information to be shared is also referred to as a shared category. The conditions for which transaction information is shared between the two target users A1 and A2 can be set by specifying the category of the transaction information to be shared. For example, the category can be set to the category of the store where the payment was made using the payment service of the target financial service, or the category of the product or service. Examples of store categories include restaurants, convenience stores, drug stores, bookstores, etc. Also, examples of product categories include food, medicine, books, etc., and examples of service categories include rent, hospitals, training gyms, dry cleaning, movies, etc. In this case, each of the target users A1 and A2 may select the category of the transaction information from a list of categories displayed on the display unit 24 of the client terminal 2A1 and 2A2 used by the target user, or may select whether or not to share the transaction information from the category of the transaction information displayed on the display unit 24. In the latter case, the category of the store, product, or service in which the transaction was made is assigned to the transaction information and can be displayed on the display unit 24. When each of the target users A1 and A2 selects the category of the transaction information to be shared, for example, each of the target users A1 and A2 can display the transaction information acquired by the transaction information acquisition unit 301 on the display unit 24 of the client terminal 2A1 and 2A2 used by the target user, and select which category of transaction information to share. The client terminal 2A1 and 2A2 transmit information indicating the selected category of transaction information to the server 3, and the server 3 stores the information in the storage unit 33 in association with the user IDs of both target users A1 and A2 and the target financial service ID indicating the settlement service (joint account) provided by the aggregation service provider.
[0077] The conditions for which transaction information is shared between the two target users A1 and A2 may be set other than for each transaction information or for the category of transaction information. For example, the conditions may be set when the expenditure amount of one transaction exceeds a preset amount, when the expenditure in a certain period exceeds a preset amount, when a transaction is performed on a specific day of the week, when a charge is made that exceeds a preset amount, etc.
[0078] In addition, the linking information acquisition unit 304b may have a function of acquiring personal account linking information that the linking information acquisition unit 304 in the first embodiment has, in addition to the function of acquiring the joint account linking information.
[0079] Fig. 11 is a diagram for explaining the linkage of financial services to a joint account. In the example of Fig. 11, a business providing a service using server 3 is a business providing a payment service. In the example of Fig. 10, two target financial services b3 and b4 are linked to a joint account a2 of a target user of this payment service. In the example of FIG. 11, in addition to the linkage of the target financial service to the joint account a2, the target financial service is also linked to the personal account a1.
[0080] The display information output unit 303b outputs the display information in response to a request for display information of the joint account screen from the client terminal 2 used by the target user. At this time, based on the linkage information acquired by the linkage information acquisition unit 304b, the display information output unit 303b outputs display information that enables display of information on the target user's transaction information regarding the linked financial service, among the transaction information acquired by the transaction information acquisition unit 301. For example, the display information output unit 303b generates, as display information, information that enables display of at least one of the target user's transaction information regarding the linked financial service, expenditure calculated using the transaction information, or balance calculated using the transaction information. In addition, this display information may be information that shows the joint account screen itself, or may be information that enables the joint account screen to be generated.
[0081] In addition, when the linked information acquisition unit 304b acquires linked information indicating linked financial services and shared transaction information, the display information output unit 303b outputs display information based on this linked information that enables display of information regarding the target user's shared transaction information regarding linked financial services, among the transaction information acquired by the transaction information acquisition unit 301.
[0082] In addition, when the linked information acquisition unit 304b acquires linked information indicating an linked financial service and a shared category, the display information output unit 303b outputs display information based on this linked information that enables display of information regarding the transaction information of the target user's shared category related to the linked financial service, among the transaction information acquired by the transaction information acquisition unit 301.
[0083] In addition, the display information output unit 303b may have a function of outputting display information for the individual account screen, in addition to the function of outputting display information for the joint account screen described above, which the display information output unit 303 in embodiment 1 has.
[0084] The linking information output unit 202b outputs the joint account linking information to the server 3 based on the operation information acquired by the operation information acquisition unit 201. In addition to the function of outputting the above-mentioned joint account linkage information, the linkage information output unit 202b may have a function of outputting the personal account linkage information that the linkage information output unit 202 in the first embodiment has.
[0085] The display information acquisition unit 203 b makes a request to acquire display information for the joint account screen to the server 3 based on the operation information acquired by the operation information acquisition unit 201 , and acquires the display information from the server 3 . In addition, the display information acquisition unit 203b may have a function of acquiring display information for the personal account screen that the display information acquisition unit 203 in embodiment 1 has, in addition to the function of acquiring display information for the joint account screen described above.
[0086] The display control unit 204b displays a joint account screen on the display unit 24 based on the operation information acquired by the operation information acquisition unit 201 and the display information acquired by the display information acquisition unit 203b. When the display information is information indicating the joint account screen itself, the display control unit 204b displays the joint account screen indicated by this information on the display unit 24. When the display information is information that enables a joint account screen to be generated, the display control unit 204b generates a joint account screen from this information and displays the generated joint account screen on the display unit 24. The joint account screen displayed by the display control unit 204b displays at least one of the following information: transaction information of the linked user regarding the linked financial service, expenditures calculated using the transaction information, or balances calculated using the transaction information.
[0087] In addition to the function of displaying the joint account screen, the display control unit 204b may have a function of displaying an individual account screen that the display control unit 204 in the first embodiment has. For example, a selection button for switching the screen display to the personal account screen of the target user A1 is displayed on the joint account screen displayed on the display unit 24 of the client terminal 2A1 used by the target user A1. The target user A1 can switch the display screen to the personal account screen by operating this selection button. Similarly, a selection button for switching the screen display to the joint account screen is displayed on the personal account screen of the target user A1 displayed on the display unit 24 of the client terminal 2A1. The target user A1 can switch the display screen to the joint account screen by operating this selection button. Similarly, the client terminal 2A2 used by the target user A2 is also capable of switching between the joint account screen and the personal account screen of the target user A2.
[0088] In this way, in server 3 of embodiment 2, when a target user performs an operation to link a target financial service to a joint account, the target user's transaction information regarding this target financial service is shared with other target users linked to the joint account. In addition, in the server 3 of embodiment 2, the target user's transaction information regarding target financial services that are not linked to a joint account, i.e., target financial services that are linked to a personal account, is not shared with other target users linked to the joint account.
[0089] Additionally, the linked information acquisition unit 304b may also acquire, from among the transaction information related to the linked financial service, information indicating the transaction information to be shared or its category. In this case, the display information output unit 303b outputs display information that enables display of information regarding the linked user's shared transaction information related to the linked financial service or transaction information of a shared category from the transaction information acquired by the transaction information acquisition unit 301. As a result, in the information processing device of embodiment 2, it is possible to share only a portion of the transaction information related to the linked financial services linked to the joint account rather than sharing all of the transaction information, enabling more detailed responses.
[0090] As described above, according to this embodiment 2, the information processing device is equipped with an association information acquisition unit 304b that acquires association information indicating an associated financial service, which is a target financial service linked to the joint account, and a display information output unit 303b that outputs display information that enables display of information regarding the target user's transaction information related to the associated financial service, among the transaction information acquired by the transaction information acquisition unit 301, based on the association information acquired by the association information acquisition unit 304b, in response to a request from the target user linked to the joint account. As a result, in the information processing device of embodiment 2, when a target user links a target financial service to a joint account, other target users linked to the joint account can also obtain the target user's transaction information regarding the linked target financial service.
[0091] Furthermore, according to this embodiment 2, the linked information acquisition unit 304b acquires linked information indicating the linked financial service and the shared transaction information, which is the shared transaction information, and the display information output unit 303b outputs display information that enables display of information regarding the target user's shared transaction information regarding the linked financial service, which is included in the transaction information acquired by the transaction information acquisition unit 301, based on the linked information acquired by the linked information acquisition unit 304b, in response to a request from the target user linked to the joint account. Furthermore, according to this embodiment 2, the linked information acquisition unit 304b acquires linked information indicating the linked financial service and the shared category, which is the category of the transaction information to be shared, and the display information output unit 303b, in response to a request from the target user linked to the joint account, outputs display information that enables display of information regarding the transaction information of the target user in the shared category related to the linked financial service, among the transaction information acquired by the transaction information acquisition unit 301, based on the linked information acquired by the linked information acquisition unit 304b. As a result, the information processing device according to the second embodiment is able to share only a portion of the transaction information relating to linked financial services linked to a joint account, enabling more detailed responses.
[0092] Embodiment 3 In the third embodiment, a case will be described in which transaction information regarding a target financial service is acquired in response to a predetermined trigger.
[0093] Fig. 12 is a configuration example of the server 3 according to the embodiment 3. In the server 3 according to the embodiment 3 shown in Fig. 12, the transaction information acquisition unit 301 is changed to a transaction information acquisition unit 301c, which is different from the server 3 according to the embodiment 1 shown in Fig. 1. Other configuration examples of the information processing system 1, server 3, and client terminal 2 in embodiment 3 are similar to the configuration examples of the information processing system 1, server 3, and client terminal 2 in embodiment 1, and the same symbols are used and only the different parts will be described.
[0094] The transaction information acquisition unit 301c has the function of acquiring transaction information related to a target financial service in response to a predetermined trigger, in addition to the function of the transaction information acquisition unit 301 in the first embodiment. That is, while the transaction information acquisition unit 301c acquires transaction information at an acquisition frequency according to the type of target financial service, if a predetermined trigger occurs, the transaction information acquisition unit 301c acquires transaction information regardless of the type of target financial service.
[0095] At this time, the transaction information acquisition unit 301c may acquire transaction information related to all of the target financial services or may acquire transaction information related to some of the target financial services in response to the above-mentioned trigger. For example, if the transaction information acquisition unit 301c is set to acquire transaction information when a payment transaction is executed for a specific payment service, the transaction information for this payment service is always updated to the latest state, so there is no need to acquire transaction information for this payment service in response to the trigger. Therefore, in such a case, the transaction information acquisition unit 301c may acquire transaction information for target financial services other than the specific payment service in response to the trigger.
[0096] For example, when the transaction information acquisition unit 301c acquires transaction information related to all of the target financial services in response to the trigger, information indicating the trigger is stored in the storage unit 33. Also, when the transaction information acquisition unit 301c acquires transaction information related to some of the target financial services in response to the trigger, information indicating the trigger is stored in the storage unit 33 in association with the target financial service IDs of the some of the target financial services. By storing the above-mentioned information in the memory unit 33, the transaction information acquisition unit 301c identifies a trigger and identifies the target financial service for which transaction information should be acquired in response to the occurrence of the trigger, and acquires the transaction information when the above-mentioned trigger occurs.
[0097] Also, for example, the trigger for the transaction information acquisition unit 301c to acquire transaction information may be a timing based on the execution of a payment transaction in the target financial service. Examples of the timing based on a payment transaction include the timing when the first payment transaction is executed in a day, or the timing when a payment transaction is executed a predetermined number of times.
[0098] Also, for example, the trigger for the transaction information acquisition unit 301c to acquire transaction information may be the timing when a client terminal application used by the target user is started. In this case, the server 3 includes an activation detection unit (not shown) that detects activation of a client terminal application used by the target user. Then, the transaction information acquisition unit 301c acquires transaction information related to all target financial services at the timing when the activation is detected by the activation detection unit.
[0099] In the above description, the target user's actions that become triggers are when the target user makes a payment and when the target user starts a client terminal application. However, the target user's action that serves as a trigger is not limited to this, and the trigger may be, for example, the timing when the target user performs a predetermined operation, such as when the target user selects an update button.
[0100] Also, for example, the trigger for the transaction information acquisition unit 301c to acquire transaction information may be the timing at which the server 3 performs a determination process based on the acquisition result by the transaction information acquisition unit 301c or the calculation result by the calculation unit 302. In this case, the server 3 includes a determination unit (not shown) that performs a determination process based on the transaction information acquired by the transaction information acquisition unit 301c in response to the trigger, or based on a calculation result by the calculation unit 302 using the transaction information acquired by the transaction information acquisition unit 301c in response to the trigger. That is, the determination unit performs the determination process based on the transaction information updated to the latest state at the timing of performing the determination process, or based on the calculation result by the calculation unit 302 using the transaction information.
[0101] An example of the determination unit is an overuse determination unit. The overuse determination unit determines that the target user has overused when the target user's expenditure is equal to or greater than the expenditure threshold or when the target user's balance is equal to or less than the balance threshold based on the calculation result by the calculation unit 302. An example of a condition for the overuse determination unit to make a determination is once a month. The condition for the overuse determination unit to make a determination may be set automatically by the server 3, or may be set by the server 3 in response to a specification by the client terminal 2 used by the target user. Further, for example, the determination unit may be a deposit necessity determination unit. The deposit necessity determination unit determines that a deposit is necessary when the balance of the target user is equal to or less than the deposit threshold based on the calculation result by the calculation unit 302. In addition, for example, the determination unit may be a fraudulent use determination unit that determines that there is a possibility of fraudulent use when the transaction amount indicated in the transaction information of the target user is equal to or greater than the upper limit threshold based on the acquisition result by the transaction information acquisition unit 301c.
[0102] In this way, the server 3 according to the third embodiment makes it possible to update transaction information regarding a target financial service in response to a trigger such as a predetermined action by the target user, regardless of the type of target financial service. As a result, the server 3 according to the third embodiment is able to ascertain the latest transaction information for each target financial service at least at the timing of the above-mentioned trigger.
[0103] In the above description, the case has been described in which the transaction information acquisition unit 301 in the server 3 according to the first embodiment has been changed to a transaction information acquisition unit 301c. However, the present invention is not limited to this, and in the server 3 according to the second embodiment, the transaction information acquisition unit 301 may be changed to a transaction information acquisition unit 301c, and the same effects as those described above can be obtained.
[0104] As described above, according to the third embodiment, the transaction information acquisition unit 301c of the information processing device acquires transaction information related to the target financial service in response to a predetermined trigger. As a result, in the information processing device according to the third embodiment, by acquiring transaction information between target financial services at a certain timing, it becomes easier to grasp transaction information regarding each target financial service.
[0105] Furthermore, according to the third embodiment, the trigger is the timing based on the execution of a payment transaction in the target financial service. Furthermore, according to the third embodiment, a start-up detection unit that detects the start-up of an application used by the target user is provided, and the trigger is the timing at which the start-up is detected by the start-up detection unit. Furthermore, according to the third embodiment, a determination unit is provided that performs a determination process based on transaction information acquired by the transaction information acquisition unit 301c in response to a trigger, or based on a calculation result by the calculation unit 302 using the transaction information acquired by the transaction information acquisition unit 301c in response to a trigger, and the trigger is the timing at which a condition for causing the determination unit to execute the determination process is satisfied. Furthermore, according to the third embodiment, the determination unit determines that the target user is overspending when the expenditure of the target user is equal to or greater than the expenditure threshold or when the balance of the target user is equal to or less than the balance threshold, based on the calculation result by the calculation unit 302. As a result, the information processing device according to the third embodiment can acquire each piece of transaction information at an appropriate timing between the target financial services.
[0106] It should be noted that the embodiments may be freely combined, or any of the components in each embodiment may be modified, or any of the components in each embodiment may be omitted. [Explanation of symbols]
[0107] 1 information processing system, 2 client terminal, 3 server (information processing device), 4 store terminal, 5 external server, 21 communication unit, 22 calculation unit, 23 operation unit, 24 display unit, 25 memory unit, 31 communication unit, 32 calculation unit, 33 memory unit, 100 communication interface, 101 input / output interface, 102 processor, 103 memory, 201 operation information acquisition unit, 202, 202b linkage information output unit, 203, 203b display information acquisition unit, 204, 204b display control unit, 301, 301c transaction information acquisition unit, 302 calculation unit, 303, 303b display information output unit, 304, 304b linkage information acquisition unit.
Claims
1. a transaction information acquisition unit that acquires transaction information of a target user regarding a plurality of target financial services; a calculation unit that calculates at least one of an expenditure or a balance of the target user based on the transaction information acquired by the transaction information acquisition unit, the frequency with which the transaction information is acquired by the transaction information acquisition unit varies depending on the type of the target financial service; The transaction information acquisition unit specifies the acquisition frequency of the transaction information based on an ID unique to the target financial service or an ID capable of distinguishing a type of the target financial service and information indicating the acquisition frequency, the information being stored in a storage unit that stores information indicating the acquisition frequency of transaction information by the transaction information acquisition unit in association with an ID unique to the target financial service or an ID capable of distinguishing a type of the target financial service.
23. An information processing apparatus comprising:
2. The target financial services are banking services provided by banks and payment services provided by businesses other than banks, The frequency with which the transaction information is acquired by the transaction information acquisition unit is higher for the payment service than for the bank service.
2. The information processing apparatus according to claim 1,
3. The transaction information regarding the payment service is information indicating a payment transaction and information indicating a deposit / withdrawal transaction, The transaction information regarding the bank service is information indicating an account transaction.
3. The information processing apparatus according to claim 2.
4. The transaction information acquisition unit acquires transaction information when a payment transaction is executed when the payment service is a specific payment service, and acquires transaction information less frequently when the payment service is a payment service other than the specific payment service than when the payment service is the specific payment service.
3. The information processing apparatus according to claim 2.
5. The transaction information acquisition unit acquires, on a specific day, transaction information related to the target financial services that are acquired at different frequencies.
2. The information processing apparatus according to claim 1,
6. The transaction information acquisition unit acquires transaction information related to the target financial services having different acquisition frequencies at a specific timing.
6. The information processing apparatus according to claim 5,
7. the target user is a plurality of target users linked to a joint account; an association information acquisition unit that acquires association information indicating an associated financial service that is the target financial service associated with the joint account; a display information output unit that outputs display information that enables display of information regarding the target user's transaction information related to the linked financial service, among the transaction information acquired by the transaction information acquisition unit, based on the linkage information acquired by the linkage information acquisition unit, in response to a request for acquisition of display information for a joint account screen from the target user linked to the joint account.
2. The information processing apparatus according to claim 1,
8. The link information acquisition unit acquires the link information indicating the linked financial service and shared transaction information which is transaction information to be shared, The display information output unit outputs display information that enables display of information regarding the shared transaction information of the target user related to the linked financial service, among the transaction information acquired by the transaction information acquisition unit, based on the linkage information acquired by the linkage information acquisition unit, in response to a request from the target user linked to the joint account.
8. The information processing apparatus according to claim 7,
9. the link information acquisition unit acquires the link information indicating the linked financial service and a shared category which is a category of transaction information to be shared; The display information output unit outputs display information that enables display of information on transaction information of the target user in the shared category related to the linked financial service among the transaction information acquired by the transaction information acquisition unit, based on the linkage information acquired by the linkage information acquisition unit, in response to a request from the target user linked to the joint account.
8. The information processing apparatus according to claim 7,
10. The transaction information acquisition unit acquires transaction information related to the target financial service in response to a predetermined trigger.
2. The information processing apparatus according to claim 1,
11. The trigger is based on the timing of execution of a payment transaction in the target financial service.
11. The information processing apparatus according to claim 10.
12. a startup detection unit that detects startup of an application used by the target user; The trigger is a timing at which the start-up is detected by the start-up detection unit.
11. The information processing apparatus according to claim 10.
13. a determination unit that performs a determination process based on transaction information acquired by the transaction information acquisition unit in response to the trigger, or based on a calculation result by the calculation unit using the transaction information acquired by the transaction information acquisition unit in response to the trigger, The trigger is a timing at which a condition for causing the determination unit to execute a determination process is satisfied.
11. The information processing apparatus according to claim 10.
14. The determination unit determines that the target user is overspending when the expenditure of the target user is equal to or greater than an expenditure threshold or when the user's balance is equal to or less than a balance threshold based on a calculation result by the calculation unit.
14. The information processing apparatus according to claim 13,
15. An information processing program for causing a computer to function as the information processing device according to any one of claims 1 to 14.
16. A transaction information acquisition unit acquires transaction information of a target user regarding a plurality of target financial services; a calculation unit calculating at least one of an expenditure or a balance of the target user based on the transaction information acquired by the transaction information acquisition unit; the frequency with which the transaction information is acquired by the transaction information acquisition unit varies depending on the type of the target financial service; The transaction information acquisition unit specifies the acquisition frequency of the transaction information based on an ID unique to the target financial service or an ID capable of distinguishing a type of the target financial service and information indicating the acquisition frequency, the information being stored in a storage unit that stores information indicating the acquisition frequency of transaction information by the transaction information acquisition unit in association with an ID unique to the target financial service or an ID capable of distinguishing a type of the target financial service.
23. An information processing method comprising:
Citation Information
Patent Citations
Account aggregation system and account aggregation method
JP2018077730A
Voucher processing system and voucher processing method
JP2018116602A
Information processing device, information processing method, and program
JP6831165B1
