JP6841117B2 - Trading programs, trading equipment and trading methods - Google Patents

Description

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

Internet banking is known in which various bank transactions (for example, deposits, transfers, transfers, balance inquiries, etc.) can be performed using a smartphone, a PC (personal computer), or the like.

Further, there is known a technique capable of confirming payment of an event participation fee by linking an SNS (Social Networking Service) with a system of a financial institution such as a bank (see, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2015-197720

When paying the participation fee for an event, it is considered that the participants of the event often pay the participation fee by, for example, handing it to the event organizer or making a bank transfer from Internet banking.

However, with these payment methods, for example, it is necessary to bring cash directly to the event organizer, or it is necessary to perform a transfer operation that specifies the transfer destination account, so it is troublesome to pay the participation fee. It takes. At the same time, event organizers and secretaries need to spend time collecting participation fees.

In one aspect, the present invention aims to facilitate the settlement of event costs.

In one embodiment, when the registration of the event associated with the first user ID indicating the first user and the first group ID indicating the first group is accepted, the group ID and the user belonging to the group are accepted. The user ID belonging to the first group ID is specified by referring to the storage unit stored in association with the user ID of the above, and the event application indicated by the event information is applied from the terminal corresponding to the specified user ID. Upon receiving the request and the payment processing instruction regarding the event cost, the transfer instruction from the account stored in association with the specified user ID to the account corresponding to the first user ID or the first group ID is settled. It is transmitted to the processing device, and the payment status of the terminal corresponding to the specified user ID is updated to the payment completion for the event in response to the payment processing completion notification from the payment processing device.
It is characterized in that the processing is executed by a computer.

Event costs can be easily settled.

It is a figure which shows an example of the whole structure of the trading system which concerns on 1st Embodiment. It is a figure which shows an example of the hardware configuration of a computer. It is a figure which shows an example of the functional structure of the trading system which concerns on 1st Embodiment. It is a figure which shows an example of a student information DB. It is a figure which shows an example of the event information DB. It is a sequence diagram which shows an example of the registration process of the account which concerns on 1st Embodiment. It is a figure which shows an example of the screen transition (account registration) in a user terminal. It is a sequence diagram which shows an example of the event registration process which concerns on 1st Embodiment. It is a figure which shows an example of the screen transition (event registration) in a user terminal. It is a sequence diagram which shows an example of the participation application of the event and the settlement processing of the participation fee which concerns on 1st Embodiment. It is a figure which shows an example of the screen transition (participation application of an event and settlement of a participation fee) in a user terminal. It is a flowchart which shows an example of the specific processing of an account and an amount which concerns on 1st Embodiment. It is a sequence diagram which shows an example of the confirmation processing of the participation situation of the event which concerns on 1st Embodiment. It is a figure which shows an example of the screen transition (confirmation of the participation status of an event and the settlement status) in a user terminal. It is a figure which shows an example of the functional structure of the trading system which concerns on 2nd Embodiment. It is a figure which shows an example of a group information DB. It is a flowchart which shows an example of the specific processing of an account and an amount which concerns on 2nd Embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[First Embodiment]
<Overall configuration>
First, the overall configuration of the trading system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of the overall configuration of the trading system 1 according to the first embodiment.

As shown in FIG. 1, the transaction system 1 according to the present embodiment includes a server device 10, one or more user terminals 20, and one or more bank systems 30, for example, a network N such as the Internet or a dedicated line. It is connected so that it can communicate via.

The server device 10 requires the banking system 30 to settle expenses (for example, participation fees for training camps and welcome parties for new students) related to events in student life such as universities (for example, training camps for seminars and club activities, welcome parties for new students, etc.). It is a computer. The server device 10 has a trading program 100.

The server device 10 accepts registration of events such as seminars and training camps for club activities by the transaction program 100. Further, the server device 10 receives, for example, an application for participation in a registered event by the transaction program 100, identifies the account to which the participation fee is transferred and the account to which the participation fee is transferred, and then charges the participation fee for the event. Request payment from the banking system 30.

The user terminal 20 is a computer used by a user (for example, a student at a university or the like). As the user terminal 20, for example, a smartphone, a PC, a tablet terminal, a mobile phone, or the like can be used. The user terminal 20 has a client program 200. The user terminal 20 can register an event, apply for participation, settle a participation fee, and the like by using the client program 200.

The banking system 30 is a computer system owned by a financial institution such as a bank. The banking system 30 includes a core banking system and the like. Further, the accounting system has a ledger DB (database) and the like for managing deposit account ledger data. The banking system 30 is an example of a payment processing device.

<Hardware configuration>
Next, the hardware configuration of the computer 400 that realizes the server device 10 and the user terminal 20 will be described with reference to FIG. FIG. 2 is a diagram showing an example of the hardware configuration of the computer 400.

The computer 400 shown in FIG. 2 has an input device 401, a display device 402, an external I / F 403, a communication I / F 404, and a ROM (Read Only Memory) 405. Further, the computer 400 shown in FIG. 2 has a RAM (Random Access Memory) 406, a CPU (Central Processing Unit) 407, and an auxiliary storage device 408. Each of these hardware is connected to each other by a bus 409.

The input device 401 is, for example, a keyboard, a mouse, a touch panel, or the like, and is used for inputting various operation signals to the computer 400. The display device 402 is, for example, a display or the like, and displays various processing results by the computer 400. The server device 10 does not have to have at least one of the input device 401 and the display device 402.

The external I / F 403 is an interface with an external device. The external device includes a recording medium 403a and the like. The computer 400 can read and write to the recording medium 403a via the external I / F 403. For example, the transaction program 100, the client program 200, and the like may be recorded on the recording medium 403a.

The recording medium 403a includes, for example, an SD memory card, a USB memory, a CD (Compact Disk), a DVD (Digital Versatile Disk), and the like.

The communication I / F 404 is an interface for connecting the computer 400 to the network N. The computer 400 can communicate with other devices via the communication I / F404. The client program 200 may be acquired (downloaded) from another device via, for example, the communication I / F404.

The ROM 405 is a non-volatile semiconductor memory that can retain data even when the power is turned off. The RAM 406 is a volatile semiconductor memory that temporarily holds programs and data. The CPU 407 is an arithmetic unit that reads a program or data from, for example, an auxiliary storage device 408 or a ROM 405 onto the RAM 406 and executes various processes.

The auxiliary storage device 408 is, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like, and is a non-volatile memory for storing programs and data. The programs and data stored in the auxiliary storage device 408 include, for example, an OS (Operating System) which is basic software, various application programs, a transaction program 100, a client program 200, and the like.

In the server device 10 and the user terminal 20 according to the present embodiment, various processes described later are realized by the computer 400 in FIG.

<Functional configuration>
Next, the functional configuration of the trading system 1 according to the present embodiment will be described with reference to FIG. FIG. 3 is a diagram showing an example of the functional configuration of the trading system 1 according to the first embodiment.

As shown in FIG. 3, the user terminal 20 according to the present embodiment includes an input reception unit 201, a display control unit 202, an account registration request unit 203, an event list request unit 204, an event registration request unit 205, and the like. It has a transfer request unit 206, a confirmation request unit 207, a settlement status management unit 208, and a communication unit 209. Each of these functional units is realized by a process in which the client program 200 causes the CPU 407 to execute.

Further, the user terminal 20 according to the present embodiment has a student ID storage unit 210 and a payment status storage unit 220. Each of these storage units can be realized by using, for example, an auxiliary storage device 408.

The input receiving unit 201 receives various inputs by the user. For example, the input receiving unit 201 accepts the input of the operation (account registration operation) for the user to register his / her own account. Further, for example, the input reception unit 201 accepts the input of the operation (participation operation) for applying for participation in the event. Further, for example, the input reception unit 201 accepts the input of the operation (bank transfer selection operation) for settling the participation fee of the event by bank transfer.

The display control unit 202 displays various screens and the like. For example, the display control unit 202 displays a screen (event participation selection screen) for selecting participation or non-participation in the event. Further, for example, the display control unit 202 displays a screen (payment method selection screen) for selecting a payment method for the event participation fee.

The account registration request unit 203 transmits an account registration request for registering the user's account information to the server device 10 via the communication unit 209.

The event list request unit 204 transmits, for example, an event list acquisition request for acquiring a list of events that the user can participate in to the server device 10 via the communication unit 209.

The event registration request unit 205 transmits an event registration request for registering an event to the server device 10 via the communication unit 209.

The transfer request unit 206 transmits a transfer request for transferring the participation fee of the event to a predetermined account to the server device 10 via the communication unit 209.

The confirmation request unit 207 sends a request (participation status confirmation request) to the server device 10 via the communication unit 209, for example, to confirm the participation status of another user who can participate in the event for which he / she has applied for participation. Send.

The payment status management unit 208 manages the payment status 221 stored in the payment status storage unit 220. The payment status 221 includes an event ID that identifies an event for which the user has applied for participation, and a classification indicating whether or not the payment for the event has been completed (that is, information indicating whether payment has been completed or payment has not been completed). The associated information.

Further, when the payment of the participation fee of the event for which the payment status management unit 208 has applied for participation is completed, the payment status management unit 208 updates the payment classification of the event included in the payment status 221 to "payment completed".

The communication unit 209 communicates with the server device 10. For example, the communication unit 209 transmits various requests such as the above-mentioned event list acquisition request and event registration request to the server device 10.

The student ID storage unit 210 stores the student ID 211 that identifies the user who uses the user terminal 20. For the student ID 211, for example, a student ID number or the like can be used. The payment status storage unit 220 stores the above-mentioned payment status 221.

As shown in FIG. 3, the server device 10 according to the present embodiment includes an account authentication request unit 101, an account registration unit 102, an event information acquisition unit 103, an event registration unit 104, a notification unit 105, and specific processing. It has a unit 106, a transfer request unit 107, a participation status confirmation unit 108, a settlement status update unit 109, and a communication unit 110. Each of these functional units is realized by a process in which the transaction program 100 is executed by the CPU 407.

Further, the server device 10 according to the present embodiment has a student information DB 120 and an event information DB 130. Each of these DBs can be realized by using, for example, an auxiliary storage device 408. At least one of these DBs may be realized by using a storage device or the like connected to the server device 10 via the network N.

When the account authentication request unit 101 receives the account registration request from the user terminal 20, the account authentication request unit 101 transmits the account authentication request to the bank system 30. The account authentication request is a request for authenticating the validity of the account information (that is, the store number, subject, account number and PIN) included in the account registration request.

When the authentication result for the account authentication request indicates that the authentication is successful, the account registration unit 102 includes the account information of the corresponding student information among the student information stored in the student information DB 120 in the account registration request. Update with account information. As a result, the account related to the account registration request is registered in the server device 10. The student information includes various information about the user (student ID, affiliation group ID, account information, etc.).

When the event information acquisition unit 103 receives the event list acquisition request from the user terminal 20, the event information acquisition unit 103 acquires the event information of the event in which the user who is the source of the acquisition request can participate from the event information DB 130. The event information includes various information about the event (for example, information indicating a group of users who can participate, information indicating the content of the event, and the like).

When the event registration unit 104 receives the event registration request from the user terminal 20, it creates event information and stores the created event information in the event information DB 130. As a result, the event related to the event registration request is registered in the server device 10.

When the event is registered in the server device 10, the notification unit 105 notifies the user terminal 20 of the user who can participate in the event that the event has been registered.

Upon receiving the transfer request from the user terminal 20, the specific processing unit 106 performs a process for specifying the transfer amount, the transfer destination account, and the transfer source account (account and amount specifying process). Here, the specific processing unit 106 has an amount specifying unit 116, a transfer destination account specifying unit 126, and a transfer source account specifying unit 136.

The amount specifying unit 116 specifies the transfer amount (that is, the participation fee of the event). The transfer destination account identification unit 126 specifies the transfer destination account (that is, the account of the user of the event secretary or the organizer) of the transfer amount. The transfer source account identification unit 136 identifies the transfer source account (that is, the account of the user who applied for participation in the event) of the transfer amount.

The transfer request unit 107 transmits a transfer request indicating a transfer instruction to the transfer destination account specified by the specific processing unit 106 to the bank system 30. At this time, the transfer request unit 107 transmits the transfer request to the bank system 30 that manages the transfer source account.

The participation status confirmation unit 108 acquires the student information of the user who can participate in the event among the student information stored in the student information DB 120 in response to the participation status confirmation request from the user terminal 20.

When the payment status update unit 109 receives the transfer result (transfer result indicating the completion of the transfer) for the transfer request, among the student information stored in the student information DB 120, the payment status included in the corresponding student information is "payment completed". Update to.

The communication unit 110 communicates with the user terminal 20 and the banking system 30. For example, the communication unit 110 returns a response (for example, an event registration result, etc.) to various requests from the user terminal 20 to the user terminal 20. Further, for example, the communication unit 110 transmits the above-mentioned account authentication request, transfer request, and the like to the bank system 30.

The student information DB 120 stores student information. The event information DB 130 stores event information.

Here, the student information DB 120 will be described with reference to FIG. FIG. 4 is a diagram showing an example of the student information DB 120.

As shown in FIG. 4, the student information DB 120 stores one or more student information. In addition, the student information has student ID, account information, affiliation group ID, and payment status as data items.

The student ID is identification information that identifies the user. Examples of the student ID include a student ID number and the like. The account information is the information of the account used by the user. The account information includes a bank code, a store number, a subject, and an account number. This information identifies the user's account. If the account information has not been registered yet, a blank is set in the account information, for example. In the example shown in FIG. 4, no account information is set in the student information of the student ID "ZZZ003".

The affiliation group ID is identification information that identifies the group to which the user belongs. Hereinafter, it is assumed that the group ID that identifies the seminar to which the user belongs is set in the affiliation group ID. That is, it is assumed that the group ID indicating the seminar to which the user belongs (for example, "○○ seminar", "△△ seminar", etc.) is set in the belonging group ID.

However, the group ID of the group of any unit may be set as the belonging group ID. For example, the affiliation group ID may be set to a group ID indicating the faculty unit "Faculty of Letters" or "Faculty of Science", or the group ID indicating the department unit "Faculty of Letters" or "Department of Physics". May be set. In addition to these, for example, a group ID indicating a group such as a major unit, a class unit, a student dormitory unit, a circle unit, or a club activity unit may be set.

Further, a plurality of belonging group IDs may be set in one student information. For example, one student information includes a first group ID indicating the first affiliation group "○○ seminar" and a second group ID indicating the second affiliation group "light music circle". You may.

The payment status includes the event ID of the event in which the user participates and the payment classification of the event. Depending on the payment status, the event in which the user participates and the payment status of the participation fee of the event are managed. When the user participates in a plurality of events, the student information includes a plurality of payment information. In the example shown in FIG. 4, the student information of the student ID "ZZZ002" includes the payment status of the participation event ID "I001" and the payment status of the participation event ID "I005".

As described above, the student information DB 120 stores the student information including the account information of the user of the student ID, the affiliation group ID, and the payment status for each student ID.

Further, the event information DB 130 will be described with reference to FIG. FIG. 5 is a diagram showing an example of the event information DB 130.

As shown in FIG. 5, one or more event information is stored in the event information DB 130. In addition, the event information has an event ID, a group ID that can participate, a title, a purpose, a content, a schedule, a participation fee, a secretary student ID, a registration date and time, and a response deadline as data items. ..

The event ID is identification information that identifies the event. The group ID that can participate is the group ID of the group that can participate in the event. The title is a title (title) used when displaying an event. The purpose, content and schedule are the purpose, content and schedule of the event, respectively. Participation fee is the cost required to participate in the event.

The secretary student ID is the student ID of the user who registered the event (that is, the organizer of the event). The registration date and time is the date and time when the event was registered. The response deadline is the deadline for the date and time when the user can apply for participation.

In this way, the event information DB 130 contains, for each event ID, a group ID that can participate, a title, a purpose, a content, a schedule, a participation fee, a secretary student ID, a registration date and time, and a response deadline. The included event information is stored.

<Account registration process>
Next, a process in which the user registers his / her own account in the server device 10 using the user terminal 20 will be described with reference to FIG. FIG. 6 is a sequence diagram showing an example of the account registration process according to the first embodiment.

First, the input receiving unit 201 of the user terminal 20 receives the input of the account registration start operation (step S101). For example, the user can start the account registration by selecting the bank account registration button G101 on the top screen G100 shown in FIG. 7. The top screen G100 shown in FIG. 7 is displayed by the display control unit 202.

The top screen G100 shown in FIG. 7 includes a university area button G102 and a company area button G103 in addition to the bank account registration button G101. By pressing the university area button G102, it is possible to transition to the university area screen G210, which will be described later. On the university area screen, you can register and participate in seminar-related events, register and participate in circle-related events, refer to timetables, and refer to guidance from the Student Affairs Division.

Further, by pressing the company area button G103, it is possible to transition to the company area screen. On the company area screen, you can apply for various recruitment from companies related to job hunting, refer to company information, and so on.

Next, the display control unit 202 of the user terminal 20 displays the bank registration screen G110 shown in FIG. 7 when the input reception unit 201 receives the input of the account registration start operation (step S102). The bank registration screen G110 shown in FIG. 7 includes a bank name designation field G111 and a next button G112. The user specifies the bank name of the bank that manages his / her account in the bank name designation field G111.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the screen transition operation (step S103). The user can perform the screen transition operation by designating the bank name of the bank that manages his / her account in the bank name designation field G111 and then pressing the next button G112.

Next, when the input receiving unit 201 receives the input of the screen transition operation, the display control unit 202 of the user terminal 20 displays the account registration screen G120 shown in FIG. 7 (step S104). The account registration screen G120 shown in FIG. 7 includes a registration content designation field G121 and a registration button G122. The user specifies various information (store number, subject, account number, password, etc.) of his / her own account in the registration content designation field G121.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the account registration operation (step S105). The user can perform the account registration operation by designating various information (store number, subject, account number, PIN, etc.) of his / her own account in the registration content specification field G121 and then pressing the registration button G122. ..

Next, the account registration request unit 203 of the user terminal 20 transmits the account registration request to the server device 10 via the communication unit 209 (step S106). The account registration request includes the student ID 211 stored in the student ID storage unit 210, the bank code indicating the bank designated in the bank name designation field G111, and the store number and subject designated in the registration content designation field G121. Includes account number and PIN.

When the account authentication request unit 101 of the server device 10 receives the account registration request from the user terminal 20 via the communication unit 110, the account authentication request unit 101 transmits the account authentication request to the bank system 30 (step S107). At this time, the account authentication request unit 101 transmits the account authentication request to the bank system 30 of the bank indicated by the bank code included in the account registration request. In addition, the account authentication request includes the above-mentioned store number, subject, account number, and PIN. In the banking system 30, the legitimacy of the account is authenticated in response to the account authentication request. The authentication of the legitimacy of an account is, for example, an authentication for confirming whether or not an account indicated by a store number, a subject, and an account number exists, and whether or not a personal identification number is correct.

Then, the communication unit 110 of the server device 10 receives the authentication result transmitted from the bank system 30. Hereinafter, it is assumed that the communication unit 110 of the server device 10 has received the authentication result indicating that the account is valid.

The account registration unit 102 of the server device 10 updates the account information included in the student information among the student information stored in the student information DB 120 (step S108). That is, among the student information stored in the student information DB 120, the account registration unit 102 includes the student information of the student ID included in the account registration request received from the user terminal 20 in the account registration request. Update with bank code, store number, subject and account number. As a result, the user's account is registered.

Then, the account registration unit 102 of the server device 10 returns the registration result indicating that the registration is completed to the user terminal 20.

Next, when the display control unit 202 of the user terminal 20 receives the registration result via the communication unit 209, the display control unit 202 displays the registration completion screen G130 shown in FIG. 7 (step S109). As a result, the user can know that the registration of his / her account has been completed.

As described above, the server device 10 according to the present embodiment can register the user's account information in response to the request from the user terminal 20.

<Event registration process>
Next, a process in which the user registers an event for which he / she is the secretary using the user terminal 20 will be described with reference to FIG. FIG. 8 is a sequence diagram showing an example of the event registration process according to the first embodiment.

First, the input receiving unit 201 of the user terminal 20 receives the input of the screen transition operation to the university area (step S201). For example, on the top screen G100 shown in FIG. 9, the user can perform a screen transition operation to the university area by selecting the university area button G102.

Next, when the input reception unit 201 receives the input of the screen transition operation to the university area, the display control unit 202 of the user terminal 20 displays the university area screen G210 shown in FIG. 9 (step S202). The university area screen G210 shown in FIG. 9 includes a “seminar event” button G211. The user can transition to the "seminar event" screen G220, which will be described later, by pressing the "seminar event" button G211. After that, it is assumed that the user presses the "seminar event" button G211 to perform the screen transition operation to the "seminar event" screen G220.

In addition to the "Seminar Event" button G211, the university area screen G210 shown in FIG. Includes a "Student Division Guidance" button to transition to a screen where you can refer to the guidance. Further, the university area screen G210 shown in FIG. 9 includes a "circle event" button for transitioning to a screen capable of registering or applying for participation in an event related to the circle.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the screen transition operation to the "seminar event" screen G220 (step S203).

Next, the event list request unit 204 of the user terminal 20 transmits an event list acquisition request to the server device 10 via the communication unit 209 (step S204). The acquisition request includes the student ID 211 stored in the student ID storage unit 210.

When the event information acquisition unit 103 of the server device 10 receives the event list acquisition request from the user terminal 20 via the communication unit 110, the event information acquisition unit 103 refers to the student information stored in the student information DB 120 and refers to the user's group ( The affiliation seminar) is specified (step S205). That is, the event information acquisition unit 103 identifies the group ID set in the affiliation group ID in the student information of the student ID included in the event list acquisition request among the student information stored in the student information DB 120.

Next, the event information acquisition unit 103 of the server device 10 acquires the event information including the group ID specified in step S205 from the event information DB 130 (step S206). That is, the event information acquisition unit 103 acquires the event information in which the group ID specified in step S205 is set as the joinable group ID among the event information stored in the event information DB 130.

Then, the event information acquisition unit 103 returns the event information acquired from the event information DB 130 to the user terminal 20.

When the event information is returned from the server device 10, the display control unit 202 of the user terminal 20 displays the “seminar event” screen G220 shown in FIG. 9 (step S207). The "seminar event" screen G220 shown in FIG. 9 includes an event list G221 and an event addition button G222. In the event list G221, a button indicating a title included in the event information returned from the server device 10 is displayed so as to be selectable.

By pressing the event addition button G222, the user can perform an event addition operation for registering a new event addition. After that, it is assumed that the user presses the event addition button G222 to perform the event addition operation.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the event addition operation (step S208).

Next, when the input reception unit 201 receives the input of the event addition operation, the display control unit 202 of the user terminal 20 displays the event registration screen G230 shown in FIG. 9 (step S209). The event registration screen G230 shown in FIG. 9 includes an event information designation field G231 and a registration button G232. The user specifies various information (title, purpose, content, schedule, participation fee, registration date and time, response deadline) of the event that he / she desires to register in the event information designation field G231.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the event registration operation (step S210). The user specifies various information (title, purpose, content, schedule, participation fee, registration date and time, response deadline) of the event that he / she wants to register in the event information specification field G231, and then presses the registration button G232. You can perform the event registration operation with.

Next, the event registration request unit 205 of the user terminal 20 transmits the event registration request to the server device 10 via the communication unit 209 (step S211). In the event registration request, the student ID 211 stored in the student ID storage unit 210, the joinable group ID indicating the group ID of the seminar to which the user belongs, and various information (title, title, designated in the event information designation field G231) are included. Purpose, content, schedule, participation fee, response deadline) are included. The group ID that can participate may be specified in the event information designation field G231.

