JP2018163597A - Transaction program, transaction apparatus, and transaction method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To facilitate settlement of an event fee.SOLUTION: There is provided a transaction program characterized in making a computer execute processing that when registration of an event associated with a first user ID and a first group ID is received, with reference to a storage unit for storing the group ID and a user ID of a user belonging to the group in association with each other, a user ID belonging to the first group ID is specified, that if a request for application of the event indicated by event information and instructions for settlement processing for an event fee are received from a terminal corresponding to the specified user ID, instructions for remittance from an account stored in association with the specified user ID to an account corresponding to the first user ID or the first group ID are transmitted to a settlement processing apparatus, and that in response to a notice of completion of the settlement processing from the settlement processing apparatus, a settlement status, as to the event, of the terminal corresponding to the specified user ID is updated to completion of the settlement.SELECTED DRAWING: Figure 11

Description

  The present invention relates to a transaction program, a transaction apparatus, and a transaction 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.

  In addition, a technique is known in which payment of event participation fees can be confirmed by linking an SNS (Social Networking Service) and a system of a financial institution such as a bank (see, for example, Patent Document 1).

JP-A-2015-197720

  When paying the event participation fee, it is considered that the event participant often pays the participation fee by handing it to the event organizer or bank transfer from the Internet banking.

  However, in 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 specifying the account of the transfer destination, so it is troublesome to pay the participation fee Cost. At the same time, event organizers and secretaries need time to collect participation fees.

  In one aspect, the present invention is directed to facilitating settlement of event costs.

In one aspect, when registration of an event associated with a first user ID indicating a first user and a first group ID indicating a first group is accepted, the user belongs to the group ID and the group An event application indicated by the event information is identified from a terminal corresponding to the identified user ID by identifying a user ID belonging to the first group ID with reference to a storage unit stored in association with the user ID Upon receiving the request and the instruction for the settlement process related to the event fee, the settlement instruction is transferred 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. The user ID identified with respect to the event in response to a payment processing completion notification from the payment processing device. To update the payment status of the corresponding terminal to the settlement completion,
The processing is executed by a computer.

  Event expenses can be settled easily.

It is a figure which shows an example of the whole structure of the transaction system which concerns on 1st embodiment. It is a figure which shows an example of the hardware constitutions of a computer. It is a figure which shows an example of a function structure of the transaction system which concerns on 1st embodiment. It is a figure which shows an example of student information DB. It is a figure which shows an example of 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 registration process of the event 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 showing an example of an event participation application and participation fee settlement processing according to the first embodiment. It is a figure which shows an example of the screen transition (settlement application of an event participation and payment of a participation expense) in a user terminal. It is a flowchart which shows an example of the specific process of the account and money amount which concern on 1st embodiment. It is a sequence diagram which shows an example of the confirmation process of the participation status of the event which concerns on 1st embodiment. It is a figure which shows an example of the screen transition (confirmation of event participation status and payment status) in a user terminal. It is a figure which shows an example of a function structure of the transaction system which concerns on 2nd embodiment. It is a figure which shows an example of group information DB. It is a flowchart which shows an example of the specific process of the account and money amount which concern on 2nd embodiment.

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

