Information processing system, information processing method and computer program

Abstract

To achieve a mechanism for enabling a user to easily change user's setting information to each of a plurality of organizations.SOLUTION: An impact PF 22 includes a first storage part for storing a plurality of user's IDs determined by a system of a plurality of organizations, and a second storage part for storing user's setting information to each of the plurality of organizations. The impact PF 22 associates a common ID allocated to the user with a plurality of IDs of the user stored in the first storage part. The impact PF 22 displays a screen which is browsable by using a common ID and is a portal screen being a screen showing the user's setting information to each of the plurality of organizations in a customer terminal 12. The impact PF 22 reflects change in the second storage part in the case that the user's setting information to a certain organization is changed on the portal screen.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to data processing technology, and more particularly to an information processing system, an information processing method, and a computer program. [Background technology]

[0002] The following Patent Document 1 proposes a specific fund designated allocation system in which an investment trust for donations is set up in advance, customers who wish to make donations purchase the investment trust, and the investment gains from the investment trust are donated to a specific donation recipient. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2009-48241 A Summary of the Invention [Problem to be solved by the invention]

[0004] In order to promote donations based on dividends, etc., it is desirable for a donor to be able to easily change the donation mode that the user has set for multiple financial institutions, etc. One objective of the present disclosure is to realize a mechanism that allows the user to easily change the user's setting information for each of multiple organizations. [Means for solving the problem]

[0005] In order to solve the above problems, an information processing system of an embodiment of the present disclosure includes a first memory unit that stores multiple IDs of a user defined in the systems of multiple organizations, a second memory unit that stores setting information of the user for each of the multiple organizations, an execution unit that executes processing for each organization's system based on the user's setting information stored in the second memory unit using the user's ID defined in the system of each organization, an association unit that associates a common ID assigned to the user with the user's multiple IDs stored in the first memory unit, a presentation unit that presents to the user a screen that can be viewed using the common ID and shows the user's setting information for each of the multiple organizations, and a change unit that reflects the change in the second memory unit when the user's setting information for a certain organization is changed on the screen.

[0006] Another aspect of the present disclosure is an information processing method, in which a computer including a first storage unit that stores multiple IDs of a user defined in the systems of multiple organizations and a second storage unit that stores user setting information for each of the multiple organizations executes processing for each organization's system based on the user setting information stored in the second storage unit using the user ID defined in the system of each organization, associates a common ID assigned to the user with the multiple IDs of the user stored in the first storage unit, presents to the user a screen that can be viewed using the common ID and shows the user's setting information for each of the multiple organizations, and when the user's setting information for a certain organization is changed on the screen, reflects the change in the second storage unit.

[0007] Any combination of the above components, and conversion of the present disclosure into an apparatus, a computer program, a recording medium storing a computer program, and the like, are also valid aspects of the present disclosure. Effect of the Invention

[0008] According to the technology disclosed herein, a mechanism can be realized that allows a user to easily change the user's setting information for each of multiple organizations. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating a configuration of an information processing system according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing functional blocks of the impact PF in FIG. 1. [Diagram 3] FIG. 11 is a diagram showing an example of customer information. [Figure 4] FIG. 13 is a diagram showing an example of donation application information. [Diagram 5] 13 is a flowchart showing the operation of the impact PF. [Figure 6] 13 is a flowchart showing the operation of the impact PF. [Figure 7] FIG. 13 is a diagram showing an example of an integration target ID designation screen. [Figure 8] FIG. 13 is a diagram showing an example in which a common ID of a target customer is associated with a plurality of individual IDs of the target customer. [Figure 9] FIG. 13 is a diagram illustrating an example of a portal screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] In the embodiment, a technology is proposed that supports a user to easily change the user's setting information for each of a plurality of organizations. Specifically, an Impact Platform (hereinafter also referred to as "Impact PF") is proposed as a system in which the technology is introduced. Impact PF supports donations funded by users' assets managed by a plurality of business companies. Donations are assumed to be made to general foundations, public interest foundations, nonprofit organizations (NPOs), etc., that aim to solve environmental problems and social issues. In the embodiment, the user is a customer of a business company such as a financial institution.