When the event registration unit 104 of the server device 10 receives the event registration request from the user terminal 20 via the communication unit 209, the event registration unit 104 creates event information (step S212). That is, the event registration unit 104 creates the event ID, the registration date and time, various information included in the event registration request, and the event information including the student ID after generating the event ID and the registration date and time. To do. At this time, the student ID is set in the data item of the secretary student ID.

Next, the event registration unit 104 of the server device 10 stores the event information created in step S212 above in the event information DB 130 (step S213). As a result, the event is registered.

Then, the event registration unit 104 of the server device 10 returns the registration result indicating that the registration is completed to the user terminal 20.

Next, the notification unit 105 of the server device 10 identifies students who can participate in the event registered in step S213 above (step S214). That is, the notification unit 105 identifies the student information of the user who belongs to the group indicated by the joinable group ID of the event information stored in the event information DB 130 in step S213.

Next, the notification unit 105 of the server device 10 notifies the user terminal 20 of the user specified in step S213 above that the event has been registered (step S215). As a result, the user (student) who can participate in the newly registered event can know that the event in which he / she can participate has been registered.

The notification unit 105 may notify that the event has been registered by displaying a predetermined pop-up on the user terminal 20 of the user who can participate, or send an e-mail to a preset e-mail address. You may notify that the event has been registered by doing so. Further, the notification unit 105 may display that the event has been registered on the top screen G100 or the like displayed by the user terminal 20.