[First embodiment]
<Overall configuration>
First, the whole structure of the transaction system 1 which concerns on this embodiment is demonstrated, referring FIG. FIG. 1 is a diagram illustrating an example of the overall configuration of a transaction system 1 according to the first embodiment.

  As shown in FIG. 1, a 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, and a network N such as the Internet or a dedicated line. It is connected so that it can communicate via.

  The server device 10 requests one or more bank systems 30 to settle a fee (for example, a participation fee for a camp or a welcome party for new students) related to an event in a student life such as a university (for example, a seminar or a club camp, a welcome party for new students) It is a computer. The server device 10 has a transaction program 100.

  The server apparatus 10 accepts registration of events such as seminars and club activities, for example, by the transaction program 100. Further, the server apparatus 10 accepts, for example, a registered application for participation in the event by the transaction program 100, specifies the transfer destination account and the transfer source account of the participation fee, and then determines the participation fee of the event. Request settlement from the bank system 30.

  The user terminal 20 is a computer used by a user (for example, a student such as a university). 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 perform event registration, participation application, payment of participation fee, and the like by the client program 200.

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

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

  A computer 400 shown in FIG. 2 includes 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. 2 includes a RAM (Random Access Memory) 406, a CPU (Central Processing Unit) 407, and an auxiliary storage device 408. These pieces of hardware are connected to each other via a bus 409.

  The input device 401 is, for example, a keyboard, a mouse, a touch panel, etc., and is used to input various operation signals to the computer 400. The display device 402 is a display, for example, and displays various processing results obtained by the computer 400. The server device 10 may not include 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. 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.

  Examples of the recording medium 403a include an SD memory card, a USB memory, a CD (Compact Disk), and a DVD (Digital Versatile Disk).

  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 / F 404. The client program 200 may be acquired (downloaded) from another device via the communication I / F 404, for example.

  The ROM 405 is a nonvolatile semiconductor memory that can retain data even when the power is turned off. The RAM 406 is a volatile semiconductor memory that temporarily stores programs and data. The CPU 407 is an arithmetic device that reads programs and data from the auxiliary storage device 408, the ROM 405, and the like 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 that stores programs and data. Examples of programs and data stored in the auxiliary storage device 408 include an OS (Operating System) that 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 transaction system 1 according to the present embodiment will be described with reference to FIG. FIG. 3 is a diagram illustrating an example of a functional configuration of the transaction 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, A transfer request unit 206, a confirmation request unit 207, a settlement status management unit 208, and a communication unit 209 are included. Each of these functional units is realized by processing that the client program 200 causes the CPU 407 to execute.

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

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

  The display control unit 202 displays various screens. 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 (settlement method selection screen) for selecting a settlement method for the event participation fee.

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

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

  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 event participation fee 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 confirming the participation status of other users who can participate in the event for which the user 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 for identifying an event for which the user has applied for participation, and a category indicating whether 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.

  In addition, when the transfer of the participation fee of the event for which the payment application has been applied for is completed, the payment status management unit 208 updates the payment category of the event included in the payment status 221 to “payment completed”.

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

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

  As illustrated 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 a specific process. Unit 106, transfer request unit 107, participation status confirmation unit 108, settlement status update unit 109, and communication unit 110. Each of these functional units is realized by processing that the transaction program 100 causes the CPU 407 to execute.

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

  Upon receiving an account registration request from the user terminal 20, the account authentication request unit 101 transmits an 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, store number, subject, account number, and password) included in the account registration request.

  If the authentication result for the account authentication request indicates successful authentication, 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. Thereby, the account according to the account registration request is registered in the server device 10. The student information includes various information related to the user (student ID, group ID, account information, etc.).

  When the event information acquisition unit 103 receives an event list acquisition request from the user terminal 20, the event information acquisition unit 103 acquires, from the event information DB 130, event information of events that the user who has transmitted the acquisition request can participate. The event information includes various information related to the event (for example, information indicating a group of users who can participate, information indicating the content of the event, and the like).

  When receiving an event registration request from the user terminal 20, the event registration unit 104 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 a user who can participate in the event that the event has been registered.

  When receiving the transfer request from the user terminal 20, the specific processing unit 106 performs processing (account and amount specifying processing) for specifying the transfer amount, the transfer destination account, and the transfer source account. Here, the specific processing unit 106 includes a money 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 a transfer amount (that is, an event participation fee). The transfer destination account specifying unit 126 specifies the transfer destination account of the transfer amount (that is, the account organizer of the event or the account of the organizer's user). The transfer source account specifying unit 136 specifies the transfer source account of the transfer amount (that is, the account of the user who applied for event participation).

  The transfer request unit 107 transmits a transfer request indicating a transfer instruction to the transfer destination account specified by the specifying 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.

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

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

  The communication unit 110 communicates with the user terminal 20 and the bank system 30. For example, the communication unit 110 returns a response (for example, an event registration result) to various requests from the user terminal 20 to the user terminal 20. For example, the communication unit 110 transmits the above-described 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 illustrating 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 includes, as data items, a student ID, account information, a belonging group ID, and a settlement status.

  The student ID is identification information for identifying the user. The student ID includes, for example, a student ID number. The account information is information on an account used by the user. The account information includes a bank code, a store number, a subject, and an account number. These pieces of information specify the user's account. If the account information is not yet registered, for example, a blank is set in the account information. In the example illustrated in FIG. 4, no account information is set for the student information of the student ID “ZZZ003”.

  The belonging group ID is identification information for identifying the group to which the user belongs. Hereinafter, it is assumed that the group ID for identifying the seminar to which the user belongs is set as the group ID. That is, it is assumed that a group ID indicating a seminar to which the user belongs (for example, “XX seminar”, “ΔΔ seminar”, etc.) is set in the belonging group ID.

  However, the group ID of an arbitrary unit group may be set as the belonging group ID. For example, a group ID indicating “Faculty of Literature” or “School of Science” that is an undergraduate unit may be set in the belonging group ID, or a group ID indicating “Department of Literature or Department of Physics” that is a department unit. May be set. In addition to these, for example, a group ID indicating a group such as a major unit, a lesson unit, a student dormitory unit, a circle unit, or a club activity unit may be set.

  A plurality of group IDs may be set for one student information. For example, one student information includes a first group ID indicating the first belonging group “XX seminar” and a second group ID indicating the second belonging group “light sound circle”. May be.

  The settlement status includes the event ID of the event in which the user participates and the settlement category of the event. Depending on the settlement status, the event in which the user participates and the payment status of the participation fee for 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 illustrated 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, for each student ID, student information including the account information of the user of the student ID, the belonging group ID, and the settlement status.

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

  As shown in FIG. 5, the event information DB 130 stores one or more event information. The event information includes, as data items, 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 an answer deadline. .

  The event ID is identification information for identifying an event. The group ID that can participate is the group ID of a group that can participate in the event. The title is a title (title) used when displaying the event. The purpose, content, and schedule are the purpose, content, and schedule of the event, respectively. The participation fee is a fee necessary for participating in the event.

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

  As described above, the event information DB 130 includes, for each event ID, a group ID, title, purpose, contents, schedule, participation fee, secretary student ID, registration date, and response deadline. Contains event information.

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

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

  In addition to the bank account registration button G101, the top screen G100 shown in FIG. 7 includes a university area button G102 and a company area button G103. By pressing the university area button G102, a transition can be made to a university area screen G210 described later. On the university area screen, you can register and participate in events related to seminars, register and participate in events related to circles, refer to timetables, and refer to guidance from the Student Affairs Division.

  Moreover, it can change to a company area screen by pressing down the company area button G103. On the company area screen, it is possible to apply for various recruitment from companies related to job hunting and to refer to company information.

  Next, when the input receiving unit 201 receives an input of an account registration start operation, the display control unit 202 of the user terminal 20 displays a bank registration screen G110 shown in FIG. 7 (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 designates the bank name of the bank managing his / her account in the bank name designation column G111.

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

  Next, when the input receiving unit 201 receives an input of a screen transition operation, the display control unit 202 of the user terminal 20 displays the account registration screen G120 illustrated 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 designates various information (store number, subject, account number, personal identification number, etc.) of his / her account in the registration content designation field G121.

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

  Next, the account registration request unit 203 of the user terminal 20 transmits an account registration request to the server device 10 via the communication unit 209 (step S106). In the account registration request, the student ID 211 stored in the student ID storage unit 210, the bank code indicating the bank specified in the bank name specification field G111, the store number, the subject specified in the registration content specification field G121, Account number and PIN are included.

  Upon receiving an account registration request from the user terminal 20 via the communication unit 110, the account authentication request unit 101 of the server device 10 transmits an account authentication request to the bank system 30 (step S107). At this time, the account authentication request unit 101 transmits an account authentication request to the bank system 30 of the bank indicated by the bank code included in the account registration request. The account authentication request includes the store number, subject, account number, and password. In the bank system 30, the validity of the account is authenticated in response to the account authentication request. The account validity authentication is, for example, authentication for confirming whether or not there is an account indicated by a store number, a subject, and an account number, and whether or not a password 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 apparatus 10 has received an 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 corresponding student information among the student information stored in the student information DB 120 (step S108). That is, the account registration unit 102 includes the account information of the student information of the student ID included in the account registration request received from the user terminal 20 among the student information stored in the student information DB 120 in the account registration request. Update with bank code, store number, subject and account number. Thereby, the user's account is registered.

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

  Next, when receiving the registration result via the communication unit 209, the display control unit 202 of the user terminal 20 displays a registration completion screen G130 shown in FIG. 7 (step S109). Thereby, 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 user account information in response to a request from the user terminal 20.

<Event registration process>
Next, a process of registering an event that the user uses as the secretary using the user terminal 20 will be described with reference to FIG. FIG. 8 is a sequence diagram showing an example of event registration processing according to the first embodiment.

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

  Next, when the input receiving unit 201 receives an input of a screen transition operation to the university area, the display control unit 202 of the user terminal 20 displays the university area screen G210 illustrated in FIG. 9 (step S202). The university area screen G210 shown in FIG. 9 includes a “semi event” button G211. The user can transition to a “semi-event” screen G220 to be described later by pressing a “semi-event” button G211. Hereinafter, it is assumed that the user performs a screen transition operation to the “semi-event” screen G220 by pressing the “semi-event” button G211.

  In addition to the “semi-event” button G211, the university area screen G210 shown in FIG. 9 includes, for example, a “tuition timetable” button for transitioning to a screen where the class timetable can be referred to, A “Student Division Information” button for transitioning to a screen where guidance can be referred to is included. Further, the university area screen G210 shown in FIG. 9 includes a “circle event” button for transitioning to a screen on which an event related to a circle can be registered and an application for participation can be made.

  Next, the input receiving unit 201 of the user terminal 20 receives an input of a screen transition operation to the “semi 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 an 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 affiliation group ( Affiliation seminar) is specified (step S205). That is, the event information acquisition unit 103 identifies the group ID set as 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 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 event information in which the group ID identified 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 a “semi-event” screen G220 shown in FIG. 9 (step S207). The “semi-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.

  The user can perform an event addition operation for registering a new event by pressing the event addition button G222. Hereinafter, it is assumed that the user performs an event addition operation by pressing the event addition button G222.

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

  Next, when the input receiving unit 201 receives an event addition operation input, the display control unit 202 of the user terminal 20 displays an 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 designates various information (title, purpose, contents, schedule, participation fee, registration date, answer deadline) of the event he / she desires to register in the event information designation field G231.

  Next, the input receiving unit 201 of the user terminal 20 receives an input of an event registration operation (step S210). The user designates various information (title, purpose, content, schedule, participation fee, registration date / time, reply deadline) of the event that he / she desires to register in the event information designation field G231 and then presses the registration button G232. Then, event registration operation can be performed.

  Next, the event registration request unit 205 of the user terminal 20 transmits an event registration request to the server device 10 via the communication unit 209 (step S211). The event registration request includes a student ID 211 stored in the student ID storage unit 210, a group ID indicating the group ID of the user's affiliation seminar, and various types of information specified in the event information specification field G231 (title, Purpose, contents, schedule, participation fee, answer deadline). The group ID that can participate may be specified in the event information specification field G231.

  When receiving an event registration request from the user terminal 20 via the communication unit 209, the event registration unit 104 of the server device 10 creates event information (step S212). That is, the event registration unit 104 generates the event ID and the registration date and time, and creates event information including the event ID, the registration date and time, various information included in the event registration request, and the student ID. 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 in the event information DB 130 (step S213). Thereby, the event is registered.

  Then, the event registration unit 104 of the server device 10 returns a 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 (step S214). That is, the notification unit 105 specifies student information of users belonging to the group indicated by the group ID that can be participated in the event information stored in the event information DB 130 in step S213 described above.

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

  The notification unit 105 may notify that an event has been registered, for example, by displaying a predetermined popup on the user terminal 20 of a user who can participate, or send an email to a preset email address. To notify that the event has been registered. The notification unit 105 may display that the event is registered on the top screen G100 displayed on the user terminal 20 or the like.

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

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

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

  Next, when the input receiving unit 201 receives an input of a screen transition operation to the university area, the display control unit 202 of the user terminal 20 displays the university area screen G210 illustrated in FIG. 11 (step S302). Hereinafter, it is assumed that the user performs a screen transition operation to the “semi-event” screen G220 by pressing the “semi-event” button G211.

  Next, the input receiving unit 201 of the user terminal 20 receives an input of a screen transition operation to the “semi-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 an 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 affiliation group ( 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 a “semi-event” screen G220 shown in FIG. 11 (step S307).

  The user can perform an event selection operation by selecting a button included in the event list G221. Hereinafter, it is assumed that the user selects the “Welcome Party Information” button G222 and performs an event selection operation.

  Next, the input reception unit 201 of the user terminal 20 receives an input of an 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 an input of the event selection operation in which the “welcome party guidance” button G222 is selected, the event participation selection screen G240 shown in FIG. 11 is displayed (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 “Guidance of welcome party”). The user can perform a participation operation by pressing the participation button G241. The user can notify the user who is the organizer of the event of non-participation by pressing the non-participation button.

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

  Next, when the input receiving unit 201 receives an input of a participation operation, the display control unit 202 of the user terminal 20 displays a settlement instruction screen G250 illustrated in FIG. 11 (Step S311). The settlement instruction screen G250 shown in FIG. 11 includes a “bank transfer” button G251 for settlement of the event participation fee by bank transfer. The user can perform a bank transfer operation by pressing a “bank transfer” button G251. It should be noted that the user can also settle the event participation cost by other settlement methods (for example, handing of the participation fee, etc.) by pressing the “other” button.

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

  Next, when the input receiving unit 201 receives an input of a bank transfer operation, the transfer request unit 206 of the user terminal 20 transmits a 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 has been 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.

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

  Next, the transfer request unit 107 of the server device 10 transmits a 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, in response to the transfer request, transfer processing of the transfer amount from the transfer source account to the transfer destination account (that is, settlement processing for event costs) is performed. 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 apparatus 10 has received a 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, the payment status of the corresponding student information among the student information stored in the student information DB 120 is updated (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 settlement status. Thereby, it is managed that the user 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 applied for participation is associated with the payment completion, 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 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 a transfer completion screen G260 shown in FIG. 11 (step S318). The transfer completion screen G260 shown in FIG. 11 displays content indicating that the transfer of the event participation fee has been completed. Thereby, the user can know that the transfer of the participation fee of the event for which he / she applied is completed.

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

  In the example illustrated in FIG. 10, for example, the payment 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 thereto. The event may be, for example, purchase of a textbook. In this case, the textbook cost purchased by the user is settled. Similarly, the event may be payment of a tuition fee, for example, or payment of a food and drink fee in a student canteen or the like. In this way, the events are not limited to welcome parties and camps where users participate, but for example, various events that require payment in student life, such as purchasing textbooks, paying tuition fees, eating and drinking in the student cafeteria, etc. There may be.

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

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

  Next, the bank account identification 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 as 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 account specifying unit 126 refers to the student information DB 120 and specifies the transfer account from the secretary student ID specified in step S402 (step S403). That is, the transfer 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 specifies 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 specifying 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.

<Event participation confirmation process>
Next, a process in which a user confirms another user who applied for participation in an event for which he / she has applied for participation using the user terminal 20 will be described with reference to FIG. FIG. 13 is a sequence diagram illustrating an example of a confirmation process of an event participation status according to the first embodiment. Note that steps S501 to S507 in FIG. 13 are the same as steps S201 to S207 in FIG.

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

  Next, when the input receiving unit 201 receives an input of a screen transition operation to the university area, the display control unit 202 of the user terminal 20 displays the university area screen G210 illustrated in FIG. 14 (step S502). Hereinafter, it is assumed that the user performs a screen transition operation to the “semi-event” screen G220 by pressing the “semi-event” button G211.

  Next, the input receiving unit 201 of the user terminal 20 receives an input of a screen transition operation on the “semi-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 an 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 affiliation group ( 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 “semi-event” screen G220 shown in FIG. 14 (step S507).

  The user can perform an event selection operation by selecting a button included in the event list G221. In the following, it is assumed that the user selects the “Welcome Party Information” button G222 indicating an event for which he has already applied for participation, and performs an event selection operation.

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

  The event detail screen G310 shown in FIG. 14 includes a detail display field G311 in which detailed information (schedule, contents, etc.) of the event is displayed, and a “participation status” button for referring to the participation application status and settlement status of the event. G312 is included. The user can confirm the participation status by pressing the “participation status” button G312.

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

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

  When the participation status confirmation unit 108 of the server apparatus 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 as the group ID that can be participated 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 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 illustrated in FIG. 14 includes a participation status list G321 indicating the participation status (participation or non-participation) of other users who can participate in the event for which the user 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. Thereby, the user can know the participation status of other users who can participate in the event for which he / she applied for participation.

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

  As described above, the server device 10 according to the present embodiment, in response to a request from the user terminal 20, information on other users who can participate in the event for which the user of the user terminal 20 has applied for participation (participation or Non-participation, settlement completion or settlement incomplete etc.) can be displayed. Thereby, the user can easily know the participation status and settlement status in the event in which the user participates.

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

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

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

  As illustrated in FIG. 15, the specific processing unit 106 of the server device 10 according to the present embodiment includes a transfer destination account specifying unit 126A. In addition, the server device 10 according to the present embodiment includes a group information DB 140. The DB can be realized using the auxiliary storage device 408, for example. Note that the DB may be realized using a storage device or the like connected to the server device 10 via the network N.

  The transfer account specifying unit 126A refers to the group information DB 140 and specifies an account corresponding to a group that can participate in the event as the transfer account.

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

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

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

<Account and amount identification processing>
Hereinafter, the account and amount specifying process in step S314 in FIG. 10 will be described with reference to FIG. FIG. 17 is a flowchart illustrating an example of account and amount specifying processing according to the second embodiment. Note that steps S601 and S604 in FIG. 17 are the same as steps S401 and S404 in FIG.

  Subsequent to step S601, the transfer destination account specifying unit 126A specifies the group ID from the received event ID with reference to the group information DB 140 (step S602). That is, the transfer destination account specifying unit 126A specifies the group ID set as the group ID that can be participated 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 specifies the transfer destination account from the group ID specified in step S602 (step S603). That is, the transfer destination account specifying 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 apparatus 10 according to the present embodiment can specify an account corresponding to a group that can participate in an event as a transfer destination account. Thereby, for example, even when a plurality of users register an event of a certain group, the same bank 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 possible within the scope of the gist of the present invention described in the claims.・ Change is possible.

Regarding the above description, the following items are further disclosed.
(Appendix 1)
When registration of an event associated with the first user ID indicating the first user and the first group ID indicating the first group is received, the group ID and the user ID of the user belonging to the group are With reference to the storage unit associated and stored, the user ID belonging to the first group ID is specified,
When receiving an event application request indicated by the event information and an instruction for a settlement process related to the event fee from a terminal corresponding to the specified user ID, the first account is stored in the account stored in association with the specified user ID. Send a payment instruction to the account corresponding to the user ID or the first group ID 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 identified user ID is updated to payment completion for the event.
A transaction program for causing a computer to execute processing.
(Appendix 2)
Notifying the terminal corresponding to the identified user ID that an event that can be applied by the user indicated by the user ID is registered;
The transaction program according to supplementary note 1, which causes a computer to execute processing.
(Appendix 3)
In response to a request from the first terminal corresponding to one user ID of the identified user ID, the settlement status of the terminal corresponding to the identified user ID is displayed on the first terminal.
The transaction program according to appendix 1 or 2, which causes a computer to execute processing.
(Appendix 4)
When registration of an event associated with the first user ID indicating the first user and the first group ID indicating the first group is received, the group ID and the user ID of the user belonging to the group are A specifying unit for specifying a user ID belonging to the first group ID with reference to the storage unit stored in association;
When receiving an event application request indicated by the event information and an instruction for a settlement process related to the event fee from a terminal corresponding to the specified user ID, the first account is stored in the account stored in association with the specified user ID. A transmission unit that transmits a transfer instruction to the account corresponding to the user ID or the first group ID to the payment processing apparatus;
In response to a payment processing completion notification from the payment processing device, an update unit that updates the payment status of the terminal corresponding to the identified user ID to payment completion for the event;
A transaction apparatus comprising:
(Appendix 5)
A notification unit for notifying that an event that can be applied by the user indicated by the user ID is registered in the terminal corresponding to the identified user ID;
The transaction apparatus according to appendix 4, characterized by comprising:
(Appendix 6)
Payment status transmission for causing the first terminal to display the payment status of the terminal corresponding to the specified user ID in response to a request from the first terminal corresponding to one user ID of the specified user IDs The transaction apparatus according to appendix 4 or 5, wherein the transaction apparatus has a portion.
(Appendix 7)
When registration of an event associated with the first user ID indicating the first user and the first group ID indicating the first group is received, the group ID and the user ID of the user belonging to the group are With reference to the storage unit associated and stored, the user ID belonging to the first group ID is specified,
When receiving an event application request indicated by the event information and an instruction for a settlement process related to the event fee from a terminal corresponding to the specified user ID, the first account is stored in the account stored in association with the specified user ID. Send a payment instruction to the account corresponding to the user ID or the first group ID 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 identified user ID is updated to payment completion for the event.
A transaction method characterized in that a computer executes a process.
(Appendix 8)
Notifying the terminal corresponding to the identified user ID that an event that can be applied by the user indicated by the user ID is 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 user ID of the identified user ID, the settlement status of the terminal corresponding to the identified user ID is displayed on the first terminal.
9. The transaction method according to appendix 7 or 8, wherein the computer executes the process.

DESCRIPTION OF SYMBOLS 1 Transaction system 10 Server apparatus 20 User terminal 30 Bank system 101 Account authentication request | requirement part 102 Account registration part 103 Event information acquisition part 104 Event registration part 105 Notification part 106 Specific processing part 107 Transfer request part 108 Participation condition confirmation part 109 Payment status update Department 110 Communication Department 116 Amount Identification Department 120 Student Information DB
126 Bank Account Identification Unit 130 Event Information DB
136 Transfer Source Account Identification Unit 201 Input Accepting 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 Settlement Status Management Unit 209 Communication Unit 210 Student ID Storage Unit 220 Settlement status storage

Claims (5)

When registration of an event associated with the first user ID indicating the first user and the first group ID indicating the first group is received, the group ID and the user ID of the user belonging to the group are With reference to the storage unit associated and stored, the user ID belonging to the first group ID is specified,
When receiving an event application request indicated by the event information and an instruction for a settlement process related to the event fee from a terminal corresponding to the specified user ID, the first account is stored in the account stored in association with the specified user ID. Send a payment instruction to the account corresponding to the user ID or the first group ID 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 identified user ID is updated to payment completion for the event.
A transaction program for causing a computer to execute processing. Notifying the terminal corresponding to the identified user ID that an event that can be applied by the user indicated by the user ID is registered;
The transaction program according to claim 1, wherein the processing is executed by a computer. In response to a request from the first terminal corresponding to one user ID of the identified user ID, the settlement status of the terminal corresponding to the identified user ID is displayed on the first terminal.
The transaction program according to claim 1, wherein the processing is executed by a computer. When registration of an event associated with the first user ID indicating the first user and the first group ID indicating the first group is received, the group ID and the user ID of the user belonging to the group are A specifying unit for specifying a user ID belonging to the first group ID with reference to the storage unit stored in association;
When receiving an event application request indicated by the event information and an instruction for a settlement process related to the event fee from a terminal corresponding to the specified user ID, the first account is stored in the account stored in association with the specified user ID. A transmission unit that transmits a transfer instruction to the account corresponding to the user ID or the first group ID to the payment processing apparatus;
In response to a payment processing completion notification from the payment processing device, an update unit that updates the payment status of the terminal corresponding to the identified user ID to payment completion for the event;
A transaction apparatus comprising: When registration of an event associated with the first user ID indicating the first user and the first group ID indicating the first group is received, the group ID and the user ID of the user belonging to the group are With reference to the storage unit associated and stored, the user ID belonging to the first group ID is specified,
When receiving an event application request indicated by the event information and an instruction for a settlement process related to the event fee from a terminal corresponding to the specified user ID, the first account is stored in the account stored in association with the specified user ID. Send a payment instruction to the account corresponding to the user ID or the first group ID 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 identified user ID is updated to payment completion for the event.
A transaction method characterized in that a computer executes a process.

Images