[0011] 1 shows the configuration of a communication system 10 according to an embodiment. The communication system 10 includes a customer terminal 12, a securities company device 14, a securities back-office system 16, a point program operating company device 18, a bank device 20, and an impact PF 22. These devices and computers that constitute the system are connected to each other via a communication network including a LAN, a WAN, the Internet, and the like.

[0012] The securities company device 14 is an information processing device that supports the operations of a securities company (XX Securities in this embodiment). The securities back-office system 16 is an information processing system that provides an information processing service that supports securities affairs to the securities company. The securities back-office system 16 supports the orders and contracts of financial products, balance management, customer management, settlement operations, custody operations, accounting operations, etc. at the securities company. For example, the securities back-office system 16 manages financial products held by the securities company's customers, and also manages the balances of the customers' accounts. The securities back-office system 16 may be realized by a single computer, or may be realized by multiple computers working together.

[0013] The point program operating company device 18 is an information processing device of a company (YY Point in this embodiment) that operates the point program. The point program can also be considered a loyalty program. The point program operating company device 18 manages the customer's point balance. The bank device 20 is an information processing device that supports the operations of a bank (ZZ Bank in this embodiment). For example, the bank device 20 manages financial products held by customers and also manages the balance of customers' accounts.

[0014] The customer terminal 12 is an information processing device operated by a customer of a securities company, a point program operating company, or a bank. The customer terminal 12 may be a laptop, a tablet terminal, or a smartphone. The customer terminal 12 may also be a user terminal operated by a user of the Impact PF22.

[0015] Note that multiple customers, multiple securities companies, multiple point program operating companies, and multiple banks may participate in communication system 10. That is, communication system 10 may include multiple customer terminals 12, multiple securities company devices 14, multiple point program operating company devices 18, and multiple bank devices 20. Securities back-office system 16 may be connected to multiple securities company devices 14 and support the operations of multiple securities companies.

[0016] Impact PF22 is an information processing system that serves as a donation platform and supports donations to public interest foundations and general foundations. Specifically, Impact PF22 executes information processing for donating at least a portion of dividends, etc., of financial products held by a customer to public interest foundations and general foundations, etc., based on the designation by the customer. Financial products held by a customer include securities, such as stocks, investment trusts, and bonds. Dividends, etc. can also be considered as profits obtained by a customer by holding financial products. For example, dividends, etc. include dividends on stocks, distributions from investment trusts, and interest on bonds. Impact PF22 may be realized by one computer, or by multiple computers working together.

[0017] In the communication system 10 of the embodiment, initially, a donation application is made from B (Impact PF 22) to B (each business company) to C (customer terminal 12), in other words, a donation application is made via each business. In the communication system 10, with the consent of the customer, the donation application is switched to B (Impact PF 22) to C (customer terminal 12).

[0018] Fig. 2 is a block diagram showing the functional blocks of Impact PF22 in Fig. 1. Each block shown in the block diagram in this specification can be realized in terms of hardware by elements such as a computer processor, CPU, and memory, electronic circuits, and mechanical devices, and in terms of software by a computer program, etc., but here, the functional blocks realized by the cooperation of these are depicted. Therefore, it will be understood by those skilled in the art that these functional blocks can be realized in various ways by combining hardware and software.

[0019] Impact PF 22 includes a processing unit 30, a memory unit 32, and a communication unit 34. Processing unit 30 executes various data processing. Processing unit 30 may be realized by a CPU of a computer constituting Impact PF 22. Memory unit 32 stores data referenced or updated by processing unit 30. Memory unit 32 may be realized by storage or memory of a computer constituting Impact PF 22. Communication unit 34 communicates with an external device according to a predetermined communication protocol. Processing unit 30 transmits and receives data to and from customer terminal 12, securities back-office system 16, point program operating company device 18, and bank device 20 via communication unit 34.

[0020] The storage unit 32 includes a customer information storage unit 40, a donation application information storage unit 42, and a donation history storage unit 44. The customer information storage unit 40 serves as a first storage unit and stores multiple IDs of users defined by multiple organizations. The donation application information storage unit 42 serves as a second storage unit and stores user setting information for each of the multiple organizations. The customer information storage unit 40 and the donation application information storage unit 42 may be implemented as a single table.