As described above, the server device 10 according to the present embodiment can register various events in response to the request from the user terminal 20. In the example shown in FIG. 8, the case where the student user registers the event has been described, but the present invention is not limited to this. The registration of the event may be performed by a user such as a faculty member, for example.

<Settlement processing for event participation and participation fee>
Next, a process in which the user applies for participation in the event using the user terminal 20 and determines the participation fee will be described with reference to FIG. FIG. 10 is a sequence diagram showing an example of the participation application for the event and the settlement processing of the participation fee according to the first embodiment. Since steps S301 to S307 in FIG. 10 are the same as steps S201 to S207 in FIG. 8, the description will be simplified as appropriate.

First, the input receiving unit 201 of the user terminal 20 receives the input of the screen transition operation to the university area (step S301). For example, on the top screen G100 shown in FIG. 11, the user can perform a screen transition operation to the university area by selecting the university area button G102.

Next, when the input reception unit 201 receives the input of the screen transition operation to the university area, the display control unit 202 of the user terminal 20 displays the university area screen G210 shown in FIG. 11 (step S302). After that, it is assumed that the user presses the "seminar event" button G211 to perform the screen transition operation to the "seminar event" screen G220.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the screen transition operation to the "seminar event" screen G220 (step S303).

Next, the event list request unit 204 of the user terminal 20 transmits an event list acquisition request to the server device 10 via the communication unit 209 (step S304). The acquisition request includes the student ID 211 stored in the student ID storage unit 210.

When the event information acquisition unit 103 of the server device 10 receives the event list acquisition request from the user terminal 20 via the communication unit 110, the event information acquisition unit 103 refers to the student information stored in the student information DB 120 and refers to the user's group ( The affiliation seminar) is specified (step S305).

Next, the event information acquisition unit 103 of the server device 10 acquires the event information of the group specified in step S305 from the event information DB 130 (step S306). Then, the event information acquisition unit 103 returns the event information acquired from the event information DB 130 to the user terminal 20.

When the event information is returned from the server device 10, the display control unit 202 of the user terminal 20 displays the “seminar event” screen G220 shown in FIG. 11 (step S307).

The user can perform the event selection operation by selecting the button included in the event list G221. Hereinafter, it is assumed that the user selects the "welcome party guidance" button G222 and performs the event selection operation.

Next, the input reception unit 201 of the user terminal 20 receives the input of the event selection operation in which the "welcome party guidance" button G222 is selected (step S308).

Next, when the display control unit 202 of the user terminal 20 receives the input of the event selection operation in which the "welcome party guidance" button G222 is selected, the display control unit 202 displays the event participation selection screen G240 shown in FIG. 11 (step S309). The event participation selection screen G240 shown in FIG. 11 includes a participation button G241 for applying to participate in the event selected by the event selection operation (that is, the event of the title “welcome party guidance”). The user can perform the participation operation by pressing the participation button G241. By pressing the non-participation button, the user can notify the user who is the secretary of the event of non-participation.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the participation operation (step S310).