[0021] The customer information storage unit 40 stores basic information on customers (hereinafter also referred to as "customer information"). FIG. 3 shows an example of customer information. The customer information includes business company information, individual ID, name, date of birth, and common ID. The business company is the customer's assets that are the source of donations, in other words, the company that manages the customer's assets for which donations are set. Business companies include, for example, financial institutions such as securities companies and banks, as well as point program management companies. The customer's assets include, for example, financial products purchased by the customer and points held by the customer.

[0022] An individual ID is a customer ID defined by the system or device of each business company, and is different for each business company and each customer. For example, individual ID "123" is a customer ID defined by the securities company device 14 of XX Securities. Individual ID "456" is a customer ID defined by the point program operating company device 18 of YY Points. Individual ID "789" is a customer ID defined by the bank device 20 of ZZ Bank. A common ID is an ID that ties together multiple individual IDs that multiple business companies have assigned to customers, and is a common ID across multiple business companies. In an embodiment, Impact PF22 assigns a common ID to a customer based on the customer's consent.

[0023] Returning to Fig. 2, donation application information storage unit 42 stores donation application information as setting information of the customer for each business company. Fig. 4 shows an example of donation application information. The donation application information is information indicating the form of donation set by the customer. The donation application information in the embodiment includes information of the business company that manages the assets of the customer for whom the donation has been set, an individual ID, a donation destination, and a donation amount.

[0024] Returning to Fig. 2, the donation history storage unit 44 stores donation history information, which is information showing the history of donations to public interest foundations, general foundations, etc., in other words, information showing the actual donation results. The donation history information may include the donation date and time, an individual ID (e.g., ID=123), the business company that made the donation (e.g., XX Securities), the name of the organization that received the donation (e.g., XX Foundation), and the donation amount (e.g., 1,000 yen).

[0025] The processing unit 30 includes a donation application receiving unit 50, an individual ID obtaining unit 52, a donation mode determining unit 54, a donation executing unit 56, a receipt issuing unit 58, a consent receiving unit 60, an ID integrating unit 62, an authentication unit 64, a portal screen providing unit 66, and a change unit 68.

[0026] The functions of the multiple functional blocks provided in the processing unit 30 may be implemented in a computer program (also referred to herein as a "donation support program"). The donation support program may be stored in a recording medium, or may be installed in the computer of Impact PF22 via a recording medium. The donation support program may also be downloaded via a communication network and installed in the computer of Impact PF22. The processor (CPU, etc.) of the computer of Impact PF22 may fulfill the functions of the multiple functional blocks by reading the donation support program into main memory and executing it.

[0027] The donation application reception unit 50 receives donation application information entered by the customer to each business company and transmitted from the securities back-office system 16, the point program operating company device 18, or the bank device 20. The donation application reception unit 50 stores the received donation application information in the donation application information storage unit 42.

[0028] Individual ID acquisition unit 52 acquires customer information associated with the individual ID indicated by the donation application information from the device of the business company indicated by the donation application information. Individual ID acquisition unit 52 stores the customer information associated with the individual ID indicated by the donation application information in customer information storage unit 40.

[0029] When donation mode determination unit 54 detects that the donation timing of a certain customer has arrived, it determines the donation mode of the customer by referring to the donation application information of the customer stored in donation application information storage unit 42. A customer for whom a donation-related process is executed is also referred to as a "target customer" hereinafter.

[0030] The donation execution unit 56 executes processing related to donations based on the donation application information of the target customer stored in the donation application information storage unit 42, and also executes processing for the system of each business company, using the individual ID indicated by the donation application information. In the embodiment, the donation execution unit 56 executes the donation processing in the manner determined by the donation manner determination unit 54. For example, the donation execution unit 56 may execute processing to transfer the donation amount from the account of the target customer to the account of the donation recipient foundation, in cooperation with a device of the business company indicated in the donation application information.

[0031] 4, donation application information storage unit 42 stores donation application information that specifies the form of donation to each of a plurality of business companies using assets held by the customer as the source of the donation. Donation execution unit 56 executes processing for the system of each business company to make a donation to each of a plurality of business companies using assets held by the customer as the source of the donation in the form specified by the donation application information.