Next, when the input reception unit 201 receives the input of the participation operation, the display control unit 202 of the user terminal 20 displays the payment instruction screen G250 shown in FIG. 11 (step S311). The settlement instruction screen G250 shown in FIG. 11 includes a "bank transfer" button G251 for settling the participation fee of the event by bank transfer. The user can perform the bank transfer operation by pressing the "bank transfer" button G251. The user can also settle the participation fee of the event by another payment method (for example, handing the participation fee) by pressing the "other" button.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the bank transfer operation (step S312).

Next, when the input receiving unit 201 receives the input of the bank transfer operation, the transfer request unit 206 of the user terminal 20 transmits the transfer request to the server device 10 via the communication unit 209 (step S313). The transfer request includes the event ID of the event for which the participation operation was performed in step S310, and the student ID 211 stored in the student ID storage unit 210. The transfer request by the transfer request unit 206 is an example of an instruction for settlement processing related to the event cost.

Upon receiving the transfer request via the communication unit 110, the identification processing unit 106 of the server device 10 performs an account and amount identification processing (step S314). By the process of specifying the account and the amount, the account information of the transfer destination account, the account information of the transfer source account, and the transfer amount are specified. The process for specifying the account and amount will be described later.

Next, the transfer request unit 107 of the server device 10 transmits the transfer request to the bank system 30 via the communication unit 110 (step S315). The transfer request includes the account information of the transfer destination account, the account information of the transfer source account, and the transfer amount. At this time, the transfer request unit 107 transmits the transfer request to the bank system 30 of the bank that manages the transfer source account. In the bank system 30, the transfer processing of the transfer amount from the transfer source account to the transfer destination account (that is, the settlement processing of the event cost) is performed in response to the transfer request. The transfer request by the transfer request unit 107 is an example of a transfer instruction.

Then, the communication unit 110 of the server device 10 receives the transfer result transmitted from the bank system 30. Hereinafter, it is assumed that the communication unit 110 of the server device 10 has received the transfer result indicating that the transfer has been completed.

When the payment status update unit 109 of the server device 10 receives the transfer result via the communication unit 110, it updates the payment status of the corresponding student information among the student information stored in the student information DB 120 (step S316). .. That is, the payment status update unit 109 sets the event ID included in the transfer request as the participation event ID and the payment completion as the payment category for the student information of the student ID included in the transfer request received in step S314 above. Add the payment status you have made. As a result, it is managed that the user has applied for participation in the event of the event ID and that the settlement of the event has been completed.