[0032] The receipt issuing unit 58 generates a receipt addressed to the customer and transmits receipt data to the customer terminal 12. The receipt may include, for example, the name of the organization to which the donation was made, the donation amount, and the date of the donation.

[0033] The consent receiving unit 60 receives information indicating that the customer has agreed to the integration of multiple individual IDs of the user at multiple business companies (hereinafter, also referred to as "consent information"). The consent receiving unit 60 may receive consent information transmitted from the system of the business company or the customer terminal 12.

[0034] The ID integration unit 62 assigns a common ID to the customer to be integrated, on condition that the consent information has been accepted by the consent acceptance unit 60. The common ID is an ID common to a plurality of business companies and is a unique ID for each customer. As a variant, the common ID may be determined by the customer, and the common ID determined by the customer may be notified to the Impact PF 22 from the customer terminal 12.

[0035] Furthermore, on the condition that the consent information is accepted by the consent accepting unit 60, the ID integrating unit 62 stores the common ID assigned to the customer in the customer information storage unit 40. The ID integrating unit 62, as an associating unit, associates the common ID with multiple individual IDs of the customer stored in advance in the customer information storage unit 40.

[0036] The authentication unit 64 executes an authentication process using the common ID. The ID integration unit 62 may issue a password corresponding to the common ID of the customer. The authentication unit 64 may authenticate the customer who has requested a portal screen described below using the common ID and the password.

[0037] The portal screen providing unit 66, as a presentation unit, presents to the customer a screen (hereinafter also referred to as a "portal screen") that can be viewed using a common ID and that shows the customer's setting information for each of a plurality of business companies. The portal screen in the embodiment is a screen that displays an aggregated display of the customer's setting information managed by each of a plurality of business companies side by side. The customer's setting information in the embodiment is donation application information. The donation application information includes information indicating the donation type, such as the donation amount. When the authentication unit 64 successfully authenticates the customer who requested the portal screen, the portal screen providing unit 66 transmits data of a portal screen that shows one or more pieces of donation application information associated with the customer to the customer terminal 12.

[0038] When a customer's setting information for a certain business company is changed on the portal screen, change unit 68 reflects the change in donation application information storage unit 42. In an embodiment, change unit 68 updates the donation application information stored in donation application information storage unit 42 so that the donation mode changed on the portal screen is reflected in the donation application information.

[0039] The operation of the communication system 10 having the above configuration will now be described. In this case, the customer uses XX Securities, YY Points, and ZZ Bank. In response to the customer's operation, customer terminal 12 transmits donation application information to securities company device 14. The donation application information is entered into Impact PF 22 via securities company device 14 and securities back-office system 16. The donation application information entered into Impact PF 22 includes the business company name, individual ID, donation destination, and donation amount, as shown in FIG. 4.

[0040] 5 is a flowchart showing the operation of Impact PF. The donation application receiving unit 50 of Impact PF 22 receives donation application information (e.g., individual ID=123) transmitted from securities back-office system 16 (Y of S10). The donation application receiving unit 50 stores the donation application information in donation application information storage unit 42 (S12). The individual ID obtaining unit 52 of Impact PF 22 obtains customer information of XX Securities, which is linked to the individual ID (e.g., individual ID=123) indicated by the donation application information, from securities back-office system 16 as customer information corresponding to the donation application information. The individual ID obtaining unit 52 stores the customer information corresponding to the donation application information in customer information storage unit 40 (S14).

[0041] Similarly, a customer applies for a donation through YY points. Customer terminal 12 transmits donation application information to point program management company device 18, and point program management company device 18 transmits the donation application information to Impact PF 22. Donation application information storage unit 42 of Impact PF 22 stores the donation application information (e.g., individual ID=456). Customer information corresponding to the donation application information (e.g., individual ID=456) is stored in customer information storage unit 40 of Impact PF 22.

[0042] Similarly, a customer makes a donation application through ZZ Bank. Customer terminal 12 transmits donation application information to bank device 20, and bank device 20 transmits the donation application information to Impact PF 22. Donation application information storage unit 42 of Impact PF 22 stores the donation application information (e.g., individual ID=789). Customer information storage unit 40 of Impact PF 22 stores customer information (e.g., individual ID=789) corresponding to the donation application information.