Then, the communication unit 110 of the server device 10 returns the transfer result received from the bank system 30 to the user terminal 20.

The payment status management unit 208 of the user terminal 20 creates a payment status 221 in which the event ID of the event for which the user has applied for participation and the payment completion are associated with each other, and stores the payment status 221 in the payment status storage unit 220 (step S317). ). As a result, the event ID of the event for which the user has applied for participation and whether or not the settlement of the event has been completed are also managed by the user terminal 20.

Next, the display control unit 202 of the user terminal 20 displays the transfer completion screen G260 shown in FIG. 11 (step S318). On the transfer completion screen G260 shown in FIG. 11, the content indicating that the transfer of the event participation fee has been completed is displayed. As a result, the user can know that the transfer of the participation fee of the event for which he / she has applied for participation has been completed.

As described above, the server device 10 according to the present embodiment specifies the information (transfer amount, transfer source account and transfer destination account) necessary for payment in response to the request from the user terminal 20, and the bank system 30. You can request payment from the bank. As a result, the user can easily settle the payment of the participation fee for participating in the event, for example.

In the example shown in FIG. 10, for example, the settlement of the participation fee when the user participates in an event such as a welcome party or a training camp has been described, but the present invention is not limited to this. The event may be, for example, the purchase of a textbook. In this case, the textbook cost purchased by the user is settled. Similarly, the event may be, for example, payment of a tuition fee or payment of food and drink charges in a student cafeteria or the like. In this way, events are not limited to welcome parties and training camps in which users participate, but are various events that require payment in student life, such as purchasing textbooks, paying tuition fees, and eating and drinking at the student cafeteria. There may be.

<Specific processing of account and amount>
Next, the process of specifying the account and the amount in step S314 will be described with reference to FIG. FIG. 12 is a flowchart showing an example of the account and amount specifying process according to the first embodiment.

First, the amount specifying unit 116 refers to the event information DB 130 and specifies the transfer amount from the received event ID (event ID included in the transfer request received from the user terminal 20) (step S401). That is, the amount specifying unit 116 specifies the amount set for the participation fee in the event information of the event ID among the event information included in the event information DB 130.

Next, the transfer destination account specifying unit 126 refers to the event information DB 130 and identifies the secretary student ID from the received event ID (step S402). That is, the transfer destination account specifying unit 126 specifies the student ID set in the secretary student ID in the event information of the event ID among the event information included in the event information DB 130.

Next, the transfer destination account specifying unit 126 refers to the student information DB 120 and identifies the transfer destination account from the secretary student ID specified in step S402 above (step S403). That is, the transfer destination account specifying unit 126 specifies the account information in the student information of the secretary student ID among the student information stored in the student information DB 120. The account information specified here is the account information of the transfer destination account.

Next, the transfer source account specifying unit 136 refers to the student information DB 120 and identifies the transfer source account from the received student ID (student ID included in the transfer request received from the user terminal 20) (step S404). That is, the transfer source account identification unit 136 specifies the account information in the student information of the student ID among the student information stored in the student information DB 120. The account information specified here is the account information of the transfer source account.

As described above, the server device 10 according to the present embodiment can specify the transfer amount, the transfer destination account, and the transfer source account.

<Confirmation process of event participation status>
Next, a process of confirming another user who has applied for participation in the event for which the user has applied for participation by using the user terminal 20 will be described with reference to FIG. FIG. 13 is a sequence diagram showing an example of a confirmation process of the participation status of the event according to the first embodiment. Since steps S501 to S507 in FIG. 13 are the same as steps S201 to S207 in FIG. 8, the description will be simplified as appropriate.

First, the input receiving unit 201 of the user terminal 20 receives the input of the screen transition operation to the university area (step S501). For example, on the top screen G100 shown in FIG. 14, the user can perform a screen transition operation to the university area by selecting the university area button G102.

Next, when the input reception unit 201 receives the input of the screen transition operation to the university area, the display control unit 202 of the user terminal 20 displays the university area screen G210 shown in FIG. 14 (step S502). After that, it is assumed that the user presses the "seminar event" button G211 to perform the screen transition operation to the "seminar event" screen G220.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the screen transition operation to the "seminar event" screen G220 (step S503).

Next, the event list request unit 204 of the user terminal 20 transmits an event list acquisition request to the server device 10 via the communication unit 209 (step S504). The acquisition request includes the student ID 211 stored in the student ID storage unit 210.

When the event information acquisition unit 103 of the server device 10 receives the event list acquisition request from the user terminal 20 via the communication unit 110, the event information acquisition unit 103 refers to the student information stored in the student information DB 120 and refers to the user's group ( The affiliation seminar) is specified (step S505).

Next, the event information acquisition unit 103 of the server device 10 acquires the event information of the group specified in step S505 from the event information DB 130 (step S506). Then, the event information acquisition unit 103 returns the event information acquired from the event information DB 130 to the user terminal 20.

When the event information is returned from the server device 10, the display control unit 202 of the user terminal 20 displays the “seminar event” screen G220 shown in FIG. 14 (step S507).

The user can perform the event selection operation by selecting the button included in the event list G221. Hereinafter, it is assumed that the user selects the "welcome party guidance" button G222 indicating the event for which he / she has already applied for participation, and performs the event selection operation.

Next, the input reception unit 201 of the user terminal 20 receives the input of the event selection operation in which the "welcome party guidance" button G222 is selected (step S508).

Next, when the display control unit 202 of the user terminal 20 receives the input of the event selection operation in which the "welcome party guidance" button G222 is selected, the display control unit 202 displays the event details screen G310 shown in FIG. 14 (step S509). As described above, when the input reception unit 201 receives the input of the event selection operation for the event for which the user has already applied for participation, the display control unit 202 displays the event detail screen G310 as shown in FIG. Whether or not the event has already been applied for participation by the user can be determined by referring to the payment status 221 stored in the payment status storage unit 220.

On the event detail screen G310 shown in FIG. 14, a detailed display column G311 displaying detailed information (schedule, content, etc.) of the event and a "participation status" button for referring to the participation application status and payment status of the event are displayed. G312 and the like are included. The user can confirm the participation status by pressing the "participation status" button G312.

Next, the input receiving unit 201 of the user terminal 20 receives the input of the participation status confirmation operation (step S510).

Next, when the input reception unit 201 receives the input of the participation status confirmation operation, the confirmation request unit 207 of the user terminal 20 transmits the participation status confirmation request to the server device 10 via the communication unit 209 (step). S511). The confirmation request includes the event ID of the event for which the event selection operation was performed in step S507.

When the participation status confirmation unit 108 of the server device 10 receives the participation status confirmation request via the communication unit 110, the participation status confirmation unit 108 identifies a group that can participate in the corresponding event information (step S512). That is, the participation status confirmation unit 108 identifies the group ID set in the joinable group ID in the event information of the event ID included in the confirmation request among the event information stored in the event information DB 130.

Next, the participation status confirmation unit 108 of the server device 10 acquires the student information of the users belonging to the joinable group specified in step S512 above from the student information DB 120 (step S513). In other words, the participation status confirmation unit 108 acquires student information of users who can participate in the event from the student information DB 120.

Then, the participation status confirmation unit 108 of the server device 10 returns the acquired student information to the user terminal 20.

The display control unit 202 of the user terminal 20 displays the participation status list screen G320 shown in FIG. 14 (step S514). The participation status list screen G320 shown in FIG. 14 includes a participation status list G321 showing the participation status (participation or non-participation) of other users who can participate in the event for which the user has applied for participation. The participation status list G321 is displayed based on the payment status of the student information returned from the server device 10. As a result, the user can know the participation status of other users who can participate in the event for which he / she has applied for participation.

The participation status list G321 may include information indicating whether or not the payment of the other user has been completed. As a result, for example, the user who is the organizer or the secretary of the event can easily confirm whether or not the payment of the participants of the event has been completed. In addition, information indicating whether or not such payment has been completed may be displayed only to the user who is the organizer or secretary of the event.

As described above, the server device 10 according to the present embodiment has information (participation or participation) of other users who can participate in the event for which the user of the user terminal 20 has applied for participation in response to the request from the user terminal 20. Non-participation, payment completed or payment not completed, etc.) can be displayed. As a result, the user can easily know the participation status and the payment status in the event in which he / she participates.

[Second Embodiment]
Next, the second embodiment will be described. In the first embodiment, the case where the account of the user who hosts or organizes the event (for example, the secretary student) is specified as the transfer destination account has been described, but in the second embodiment, it corresponds to the group who can participate in the event. The case where the account is specified as the transfer destination account will be described.

In the second embodiment, the differences from the first embodiment will be mainly described, and the same components as those in the first embodiment will be given the same reference numerals as those in the first embodiment. , The description is omitted.

<Functional configuration>
First, the functional configuration of the trading system 1 according to the present embodiment will be described with reference to FIG. FIG. 15 is a diagram showing an example of the functional configuration of the trading system 1 according to the second embodiment.

As shown in FIG. 15, the identification processing unit 106 of the server device 10 according to the present embodiment has a transfer destination account identification unit 126A. Further, the server device 10 according to the present embodiment has the group information DB 140. The DB can be realized by using, for example, an auxiliary storage device 408. The DB may be realized by using a storage device or the like connected to the server device 10 via the network N.

The transfer destination account identification unit 126A refers to the group information DB 140 and identifies the account corresponding to the group that can participate in the event as the transfer destination account.

The group information DB 140 stores the group information. Here, the group information DB 140 will be described with reference to FIG. FIG. 16 is a diagram showing an example of the group information DB 140.

As shown in FIG. 16, the group information DB 140 stores one or more group information. Further, the group information has a group ID and account information as data items.

As described above, the group information DB 140 stores the group information including the account information of the group for each group.

<Specific processing of account and amount>
Hereinafter, the process of specifying the account and the amount in step S314 of FIG. 10 will be described with reference to FIG. FIG. 17 is a flowchart showing an example of the identification process of the account and the amount of money according to the second embodiment. Since steps S601 and S604 in FIG. 17 are the same as steps S401 and S404 in FIG. 12, the description thereof will be omitted.

Following step S601, the transfer destination account identification unit 126A refers to the group information DB 140 and identifies the group ID from the received event ID (step S602). That is, the transfer destination account specifying unit 126A identifies the group ID set in the joinable group ID in the event information of the event ID among the event information included in the event information DB 130.

Next, the transfer destination account specifying unit 126A refers to the group information DB 140 and identifies the transfer destination account from the group ID specified in step S602 above (step S603). That is, the transfer destination account identification unit 126A specifies the account information in the group information including the group ID among the group information stored in the group information DB 140. The account information specified here is the account information of the transfer destination account.

As described above, the server device 10 according to the present embodiment can specify the account corresponding to the group capable of participating in the event as the transfer destination account. Thereby, for example, even when a plurality of users register an event of a certain group, the same transfer destination account can be used.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed.