[0043] If the donation application information is not accepted (N in S10), the processes of S12 and S14 are skipped.

[0044] In the embodiment, the timing of donation is the timing when the assets of the customer managed by each business company increase. For example, the timing of donation is the timing when stock dividends, bond interest, or investment trust distributions are deposited into the customer's account managed by a financial institution. Also, the timing of donation is the timing when new points are added to the points of the customer managed by a point program management company.

[0045] The securities back-office system 16 notifies Impact PF 22 of the occurrence of an event that triggers a donation. For example, the securities back-office system 16 notifies Impact PF 22 that a dividend has been deposited into the client's securities account opened with XX Securities. This notification includes an individual ID (e.g., individual ID=123). The donation mode determination unit 54 of Impact PF 22 detects that it is time to make a donation from the client's securities account based on the notification. When the donation mode determination unit 54 detects that it is time to donate (Y in S16), it refers to the donation application information linked to the individual ID indicated in the notification and identifies the donation destination and donation amount (S18).

[0046] The donation execution unit 56 of Impact PF 22 executes a process to donate the amount specified in S18 to the donation recipient specified in S18 (S20). For example, the donation execution unit 56 may cause the securities back-office system 16 to execute a transfer process of the donation amount from the customer's account at XX Securities to the account of the donation recipient foundation by calling an API (Application Programming Interface) for transfer instructions provided by the securities back-office system 16. The donation execution unit 56 stores donation history information indicating details of the donation made in S20 in the donation history storage unit 44 (S22).

[0047] Similarly, the donation mode determination unit 54 of Impact PF 22 detects that it is time for the customer to make a donation from the points he or she owns, based on a notification (e.g., individual ID=456) from the point program management company device 18. The donation execution unit 56 of Impact PF 22 cooperates with the point program management company device 18 to execute donation processing in the mode indicated by the donation application information linked to the individual ID indicated in the notification. For example, the donation execution unit 56 may call an API provided by the point program management company device 18 to cause the point program management company device 18 to execute a process of transferring the amount indicated in the donation application information from the YY point business company to the donation recipient foundation, and a process of deducting points equivalent to that amount from the points held by the customer.

[0048] Similarly, the donation mode determination unit 54 of Impact PF 22 detects that it is time to make a donation from the bank account held by the customer based on a notification (e.g., individual ID=789) from the bank device 20. The donation execution unit 56 of Impact PF 22 cooperates with the bank device 20 to execute donation processing in the mode indicated by the donation application information linked to the individual ID indicated in the notification. For example, the donation execution unit 56 may call an API provided by the bank device 20 to cause the bank device 20 to execute a transfer process of the donation amount from the customer's account at ZZ Bank to the account of the foundation to which the donation is to be made.

[0049] If it is not detected that the donation timing has arrived (N in S16), the process of S18 to S22 is skipped.

[0050] When the receipt issuing time has come, the receipt issuing unit 58 of Impact PF22 detects this (Y in S24). The receipt issuing time may be a specific date and time in a predetermined unit period (for example, midnight on the first day of each month), or when data requesting receipt issuance is received from the customer terminal 12. The receipt issuing unit 58 generates a receipt addressed to the customer, including the name of the organization to which the donation is made and the donation amount, based on the donation history information stored in the donation history storage unit 44. The receipt issuing unit 58 transmits the generated receipt data to the customer terminal 12 (S26). If it has not been detected that the receipt issuing time has come (N in S24), the process of S26 is skipped.

[0051] 6 is also a flowchart showing the operation of Impact PF 22. In response to a customer's operation, the customer terminal 12 transmits data requesting an integration target ID designation screen to Impact PF 22. The consent acceptance unit 60 of Impact PF 22 receives the data requesting an integration target ID designation screen transmitted from the customer terminal 12 (Y in S30). The consent acceptance unit 60 transmits data of the integration target ID designation screen to the customer terminal 12 (S32). The customer terminal 12 displays the integration target ID designation screen on the display.

[0052] FIG. 7 shows an example of a screen for designating IDs to be integrated. The screen 70 for designating IDs to be integrated has fields for inputting information on the individual IDs to be integrated and the business company that assigned the individual IDs to the customer. The screen 70 for designating IDs to be integrated is a screen on which multiple pairs of business companies and individual IDs can be designated. The customer terminal 12 transmits the ID information to be integrated that the customer inputs on the screen 70 for designating IDs to be integrated to Impact PF 22. The ID information to be integrated is information indicating that the customer has agreed to integrate multiple individual IDs. The ID information to be integrated in the embodiment includes multiple pairs of individual IDs to be integrated and the business company that assigned the individual IDs to the customer. A customer who has agreed to the integration of multiple individual IDs is also referred to as a "target customer" below.

[0053] The consent acceptance unit 60 accepts the ID information to be integrated sent from the customer terminal 12 (Y of S34). The ID integration unit 62 of Impact PF 22 refers to the customer information stored in the customer information storage unit 40 and determines whether the multiple individual IDs indicated by the ID information to be integrated are IDs assigned to the same person. Specifically, when the pair of the customer's name and date of birth associated with each of the multiple individual IDs to be integrated matches, the ID integration unit 62 determines that the multiple individual IDs are IDs assigned to the same person.

[0054] If it is determined that the multiple individual IDs to be integrated are IDs assigned to the same person (Y in S36), the ID integration unit 62 determines a unique common ID for the target customer (S38). The ID integration unit 62 associates the common ID assigned to the target customer in S38 with the multiple individual IDs of the target customer stored in the customer information storage unit 40 (S40). Figure 8 shows an example in which the multiple individual IDs of the target customer are associated with the common ID of the target customer.

[0055] If it is determined that the multiple individual IDs to be integrated are not IDs assigned to the same person (N in S36), the processes of S38 and S40 are skipped. If the ID information to be integrated sent from the customer terminal 12 is not accepted (N in S34), the processes of S36 to S40 are skipped. If data requesting a screen to specify the IDs to be integrated is not accepted from the customer terminal 12 (N in S30), the processes of S32 to S40 are skipped.

[0056] In response to a customer's operation, the customer terminal 12 transmits data including a common ID designated by the customer and requesting a portal screen to Impact PF 22. When the authentication unit 64 of Impact PF 22 receives the data requesting the portal screen transmitted from the customer terminal 12 (Y of S42), it authenticates the requesting customer based on the common ID indicated by the data. For example, the customer terminal 12 may transmit data including a pair of a common ID and a password to Impact PF 22, and the authentication unit 64 of Impact PF 22 may authenticate the requesting customer using the pair of the common ID and the password.

[0057] If authentication of the requesting customer is successful, the portal screen providing unit 66 of the impact PF 22 refers to the customer information storage unit 40 to identify multiple individual IDs of the requesting customer associated with the common ID of the requesting customer. The portal screen providing unit 66 refers to the donation application information storage unit 42 to identify multiple donation application information of the requesting customer associated with the multiple individual IDs of the requesting customer. The portal screen providing unit 66 transmits portal screen data including the multiple donation application information of the requesting customer to the customer terminal 12 (S44). The customer terminal 12 displays the portal screen on the display.

[0058] FIG. 9 shows an example of a portal screen. FIG. 9 shows a portal screen 80 provided to a customer with a common ID of "abc". The portal screen 80 includes donation application information that the customer has processed through each business company, and FIG. 9 shows three pieces of donation application information. The portal screen 80 also includes a change object 82, which is a screen element for changing the donation application information. A customer viewing the portal screen 80 selects the change object 82 of the donation application information that the customer wishes to change, and inputs the change information of the donation application information into the portal screen 80. The customer terminal 12 transmits the change information of the donation application information to Impact PF 22 in response to the customer's operation. The change information of the donation application information transmitted from the customer terminal 12 to Impact PF 22 includes the common ID and the business company that made the donation, and may further include the changed organization to which the donation is to be made and / or the changed donation amount.