With respect to the above description, the following sections will be further disclosed.
(Appendix 1)
When the registration of the event associated with the first user ID indicating the first user and the first group ID indicating the first group is accepted, the group ID and the user ID of the user belonging to the group are assigned. The user ID belonging to the first group ID is specified by referring to the storage unit stored in association with each other.
When the event application request and the payment processing instruction regarding the event cost indicated by the event information are received from the terminal corresponding to the specified user ID, the first first from the account stored in association with the specified user ID. Send the transfer instruction to the user ID or the account corresponding to the first group ID to the payment processing device, and
In response to the payment processing completion notification from the payment processing device, the payment status of the terminal corresponding to the specified user ID is updated to payment completion for the event.
A trading program characterized by having a computer perform processing.
(Appendix 2)
Notifies the terminal corresponding to the specified user ID that an event that the user indicated by the user ID can apply for has been registered.
The trading program according to Appendix 1, wherein the processing is executed by a computer.
(Appendix 3)
In response to a request from the first terminal corresponding to one of the specified user IDs, the payment status of the terminal corresponding to the specified user ID is displayed on the first terminal.
The trading program according to Appendix 1 or 2, wherein the processing is executed by a computer.
(Appendix 4)
When the registration of the event associated with the first user ID indicating the first user and the first group ID indicating the first group is accepted, the group ID and the user ID of the user belonging to the group are assigned. With reference to the storage unit stored in association with each other, a specific unit that identifies a user ID belonging to the first group ID, and a specific unit.
When the event application request and the payment processing instruction regarding the event cost indicated by the event information are received from the terminal corresponding to the specified user ID, the first first from the account stored in association with the specified user ID. A transmission unit that transmits a transfer instruction to the user ID or the account corresponding to the first group ID to the payment processing device, and
In response to the payment processing completion notification from the payment processing device, an update unit that updates the payment status of the terminal corresponding to the specified user ID to payment completion for the event, and an update unit.
A trading device characterized by having.
(Appendix 5)
A notification unit that notifies the terminal corresponding to the specified user ID that an event that the user indicated by the user ID can apply for has been registered.
The trading apparatus according to Appendix 4, wherein the device is characterized by having.
(Appendix 6)
In response to a request from the first terminal corresponding to one of the specified user IDs, the payment status transmission for displaying the payment status of the terminal corresponding to the specified user ID on the first terminal. The trading device according to Appendix 4 or 5, characterized in that it has a unit.
(Appendix 7)
When the registration of the event associated with the first user ID indicating the first user and the first group ID indicating the first group is accepted, the group ID and the user ID of the user belonging to the group are assigned. The user ID belonging to the first group ID is specified by referring to the storage unit stored in association with each other.
When the event application request and the payment processing instruction regarding the event cost indicated by the event information are received from the terminal corresponding to the specified user ID, the first first from the account stored in association with the specified user ID. Send the transfer instruction to the user ID or the account corresponding to the first group ID to the payment processing device, and
In response to the payment processing completion notification from the payment processing device, the payment status of the terminal corresponding to the specified user ID is updated to payment completion for the event.
A trading method characterized by a computer performing processing.
(Appendix 8)
Notifies the terminal corresponding to the specified user ID that an event that the user indicated by the user ID can apply for has been registered.
The transaction method according to Appendix 7, wherein the processing is executed by a computer.
(Appendix 9)
In response to a request from the first terminal corresponding to one of the specified user IDs, the payment status of the terminal corresponding to the specified user ID is displayed on the first terminal.
The trading method according to Appendix 7 or 8, wherein the processing is executed by a computer.

1 Transaction system 10 Server device 20 User terminal 30 Bank system 101 Account authentication request unit 102 Account registration unit 103 Event information acquisition unit 104 Event registration unit 105 Notification unit 106 Specific processing unit 107 Transfer request unit 108 Participation status confirmation unit 109 Payment status update Department 110 Communication Department 116 Amount Identification Department 120 Student Information DB
126 Transfer destination account identification department 130 Event information DB
136 Transfer source account identification unit 201 Input reception unit 202 Display control unit 203 Account registration request unit 204 Event list request unit 205 Event registration request unit 206 Transfer request unit 207 Confirmation request unit 208 Payment status management department 209 Communication department 210 Student ID storage unit 220 Payment status storage unit

Claims (5)

When the registration of the event associated with the first user ID indicating the first user and the first group ID indicating the first group is accepted, the group ID and the user ID of the user belonging to the group are assigned. The second user ID belonging to the first group ID is specified by referring to the first storage unit stored in association with each other.
Upon receiving the event application request indicated by the event information and the payment processing instruction regarding the event cost from the terminal corresponding to the specified second user ID, the second user ID and the bank account are stored in association with each other. referring to the storage unit to identify a first bank corresponding to the identified second user ID, the
By referring to the third storage unit that stores the group ID and the bank account in association with each other, the second bank account corresponding to the first group ID is specified.
A transfer instruction from the specified first bank account to the specified second bank account is transmitted to the payment processing device.
In response to the payment processing completion notification from the payment processing device, the payment status of the terminal corresponding to the specified second user ID is updated to payment completion for the event.
A trading program characterized by having a computer perform processing. The terminal corresponding to the identified second user ID, possible events user application indicated by the second user ID to notify that it has been registered,
The trading program according to claim 1, wherein the processing is executed by a computer. In response to a request from a first terminal corresponding to one of the user ID of the specified second user ID, and the payment status of the terminal corresponding to the identified second user ID first terminal To display on
The trading program according to claim 1 or 2, wherein the processing is executed by a computer. When the registration of the event associated with the first user ID indicating the first user and the first group ID indicating the first group is accepted, the group ID and the user ID of the user belonging to the group are assigned. With reference to the first storage unit stored in association with each other, the first specific unit that identifies the second user ID belonging to the first group ID, and the first specific unit.
Upon receiving the event application request indicated by the event information and the payment processing instruction regarding the event cost from the terminal corresponding to the specified second user ID, the second user ID and the bank account are stored in association with each other. With reference to the storage unit of, the second specific unit that identifies the first bank account corresponding to the specified second user ID, and
With reference to the third storage unit that stores the group ID and the bank account in association with each other, the third specific unit that identifies the second bank account corresponding to the first group ID, and the third specific unit.
A transmission unit that transmits a transfer instruction from the specified first bank account to the specified second bank account to the payment processing device.
In response to the payment processing completion notification from the payment processing device, an update unit that updates the payment status of the terminal corresponding to the specified second user ID with respect to the event to payment completion, and an update unit.
A trading device characterized by having. When the registration of the event associated with the first user ID indicating the first user and the first group ID indicating the first group is accepted, the group ID and the user ID of the user belonging to the group are assigned. The second user ID belonging to the first group ID is specified by referring to the first storage unit stored in association with each other.
Upon receiving the event application request indicated by the event information and the payment processing instruction regarding the event cost from the terminal corresponding to the specified second user ID, the second user ID and the bank account are stored in association with each other. referring to the storage unit to identify a first bank corresponding to the identified second user ID, the
By referring to the third storage unit that stores the group ID and the bank account in association with each other, the second bank account corresponding to the first group ID is specified.
A transfer instruction from the specified first bank account to the specified second bank account is transmitted to the payment processing device.
In response to the payment processing completion notification from the payment processing device, the payment status of the terminal corresponding to the specified second user ID is updated to payment completion for the event.
A trading method characterized by a computer performing processing.

Images