[0059] Change unit 68 of impact PF 22 accepts change information for the donation application information transmitted from customer terminal 12 (Y of S46). Change unit 68 changes the donation application information stored in donation application information storage unit 42 based on the accepted change information (S48). For example, change unit 68 may refer to customer information storage unit 40 and identify an individual ID for the donation application information to be changed based on a combination of a common ID and a business company indicated in the change information. Change unit 68 may identify the donation application information to be changed from among the donation application information stored in donation application information storage unit 42 based on the identified individual ID. Change unit 68 may update the donation destination and / or donation amount indicated in the donation application information to be changed to the content indicated in the change information.

[0060] If no change information for the donation application information is received from the customer terminal 12 (N in S46), the process of S48 is skipped. Also, if no data requesting a portal screen is received from the customer terminal 12 (N in S42), the processes of S44 to S48 are skipped.

[0061] According to the Impact PF22 of the embodiment, the customer can view a portal screen showing the customer's setting information for each of a plurality of business companies (in the embodiment, donation application information showing the form of donation) using a common ID. Also, according to the Impact PF22 of the embodiment, when changing the setting information, the customer does not need to access the device of each business company, and can change the setting information for any business company from the portal screen. This improves convenience when changing the settings.

[0062] In addition, according to the embodiment of Impact PF22, multiple individual IDs of a customer defined by multiple business companies are integrated into a common ID, subject to the customer's consent. This makes it possible to switch from using Impact PF22 via a business company (BtoBtoC) to using Impact PF22 directly (BtoC), subject to the customer's consent.

[0063] The present disclosure has been described above based on the embodiments. The contents described in the embodiments are merely examples, and it will be understood by those skilled in the art that various modifications are possible in the combination of the components and processing steps of the embodiments, and that such modifications are also within the scope of the present disclosure.

[0064] The technical ideas described in the embodiments can be applied to various systems other than systems that support donations, etc. For example, the technical ideas described in the embodiments can be applied to impact investments that aim to achieve both the solution of environmental and social issues and investment returns, and are funded by user assets managed by multiple business companies. In that case, the investment destinations and investment amounts of the impact investments set by the customer, which are managed by each of the multiple business companies, may be displayed together on a portal screen. The investment destinations and / or investment amounts of the impact investments set in any business company may be changed from the portal screen. The technical ideas described in the embodiments can also be applied to a case where information (e.g., the user's address information, etc.) set individually by the user for multiple business companies is changed using the portal screen.

[0065] <Additional Notes> The above description of the embodiment and modifications discloses the following techniques. [Technology 1] A first storage unit that stores a plurality of IDs of users defined in systems of a plurality of organizations; A second storage unit that stores setting information of the user for each of the plurality of organizations; an execution unit that executes processing for a system of each organization based on the setting information of the user stored in the second storage unit, using an ID of the user defined in the system of each organization; an association unit that associates a common ID assigned to the user with the multiple IDs of the user stored in the first storage unit; a presentation unit that presents to the user a screen that can be viewed using the common ID and indicates setting information of the user for each of the multiple organizations; a change unit that, when the setting information of the user for a certain organization is changed on the screen, reflects the change in the second storage unit; An information processing system comprising: According to this information processing system, a user can view a screen (hereinafter referred to as a "portal screen") showing the user's setting information for each of a plurality of organizations (business companies, etc.) using a common ID. Furthermore, according to this information processing system, a user can change the setting information for any organization using the portal screen, instead of accessing the devices of each organization to change the setting information. This can improve the convenience when changing the settings. [Technology 2] A reception unit that receives information indicating that the user agrees to integrate the multiple IDs, The associating unit associates a common ID assigned to the user with the multiple IDs of the user stored in the first storage unit, on the condition that the information indicating the agreement is accepted. An information processing system according to technology 1. According to this information processing system, multiple IDs of a user defined in multiple organizations can be integrated into a common ID, subject to the user's consent. [Technology 3] The second storage unit stores setting information of the user regarding a form of donation to each of the plurality of organizations using assets held by the user as a source of funds; the execution unit executes a process for making a donation to each of the plurality of organizations using assets owned by the user in a manner defined by setting information of the user, on a system of each of the organizations; The information processing system according to any one of claims 1 to 2. According to this information processing system, the manner in which a user makes a donation to each of a plurality of organizations using assets held by the user as the source of the donation can be easily changed from a portal screen. [Technology 4] A computer including a first storage unit that stores a plurality of IDs of a user defined in a system of a plurality of organizations, and a second storage unit that stores setting information of the user for each of the plurality of organizations, Executing a process for a system of each organization based on the setting information of the user stored in the second storage unit, using an ID of the user defined in the system of each organization; Associating a common ID assigned to the user with the multiple IDs of the user stored in the first storage unit; presenting to the user a screen that can be viewed using the common ID and indicates setting information of the user for each of the plurality of organizations; When the setting information of the user for a certain organization is changed on the screen, the change is reflected in the second storage unit. Information processing methods. This information processing method achieves the effects described in Technology 1. [Technology 5] A computer including a first storage unit that stores a plurality of IDs of a user defined in a system of a plurality of organizations, and a second storage unit that stores setting information of the user for each of the plurality of organizations, a function of executing a process for a system of each organization based on the setting information of the user stored in the second storage unit, using an ID of the user defined in the system of each organization; a function of associating a common ID assigned to the user with a plurality of IDs of the user stored in the first storage unit; a function of presenting to the user a screen that can be viewed using the common ID and indicates setting information of the user for each of the multiple organizations; a function of reflecting a change in the second storage unit when the user's setting information for a certain organization is changed on the screen; A computer program to achieve this. According to this computer program, a computer that achieves the effects described in Technique 1 can be realized. [Explanation of symbols]

[0066] 12 customer terminal, 22 impact PF, 40 customer information storage unit, 42 donation application information storage unit, 56 donation execution unit, 60 consent acceptance unit, 62 ID integration unit, 66 portal screen providing unit, 68 change unit, 80 portal screen.

Claims

1. A first storage unit that stores a plurality of IDs of users defined in systems of a plurality of organizations; a second storage unit configured to store setting information of the user for each of the plurality of organizations; an execution unit that executes a process for a system of each organization based on the setting information of the user stored in the second storage unit, using an ID of the user defined in the system of each organization; an association unit that associates a common ID assigned to the user with a plurality of IDs of the user stored in the first storage unit; a presentation unit that presents to the user a screen that can be viewed using the common ID and indicates setting information of the user for each of the plurality of organizations; a change unit that, when the setting information of the user for a certain organization is changed on the screen, reflects the change in the second storage unit; An information processing system comprising:

2. a reception unit configured to receive information indicating that the user agrees to integrate the plurality of IDs; The associating unit associates a common ID assigned to the user with the multiple IDs of the user stored in the first storage unit, on the condition that the information indicating the agreement is accepted. The information processing system according to claim 1 .

3. The second storage unit stores setting information of the user regarding a form of donation to each of the plurality of organizations using assets owned by the user as a source of funds; the execution unit executes a process for making a donation to each of the plurality of organizations using assets owned by the user in a manner defined by setting information of the user, on a system of each of the organizations; 3. The information processing system according to claim 1 or 2.

4. A computer including a first storage unit that stores a plurality of IDs of a user defined in a system of a plurality of organizations, and a second storage unit that stores setting information of the user for each of the plurality of organizations, Executing a process for a system of each organization based on the setting information of the user stored in the second storage unit, using an ID of the user defined in the system of each organization; Associating a common ID assigned to the user with the multiple IDs of the user stored in the first storage unit; presenting to the user a screen that can be viewed using the common ID and indicates setting information of the user for each of the plurality of organizations; When the setting information of the user for a certain organization is changed on the screen, the change is reflected in the second storage unit. Information processing methods.

5. A computer including a first storage unit that stores a plurality of IDs of a user defined in a system of a plurality of organizations, and a second storage unit that stores setting information of the user for each of the plurality of organizations, a function of executing a process for a system of each organization based on the setting information of the user stored in the second storage unit, using an ID of the user defined in the system of each organization; A function of associating a common ID assigned to the user with a plurality of IDs of the user stored in the first storage unit; a function of presenting to the user a screen that can be viewed using the common ID and indicates setting information of the user for each of the multiple organizations; a function of reflecting a change in the second storage unit when the setting information of the user for a certain organization is changed on the screen; A computer program to achieve this.

Images